00:10.45 | Kevin2 | Hi |
00:21.40 | lkcl_ | hiya Kevin2 |
00:23.18 | Kevin2 | lkcl_: Hi. |
00:23.45 | Kevin2 | You ever get a chance to try the new haret on hermes? It looks like cr2 got a chance to try it out. |
00:24.14 | lkcl_ | new haret? no. still using the old one. |
01:15.54 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
01:50.53 | *** join/#htc-linux jgw_ (n=jgw@c-24-22-48-124.hsd1.or.comcast.net) |
01:52.02 | lkcl | ok i'm getting a small click in the speaker when i play sound. |
01:52.14 | lkcl | like someone applied DC current across it. |
01:52.16 | lkcl | on the blueangel. |
01:54.52 | *** part/#htc-linux jgw_ (n=jgw@c-24-22-48-124.hsd1.or.comcast.net) |
03:16.16 | *** join/#htc-linux Ralith (n=ralith@soggy202.drizzle.com) |
03:19.47 | *** join/#htc-linux rejon (n=rejon@c-67-174-202-239.hsd1.ca.comcast.net) |
03:20.51 | *** part/#htc-linux rejon (n=rejon@c-67-174-202-239.hsd1.ca.comcast.net) |
03:21.31 | *** join/#htc-linux psokolovsky_ (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com) |
05:25.56 | *** join/#htc-linux bd2 (n=ufo@89.113.84.151) |
06:11.22 | *** join/#htc-linux JTRipper_ (n=jtripper@p54B1D2D1.dip.t-dialin.net) |
07:01.29 | *** join/#htc-linux ellisway (n=ellis@host-87-74-241-174.bulldogdsl.com) |
07:10.04 | *** join/#htc-linux rob_w (n=rob_w@p549B97A1.dip0.t-ipconnect.de) |
07:14.52 | *** join/#htc-linux LunohoD_ (n=alex@e180115204.adsl.alicedsl.de) |
07:30.58 | *** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
07:31.29 | *** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
07:57.25 | *** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
08:06.16 | *** join/#htc-linux Fossi (n=cmewes@195.177.48.115) |
08:49.14 | *** join/#htc-linux RoEn_PC (n=roen@p54A64F77.dip.t-dialin.net) |
09:14.18 | *** join/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com) |
09:19.01 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
09:33.48 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
09:48.39 | *** join/#htc-linux booba (n=booba@AAnnecy-256-1-5-119.w90-10.abo.wanadoo.fr) |
10:02.08 | *** join/#htc-linux gw280_ (i=authdeni@vm.gwright.org.uk) |
10:35.01 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
10:42.20 | *** join/#htc-linux TripleDES (n=sergio@89.129.143.241) |
11:17.29 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
11:59.12 | *** join/#htc-linux goxboxlive (n=goxboxli@gw.hjelcowi.no) |
12:00.15 | goxboxlive | hi |
12:05.25 | *** join/#htc-linux WizMaui (n=WizMaui@62.112.90.231) |
12:22.50 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
12:29.41 | *** join/#htc-linux gw280 (i=authdeni@vm.gwright.org.uk) |
12:41.27 | *** join/#htc-linux Funklord (n=cow@c-cbd572d5.014-46-73746f28.cust.bredbandsbolaget.se) |
12:44.43 | *** join/#htc-linux gw280_ (n=george@vm.gwright.org.uk) |
12:53.39 | *** join/#htc-linux lkcl_work (n=c3a976e3@217.147.94.29) |
12:54.17 | lkcl_work | allo darlins |
12:56.05 | lkcl_work | i am still on blueangel sound, struggling with asoc, but i am making random wobbly progress |
12:56.24 | cr2 | hi lkcl |
12:56.35 | cr2 | have you done the i2c trace ? |
13:08.17 | *** join/#htc-linux pH5 (n=ph5@p5485DEF2.dip.t-dialin.net) |
13:16.43 | *** join/#htc-linux lkcl_work (n=c3a976e3@217.147.94.29) |
13:16.49 | *** join/#htc-linux lkcl_work (n=c3a976e3@217.147.94.29) |
13:17.50 | pH5 | lkcl, cr2, pof: what is the current state of the hermes? |
13:20.30 | *** join/#htc-linux apt (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
13:20.30 | *** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux |
13:20.32 | Kevin2 | Hi |
13:20.35 | cr2 | the gpio/watch gpio is of course broken |
13:20.49 | pH5 | hi babeloued, Kevin2 |
13:21.11 | babeloued | hi pH5 |
13:21.12 | cr2 | the machine name is not registered so you get "Default" as a name. |
13:21.17 | cr2 | hi Kevin2 |
13:21.17 | pH5 | cr2: ok, so it's still in boot preparation phase? |
13:21.50 | babeloued | somebody use w100fb like on blueangel ? |
13:21.52 | cr2 | pH5: yes. i think it makes sense to do 'dump *' first :) |
13:22.21 | babeloued | cr2 : i ve same problem as universal on suspend :) |
13:22.27 | Kevin2 | cr2: Can you send the subsystem ids to me - I'll add the appropriate machine classes. |
13:23.01 | cr2 | pH5: do you know max1587 id on magician ? |
13:23.13 | cr2 | Kevin2: i'll have a look. |
13:23.32 | lkcl_work | allo pH5 |
13:23.57 | babeloued | cr2 i think there is something strange with apmd and apm command line |
13:24.03 | pH5 | hey lkcl |
13:24.07 | Kevin2 | Also, I've been investigating wi on Samsung processors. It is interesting that the 920t processor has a very similar debug interface to the one in the pxa (probably even more powerful). However, unlike the Intel it appears to only be accessible via JTAG port. |
13:24.10 | cr2 | lkcl_work: i have finally found the standalone RTC |
13:24.19 | pH5 | cr2: no, how do I get to it? watch pwr-i2c traffic during suspend/resume? |
13:24.34 | cr2 | babeloued: which resume problem on the universal ? |
13:24.35 | lkcl_work | cr2: pierrox sent me a new patch, against 2.6.19 (mainline) because 2.6.19-hh3 merge was a screw-up with lots of conflicts for him |
13:24.37 | pH5 | I couldn't anything there so far. |
13:24.40 | Kevin2 | pH5: Yes |
13:24.41 | Kevin2 | set trace 0xae301688 # I2C IDBR |
13:24.41 | Kevin2 | set trace2 0xaef00188 # I2C PIDBR |
13:24.41 | Kevin2 | wi 10 |
13:24.43 | cr2 | pH5: i have looked into nk.exe |
13:24.58 | lkcl_work | hooray! ... erm... for what hardware? :) |
13:25.25 | cr2 | lkcl_work: for universal. but it should be the same for sable. |
13:25.58 | lkcl_work | guys, remember: we need to do an update on every htc device to use the latest suspend/resume platform_device design |
13:25.59 | cr2 | Kevin2: i have problems watching the spi. |
13:26.11 | lkcl_work | until then we're going to have lots of problems with resume. |
13:26.21 | lkcl_work | cr2: great |
13:26.44 | lkcl_work | pH5: thanks for the sound tips. the SSP2 and SSP3 were completely uninitialised. |
13:26.54 | cr2 | there are no problems on universal when you don't use the broken char/sa1100-rtc driver. |
13:27.02 | babeloued | cr2 : goxboxlive say that opie does not suspend, on BA command line i have same problem, i need to press CTRL+C after apm -s command line |
13:27.13 | cr2 | lkcl_work: there are no ssp2/ssp3 on pxa263 |
13:27.22 | Kevin2 | I think it might be possible to get much of the wi functionality anyway. One should be able to pull out the pxa specific parts of the interrupt watching. The breakpoint stuff one can obtain by overwriting instructions with an "undefined instruction" and then catching the resulting fault. And finally, one may be able to get some memory tracing by playing with the MMU to prohibit accesses, then catching the result |
13:27.29 | cr2 | should i write the 'dump pxa26xssp' ? |
13:27.29 | lkcl_work | pH5: you wouldn't mind taking a look at this and filling in some notes, could you? http://wiki.xda-developers.com/index.php?pagename=BlueangelPXAdumps |
13:27.57 | babeloued | lkcl_work : do you have problem with latest w100fb driver ? |
13:28.01 | pH5 | cr2: decoding the control registers would be cool |
13:28.07 | pH5 | lkcl: ok , I'll look at it |
13:28.11 | cr2 | babeloued: it's opie problem, not the suspend itself. |
13:28.15 | lkcl_work | oh btw i might get a chance to borrow an h6340 for a few weeks, next year |
13:28.33 | lkcl_work | oh. cr2, you are lucky |
13:29.20 | Kevin2 | cr2: What problems do you have with spi? |
13:29.21 | lkcl_work | cr2: that would explain it :) |
13:29.31 | lkcl_work | babeloued: on blueangel? no, other than the screen goes blank due to apm switching it off and it doesn't come back on again |
13:29.42 | cr2 | Kevin2: there are 3 16bit regs: +200 (status) +202 (write) and +204 (read) |
13:30.08 | lkcl_work | on himalaya: yes, cos i don't know the registers, and the driver is now nice and 'proper' - none of this 'shove in some hexadecimal at a few memory locations' approach :0 |
13:30.18 | cr2 | Kevin2: whatever i set, i'm flooded and overrun by the fifo messages in (status) |
13:30.22 | babeloued | lkcl_work : i 've same with .19 kernel and since yesturday with latest w100fb driver, my BA does not boot |
13:30.50 | lkcl_work | ta pH5. the settings change when sound is being played. |
13:31.59 | Kevin2 | cr2: you should be able to watch +202 and +204. Make sure you have the mask disabled (set tracemask -1). If you're still having problems, send me the first few lines of wi output - It'll show how the debug registers are setup. |
13:32.01 | lkcl_work | babeloued: ohhh... yes, i did - when playing opie mediaplayer, it messed with the screen - but the mediaplayer had lots of memory trap violations in the kernel logs |
13:33.05 | lkcl_work | ahhh joy. who's made some mods? do a cvs diff -u -D '2 days ago' drivers/video and see who's been committing stuff. it was probably me by mistake ha ha |
13:33.17 | Kevin2 | cr2: Oops - use "set tracemask 0". |
13:33.23 | cr2 | Kevin2: ok, i'll look in my logs. |
13:34.02 | cr2 | Kevin2: ok. |
13:34.17 | babeloued | lkcl_work : yes lot of trap ! so for moment i use two days ago driver of w100fb. no isn t you. psolovsky say it work on hx4700 |
13:34.27 | pH5 | cr2: the pxa263 only has SSP(1)? ok, that explains why the SSP2/3 control register dumps look a bit strange :) |
13:34.48 | cr2 | lkcl_work: can you compare the ba and hima ssp setup ? |
13:35.18 | cr2 | pH5: it has NSSP (ts and backup battery), but it has a different address. |
13:37.18 | cr2 | Kevin2: i'll try tracing spi later today. btw, the 0x51 i2c chip that you have is an RTC. |
13:37.42 | cr2 | http://wiki.xda-developers.com/index.php?pagename=HTC_I2C_IDs |
13:39.24 | Kevin2 | cr2: BTW, another trick to reduce trace traffic is to use "set ignoreaddr 0xaddr1 0xaddr2 ..." |
13:39.25 | cr2 | ok. |
13:39.26 | Kevin2 | If you have an instruction address that constantly reads/writes to memory and you're not interested in it, you can ignore those instruction addresses. |
13:39.27 | Kevin2 | cr2: What is the RTC for? |
13:39.27 | cr2 | realtime clock. |
13:39.28 | cr2 | with its own battery, and i2c interface. |
13:39.28 | Kevin2 | Yeah, but what is it used by? |
13:39.29 | cr2 | to keep time :) |
13:39.29 | cr2 | date and time. |
13:40.13 | cr2 | wince just reads it at bootup and copies into pxa27x RTC. |
13:40.14 | Kevin2 | Hrmm. I think I see - it allows the pda to have time even if it can't contact the cell towers. |
13:40.34 | cr2 | and if the main/backup battery is dead. |
13:40.55 | cr2 | and cpu is completely shut down. |
13:41.16 | Kevin2 | Does the PXA RTC run when the processor is in suspend state? |
13:41.38 | cr2 | i don't know how linux deals with multiple RTCs. maybe an interesting question. |
13:41.41 | cr2 | of course. |
13:42.51 | Kevin2 | Is this the doc link: http://www.e-lab.de/downloads/DOCs/RTC8564.pdf |
13:43.22 | cr2 | yes. there is a linux driver. at least on my suse notebook. |
13:43.45 | cr2 | i'll commit it into CVS today. don't know why it's not in mainline. |
13:45.15 | Kevin2 | I'm off to work - bye. |
13:45.46 | cr2 | bye |
13:45.47 | lkcl_work | babeloued: extra params need to be added to cope with the three different devices which use that driver. you can see clearly that many parameters are hard-coded. |
13:46.18 | lkcl_work | cr2: later, yes. i am back to the uk tomorrow, packing etc. i will take all my devices with me, i promise :) |
13:46.28 | cr2 | lkcl_work: don't forget about the video capture |
13:46.35 | cr2 | lkcl_work: ok :) |
13:49.12 | babeloued | lkcl_work : ok. |
13:54.44 | *** part/#htc-linux goxboxlive (n=goxboxli@gw.hjelcowi.no) |
13:58.33 | *** join/#htc-linux lkcl_work (n=c3a976e3@217.147.94.29) |
14:38.06 | *** part/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com) |
15:44.40 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
15:53.09 | *** join/#htc-linux ralith_ (n=ralith@66.150.12.86) |
16:16.27 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
16:18.58 | *** join/#htc-linux RoEn_PC (n=roen@p54A67B67.dip.t-dialin.net) |
16:32.42 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
16:33.03 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
16:47.35 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
16:47.45 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
17:05.37 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
17:16.22 | *** join/#htc-linux BabelOued (n=Fabrice@82.238.28.28) |
17:44.38 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
17:56.15 | *** join/#htc-linux Ralith (n=ralith@66.150.12.86) |
18:08.22 | *** join/#htc-linux TripleDES (n=sergio@89.129.143.241) |
18:21.24 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
19:24.43 | *** join/#htc-linux pwr (n=pwr@86.121.147.90) |
20:11.02 | *** join/#htc-linux ccureau (n=chris@cl-64.atl-01.us.sixxs.net) |
20:11.29 | ccureau | question: are the gpios in a set location on these arm chips? |
20:11.47 | ccureau | say, if we read from gpio 1, then it'll read from the same memory location? |
20:22.25 | *** join/#htc-linux pH5 (n=ph5@p5485C983.dip.t-dialin.net) |
20:25.53 | pH5 | cr2: what do I have to look for in nk.exe to find the pwr i2c code? |
20:29.02 | lkcl | pH5: got a suggestion for you |
20:29.28 | lkcl | how many gpio pins are outputs that you dont know what they are for? |
20:30.12 | pH5 | lkcl: not sure. why? |
20:30.38 | lkcl | is it 5 or is it 30 |
20:30.54 | lkcl | count them. seriously. |
20:33.11 | pH5 | let's see, 3,4,9,18,48,56,57,114,116,119 are white in the wiki gpio list |
20:33.39 | lkcl | ok dat quite a few. |
20:33.49 | pH5 | then I have about 8 unknown ones on the cpld |
20:34.38 | lkcl | ok which are default to 1? |
20:34.59 | BabelOued | lkcl : latest w100fb driver that is working for me is revision 1.27 with platform_device fix, the two other comit are without platform_device |
20:35.22 | lkcl | in a pxadump |
20:35.46 | pH5 | hm.. gpio 116 and four of the egpios |
20:37.13 | lkcl | and 3 is unidentified. |
20:37.39 | pH5 | yes, and 4 and 9 are inputs, actually |
20:37.54 | lkcl | ok so thats not so many to do pfw 0x40e00130 1 0x00200000 or whatever is it? |
20:38.01 | lkcl | to set them to 0 |
20:43.18 | lkcl | then chqange vol |
20:46.46 | lkcl | and what will happen, if you have the right one, is that it will simply be reset to 1 when you change volume. |
20:47.18 | lkcl | the reason is because wavedev checks whether it's 0, and if it's zero, sets it to 1, to power up the i2c. |
20:50.32 | lkcl | it's how i accidentally found the other two acx powerup gpios |
20:51.10 | lkcl | which are set when the dll is first loaded, and are never powered down even when you switch off wireless |
20:51.34 | lkcl | BabelOued: probably a good idea to send a message about that to kd@hh.org |
20:53.52 | BabelOued | lkcl : ok. and i ask about how disable hwaccel that seem to be the only major difference |
20:53.54 | pH5 | lkcl: cool! I'll try that when I play with haret next time. I already know my codec power pin, though. |
20:54.51 | lkcl | it would help to have some haret gpio set/clear commands. |
20:55.54 | BabelOued | any news about sound on ba ? |
20:58.49 | lkcl | not yet. still having fun floundering around |
21:08.17 | cr2 | pH5: the suspend sequence, and the voltage change related kernel ioctls. i'm thinking about creating a wiki page for the last |
21:10.21 | cr2 | lkcl: with 4 devices it's not easy to find out which one to take next :) i was searching for the audio data yesterday, but found only RTC and power i2c data. |
21:11.19 | cr2 | it seems to me that universal can charge the battery even in the suspended state, and there is one extra gpio related to it. |
21:12.14 | cr2 | hmm. spi on sable. |
21:18.38 | ccureau | cr2: got a sec? |
21:20.00 | *** join/#htc-linux rmoravcik (n=rmoravci@icm4-orange.orange.sk) |
21:43.11 | ccureau | cr2: I'm in the middle of disassembling and looking at a dll file from my phone...touch.dll to be specific |
21:44.12 | ccureau | I'm trying to determine the routine that is called when the screen touch happens...closest I can see is the TouchCreateEvent subroutine. |
21:44.31 | ccureau | might you have any suggestions for figuring that out? |
22:12.31 | *** join/#htc-linux WizMaui_ (n=WizMaui@62.112.90.231) |
22:14.14 | *** join/#htc-linux rmoravci1 (n=rmoravci@icm2-orange.orange.sk) |
22:38.58 | *** join/#htc-linux Fossi (n=Fossi@e176108025.adsl.alicedsl.de) |
23:45.59 | *** join/#htc-linux Ralith (n=ralith@soggy202.drizzle.com) |
23:52.37 | cr2 | Kevin2: spi trace: |
23:52.41 | cr2 | HaRET(1)# wi 5 |
23:52.45 | cr2 | Will set memory tracing to:a9200202 a9200204 0000000a a9200202 a9200204 |
23:52.46 | cr2 | Will set software debug to:ffffffff->00000003 ffffffff->00000003 |
23:52.46 | cr2 | irq:9062d9d8@b09143f8=9101e020 abort:906215d4@b09143f0=9101e048 prefetch:9062d548@b09143ec=9101e088 data=90ff5000 C=9101e358,9101e61c,9101e13c sizes=a:000000a8,c:00000680,t:0002c748 |
23:52.46 | cr2 | Replacing windows exception handlers... |
23:52.46 | cr2 | Finished installing exception handlers. |
23:52.47 | cr2 | 0000bb61: irq 30(RTC0) |
23:53.04 | cr2 | 105c7c72: debug 09633c74: e1c320b2(strh) 0000c000 a9200200 |
23:53.08 | cr2 | 10678f7b: debug 09633c74: e1c320b2(strh) 0000c000 a9200200 |
23:53.09 | cr2 | 10679003: debug 09633cc0: e1d230b4(ldrh) 00002020 a9200200 |
23:53.09 | cr2 | 106d0333: debug 09633c74: e1c320b2(strh) 0000c000 a9200200 |
23:53.09 | cr2 | 106d03ba: debug 09633cc0: e1d230b4(ldrh) 00002020 a9200200 |
23:53.09 | cr2 | Handled 56984 irq, 36212 abort, 0 prefetch, 20939 lost, 0 errors |
23:53.09 | cr2 | HaRET(11)# |