00:00.20 | maejrep[w] | yeah same here lavender-t |
00:00.25 | maejrep[w] | but dcordes isn't seeing that |
00:00.27 | NetRipper | maejrep[w], i've been removing some debug stuff and need to update teh #if's for diamond and cdma variants too |
00:00.39 | maejrep[w] | NetRipper: which debug stuff? prink's? |
00:00.41 | maejrep[w] | +t |
00:00.48 | NetRipper | maejrep[w], printk's yes |
00:01.38 | cr2 | dcordes: you've posted the dump muu ? i'll check |
00:02.10 | NetRipper | maejrep[w], what does "clamshell" mean? |
00:02.30 | dcordes | http://linuxtogo.org/~lgorris/misc/x1-mmu.txt |
00:02.41 | cr2 | dcordes: you don't have any extra mappings |
00:03.00 | cr2 | dcordes: can you try to add both 923 and b23 ? |
00:03.33 | cr2 | addlist mmutrace 0x92300000 4 |
00:03.39 | cr2 | addlist mmutrace 0xb2300000 4 |
00:03.50 | cr2 | and for the write too |
00:04.17 | cr2 | lavender-t: do you have strong nerves ? |
00:04.29 | lavender-t | ahhhhh :s |
00:05.01 | lavender-t | anything could burn my phone ? |
00:05.25 | *** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk) |
00:05.32 | maejrep[w] | 92300000 | a9900000 | 1MB section | AP=1 T=2 |
00:05.38 | cr2 | can you sed the register names to http://wiki.xda-developers.com/index.php?pagename=RaphaelLCD |
00:05.38 | dcordes | cr2: ok addlist'D |
00:05.44 | maejrep[w] | b2300000 | a9900000 | 1MB section | AP=1 T=2 |
00:05.48 | cr2 | using data from |
00:06.23 | cr2 | http://wiki.xda-developers.com/index.php?pagename=RaphaelMDDI |
00:06.31 | cr2 | as a separate column ? |
00:09.05 | lavender-t | cr2: were you talking to me ? |
00:09.43 | cr2 | yes :) it's 1:09, and i'm going crazy with mddi ;) |
00:09.51 | lavender-t | ok :) |
00:10.07 | lavender-t | but i need to figure out what it is first ... |
00:10.09 | cr2 | but don't delete the original numbers |
00:10.37 | cr2 | because i'll 'join' with the raph/diam800 using it. |
00:11.10 | maejrep[w] | lavender-t: he's saying use the MDDI page as a reference point, and add the names into the LCD page |
00:11.26 | cr2 | SSICTL 0x120000 |
00:11.28 | maejrep[w] | ie, if it says 150000, make it say GPIOD etc |
00:11.45 | lavender-t | ah ok |
00:12.00 | cr2 | 120000=170 |
00:12.30 | cr2 | so it should be | SSICTL | 120000 | =170 | |
00:12.46 | maejrep[w] | if you really want to be thorough you can make it: mddi_write( 170, SSICTL ) :D |
00:12.53 | lavender-t | got it. will do. |
00:13.04 | cr2 | maejrep: mddi_remote_write ? |
00:13.13 | dcordes | cr2: what to do after addlist |
00:13.21 | cr2 | dcordes: wi |
00:13.22 | maejrep[w] | no, in .27 there's a macro called mddi_write and mddi_read |
00:13.32 | cr2 | maejrep[w]: ok, like in the spl |
00:13.38 | maejrep[w] | which is defined as writel( (a), MDDI_##name ) |
00:14.04 | maejrep[w] | and hten MDDI_SSICTL is defined as 120000 |
00:14.17 | cr2 | maejrep[w]: strange, because out of this patent pictures i got an idea that's it is really remote |
00:14.31 | cr2 | ok |
00:14.44 | maejrep[w] | hmm, could be, iwll have to check again |
00:14.59 | cr2 | lavender-t: some regs are not documented by google |
00:15.04 | cr2 | lavender-t: like PWM1* |
00:15.29 | maejrep[w] | cr2: so you said dcordes' x1 can help explain pwm ? |
00:16.36 | lavender-t | ok i guess i will leave the ?s as is |
00:16.47 | dcordes | 000.026 7805f810: e5853000(str) # b2300000 =000001cc |
00:16.47 | dcordes | 000.026 7805f850: e5853000(str) # b2300000 =00000030 |
00:16.47 | dcordes | 000.026 7805f8d8: e5853000(str) # b2300000 =000001cd |
00:16.47 | dcordes | 000.026 7805f970: 05852000(str) # b2300000 =00000200 |
00:16.54 | dcordes | it seems to react on keypress |
00:17.02 | dcordes | outputs more lines then |
00:21.39 | NetRipper | right, im off to bed, ill finish tomorrow and commit it :) |
00:21.43 | NetRipper | good night |
00:22.09 | cr2 | maejrep[w]: g1 uses the arg3 modification for pwm |
00:22.43 | cr2 | maejrep[w]: and arg2=2*arg3 in the 7param formula |
00:23.02 | dcordes | cr2: http://privatepaste.com/0d1YhjwX4b |
00:24.37 | cr2 | maejrep[w]: which should be a normal symmetric clock signal. when you change the arg3, you get a pwm |
00:25.40 | cr2 | dcordes: what is 0x6c/2 device ? |
00:25.51 | cr2 | 0x36, hmm. |
00:26.02 | cr2 | camera ? accelerometer ? OJ ? :) |
00:26.29 | maejrep[w] | cr2: what is pwm? |
00:26.56 | maejrep[w] | i think 36 is camera, yes |
00:27.11 | cr2 | pulse-width modulation |
00:27.21 | dcordes | cr2: led is complicated on x1 maybe it's that |
00:27.35 | maejrep[w] | hmm |
00:27.37 | cr2 | maejrep[w]: if he has the same cam as we |
00:27.47 | maejrep[w] | cr2: looks like they fixed the i2c driver in x1 :) |
00:28.00 | maejrep[w] | oh, maybe not |
00:28.09 | maejrep[w] | just the 36 driver does it correctly: |
00:28.09 | cr2 | maejrep: _________|^^^^^^^^^|______________| |
00:28.23 | dcordes | http://wiki.xda-developers.com/index.php?pagename=Kovsky_Cameras |
00:28.28 | maejrep[w] | # |
00:28.28 | maejrep[w] | # |
00:28.28 | maejrep[w] | 001.129 7805fbc4: e5873000(str) # b2300000 =0000016c |
00:28.28 | maejrep[w] | # |
00:28.28 | maejrep[w] | 001.129 7805fbec: e5873000(str) # b2300000 =00000208 |
00:28.51 | maejrep[w] | in the other chips, they don't do the 0x200 "last byte" bit |
00:28.55 | cr2 | maejrep: the ratio between 1 and 0 changes. for normal usual clock it's 1:1 |
00:28.56 | maejrep[w] | bye i2c-msm does |
00:29.39 | maejrep[w] | dcordes: actually, if you have auto-backlight-adjust enabled, it could be that |
00:29.55 | maejrep[w] | the light sensor is on i2c |
00:30.12 | cr2 | maejrep[w]: brightness sensor ? but it's on microP ? |
00:30.14 | maejrep[w] | but on raph, the light sensor is part of klt i think |
00:30.22 | cr2 | ok |
00:30.34 | maejrep[w] | cr2: yeah, but I don't know what else could explain his 38 reads |
00:30.38 | dcordes | klt microP are the two microcontrollers? |
00:31.00 | maejrep[w] | there are 2 microp chips: klt and ksc (microp-led and microp-key) |
00:31.20 | maejrep[w] | probably the same chip/controller, but at different addresses, so they're considered separate "chips" |
00:31.33 | dcordes | ok |
00:32.09 | cr2 | 22:35:52 [D:AUD] open [\Windows\AudioPara3.csv] success!! |
00:32.19 | maejrep[w] | dcordes: actually what's weird is that he's not reading anything |
00:32.24 | maejrep[w] | er cr2 |
00:32.32 | dcordes | cr2: is that from blackstone dmesg? |
00:32.37 | cr2 | yes |
00:32.38 | maejrep[w] | cr2: what?? is it really that simple? :P |
00:32.41 | maejrep[w] | a .csv file |
00:32.50 | cr2 | maejrep[w]: check it |
00:33.00 | maejrep[w] | my phone's off cause I don't have a charger at work :P |
00:33.08 | maejrep[w] | (with the reboot bug) |
00:33.08 | cr2 | k |
00:33.28 | maejrep[w] | dcordes: can you upload that audiopara3.csv file somewhere? |
00:33.58 | dcordes | I don't have blackstone |
00:34.47 | cr2 | 22:35:52 [D:AUD] open TIAGC.csv success!! |
00:35.00 | maejrep[w] | oh |
00:35.03 | cr2 | dcordes: kaiser & x1 ? |
00:35.20 | cr2 | lol |
00:35.21 | maejrep[w] | dcordes: can you check if you have it on any of your devices |
00:35.27 | cr2 | 22:35:52 [D:AUD] AgcTable[2] (enable AGC youtube.exe) |
00:35.33 | maejrep[w] | yeah i saw that heh |
00:35.39 | dcordes | youtube in dmesg |
00:35.59 | cr2 | it's like ati that hardcoded the PocketTV.exe in the video driver ;) |
00:37.02 | cr2 | 22:35:52 [D:GSNR] Pass CRC32-3 |
00:37.13 | cr2 | why does the accelerometer do CRC32 ? |
00:37.52 | cr2 | hehe. my old good friends: MD and NS |
00:37.56 | cr2 | 22:35:53 [D:BT] [BTU]MD NS ADDR 504070d8 504070dc |
00:37.56 | cr2 | 22:35:53 [D:BT] [BTU]MD NS 3ff9b ff9e0044 |
00:37.56 | cr2 | 22:35:53 [D:BT] [BTU]Uart_DM_Clock(1, 115200) |
00:38.04 | maejrep[w] | nice |
00:38.23 | cr2 | maejrep[w]: btw, you can invert them into 7param |
00:38.38 | cr2 | and check if arg2=arg3*2 |
00:38.56 | maejrep[w] | to know pwm? |
00:38.56 | cr2 | it's not a pwm |
00:39.19 | cr2 | pwm is when arg2 != arg3*2 |
00:39.30 | exco | imfloflo: we don't need to chat on xda-devs ... if I can help you just ask me here |
00:39.39 | dcordes | maejrep[w]: http://linuxtogo.org/~lgorris/misc/ |
00:44.07 | maejrep[w] | dcordes: 403 forbidden |
00:45.36 | dcordes | maejrep[w]: retry. I didn't have that problem before |
00:45.59 | maejrep[w] | worked, thanks |
00:46.39 | maejrep[w] | wow |
00:46.45 | maejrep[w] | that looks like it could be very useful information ;o |
00:48.47 | maejrep[w] | dcordes: didn't have TIAGC.csv? |
00:49.28 | maejrep[w] | cr2: isn't GSNR "ground signal to noise ratio"? why do you say accelerometer? |
00:49.56 | cr2 | G-SeNsoR n |
00:50.02 | cr2 | in htc-speak |
00:50.38 | maejrep[w] | that's lame |
00:52.15 | cr2 | 22:35:54 Turn on PMIC VREG[0x100] |
00:52.16 | cr2 | .22:35:54 [D:CAM] Turn on sensor VDDD 1.8v OK |
00:52.36 | cr2 | ok, this interface is already known |
00:53.25 | cr2 | hm . different cam on blac100 ? |
00:53.28 | maejrep[w] | i wish i could find the dmesg area on my phone |
00:53.29 | cr2 | 22:35:54 [D:CAM] Check MT9P012 |
00:53.35 | maejrep[w] | looks the same? |
00:53.40 | maejrep[w] | or is ours p011 ? |
00:53.51 | maejrep[w] | raph is same as on g1 |
00:54.08 | cr2 | don't remember |
00:54.14 | maejrep[w] | at least, same sensor .. i2c chip *might* be different .. yet to look into it |
00:54.27 | maejrep[w] | i know g1's camera sensor is on a different i2c data address |
00:54.30 | cr2 | MI380 is the second one. i think it's the same on raph |
00:54.38 | maejrep[w] | i don't have the 2nd one |
00:54.52 | maejrep[w] | http://wiki.xda-developers.com/index.php?pagename=RaphaelCameras |
00:54.58 | maejrep[w] | MT9T013 |
00:55.08 | maejrep[w] | so it is different |
00:55.13 | maejrep[w] | other cam is MT9V113 |
00:55.33 | cr2 | ok |
00:55.38 | cr2 | 22:35:54 Turn off PMIC VREG[0x800000] |
00:55.38 | cr2 | .22:35:54 [D:SD] SD power off- |
00:55.39 | maejrep[w] | <PROTECTED> |
00:55.43 | cr2 | this one is known too |
00:55.54 | maejrep[w] | (on g1 it's 0x78>>1 |
00:56.01 | cr2 | all different |
00:57.11 | cr2 | 22:35:56 [D:DISP] g_CurrentPanelType=10 |
00:57.21 | maejrep[w] | cr2: theoretically we should be able to copy the g1 camera implementation, right? assuming we get the vreg/clk/whatever-else figured out? |
00:57.32 | maejrep[w] | 0xa or 0x10 ? |
00:57.43 | cr2 | 0xa, i think |
00:57.48 | maejrep[w] | probably |
00:57.54 | maejrep[w] | spl will tell you :P |
00:57.58 | maejrep[w] | (%d vs %x) |
00:57.59 | dcordes | any further i2c tests required? |
00:58.07 | cr2 | isn't it some binary qcom library for cam ? |
00:58.31 | maejrep[w] | dcordes: if you want to check scancodes for keyboard .. ? :) |
00:58.31 | maejrep[w] | really? :| |
00:58.31 | maejrep[w] | i know the i2c chip driver is implemented in source |
00:58.44 | maejrep[w] | but I don't know what they do with that chip driver yet |
00:59.05 | cr2 | 22:35:56 [D:TP] TSSC_CTL=0x7d |
00:59.05 | cr2 | 22:35:56 [D:TP] TSSC_STATUS=0x200 |
00:59.37 | dcordes | maejrep[w]: how? |
00:59.40 | maejrep[w] | that looks different |
01:00.20 | maejrep[w] | dcordes: the same mmutrace dump you did to get what you pasted earlier, but a) turn off backlight-adjust to reduce chatter, and b) press a key and write down the number right after the "000001cf" line |
01:00.44 | maejrep[w] | maybe just a spot check to see how different it is |
01:01.02 | maejrep[w] | checking things like TAB, BKSP, Q, SPACE, |
01:01.16 | maejrep[w] | if it's very different we'll need to document all the keycodes |
01:01.18 | maejrep[w] | *scancodes |
01:01.26 | dcordes | ok |
01:02.06 | maejrep[w] | dcordes: on press, you'll see a number < 0x80 (like 0x30 for example). then when you release, you'll see that same number | 0x80 (in this example, 0xa0) |
01:02.15 | maejrep[w] | you only need the keypress number |
01:02.20 | maejrep[w] | not release |
01:04.33 | dcordes | wince calls the navi sensor "optical joystick" |
01:04.41 | maejrep[w] | o.0 |
01:04.43 | cr2 | good night, it's too late... |
01:04.44 | maejrep[w] | it's not optical |
01:04.46 | maejrep[w] | nite cr2 |
01:05.00 | maejrep[w] | dcordes: behind the scenes it calls it navi |
01:05.06 | maejrep[w] | htcnavi.dll e.g. |
01:05.27 | dcordes | ok been wondering why you call it navi |
01:05.40 | maejrep[w] | that's why :) |
01:05.54 | dcordes | the x1 leds are neat |
01:05.57 | maejrep[w] | its what htc calls it in their service manual as well |
01:06.03 | maejrep[w] | what leds does it have? |
01:06.16 | maejrep[w] | x1 is xperia? |
01:06.26 | dcordes | untick auto adjust backlight? |
01:06.38 | maejrep[w] | yeah, that'll make it easier to read the i2c output |
01:06.43 | dcordes | xperia x1 = kovsky = venus |
01:07.10 | maejrep[w] | cool |
01:07.41 | maejrep[w] | oh the keyboard layout is very different :x |
01:08.47 | dcordes | hm the keyboard backlighht sort of fades on also |
01:09.00 | maejrep[w] | that sounds complicated :p |
01:09.10 | maejrep[w] | have you been into the spl yet? |
01:09.11 | dcordes | why? |
01:09.18 | maejrep[w] | it might report the microp version number |
01:09.32 | dcordes | no but cr2 |
01:10.13 | maejrep[w] | oh you dumped the spl? i meant booting into the spl (tri-color bootloader) |
01:11.01 | dcordes | oh sorry. no I didn't do that but I've got a hard spl |
01:11.24 | maejrep[w] | 22:48:48 [D:KEY] Init MicroP keyblock |
01:14.06 | lavender-t | oh cr2's left ? |
01:14.23 | maejrep[w] | yes |
01:14.26 | lavender-t | just sed the file |
01:16.07 | lavender-t | how to send the file to him ? |
01:17.49 | maejrep[w] | isn't it just on the wiki? |
01:18.12 | lavender-t | yep ... so i just need to update the wiki ? |
01:18.18 | maejrep[w] | yeah i think so |
01:18.26 | maejrep[w] | heading home |
01:18.39 | lavender-t | ok will do. |
01:20.07 | dcordes | lavender-t: I wish you a pleasent evening |
01:20.24 | dcordes | maejrep[w] I mean. will test the keycodes tomorrow |
01:20.36 | dcordes | also going to bed. gnite |
01:27.34 | *** join/#htc-linux zycho_ (n=zycho@a89-183-89-249.net-htp.de) |
02:35.49 | *** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net) |
02:38.57 | *** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net) |
02:52.30 | *** join/#htc-linux nato2k (n=templarn@76.205.128.145) |
02:52.38 | *** part/#htc-linux nato2k (n=templarn@76.205.128.145) |
02:59.18 | *** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net) |
03:01.57 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
03:35.54 | maejrep | cr2: so seems that reboot problem just kind of cleared itself up while I was preparing to do the hard reset :| |
03:36.24 | maejrep | i went to disable RNDIS (advanced networking functionality), and it got stuck trying to do that, so I reset it, and then it all worked fine after that (including power collapse) |
03:36.30 | maejrep | kinda strange |
03:39.01 | *** join/#htc-linux infernix (n=nix@unaffiliated/infernix) |
03:45.08 | *** join/#htc-linux _workkaze (n=kaze@ABordeaux-152-1-43-136.w82-125.abo.wanadoo.fr) |
03:46.51 | *** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net) |
03:48.28 | *** join/#htc-linux maejrep (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net) |
04:02.28 | *** join/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de) |
04:02.52 | *** join/#htc-linux infernix (n=nix@unaffiliated/infernix) |
04:25.00 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net) |
05:07.01 | *** join/#htc-linux tmzt (n=tmzt@adsl-69-221-148-155.dsl.akrnoh.ameritech.net) |
05:12.46 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
05:13.48 | lavender-t | hi maejrep, any new updates to your patches ? |
05:14.05 | lavender-t | i mean the .27 ? |
05:18.29 | maejrep | i haven't done anything with it |
05:19.43 | lavender-t | you know anyone's porting it to diam ? netripper ? |
05:19.54 | maejrep | I don't |
05:20.24 | maejrep | NetRipper has been working on cleaning up the changes to get ready for the first big ltg commit to the .27 branch |
05:20.34 | lavender-t | k ic |
05:21.02 | maejrep | it'll likely feel like a step backward at that point until the remaining merge issues have been resolved |
05:21.40 | lavender-t | i'll give it a try ... time is a little limited though. gonna take a 2-week vacation from next week :) |
05:22.18 | maejrep | so you'll have 2 weeks to work on it?! :D |
05:22.22 | maejrep | jk :p |
05:22.47 | lavender-t | oh man ... |
05:22.47 | *** join/#htc-linux zycho (n=zycho@a89-183-89-249.net-htp.de) |
05:59.34 | *** join/#htc-linux miknix (n=miknix@adsl-67-117-91-116.dsl.sntc01.pacbell.net) |
06:02.08 | *** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com) |
06:11.30 | parmaster | i guess the choice of using yaffs would be because of wear leveling |
06:12.04 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
06:16.57 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
06:31.39 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
06:41.20 | maejrep | cr2: I found my wince dmesg area ;x |
06:41.26 | maejrep | 0x17600000 |
06:42.27 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
06:46.37 | *** join/#htc-linux Kuma (n=John@f054218077.adsl.alicedsl.de) |
06:46.44 | *** join/#htc-linux bs_ (n=kra@87.72.13.87) |
06:54.39 | *** join/#htc-linux MethoS (n=lem@host-091-096-211-086.ewe-ip-backbone.de) |
07:03.01 | maejrep | http://www.privatepaste.com/c61C6R9zw9 - nice to know :P klt init |
07:24.47 | *** join/#htc-linux lpotter (n=ljp@58.173.176.153) |
07:25.07 | *** join/#htc-linux sietse (n=sietse@vogons.xs4all.nl) |
07:31.44 | *** join/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de) |
07:34.34 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
07:39.16 | *** join/#htc-linux seand (n=sean@adsl-69-232-201-43.dsl.pltn13.pacbell.net) |
07:45.13 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-39-53.web.vodafone.de) |
07:45.26 | cr2 | maejrep: hi |
07:45.44 | cr2 | maejrep: found something useful in dmesg ? |
07:46.03 | maejrep | some clues to hardware |
07:46.07 | maejrep | not really earth shattering |
07:46.22 | maejrep | a lot of it we already knew, but some of it is most likely raph800 specific |
07:47.22 | maejrep | looks like the modem reset hook is probably implemented in HtcServices.dll |
07:48.06 | cr2 | do you see the SMD channel list ? |
07:48.39 | maejrep | it auto detects everything else, except AT and DATA i think |
07:48.47 | maejrep | but yeah i think i saw those offsets in the output |
07:49.15 | cr2 | do you see them in smem ? |
07:49.20 | maejrep | yes |
07:49.28 | maejrep | i've had that information for a while now |
07:49.33 | maejrep | just haven't implemented it |
07:49.33 | cr2 | lavender-t: thanks for editing the wiki :) |
07:49.50 | cr2 | maejrep: hm. why is it not autodetected ? |
07:50.12 | maejrep | cause qct,htc,sprint are dumb? |
07:50.13 | maejrep | :p |
07:50.37 | maejrep | (mostly qct) |
07:50.49 | cr2 | ok |
07:51.28 | exco | can I find out the wifi base address of Polaris with haretconsole? |
07:52.29 | maejrep | 22:44:34 [K] OEMSetAlarmTime: [0x36a7af4a], 1-20, 22:50:50 |
07:52.44 | maejrep | seems strange |
07:53.01 | cr2 | exco: i don't think you need to do it. sdio will take care. what you need is to find the power gpios and vregs |
07:53.45 | cr2 | maejrep: you want to do psoc cmd9 ? |
07:53.58 | cr2 | it's the psoc id sequence |
07:55.18 | cr2 | maejrep: mddi_client_lcd_get_vsync_param |
07:55.29 | cr2 | maejrep: which dll has this string ? |
07:55.49 | maejrep | not sure |
07:55.57 | cr2 | nk.exe ? |
07:56.50 | cr2 | ok, i must leave now |
07:58.13 | maejrep | looks like no |
07:58.20 | maejrep | dont see it in oem_misc either |
07:59.11 | *** join/#htc-linux ewasx (n=Armin@armin-dev.ict.tno.nl) |
07:59.30 | *** join/#htc-linux DracoDan| (n=F@pool-71-163-138-224.washdc.east.verizon.net) |
08:07.47 | maejrep | cr2: CertVerify: DISPTOOLS.dll trust = 2 ? |
08:07.52 | maejrep | for the vsync param line |
08:17.20 | *** join/#htc-linux sietse (n=sietse@vogons.xs4all.nl) |
08:23.45 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
08:37.50 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
08:38.02 | exco | if I think I have the correct gpio for an action (button press) can I execute it with haret to check if I'm right? |
09:02.14 | *** join/#htc-linux ALoGeNo (n=alogeno@unaffiliated/alogeno) |
09:10.05 | *** join/#htc-linux timebomb (n=tb@e176123067.adsl.alicedsl.de) |
09:14.51 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
09:19.33 | NetRipper | marex, in the htcraphael-panel.c you bail out when it's not a raphael.. shouldn't it also work for diamond? |
09:19.56 | NetRipper | s/marex/maejrep/ |
09:20.03 | marex | huh ? I have nothing to do wtih msm based devices |
09:20.05 | marex | ah ok |
09:20.06 | NetRipper | sorry ;) |
09:20.16 | NetRipper | tab-laziness |
09:26.01 | *** join/#htc-linux pichurri (n=pichurri@users3.ilo.org) |
09:26.51 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
09:26.54 | Untouchab1e | Good morning _D |
09:27.27 | NetRipper | morning |
09:29.05 | *** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl) |
09:29.40 | Untouchab1e | How are you? |
09:30.26 | NetRipper | im good, at work |
09:30.29 | NetRipper | you? |
09:30.33 | Untouchab1e | hehe, also good.. At class |
09:30.36 | Untouchab1e | ^^ |
09:30.52 | *** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl) |
09:31.15 | Untouchab1e | Installed eclipse and the ADT yesterday.. I like the idea of the layout being handled by .xml |
09:32.31 | NetRipper | ah |
09:32.41 | NetRipper | bit WPF/XAML like? |
09:32.50 | NetRipper | but then for java instead of .net |
09:33.29 | Untouchab1e | Yeah, I guess.. |
09:33.45 | *** join/#htc-linux mib_iumf19 (i=5144ce60@gateway/web/ajax/mibbit.com/x-88b1cbc1486bfa3a) |
09:34.28 | Untouchab1e | Ive been working quite a bit with VB.NET and C#.Net, so I like it when layouts doesnt need to be hard-coded ^^ |
09:34.41 | Untouchab1e | However, Eclipse isnt working too well for me on any of my computers.. |
09:34.55 | Untouchab1e | Used up 1,5GB of RAM.. lol |
09:35.26 | NetRipper | ouch |
09:35.41 | NetRipper | guess you're not using a barebone eclipse :) |
09:36.49 | Untouchab1e | yeah, might seem like it.. |
09:37.35 | Untouchab1e | I tried it on my laptop first, (4GB RAM, Intel Core 2 Duo 2,4GHz), and I got that major memory hog.. There goes my dream of doing some Android development on my NetBook, lol |
09:40.13 | NetRipper | 4gb must be plenty for eclipse |
09:40.20 | Untouchab1e | yeah, one would think so |
09:40.31 | NetRipper | you got some screwed up eclipse perhaps ;) |
09:40.51 | Untouchab1e | but suddenly, Eclipse just went awesomely slow and reported memory overflow and wanted to close |
09:40.52 | Untouchab1e | :P |
09:41.07 | NetRipper | yea, sounds like memory leak |
09:41.46 | Untouchab1e | Can't say my first impression with Eclipse is all good :P |
09:43.56 | Untouchab1e | oh well, on brighter matters.. anything new with the port? Have we decided if we will wait for .8 or stick with .7? |
09:55.22 | *** part/#htc-linux daspsycho_work (n=TimJorda@213.155.79.202) |
09:55.50 | NetRipper | .7 |
09:56.01 | NetRipper | maybe we'll port to .28 againt though, we'll see that then |
09:58.13 | Untouchab1e | Okey.. sounds good |
10:25.08 | *** join/#htc-linux TheEnforcer (n=kvirc@p54990131.dip0.t-ipconnect.de) |
10:32.20 | *** join/#htc-linux metter (n=metter@239-186.203-62.cust.bluewin.ch) |
10:46.25 | *** join/#htc-linux mib_69lnyg (i=5144ce60@gateway/web/ajax/mibbit.com/x-d7192d98e08ef132) |
10:51.21 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) |
11:16.52 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
12:02.53 | *** join/#htc-linux mib_69lnyg (i=5144ce60@gateway/web/ajax/mibbit.com/x-97ed0fc401c4f9ce) |
12:14.34 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
12:14.36 | Untouchab1e | :D |
13:08.08 | *** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-b512365ea80beeb6) |
13:38.45 | *** join/#htc-linux stadicon (n=liberost@79.107.28.155) |
13:39.13 | stadicon | hi |
13:40.40 | stadicon | i am interested in helping with drivers for DIAM100 |
13:41.14 | stadicon | is there anyone can help me? |
13:44.22 | imfloflo | yes |
13:44.44 | imfloflo | jsut let your message |
13:44.50 | imfloflo | people rea log |
14:11.20 | maejrep | <NetRipper> marex, in the htcraphael-panel.c you bail out when it's not a raphael.. shouldn't it also work for diamond? <-- you want me to make it work for everything before it works for me?! |
14:11.21 | maejrep | ;) |
14:11.43 | NetRipper | maejrep, no just needed to konw if it was specifically to raphael or not |
14:11.57 | maejrep | lol |
14:12.17 | NetRipper | maejrep, btw, when i boot, i get an error regarding clock |
14:12.18 | maejrep | yeah, i wasn't done debugging that area yet ;x |
14:12.27 | NetRipper | it tries to set sdc clock to 50mhz, but it fails |
14:12.33 | NetRipper | clock 21:50000000 |
14:12.37 | maejrep | but it works? |
14:12.43 | NetRipper | it mounts, yes |
14:13.08 | NetRipper | but the clock function returns an error |
14:13.11 | maejrep | I think there was a change to drivers/mmc/hosts/msm* that made it use sdcc_set_host_clock |
14:13.15 | maejrep | that I missed |
14:13.44 | maejrep | I get the same error, but didn't get a chance to look into it yet |
14:13.49 | NetRipper | ah ok |
14:13.54 | NetRipper | when i try to boot android, it hangs |
14:13.57 | NetRipper | well not the device |
14:14.01 | NetRipper | but it just doesn't boot android |
14:14.11 | NetRipper | thought it may have to do with it |
14:14.19 | NetRipper | does android boot for you? |
14:16.41 | NetRipper | it stops before the splash screen displays |
14:17.05 | maejrep | another option is to set fmax to 48MHz ? |
14:17.08 | maejrep | i have not tried android |
14:18.19 | NetRipper | think i'll just commit this and we'll go from there |
14:18.37 | NetRipper | last thing left is fixing up the diamond board |
14:18.52 | stadicon | may i ask in which folder is htcraphael-panel.c? |
14:19.02 | NetRipper | arch/arm/mach-msm/ |
14:19.11 | stadicon | oh, great thanks |
14:19.20 | stadicon | i was looking on drivers/input :) |
14:19.31 | NetRipper | board-htcraphael-panel.c |
14:20.27 | stadicon | so we need to give "touch" capabilities to the driver? |
14:21.15 | NetRipper | we already have touchscren |
14:21.38 | NetRipper | drivers/input/touchscreen/ |
14:21.44 | NetRipper | msm_ts |
14:21.53 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
14:23.02 | maejrep | there's a lot of stuff still on my todo list :p |
14:25.37 | NetRipper | maejrep, ok no problem, just wanted to know if i have the same result as you do :) |
14:25.43 | NetRipper | or if i screwed up something |
14:25.44 | NetRipper | ;) |
14:26.18 | maejrep | yeah, I get the clock error, but it still works for me |
14:26.34 | maejrep | so I get a feeling dropping the max freq a little bit might help with that |
14:27.02 | stadicon | yes, but there is a touch interface on the "board" |
14:27.22 | stadicon | i mean, the call buttons etc. are a "capacitive screen" |
14:27.34 | maejrep | that's a different "touchscreen" stadicon |
14:27.40 | maejrep | and there's not a full driver for it yet |
14:27.45 | stadicon | yes |
14:28.07 | maejrep | we have the research for it, just haven't written a driver yet |
14:28.40 | maejrep | board-htcraphael-keypad should implement the 5 hard buttons behind the navi (that's what that area is called), but not the touch sensitive aspect of it |
14:28.42 | stadicon | that's what i said before... |
14:28.53 | maejrep | which means we still can't distinguish between Home and Send, for example |
14:29.11 | stadicon | yes, i understand that |
14:29.17 | stadicon | so we have to make a new driver |
14:29.25 | stadicon | for this touchscreen... |
14:29.39 | maejrep | yes, sorry, that is correct |
14:29.41 | NetRipper | yep |
14:29.41 | stadicon | i am really interested in working on that |
14:29.58 | stadicon | but i haven't worked again on drivers... :( |
14:30.01 | NetRipper | but let's call it the navi instead of touchscreen to prevent confusion |
14:30.02 | NetRipper | :) |
14:30.05 | *** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net) |
14:30.06 | maejrep | :) |
14:30.15 | stadicon | i am now reading a tutorial about driver writing |
14:30.17 | maejrep | stadicon: the i2c research for it is on the wiki |
14:30.32 | stadicon | oh, ok |
14:30.39 | stadicon | i'll take a look |
14:30.45 | maejrep | you're more than welcome to help :D |
14:30.54 | stadicon | sorry to annoy you but i want to help that project |
14:31.17 | stadicon | yes, but i am quite a starter on that area :p |
14:31.33 | stadicon | i 've done lots of other things about programming and linux |
14:31.38 | stadicon | but not that yet :) |
14:31.40 | stadicon | anyway |
14:31.47 | stadicon | i'll give it a shot |
14:31.48 | maejrep | actually, I think there's still some confusion as to what each byte of the data actually represents |
14:31.56 | maejrep | but we get all the data |
14:32.23 | maejrep | like we haven't fully figured out how to translate the values into x/y coordinates for each section |
14:32.30 | maejrep | off to work, bye~ |
14:33.02 | stadicon | bye |
14:33.28 | stadicon | this is the pagee maejrep said, right? http://wiki.xda-developers.com/index.php?pagename=Raphael_Navi&redirectfrom=Raphael_I2C_Navi |
14:33.35 | stadicon | <NetRipper> |
14:34.04 | NetRipper | stadicon, yes, i think so |
14:39.03 | stadicon | sorry if this is a stupid question, but what's the way to research on this? |
14:39.18 | stadicon | i mean, is there any tool i can work to look about those bytes? |
14:44.30 | NetRipper | you can use haret for that |
14:44.52 | NetRipper | using haret you can trace memory addresses and see which memory addresses get changes and what their new values are |
14:53.36 | stadicon | i see |
14:53.37 | stadicon | thanks |
14:59.22 | NetRipper | stadicon, it's also useful to read back logs of the last few weeks (see topic).. just search for 'i2c' and 'trace'.. you'll find on how to do the traces... you can also refer to the memorymaps to see the locations of the i2c |
15:05.46 | *** part/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de) |
15:06.51 | stadicon | ok, i'll try that |
15:10.16 | NetRipper | hm android does boot on .27 (with the 48mhz, i guess 144khz was just too slow, and i even waited 15 mins) |
15:10.29 | NetRipper | but it's nearly not responding.. many timeouts |
15:10.31 | NetRipper | for mddi |
15:10.40 | NetRipper | msmfb_pan_display timeout |
15:30.53 | *** join/#htc-linux orux (n=jose@89.130.46.3) |
15:31.46 | *** join/#htc-linux zsircusr (n=drcordes@ip-77-25-197-255.web.vodafone.de) |
15:34.44 | *** part/#htc-linux mib_69lnyg (i=5144ce60@gateway/web/ajax/mibbit.com/x-97ed0fc401c4f9ce) |
15:39.27 | *** part/#htc-linux orux (n=jose@89.130.46.3) |
15:45.43 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
15:46.27 | *** join/#htc-linux orux (n=jose@89.130.46.3) |
15:46.33 | *** join/#htc-linux MethoS (n=lem@host-091-097-242-039.ewe-ip-backbone.de) |
16:03.20 | *** join/#htc-linux Zinbolic (n=chatzill@84.238.80.215) |
16:19.48 | maejrep[w] | [09:39:18] <stadicon> i mean, is there any tool i can work to look about those bytes? <-- if you can boot to linux, you can use a cross-compiled i2ctools package on the device to dump i2c chip data |
16:19.51 | maejrep[w] | that's what I did |
16:22.19 | AstainHellbring | morning maejrep[w] |
16:24.03 | NetRipper | maejrep[w], do you have something to add on this? http://netripper.pastebin.com/m20520658 |
16:31.43 | maejrep[w] | NetRipper: did the clock fmax change work ? |
16:31.49 | NetRipper | yes |
16:31.52 | maejrep[w] | nice |
16:32.01 | NetRipper | 50mhz was too high, so it simply didn't pick any frequency |
16:32.10 | NetRipper | the highest frequency in the array is 48mhz |
16:32.19 | maejrep[w] | i think it looks about right.. |
16:32.20 | NetRipper | if we'd add one for 50, it'd probably work |
16:32.22 | maejrep[w] | (the log) |
16:32.23 | NetRipper | ok |
16:35.02 | Balsat | Has the git for .27 been updatet? |
16:35.57 | NetRipper | almost |
16:36.42 | Balsat | Nice... can't wait ;-) |
16:38.05 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
16:38.30 | NetRipper | ok, it's there, http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.27 |
16:39.02 | NetRipper | i gtg home, bbl |
16:39.16 | Balsat | Nice job netripper |
16:39.26 | NetRipper | let me know if someone has problems compiling |
16:40.01 | Balsat | is it git checkout -b htc-msm-2.6.27 origin/htc-msm-2.6.27 do get that git |
16:41.19 | *** join/#htc-linux pH5 (n=ph5@e178202058.adsl.alicedsl.de) |
16:45.58 | maejrep[w] | yes |
16:48.28 | stadicon | maejrep: you mean to boot on linux on my host pc |
16:48.39 | stadicon | or boot linux on my diamond? |
16:48.40 | maejrep[w] | no |
16:48.42 | maejrep[w] | on the phone |
16:49.00 | stadicon | yes, i can boot android |
16:49.15 | maejrep[w] | as long as you can ssh in, that should be all you need |
16:49.18 | maejrep[w] | and the i2c tools |
16:49.49 | stadicon | so, i'll use a host pc and linux booted on my phone? |
16:49.58 | stadicon | i'll take a look. |
16:50.23 | stadicon | is i2c-msms.c the driver about the navi? |
16:50.32 | stadicon | *i2c-msm.c |
16:50.51 | maejrep[w] | yeah what I did was boot to linux, ssh in from my desktop pc, and run i2cdump from the sd card, while touching different areas of the navi |
16:50.56 | maejrep[w] | i2c-msm is the i2c bus driver |
16:51.00 | maejrep[w] | you should not change that |
16:51.20 | maejrep[w] | to implement the navi it will have to be an i2c "chip" driver |
16:51.24 | maejrep[w] | at address 0x62 |
16:51.42 | stadicon | i see. |
16:51.44 | maejrep[w] | added from board-htcraphael, in the i2c_devices section |
16:52.30 | stadicon | board-htcraphael and board-htcdiamond, right? |
16:52.40 | maejrep[w] | yes |
16:52.55 | stadicon | ok |
16:52.58 | maejrep[w] | look at microp-klt and microp-ksc.c |
16:53.09 | maejrep[w] | they implement i2c for the LEDs and Keyboard (raph) |
16:53.21 | stadicon | ok |
16:53.26 | stadicon | i'll use them as template |
16:55.52 | maejrep[w] | keep me updated on that if you don't mind :) I was actually planning to look at that in the near future, so if you get it knocked out, then I won't ;) |
16:56.29 | stadicon | yes, but consider that i am a noob at that :p |
16:56.53 | stadicon | but i think i can work on that :) |
16:57.21 | stadicon | i just hope you have enough patience for all my questions :) |
16:57.24 | Balsat | "make htcraphael_defconfig ARCH=arm".... Can't find default configuration "arch/arm/configs/htcraphael_defconfig.... shall i copy the config from the old kernel? |
17:00.01 | stadicon | i can't find microp-klt and microp-ksc |
17:03.59 | *** join/#htc-linux MethoS- (n=lem@host-091-097-242-049.ewe-ip-backbone.de) |
17:08.05 | stadicon | maejrep? |
17:11.35 | maejrep[w] | Balsat: did his commit not include defconfig? |
17:11.47 | maejrep[w] | stadicon: i think it was only committed to the .27 branch |
17:11.54 | maejrep[w] | I don't think it got committed to .25 |
17:12.01 | maejrep[w] | but the file that's in .27 should also work with .25 |
17:12.59 | stadicon | oh, then i'll download .27 git |
17:13.01 | stadicon | thanks |
17:14.06 | maejrep[w] | Balsat: the old kernel config should still work for .27, after disabling ADSP and RPC, and renaming ARCH_MSM7X00 to ARCH_MSM |
17:14.27 | NetRipper | Balsat, the file should be there |
17:15.25 | *** join/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de) |
17:15.43 | NetRipper | Balsat, if you had the git clone already before.. did you do a git pull before you did the -b? |
17:18.29 | Balsat | No there is no defconfig in .27... trying to use the one from .25 |
17:18.32 | *** join/#htc-linux ewasx (n=armin@5-157.surfsnel.dsl.internl.net) |
17:18.51 | NetRipper | the defconfig is there. |
17:18.55 | NetRipper | make sure you have the latest version |
17:19.00 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commitdiff;h=67654de7d2fb753cce73334196404d4cc092be24 |
17:19.03 | NetRipper | first file |
17:19.36 | stadicon | i duplicated my previous kernel directory and i switched to htc-msm-2.6.27 but still there is no microp-ktl.c file |
17:20.28 | stadicon | is it a problem that i switched from a 2.6.25 branch? |
17:20.37 | NetRipper | no it shouldn't |
17:21.24 | stadicon | strange. |
17:21.28 | stadicon | where are those files? |
17:21.31 | NetRipper | do a git pull |
17:22.40 | stadicon | oh, ok |
17:22.42 | stadicon | great :) |
17:22.44 | stadicon | it worked |
17:22.46 | NetRipper | ok |
17:22.51 | NetRipper | Balsat, do a git pull as well |
17:23.08 | stadicon | i don't remember me doing a git pull on the previous branch |
17:23.14 | stadicon | was that wrong? |
17:23.22 | NetRipper | git pull retrieves the latest changes from the git |
17:23.41 | NetRipper | git checkout simply changes branches, it doesn't retrieve new data |
17:23.42 | stadicon | yes, but isn't it "branch specific"? |
17:23.54 | NetRipper | no it's not |
17:24.06 | stadicon | oh. |
17:24.13 | NetRipper | at least not to my experience |
17:24.34 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
17:24.36 | stadicon | ok, i'll check a git pull on my 2.6.25 to see if those files are downloaded their. |
17:24.43 | stadicon | meanwhile, i am working on i2ctools |
17:24.46 | NetRipper | ok |
17:25.01 | stadicon | can you remind me what should be my diamond ip? |
17:25.16 | NetRipper | 192.168.0.206 |
17:25.26 | NetRipper | you can use the angstrom initrd for usb |
17:25.33 | NetRipper | you need to set 192.168.0.200 on your pc |
17:26.00 | stadicon | i've just booted the kernel |
17:26.07 | stadicon | i didn't even load android |
17:26.15 | NetRipper | http://www.netripper.com/raphael/20081204-01_raph_diam_angstrom_usb/ |
17:26.26 | NetRipper | the default.txt and zImage are outdated |
17:27.00 | stadicon | ok, i only need initrd |
17:27.03 | NetRipper | or you can use the android initrd, but that has telnetd, not ssh (which means you cannot scp to your device) |
17:28.02 | NetRipper | dinnertime, bbl :) |
17:28.11 | stadicon | have a nice dinner :) |
17:35.58 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
17:36.02 | Untouchab1e | Good Evening all :D |
17:37.17 | pH5 | evening |
17:38.47 | exco | good evening |
17:41.33 | stadicon | hi |
17:45.24 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-213-62.web.vodafone.de) |
17:45.50 | cr2 | hi |
17:46.41 | cr2 | finally got rid of windows on nc10 :) |
17:47.27 | exco | I guess you put Mac OS X :-P |
17:47.32 | exco | on it |
17:47.33 | pH5 | hi cr2, I'm so envious now. |
17:47.36 | cr2 | linux is so much faster, why do people still use windows ?! |
17:48.14 | cr2 | don't know to fast is the atom cpu for crosscompiling |
17:49.09 | cr2 | pH5: there is no DSL here, and umts comes only from vodafone ;) so i had no other chance |
17:49.35 | Balsat | git pull did the magic for me ;-) |
17:50.18 | pH5 | beware, that man is reading minds. |
17:50.26 | AstainHellbring | anyone tried crosscompiling on atom yet? |
17:51.46 | cr2 | lol |
17:51.48 | marex | AstainHellbring, what is so special about atom ? |
17:51.55 | cr2 | AstainHellbring: i'll try |
17:52.06 | cr2 | marex: that's a slow cpu ? |
17:52.07 | AstainHellbring | dunno 100% sure marex just that its a low power cpu |
17:52.11 | AstainHellbring | and its 1.6ghz |
17:52.21 | marex | Abracadabra, so what ? |
17:52.32 | marex | AstainHellbring, ^ |
17:52.38 | cr2 | pxa270 is 624MHz, but you don't want to crosscompile there |
17:52.58 | marex | cr2, hi, long time no bla...errr, long time no see :) |
17:53.17 | cr2 | marex: yeah, i still can't resume on n560 ;) |
17:53.31 | marex | cr2, I was compiling something on pxa27x at 416Mhz with 32meggs of ram ... :) |
17:53.39 | cr2 | marex: and there is no sound support too... |
17:54.01 | marex | cr2, ah... I see you are pretty lazy about fixing the asoc driver :) |
17:54.06 | cr2 | marex: pull the oe tree, and compile :) |
17:54.10 | pH5 | marex: should have overclocked to 624 ;) |
17:54.10 | cr2 | LOL |
17:55.03 | marex | pH5, I tried, but it stopped responding after a few seconds |
17:55.12 | marex | it held at 520 though ;) |
17:55.23 | marex | cr2, :D |
17:55.48 | exco | so what distro did you put on your NC 10 - if I may ask, cr2 |
17:58.28 | cr2 | exco: debian lenny |
17:59.35 | cr2 | exco: and umts is configured manually. linux is not that user-friendly yet. |
18:00.33 | cr2 | pH5: i would have dumped the local phone firmware, but don't know how :) |
18:01.03 | AstainHellbring | hopes crosscompile works well on atom as thats what I was gonna use my eee for |
18:01.25 | exco | couldn't you also do it the gui way with network manager applet? (well if you were a gui guy) |
18:01.29 | cr2 | AstainHellbring: it's a x86 cpu, what can go wrong ? |
18:01.44 | AstainHellbring | yah true just hope that it works well and not just works... |
18:01.48 | radem205 | hey exco |
18:01.54 | exco | if I think I have the correct gpio for an action (e.g. button press) can I execute it with haret to check if I'm right? |
18:01.59 | exco | hi radem205 |
18:02.22 | radem205 | I read that you could establish a data connection in Android, is that right? |
18:02.28 | exco | yes |
18:02.33 | pH5 | AstainHellbring: I wonder if that hyperthreading works for parallel compiling. my single core celeron 220 wasn't all that fast. |
18:02.34 | cr2 | exco: i've tried , but it's too modem-oriented. a more fine-tuned gprs & such gui should look different |
18:02.51 | Balsat | The .27 kernel is working with Android, but damn it is slow... The kernel is about 2 min to startup, and i can't get any reation in Android |
18:03.17 | radem205 | Ok, I think it's depend on my provider because I can't establish a data connection |
18:03.21 | exco | cr2: it should - but 0.7 is better than the versions before ;-) |
18:03.47 | pH5 | cr2: how is the module connected? pci-express? |
18:03.56 | exco | radem205: imfloflo also couldn't get it to work (I even sent him the files straight from my SD card) |
18:04.10 | radem205 | ok, so I'll wait :) |
18:04.13 | radem205 | Do you have experience with keymapping exco? |
18:04.30 | cr2 | exco: i'm familiar with the pppd internals for more than a decade, so that may be a problem |
18:05.28 | cr2 | pH5: they say it's a mini-pci card, but linux sees it as an usb modem /dev/ttyACM0 |
18:05.36 | exco | no - but I'm trying to learn how to do it (well I can trace the easy gpio's - I think and afair now I need to assign that to some function to check if I'm right) |
18:05.38 | radem205 | Because probably the only thing we have to do on the polaris is assigning the buttons right |
18:06.02 | radem205 | rogro had already done that, but some buttons have the same gpio number |
18:06.03 | cr2 | Bus 005 Device 004: ID 0ac8:c326 Z-Star Microelectronics Corp. |
18:06.04 | cr2 | Bus 005 Device 003: ID 04e8:6773 Samsung Electronics Co., Ltd |
18:06.06 | cr2 | Bus 005 Device 002: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technolo |
18:06.25 | radem205 | so we have to figure out how egpio (extended gpio) works to let the buttons work |
18:06.25 | cr2 | "Samsung" is the modem |
18:06.47 | exco | radem205: yes and someone explained it the other day how it works (some matrix) but I can't find it |
18:07.33 | radem205 | dubbeld00 said something about egpio but it isn't enough to know how it works |
18:07.35 | cr2 | P: Vendor=04e8 ProdID=6773 Rev= 0.01 |
18:07.37 | cr2 | S: Manufacturer=SAMSUNG Electronics CO.,Ltd. |
18:07.39 | cr2 | S: Product=SAMSUNG HSPA Modem |
18:07.41 | exco | Can one emulate a button press using haretconsole ? |
18:07.44 | Balsat | I got alot of "W/SurfaceComposerClient( 66): lock_layer timed out (is the CPU pegged?) layer=0, lcblk=0x42560020, state=00000042 (was 00000042)" in Android logcat |
18:08.05 | cr2 | exco: no, but it'd be easy to create such command |
18:08.18 | maejrep[w] | Balsat: you probably don't have the framebuffer working |
18:08.26 | cr2 | SendMessage() |
18:08.34 | maejrep[w] | if you are using htc_fb_console, it will put in a 1s delay after every printk |
18:08.46 | exco | so how do you check if the gpio you guessed is right, cr2? |
18:08.48 | cr2 | maejrep[w]: now i can checkout the kernel source :) |
18:09.00 | cr2 | exco: where ? |
18:09.19 | radem205 | When you use haret to see which button has which gpio you find that some buttons use the same gpio, but I think we have to figure out what irq is using when you press a button |
18:09.48 | exco | that shouldn't be too hard, radem205 |
18:09.58 | maejrep[w] | what device? |
18:10.04 | cr2 | radem205: you need to have some idea how the "keyoard" is organized |
18:10.28 | maejrep[w] | if its a gpio matrix, you should see 2 gpios per key |
18:10.44 | exco | maejrep[w]: Polaris |
18:11.41 | *** part/#htc-linux orux (n=jose@89.130.46.3) |
18:13.40 | radem205 | maejrep[w]: Could you explain this line (haret output): "in1: in1-24(216)=0" |
18:14.02 | radem205 | Rogro said that this line becomes "1" when pressing the call or hangup button |
18:15.13 | radem205 | Exco: Did you get an output like this: "002.269 GPIOS GPGDAT: GPG3(195)=0" when you use haret to find the gpio? |
18:16.03 | exco | 195 is left according to my notes |
18:16.32 | tmzt | stadicon: what device do you have, why do you need i2ctools? |
18:17.03 | radem205 | the numbers are wrong I know, but do you have such output? |
18:18.05 | exco | radem205: yes |
18:18.58 | exco | what do you mean by "the numbers are wrong", radem205 |
18:19.10 | tmzt | can we support all frequencies and use a table only for exceptions to the formula? |
18:19.25 | radem205 | I mean that the number in my example are wrong and doesn't related to the polaris |
18:19.39 | radem205 | do you have the complete output? If yes, maybe it's smart to post it on xda, including notes which button is pressed each time |
18:19.43 | radem205 | can you do that? |
18:20.34 | tmzt | htcraphael-panel.c should only be included for MACH_RAPH* and MACH_DIAM* right, I'd rather get reports it works than reports it doesn't |
18:20.48 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
18:21.04 | exco | radem205: I haven't done all buttons - because on some there's so much output I don't know what is the right number(s) |
18:21.36 | exco | that's why I was asking how to verify the findings |
18:22.17 | radem205 | have you looked here: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation |
18:24.32 | exco | radem205: yes |
18:24.54 | exco | radem205: does that help someone if I put it like this: |
18:24.56 | exco | * select/enterin3: in3-22(278)=0/1 |
18:24.57 | exco | * SD card presentin3: in3-26(282)=1 |
18:24.57 | exco | * SD card absentin3: in3-26(282)=0 |
18:25.01 | exco | on the wiki or somewhere |
18:26.11 | *** join/#htc-linux cr2_ (n=cr2@ip-90-187-213-218.web.vodafone.de) |
18:29.02 | radem205 | I don't know, it can't hurt I think |
18:30.28 | radem205 | could you upload the complete output so everyone can see it and maybe some can working on it? |
18:37.13 | exco | radem205: put it here http://wiki.xda-developers.com/index.php?pagename=Polaris_GPIO and will add the missing buttons once I have them / and can try to watch other events on request. |
18:39.01 | radem205 | good job! |
18:39.03 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-c052ab81d15cd7ba) |
18:39.10 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
18:39.36 | exco | if you tell me how to convert it to a usable form I'll do that as well (maybe faster if someone does it who knows what he is doing) |
18:39.54 | maejrep[w] | radem205: that means that pin 24 of gpio bank 1 went from high (enabled/has voltage on the line) to low (0 voltage, like turning off a switch) |
18:42.03 | radem205 | maejrep[w]: thank you! What you could see here http://wiki.xda-developers.com/index.php?pagename=Polaris_GPIO is that we have a call/hangup button with the same gpio number. Do you know how we can get these buttons work seperatly? |
18:42.05 | maejrep[w] | radem205: see http://wiki.xda-developers.com/index.php?pagename=Raphael_GPIO for an example |
18:42.32 | maejrep[w] | radem205: is it like the raphael where the area of the buttons is capacitive touch sensitive? |
18:42.48 | maejrep[w] | ie, just by touching it, does an led turn on or something to that effect? |
18:43.04 | maejrep[w] | or if in "watch gpios", does anything happen just by touching lightly? also in "wirq" |
18:43.41 | radem205 | as far as I know it isn't capacitive touch sensitive. |
18:44.28 | maejrep[w] | are there any other buttons that are like that? |
18:44.38 | exco | maejrep[w]: in watch gpios nothing is happening when touching it lightly |
18:45.15 | radem205 | the volume slide button has also one gpio. When mapping this gpio in android only volume up works |
18:45.19 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
18:45.20 | exco | maejrep[w]: yes - volume up/down, voicedial, wheel cw/ccw |
18:45.28 | maejrep[w] | ok, try: wirq 1 (find anything that is happening too often, and ignore that bit with: ibit irqs <number that's in parentheses> |
18:45.35 | maejrep[w] | then do: joinlist traces gpios |
18:45.47 | radem205 | can you do this exco? |
18:45.49 | maejrep[w] | and do wirq 1 again, and ibit traces <chatty numbers> |
18:46.09 | maejrep[w] | then when you're satisified that you're ignoring the uninteresting bits, do: wirq 5 |
18:46.14 | maejrep[w] | and try each button |
18:46.19 | maejrep[w] | and see if it changes |
18:46.19 | exco | 000.994 IRQS IRQ0: USB_OTG(15)=1 |
18:46.20 | exco | <PROTECTED> |
18:46.30 | maejrep[w] | ibit IRQS 15 |
18:48.30 | maejrep[w] | radem205: are the other buttons the same also? like OK + Win key / IE + Radio? |
18:49.11 | radem205 | these buttons have different gpio numbers |
18:49.25 | exco | radem do you also have a Polaris at hand? |
18:50.15 | radem205 | yes, but unfortunately I can't start haretconsole |
18:50.19 | exco | it'll take me a minute - deactivating the button actions real quick with aebuttons to make the tracing easier |
18:50.33 | radem205 | ok, take it easy :) |
18:50.37 | exco | radem205: on win? |
18:50.51 | maejrep[w] | radem205: you can also just telnet to the ip, port 9999 |
18:51.12 | maejrep[w] | ie if you're ocnnected to activesync: telnet 169.254.2.1 9999 |
18:51.48 | radem205 | ok I 'll give it a try |
18:52.57 | exco | wow I thought you had to setup usb networking to be able to do that |
18:54.28 | exco | I wonder why noone ever wrote a tutorial on button tracing (bet the same question have been here over and over when you look at how many HTC/other devices are at least partly working with some Linux now) |
18:55.03 | radem205 | maejrep[w]: what do you mean with chatty numbers? |
18:57.08 | exco | after joinlist traces gpios I get irgs and gpios at the same time (was wondering that earlier if I had to do separate traces on irq/gpio) |
18:57.31 | tmzt | non-MD/NS, what is this? |
18:57.47 | exco | radem205: I suppose the stuff that comes up without you doing anything/spam so to speak |
18:58.23 | NetRipper | i'd really suggest using haretconsole |
18:58.26 | NetRipper | instead of telnet |
18:58.50 | exco | ok I have it quiet now |
18:59.12 | radem205 | ok nice |
19:00.01 | exco | no touch-sensitive buttons (well the wheel - sort of ;-) ), maejrep[w] |
19:00.44 | radem205 | do you have some interesting output exco? |
19:01.12 | *** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net) |
19:01.14 | tcccp | re |
19:02.09 | exco | wheel cw http://pastebin.com/d77949d76 |
19:03.01 | exco | wheel ccw http://pastebin.com/d3975bbdb |
19:05.37 | radem205 | Exco: http://forum.xda-developers.com/showpost.php?p=3202836&postcount=425 |
19:05.45 | exco | looks astonishingly alike, or do I just not see it? |
19:05.48 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
19:06.23 | radem205 | yes, the only thing what is different is the line "in1: in1-20(212)=1 @~800192c0" |
19:08.04 | tmzt | so the arm9 checks those bits (are they in smem) and enables the clock if set? what are you calling a-clocks and b-clocks? |
19:08.39 | radem205 | it look likes Rogro has figure it out |
19:08.56 | exco | so that means obsolete work I guess .... |
19:10.00 | tmzt | exco: it appears the x86 version have a particular setting /init.rc that enables ppp instead of rmnet/qmi |
19:10.07 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
19:10.10 | tmzt | this should work on arm also for wince amss's |
19:10.21 | radem205 | I think it is good that you let see your findings to Rogro, because maybe he can optimized the code |
19:11.28 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B033CD6.dip.t-dialin.net) |
19:11.34 | exco | tmzt: I don't really get what you're talking about (sorry) |
19:12.05 | tmzt | what you were talking with cr2 about, though I couldn't follow it very well |
19:12.36 | *** join/#htc-linux DasFx (n=John@5354790B.cable.casema.nl) |
19:14.05 | exco | that may very well be because I don't know what I'm talking about :-( |
19:15.03 | tmzt | you asked about ppp didn't you? |
19:16.11 | exco | well I was asking if it could be done through a gui (shame on me) - but just out of curiosity |
19:17.33 | tmzt | yeah, there's a setting in /init.rc I think enables it through the gui, there is a also a program for android that can enable/disable ppp with the dzo scripts |
19:17.52 | exco | can i list the gpios/irqs currently ignored with ibit |
19:18.58 | tmzt | check your logs |
19:19.19 | tmzt | unfortunately I don't think you can/know how |
19:19.42 | exco | exiting haretconsole and connecting again resets it? |
19:20.22 | tmzt | I think you have to close haret.exe itself, |
19:20.37 | tmzt | or you want wbit 1..2000 or something like that |
19:22.04 | exco | you're right - you have to close haret |
19:25.12 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
19:29.41 | *** join/#htc-linux stefan_schmidt_ (n=stefan@p5B037D9D.dip.t-dialin.net) |
19:31.01 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-143-216.web.vodafone.de) |
19:34.06 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d179.pool.einsundeins.de) |
19:35.35 | *** join/#htc-linux lastik_ (n=eraser@80.92.96.29) |
19:36.02 | exco | to be honest ... I can't tell any difference between wheel cw & ccw (well at least it can look totally the same) |
19:36.05 | exco | http://pastebin.com/d382984ef |
19:36.18 | *** join/#htc-linux Sti_0239 (n=Where_is@88.205-65-87.adsl-dyn.isp.belgacom.be) |
19:40.31 | radem205 | exco: It's vice versa, cw: in1-20 | in 1-15 and ccw: in1-15 | in1-20 |
19:42.26 | exco | radem205: no - it's just a part of it |
19:42.36 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
19:43.58 | exco | oh - you're right |
19:48.13 | exco | radem205: no you're wrong in1-20=1 in1-15=1 in1-20=0 in1-15=0 is a circle |
19:48.57 | radem205 | yes I know I was wrong :) |
19:49.47 | exco | still - if you turn left/right/left/right/left/right |
19:50.10 | radem205 | I think I was right :) |
19:51.15 | exco | the numbers change in1-20=0/in1-20=1/in1-20=0/in1-20=1 or the same with one of the other 3 available possibilities |
19:51.59 | radem205 | when you look at the "0" and "1" in the back of the line you can see that the 20 and 15 are vice versa |
19:52.08 | cr2 | NetRipper: have you applied the .27 patch ? |
19:53.11 | exco | radem205: yes, but if those four sates form a circle - it doesn't matter |
19:54.39 | *** part/#htc-linux stadicon (n=liberost@79.107.28.155) |
19:55.37 | radem205 | hmm, when you have twice "1" and twice "0" and the in1-15 and in1-20 are vice versa it does make sense |
19:56.32 | exco | the software always knows the current state in1-20=0 for example? |
19:56.41 | exco | then I know how it work |
19:56.43 | exco | 's |
19:57.04 | exco | even if rogro already knows how to do it - it was still interesting finding that out |
19:57.34 | radem205 | haha sure :) |
19:58.16 | radem205 | but we can inform rogro about our findings and maybe he can optimized his code |
19:58.33 | dcordes | NetRipper: what's needed on the host side to use the usbnet? |
19:59.08 | dcordes | does raphael hang during boot while it is charging? |
19:59.16 | dcordes | (or diam) |
19:59.40 | cr2 | hi dcordes |
19:59.44 | dcordes | hi |
19:59.48 | cr2 | dcordes: 100% linux now |
19:59.55 | dcordes | I've seen it in the log. nice |
20:00.24 | cr2 | there is one annoying samsung misfeature |
20:00.50 | cr2 | if you loose the umts link, the modem drops your pin |
20:00.51 | dcordes | did you mail laforge? |
20:01.05 | dcordes | ok so modem works too |
20:01.19 | dcordes | I would disable the pin in that case |
20:01.24 | *** join/#htc-linux timebomb (n=tb@e176115185.adsl.alicedsl.de) |
20:01.26 | cr2 | no, i found the description by some polish guys |
20:01.42 | cr2 | dcordes: hmm, how do you think i'm logged on ? |
20:02.55 | cr2 | i'm downloading everything possible now. flatrate should be used :) |
20:04.42 | exco | radem205: you can point him to the wiki page if you like (I'll update that in a bit) |
20:08.53 | tmzt | cr2: are you using fso-frameworkd? |
20:11.17 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
20:13.25 | radem205 | ok I'll do that |
20:13.33 | radem205 | when do you update the wiki? |
20:14.18 | radem205 | because I think the latest developments are interesting for him |
20:14.31 | dcordes | cr2: kovsky dies after "trout_pwrsink_set:STUB!" messages while charging during boot |
20:17.18 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
20:21.09 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
20:21.42 | radem205 | thanks Exco (good job!) |
20:22.38 | exco | do you think that's right what I wrote about the wheel? |
20:23.39 | cr2 | dcordes_: what is the value of CROSS_COMPILE= for the kernel ? |
20:24.00 | cr2 | i've already forgotten how to compile the kernel :) |
20:24.01 | NetRipper | dcordes_, make sure you boot with the usb cable connected, and with usb in "activesync" mode (you know when you insert the usb cable, you get a popup for activesync/disk drive/internet sharing) |
20:24.18 | dcordes_ | that doesn't work. kovsky freezes with usb power connected. |
20:24.23 | *** join/#htc-linux utter0192 (n=dk@92.12.9.180) |
20:24.34 | radem205 | yes I think it's good! Unfortunatly we don't know better :( |
20:24.35 | NetRipper | dcordes_, also try disabling 'advanced networking' in activesync settings on your phone.. also helps |
20:24.48 | dcordes_ | cr2: the path to the toolchain prefix |
20:24.55 | cr2 | bash: make: command not found |
20:25.11 | NetRipper | lol install gcc, make, autoconf, etc |
20:25.44 | dcordes_ | build-essential |
20:25.49 | cr2 | standard install is a bit strange |
20:26.02 | cr2 | i've installed kde on top of it |
20:27.49 | *** join/#htc-linux JotaeLe (n=basura@62.57.224.133.dyn.user.ono.com) |
20:28.06 | JotaeLe | Hi all |
20:29.06 | cr2 | hm. the atom is certainly not the amd64. but with make -j 3 it's bearable |
20:29.44 | cr2 | cegcc svn is 4.3.2 now ? |
20:30.32 | cr2 | hehe. the fans switched on |
20:31.40 | dcordes_ | crap I won't get the usb console until I fix the power bug |
20:34.10 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
20:34.56 | *** join/#htc-linux Xime (n=xime@bankize.net) |
20:34.59 | *** join/#htc-linux MethoS-- (n=lem@dyndsl-085-016-166-025.ewe-ip-backbone.de) |
20:35.01 | NetRipper | dcordes_, if you soft reset the phone.. dont connect the usb cable.. see if it boots then (without ever connecting usb) |
20:35.04 | dcordes_ | dzo: did you have a look at kaiser wifi? |
20:35.51 | dcordes_ | dzo: I will try building the driver in htc-vogue |
20:36.32 | cr2 | dcordes_: vogue does not have wifi ? |
20:36.32 | dcordes_ | NetRipper: I already know it's the charging that causes the freeze. |
20:36.36 | NetRipper | dcordes_, ok |
20:36.46 | dcordes_ | cr2: htc-vogue branch |
20:36.51 | dcordes_ | kaiser is in there |
20:37.13 | NetRipper | you can set it not to charge when the usb cable is connected, maybe that helps you get into a shell? |
20:37.20 | dcordes_ | good idea |
20:38.22 | NetRipper | you should also verify all memory addresses in msm_iomap.h.. wrong mappings may also cause weird behaviour |
20:38.24 | Untouchab1e | Good evening all |
20:38.27 | Untouchab1e | how's it going? :) |
20:38.39 | maejrep[w] | where does it freeze dcordes_ ? |
20:38.58 | NetRipper | at the end - during the stub messages |
20:39.22 | maejrep[w] | that's where I was getting freezes too |
20:39.25 | dcordes_ | maejrep[w]: after mmc, rtc, trout_pwrsink_set:STUB! is printed a few times. then it freezes |
20:39.32 | maejrep[w] | but that was resolved with the activesync mode |
20:39.35 | maejrep[w] | for me |
20:39.38 | exco | cr2: earlier you said I need to find power gpios and vregs to get wifi working on Polaris - I think I have the gpios - how do I go about finding vregs? |
20:39.42 | maejrep[w] | dcordes_: .25 or .27? |
20:39.51 | dcordes_ | .27 from linuxtogo |
20:40.04 | maejrep[w] | dcordes_: with HTCRAPHAEL mach type? |
20:40.11 | NetRipper | hm.. stupid idea perhaps.. is it not possible to set the kernel in some sort of 'single threaded mode', so that devices are inited in sequence which would allow to debug easier |
20:40.21 | dcordes_ | sorry, I didn't copy the new kernel yet. still using the patch .27 kernel |
20:40.28 | dcordes_ | yes, htcraphael |
20:40.40 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbff04d.pool.einsundeins.de) |
20:40.49 | maejrep[w] | NetRipper: init=/sbin/bb or something like that? |
20:41.03 | cr2 | exco: do you have the spl ? |
20:41.05 | maejrep[w] | not sure how to force init 1 (single user mode) |
20:41.36 | NetRipper | single user mode is not the same as single threaded i think |
20:41.36 | cr2 | maejrep[w]: i'm ready to compile the kernel |
20:41.41 | exco | dcordes_: you said here: http://forum.xda-developers.com/showpost.php?p=2699355&postcount=413 you didn't know the kaiser/polaris wifi base address - did that turn up by now? and if not - where do I get started |
20:42.07 | exco | cr2 spl? |
20:42.08 | NetRipper | to force init 1, add 'single' to the cmd, but i dont think that's it.. |
20:42.22 | *** join/#htc-linux miknix (n=miknix@sjcc176x121.sjccnet.com) |
20:42.27 | cr2 | exco: pwf polspl 0x0 0x100000 |
20:42.46 | maejrep[w] | ah |
20:43.07 | cr2 | exco: get power+sdio working first |
20:43.37 | cr2 | hmm. atom is not that bad |
20:43.51 | exco | I don't know what "pwf polspl 0x0 0x100000" I did but it doesn't give any output |
20:44.06 | cr2 | exco: in haret |
20:44.15 | exco | cr2: yes |
20:44.42 | maejrep[w] | exco: it writes a file to the same directory as haret.exe |
20:44.46 | cr2 | maejrep[w]: the raph800 lcd init looks like a mix of epson+toshiba. i'm confused |
20:45.01 | maejrep[w] | cr2: and "display 2" tells me HITACHI |
20:45.03 | maejrep[w] | wtf?!!?! |
20:45.04 | maejrep[w] | :p |
20:45.30 | exco | you want that file, maejrep[w], cr2? |
20:45.43 | maejrep[w] | cr2 is better equipped to make use of it :) |
20:47.13 | cr2 | maejrep[w]: ok. |
20:47.13 | cr2 | ar.c:(.text+0xa82): undefined reference to `yyparse' |
20:47.14 | cr2 | hehe. bison is missing |
20:47.15 | cr2 | how do i install all possible debian packages ? |
20:47.15 | cr2 | tmzt: you are the debian guy |
20:47.39 | dcordes_ | maejrep[w]: on the kovsky, keyboard slideout gpio seems to be mapping to card detect |
20:48.03 | dcordes_ | I just slided out the keyboard and msm_sdcc initialized the card |
20:48.09 | cr2 | maejrep[w]: hitachi is id=5 |
20:49.22 | cr2 | dcordes_: i've managed to get inet access on the raph too |
20:49.35 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
20:49.45 | dcordes_ | cr2: what was the problem? |
20:49.47 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
20:49.49 | AstainHellbring | cr2 using raphs inet or usb? |
20:50.14 | exco | cr2: you want it? what is it? what is it good for? |
20:50.34 | cr2 | AstainHellbring: nc10 builtin usb |
20:50.47 | cr2 | exco: yes, gzip it and put somewhere |
20:51.00 | dcordes_ | cr2: did the debian shipped rndis modules work? |
20:51.10 | cr2 | dcordes_: the problem was that the wince is not user-friendly. |
20:51.24 | *** join/#htc-linux MethoS (n=lem@dyndsl-085-016-166-211.ewe-ip-backbone.de) |
20:52.16 | cr2 | <4>[ 0.720091] ulpi: write 0x1d to 0x0d |
20:52.17 | cr2 | <4>[ 0.720305] ulpi: write 0x1d to 0x10 |
20:52.33 | dcordes_ | yea the configuration is not that intuitive |
20:52.37 | cr2 | maejrep[w]: it is not clear if we really need it |
20:53.36 | dcordes_ | maejrep: can I use i2c-tools instead of haret to sort out the keycodes? |
20:54.03 | exco | cr2: www.excogitation.de/Android_on_Polaris/polspl.gz |
20:55.01 | *** join/#htc-linux orux (n=jose@89.130.46.3) |
20:56.27 | cr2 | exco: got it |
20:57.45 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-167-033.ewe-ip-backbone.de) |
20:57.52 | exco | cr2: get power+sdio working first - well sdio should be done soon - about power - where to start and shouldn't that be the same as on kaiser? |
20:58.23 | *** join/#htc-linux pl_levy (n=chatzill@aasa224.neoplus.adsl.tpnet.pl) |
21:01.34 | exco | the wifi sounded just like it wasn't too much work - and would be so awesome (maybe not) |
21:02.09 | *** part/#htc-linux orux (n=jose@89.130.46.3) |
21:03.38 | dcordes_ | exco: which kernel do you use? |
21:04.40 | exco | rogros |
21:04.52 | dcordes_ | you should use the htc-vogue kernel |
21:05.10 | exco | the last time I tried - it wasn't booting on Polaris |
21:05.32 | dcordes_ | did you build with polaris or kaiser defconfig? |
21:05.54 | exco | rogro is using that branch afaik and making the neccessary changes - hope he pushes ist sometime soon |
21:07.51 | dcordes_ | ok then. I thought about the old rogro kernel. did he put the patches? |
21:08.32 | exco | haven't seen any |
21:08.47 | exco | put you mean apply? |
21:09.35 | dcordes_ | publish/provide/upload |
21:09.55 | exco | ah - ok - then I haven't seen any - so no |
21:10.38 | dcordes_ | exco: is there an active thread where you discuss the polaris related things? |
21:10.49 | exco | but he was talking in here on how to best setup ltg so it's easy to build for kaiser/vogue/polaris |
21:11.19 | exco | niki should also be considered I guess (since it's so similar) |
21:11.31 | exco | dcordes_: http://forum.xda-developers.com/showthread.php?p=3202836#post3202836 |
21:11.54 | exco | I'm keeping the wiki up to date http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux |
21:14.37 | dcordes_ | ok thanks |
21:27.19 | cr2 | omg. even awk is not installed |
21:29.11 | cr2 | maejrep[w]: i'm thinking about the 7param formula, and it seems to me that the 48MHz clock is 32MHz in reality |
21:30.29 | cr2 | 12*16=192 |
21:31.48 | cr2 | 192*2=384 |
21:32.29 | dcordes_ | cr2: how can I trace kovsky IRQ ? |
21:33.27 | cr2 | dcordes_: gpio irq , or msm irq ? |
21:37.32 | dcordes_ | cr2: I see no irqs when I run wirq |
21:37.40 | exco | did anybody here try neocore on a msm7200 device yet (or does someone have the apk for me?) |
21:37.54 | dcordes_ | exco: what's that? |
21:37.57 | cr2 | dcordes_: do you use the 0x9* address or 0xb* ? |
21:38.13 | exco | some 3d benchmark |
21:38.24 | cr2 | glxgears :) |
21:38.29 | dcordes_ | cr2: I set nothing extra |
21:38.38 | dcordes_ | http://wiki.xda-developers.com/index.php?pagename=Kovsky_GPIO updated |
21:38.51 | cr2 | dcordes_: you had the same problem with i2c |
21:38.54 | dcordes_ | cr2: I assumed 7201A is in git :> |
21:39.19 | dcordes_ | haretconsole git |
21:39.21 | cr2 | 192*4=768 |
21:39.34 | cr2 | integer arithmetic is fun |
21:39.44 | dcordes_ | yay |
21:40.42 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
21:44.44 | cr2 | marex: do you still have n560 ? |
21:45.03 | *** join/#htc-linux zycho_ (n=zycho@a89-183-89-249.net-htp.de) |
21:45.22 | marex | cr2, n560 yes, time no ;) |
21:46.10 | cr2 | maejrep[w]: my sick integer arithmetic brain thinks that the SD clock is originating from 768MHz clock. probably coming from some dark arm9 internals |
21:47.05 | cr2 | marex: send it to kiozen |
21:47.33 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-167742f2e2ab5215) |
21:48.20 | marex | cr2, send what ? |
21:50.16 | cr2 | n560 |
21:52.26 | dcordes_ | what is a/m in Raphael_GPIO ? |
21:52.41 | tmzt | apt-get install build-essential on ubuntu at least |
21:52.43 | cr2 | arm11 arm9 |
21:52.52 | cr2 | a(pplication) m(odem) |
21:53.02 | cr2 | cf. A2M |
21:53.11 | marex | cr2, are you serious ? |
21:53.25 | dcordes_ | cr2: aka owner bit? |
21:54.09 | dcordes_ | how can the a/m value be 4,0 ? |
21:54.24 | cr2 | dcordes_: yes, the owner |
21:54.38 | cr2 | 4,0 is a data entry bug |
21:54.47 | cr2 | it'd be in the alt column |
21:54.59 | dcordes_ | k |
21:55.06 | cr2 | 4 is some mixture of drvstr+alt+pull |
21:55.21 | tmzt | you get awk/bison cr2? |
21:55.34 | cr2 | which i need to decipher too ;) |
21:55.40 | cr2 | tmzt: apt-get |
21:55.54 | cr2 | marex: sure |
21:56.07 | marex | cr2, no |
21:56.38 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
21:56.43 | cr2 | marex: we will make some brain surgery on it. |
21:57.00 | cr2 | marex: we want to finish the n560 support |
21:58.43 | cr2 | marex: so we want to buy a device, which we can destroy in the process . |
22:01.36 | marex | cr2, so ... what ? |
22:13.29 | tmzt | cr2: do you know what a-clock and b-clock refer to? |
22:15.17 | cr2 | tmzt: i use such name to separate the 2 value (MD/NS) and 1 value (0xa|xxx) clocks |
22:16.13 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
22:16.20 | cr2 | exco: what do you know about the polaris cpld ? does it have the same functions / bits as kaiser ? |
22:17.49 | cr2 | polaris has BT_UART1_MODE, H2W_UART1_MODE and BT_H2W_MODE |
22:18.01 | cr2 | is it the same as on g1 ? |
22:18.49 | cr2 | wifi is sdc1, sd is sdc2 |
22:23.37 | cr2 | hehe. pola100 has 0xa2c for pmdh clk |
22:27.24 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
22:27.42 | exco | cr2: do we have a console in android so I can check? |
22:28.15 | cr2 | exco: i have never used android. |
22:31.49 | *** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1) |
22:34.11 | cr2 | exco: pola100 uses vreg(1,... for wifi and vreg(2,... for sd |
22:34.43 | cr2 | it's tge same as g1 i think |
22:35.23 | infernixx | is the kaiser sd driver stable yet? |
22:36.05 | infernixx | i havent kept track of the efforts to get it working in PIO mode |
22:36.06 | maejrep[w] | cr2: 768MHz? how? |
22:37.27 | cr2 | no, it's not the same as g1 |
22:37.34 | maejrep[w] | [15:52:36] <cr2> maejrep[w]: it is not clear if we really need it <-- need what? |
22:37.55 | maejrep[w] | [15:53:35] <dcordes_> maejrep: can I use i2c-tools instead of haret to sort out the keycodes? <-- yes, but only if microp-keyboard is not loaded |
22:37.57 | cr2 | maejrep[w]: this hardware usb bugfix. |
22:38.13 | maejrep[w] | what bug fix? :o |
22:38.24 | cr2 | maejrep[w]: i don't know the usb internals |
22:38.43 | cr2 | maejrep[w]: g1 code writes some values into phy, to fix some bug |
22:39.15 | cr2 | maejrep[w]: imvho the 19MHz clock is 19.2MHz and 48MHz clock is 32MHz |
22:39.39 | cr2 | i can provide you my rationale, but it's too long for irc :) |
22:39.57 | NetRipper | start a blog |
22:39.58 | NetRipper | ;) |
22:40.01 | cr2 | LOL |
22:40.15 | cr2 | this channel is very close to that ;-) |
22:40.20 | NetRipper | so true |
22:40.52 | cr2 | maejrep[w]: i don't know if you can somehow use this information |
22:41.11 | cr2 | the 32MHz rationale is very simple |
22:41.27 | cr2 | compare the values for 12,24 and (48) |
22:41.53 | cr2 | the arg3 is some pwm parameter, we have it as arg2/2 |
22:41.59 | exco | cr2: so with vreg and gpio known wifi should be a quick fix? |
22:42.01 | cr2 | the rest is identical |
22:42.26 | cr2 | the values are 12:24:xx -> 0x20:0x10:0xc |
22:42.35 | cr2 | xx should be 32 |
22:43.05 | BabelO | popopolo !!! |
22:43.11 | *** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net) |
22:44.14 | cr2 | BabelO: ? :) |
22:44.23 | *** join/#htc-linux konsta (n=asds@host81-154-247-76.range81-154.btcentralplus.com) |
22:44.40 | NetRipper | oh btw, for anyone that wants to use haretconsole on windows, i made a small package (for my own convinience)... includes python, but you dont have to install python.. http://www.netripper.com/raphael/HaretconsolePackageForWin.zip |
22:44.43 | BabelO | cr2: reading battery charge on omap :) |
22:45.01 | cr2 | exco: you need to compile the tiacx driver. and add the power/detect functions for polaris |
22:45.12 | cr2 | BabelO: nice |
22:45.13 | NetRipper | it has a .bat to easily start it when connected via activesync |
22:48.40 | BabelO | cr2: what kernel do you use on MSM ? i m still with 2.6.26 :( |
22:50.00 | cr2 | BabelO: maejrep[w] uses .27 |
22:50.08 | cr2 | but it's buggy |
22:50.21 | exco | cr2: sounds easy (now if I had any idea ...) - will probably come back tomorrow and keep asking ;-) I think it would be best to start with Angstrom image? |
22:50.36 | cr2 | of course. |
22:50.49 | BabelO | cr2: can't be more buggy than windows :) |
22:51.09 | cr2 | i don't understand the people who try to run and debug android, when they perfectly know that the kernel is buggy and incomplete |
22:51.31 | exco | Good night and thanks for all the -fish- - help I mean |
22:51.32 | cr2 | adding 10 more layers of complexit |
22:51.43 | BabelO | cr2: i reach a new personnal record :) 34 days of windows XP without reboot, it is half working, but still works |
22:51.43 | cr2 | bye |
22:51.53 | cr2 | lol |
22:52.14 | *** part/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de) |
22:52.16 | cr2 | BabelO: i'll replace XP with suse LDS soon. |
22:52.24 | BabelO | what is LDS ? |
22:52.39 | cr2 | LinuxDesktopSomething :) |
22:53.15 | NetRipper | maejrep[w], that "Keyboard backlight" gpio you found on raph800.. how'd you trace it? it doesn't show up in 'watch gpios' on haret |
22:53.17 | cr2 | we have official support for it. and it's cheaper than XP :) |
22:53.19 | NetRipper | for raph100 |
22:53.25 | BabelO | cr2: ok :) |
22:54.05 | cr2 | NetRipper: it's an i2c command ? |
22:54.17 | NetRipper | cr2, on raph800 it's a gpio |
22:54.22 | cr2 | NetRipper: hmm. |
22:54.25 | NetRipper | cr2, at least, that's documented in wiki |
22:54.32 | NetRipper | i cant find it on raph100 |
22:54.49 | NetRipper | although |
22:55.07 | cr2 | ok |
22:55.10 | NetRipper | when doing an mmutrace i see values going 0-1 |
22:55.14 | NetRipper | but back right away |
22:55.19 | NetRipper | not consistently 1 = on and 0 is off or something |
22:55.19 | cr2 | NetRipper: what about stylus gpio ? |
22:55.23 | NetRipper | sec. |
22:55.43 | cr2 | eventually i'll configure the wifi AP at home, and then can trace things too |
22:56.01 | NetRipper | you dont use windows? |
22:56.22 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
22:56.22 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
22:56.33 | cr2 | not anymore |
22:56.53 | NetRipper | linux has ndis too, you can use your linux to connect to haret |
22:57.03 | cr2 | maejrep[w]: i must honestly tell you that the 7200 lcd init is even a bigger pita than raph800 :) |
22:57.49 | cr2 | NetRipper: need to finish the RE things first. with the precious time :) |
22:58.01 | NetRipper | cr2, what is SCL and SDA? |
22:58.15 | cr2 | i2c lines |
22:58.19 | NetRipper | hm |
22:58.22 | maejrep[w] | NetRipper: just watch gpios, when I would press a key or open the slider, I'd see it go high when the light came on, then low when the light went off |
22:58.26 | cr2 | SerialCLock and SerialDAta |
22:58.47 | NetRipper | both stylus and keyboard backlight seem to trigger SCL and SDA gpios |
22:58.55 | NetRipper | 2-17 and 2-18 |
22:59.01 | NetRipper | so they may be i2c after all |
22:59.03 | maejrep[w] | SCL and SDA i believe are only on alt funcs |
22:59.14 | cr2 | NetRipper: it's better to mask all ALT gpios |
22:59.30 | cr2 | because you never know what pops up there |
22:59.51 | NetRipper | 2-17 and 2-18 are not alt, are they? |
22:59.56 | cr2 | tracing makes real sense only with real=non-alt gpios |
23:00.03 | maejrep[w] | SCL and SDA are alt iirc |
23:00.22 | NetRipper | ok so i have to ibit the gpio's that have 'alt' in their description? |
23:00.23 | cr2 | any nongpio function is alt |
23:00.32 | cr2 | yes |
23:00.46 | maejrep[w] | NetRipper: the "4,1" is what indicates that it's alt |
23:00.50 | NetRipper | so basically bank 5 |
23:00.52 | cr2 | we already know their purpose, so tracing is useless |
23:01.25 | cr2 | 4 is alt, and 1 is for suspend/disable |
23:01.26 | NetRipper | maejrep[w], oh.. so any gpio that has a comma in the alt |
23:01.37 | maejrep[w] | i think |
23:01.43 | maejrep[w] | cr2 can explain it better |
23:01.49 | maejrep[w] | i'm not fully understanding it myself |
23:01.51 | NetRipper | but still |
23:01.58 | cr2 | NetRipper: i'm lazy, so i've saved me some time for editing |
23:02.00 | maejrep[w] | that's just what I understand of it |
23:02.02 | NetRipper | it's only 2-17 and 2-18 being triggered |
23:02.07 | NetRipper | no others |
23:02.14 | maejrep[w] | NetRipper: try mmutrace i2c |
23:02.18 | maejrep[w] | see if the backlight is done by i2c |
23:02.33 | NetRipper | despite them being alt.. it should trigger other gpios if it were via gpios |
23:02.35 | cr2 | the real "ALT" setting can be extracted from the CFG register value |
23:02.39 | maejrep[w] | i know others did say that they saw the backlight turn on with the keyboard driver |
23:02.43 | maejrep[w] | even though I don't |
23:02.46 | maejrep[w] | so I don't know why |
23:02.53 | cr2 | but you need to know where are the drvstr,pull and alt bits there |
23:03.03 | NetRipper | maejrep[w], ok |
23:03.13 | maejrep[w] | cr2: have you confirmed that we can read the alt cfg from the same memory address? |
23:03.23 | maejrep[w] | does it need an A2M interrupt? |
23:03.28 | BabelO | cr2: what is FFS for you ? |
23:03.40 | maejrep[w] | for fuck's sake? |
23:03.45 | cr2 | maejrep[w]: i need the blackstone wince kernel for that, to be 100% sure |
23:03.50 | maejrep[w] | ah |
23:03.54 | NetRipper | maejrep[w], also some users on forum reported that 'pulling in and out' stylus would bring them back to their home screen (back on android 0.8)... it never did for me... so maybe my stylus is not gpio.. and just i2c... i'll trace i2c now.. sec |
23:03.56 | maejrep[w] | why blackstone and not others? :p |
23:04.35 | maejrep[w] | NetRipper: also note that windows does some stuff as a result of pulling the stylus |
23:04.49 | cr2 | NetRipper: stylus gpio may be an irq (wakeup too) |
23:04.49 | maejrep[w] | so it might be better to watch irqs instead |
23:04.56 | maejrep[w] | cr2: it is wakeup |
23:05.09 | maejrep[w] | when you pull the stylus, it turns the device on |
23:05.12 | cr2 | look for unassigned wiki irqs |
23:05.37 | cr2 | BabelO: in the battery context ? |
23:05.50 | BabelO | cr2: no |
23:05.54 | BabelO | cr2: it is that |
23:05.57 | BabelO | #define GSM_FFS_VIRTUAL_ADDRESS 0xc3f00000 |
23:05.58 | BabelO | #define GSM_CODE_VIRTUAL_ADDRESS 0xc3b00000 |
23:06.16 | cr2 | no idea |
23:06.29 | maejrep[w] | cr2: can amss be dumped from memory? |
23:06.46 | maejrep[w] | or perhaps extracted from stock rom? |
23:06.56 | tmzt | imgfs |
23:07.35 | NetRipper | maejrep[w], http://netripper.pastebin.com/m61f1db65 |
23:07.40 | dcordes_ | is somebody able to edit xda wiki? |
23:07.48 | dcordes_ | I get the blank page problem |
23:08.19 | maejrep[w] | NetRipper: can you do that as mmutrace, not traces? :) |
23:08.32 | NetRipper | oh |
23:08.40 | NetRipper | ah |
23:08.41 | NetRipper | oops |
23:08.41 | NetRipper | :) |
23:08.44 | NetRipper | my mistake |
23:09.36 | maejrep[w] | dcordes_: sometimes that's related to the type of markup you use |
23:09.50 | maejrep[w] | try using old style, or tweaking your wiki code |
23:10.54 | NetRipper | er |
23:11.04 | NetRipper | mmutrace is not showing anything |
23:11.23 | cr2 | maejrep[w]: when titan came out (first known htc msm7x00 phone) it was possible, but then they have closed that hole (i think) |
23:11.24 | maejrep[w] | addlist mmutrace 0xb2300000 1 & addlist mmutrace 0xb230000c 1 |
23:11.58 | cr2 | maejrep[w]: amss can be extracted from update .nbh |
23:12.28 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
23:12.40 | cr2 | or from googel .ota or how it is called, as tmzt said |
23:12.55 | maejrep[w] | .ota? |
23:13.00 | maejrep[w] | i mean for our devices |
23:13.05 | cr2 | .nbh |
23:13.11 | maejrep[w] | so it can be extracted from the stock rom .nbh? |
23:13.28 | cr2 | but i'd better looked at ota g1 version :) |
23:13.35 | cr2 | yes |
23:13.51 | NetRipper | hm |
23:14.48 | NetRipper | cr2, why do i have to trace i2c on 0xb2300000.. instead of p2v(0xa9900000)? is the phys address wrong in wiki? |
23:15.09 | maejrep[w] | cause p2v() will by default give you an untraceable virt address |
23:15.21 | NetRipper | :s |
23:15.26 | NetRipper | nice. |
23:15.27 | maejrep[w] | b23* is the same physical address, but it's traceable |
23:15.35 | cr2 | maejrep[w]: sometimes |
23:15.45 | maejrep[w] | if you do dump mmu 2 a9900000 you'll see 2 mappings |
23:15.51 | dcordes_ | shrugs |
23:15.52 | cr2 | yes |
23:15.57 | dcordes_ | I just skipped the preview :P |
23:16.40 | cr2 | NetRipper: actually, you should trace all virtual mappings of 0xa9900000 |
23:16.59 | NetRipper | maejrep[w], http://netripper.pastebin.com/d251ed37d |
23:17.01 | cr2 | 10 drivers can ioremap it to 10 $randomadress |
23:17.05 | NetRipper | cr2, oh |
23:17.15 | NetRipper | cr2, it's that issue where you wanted Kevin2 to update haret for |
23:17.23 | cr2 | yes |
23:17.59 | maejrep[w] | interesting |
23:18.03 | dcordes_ | http://wiki.xda-developers.com/index.php?pagename=Raph800GPIODump task 55 |
23:18.07 | dcordes_ | is this debug console? |
23:18.07 | maejrep[w] | it considers the stylus a keyboard event ;oi |
23:18.17 | NetRipper | maejrep[w], /me cries |
23:18.19 | maejrep[w] | dcordes_: that's spl |
23:18.37 | dcordes_ | the usb debug port? |
23:18.39 | NetRipper | maejrep[w], it's a scancode you didnt map before? |
23:18.40 | dcordes_ | usb>serial |
23:18.41 | maejrep[w] | in raph, hold vol down and power + soft reset until the tri-color bootloader |
23:18.58 | maejrep[w] | NetRipper: no, no scancode |
23:19.02 | maejrep[w] | dcordes_: yes |
23:19.03 | dcordes_ | ok |
23:19.08 | maejrep[w] | then use mtty to connect |
23:19.11 | maejrep[w] | and task 55 |
23:19.15 | dcordes_ | I had that in kovsky wince dmesg |
23:19.18 | dcordes_ | no need :) |
23:19.21 | cr2 | dcordes_: it's some conspiracy :) |
23:19.37 | cr2 | maejrep[w]: mtty == cu/minicom |
23:19.43 | NetRipper | maejrep[w], is it something hard to implement? i have no clue on what im seeing |
23:19.48 | maejrep[w] | NetRipper: it's in the upper byte of the scancode, which microp-keypad is ignoring now |
23:19.55 | maejrep[w] | ok |
23:20.12 | cr2 | maejrep[w]: pH5 has written some similar tool, and pof too |
23:20.28 | maejrep[w] | 0xce,10 -> "tell microp i want to read channel 10 of 0x67 chip address" |
23:20.38 | maejrep[w] | the next two responses with ..c==______ |
23:20.44 | maejrep[w] | are the responses from the chip |
23:20.50 | maejrep[w] | in this case, 2 bytes are being read off the chip |
23:20.56 | maejrep[w] | for keyboard scancodes, we only look at the first byte |
23:21.05 | cr2 | ce,10,2,x |
23:21.08 | maejrep[w] | in this case, the stylus is 0x01 on the upper byte |
23:21.15 | cr2 | is a wiki 'ism for that |
23:21.29 | *** join/#htc-linux stadicon (n=liberost@79.107.28.155) |
23:21.30 | maejrep[w] | cr2: the ,2 means "read 2 bytes"? |
23:21.38 | cr2 | buffer size |
23:21.41 | NetRipper | and when its 0x00 on the upper byte, it's removed? |
23:21.43 | stadicon | hi |
23:21.47 | cr2 | x means buffer ptr |
23:21.47 | maejrep[w] | cause i can never tell if you mean how many bytes, or to *write* 0x02 :p |
23:22.06 | maejrep[w] | NetRipper: no, the 0x80 is the removal |
23:22.18 | NetRipper | maejrep[w], ok |
23:22.25 | cr2 | maejrep[w]: in most cases it's some wince function, which was documented at the bottom |
23:22.25 | maejrep[w] | for keyrelease events, you get <scancode>|0x80 on the lower byte (1st byte) |
23:23.11 | maejrep[w] | but in this case, the 2nd byte of ce,10 is 0x01 on event, and 2nd byte of ce,11 is 0x00 on insert, 0x80 on removal |
23:23.14 | cr2 | maejrep[w]: i may have entered something inconsistently, but i'll try to be more accurate now :) |
23:23.53 | maejrep[w] | so that's how we'll detect stylus |
23:24.20 | maejrep[w] | NetRipper: looks like your driver is different from mine |
23:24.30 | NetRipper | maejrep[w], as im not really understanding this.. can you update wiki with this info? |
23:24.34 | dcordes_ | how does msm_fb know which panel to use? |
23:24.35 | maejrep[w] | mine reads ce,10 then ce,11 then sets LCDs, then reads ce,10 and ce,11 again |
23:24.38 | cr2 | maejrep[w]: stylus is an i2c event on raph100 ? sounds very complex for a wakeup irq |
23:25.00 | maejrep[w] | cr2: possibly not - but it *is* received as a keyboard event apparently |
23:25.09 | maejrep[w] | it might also be provided as a gpio, but can't tell that for sure yet |
23:25.17 | cr2 | dcordes_: you can query the gpios, which define it. |
23:25.19 | maejrep[w] | NetRipper: anything useful on opening keyboard slider? |
23:25.29 | dcordes_ | cr2: how to do that? |
23:25.30 | NetRipper | keyboard slider = gpio |
23:25.37 | maejrep[w] | NetRipper: i mean the backlight |
23:25.44 | NetRipper | sec. |
23:25.54 | NetRipper | i'll also have to press a key though |
23:25.55 | maejrep[w] | which would be on cc,* |
23:26.01 | maejrep[w] | it doesn't turn on just by opening? |
23:26.07 | cr2 | dcordes_: i think there is a sample implementation in the g1 source. which applies to g1 only, though. |
23:26.11 | NetRipper | yes |
23:26.43 | cr2 | maejrep[w]: was it possible to control the backlight with the haret-w.exe ? |
23:26.54 | maejrep[w] | cr2: forgot to try it ;x |
23:26.59 | NetRipper | maejrep[w], http://netripper.pastebin.com/m67823143 |
23:27.03 | maejrep[w] | but i was able to control the other leds in linux |
23:27.06 | maejrep[w] | with i2cset |
23:27.25 | cr2 | maejrep[w]: check it, the we may consider merging the code into mainline |
23:27.49 | cr2 | s/the w/then w/ |
23:28.09 | cr2 | but it only does on/off |
23:28.26 | cr2 | i don't know a portable way to change the brightness |
23:29.49 | NetRipper | maejrep[w], this is better: http://netripper.pastebin.com/m6e944774 |
23:29.50 | maejrep[w] | i haven't played with brightness yet |
23:30.05 | BabelO | good night |
23:30.30 | cr2 | BabelO: good night |
23:30.34 | maejrep[w] | hmm |
23:30.45 | maejrep[w] | NetRipper: cc,40,0f,65 is interesting |
23:30.50 | maejrep[w] | I don't think I tried that one |
23:31.34 | maejrep[w] | adds to his todo list |
23:31.55 | NetRipper | maejrep[w], can you englishten me what the cc,40,0f,65 sequence means... as i can only find the cc on the pastebin |
23:32.01 | NetRipper | enlighten* |
23:32.17 | NetRipper | englishten is because of the time of day |
23:32.27 | maejrep[w] | ok, so a better understanding of it will come from reading i2c-msm.c |
23:32.31 | maejrep[w] | but here's the short version |
23:32.32 | NetRipper | ok |
23:33.56 | cr2 | maejrep[w]: what is cc,20,2,0 ? |
23:34.34 | NetRipper | cr2, from wiki: cc,20,02,00 - lcd poweron related |
23:35.13 | cr2 | NetRipper: yes, i've put it there :) but what does 'related' mean |
23:35.20 | NetRipper | ah ;) |
23:35.47 | maejrep[w] | NetRipper: http://netripper.pastebin.com/m498a5e3f |
23:36.10 | maejrep[w] | cr2: I don't recall |
23:36.52 | maejrep[w] | NetRipper: in reality, that 0x01 and 0x79 on lines 5 and 6 are the 1st and 2nd byte |
23:37.00 | maejrep[w] | 0x23 is just the data address, not really a "first byte" |
23:37.44 | maejrep[w] | NetRipper: but everything you see there is handled by i2c-msm |
23:38.43 | maejrep[w] | so, all you need to know are: write to chip 0x66, data 0x23, buffer { 0x01, 0x79 } |
23:39.09 | maejrep[w] | and: write to chip 0x66, data 0x33, read from chip 0x66, length 2 |
23:39.23 | maejrep[w] | and the driver takes care of translating it |
23:40.08 | NetRipper | maejrep[w], ok.. |
23:41.29 | maejrep[w] | does that make sense? :P |
23:41.34 | NetRipper | im trying |
23:41.36 | maejrep[w] | I can back up if you'd like |
23:41.47 | NetRipper | let me tell you what i understand now |
23:42.37 | NetRipper | those lines 3-6, are they by the i2c driver or by the hardware? |
23:43.36 | NetRipper | how does the driver know what the hardware wants to tell (thus what command to send?) |
23:44.16 | maejrep[w] | c== is the hardware |
23:44.20 | maejrep[w] | b2300000 = is from the driver |
23:44.32 | maejrep[w] | b230000c== is from the hardware |
23:44.34 | NetRipper | ok |
23:44.52 | maejrep[w] | so, +0 is send, +0xc is recv |
23:45.03 | NetRipper | yes |
23:45.10 | maejrep[w] | 0x4 is the status buffer, but we don't need to deal with that |
23:45.21 | maejrep[w] | and i forgot what 0x8 is |
23:45.23 | NetRipper | ok so.. an interrupt occurs.. but how does the driver know which chip to 'poll'? |
23:45.35 | maejrep[w] | it knows by the interrupt |
23:45.45 | NetRipper | an interrupt doesn't pass any data, does it? |
23:45.47 | maejrep[w] | so... say gpio 27 interrupt is raised |
23:45.59 | maejrep[w] | the driver knows "gpio 27 is the keyboard interrupt" |
23:46.02 | NetRipper | ah |
23:46.05 | maejrep[w] | so its the keyboard driver that has hooked that interrupt |
23:46.16 | maejrep[w] | therefore it is going to read ce,10 and ce,11 |
23:47.07 | NetRipper | ok and how does i2c know the hardware will send 2 bytes, and not 20? |
23:47.30 | maejrep[w] | it doesn't have to -- the driver knows |
23:47.47 | maejrep[w] | so, driver knows that ce,10 returns 2 bytes, therefore it tells the i2c bus driver "give me 2 bytes" |
23:47.54 | NetRipper | ok |
23:48.15 | NetRipper | so the i2c bus driver simply stops after those 2 bytes as it assumes it's done |
23:48.19 | NetRipper | ok |
23:48.52 | NetRipper | ok and now back to the sequence.. cc,40,0f,65... you got that from my pastebin, right? |
23:49.48 | maejrep[w] | yes |
23:49.52 | maejrep[w] | and yes |
23:50.00 | maejrep[w] | line 44 |
23:50.05 | maejrep[w] | is where it starts |
23:50.17 | maejrep[w] | it's all write (there is no read related to it) |
23:50.31 | NetRipper | ah |
23:50.36 | maejrep[w] | the only reads you'll see on chip 0x66 (cc) is most likely for either version info or ADC (light sensor) |
23:50.43 | lavender-t | hello guys, anything tricky about the MSM_FB stuff in .27 ? |
23:50.49 | maejrep[w] | or to read the current LED status i guess |
23:51.32 | maejrep[w] | so, 0x100 means "chip address". 0x200 means "last byte", and 0x01 means "read" |
23:51.37 | maejrep[w] | i'm sure there are more flags |
23:51.49 | NetRipper | maejrep[w], so the first sequence is cc, 23, 1, 79? when the keyboard is opened |
23:52.01 | maejrep[w] | yes, and it's a write |
23:52.13 | NetRipper | oh, we only care abou treads? |
23:52.16 | NetRipper | reads* |
23:52.27 | lavender-t | i realized msm_mddi0_device is not there any more ? |
23:52.29 | maejrep[w] | so you're writing 0x0179 to data address 0x23 of chip 0x66 |
23:52.42 | maejrep[w] | lavender-t: it was moved i think |
23:52.47 | NetRipper | maejrep[w], ok |
23:52.55 | maejrep[w] | hmm |
23:53.02 | maejrep[w] | actually, that might be 0x7901 |
23:53.09 | maejrep[w] | will have to check endianness again :p |
23:53.39 | maejrep[w] | but either way, you'd send it in that order as a byte array |
23:53.43 | NetRipper | ok |
23:54.11 | maejrep[w] | so: buffer = { 0x23, 0x01, 0x79 }; i2c_master_send( client, buffer, 3 ) |
23:54.41 | NetRipper | maejrep[w], final question.. the i2c hardware writes two bytes.. but it does it right after eachother.. the i2c bus driver must read it in sequence.. is ther ean interrupt between each byte read? |
23:55.14 | maejrep[w] | and the next one down would be: i2c_master_send( client, "\x33", 1 ); i2c_master_recv( client, buffer, 2 ); |
23:55.14 | NetRipper | the driver should indicate somehow like 'ok give me the next byte' |
23:56.04 | maejrep[w] | I don't think so, I think its just a series of "wait_for_.." polls |
23:56.24 | cr2 | lavender-t: the raph800 lcd init seems to be tricky |
23:56.49 | maejrep[w] | <PROTECTED> |
23:57.05 | NetRipper | hm ok |
23:57.06 | maejrep[w] | <PROTECTED> |
23:57.07 | cr2 | lavender-t: i've put the last nail into the SD clocks story. the 19MHz clock is 19.2 and 48MHz is 32MHz ;) |
23:57.07 | maejrep[w] | etc |
23:57.12 | NetRipper | ok |
23:57.19 | NetRipper | it uses the other bytes for that |
23:57.43 | maejrep[w] | actually |
23:57.49 | maejrep[w] | yes |
23:57.51 | NetRipper | maejrep[w], im starting to put it together a bit :) |
23:57.52 | maejrep[w] | but there is an interrupt |
23:57.54 | maejrep[w] | :) |
23:57.55 | lavender-t | cr2: oh that's cool :) |
23:58.28 | NetRipper | maejrep[w], thanks for your explanation |
23:59.03 | maejrep[w] | <PROTECTED> |
23:59.03 | maejrep[w] | <PROTECTED> |
23:59.03 | maejrep[w] | <PROTECTED> |
23:59.03 | maejrep[w] | <PROTECTED> |
23:59.23 | lavender-t | maejrep[w]: after the console handover and the 2 vibras, nothing showed up on the screen |
23:59.42 | lavender-t | i wonder if you hit that in .27 as well ? |
23:59.46 | cr2 | maejrep[w]: you have hitachi lcd ? |
23:59.51 | *** join/#htc-linux Kuma (n=John@f054218077.adsl.alicedsl.de) |
23:59.57 | *** join/#htc-linux timebomb (n=tb@e176115185.adsl.alicedsl.de) |