| 00:00.08 | NetRipper | bedtime |
| 00:00.09 | NetRipper | good night :) |
| 00:01.02 | maejrep | you can enable the kernel options |
| 00:01.10 | maejrep | for sparsemem or discontig |
| 00:01.19 | NetRipper | they're not available in menuconfig |
| 00:01.21 | maejrep | sparsemem is the more recent way |
| 00:01.28 | maejrep | right you need to enable it in Kconfig iirc |
| 00:01.47 | maejrep | its still early |
| 00:01.48 | NetRipper | and it's also not the way they done it in kaiser |
| 00:01.59 | maejrep | you can see some kernel changes in commits where they enable it for certain archs |
| 00:02.14 | maejrep | s/arch/mach/ |
| 00:02.22 | NetRipper | ok |
| 00:05.30 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 00:08.36 | *** join/#htc-linux konsta (n=asds@host81-157-60-163.range81-157.btcentralplus.com) |
| 00:12.02 | *** join/#htc-linux Arto (n=AstainHe@c-67-164-195-234.hsd1.ut.comcast.net) |
| 00:12.04 | maejrep | hmm, spl sends command c4,f,3,x to psoc/navi to get version (what I think is getting version anyway), but my dmesg shows COMMAND_GET_VERSION sends 0x9 to psoc to get version |
| 00:14.36 | maejrep | <PROTECTED> |
| 00:15.04 | maejrep | ^ if that is anything like the keypad driver, you have to do it "a second time" because you have to flush the buffer before the irq is reactivated |
| 00:15.41 | maejrep | it may not be the same, so that might be unnecessary, and could speed things up significantly if removed (?) |
| 00:16.42 | maejrep | hmm, i wonder what it would take to get pdata on i2c chips correctly :x |
| 00:17.49 | Arto | pdata? |
| 00:21.44 | maejrep | ah, *platform_data is already in board_info :) that was obvious |
| 00:26.56 | exco | I just compiled a kernel witz rogro's and dzo's latest changes - but it doesn't boot on Polaris |
| 00:27.29 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 00:28.47 | maejrep | NetRipper: moving navi_info from being hard-coded in navi.c to being pdata passed in from board-raph.c |
| 00:31.25 | *** join/#htc-linux alberink_ (n=alberink@cc206592-b.ensch1.ov.home.nl) |
| 00:31.37 | maejrep | NetRipper: ever seen "WARNING: Bad VDD (0 != 7) for this freq", right after setting up acpu_clk? |
| 00:32.41 | exco | is there already a working kernel for vogue/kaiser with the latest changes (that I can try on Polaris) |
| 00:33.45 | Pure4Real | maejrep: NetRipper went to bed |
| 00:33.49 | maejrep | you can try compiling from latest git |
| 00:33.56 | maejrep | Pure4Real: I know :) but he reads logs |
| 00:34.03 | Pure4Real | ah, ok :) |
| 00:34.50 | exco | well, I did - but it doesn't boot on Polaris, maejrep |
| 00:37.48 | maejrep | how far does it get |
| 00:41.24 | maejrep | [ 6.392147] raph_navi_pad: Version? 0xf buf: 82 0 20 |
| 00:41.25 | maejrep | [ 6.878139] raph_navi_pad: Version? 0x9 buf: 0 0 0 |
| 00:41.35 | maejrep | looks like 0xf is version after all ;o |
| 00:41.53 | maejrep | but 0082 is not what I was expecting |
| 00:50.55 | *** join/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 00:51.00 | asj_xda | hi |
| 00:51.47 | asj_xda | can anyone here try to reach http:/android.ace-com.cz/kernel/ |
| 00:51.48 | asj_xda | ? |
| 00:54.17 | Pure4Real | trying |
| 00:55.03 | asj_xda | it is really strange, because from some destinations it is reachable and from others not and I do not know why |
| 00:55.18 | Pure4Real | ;; Got SERVFAIL reply from 213.156.54.81, trying next server |
| 00:55.18 | Pure4Real | ;; connection timed out; no servers could be reached |
| 00:55.46 | Pure4Real | what is the ip? |
| 00:56.02 | exco | Name:http:/android.ace-com.cz/kernel/ Address: 206.222.226.17 |
| 00:56.54 | asj_xda | ns1.ace-com.cz = 85.70.78.130 |
| 00:57.11 | asj_xda | all the services should be on that IP |
| 00:57.34 | asj_xda | from some destinations it works, from others that gets timeout |
| 00:57.41 | exco | maejrep: are you talking to me? |
| 00:58.09 | asj_xda | if you try to set type=any in nslookup? |
| 00:58.09 | maejrep | I asked how far it gets |
| 00:58.09 | maejrep | the rest was just me |
| 00:58.54 | Pure4Real | asj_xda: i cant get to your webserver using the ip adress 85.70.78.130 |
| 00:59.07 | Pure4Real | that's where i should point my browser to right? |
| 00:59.27 | exco | maejrep: compiles fine - when I try to launch it with haret - the progress bar goes to the right but never finishes |
| 01:00.24 | asj_xda | Pure4Real: Because the server is resolving it only by names not by IP, there is 1 IP for all subdomains |
| 01:00.35 | Pure4Real | ah ok |
| 01:01.57 | asj_xda | but I would guess it should redirect to some default page anyway, I would rather create new server than look for some stupid missconfigurations :D:D:D |
| 01:02.28 | Pure4Real | dont worry about it too much |
| 01:02.43 | Pure4Real | we already have two sites for the kernels |
| 01:03.17 | asj_xda | of course, but i have mailserver here too :D |
| 01:03.24 | asj_xda | this way I am out of my mails |
| 01:04.34 | *** join/#htc-linux Monaro427 (i=root@svalbard.freeshell.org) |
| 01:09.32 | *** join/#htc-linux Orbo_ (n=daniel@zone2.robinson.cam.ac.uk) |
| 01:18.33 | exco | Does anybody know if mullins opened up a Kaiser to identify all the chips? |
| 01:19.31 | maejrep | exco: it never finishes, or it gets to 100% then nothing happens? |
| 01:20.14 | exco | maejrep: it seems to get to 100% and nothing happens |
| 01:20.27 | maejrep | that usually means that the machtype is wrong |
| 01:20.38 | exco | but the polaris one should be working now |
| 01:20.46 | maejrep | make sure your default.txt machtype matches the machtype that is compiled into the kernel you're trying to boot |
| 01:20.54 | exco | I'll try what happens with vogue/kaiser mtype |
| 01:21.14 | maejrep | that may not fix it, just make sure when you compiled it, you compiled support for the polaris |
| 01:21.18 | exco | the kernel should now support vogue & kaiser & polaris' mtype |
| 01:21.46 | maejrep | yes but it may not support those by default.. try: grep CONFIG_MACH_ .config |
| 01:22.12 | exco | CONFIG_MACH_HTCVOGUE=y |
| 01:22.12 | exco | CONFIG_MACH_HTCKAISER=y |
| 01:22.12 | exco | CONFIG_MACH_HTCPOLARIS=y |
| 01:23.25 | maejrep | hmm |
| 01:23.35 | maejrep | dunno then, i don't know much about that branch |
| 01:23.44 | exco | with vogue's mtype it does jump to kernel, but ends with a kernel panic |
| 01:24.21 | exco | I don't even know if it successfully builds for kaiser/vogue atm - because there's no kernel and responses around yet |
| 01:32.10 | maejrep | NetRipper: battery works now, and doesn't break ether ;) |
| 01:37.54 | maejrep | also updates charging status as unplugging/plugging, and switches current with USB/AC plugged in |
| 01:38.01 | maejrep | (AC=900mA, USB=500mA) |
| 01:41.22 | exco | maejrep: doesn't boot with Kaiser mtype either :-( |
| 01:41.39 | maejrep | NetRipper: also increased the msmfb_start_dma warning timeout to 50, so it doesn't warn as often as it is |
| 01:41.40 | exco | so you got battery working for Raphael? |
| 01:41.44 | maejrep | yes |
| 01:42.00 | exco | nice |
| 01:42.13 | Arto | congratz maejrep whats the next step to work on? |
| 01:42.14 | maejrep | still some work to do, but it detects charging status and battery id |
| 01:42.39 | maejrep | current, capacity, level, etc, still need to be worked out |
| 01:42.52 | exco | it doesn't by chance also use the ds2746 :-P |
| 01:42.57 | maejrep | i don't konw what that is |
| 01:44.20 | exco | DS2746 Low-Cost 2-Wire Battery Monitor with Ratiometric A/D Inputs |
| 01:45.23 | maejrep | no idea :| I only know I send a proc_comm command, and read 20 bytes out of smem |
| 01:45.35 | maejrep | then read 2 gpios, and that's it |
| 01:45.42 | maejrep | if that's the same thing, then sure ;) |
| 01:46.47 | maejrep | it works the same way as vogue's battery driver (which is slightly different from raph100) |
| 01:47.21 | maejrep | raph800 is like a cross between vogue and raph100 :p |
| 01:48.07 | exco | you're lucky then ... :-) on Polaris it works different (and unfortunately you're not the one to talk me through it) |
| 01:53.46 | maejrep | how different? |
| 01:53.53 | maejrep | is it direct to i2c? |
| 01:54.03 | maejrep | do you know the i2c chip address for it? |
| 01:54.37 | exco | from what I read it's controlled through i2c |
| 01:55.53 | exco | I don't know anything about that - nor the address ... but ppman made a start here http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=22f9dfdc603d92d48f1e02f548a49b5c733c9307 |
| 01:57.05 | maejrep | kaiser does it same way as polaris? |
| 01:57.34 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 01:57.35 | exco | I think so |
| 01:58.57 | maejrep | does it work? |
| 01:59.12 | maejrep | and does it use i2c_msm, or is it a different i2c bus? |
| 01:59.29 | maejrep | cause using .addr=0 is not going to work appropriately on the msm bus |
| 02:00.22 | maejrep | ugh, that driver uses the old i2c api :| |
| 02:00.29 | exco | I think nobody tried it |
| 02:00.38 | exco | old i2c api - that doesn't sound good now |
| 02:00.45 | maejrep | should read Documentation/i2c/* |
| 02:01.04 | maejrep | things like i2c_probe, attach_adapter, attach_client, etc, are being phased out |
| 02:01.51 | maejrep | have you traced the i2c bus during a battery poll? |
| 02:02.56 | exco | no - but you sure as hell sound like you want to tell me howto do that :-) |
| 02:03.23 | asj_xda | ok pals, enough for today.. have to go to bed.. :) |
| 02:03.27 | asj_xda | CU L8r |
| 02:03.41 | exco | good night asj_xda |
| 02:04.13 | *** part/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 02:05.48 | exco | maejrep: haretconsole is hot :-) |
| 02:05.50 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
| 02:06.57 | maejrep | addlist traces 0xb2300000 / addlist traces 0xb230000c / wirq 1, ibit chatty irqs and traces, then wirq 10 |
| 02:07.29 | miknix | hum.. |
| 02:07.37 | miknix | looks like slashdot was slashdotted |
| 02:07.58 | exco | maejrep: that rebooted my Polaris ;-) |
| 02:08.13 | exco | hope it didn't hardreset |
| 02:08.53 | exco | I got lucky |
| 02:08.57 | maejrep | strange |
| 02:09.11 | maejrep | is your i2c base addr different? |
| 02:09.30 | maejrep | oh, that's why ;x |
| 02:09.37 | maejrep | should have been mmutrace, not traces |
| 02:09.59 | maejrep | addlist mmutrace 0xb2300000 |
| 02:09.59 | maejrep | addlist mmutrace 0xb230000c |
| 02:10.00 | exco | addlist mmutraces 0xb2300000 / 0xb230000c ? |
| 02:10.58 | maejrep | you'll see things like: |
| 02:10.59 | maejrep | haretlog-20090107_202823.log:007862: mmutrace 7803d878: e5853000(str) b2300000 000001c5 (00000000) |
| 02:10.59 | maejrep | haretlog-20090107_202823.log:007862: mmutrace 7803d940: 05852000(str) b2300000 00000200 (00000000) |
| 02:11.04 | maejrep | (a lot of them) |
| 02:11.12 | exco | yeah, I sort of find my way around haretconsole |
| 02:11.17 | maejrep | just copy at least 10 seconds of it to privatepaste.com |
| 02:12.07 | exco | http://pastebin.com/d25c0333b |
| 02:13.32 | exco | 30s : http://pastebin.com/d429c3d79 |
| 02:13.38 | *** join/#htc-linux br1ck (n=br1ck@xdslcn167.osnanet.de) |
| 02:15.37 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 02:17.45 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
| 02:17.56 | *** join/#htc-linux ykut_johny (n=ykut_joh@www.mitsa.org.my) |
| 02:19.20 | maejrep | hmm |
| 02:19.22 | maejrep | that's not useful |
| 02:19.53 | exco | you need more? a different mmutrace address? |
| 02:20.08 | maejrep | show v2p(0xb2300000) |
| 02:21.03 | maejrep | dump mmu 2 0xA9900000 |
| 02:21.15 | maejrep | looks like your virtual mapping is different from ours |
| 02:21.31 | maejrep | try using b2100000 and b210000c instead |
| 02:22.00 | maejrep | 00: Mapping b2300000(@a9b00000) accesses to e1100000 (tbl a9b02402) <-- on my device, b2300000 is a9900000 |
| 02:23.10 | exco | can I abort a "wirq 300" without disconnecting (ctrl+c)? |
| 02:23.52 | maejrep | no |
| 02:24.16 | exco | doesn't show anything else than what's already on pastebin |
| 02:24.28 | exco | (with more time I mean) |
| 02:24.57 | maejrep | what did the dump mmu show? |
| 02:25.06 | exco | show v2p(0xb2300000) |
| 02:25.06 | exco | 0xa9b00000 |
| 02:26.02 | exco | http://pastebin.com/d6233ecd2 |
| 02:26.23 | maejrep | b1f00000 | a9900000 | 1MB section | AP=1 T=2 |
| 02:26.27 | maejrep | that's the one |
| 02:26.36 | maejrep | 0xb1f00000 and 0xb1f0000c |
| 02:28.48 | exco | so addlist mmutrace 0xb1f00000 |
| 02:28.48 | exco | addlist mmutrace 0xb1f0000c? |
| 02:29.11 | maejrep | yes |
| 02:29.39 | exco | in addition to the other ones? |
| 02:30.30 | exco | doesn't look more interesting than before http://pastebin.com/d3a2aa633 |
| 02:32.34 | maejrep | hmm, maybe it doesn't poll every 10 seconds then |
| 02:33.09 | maejrep | or its a different i2c bus |
| 02:33.50 | maejrep | try 0x91f00000 and 0x91f0000c |
| 02:33.57 | maejrep | could be a different virtual bindnig |
| 02:34.01 | exco | shouldn't it be 0xa9b00000 -> b2300000 ? |
| 02:34.18 | maejrep | the physical address for i2c should be the same for all msm machines |
| 02:34.28 | maejrep | which is 0xa9900000 |
| 02:34.38 | maejrep | on my machine, that maps to 0xb2300000 |
| 02:34.47 | exco | that's what show v2p(0xb2300000) gives |
| 02:34.47 | maejrep | on your machine its 0x91f00000 and 0xb1f00000 |
| 02:34.53 | maejrep | forget b2300000 |
| 02:35.33 | maejrep | that's wrong for your device |
| 02:35.34 | maejrep | b2300000 is 0xa9b00000 on your device, which is the wrong physical address |
| 02:36.06 | maejrep | clearlist mmutrace, then add those 91f* addresses ^ |
| 02:38.12 | exco | still nothing new |
| 02:38.44 | exco | http://pastebin.com/d27c108f5 |
| 02:42.58 | maejrep | so then how do you know the battery works over i2c? |
| 02:43.52 | maejrep | surely someone traced it over i2c in order to know that |
| 02:44.01 | maejrep | and this is showing that nothing is going over i2c |
| 02:44.50 | maejrep | do you have battery.dll and battdrvr.dll? can you upload them to www.privatepaste.com/upload |
| 02:50.56 | exco | I will upload it in a second |
| 02:51.35 | *** join/#htc-linux Moku (n=John@f049172166.adsl.alicedsl.de) |
| 02:54.54 | exco | no battery.dll - only battdrv.dll on my device http://www.privatepaste.com/aeQx8zvgYW |
| 03:00.04 | exco | dzo: your latest commit is broken :-) |
| 03:01.31 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 03:03.41 | *** join/#htc-linux venny_ (i=Travis@h216-45-127-2.dynamic.platinum.ca) |
| 03:16.19 | Pure4Real | dzo: build of kaiser kernel fails because of missing board-vogue.h |
| 03:16.42 | Pure4Real | it happens since the latest commit |
| 03:17.25 | Pure4Real | or latest two commits |
| 03:19.40 | exco | yeah error: board-vogue.h: No such file or directory - since the latest commit |
| 03:20.57 | exco | Also Polaris doesn't boot with the kernel built after the previous commit (that might not be related tough) |
| 03:53.59 | *** join/#htc-linux PoohbaLT (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net) |
| 03:56.06 | cr2 | maejrep: psoc detect cmd is 9 ? |
| 03:57.03 | maejrep | cr2: version is 0xf i think |
| 03:57.37 | maejrep | but it returns 8200 |
| 03:58.03 | cr2 | i thought it was 2 bufeers, need to check |
| 03:58.07 | cr2 | 22:44:29 [D:KEY] [I2C_WB] (0xcc, 0x20, 0x4c)! |
| 03:58.20 | maejrep | cc is microp |
| 03:59.02 | cr2 | i2c_wr(cc,20,2,0) |
| 03:59.07 | cr2 | it's from my lcd init |
| 03:59.23 | cr2 | and you have |
| 03:59.26 | cr2 | i2c wr: cc,20,29,0 |
| 04:00.46 | maejrep | ah |
| 04:01.40 | cr2 | 1. memset x12 and memset x20 bufs |
| 04:02.34 | cr2 | move 9 in the 0x12 buf |
| 04:02.40 | cr2 | and call |
| 04:02.50 | cr2 | c4,0,1,*buf |
| 04:03.21 | cr2 | msleep 20 |
| 04:04.09 | cr2 | then pick 3 byte values from the buf |
| 04:04.17 | cr2 | offsets 0x10 |
| 04:04.40 | cr2 | x9 and x8 |
| 04:05.08 | maejrep | hmm |
| 04:05.19 | cr2 | it's the first stage |
| 04:05.31 | cr2 | you may just dump the full 0x12 buf |
| 04:05.51 | cr2 | then : |
| 04:06.37 | cr2 | clean the x12 buf |
| 04:06.57 | cr2 | and send |
| 04:07.10 | cr2 | c4,1,0x12,*buf12 |
| 04:07.51 | cr2 | the 3 bytes should match |
| 04:08.01 | cr2 | otherwise it loops 3 times |
| 04:08.37 | maejrep | it resends the command 3 times? |
| 04:08.49 | cr2 | check the third byte =1 or 5 |
| 04:09.13 | cr2 | yes, there is some logic here, i'll check |
| 04:09.22 | maejrep | <maejrep> [ 6.392147] raph_navi_pad: Version? 0xf buf: 82 0 20 |
| 04:09.22 | maejrep | <maejrep> [ 6.878139] raph_navi_pad: Version? 0x9 buf: 0 0 0 |
| 04:09.49 | cr2 | yes, it loops 3 times, if at least 1 does not match |
| 04:10.43 | cr2 | thrird byte 1,5 ottherwise psoc worng platform |
| 04:11.10 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
| 04:11.29 | cr2 | the second byte is dvt/cvt/pvt |
| 04:11.49 | maejrep | ah |
| 04:11.50 | maejrep | ok |
| 04:11.58 | maejrep | know what those mean? :) |
| 04:12.00 | maejrep | mine shows EVT |
| 04:12.02 | cr2 | 1 is raph, 5 is herm |
| 04:12.20 | cr2 | swetland said what it means, i've forgot |
| 04:12.43 | cr2 | engineering,validated, something |
| 04:13.26 | cr2 | development stages |
| 04:13.53 | cr2 | hmm. why the 0x20 buf... |
| 04:15.30 | cr2 | ok, it's a tricky stack buf layout |
| 04:18.04 | cr2 | r4-r7,lr |
| 04:18.17 | cr2 | 1 2 3 4 5 |
| 04:18.26 | cr2 | and sub 0x40 |
| 04:20.13 | swetland | engineering verification test |
| 04:21.03 | maejrep | cr2: just looked at the tricolor screen's code in spl... it writes it in RGB565 packing |
| 04:21.28 | maejrep | which is odd, cause it looks correct to me... so does that mean spl is initializing the panel in 565 mode? |
| 04:21.57 | cr2 | swetland: thanks |
| 04:22.22 | cr2 | maejrep: i think the spl operates in a different mode ? |
| 04:22.34 | cr2 | maejrep: it does not use mdp ? |
| 04:22.38 | maejrep | the panel is in a different mode? |
| 04:22.51 | cr2 | no, the mdp-less mode |
| 04:23.23 | cr2 | because the mdp has *ibuf*565 , but the panel*666 |
| 04:23.50 | cr2 | mdp can also control tvout |
| 04:24.44 | cr2 | hmm. do you think raph800 has toshiba _and_ epson at the same time ? |
| 04:25.05 | maejrep | that would be tricky |
| 04:25.25 | maejrep | but i thought toshiba was the controller, and epson the panel |
| 04:25.41 | maejrep | (except on raph100 and trout, which have toshiba controller *and* panel)? |
| 04:26.13 | maejrep | in trout-panel, it runs the first toshiba_init table, then runs a panel-specific init table, based on the panel id |
| 04:26.14 | cr2 | panel is a different thing |
| 04:26.31 | cr2 | i think we have hitachi with NetRipper |
| 04:27.20 | maejrep | spl says I have hitachi |
| 04:27.31 | cr2 | imho, it's mddi -> mdc (toshi/epson) -> panel (hitachi,toshiba,toppoly,whatever else) |
| 04:27.46 | cr2 | ok, so you have the same panel |
| 04:28.06 | cr2 | on toshiba mdc (mddi client) |
| 04:28.09 | maejrep | I do get mddi timeouts with my current -panel |
| 04:28.25 | cr2 | you need to query the local gpios to detect the panel. |
| 04:28.34 | maejrep | I get panel_id = 0x3 |
| 04:28.36 | cr2 | similar to g1, but the bit menaing is different |
| 04:28.52 | cr2 | on epson, the gpios are at a different place. |
| 04:29.12 | cr2 | so imho your panel_id is meaningless ;) |
| 04:29.27 | maejrep | :( |
| 04:30.05 | maejrep | does that mean none of trout's -panel code is usable for me? ;p |
| 04:30.51 | maejrep | btw, I changed clock-wince.c to enable PMDH_CLK using the +0x8c bits |
| 04:31.05 | cr2 | unless you can prove that raph800 has both epson and toshiba, it's not very useful |
| 04:31.27 | cr2 | clock-wince needs even much more changes... |
| 04:31.33 | maejrep | I know |
| 04:32.02 | cr2 | i think your panel-id needs the epson gpio anyway. |
| 04:32.23 | cr2 | we should document the code as is, and then decide what to do. |
| 04:32.48 | maejrep | board-panel? |
| 04:33.10 | cr2 | [05:28] <maejrep> I get panel_id = 0x3 |
| 04:33.26 | cr2 | you mean in wince smem ? |
| 04:33.36 | maejrep | no, using the current -panel code :p |
| 04:33.55 | maejrep | in spl, "display 2" returns current panel type = HITACHI |
| 04:34.10 | maejrep | in wince: 04:02:45 [D:DISP] g_CurrentPanelType=5... |
| 04:34.54 | cr2 | i will trust "HITACHI" more than the index |
| 04:35.13 | cr2 | afair the index on raph800 is double converted |
| 04:35.19 | maejrep | and in board-panel, the panel id detection always returns 3, but that's using the trout panel id code |
| 04:35.22 | cr2 | probably to match the raph100 ids |
| 04:35.45 | cr2 | trout panel id code does not apply. that's 100% sure |
| 04:35.51 | maejrep | ok |
| 04:36.41 | cr2 | btw, about the clocks |
| 04:37.10 | cr2 | i think it will be possible to find the serial clock algorithm |
| 04:37.21 | cr2 | but i don't know if we really need it. |
| 04:37.32 | maejrep | so that's R0 = 5, to get "HITACHI" |
| 04:37.54 | cr2 | the 115200 MD/NS setting for uart2DM is known. |
| 04:38.04 | cr2 | maejrep: i'll check now |
| 04:38.22 | cr2 | MDDI client Epson S1D13774 (raph800 and blac100) |
| 04:38.30 | cr2 | <PROTECTED> |
| 04:38.32 | cr2 | <PROTECTED> |
| 04:38.47 | cr2 | these regs are used for panel detection on raph800 |
| 04:40.50 | maejrep | yeah I have some notes on that |
| 04:40.58 | maejrep | but I really don't know what those are |
| 04:41.20 | maejrep | like how to I put that into code, using existing APIs if possible :p |
| 04:41.51 | maejrep | (i dont know if its mddi_write(), mddi_remote_write, etc) |
| 04:42.26 | maejrep | there's also two branches there, and I can't tell which branch it's actually taking |
| 04:43.22 | cr2 | mddi_write is for the mddi.c only |
| 04:43.37 | cr2 | for the PMDH initial setup |
| 04:43.48 | maejrep | ok, and that's the same between raph100 and 800 |
| 04:43.55 | cr2 | which has hardcoded values now, btw. it'l in wiki already |
| 04:44.09 | maejrep | yeah, I've changed those values in mddi.c |
| 04:44.11 | cr2 | raph100 and raph800 have some differences there |
| 04:44.16 | maejrep | to match the wiki |
| 04:44.25 | cr2 | and the pmdh clock timing. a19 vs a41 afair |
| 04:44.27 | maejrep | 0x68 PAD_CTL 0xa850f 0xa8505 0xa850f |
| 04:44.32 | maejrep | that's the only difference |
| 04:44.51 | cr2 | not the only |
| 04:44.51 | maejrep | and DRIVE_LO is different also |
| 04:44.57 | cr2 | yes |
| 04:45.14 | maejrep | that's gonna be a pain :x |
| 04:45.31 | cr2 | i mean different to g1 |
| 04:45.42 | maejrep | oh i meant different between raph100 and raph800 |
| 04:46.10 | cr2 | clk/dev g1 raph100 blac100 raph800 |
| 04:46.22 | cr2 | <PROTECTED> |
| 04:47.10 | cr2 | http://wiki.xda-developers.com/index.php?pagename=MSM_CLK |
| 04:48.13 | maejrep | I don't understand that.. it's not a rate right? |
| 04:48.19 | maejrep | what is a41? |
| 04:48.26 | cr2 | hmm. mdc_clk and mdp_clk need to be separared... |
| 04:48.31 | cr2 | the NS setting |
| 04:48.47 | cr2 | mddi_clk does not use MD |
| 04:48.56 | cr2 | i2c too |
| 04:49.12 | maejrep | <PROTECTED> |
| 04:49.27 | cr2 | yes |
| 04:49.44 | maejrep | in clkregime, that gets ORR 0xa00 |
| 04:49.53 | maejrep | where did you find the 0x41 of that? |
| 04:50.03 | cr2 | some other S bits |
| 04:50.28 | cr2 | you need a cpu manual to know for sure ;) |
| 04:50.40 | cr2 | 0xa00 is some basic setting. |
| 04:50.59 | cr2 | then you have 0xb00 for clocks using MD |
| 04:51.06 | cr2 | one more bit |
| 04:51.12 | maejrep | a8600080 | 00000a00 00004a80 00000200 00000a04 | .....J.......... |
| 04:51.19 | cr2 | and some other bits |
| 04:51.28 | cr2 | don't trust the dumped values |
| 04:51.55 | cr2 | we know since the SDC clocks that the values you read back != the written there. |
| 04:52.10 | cr2 | at least not always. |
| 04:52.47 | maejrep | ok |
| 04:52.55 | cr2 | the spl sets 0xa41 |
| 04:53.16 | cr2 | disptools may be different, but i doubt it. |
| 04:53.31 | maejrep | so I was only setting the 0x800 and 0x200 bits in that reg for PMDH_CLK, should I add 0x41 as well, or is that already in place from somewhere else? |
| 04:53.41 | maejrep | disptools doesn't set it directly |
| 04:53.44 | maejrep | it uses clkregime.dll |
| 04:53.56 | maejrep | to enable clock 0x38 iirc |
| 04:54.07 | maejrep | which clkregime enables by setting 0xa00 in the 8c reg |
| 04:54.10 | cr2 | if you control the mddi_clk directly, set the 0xa41 for raph800 |
| 04:54.17 | maejrep | ok |
| 04:54.34 | cr2 | i have 0xa19 |
| 04:55.05 | maejrep | in a dump? |
| 04:55.16 | cr2 | no, in the spl |
| 04:55.21 | maejrep | ah |
| 04:55.26 | cr2 | and in the wince kernel too. |
| 04:55.59 | maejrep | LDR R2, =0xB320008C |
| 04:55.59 | maejrep | MOVL R3, 0xA41 |
| 04:56.05 | maejrep | heh, didn't notice that before :p |
| 04:56.37 | cr2 | the htc clock control on msm is a real mess. partial direct control + 2 apis ;) |
| 04:58.04 | maejrep | ;x |
| 04:59.05 | maejrep | so: panel_id = (client_data->remote_read(client_data, GPIODATA) >> 4) & 3; |
| 04:59.12 | maejrep | that is different for epson? |
| 05:00.43 | cr2 | yes |
| 05:00.59 | cr2 | GPIODATA is for toshiba |
| 05:01.42 | cr2 | for epson you need to use those |
| 05:01.45 | cr2 | GPIOP_CONFIG 0x0300 |
| 05:01.47 | cr2 | <PROTECTED> |
| 05:01.48 | cr2 | <PROTECTED> |
| 05:02.00 | maejrep | but is that done with remote_read() ? |
| 05:02.03 | cr2 | not yet documented though |
| 05:02.36 | cr2 | yes. it's the remote mdc, not the local pmdh registers |
| 05:02.46 | cr2 | think mddi == spi |
| 05:03.02 | *** join/#htc-linux Tinyboom (n=nahh@85.84-49-89.nextgentel.com) |
| 05:03.08 | cr2 | you setup the contrller first. |
| 05:03.20 | cr2 | and then talk to the "client" over the serial bus. |
| 05:04.51 | maejrep | MOV R1, #0 |
| 05:04.51 | maejrep | MOV R0, #0x300 |
| 05:04.51 | maejrep | BL sub_8802DB94 |
| 05:04.56 | maejrep | that's write? |
| 05:05.07 | maejrep | MOV R0, #0x300 |
| 05:05.07 | maejrep | BL sub_8802DC68 |
| 05:05.08 | maejrep | and read? |
| 05:06.11 | cr2 | mddi_remote_write_r0_r1 and mddi_remote_read_r0 |
| 05:06.14 | cr2 | yes |
| 05:06.41 | maejrep | i see |
| 05:06.49 | cr2 | just rename them right now |
| 05:06.52 | cr2 | 'n' |
| 05:09.04 | maejrep | <PROTECTED> |
| 05:09.20 | *** join/#htc-linux Zack84a (n=zack84a@r74-192-0-176.bcstcmta01.clsttx.tl.dh.suddenlink.net) |
| 05:09.39 | maejrep | with panel_id = read(324) & 0x3000 |
| 05:09.49 | maejrep | >> 12 |
| 05:11.45 | maejrep | gonna boot with that and some printks to see what is actually returned |
| 05:11.56 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) |
| 05:14.04 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
| 05:14.19 | cr2 | ok |
| 05:14.49 | maejrep | freezes after the init() printk |
| 05:15.14 | maejrep | <PROTECTED> |
| 05:15.54 | Arto | hiya maejrep |
| 05:16.37 | maejrep | i think that was the clock, cr2 |
| 05:16.44 | maejrep | changing it back to just a00 |
| 05:18.32 | maejrep | hi |
| 05:19.31 | *** join/#htc-linux TheOther (n=nahh@92.80-202-157.nextgentel.com) |
| 05:20.43 | maejrep | cr2: |
| 05:20.46 | maejrep | [ 9.447628] htcraphael_mddi_epson_client_init: write(300,0); read(300) => 203f |
| 05:20.46 | maejrep | [ 9.528164] htcraphael_mddi_epson_client_init: write(30c,3000); read(324) => 283f |
| 05:20.46 | maejrep | [ 9.608333] htcraphael_mddi_epson_client_init: adjusted panel id = 2 |
| 05:20.47 | maejrep | :X |
| 05:20.56 | maejrep | I'm guessing that's right |
| 05:21.15 | maejrep | (2 != 3 and != 1, thus it sets r3=5 |
| 05:21.54 | maejrep | which then is interpreted as hitachi |
| 05:22.02 | cr2 | ok |
| 05:24.16 | cr2 | 0xa00 means slower speed i think. |
| 05:24.52 | cr2 | a8600080 | 00000a00 00004a80 00000600 00000a0c |
| 05:25.00 | cr2 | 0xa0c read on raph |
| 05:25.10 | cr2 | which should be 0xa19 |
| 05:25.54 | Arto | working on fixing lcd maejrep? |
| 05:26.11 | cr2 | maejrep: is the MDP area dumpable ? |
| 05:30.24 | maejrep | i'm not sure |
| 05:31.29 | cr2 | maejrep: the epson init is rather transparent |
| 05:31.38 | maejrep | as in easy? :) |
| 05:31.48 | cr2 | 18=3bf |
| 05:31.59 | cr2 | 28=205 |
| 05:32.06 | cr2 | and so only |
| 05:32.14 | cr2 | only the spi init is tedious |
| 05:32.21 | maejrep | cr2: it does still use the 150000 etc remote regs, it seems |
| 05:33.06 | cr2 | yes, i see it too. that's why i'm a bit surprised |
| 05:33.12 | maejrep | cause even after setting panel id (r3=5), it does 150004 = 3cf |
| 05:33.35 | maejrep | gonna try to dump mdp |
| 05:33.41 | cr2 | yes. so it's a question |
| 05:33.43 | maejrep | but it might not be readable |
| 05:33.52 | cr2 | does disptools have it too ? |
| 05:34.20 | *** join/#htc-linux Tinyboom (n=nahh@112.80-202-155.nextgentel.com) |
| 05:34.24 | cr2 | btw, dump the product id 0 and 1 from epson |
| 05:34.40 | maejrep | 92500000 | aa200000 | 1MB section | AP=1 T=2 |
| 05:34.40 | maejrep | b2500000 | aa200000 | 1MB section | AP=1 T=2 |
| 05:35.24 | maejrep | looks like it is readable |
| 05:36.04 | cr2 | ok |
| 05:36.20 | maejrep | what would be useful about it |
| 05:37.06 | maejrep | http://www.privatepaste.com/570yTmA1v1 -- mdp dump |
| 05:37.35 | maejrep | product id 0 and 1, can I do that from haret, or should I use remote_read? |
| 05:38.09 | cr2 | remote_read |
| 05:38.25 | cr2 | you can read some other regs too |
| 05:38.29 | cr2 | like sdram cfg |
| 05:39.20 | maejrep | <PROTECTED> |
| 05:40.47 | cr2 | yes |
| 05:40.50 | cr2 | clock source |
| 05:40.53 | cr2 | pin driver ctrl |
| 05:41.37 | cr2 | there is a big init blob here. |
| 05:43.37 | maejrep | but I need to define a lot of macros to be able to do it easily |
| 05:46.20 | cr2 | like for g1 |
| 05:46.38 | cr2 | many more epson regs are initialized through this table |
| 05:46.49 | cr2 | (reg,val) all 16bit |
| 05:46.58 | cr2 | but the init depends on the panel |
| 05:47.21 | cr2 | looks like g1 code actually. not surprising though :) |
| 05:47.26 | maejrep | there are some things that can't be done in the table though |
| 05:47.38 | maejrep | like the loop for 0x2c / POWER_SAVE |
| 05:48.45 | cr2 | the table is huge. |
| 05:48.55 | cr2 | time to split the toshiba and epson page |
| 05:49.12 | cr2 | ok |
| 05:51.49 | cr2 | maybe several columns for the panels |
| 05:54.29 | maejrep | did you find anything useful in the mdp dump? |
| 05:55.33 | maejrep | ok, something I did made the panel very unhappy :) |
| 05:55.53 | cr2 | it should be compared to g1 |
| 05:55.53 | cr2 | hehe |
| 05:55.53 | maejrep | it's shifting all over the place :p |
| 05:56.00 | cr2 | vsync ? |
| 05:57.26 | maejrep | http://www.privatepaste.com/7b0KUZmByE |
| 05:58.10 | maejrep | I think it was adding these to the init table: |
| 05:58.10 | maejrep | <PROTECTED> |
| 05:58.10 | maejrep | <PROTECTED> |
| 05:58.27 | maejrep | gonna take those out and only work with reads first :p |
| 06:01.21 | maejrep | hmm, same read errors |
| 06:01.30 | maejrep | panel didn't go haywire this time at least |
| 06:02.19 | cr2 | ok |
| 06:03.08 | cr2 | hmm. looks like it all failed |
| 06:03.31 | cr2 | ok, the init tables ned to be added to wiki |
| 06:07.10 | maejrep | might be the clock.. I did another change that might have affected it.. gonna go back to just |0xa00 and see if that lets me read properly again |
| 06:07.28 | cr2 | ok |
| 06:07.42 | cr2 | the block starts with reg30 |
| 06:07.59 | maejrep | i really wish wince didnt take so long to boot >:/ |
| 06:08.23 | cr2 | hehe |
| 06:08.33 | cr2 | 30 is not in the list... |
| 06:09.00 | maejrep | neither was 30c |
| 06:09.45 | maejrep | just got a kernel panic, crc error on initramfs :| |
| 06:10.22 | maejrep | which means another 5 minutes while wince boots and decides to let me recopy the image and reboot |
| 06:12.41 | cr2 | hmm |
| 06:16.10 | maejrep | looks like it was the clock |
| 06:16.55 | maejrep | [ 9.642208] htcraphael_mddi_epson_client_init: adjusted panel id = 2 |
| 06:16.55 | maejrep | [ 9.723354] htcraphael_mddi_epson_client_init: PRODUCT0 => 0 |
| 06:16.55 | maejrep | [ 9.804500] htcraphael_mddi_epson_client_init: PRODUCT1 => 46 |
| 06:16.55 | maejrep | [ 9.885585] htcraphael_mddi_epson_client_init: SDRAM_STATUS => 121 |
| 06:16.55 | maejrep | [ 9.966793] htcraphael_mddi_epson_client_init: CLOCK_SOURCE => 31a |
| 06:16.56 | maejrep | [ 10.047908] htcraphael_mddi_epson_client_init: PIN_DRIVE_CTRL => 3bf |
| 06:16.58 | maejrep | [ 10.129024] htcraphael_mddi_epson_client_init: POWER_SAVE => 123 |
| 06:17.23 | maejrep | MOVL R1, 0x205 |
| 06:17.23 | maejrep | MOV R0, #0x28 |
| 06:17.29 | maejrep | different CLOCK_SOURCE |
| 06:21.37 | lama | ah |
| 06:21.57 | lama | there is linux kernel for g900 |
| 06:22.35 | lama | http://goandroid.net/news/a-73.html |
| 06:26.34 | *** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net) |
| 06:34.16 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 06:36.02 | *** join/#htc-linux lpotter (n=ljp@58.173.176.153) |
| 06:38.52 | maejrep | cr2: i made my panel unhappy again :p |
| 06:39.53 | maejrep | [ 9.752468] htcraphael_mddi_epson_client_init: adjusted panel id = 2 |
| 06:39.53 | maejrep | [ 9.833645] htcraphael_mddi_epson_client_init: PRODUCT0 => 0 |
| 06:39.53 | maejrep | [ 9.914913] htcraphael_mddi_epson_client_init: PRODUCT1 => 46 |
| 06:39.53 | maejrep | [ 9.996151] htcraphael_mddi_epson_client_init: SDRAM_STATUS => 121 |
| 06:39.53 | maejrep | [ 10.079189] htcraphael_mddi_epson_client_init: CLOCK_SOURCE => 205 |
| 06:39.54 | maejrep | [ 10.174892] htcraphael_mddi_epson_client_init: PIN_DRIVE_CTRL => 3bf |
| 06:39.56 | maejrep | [ 10.256069] htcraphael_mddi_epson_client_init: POWER_SAVE => 12b |
| 06:39.58 | maejrep | [ 10.337215] htcraphael_mddi_epson_client_init: MAIN_PATH_CONFIG => 505 |
| 06:42.37 | cr2 | ok |
| 06:43.08 | maejrep | I think we can't do the init the same way spl does, at least with the table |
| 06:43.23 | maejrep | we'd basically have to do the init in the function |
| 06:43.30 | maejrep | there's too much logic involved |
| 06:47.14 | cr2 | i'll try to document all what i've found |
| 06:48.29 | cr2 | so the init can be done as in spl |
| 06:48.39 | cr2 | the spi init is a different issue |
| 06:49.56 | cr2 | cc,20,29 is the first step in hitachi lcd poweron |
| 06:50.34 | cr2 | and then a lof of spi commands |
| 06:51.41 | *** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
| 06:52.04 | maejrep | saw that |
| 06:52.21 | cr2 | should be documented too |
| 06:54.11 | maejrep | i'll try turning that init into pseudo code |
| 06:54.21 | maejrep | but for now, need sleep |
| 06:54.37 | cr2 | i'll leave to work :) |
| 06:54.45 | maejrep | lol :x |
| 06:54.57 | cr2 | bbl |
| 07:16.56 | *** join/#htc-linux kiozen (n=oeichler@p54922361.dip0.t-ipconnect.de) |
| 07:38.19 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 07:45.31 | *** join/#htc-linux ALoGeNoff (n=alogeno@5.pool85-60-50.dynamic.orange.es) |
| 07:59.09 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 08:10.05 | *** join/#htc-linux Guest25258 (n=root@87.72.13.87) |
| 08:14.27 | Guest25258 | q |
| 08:16.19 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
| 08:16.50 | *** join/#htc-linux opennandra (n=opennand@80.122.179.98) |
| 08:21.54 | *** join/#htc-linux mrkllman (n=root@87.72.13.87) |
| 08:22.07 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 08:26.38 | *** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
| 08:27.23 | *** join/#htc-linux timebomb (n=tb@e176126040.adsl.alicedsl.de) |
| 08:47.57 | NetRipper | maejrep, yes i have seen that Bad VDD stuff.. but doesn't happen always |
| 08:48.21 | NetRipper | somehow i didnt get it when i changed memory map, but that may just 've been coincedence |
| 08:50.59 | *** join/#htc-linux Kensan_ (n=ken@gw.ptr-80-238-228-35.customer.ch.netstream.com) |
| 08:51.34 | NetRipper | maejrep, good job about the battery :) |
| 08:52.17 | NetRipper | maejrep, and for that navi, are there also differences between raph100/raph800 regarding that? or are you moving to pdata to make it nicer? |
| 08:59.55 | opennandra | http://open-nandra.com/?p=87&preview=true |
| 09:01.32 | *** join/#htc-linux Guest55673 (n=root@87.72.13.87) |
| 09:16.53 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089c53.pool.mediaWays.net) |
| 09:39.27 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 10:20.53 | *** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl) |
| 10:27.16 | *** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) |
| 11:18.02 | *** join/#htc-linux exco (n=exco@e181120013.adsl.alicedsl.de) |
| 11:40.31 | *** join/#htc-linux Pure4Real (n=pure4rea@89-97-140-219.ip17.fastwebnet.it) |
| 11:46.02 | *** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) |
| 11:46.55 | dcordes_ | opennandra: nice. which kernel version? |
| 11:50.05 | *** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) |
| 11:52.16 | exco | dzo: Your package should now be called for Vogue, Kaiser and Polaris ;-) |
| 11:54.02 | opennandra | dcordes: 2.6.25 |
| 11:54.06 | opennandra | based on linwizard |
| 11:54.17 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 11:56.22 | opennandra | dcordes: I would like to try port openmoko to this |
| 11:56.28 | opennandra | would be challenge for me ;D |
| 11:57.38 | dcordes_ | opennandra: does the modem use one at line for communication with system? |
| 11:58.24 | opennandra | dcordes_: ? don't understand your quesion sorry |
| 11:59.15 | dcordes_ | opennandra: what is the gsm modem in oxygen? |
| 11:59.33 | opennandra | hmm don't know yet |
| 11:59.44 | opennandra | it would be next step to work with modem |
| 11:59.58 | opennandra | but something similar to typhoon I suppose |
| 12:00.01 | opennandra | or like in wizard |
| 12:00.11 | opennandra | I see some driver and I would like to test |
| 12:03.07 | opennandra | dcordes_: why you asking? |
| 12:16.13 | dcordes_ | opennandra: to evaluate what userspace stuff we need for the modem |
| 12:16.18 | dcordes_ | in openmoko |
| 12:22.23 | opennandra | dcordes_ ok |
| 12:22.53 | opennandra | I think I will try openmoko rootfs from here : http://grigio.org/howto_openmoko_htc_magician_s100_dual_boot_wince |
| 12:24.55 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089c53.pool.mediaWays.net) |
| 12:42.46 | ali1234 | dcordes_: all the omap850s have the same modem, it currently has no real driver, just experimental code |
| 12:47.28 | dcordes_ | ali1234: you can talk to it? |
| 12:48.59 | *** join/#htc-linux ClashTheBunny (i=c72ec6e7@gateway/web/ajax/mibbit.com/x-2aecf45d3a9e38d4) |
| 12:50.48 | *** join/#htc-linux pawel (n=pawel@195.205.38.95) |
| 12:53.23 | ali1234 | dcordes_: yeah |
| 13:00.14 | opennandra | dcordes_: it's based on vivien gsm driver? |
| 13:00.35 | opennandra | sorry |
| 13:00.44 | opennandra | ali1234: it's based on vivien gsm driver? |
| 13:14.32 | ali1234 | opennandra: the experimental code is, yeah |
| 13:14.36 | lupine_85 | dcordes_: not yet, I've been snowed under at work |
| 13:14.38 | ali1234 | that isn't really what i would call a driver |
| 13:15.01 | ali1234 | since it doesn't implement a proper tty device, it cannot be used with any existing software package |
| 13:15.02 | lupine_85 | there's no package out there which does exactly what I want, so I'll be knocking some ruby scripts together to do the work at some point |
| 13:15.59 | ali1234 | opennandra: we found some omap driver for 2.4 in a manufacturer GPL release tarball, it looks like a much better way to go |
| 13:16.21 | ali1234 | for linux kernel 2.4 that is, it needs to be ported |
| 13:18.22 | opennandra | ali1243: hmm could you post me a tarball and why vivien driver isn't good point to start? |
| 13:18.41 | opennandra | I see also some modifications in linwizard tree |
| 13:19.02 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089c53.pool.mediaWays.net) |
| 13:19.24 | opennandra | http://git.lurian.net/?p=linwizard-kernel.git;a=shortlog;h=refs/heads/GSM-CSMI |
| 13:19.28 | dcordes_ | ali1234: you don't get a tty device? what else do you get? |
| 13:26.47 | ali1234 | dcordes_: it's not that you don't get a tty, it's that you get something that isn't a tty :) |
| 13:27.28 | ali1234 | dcordes_: that is, you get a character device that isn't a tty, and so cannot be read and written at the same time |
| 13:27.47 | dcordes_ | I see |
| 13:30.57 | *** join/#htc-linux ClashTheBunny_ (i=c72ec6e7@gateway/web/ajax/mibbit.com/x-a6fa3d5466419e0e) |
| 13:31.24 | opennandra | ali1234: what about driver for 2.4 kernel? |
| 13:32.19 | *** join/#htc-linux ClashTheBunny (i=c72ec6e7@gateway/web/ajax/mibbit.com/x-888d7bc5c245c976) |
| 13:40.14 | opennandra | ali1234: isn't this driver for 2.4 ? http://git.lurian.net/?p=linwizard-kernel.git;a=commit;h=bfc0056a8f218135f643a0d59343d9e38577d285 |
| 13:41.00 | ali1234 | yes that's it |
| 13:41.20 | ali1234 | it doesn't work yet though |
| 13:41.48 | opennandra | ali1234: understand |
| 13:41.55 | opennandra | is something working? |
| 13:42.08 | ali1234 | no |
| 13:42.54 | opennandra | ali1234: ok som on any HTC isn't gsm working yet? |
| 13:43.17 | *** join/#htc-linux Guest55673 (n=root@87.72.13.87) |
| 13:43.18 | ali1234 | yes it works on the really old ones |
| 13:44.34 | opennandra | ali1234: and whats wrong with vivien gsm module for typhoon? Can't be adapted to 850? |
| 13:44.54 | ali1234 | it already has been |
| 13:45.11 | ali1234 | it doesn't work with any software package for reasons i stated above |
| 13:45.26 | ali1234 | it didn't work properly on typhoon either |
| 13:45.42 | ali1234 | it is experimental code and not usable for anything else |
| 13:45.47 | opennandra | ok |
| 13:45.53 | opennandra | so what could be solution? |
| 13:46.00 | ali1234 | port the TI 2.4 driver |
| 13:46.14 | opennandra | just for clarification |
| 13:46.21 | opennandra | omap 850 has on Soc gsm modem |
| 13:46.26 | opennandra | right? |
| 13:46.28 | ali1234 | right |
| 13:46.45 | opennandra | ok I see to typhoon code and it load some fw |
| 13:46.45 | ali1234 | and it is mostly compatible with omap730 |
| 13:47.07 | opennandra | it's necessary also for 2.4 driver? |
| 13:47.13 | ali1234 | yes |
| 13:47.33 | opennandra | and from where I can get fw? |
| 13:47.39 | opennandra | dump memory in wince? |
| 13:48.26 | ali1234 | the driver is two parts on wizard. one part can be extracted from rom, the other can be dumped from memory |
| 13:48.44 | ali1234 | i wrote a post about how to dump it on wizard dev mailing list |
| 13:49.04 | opennandra | ok thx |
| 13:49.20 | opennandra | I'll look on this ported code and try to understand it |
| 13:49.31 | *** join/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 13:49.38 | asj_xda | hi |
| 13:49.56 | ali1234 | opennandra: http://sourceforge.net/mailarchive/forum.php?thread_name=3d374d00808101440y3f6b9b1bq414513b0c2a6e5a5%40mail.gmail.com&forum_name=linwizard-devel |
| 13:50.36 | ali1234 | opennandra: pdocread.exe is a windows / wince tool, part of itsutils |
| 13:50.46 | opennandra | ok |
| 13:51.37 | ali1234 | devmem3 is a linux tool that i made based on devmem2. i guess you could dump the same memory in wince if you prefer. |
| 13:52.14 | ali1234 | also note addresses may be different for your device |
| 13:53.20 | opennandra | ok how can get correct addresses? |
| 13:54.31 | ali1234 | opennandra: when you boot with haret the fw stays loaded in memory. dump memory through strings/grep and look for the things like "GSM" which appear many times in the firmware |
| 13:55.10 | opennandra | :) smart |
| 13:55.17 | ali1234 | opennandra: compare the wizard and typhoon drivers, you'll see that although the base address moves, the offsets stay the same |
| 13:55.31 | opennandra | ok |
| 13:55.32 | ali1234 | opennandra: so basically you can figure out the rest by guessing |
| 13:55.40 | opennandra | ok |
| 13:55.43 | opennandra | ali1234 |
| 13:55.51 | opennandra | I register new mach-type in arm site |
| 13:56.06 | opennandra | <PROTECTED> |
| 13:56.20 | opennandra | can I do this for my devbranch? |
| 13:56.29 | ali1234 | i don't know about that |
| 13:56.43 | opennandra | ok |
| 13:56.54 | ali1234 | i think all omap850s fall into same machine type? |
| 13:59.04 | opennandra | yes but I register htc oxygen |
| 13:59.09 | opennandra | same line htc wizard |
| 13:59.12 | opennandra | like |
| 14:00.20 | ali1234 | i thought machine type was like omap1 omap2 etc |
| 14:00.28 | ali1234 | omap850 being omap1 |
| 14:01.17 | *** join/#htc-linux ClashTheBunny_ (i=c72ec6e7@gateway/web/ajax/mibbit.com/x-ef17ca91f86e62ed) |
| 14:01.47 | dcordes_ | NetRipper: does the htc-msm-2.6.27 kernel built with htcraphael_defconfig work with all the 4 machines? |
| 14:07.32 | *** join/#htc-linux balsat (n=balsat@87.72.13.87) |
| 14:08.23 | opennandra | ali1234: I'll check but for board MACHINE_START code I'll next unique one |
| 14:09.34 | asj_xda | dcordes: Hi, I've seen on the phorum, that I am not the only one with the "lines on display" issue, did you get any Idea on how to find out what is the difference to other Kaisers? |
| 14:10.05 | dcordes | asj_xda: got a link? no |
| 14:10.37 | asj_xda | dcordes: What link? |
| 14:11.08 | dcordes | link to I've seen on the phorum |
| 14:12.01 | asj_xda | dcordes: http://forum.xda-developers.com/showpost.php?p=3302998&postcount=2993 |
| 14:26.49 | *** join/#htc-linux timebomb (n=tb@85.183.25.191) |
| 14:28.21 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 14:28.28 | *** part/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 14:42.02 | opennandra | ali1234: modem is connected to chip via spi? |
| 14:47.15 | NetRipper | dcordes, yes, i try to keep everything i put in git work with all 4 machines |
| 14:47.35 | NetRipper | it's not android-ready yet though |
| 14:48.33 | NetRipper | dcordes, obviously diamond stuff is missing hardware keyboard etc, so stuff like that is removed from those machs |
| 15:00.00 | *** join/#htc-linux MethoS (n=lem@host-091-096-211-061.ewe-ip-backbone.de) |
| 15:21.16 | *** part/#htc-linux exco (n=exco@e181120013.adsl.alicedsl.de) |
| 15:21.55 | mickeyl | hi folks |
| 15:21.59 | mickeyl | how's work progressing? |
| 15:22.42 | *** join/#htc-linux MethoS (n=lem@host-091-096-211-061.ewe-ip-backbone.de) |
| 15:22.44 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-9a755674cde47b8c) |
| 15:24.23 | *** part/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 15:40.07 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
| 16:00.56 | xutywx | is anybody bored here? :P who can write drivers for touchscreen for toshiba g900 ? ;P |
| 16:01.49 | tmzt | xutywx: is your framebuffer working now? |
| 16:01.56 | xutywx | yes ;) |
| 16:02.10 | tmzt | you want to trace gpios with haret |
| 16:02.11 | xutywx | android and angstrom are booting ;) |
| 16:02.42 | xutywx | gauy named tuba is working on it but nowadays he doesnt have time |
| 16:03.08 | xutywx | http://www.youtube.com/watch?v=m4nlTKFI9aU |
| 16:03.10 | xutywx | look |
| 16:04.38 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-57d2c2ba12d819b6) |
| 16:12.24 | *** join/#htc-linux orux (n=jose@89.130.46.3) |
| 16:16.47 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
| 16:24.56 | AstainHellbring | morning |
| 16:33.35 | *** join/#htc-linux cr2 (n=cr2@ip-77-25-94-169.web.vodafone.de) |
| 16:34.01 | cr2 | hi |
| 16:34.08 | AstainHellbring | hi cr2 |
| 16:34.13 | cr2 | tmzt: i've looked at the g1 3d |
| 16:35.10 | cr2 | hi AstainHellbring |
| 16:35.29 | tmzt | cr2: hi |
| 16:36.22 | AstainHellbring | whats new cr2? |
| 16:36.44 | dcordes | mickeyl: hi. which work? |
| 16:36.56 | *** join/#htc-linux Dunedan (n=dunedan@phoenitydawn.de) |
| 16:37.05 | mickeyl | getting linux on any of your devices to a state where userland guys can pick up |
| 16:37.54 | dcordes | depends on what that state is |
| 16:38.15 | orux | Hello all. An interesting doc about msm6280 chipset; explaining its architecture, mddi, mdp and other things: http://www.megaupload.com/?d=B83EKN1T |
| 16:38.22 | *** join/#htc-linux drasar (n=maik@213.192.21.13) |
| 16:38.26 | mickeyl | well, you know... concentrating on getting work done, which requires hardware being supported |
| 16:38.43 | dcordes | mickeyl: many people are having fun with android on the msm7200 devices |
| 16:38.55 | mickeyl | no, i meant Linux |
| 16:38.56 | mickeyl | :D |
| 16:39.57 | dcordes | maybe the userspace developers should decrease their demands |
| 16:40.14 | dcordes | then people could have fun with openmoko on these devices too |
| 16:41.11 | tmzt | which devices is smd not working on? |
| 16:41.18 | tmzt | only raph800? |
| 16:41.30 | dcordes | none me think |
| 16:41.47 | tmzt | only ppp doesn't work on raph800 |
| 16:41.50 | tmzt | at works? |
| 16:43.39 | dcordes | R/W Access to /dev/smd1 (For PPP) NO All . |
| 16:44.02 | mickeyl | heh |
| 16:44.15 | mickeyl | well, any sane connectivity is not a too high demand iMO |
| 16:44.23 | *** join/#htc-linux metter (n=metter@97.102.202.62.cust.bluewin.ch) |
| 16:44.26 | mickeyl | at the end of the day, it's just that |
| 16:44.56 | cr2 | dcordes: why is that ? |
| 16:44.57 | dcordes | maybe dzo can have a look at the non-A usb |
| 16:45.21 | cr2 | mickeyl: what functions do you expect ? |
| 16:45.30 | dcordes | cr2: I have no clue it is from the wiki. are the addresses for smd hardcoded in the g1 tree? |
| 16:46.08 | cr2 | dcordes: i thought that the problem is that the /dev node is not created for DATA1 |
| 16:46.29 | cr2 | dcordes: the layout is the same as on g1, and the 7201A code works |
| 16:46.44 | mickeyl | cr2: usbeth or wifi |
| 16:47.08 | dcordes | mickeyl: on the newer devices you have the usb working |
| 16:47.10 | cr2 | mickeyl: firmware loader needs to be ported for wifi |
| 16:47.24 | mickeyl | newer means which model? |
| 16:47.30 | dcordes | mickeyl: all of the new htc models |
| 16:47.38 | tmzt | cr2: it is? does maejrep just need to add the registration to the kernel? or you mean just create the special file? I think we tried that and it didn't work |
| 16:47.39 | cr2 | mickeyl: the cdc_ether is working on 7x0xA |
| 16:48.14 | dcordes | mickeyl: raphael (touch pro), diamond, blackstone (touch hd) ... |
| 16:48.25 | cr2 | tmzt: i thought that the numbers were hardcoded, while you should go through the list picking the names |
| 16:48.28 | dcordes | mickeyl: SE xperia x1 |
| 16:48.39 | mickeyl | d'oh! |
| 16:48.46 | mickeyl | got linux on xperia yet? |
| 16:48.51 | dcordes | yes |
| 16:48.53 | mickeyl | that'd be interesting, i love the formfactor |
| 16:49.00 | tmzt | cr2: something like that, but maejrep didn't add the call in the kernel to register smd1 expecting it to be detected |
| 16:49.02 | mickeyl | GSM as well? |
| 16:49.12 | mickeyl | [or is it the same as on the others] |
| 16:49.30 | dcordes | mickeyl: I didn't test any radio spec things on my xperia yet |
| 16:49.40 | cr2 | tmzt: it's not nice, but may be done quick and dirty |
| 16:49.45 | mickeyl | i see. please keep me posted. that would be interesting |
| 16:50.10 | cr2 | dcordes: what amss id do you have ? |
| 16:50.59 | dcordes | cr2: my bootsplash doesn't tell |
| 16:51.02 | dcordes | mickeyl: ok |
| 16:53.13 | mickeyl | touch hd has no keyboard? |
| 16:53.18 | dcordes | correct |
| 16:53.19 | mickeyl | needs one with keyboard |
| 16:53.27 | mickeyl | ok, so touch pro would be the recommended |
| 16:53.29 | mickeyl | (for me) |
| 16:53.35 | tmzt | or x1 |
| 16:53.56 | mickeyl | how do these two compare? any critical things where one is better? |
| 16:54.02 | AstainHellbring | or the HD Pro that is still to be released |
| 16:54.05 | mickeyl | (for linux) |
| 16:54.29 | dcordes | mickeyl: x1 has some manufacturing problem where the plastic of the housing is bad and breaks easily. |
| 16:54.33 | tmzt | mickeyl: I mean x1 also has keyboard |
| 16:54.59 | mickeyl | tmzt: right |
| 16:55.02 | *** join/#htc-linux imfloflo_ (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 16:55.03 | mickeyl | dcordes: ooh |
| 16:55.05 | dcordes | mickeyl: x1 has 480x800 display, touch pro has vga |
| 16:55.17 | *** join/#htc-linux imfloflo_ (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 16:55.26 | dcordes | touch pro keyboard is more powerful |
| 16:55.32 | mickeyl | ok |
| 16:55.37 | tmzt | other than that there is g1/adp1 which is the google phone but could be flashed with a different filesystem, it has a slide up and out screen and a five-line keyboard |
| 16:55.37 | mickeyl | thanks |
| 16:55.39 | cr2 | dcordes: vga on a 2.8" is an overkill. |
| 16:55.59 | cr2 | g1 has half-vga |
| 16:56.10 | dcordes | no |
| 16:56.12 | tmzt | yeah, just thought of that |
| 16:56.18 | dcordes | does it?? |
| 16:56.23 | mickeyl | tmzt: i didn't hear much wrt. any developer-g1 success stories. i wonder whether any would be interested in really freeing 'em |
| 16:56.48 | dcordes | mickeyl: stefan schmidt mentioned something |
| 16:56.59 | tmzt | the only one who expressed interest in debian is wasabi, haven't heard much about it though |
| 16:57.03 | cr2 | mickeyl: it's a bit more free than the greenphone |
| 16:57.13 | mickeyl | cr2: a bit? :) |
| 16:57.21 | cr2 | because the bt/wifi drivers are gpl |
| 16:57.22 | tmzt | they are using debian in a chroot now but still using zygote/surfaceflinger for graphics |
| 16:57.23 | dcordes | g1 has 320x480 |
| 16:57.24 | mickeyl | ah |
| 16:57.45 | cr2 | the gsm/camera/3d is closed source |
| 16:57.54 | mickeyl | i don't see the glofiish progressing, so i htc-linux looks like the best bet for another free device |
| 16:58.07 | tmzt | also, X on there without the video display hack is difficult (same as other msm), I'm hoping dri/drm could be adapted to handle flipping,etc. but I don't know |
| 16:58.21 | dcordes | mickeyl: laforge still got problems with the radio? |
| 16:58.23 | tmzt | otherwise we only have the msmfb and it's ioctls |
| 16:58.30 | cr2 | 3d is a software implementation of AHI+mesa with some hw support ;) |
| 16:58.41 | mickeyl | dcordes: yes, and i'm afraid he had 0 time to further investigate this |
| 16:58.47 | tmzt | and hw3d on A devices but we don't know how to use that without libhgl which is the closed gles library |
| 16:59.03 | dcordes | mickeyl: maybe other people will pick it up |
| 16:59.23 | mickeyl | dcordes: my hope as well, but experience tells it doesn't look good. |
| 16:59.23 | cr2 | tmzt: i'd be happy with the raw framebuffer |
| 16:59.27 | tmzt | cr2: google also has libagl which is their mesa-like gl es implementation, it uses libhgl when available |
| 16:59.45 | tmzt | cr2: yes, if we could force it to dma without a kernel thread running |
| 16:59.45 | *** part/#htc-linux [Abra_London] (n=aaabraca@unaffiliated/abracadabra) |
| 17:00.01 | mickeyl | ok, let me get some quotes for a htc pro |
| 17:00.08 | mickeyl | googling for prices |
| 17:00.14 | dcordes | mickeyl: maybe somebody wants android on it :) |
| 17:00.25 | mickeyl | *shudder* yeah |
| 17:00.25 | cr2 | tmzt: the real progress will be to write a 2D accelerated fb driver, but it's a lot of work i guess |
| 17:01.15 | cr2 | tmzt: clocks and lcd panel init first ;) |
| 17:01.16 | dcordes | updates linux-msm7xxxx_git.bb |
| 17:02.58 | cr2 | hehe, recompiling firefox3.06 |
| 17:03.15 | mickeyl | what's the state of support for -- lets say the touch pro -- in OE? |
| 17:03.17 | cr2 | gcc-4.1.0 crashed on it |
| 17:03.21 | mickeyl | much to add or ready-to-go? |
| 17:03.43 | cr2 | mickeyl: OE ? |
| 17:03.55 | drasar | Hi cr2. How far are you with my Himalaya patch commiting? |
| 17:03.57 | mickeyl | OpenEmbedded, which is my favoured built environment |
| 17:04.04 | mickeyl | s/built/build/ |
| 17:04.15 | cr2 | drasar: i think you've told me pH5 committed it ? |
| 17:04.29 | tmzt | it's armv6novfp, dcordes you have it building right? |
| 17:04.35 | cr2 | mickeyl: yes i know, but what do you want to build ? |
| 17:05.07 | drasar | cr2: Yes, but only into linuxtogo GIT |
| 17:05.08 | cr2 | mickeyl: i use the nagrstom console image |
| 17:05.29 | cr2 | drasar: ok. post the patch somewhere |
| 17:05.38 | mickeyl | cr2: well ideally, i want X and the freesmartphone.org framework |
| 17:05.56 | cr2 | mickeyl: i don't think somebody done it yet |
| 17:06.05 | dcordes | mickeyl: it's htcraphael in OE. I'm updating the kernel now. afaik X works well. in the fso images you can ring out using frameworkd. |
| 17:06.09 | drasar | cr2: pH5 hasn't commit right for handhelds CVS |
| 17:06.15 | mickeyl | dcordes: that's amazing! |
| 17:06.17 | mickeyl | i guess i'm sold |
| 17:06.38 | cr2 | :) |
| 17:06.44 | cr2 | drasar: ok |
| 17:06.52 | tmzt | dcordes: what's the patch for kernel for X to work? the one without vkeyb |
| 17:06.56 | *** part/#htc-linux orux (n=jose@89.130.46.3) |
| 17:07.12 | dcordes | tmzt: you mean on kaiser? |
| 17:07.23 | tmzt | it's the same on all of them? |
| 17:07.24 | drasar | cr2: You can find that patch at http://www.handhelds.org/hypermail/kernel-bugs/current/0238.html |
| 17:07.46 | dcordes | tmzt: no. on the A-devices you obviously need no hackery. X works ootb |
| 17:08.03 | dcordes | lupine_85: am I right? |
| 17:08.12 | cr2 | drasar: ok |
| 17:08.44 | mickeyl | EUR 499,99 |
| 17:08.47 | cr2 | dcordes: the sane mddi refresh is hackery |
| 17:08.48 | mickeyl | that's not too bad |
| 17:09.18 | dcordes | cr2: what's sane mddi refresh? the normal (g1 based) code? |
| 17:09.49 | cr2 | dcordes: hardware refresh without a kernel thread |
| 17:10.23 | *** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl) |
| 17:10.40 | cr2 | g1 is not sane because it uses a closed source hw3d lib ;) |
| 17:17.32 | dcordes | mickeyl: what I said about raphael in OE virtually applies to xperia too |
| 17:18.06 | cr2 | dcordes: it's 98% about kernel drivers |
| 17:18.59 | mickeyl | dcordes: interesting. that really sounds like we will see a bunch of freed devices mid-term |
| 17:19.02 | dcordes | I know. mickeyl asked about OE though |
| 17:20.22 | tmzt | Makefile |
| 17:20.23 | lupine_85 | dcordes: it needed the VDH |
| 17:20.41 | dcordes | lupine_85: what's that? |
| 17:20.51 | tmzt | lupine_85: is there a version without the vkeyb? |
| 17:20.57 | lupine_85 | some sort of pollying thing that updated the screen a lot |
| 17:21.14 | lupine_85 | there's a patch to replace it in htc-msm-2.6.27 but I've not even compiled that branch |
| 17:21.40 | dcordes | so X should work ootb in htc-msm-2.6.27 ? I can try on xperia |
| 17:22.15 | cr2 | dcordes: X = Xfbserver ? |
| 17:22.25 | tmzt | lupine_85: the patch is still a kernel thread though? just not tsts anymore? |
| 17:22.32 | dcordes | cr2: Xfbdev |
| 17:22.39 | cr2 | ok |
| 17:29.44 | dcordes | what kernel version is htc-vogue at? |
| 17:31.54 | tmzt | dcordes: Makefile |
| 17:39.02 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 17:40.45 | *** join/#htc-linux acsviluppo (n=acsvilup@94.163.153.90) |
| 17:41.29 | *** join/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 17:44.12 | *** join/#htc-linux MaRx88 (n=IceChat7@chello089077138234.chello.pl) |
| 17:46.55 | *** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) |
| 17:52.38 | *** join/#htc-linux ALoGeNoff (n=alogeno@231.pool85-60-63.dynamic.orange.es) |
| 18:16.01 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
| 18:23.08 | dcordes | I think board-htcraphael-navi should be a configurable driver and not be hardcoded in arch/arm/mach-msm/Makefile |
| 18:23.25 | dcordes | and depend on the microp |
| 18:26.44 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87df92.pool.einsundeins.de) |
| 18:31.15 | *** part/#htc-linux asj_xda (n=asj@130.78.broadband3.iol.cz) |
| 18:46.38 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 18:59.07 | *** join/#htc-linux xutywx (n=pawel@195.205.38.95) |
| 19:12.43 | dcordes | somebody with cdma raph present? |
| 19:13.37 | AstainHellbring | has a cdma raph |
| 19:13.42 | AstainHellbring | the raph 800 to be exact |
| 19:13.45 | AstainHellbring | whatcha need? |
| 19:15.07 | dcordes | on the kovsky I get "msmfb_start_dma ~30ms after vsync request" printks. do you have them too? |
| 19:15.22 | AstainHellbring | kovsky? |
| 19:15.39 | dcordes | xperia |
| 19:16.11 | AstainHellbring | where do you get those? |
| 19:16.37 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089c53.pool.mediaWays.net) |
| 19:18.09 | dcordes | on the console |
| 19:18.13 | dcordes | you don't? |
| 19:18.34 | AstainHellbring | lemme grab the latest build for raph800 and try it again haven't launched on the 800 in a bit |
| 19:18.48 | dcordes | it's because time_since_request > 20 |
| 19:19.13 | dcordes | vsync_request_time |
| 19:21.10 | AstainHellbring | maejrep is there a new build with your latest work available anywhere? |
| 19:24.31 | dcordes | AstainHellbring: don't have the git locally? |
| 19:25.20 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
| 19:26.10 | AstainHellbring | oh yah |
| 19:26.30 | AstainHellbring | lemme boot up my eee where I have it stored |
| 19:26.35 | dcordes | ok |
| 19:26.53 | AstainHellbring | can you remind me the command to have git update? |
| 19:28.02 | dcordes | git-pull |
| 19:30.33 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) [NETSPLIT VICTIM] |
| 19:31.13 | *** join/#htc-linux AstainEEE (n=arto@unaffiliated/astainhellbring) |
| 19:31.53 | AstainEEE | ok got it updated |
| 19:33.51 | *** join/#htc-linux MaRx88 (n=IceChat7@chello089077138234.chello.pl) |
| 19:35.26 | AstainEEE | damn I gotta get my cross compiler installed to |
| 19:39.46 | lupine_85 | tmzt: think so, haven't looked at it |
| 19:45.57 | *** join/#htc-linux liba2k (n=liba2k@194.90.149.193) |
| 19:47.03 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 19:47.20 | xutywx | does anyone know how to get the touchscreen in g900 working? |
| 19:48.16 | tmzt | xutywx: hello again |
| 19:48.35 | xutywx | hi |
| 19:48.42 | tmzt | have you tried tracing gpios in haret? |
| 19:49.09 | xutywx | no - i hadnt got time |
| 19:49.22 | xutywx | so... what should i do? |
| 19:49.44 | xutywx | as m friend says it is ac97 controlled as i remember |
| 19:52.34 | tmzt | ah, so the touchscreen is in the ac97 codec? |
| 19:52.42 | tmzt | I think there are devices like that |
| 19:52.43 | xutywx | probably yes |
| 19:52.53 | xutywx | ? |
| 19:53.22 | *** join/#htc-linux exco (n=exco@e181120013.adsl.alicedsl.de) |
| 19:54.06 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
| 19:57.19 | *** join/#htc-linux TL|Jermu (n=no@a91-156-151-141.elisa-laajakaista.fi) |
| 19:59.00 | xutywx | i have <*> Support for WM97xx AC97 touchscreen controllers |
| 19:59.00 | xutywx | [*] WM9713 Touchscreen interface support |
| 19:59.01 | xutywx | <*> Philips UCB1400 touchscreen compiled in but it doesnt work ;/ |
| 19:59.17 | xutywx | maybe i should add some devices in /dev or sth? |
| 20:00.19 | tmzt | try that, but you will need to add a platform_device to your board file |
| 20:00.27 | tmzt | I think |
| 20:00.59 | tmzt | do you know it's a wm9713 chip? |
| 20:01.09 | tmzt | and I think ucb is not ac97 |
| 20:01.11 | xutywx | no - it;s a guess |
| 20:01.32 | xutywx | platform_device ? what's that? |
| 20:02.49 | tmzt | just a struct in your .c file, you also add it to the list of devices that get registered |
| 20:05.20 | xutywx | a have it already |
| 20:05.44 | xutywx | http://goandroid.net/kernel.tar.gz |
| 20:05.53 | xutywx | these are files that i use |
| 20:07.14 | tmzt | can you paste just the files in mach-pxa that you use |
| 20:07.17 | tmzt | that's 60mb |
| 20:07.38 | xutywx | ok moment |
| 20:07.50 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 20:07.51 | tmzt | not Makefile Kconfig |
| 20:08.49 | *** join/#htc-linux Sundial (n=jmissao@unaffiliated/sundial) |
| 20:10.29 | xutywx | only files with g900 in name - probably all pid.pl/paczka.rar |
| 20:11.31 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
| 20:14.54 | tmzt | static struct platform_device g900_gpio_keys = { |
| 20:14.54 | tmzt | <PROTECTED> |
| 20:15.19 | tmzt | make one of those with .name = "wm9713" |
| 20:16.10 | tmzt | sorry, we need something else first |
| 20:16.14 | tmzt | since this is a codec |
| 20:19.34 | tmzt | try .name = wm97xx-ts |
| 20:20.58 | xutywx | .dev = { .... can i delete it? |
| 20:21.21 | tmzt | copy that g900_gpio_keys, make it g900_touchscreen |
| 20:21.28 | tmzt | this doesn't replace the other struct |
| 20:21.37 | tmzt | but yes, leave out .dev for right now |
| 20:21.56 | xutywx | .id = -1 is ok? |
| 20:22.14 | tmzt | leave that out too |
| 20:22.23 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
| 20:22.42 | xutywx | static struct platform_device *g900_devices[] __initdata = { in that i should add &g900_touchscreen, ? |
| 20:23.01 | tmzt | no, in the .c file not in that struct |
| 20:23.13 | tmzt | yes |
| 20:23.15 | tmzt | sorry |
| 20:23.23 | xutywx | ok ;) what next? |
| 20:23.28 | tmzt | try that |
| 20:23.34 | xutywx | ok ;) |
| 20:23.34 | *** join/#htc-linux Sti_0231 (n=Where_is@56.211-65-87.adsl-dyn.isp.belgacom.be) |
| 20:23.46 | tmzt | I don't see anything using wm7xxx-ts, still looking |
| 20:24.20 | tmzt | we need to find the irq for this though |
| 20:25.25 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-111-187.web.vodafone.de) |
| 20:25.49 | tmzt | cr2: are you familiar with wm97xx touchscreens? |
| 20:26.23 | cr2 | wm97 ? |
| 20:26.32 | tmzt | yeah |
| 20:26.32 | cr2 | on which device ? |
| 20:26.45 | tmzt | on g900, but I mean do you know any other device using it |
| 20:27.03 | cr2 | older palms ? |
| 20:27.23 | cr2 | are you sure it's wm97 ? |
| 20:27.47 | tmzt | no, xutywx says someone thinks its ac97 though |
| 20:28.08 | tmzt | < xutywx> as m friend says it is ac97 controlled as i remember |
| 20:29.06 | tmzt | interesting, this could help with diam http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-01/msg06122.htm |
| 20:29.28 | tmzt | if we keep ts calibration in kernel |
| 20:30.46 | cr2 | only #ifdef android |
| 20:33.07 | cr2 | tmzt: if a rom is available, it should be dissected. otherwise run testwm5 |
| 20:33.40 | cr2 | i'll check |
| 20:35.48 | cr2 | has i2c inside |
| 20:36.22 | tmzt | em-x720 has wm97xx-ts if we need it |
| 20:36.30 | cr2 | btw, i forgot my power supply at work. will disconnect in ~2h ? |
| 20:37.28 | cr2 | i have a gpio dump here |
| 20:37.40 | cr2 | is it in hh.org wiki ? |
| 20:37.52 | tmzt | of? |
| 20:37.56 | cr2 | g900 |
| 20:38.43 | cr2 | x01t too ? |
| 20:39.40 | cr2 | uh. it has mdoc ? |
| 20:40.08 | cr2 | hehe. with protection key |
| 20:41.17 | cr2 | TechFaith Wireless(BJ) |
| 20:41.23 | cr2 | wtf is that ? |
| 20:44.13 | *** join/#htc-linux MaRx88 (n=IceChat7@chello089077138234.chello.pl) |
| 20:45.17 | *** join/#htc-linux opennandra (n=opennand@afrodita.advanet.sk) |
| 20:53.04 | xutywx | it does not work ;/ battery deplated so ill be back tomorrow |
| 20:53.11 | xutywx | thx and bye ;) |
| 20:53.47 | xutywx | it boots but angstrom doesnt recognizes it |
| 21:14.15 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 21:15.40 | *** join/#htc-linux acsviluppo (n=acsvilup@94.163.179.103) |
| 21:16.42 | *** part/#htc-linux acsviluppo (n=acsvilup@94.163.179.103) |
| 21:17.20 | *** join/#htc-linux acsviluppo (n=acsvilup@94.163.179.103) |
| 21:28.25 | *** join/#htc-linux MethoS (n=lem@host-091-097-240-133.ewe-ip-backbone.de) |
| 21:29.29 | *** join/#htc-linux MethoS (n=lem@host-091-097-240-133.ewe-ip-backbone.de) |
| 21:32.40 | *** join/#htc-linux MethoS (n=lem@host-091-097-240-133.ewe-ip-backbone.de) |
| 21:34.24 | *** join/#htc-linux mr (n=user@dslb-088-073-213-102.pools.arcor-ip.net) |
| 21:44.20 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 21:45.34 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 21:46.28 | *** join/#htc-linux cr2_ (n=cr2@ip-77-24-71-62.web.vodafone.de) |
| 21:47.39 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 21:50.35 | Guest91721 | hello, maybe some can help me or give me a hint I'm trying to boot android on my thc touch diamond and after the pin promt it it fades grey or freezes, I have no chance to open any menu or so |
| 21:52.21 | *** join/#htc-linux timebomb (n=tb@e176120011.adsl.alicedsl.de) |
| 21:53.19 | tmzt | maejrep: are you here? |
| 21:59.54 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbffad0.pool.einsundeins.de) |
| 22:15.48 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 22:23.58 | *** join/#htc-linux ljp (n=lpotter@218.185.108.156) |
| 22:32.03 | *** join/#htc-linux Heema (n=heema@217.139.239.165) |
| 22:32.33 | konsta | Guest91721: the hint you request can be found by reading the forum thread which told you about this channel. The question has been answered there maybe forty or fifty times, and the answer is to read the FAQ section of the Wiki. |
| 22:32.54 | *** join/#htc-linux MethoS (n=lem@host-091-097-240-133.ewe-ip-backbone.de) |
| 22:33.55 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 22:38.15 | *** join/#htc-linux Heema (n=Heema@217.139.239.165) |
| 22:40.53 | Guest91721 | I have read the wiki solution, but my problem is to get into any menu to setup the timeout settings |
| 22:44.49 | *** join/#htc-linux ClashTheBunny (i=60ed211a@gateway/web/ajax/mibbit.com/x-8c1aed1a229bb5c3) |
| 22:47.27 | *** join/#htc-linux Heema (n=Heema@217.139.239.165) |
| 22:48.27 | *** join/#htc-linux acsviluppo (n=acsvilup@151.67.29.135) |
| 22:49.27 | *** part/#htc-linux Heema (n=Heema@217.139.239.165) |
| 22:50.42 | *** join/#htc-linux MethoS (n=lem@host-091-097-240-133.ewe-ip-backbone.de) |
| 22:56.23 | *** join/#htc-linux Heema (n=Heema@217.139.239.165) |
| 22:56.35 | *** join/#htc-linux ClashTheBunny (i=60ed211a@gateway/web/ajax/mibbit.com/x-af603f36fa43375f) |
| 22:56.48 | *** part/#htc-linux Heema (n=Heema@217.139.239.165) |
| 23:00.34 | Guest91721 | another thing is, if I move the keyboard, the background does not refresh and I see the traces of the move |
| 23:01.31 | tmzt | Guest91721: do you have a cdma or gsm diamond? |
| 23:03.13 | Guest91721 | I guess a GSM it's a O2 germany one |
| 23:03.41 | tmzt | interesting |
| 23:03.55 | tmzt | what keyboard, the green one? |
| 23:04.42 | cr2_ | tmzt: devioctl -> ptr,8,0,0,7,0x48 |
| 23:05.00 | tmzt | cr2_: sorry? |
| 23:05.21 | cr2_ | hmm |
| 23:05.53 | Guest91721 | after booting, I have a blue rectangle and a click on it and it gets green, yes |
| 23:06.39 | Guest91721 | sorry im realy new in this topic where can I see the ptr ? in the default.txt ? |
| 23:06.59 | cr2_ | ptr,0x220800,...,8,7 |
| 23:07.18 | cr2_ | 0x48 should be the i2c id |
| 23:07.40 | cr2_ | or 0x48>>1 |
| 23:07.50 | cr2_ | which touchscreen is that ? |
| 23:08.19 | cr2_ | i think it'd be easy to mmutrace the 1688 i2c data reg, and touch the screen. |
| 23:10.52 | *** join/#htc-linux Heema (n=Heema@217.139.239.165) |
| 23:11.02 | Guest91721 | how can I figure out the touch screen sorry ^^, maybe it helbs that model is a DIAM300 |
| 23:13.19 | *** join/#htc-linux cmonex (n=xy6091@i8p6w63khs.adsl.datanet.hu) |
| 23:28.50 | Guest91721 | if taken some photos of that issue, you can take a look on http://gipx.net/rsrc/android/ |
| 23:30.06 | tmzt | cr2_: that was to Guest91721 then? |
| 23:30.14 | Guest91721 | yes |
| 23:32.21 | cr2_ | tmzt: no, g900 |
| 23:38.32 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 23:39.53 | tmzt | oh, right |
| 23:40.03 | *** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
| 23:40.13 | tmzt | so its not ac97 then? |
| 23:40.17 | tmzt | i2c |
| 23:43.25 | miknix | hello BabelO |
| 23:49.05 | *** join/#htc-linux exco (n=exco@e181065103.adsl.alicedsl.de) |
| 23:53.01 | *** join/#htc-linux MaRx88_ (n=IceChat7@chello089077138234.chello.pl) |