IRC log for #htc-linux on 20090121

00:00.20maejrep[w]yeah same here lavender-t
00:00.25maejrep[w]but dcordes isn't seeing that
00:00.27NetRippermaejrep[w], i've been removing some debug stuff and need to update teh #if's for diamond and cdma variants too
00:00.39maejrep[w]NetRipper: which debug stuff?  prink's?
00:00.41maejrep[w]+t
00:00.48NetRippermaejrep[w], printk's yes
00:01.38cr2dcordes: you've posted the dump muu ? i'll check
00:02.10NetRippermaejrep[w], what does "clamshell" mean?
00:02.30dcordeshttp://linuxtogo.org/~lgorris/misc/x1-mmu.txt
00:02.41cr2dcordes: you don't have any extra mappings
00:03.00cr2dcordes: can you try to add both 923 and b23 ?
00:03.33cr2addlist mmutrace 0x92300000 4
00:03.39cr2addlist mmutrace 0xb2300000 4
00:03.50cr2and for the write too
00:04.17cr2lavender-t: do you have strong nerves ?
00:04.29lavender-tahhhhh :s
00:05.01lavender-tanything could burn my phone ?
00:05.25*** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk)
00:05.32maejrep[w]92300000  | a9900000 |   1MB section |    AP=1 T=2
00:05.38cr2can you sed the register names to http://wiki.xda-developers.com/index.php?pagename=RaphaelLCD
00:05.38dcordescr2: ok addlist'D
00:05.44maejrep[w]b2300000  | a9900000 |   1MB section |    AP=1 T=2
00:05.48cr2using data from
00:06.23cr2http://wiki.xda-developers.com/index.php?pagename=RaphaelMDDI
00:06.31cr2as a separate column ?
00:09.05lavender-tcr2: were you talking to me ?
00:09.43cr2yes :) it's 1:09, and i'm going crazy with mddi ;)
00:09.51lavender-tok :)
00:10.07lavender-tbut i need to figure out what it is first ...
00:10.09cr2but don't delete the original numbers
00:10.37cr2because i'll 'join' with the raph/diam800 using it.
00:11.10maejrep[w]lavender-t: he's saying use the MDDI page as a reference point, and add the names into the LCD page
00:11.26cr2SSICTL  0x120000
00:11.28maejrep[w]ie, if it says 150000, make it say GPIOD etc
00:11.45lavender-tah ok
00:12.00cr2120000=170
00:12.30cr2so it should be | SSICTL | 120000 | =170 |
00:12.46maejrep[w]if you really want to be thorough you can make it:  mddi_write( 170, SSICTL )  :D
00:12.53lavender-tgot it. will do.
00:13.04cr2maejrep: mddi_remote_write ?
00:13.13dcordescr2: what to do after addlist
00:13.21cr2dcordes: wi
00:13.22maejrep[w]no, in .27 there's a macro called mddi_write and mddi_read
00:13.32cr2maejrep[w]: ok, like in the spl
00:13.38maejrep[w]which is defined as writel( (a), MDDI_##name )
00:14.04maejrep[w]and hten MDDI_SSICTL is defined as 120000
00:14.17cr2maejrep[w]: strange, because out of this patent pictures i got an idea that's it is really remote
00:14.31cr2ok
00:14.44maejrep[w]hmm, could be, iwll have to check again
00:14.59cr2lavender-t: some regs are not documented by google
00:15.04cr2lavender-t: like PWM1*
00:15.29maejrep[w]cr2: so you said dcordes' x1 can help explain pwm ?
00:16.36lavender-tok i guess i will leave the ?s as is
00:16.47dcordes000.026 7805f810: e5853000(str)         # b2300000 =000001cc
00:16.47dcordes000.026 7805f850: e5853000(str)         # b2300000 =00000030
00:16.47dcordes000.026 7805f8d8: e5853000(str)         # b2300000 =000001cd
00:16.47dcordes000.026 7805f970: 05852000(str)         # b2300000 =00000200
00:16.54dcordesit seems to react on keypress
00:17.02dcordesoutputs more lines then
00:21.39NetRipperright, im off to bed, ill finish tomorrow and commit it :)
00:21.43NetRippergood night
00:22.09cr2maejrep[w]: g1 uses the arg3 modification for pwm
00:22.43cr2maejrep[w]: and arg2=2*arg3 in the 7param formula
00:23.02dcordescr2: http://privatepaste.com/0d1YhjwX4b
00:24.37cr2maejrep[w]: which should be a normal symmetric clock signal. when you change the arg3, you get a pwm
00:25.40cr2dcordes: what is 0x6c/2 device ?
00:25.51cr20x36, hmm.
00:26.02cr2camera ? accelerometer ? OJ ? :)
00:26.29maejrep[w]cr2: what is pwm?
00:26.56maejrep[w]i think 36 is camera, yes
00:27.11cr2pulse-width modulation
00:27.21dcordescr2: led is complicated on x1 maybe it's that
00:27.35maejrep[w]hmm
00:27.37cr2maejrep[w]: if he has the same cam as we
00:27.47maejrep[w]cr2: looks like they fixed the i2c driver in x1 :)
00:28.00maejrep[w]oh, maybe not
00:28.09maejrep[w]just the 36 driver does it correctly:
00:28.09cr2maejrep: _________|^^^^^^^^^|______________|
00:28.23dcordeshttp://wiki.xda-developers.com/index.php?pagename=Kovsky_Cameras
00:28.28maejrep[w]#
00:28.28maejrep[w]#
00:28.28maejrep[w]001.129 7805fbc4: e5873000(str) # b2300000 =0000016c
00:28.28maejrep[w]#
00:28.28maejrep[w]001.129 7805fbec: e5873000(str) # b2300000 =00000208
00:28.51maejrep[w]in the other chips, they don't do the 0x200 "last byte" bit
00:28.55cr2maejrep: the ratio between 1 and 0 changes. for normal usual clock it's 1:1
00:28.56maejrep[w]bye i2c-msm does
00:29.39maejrep[w]dcordes: actually, if you have auto-backlight-adjust enabled, it could be that
00:29.55maejrep[w]the light sensor is on i2c
00:30.12cr2maejrep[w]: brightness sensor ? but it's on microP ?
00:30.14maejrep[w]but on raph, the light sensor is part of klt i think
00:30.22cr2ok
00:30.34maejrep[w]cr2: yeah, but I don't know what else could explain his 38 reads
00:30.38dcordesklt microP are the two microcontrollers?
00:31.00maejrep[w]there are 2 microp chips: klt and ksc (microp-led and microp-key)
00:31.20maejrep[w]probably the same chip/controller, but at different addresses, so they're considered separate "chips"
00:31.33dcordesok
00:32.09cr222:35:52 [D:AUD] open [\Windows\AudioPara3.csv] success!!
00:32.19maejrep[w]dcordes: actually what's weird is that he's not reading anything
00:32.24maejrep[w]er cr2
00:32.32dcordescr2: is that from blackstone dmesg?
00:32.37cr2yes
00:32.38maejrep[w]cr2: what??  is it really that simple? :P
00:32.41maejrep[w]a .csv file
00:32.50cr2maejrep[w]: check it
00:33.00maejrep[w]my phone's off cause I don't have a charger at work :P
00:33.08maejrep[w](with the reboot bug)
00:33.08cr2k
00:33.28maejrep[w]dcordes: can you upload that audiopara3.csv file somewhere?
00:33.58dcordesI don't have blackstone
00:34.47cr222:35:52 [D:AUD] open TIAGC.csv success!!
00:35.00maejrep[w]oh
00:35.03cr2dcordes: kaiser & x1 ?
00:35.20cr2lol
00:35.21maejrep[w]dcordes: can you check if you have it on any of your devices
00:35.27cr222:35:52 [D:AUD] AgcTable[2] (enable AGC youtube.exe)
00:35.33maejrep[w]yeah i saw that heh
00:35.39dcordesyoutube in dmesg
00:35.59cr2it's like ati that hardcoded the PocketTV.exe in the video driver ;)
00:37.02cr222:35:52 [D:GSNR] Pass CRC32-3
00:37.13cr2why does the accelerometer do CRC32 ?
00:37.52cr2hehe. my old good friends: MD and NS
00:37.56cr222:35:53 [D:BT] [BTU]MD NS ADDR 504070d8 504070dc
00:37.56cr222:35:53 [D:BT] [BTU]MD NS 3ff9b ff9e0044
00:37.56cr222:35:53 [D:BT] [BTU]Uart_DM_Clock(1, 115200)
00:38.04maejrep[w]nice
00:38.23cr2maejrep[w]: btw, you can invert them into 7param
00:38.38cr2and check if arg2=arg3*2
00:38.56maejrep[w]to know pwm?
00:38.56cr2it's not a pwm
00:39.19cr2pwm is when arg2 != arg3*2
00:39.30excoimfloflo: we don't need to chat on xda-devs ... if I can help you just ask me here
00:39.39dcordesmaejrep[w]: http://linuxtogo.org/~lgorris/misc/
00:44.07maejrep[w]dcordes: 403 forbidden
00:45.36dcordesmaejrep[w]: retry. I didn't have that problem before
00:45.59maejrep[w]worked, thanks
00:46.39maejrep[w]wow
00:46.45maejrep[w]that looks like it could be very useful information ;o
00:48.47maejrep[w]dcordes: didn't have TIAGC.csv?
00:49.28maejrep[w]cr2: isn't GSNR "ground signal to noise ratio"?  why do you say accelerometer?
00:49.56cr2G-SeNsoR n
00:50.02cr2in htc-speak
00:50.38maejrep[w]that's lame
00:52.15cr222:35:54 Turn on PMIC VREG[0x100]
00:52.16cr2.22:35:54 [D:CAM] Turn on sensor VDDD 1.8v OK
00:52.36cr2ok, this interface is already known
00:53.25cr2hm . different cam on blac100 ?
00:53.28maejrep[w]i wish i could find the dmesg area on my phone
00:53.29cr222:35:54 [D:CAM] Check MT9P012
00:53.35maejrep[w]looks the same?
00:53.40maejrep[w]or is ours p011 ?
00:53.51maejrep[w]raph is same as on g1
00:54.08cr2don't remember
00:54.14maejrep[w]at least, same sensor .. i2c chip *might* be different .. yet to look into it
00:54.27maejrep[w]i know g1's camera sensor is on a different i2c data address
00:54.30cr2MI380 is the second one. i think it's the same on raph
00:54.38maejrep[w]i don't have the 2nd one
00:54.52maejrep[w]http://wiki.xda-developers.com/index.php?pagename=RaphaelCameras
00:54.58maejrep[w]MT9T013
00:55.08maejrep[w]so it is different
00:55.13maejrep[w]other cam is MT9V113
00:55.33cr2ok
00:55.38cr222:35:54 Turn off PMIC VREG[0x800000]
00:55.38cr2.22:35:54 [D:SD] SD power off-
00:55.39maejrep[w]<PROTECTED>
00:55.43cr2this one is known too
00:55.54maejrep[w](on g1 it's 0x78>>1
00:56.01cr2all different
00:57.11cr222:35:56 [D:DISP] g_CurrentPanelType=10
00:57.21maejrep[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.32maejrep[w]0xa or 0x10 ?
00:57.43cr20xa, i think
00:57.48maejrep[w]probably
00:57.54maejrep[w]spl will tell you :P
00:57.58maejrep[w](%d vs %x)
00:57.59dcordesany further i2c tests required?
00:58.07cr2isn't it some binary qcom library for cam ?
00:58.31maejrep[w]dcordes: if you want to check scancodes for keyboard .. ? :)
00:58.31maejrep[w]really? :|
00:58.31maejrep[w]i know the i2c chip driver is implemented in source
00:58.44maejrep[w]but I don't know what they do with that chip driver yet
00:59.05cr222:35:56 [D:TP] TSSC_CTL=0x7d
00:59.05cr222:35:56 [D:TP] TSSC_STATUS=0x200
00:59.37dcordesmaejrep[w]: how?
00:59.40maejrep[w]that looks different
01:00.20maejrep[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.44maejrep[w]maybe just a spot check to see how different it is
01:01.02maejrep[w]checking things like TAB, BKSP, Q, SPACE,
01:01.16maejrep[w]if it's very different we'll need to document all the keycodes
01:01.18maejrep[w]*scancodes
01:01.26dcordesok
01:02.06maejrep[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.15maejrep[w]you only need the keypress number
01:02.20maejrep[w]not release
01:04.33dcordeswince calls the navi sensor "optical joystick"
01:04.41maejrep[w]o.0
01:04.43cr2good night, it's too late...
01:04.44maejrep[w]it's not optical
01:04.46maejrep[w]nite cr2
01:05.00maejrep[w]dcordes: behind the scenes it calls it navi
01:05.06maejrep[w]htcnavi.dll e.g.
01:05.27dcordesok been wondering why you call it navi
01:05.40maejrep[w]that's why :)
01:05.54dcordesthe x1 leds are neat
01:05.57maejrep[w]its what htc calls it in their service manual as well
01:06.03maejrep[w]what leds does it have?
01:06.16maejrep[w]x1 is xperia?
01:06.26dcordesuntick auto adjust backlight?
01:06.38maejrep[w]yeah, that'll make it easier to read the i2c output
01:06.43dcordesxperia x1 = kovsky = venus
01:07.10maejrep[w]cool
01:07.41maejrep[w]oh the keyboard layout is very different :x
01:08.47dcordeshm the keyboard backlighht sort of fades on also
01:09.00maejrep[w]that sounds complicated :p
01:09.10maejrep[w]have you been into the spl yet?
01:09.11dcordeswhy?
01:09.18maejrep[w]it might report the microp version number
01:09.32dcordesno but cr2
01:10.13maejrep[w]oh you dumped the spl?  i meant booting into the spl (tri-color bootloader)
01:11.01dcordesoh sorry. no I didn't do that but I've got a hard spl
01:11.24maejrep[w]22:48:48 [D:KEY] Init MicroP keyblock
01:14.06lavender-toh cr2's left ?
01:14.23maejrep[w]yes
01:14.26lavender-tjust sed the file
01:16.07lavender-thow to send the file to him ?
01:17.49maejrep[w]isn't it just on the wiki?
01:18.12lavender-tyep ... so i just need to update the wiki ?
01:18.18maejrep[w]yeah i think so
01:18.26maejrep[w]heading home
01:18.39lavender-tok will do.
01:20.07dcordeslavender-t: I wish you a pleasent evening
01:20.24dcordesmaejrep[w] I mean. will test the keycodes tomorrow
01:20.36dcordesalso 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.54maejrepcr2: so seems that reboot problem just kind of cleared itself up while I was preparing to do the hard reset :|
03:36.24maejrepi 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.30maejrepkinda 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.48lavender-thi maejrep, any new updates to your patches ?
05:14.05lavender-ti mean the .27 ?
05:18.29maejrepi haven't done anything with it
05:19.43lavender-tyou know anyone's porting it to diam ? netripper ?
05:19.54maejrepI don't
05:20.24maejrepNetRipper has been working on cleaning up the changes to get ready for the first big ltg commit to the .27 branch
05:20.34lavender-tk ic
05:21.02maejrepit'll likely feel like a step backward at that point until the remaining merge issues have been resolved
05:21.40lavender-ti'll give it a try ... time is a little limited though. gonna take a 2-week vacation from next week :)
05:22.18maejrepso you'll have 2 weeks to work on it?! :D
05:22.22maejrepjk :p
05:22.47lavender-toh 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.30parmasteri 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.20maejrepcr2: I found my wince dmesg area ;x
06:41.26maejrep0x17600000
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.01maejrephttp://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.26cr2maejrep: hi
07:45.44cr2maejrep: found something useful in dmesg ?
07:46.03maejrepsome clues to hardware
07:46.07maejrepnot really earth shattering
07:46.22maejrepa lot of it we already knew, but some of it is most likely raph800 specific
07:47.22maejreplooks like the modem reset hook is probably implemented in HtcServices.dll
07:48.06cr2do you see the SMD channel list ?
07:48.39maejrepit auto detects everything else, except AT and DATA i think
07:48.47maejrepbut yeah i think i saw those offsets in the output
07:49.15cr2do you see them in smem ?
07:49.20maejrepyes
07:49.28maejrepi've had that information for a while now
07:49.33maejrepjust haven't implemented it
07:49.33cr2lavender-t: thanks for editing the wiki :)
07:49.50cr2maejrep: hm. why is it not autodetected ?
07:50.12maejrepcause qct,htc,sprint are dumb?
07:50.13maejrep:p
07:50.37maejrep(mostly qct)
07:50.49cr2ok
07:51.28excocan I find out the  wifi base address of Polaris with haretconsole?
07:52.29maejrep22:44:34 [K] OEMSetAlarmTime: [0x36a7af4a], 1-20, 22:50:50
07:52.44maejrepseems strange
07:53.01cr2exco: 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.45cr2maejrep: you want to do psoc cmd9 ?
07:53.58cr2it's the psoc id sequence
07:55.18cr2maejrep: mddi_client_lcd_get_vsync_param
07:55.29cr2maejrep: which dll has this string ?
07:55.49maejrepnot sure
07:55.57cr2nk.exe ?
07:56.50cr2ok, i must leave now
07:58.13maejreplooks like no
07:58.20maejrepdont 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.47maejrepcr2: CertVerify: DISPTOOLS.dll trust = 2  ?
08:07.52maejrepfor 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.02excoif 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.33NetRippermarex, in the htcraphael-panel.c you bail out when it's not a raphael.. shouldn't it also work for diamond?
09:19.56NetRippers/marex/maejrep/
09:20.03marexhuh ? I have nothing to do wtih msm based devices
09:20.05marexah ok
09:20.06NetRippersorry ;)
09:20.16NetRippertab-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.54Untouchab1eGood morning _D
09:27.27NetRippermorning
09:29.05*** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl)
09:29.40Untouchab1eHow are you?
09:30.26NetRipperim good, at work
09:30.29NetRipperyou?
09:30.33Untouchab1ehehe, also good.. At class
09:30.36Untouchab1e^^
09:30.52*** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl)
09:31.15Untouchab1eInstalled eclipse and the ADT yesterday.. I like the idea of the layout being handled by .xml
09:32.31NetRipperah
09:32.41NetRipperbit WPF/XAML like?
09:32.50NetRipperbut then for java instead of .net
09:33.29Untouchab1eYeah, I guess..
09:33.45*** join/#htc-linux mib_iumf19 (i=5144ce60@gateway/web/ajax/mibbit.com/x-88b1cbc1486bfa3a)
09:34.28Untouchab1eIve 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.41Untouchab1eHowever, Eclipse isnt working too well for me on any of my computers..
09:34.55Untouchab1eUsed up 1,5GB of RAM.. lol
09:35.26NetRipperouch
09:35.41NetRipperguess you're not using a barebone eclipse :)
09:36.49Untouchab1eyeah, might seem like it..
09:37.35Untouchab1eI 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.13NetRipper4gb must be plenty for eclipse
09:40.20Untouchab1eyeah, one would think so
09:40.31NetRipperyou got some screwed up eclipse perhaps ;)
09:40.51Untouchab1ebut suddenly, Eclipse just went awesomely slow and reported memory overflow and wanted to close
09:40.52Untouchab1e:P
09:41.07NetRipperyea, sounds like memory leak
09:41.46Untouchab1eCan't say my first impression with Eclipse is all good :P
09:43.56Untouchab1eoh 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.50NetRipper.7
09:56.01NetRippermaybe we'll port to .28 againt though, we'll see that then
09:58.13Untouchab1eOkey.. 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.36Untouchab1e: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.13stadiconhi
13:40.40stadiconi am interested in helping with drivers for DIAM100
13:41.14stadiconis there anyone can help me?
13:44.22imflofloyes
13:44.44imfloflojsut let your message
13:44.50imfloflopeople rea log
14:11.20maejrep<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.21maejrep;)
14:11.43NetRippermaejrep, no just needed to konw if it was specifically to raphael or not
14:11.57maejreplol
14:12.17NetRippermaejrep, btw, when i boot, i get an error regarding clock
14:12.18maejrepyeah, i wasn't done debugging that area yet ;x
14:12.27NetRipperit tries to set sdc clock to 50mhz, but it fails
14:12.33NetRipperclock 21:50000000
14:12.37maejrepbut it works?
14:12.43NetRipperit mounts, yes
14:13.08NetRipperbut the clock function returns an error
14:13.11maejrepI think there was a change to drivers/mmc/hosts/msm* that made it use sdcc_set_host_clock
14:13.15maejrepthat I missed
14:13.44maejrepI get the same error, but didn't get a chance to look into it yet
14:13.49NetRipperah ok
14:13.54NetRipperwhen i try to boot android, it hangs
14:13.57NetRipperwell not the device
14:14.01NetRipperbut it just doesn't boot android
14:14.11NetRipperthought it may have to do with it
14:14.19NetRipperdoes android boot for you?
14:16.41NetRipperit stops before the splash screen displays
14:17.05maejrepanother option is to set fmax to 48MHz ?
14:17.08maejrepi have not tried android
14:18.19NetRipperthink i'll just commit this and we'll go from there
14:18.37NetRipperlast thing left is fixing up the diamond board
14:18.52stadiconmay i ask in which folder is htcraphael-panel.c?
14:19.02NetRipperarch/arm/mach-msm/
14:19.11stadiconoh, great thanks
14:19.20stadiconi was looking on drivers/input :)
14:19.31NetRipperboard-htcraphael-panel.c
14:20.27stadiconso we need to give "touch" capabilities to the driver?
14:21.15NetRipperwe already have touchscren
14:21.38NetRipperdrivers/input/touchscreen/
14:21.44NetRippermsm_ts
14:21.53*** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com)
14:23.02maejrepthere's a lot of stuff still on my todo list :p
14:25.37NetRippermaejrep, ok no problem, just wanted to know if i have the same result as you do :)
14:25.43NetRipperor if i screwed up something
14:25.44NetRipper;)
14:26.18maejrepyeah, I get the clock error, but it still works for me
14:26.34maejrepso I get a feeling dropping the max freq a little bit might help with that
14:27.02stadiconyes, but there is a touch interface on the "board"
14:27.22stadiconi mean, the call buttons etc. are a "capacitive screen"
14:27.34maejrepthat's a different "touchscreen" stadicon
14:27.40maejrepand there's not a full driver for it yet
14:27.45stadiconyes
14:28.07maejrepwe have the research for it, just haven't written a driver yet
14:28.40maejrepboard-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.42stadiconthat's what i said before...
14:28.53maejrepwhich means we still can't distinguish between Home and Send, for example
14:29.11stadiconyes, i understand that
14:29.17stadiconso we have to make a new driver
14:29.25stadiconfor this touchscreen...
14:29.39maejrepyes, sorry, that is correct
14:29.41NetRipperyep
14:29.41stadiconi am really interested in working on that
14:29.58stadiconbut i haven't worked again on drivers... :(
14:30.01NetRipperbut let's call it the navi instead of touchscreen to prevent confusion
14:30.02NetRipper:)
14:30.05*** join/#htc-linux nato2k (n=templarn@adsl-76-205-128-145.dsl.frs2ca.sbcglobal.net)
14:30.06maejrep:)
14:30.15stadiconi am now reading a tutorial about driver writing
14:30.17maejrepstadicon: the i2c research for it is on the wiki
14:30.32stadiconoh, ok
14:30.39stadiconi'll take a look
14:30.45maejrepyou're more than welcome to help :D
14:30.54stadiconsorry to annoy you but i want to help that project
14:31.17stadiconyes, but i am quite a starter on that area :p
14:31.33stadiconi 've done lots of other things about programming and linux
14:31.38stadiconbut not that yet :)
14:31.40stadiconanyway
14:31.47stadiconi'll give it a shot
14:31.48maejrepactually, I think there's still some confusion as to what each byte of the data actually represents
14:31.56maejrepbut we get all the data
14:32.23maejreplike we haven't fully figured out how to translate the values into x/y coordinates for each section
14:32.30maejrepoff to work, bye~
14:33.02stadiconbye
14:33.28stadiconthis is the pagee maejrep said, right? http://wiki.xda-developers.com/index.php?pagename=Raphael_Navi&redirectfrom=Raphael_I2C_Navi
14:33.35stadicon<NetRipper>
14:34.04NetRipperstadicon, yes, i think so
14:39.03stadiconsorry if this is a stupid question, but what's the way to research on this?
14:39.18stadiconi mean, is there any tool i can work to look about those bytes?
14:44.30NetRipperyou can use haret for that
14:44.52NetRipperusing haret you can trace memory addresses and see which memory addresses get changes and what their new values are
14:53.36stadiconi see
14:53.37stadiconthanks
14:59.22NetRipperstadicon, 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.51stadiconok, i'll try that
15:10.16NetRipperhm android does boot on .27 (with the 48mhz, i guess 144khz was just too slow, and i even waited 15 mins)
15:10.29NetRipperbut it's nearly not responding.. many timeouts
15:10.31NetRipperfor mddi
15:10.40NetRippermsmfb_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.48maejrep[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.51maejrep[w]that's what I did
16:22.19AstainHellbringmorning maejrep[w]
16:24.03NetRippermaejrep[w], do you have something to add on this? http://netripper.pastebin.com/m20520658
16:31.43maejrep[w]NetRipper: did the clock fmax change work ?
16:31.49NetRipperyes
16:31.52maejrep[w]nice
16:32.01NetRipper50mhz was too high, so it simply didn't pick any frequency
16:32.10NetRipperthe highest frequency in the array is 48mhz
16:32.19maejrep[w]i think it looks about right..
16:32.20NetRipperif we'd add one for 50, it'd probably work
16:32.22maejrep[w](the log)
16:32.23NetRipperok
16:35.02BalsatHas the git for .27 been updatet?
16:35.57NetRipperalmost
16:36.42BalsatNice... can't wait ;-)
16:38.05*** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl)
16:38.30NetRipperok, 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.02NetRipperi gtg home, bbl
16:39.16BalsatNice job netripper
16:39.26NetRipperlet me know if someone has problems compiling
16:40.01Balsatis 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.58maejrep[w]yes
16:48.28stadiconmaejrep: you mean to boot on linux on my host pc
16:48.39stadiconor boot linux on my diamond?
16:48.40maejrep[w]no
16:48.42maejrep[w]on the phone
16:49.00stadiconyes, i can boot android
16:49.15maejrep[w]as long as you can ssh in, that should be all you need
16:49.18maejrep[w]and the i2c tools
16:49.49stadiconso, i'll use a host pc and linux booted on my phone?
16:49.58stadiconi'll take a look.
16:50.23stadiconis i2c-msms.c the driver about the navi?
16:50.32stadicon*i2c-msm.c
16:50.51maejrep[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.56maejrep[w]i2c-msm is the i2c bus driver
16:51.00maejrep[w]you should not change that
16:51.20maejrep[w]to implement the navi it will have to be an i2c "chip" driver
16:51.24maejrep[w]at address 0x62
16:51.42stadiconi see.
16:51.44maejrep[w]added from board-htcraphael, in the i2c_devices section
16:52.30stadiconboard-htcraphael and board-htcdiamond, right?
16:52.40maejrep[w]yes
16:52.55stadiconok
16:52.58maejrep[w]look at microp-klt and microp-ksc.c
16:53.09maejrep[w]they implement i2c for the LEDs and Keyboard (raph)
16:53.21stadiconok
16:53.26stadiconi'll use them as template
16:55.52maejrep[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.29stadiconyes, but consider that i am a noob at that :p
16:56.53stadiconbut i think i can work on that :)
16:57.21stadiconi just hope you have enough patience for all my questions :)
16:57.24Balsat"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.01stadiconi 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.05stadiconmaejrep?
17:11.35maejrep[w]Balsat: did his commit not include defconfig?
17:11.47maejrep[w]stadicon: i think it was only committed to the .27 branch
17:11.54maejrep[w]I don't think it got committed to .25
17:12.01maejrep[w]but the file that's in .27 should also work with .25
17:12.59stadiconoh, then i'll download .27 git
17:13.01stadiconthanks
17:14.06maejrep[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.27NetRipperBalsat, the file should be there
17:15.25*** join/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de)
17:15.43NetRipperBalsat, if you had the git clone already before.. did you do a git pull before you did the -b?
17:18.29BalsatNo 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.51NetRipperthe defconfig is there.
17:18.55NetRippermake sure you have the latest version
17:19.00NetRipperhttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commitdiff;h=67654de7d2fb753cce73334196404d4cc092be24
17:19.03NetRipperfirst file
17:19.36stadiconi 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.28stadiconis it a problem that i switched from a 2.6.25 branch?
17:20.37NetRipperno it shouldn't
17:21.24stadiconstrange.
17:21.28stadiconwhere are those files?
17:21.31NetRipperdo a git pull
17:22.40stadiconoh, ok
17:22.42stadicongreat :)
17:22.44stadiconit worked
17:22.46NetRipperok
17:22.51NetRipperBalsat, do a git pull as well
17:23.08stadiconi don't remember me doing a git pull on the previous branch
17:23.14stadiconwas that wrong?
17:23.22NetRippergit pull retrieves the latest changes from the git
17:23.41NetRippergit checkout simply changes branches, it doesn't retrieve new data
17:23.42stadiconyes, but isn't it "branch specific"?
17:23.54NetRipperno it's not
17:24.06stadiconoh.
17:24.13NetRipperat least not to my experience
17:24.34*** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl)
17:24.36stadiconok, i'll check a git pull on my 2.6.25 to see if those files are downloaded their.
17:24.43stadiconmeanwhile, i am working on i2ctools
17:24.46NetRipperok
17:25.01stadiconcan you remind me what should be my diamond ip?
17:25.16NetRipper192.168.0.206
17:25.26NetRipperyou can use the angstrom initrd for usb
17:25.33NetRipperyou need to set 192.168.0.200 on your pc
17:26.00stadiconi've just booted the kernel
17:26.07stadiconi didn't even load android
17:26.15NetRipperhttp://www.netripper.com/raphael/20081204-01_raph_diam_angstrom_usb/
17:26.26NetRipperthe default.txt and zImage are outdated
17:27.00stadiconok, i only need initrd
17:27.03NetRipperor you can use the android initrd, but that has telnetd, not ssh (which means you cannot scp to your device)
17:28.02NetRipperdinnertime, bbl :)
17:28.11stadiconhave a nice dinner :)
17:35.58*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
17:36.02Untouchab1eGood Evening all :D
17:37.17pH5evening
17:38.47excogood evening
17:41.33stadiconhi
17:45.24*** join/#htc-linux cr2 (n=cr2@ip-90-187-213-62.web.vodafone.de)
17:45.50cr2hi
17:46.41cr2finally got rid of windows on nc10 :)
17:47.27excoI guess you put Mac OS X :-P
17:47.32excoon it
17:47.33pH5hi cr2, I'm so envious now.
17:47.36cr2linux is so much faster, why do people still use windows ?!
17:48.14cr2don't know to fast is the atom cpu for crosscompiling
17:49.09cr2pH5: there is no DSL  here, and umts comes only from vodafone ;) so i had no other chance
17:49.35Balsatgit pull did the magic for me ;-)
17:50.18pH5beware, that man is reading minds.
17:50.26AstainHellbringanyone tried crosscompiling on atom yet?
17:51.46cr2lol
17:51.48marexAstainHellbring, what is so special about atom ?
17:51.55cr2AstainHellbring: i'll try
17:52.06cr2marex: that's a slow cpu ?
17:52.07AstainHellbringdunno 100% sure marex just that its a low power cpu
17:52.11AstainHellbringand its 1.6ghz
17:52.21marexAbracadabra, so what ?
17:52.32marexAstainHellbring, ^
17:52.38cr2pxa270 is 624MHz, but you don't want to crosscompile there
17:52.58marexcr2, hi, long time no bla...errr, long time no see :)
17:53.17cr2marex: yeah, i still can't resume on n560 ;)
17:53.31marexcr2, I was compiling something on pxa27x at 416Mhz with 32meggs of ram ... :)
17:53.39cr2marex: and there is no sound support too...
17:54.01marexcr2, ah... I see you are pretty lazy about fixing the asoc driver :)
17:54.06cr2marex: pull the oe tree, and compile :)
17:54.10pH5marex: should have overclocked to 624 ;)
17:54.10cr2LOL
17:55.03marexpH5, I tried, but it stopped responding after a few seconds
17:55.12marexit held at 520 though ;)
17:55.23marexcr2, :D
17:55.48excoso what distro did you put on your NC 10 - if I may ask, cr2
17:58.28cr2exco: debian lenny
17:59.35cr2exco: and umts is configured manually. linux is not that user-friendly yet.
18:00.33cr2pH5: i would have dumped the local phone firmware, but don't know how :)
18:01.03AstainHellbringhopes crosscompile works well on atom as thats what I was gonna use my eee for
18:01.25excocouldn't you also do it the gui way with network manager applet? (well if you were a gui guy)
18:01.29cr2AstainHellbring: it's a x86 cpu, what can go wrong ?
18:01.44AstainHellbringyah true just hope that it works well and not just works...
18:01.48radem205hey exco
18:01.54excoif 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.59excohi radem205
18:02.22radem205I read that you could establish a data connection in Android, is that right?
18:02.28excoyes
18:02.33pH5AstainHellbring: I wonder if that hyperthreading works for parallel compiling. my single core celeron 220 wasn't all that fast.
18:02.34cr2exco: i've tried , but it's too modem-oriented. a more fine-tuned gprs & such gui should look different
18:02.51BalsatThe .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.17radem205Ok, I think it's depend on my provider because I can't establish a data connection
18:03.21excocr2: it should - but 0.7 is better than the versions before ;-)
18:03.47pH5cr2: how is the module connected? pci-express?
18:03.56excoradem205: imfloflo also couldn't get it to work (I even sent him the files straight from my SD card)
18:04.10radem205ok, so I'll wait :)
18:04.13radem205Do you have experience with keymapping exco?
18:04.30cr2exco: i'm familiar with the pppd internals for more than a decade, so that may be a problem
18:05.28cr2pH5: they say it's a mini-pci card, but linux sees it as an usb modem /dev/ttyACM0
18:05.36excono - 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.38radem205Because probably the only thing we have to do on the polaris is assigning the buttons right
18:06.02radem205rogro had already done that, but some buttons have the same gpio number
18:06.03cr2Bus 005 Device 004: ID 0ac8:c326 Z-Star Microelectronics Corp.
18:06.04cr2Bus 005 Device 003: ID 04e8:6773 Samsung Electronics Co., Ltd
18:06.06cr2Bus 005 Device 002: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technolo
18:06.25radem205so we have to figure out how egpio (extended gpio) works to let the buttons work
18:06.25cr2"Samsung" is the modem
18:06.47excoradem205: yes and someone explained it the other day how it works (some matrix) but I can't find it
18:07.33radem205dubbeld00 said something about egpio but it isn't enough to know how it works
18:07.35cr2P:  Vendor=04e8 ProdID=6773 Rev= 0.01
18:07.37cr2S:  Manufacturer=SAMSUNG Electronics CO.,Ltd.
18:07.39cr2S:  Product=SAMSUNG HSPA Modem
18:07.41excoCan one emulate a button press using haretconsole ?
18:07.44BalsatI 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.05cr2exco: no, but it'd be easy to create such command
18:08.18maejrep[w]Balsat: you probably don't have the framebuffer working
18:08.26cr2SendMessage()
18:08.34maejrep[w]if you are using htc_fb_console, it will put in a 1s delay after every printk
18:08.46excoso how do you check if the gpio you guessed is right, cr2?
18:08.48cr2maejrep[w]: now i can checkout the kernel source :)
18:09.00cr2exco: where ?
18:09.19radem205When 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.48excothat shouldn't be too hard, radem205
18:09.58maejrep[w]what device?
18:10.04cr2radem205: you need to have some idea how the "keyoard" is organized
18:10.28maejrep[w]if its a gpio matrix, you should see 2 gpios per key
18:10.44excomaejrep[w]: Polaris
18:11.41*** part/#htc-linux orux (n=jose@89.130.46.3)
18:13.40radem205maejrep[w]: Could you explain this line (haret output): "in1: in1-24(216)=0"
18:14.02radem205Rogro said that this line becomes "1" when pressing the call or hangup button
18:15.13radem205Exco: Did you get an output like this: "002.269 GPIOS GPGDAT: GPG3(195)=0" when you use haret to find the gpio?
18:16.03exco195 is left according to my notes
18:16.32tmztstadicon: what device do you have, why do you need i2ctools?
18:17.03radem205the numbers are wrong I know, but do you have such output?
18:18.05excoradem205: yes
18:18.58excowhat do you mean by "the numbers are wrong", radem205
18:19.10tmztcan we support all frequencies and use a table only for exceptions to the formula?
18:19.25radem205I mean that the number in my example are wrong and doesn't related to the polaris
18:19.39radem205do 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.43radem205can you do that?
18:20.34tmzthtcraphael-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.04excoradem205: 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.36excothat's why I was asking how to verify the findings
18:22.17radem205have you looked here: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation
18:24.32excoradem205: yes
18:24.54excoradem205: does that help someone if I put it like this:
18:24.56exco* select/enterin3: in3-22(278)=0/1
18:24.57exco* SD card presentin3: in3-26(282)=1
18:24.57exco* SD card absentin3: in3-26(282)=0
18:25.01excoon the wiki or somewhere
18:26.11*** join/#htc-linux cr2_ (n=cr2@ip-90-187-213-218.web.vodafone.de)
18:29.02radem205I don't know, it can't hurt I think
18:30.28radem205could you upload the complete output so everyone can see it and maybe some can working on it?
18:37.13excoradem205: 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.01radem205good 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.36excoif 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.54maejrep[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.03radem205maejrep[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.05maejrep[w]radem205: see http://wiki.xda-developers.com/index.php?pagename=Raphael_GPIO for an example
18:42.32maejrep[w]radem205: is it like the raphael where the area of the buttons is capacitive touch sensitive?
18:42.48maejrep[w]ie, just by touching it, does an led turn on or something to that effect?
18:43.04maejrep[w]or if in "watch gpios", does anything happen just by touching lightly?  also in "wirq"
18:43.41radem205as far as I know it isn't capacitive touch sensitive.
18:44.28maejrep[w]are there any other buttons that are like that?
18:44.38excomaejrep[w]:  in watch gpios nothing is happening when touching it lightly
18:45.15radem205the 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.20excomaejrep[w]: yes - volume up/down, voicedial, wheel cw/ccw
18:45.28maejrep[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.35maejrep[w]then do:  joinlist traces gpios
18:45.47radem205can you do this exco?
18:45.49maejrep[w]and do wirq 1 again, and ibit traces <chatty numbers>
18:46.09maejrep[w]then when you're satisified that you're ignoring the uninteresting bits, do:  wirq 5
18:46.14maejrep[w]and try each button
18:46.19maejrep[w]and see if it changes
18:46.19exco000.994     IRQS     IRQ0: USB_OTG(15)=1
18:46.20exco<PROTECTED>
18:46.30maejrep[w]ibit IRQS 15
18:48.30maejrep[w]radem205: are the other buttons the same also?  like OK + Win key / IE + Radio?
18:49.11radem205these buttons have different gpio numbers
18:49.25excoradem do you also have a Polaris at hand?
18:50.15radem205yes, but unfortunately I can't start haretconsole
18:50.19excoit'll take me a minute - deactivating the button actions real quick with aebuttons to make the tracing easier
18:50.33radem205ok, take it easy :)
18:50.37excoradem205: on win?
18:50.51maejrep[w]radem205: you can also just telnet to the ip, port 9999
18:51.12maejrep[w]ie if you're ocnnected to activesync:  telnet 169.254.2.1 9999
18:51.48radem205ok I 'll give it a try
18:52.57excowow I thought you had to setup usb networking to be able to do that
18:54.28excoI 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.03radem205maejrep[w]: what do you mean with chatty numbers?
18:57.08excoafter 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.31tmztnon-MD/NS, what is this?
18:57.47excoradem205: I suppose the stuff that comes up without you doing anything/spam so to speak
18:58.23NetRipperi'd really suggest using haretconsole
18:58.26NetRipperinstead of telnet
18:58.50excook I have it quiet now
18:59.12radem205ok nice
19:00.01excono touch-sensitive buttons (well the wheel - sort of ;-) ), maejrep[w]
19:00.44radem205do you have some interesting output exco?
19:01.12*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net)
19:01.14tcccpre
19:02.09excowheel cw http://pastebin.com/d77949d76
19:03.01excowheel ccw http://pastebin.com/d3975bbdb
19:05.37radem205Exco: http://forum.xda-developers.com/showpost.php?p=3202836&postcount=425
19:05.45excolooks 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.23radem205yes, the only thing what is different is the line "in1: in1-20(212)=1 @~800192c0"
19:08.04tmztso 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.39radem205it look likes Rogro has figure it out
19:08.56excoso that means obsolete work I guess ....
19:10.00tmztexco: 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.10tmztthis should work on arm also for wince amss's
19:10.21radem205I 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.34excotmzt: I don't really get what you're talking about (sorry)
19:12.05tmztwhat 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.05excothat may very well be because I don't know what I'm talking about :-(
19:15.03tmztyou asked about ppp didn't you?
19:16.11excowell I was asking if it could be done through a gui (shame on me) - but just out of curiosity
19:17.33tmztyeah, 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.52excocan i list the gpios/irqs currently ignored with ibit
19:18.58tmztcheck your logs
19:19.19tmztunfortunately I don't think you can/know how
19:19.42excoexiting haretconsole and connecting again resets it?
19:20.22tmztI think you have to close haret.exe itself,
19:20.37tmztor you want wbit 1..2000 or something like that
19:22.04excoyou'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.02excoto be honest ... I can't tell any difference between wheel cw & ccw (well at least it can look totally the same)
19:36.05excohttp://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.31radem205exco: It's vice versa, cw: in1-20 | in 1-15 and ccw: in1-15 | in1-20
19:42.26excoradem205: no - it's just a part of it
19:42.36*** join/#htc-linux dzo (n=dzo@121.98.128.127)
19:43.58excooh - you're right
19:48.13excoradem205:  no you're wrong in1-20=1 in1-15=1 in1-20=0 in1-15=0 is a circle
19:48.57radem205yes I know I was wrong :)
19:49.47excostill - if you turn left/right/left/right/left/right
19:50.10radem205I think I was right :)
19:51.15excothe 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.59radem205when 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.08cr2NetRipper: have you applied the .27 patch ?
19:53.11excoradem205: 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.37radem205hmm, when you have twice "1" and twice "0" and the in1-15 and in1-20 are vice versa it does make sense
19:56.32excothe software always knows the current state in1-20=0 for example?
19:56.41excothen I know how it work
19:56.43exco's
19:57.04excoeven if rogro already knows how to do it - it was still interesting finding that out
19:57.34radem205haha sure :)
19:58.16radem205but we can inform rogro about our findings and maybe he can optimized his code
19:58.33dcordesNetRipper: what's needed on the host side to use the usbnet?
19:59.08dcordesdoes raphael hang during boot while it is charging?
19:59.16dcordes(or diam)
19:59.40cr2hi dcordes
19:59.44dcordeshi
19:59.48cr2dcordes: 100% linux now
19:59.55dcordesI've seen it in the log. nice
20:00.24cr2there is one annoying samsung misfeature
20:00.50cr2if you loose the umts link, the modem drops your pin
20:00.51dcordesdid you mail laforge?
20:01.05dcordesok so modem works too
20:01.19dcordesI would disable the pin in that case
20:01.24*** join/#htc-linux timebomb (n=tb@e176115185.adsl.alicedsl.de)
20:01.26cr2no, i found the description by some polish guys
20:01.42cr2dcordes: hmm, how do you think i'm logged on ?
20:02.55cr2i'm downloading everything possible now. flatrate should be used :)
20:04.42excoradem205: you can point him to the wiki page if you like (I'll update that in a bit)
20:08.53tmztcr2: are you using fso-frameworkd?
20:11.17*** join/#htc-linux dzo (n=dzo@121.98.128.127)
20:13.25radem205ok I'll do that
20:13.33radem205when do you update the wiki?
20:14.18radem205because I think the latest developments are interesting for him
20:14.31dcordescr2: 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.42radem205thanks Exco (good job!)
20:22.38excodo you think that's right what I wrote about the wheel?
20:23.39cr2dcordes_: what is the value of CROSS_COMPILE= for the kernel ?
20:24.00cr2i've already forgotten how to compile the kernel :)
20:24.01NetRipperdcordes_, 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.18dcordes_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.34radem205yes I think it's good! Unfortunatly we don't know better :(
20:24.35NetRipperdcordes_, also try disabling 'advanced networking' in activesync settings on your phone.. also helps
20:24.48dcordes_cr2: the path to the toolchain prefix
20:24.55cr2bash: make: command not found
20:25.11NetRipperlol install gcc, make, autoconf, etc
20:25.44dcordes_build-essential
20:25.49cr2standard install is a bit strange
20:26.02cr2i'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.06JotaeLeHi all
20:29.06cr2hm. the atom is certainly not the amd64. but with make -j 3 it's bearable
20:29.44cr2cegcc svn is 4.3.2 now ?
20:30.32cr2hehe. the fans switched on
20:31.40dcordes_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.01NetRipperdcordes_, if you soft reset the phone.. dont connect the usb cable.. see if it boots then (without ever connecting usb)
20:35.04dcordes_dzo: did you have a look at kaiser wifi?
20:35.51dcordes_dzo: I will try building the driver in htc-vogue
20:36.32cr2dcordes_: vogue does not have wifi ?
20:36.32dcordes_NetRipper: I already know it's the charging that causes the freeze.
20:36.36NetRipperdcordes_, ok
20:36.46dcordes_cr2: htc-vogue branch
20:36.51dcordes_kaiser is in there
20:37.13NetRipperyou can set it not to charge when the usb cable is connected, maybe that helps you get into a shell?
20:37.20dcordes_good idea
20:38.22NetRipperyou should also verify all memory addresses in msm_iomap.h.. wrong mappings may also cause weird behaviour
20:38.24Untouchab1eGood evening all
20:38.27Untouchab1ehow's it going? :)
20:38.39maejrep[w]where does it freeze dcordes_ ?
20:38.58NetRipperat the end - during the stub messages
20:39.22maejrep[w]that's where I was getting freezes too
20:39.25dcordes_maejrep[w]: after mmc, rtc, trout_pwrsink_set:STUB! is printed a few times. then it freezes
20:39.32maejrep[w]but that was resolved with the activesync mode
20:39.35maejrep[w]for me
20:39.38excocr2: 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.42maejrep[w]dcordes_: .25 or .27?
20:39.51dcordes_.27 from linuxtogo
20:40.04maejrep[w]dcordes_: with HTCRAPHAEL mach type?
20:40.11NetRipperhm.. 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.21dcordes_sorry, I didn't copy the new kernel yet. still using the patch .27 kernel
20:40.28dcordes_yes, htcraphael
20:40.40*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbff04d.pool.einsundeins.de)
20:40.49maejrep[w]NetRipper: init=/sbin/bb or something like that?
20:41.03cr2exco: do you have the spl ?
20:41.05maejrep[w]not sure how to force init 1 (single user mode)
20:41.36NetRippersingle user mode is not the same as single threaded i think
20:41.36cr2maejrep[w]: i'm ready to compile the kernel
20:41.41excodcordes_: 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.07excocr2 spl?
20:42.08NetRipperto 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.27cr2exco: pwf polspl 0x0 0x100000
20:42.46maejrep[w]ah
20:43.07cr2exco: get power+sdio working first
20:43.37cr2hmm. atom is not that bad
20:43.51excoI don't know what "pwf polspl 0x0 0x100000" I did but it doesn't give any output
20:44.06cr2exco: in haret
20:44.15excocr2:  yes
20:44.42maejrep[w]exco: it writes a file to the same directory as haret.exe
20:44.46cr2maejrep[w]: the raph800 lcd init looks like a mix of epson+toshiba. i'm confused
20:45.01maejrep[w]cr2: and "display 2" tells me HITACHI
20:45.03maejrep[w]wtf?!!?!
20:45.04maejrep[w]:p
20:45.30excoyou want that file, maejrep[w], cr2?
20:45.43maejrep[w]cr2 is better equipped to make use of it :)
20:47.13cr2maejrep[w]: ok.
20:47.13cr2ar.c:(.text+0xa82): undefined reference to `yyparse'
20:47.14cr2hehe. bison is missing
20:47.15cr2how do i install all possible debian packages ?
20:47.15cr2tmzt: you are the debian guy
20:47.39dcordes_maejrep[w]: on the kovsky, keyboard slideout gpio seems to be mapping to card detect
20:48.03dcordes_I just slided out the keyboard and msm_sdcc initialized the card
20:48.09cr2maejrep[w]: hitachi is id=5
20:49.22cr2dcordes_: 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.45dcordes_cr2: what was the problem?
20:49.47*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
20:49.49AstainHellbringcr2 using raphs inet or usb?
20:50.14excocr2: you want it? what is it? what is it good for?
20:50.34cr2AstainHellbring: nc10 builtin usb
20:50.47cr2exco: yes, gzip it and put somewhere
20:51.00dcordes_cr2: did the debian shipped rndis modules work?
20:51.10cr2dcordes_: 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.16cr2<4>[    0.720091] ulpi: write 0x1d to 0x0d
20:52.17cr2<4>[    0.720305] ulpi: write 0x1d to 0x10
20:52.33dcordes_yea the configuration is not that intuitive
20:52.37cr2maejrep[w]: it is not clear if we really need it
20:53.36dcordes_maejrep: can I use i2c-tools instead of haret to sort out the keycodes?
20:54.03excocr2: www.excogitation.de/Android_on_Polaris/polspl.gz
20:55.01*** join/#htc-linux orux (n=jose@89.130.46.3)
20:56.27cr2exco: got it
20:57.45*** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-167-033.ewe-ip-backbone.de)
20:57.52excocr2: 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.34excothe 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.38dcordes_exco: which kernel do you use?
21:04.40excorogros
21:04.52dcordes_you should use the htc-vogue kernel
21:05.10excothe last time I tried - it wasn't booting on Polaris
21:05.32dcordes_did you build with polaris or kaiser defconfig?
21:05.54excorogro is using that branch afaik and making the neccessary changes - hope he pushes ist sometime soon
21:07.51dcordes_ok then. I thought about the old rogro kernel. did he put the patches?
21:08.32excohaven't seen any
21:08.47excoput you mean apply?
21:09.35dcordes_publish/provide/upload
21:09.55excoah - ok - then I haven't seen any - so no
21:10.38dcordes_exco: is there an active thread where you discuss the polaris related things?
21:10.49excobut he was talking in here on how to best setup ltg so it's easy to build for kaiser/vogue/polaris
21:11.19exconiki should also be considered I guess (since it's so similar)
21:11.31excodcordes_: http://forum.xda-developers.com/showthread.php?p=3202836#post3202836
21:11.54excoI'm keeping the wiki up to date http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux
21:14.37dcordes_ok thanks
21:27.19cr2omg. even awk is not installed
21:29.11cr2maejrep[w]: i'm thinking about the 7param formula, and it seems to me that the 48MHz clock is 32MHz in reality
21:30.29cr212*16=192
21:31.48cr2192*2=384
21:32.29dcordes_cr2: how can I trace kovsky IRQ ?
21:33.27cr2dcordes_: gpio irq , or msm irq ?
21:37.32dcordes_cr2: I see no irqs when I run wirq
21:37.40excodid anybody here try neocore on a msm7200 device yet (or does someone have the apk for me?)
21:37.54dcordes_exco: what's that?
21:37.57cr2dcordes_: do you use the 0x9* address or 0xb* ?
21:38.13excosome 3d benchmark
21:38.24cr2glxgears :)
21:38.29dcordes_cr2: I set nothing extra
21:38.38dcordes_http://wiki.xda-developers.com/index.php?pagename=Kovsky_GPIO updated
21:38.51cr2dcordes_: you had the same problem with i2c
21:38.54dcordes_cr2: I assumed 7201A is in git :>
21:39.19dcordes_haretconsole git
21:39.21cr2192*4=768
21:39.34cr2integer arithmetic is fun
21:39.44dcordes_yay
21:40.42*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
21:44.44cr2marex: do you still have n560 ?
21:45.03*** join/#htc-linux zycho_ (n=zycho@a89-183-89-249.net-htp.de)
21:45.22marexcr2, n560 yes, time no ;)
21:46.10cr2maejrep[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.05cr2marex: send it to kiozen
21:47.33*** join/#htc-linux Othello (i=Othello@gateway/tor/x-167742f2e2ab5215)
21:48.20marexcr2, send what ?
21:50.16cr2n560
21:52.26dcordes_what is a/m in Raphael_GPIO ?
21:52.41tmztapt-get install build-essential on ubuntu at least
21:52.43cr2arm11 arm9
21:52.52cr2a(pplication) m(odem)
21:53.02cr2cf. A2M
21:53.11marexcr2, are you serious ?
21:53.25dcordes_cr2: aka owner bit?
21:54.09dcordes_how can the a/m value be 4,0 ?
21:54.24cr2dcordes_: yes, the owner
21:54.38cr24,0 is a data entry bug
21:54.47cr2it'd be in the alt column
21:54.59dcordes_k
21:55.06cr24 is some mixture of drvstr+alt+pull
21:55.21tmztyou get awk/bison cr2?
21:55.34cr2which i need to decipher too ;)
21:55.40cr2tmzt: apt-get
21:55.54cr2marex: sure
21:56.07marexcr2, no
21:56.38*** join/#htc-linux infernixx (n=nix@unaffiliated/infernix)
21:56.43cr2marex: we will make some brain surgery on it.
21:57.00cr2marex: we want to finish the n560 support
21:58.43cr2marex: so we want to buy a device, which we can destroy in the process .
22:01.36marexcr2, so ... what ?
22:13.29tmztcr2: do you know what a-clock and b-clock refer to?
22:15.17cr2tmzt: 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.20cr2exco: what do you know about the polaris cpld ? does it have the same functions / bits as kaiser ?
22:17.49cr2polaris has BT_UART1_MODE, H2W_UART1_MODE and BT_H2W_MODE
22:18.01cr2is it the same as on g1 ?
22:18.49cr2wifi is sdc1, sd is sdc2
22:23.37cr2hehe. pola100 has 0xa2c for pmdh clk
22:27.24*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
22:27.42excocr2: do we have a console in android so I can check?
22:28.15cr2exco: i have never used android.
22:31.49*** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1)
22:34.11cr2exco: pola100 uses vreg(1,... for wifi and vreg(2,... for sd
22:34.43cr2it's tge same as g1 i think
22:35.23infernixxis the kaiser sd driver stable yet?
22:36.05infernixxi havent kept track of the efforts to get it working in PIO mode
22:36.06maejrep[w]cr2: 768MHz?  how?
22:37.27cr2no, it's not the same as g1
22:37.34maejrep[w][15:52:36]  <cr2> maejrep[w]: it is not clear if we really need it <-- need what?
22:37.55maejrep[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.57cr2maejrep[w]: this hardware usb bugfix.
22:38.13maejrep[w]what bug fix? :o
22:38.24cr2maejrep[w]: i don't know the usb internals
22:38.43cr2maejrep[w]: g1 code writes some values into phy, to fix some bug
22:39.15cr2maejrep[w]: imvho the 19MHz clock is 19.2MHz and 48MHz clock is 32MHz
22:39.39cr2i can provide you my rationale, but it's too long for irc :)
22:39.57NetRipperstart a blog
22:39.58NetRipper;)
22:40.01cr2LOL
22:40.15cr2this channel is very close to that ;-)
22:40.20NetRipperso true
22:40.52cr2maejrep[w]: i don't know if you can somehow use this information
22:41.11cr2the 32MHz rationale is very simple
22:41.27cr2compare the values for 12,24 and (48)
22:41.53cr2the arg3 is some pwm parameter, we have it as arg2/2
22:41.59excocr2: so with vreg and gpio known wifi should be a quick fix?
22:42.01cr2the rest is identical
22:42.26cr2the values are 12:24:xx -> 0x20:0x10:0xc
22:42.35cr2xx should be 32
22:43.05BabelOpopopolo !!!
22:43.11*** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net)
22:44.14cr2BabelO: ? :)
22:44.23*** join/#htc-linux konsta (n=asds@host81-154-247-76.range81-154.btcentralplus.com)
22:44.40NetRipperoh 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.43BabelOcr2: reading battery charge on omap :)
22:45.01cr2exco: you need to compile the tiacx driver. and add the power/detect functions for polaris
22:45.12cr2BabelO: nice
22:45.13NetRipperit has a .bat to easily start it when connected via activesync
22:48.40BabelOcr2: what kernel do you use on MSM ? i m still with 2.6.26 :(
22:50.00cr2BabelO: maejrep[w] uses .27
22:50.08cr2but it's buggy
22:50.21excocr2: 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.36cr2of course.
22:50.49BabelOcr2: can't be more buggy than windows :)
22:51.09cr2i 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.31excoGood night and thanks for all the -fish- - help I mean
22:51.32cr2adding 10 more layers of complexit
22:51.43BabelOcr2: i reach a new personnal record :) 34 days of windows XP without reboot, it is half working, but still works
22:51.43cr2bye
22:51.53cr2lol
22:52.14*** part/#htc-linux exco (n=exco@e181104124.adsl.alicedsl.de)
22:52.16cr2BabelO: i'll replace XP with suse LDS soon.
22:52.24BabelOwhat is LDS ?
22:52.39cr2LinuxDesktopSomething :)
22:53.15NetRippermaejrep[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.17cr2we have official support for it. and it's cheaper than XP :)
22:53.19NetRipperfor raph100
22:53.25BabelOcr2: ok :)
22:54.05cr2NetRipper: it's an i2c command ?
22:54.17NetRippercr2, on raph800 it's a gpio
22:54.22cr2NetRipper: hmm.
22:54.25NetRippercr2, at least, that's documented in wiki
22:54.32NetRipperi cant find it on raph100
22:54.49NetRipperalthough
22:55.07cr2ok
22:55.10NetRipperwhen doing an mmutrace i see values going 0-1
22:55.14NetRipperbut back right away
22:55.19NetRippernot consistently 1 = on and 0 is off or something
22:55.19cr2NetRipper: what about stylus gpio ?
22:55.23NetRippersec.
22:55.43cr2eventually i'll configure the wifi AP at home, and then can trace things too
22:56.01NetRipperyou 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.33cr2not anymore
22:56.53NetRipperlinux has ndis too, you can use your linux to connect to haret
22:57.03cr2maejrep[w]: i must honestly tell you that the 7200 lcd init is even a bigger pita than raph800 :)
22:57.49cr2NetRipper: need to finish the RE things first. with the precious time :)
22:58.01NetRippercr2, what is SCL and SDA?
22:58.15cr2i2c lines
22:58.19NetRipperhm
22:58.22maejrep[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.26cr2SerialCLock and SerialDAta
22:58.47NetRipperboth stylus and keyboard backlight seem to trigger SCL and SDA gpios
22:58.55NetRipper2-17 and 2-18
22:59.01NetRipperso they may be i2c after all
22:59.03maejrep[w]SCL and SDA i believe are only on alt funcs
22:59.14cr2NetRipper: it's better to mask all ALT gpios
22:59.30cr2because you never know what pops up there
22:59.51NetRipper2-17 and 2-18 are not alt, are they?
22:59.56cr2tracing makes real sense only with real=non-alt gpios
23:00.03maejrep[w]SCL and SDA are alt iirc
23:00.22NetRipperok so i have to ibit the gpio's that have 'alt' in their description?
23:00.23cr2any nongpio function is alt
23:00.32cr2yes
23:00.46maejrep[w]NetRipper: the "4,1" is what indicates that it's alt
23:00.50NetRipperso basically bank 5
23:00.52cr2we already know their purpose, so tracing is useless
23:01.25cr24 is alt, and 1 is for suspend/disable
23:01.26NetRippermaejrep[w], oh.. so any gpio that has a comma in the alt
23:01.37maejrep[w]i think
23:01.43maejrep[w]cr2 can explain it better
23:01.49maejrep[w]i'm not fully understanding it myself
23:01.51NetRipperbut still
23:01.58cr2NetRipper: i'm lazy, so i've saved me some time for editing
23:02.00maejrep[w]that's just what I understand of it
23:02.02NetRipperit's only 2-17 and 2-18 being triggered
23:02.07NetRipperno others
23:02.14maejrep[w]NetRipper: try mmutrace i2c
23:02.18maejrep[w]see if the backlight is done by i2c
23:02.33NetRipperdespite them being alt.. it should trigger other gpios if it were via gpios
23:02.35cr2the real "ALT" setting can be extracted from the CFG register value
23:02.39maejrep[w]i know others did say that they saw the backlight turn on with the keyboard driver
23:02.43maejrep[w]even though I don't
23:02.46maejrep[w]so I don't know why
23:02.53cr2but you need to know where are the drvstr,pull and alt bits there
23:03.03NetRippermaejrep[w], ok
23:03.13maejrep[w]cr2: have you confirmed that we can read the alt cfg from the same memory address?
23:03.23maejrep[w]does it need an A2M interrupt?
23:03.28BabelOcr2: what is FFS for you ?
23:03.40maejrep[w]for fuck's sake?
23:03.45cr2maejrep[w]: i need the blackstone wince kernel for that, to be 100% sure
23:03.50maejrep[w]ah
23:03.54NetRippermaejrep[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.56maejrep[w]why blackstone and not others? :p
23:04.35maejrep[w]NetRipper: also note that windows does some stuff as a result of pulling the stylus
23:04.49cr2NetRipper: stylus gpio may be an irq (wakeup too)
23:04.49maejrep[w]so it might be better to watch irqs instead
23:04.56maejrep[w]cr2: it is wakeup
23:05.09maejrep[w]when you pull the stylus, it turns the device on
23:05.12cr2look for unassigned wiki irqs
23:05.37cr2BabelO: in the battery context ?
23:05.50BabelOcr2: no
23:05.54BabelOcr2: it is that
23:05.57BabelO#define GSM_FFS_VIRTUAL_ADDRESS 0xc3f00000
23:05.58BabelO#define GSM_CODE_VIRTUAL_ADDRESS 0xc3b00000
23:06.16cr2no idea
23:06.29maejrep[w]cr2: can amss be dumped from memory?
23:06.46maejrep[w]or perhaps extracted from stock rom?
23:06.56tmztimgfs
23:07.35NetRippermaejrep[w], http://netripper.pastebin.com/m61f1db65
23:07.40dcordes_is somebody able to edit xda wiki?
23:07.48dcordes_I get the blank page problem
23:08.19maejrep[w]NetRipper: can you do that as mmutrace, not traces? :)
23:08.32NetRipperoh
23:08.40NetRipperah
23:08.41NetRipperoops
23:08.41NetRipper:)
23:08.44NetRippermy mistake
23:09.36maejrep[w]dcordes_: sometimes that's related to the type of markup you use
23:09.50maejrep[w]try using old style, or tweaking your wiki code
23:10.54NetRipperer
23:11.04NetRippermmutrace is not showing anything
23:11.23cr2maejrep[w]: when titan came out (first known htc msm7x00 phone) it was possible, but then they have closed that hole (i think)
23:11.24maejrep[w]addlist mmutrace 0xb2300000 1  & addlist mmutrace 0xb230000c 1
23:11.58cr2maejrep[w]: amss can be extracted from update .nbh
23:12.28*** join/#htc-linux Balsat (n=kll@87.72.13.87)
23:12.40cr2or from googel .ota or how it is called, as tmzt said
23:12.55maejrep[w].ota?
23:13.00maejrep[w]i mean for our devices
23:13.05cr2.nbh
23:13.11maejrep[w]so it can be extracted from the stock rom .nbh?
23:13.28cr2but i'd better looked at ota g1 version :)
23:13.35cr2yes
23:13.51NetRipperhm
23:14.48NetRippercr2, why do i have to trace i2c on 0xb2300000.. instead of p2v(0xa9900000)? is the phys address wrong in wiki?
23:15.09maejrep[w]cause p2v() will by default give you an untraceable virt address
23:15.21NetRipper:s
23:15.26NetRippernice.
23:15.27maejrep[w]b23* is the same physical address, but it's traceable
23:15.35cr2maejrep[w]: sometimes
23:15.45maejrep[w]if you do dump mmu 2 a9900000 you'll see 2 mappings
23:15.51dcordes_shrugs
23:15.52cr2yes
23:15.57dcordes_I just skipped the preview :P
23:16.40cr2NetRipper: actually, you should trace all virtual mappings of 0xa9900000
23:16.59NetRippermaejrep[w], http://netripper.pastebin.com/d251ed37d
23:17.01cr210 drivers can ioremap it to 10 $randomadress
23:17.05NetRippercr2, oh
23:17.15NetRippercr2, it's that issue where you wanted Kevin2 to update haret for
23:17.23cr2yes
23:17.59maejrep[w]interesting
23:18.03dcordes_http://wiki.xda-developers.com/index.php?pagename=Raph800GPIODump task 55
23:18.07dcordes_is this debug console?
23:18.07maejrep[w]it considers the stylus a keyboard event ;oi
23:18.17NetRippermaejrep[w], /me cries
23:18.19maejrep[w]dcordes_: that's spl
23:18.37dcordes_the usb debug port?
23:18.39NetRippermaejrep[w], it's a scancode you didnt map before?
23:18.40dcordes_usb>serial
23:18.41maejrep[w]in raph, hold vol down and power + soft reset until the tri-color bootloader
23:18.58maejrep[w]NetRipper: no, no scancode
23:19.02maejrep[w]dcordes_: yes
23:19.03dcordes_ok
23:19.08maejrep[w]then use mtty to connect
23:19.11maejrep[w]and task 55
23:19.15dcordes_I had that in kovsky wince dmesg
23:19.18dcordes_no need :)
23:19.21cr2dcordes_: it's some conspiracy :)
23:19.37cr2maejrep[w]: mtty == cu/minicom
23:19.43NetRippermaejrep[w], is it something hard to implement? i have no clue on what im seeing
23:19.48maejrep[w]NetRipper: it's in the upper byte of the scancode, which microp-keypad is ignoring now
23:19.55maejrep[w]ok
23:20.12cr2maejrep[w]: pH5 has written some similar tool, and pof too
23:20.28maejrep[w]0xce,10 -> "tell microp i want to read channel 10 of 0x67 chip address"
23:20.38maejrep[w]the next two responses with ..c==______
23:20.44maejrep[w]are the responses from the chip
23:20.50maejrep[w]in this case, 2 bytes are being read off the chip
23:20.56maejrep[w]for keyboard scancodes, we only look at the first byte
23:21.05cr2ce,10,2,x
23:21.08maejrep[w]in this case, the stylus is 0x01 on the upper byte
23:21.15cr2is a wiki 'ism for that
23:21.29*** join/#htc-linux stadicon (n=liberost@79.107.28.155)
23:21.30maejrep[w]cr2: the ,2 means "read 2 bytes"?
23:21.38cr2buffer size
23:21.41NetRipperand when its 0x00 on the upper byte, it's removed?
23:21.43stadiconhi
23:21.47cr2x means buffer ptr
23:21.47maejrep[w]cause i can never tell if you mean how many bytes, or to *write* 0x02 :p
23:22.06maejrep[w]NetRipper: no, the 0x80 is the removal
23:22.18NetRippermaejrep[w], ok
23:22.25cr2maejrep[w]: in most cases it's some wince function, which was documented at the bottom
23:22.25maejrep[w]for keyrelease events, you get <scancode>|0x80 on the lower byte (1st byte)
23:23.11maejrep[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.14cr2maejrep[w]: i may have entered something inconsistently, but i'll try to be more accurate now :)
23:23.53maejrep[w]so that's how we'll detect stylus
23:24.20maejrep[w]NetRipper: looks like your driver is different from mine
23:24.30NetRippermaejrep[w], as im not really understanding this.. can you update wiki with this info?
23:24.34dcordes_how does msm_fb know which panel to use?
23:24.35maejrep[w]mine reads ce,10 then ce,11 then sets LCDs, then reads ce,10 and ce,11 again
23:24.38cr2maejrep[w]: stylus is an i2c event on raph100 ? sounds very complex for a wakeup irq
23:25.00maejrep[w]cr2: possibly not - but it *is* received as a keyboard event apparently
23:25.09maejrep[w]it might also be provided as a gpio, but can't tell that for sure yet
23:25.17cr2dcordes_: you can query the gpios, which define it.
23:25.19maejrep[w]NetRipper: anything useful on opening keyboard slider?
23:25.29dcordes_cr2: how to do that?
23:25.30NetRipperkeyboard slider = gpio
23:25.37maejrep[w]NetRipper: i mean the backlight
23:25.44NetRippersec.
23:25.54NetRipperi'll also have to press a key though
23:25.55maejrep[w]which would be on cc,*
23:26.01maejrep[w]it doesn't turn on just by opening?
23:26.07cr2dcordes_: i think there is a sample implementation in the g1 source. which applies to g1 only, though.
23:26.11NetRipperyes
23:26.43cr2maejrep[w]: was it possible to control the backlight with the haret-w.exe ?
23:26.54maejrep[w]cr2: forgot to try it ;x
23:26.59NetRippermaejrep[w], http://netripper.pastebin.com/m67823143
23:27.03maejrep[w]but i was able to control the other leds in linux
23:27.06maejrep[w]with i2cset
23:27.25cr2maejrep[w]: check it, the we may consider merging the code into mainline
23:27.49cr2s/the w/then w/
23:28.09cr2but it only does on/off
23:28.26cr2i don't know a portable way to change the brightness
23:29.49NetRippermaejrep[w], this is better: http://netripper.pastebin.com/m6e944774
23:29.50maejrep[w]i haven't played with brightness yet
23:30.05BabelOgood night
23:30.30cr2BabelO: good night
23:30.34maejrep[w]hmm
23:30.45maejrep[w]NetRipper: cc,40,0f,65 is interesting
23:30.50maejrep[w]I don't think I tried that one
23:31.34maejrep[w]adds to his todo list
23:31.55NetRippermaejrep[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.01NetRipperenlighten*
23:32.17NetRipperenglishten is because of the time of day
23:32.27maejrep[w]ok, so a better understanding of it will come from reading i2c-msm.c
23:32.31maejrep[w]but here's the short version
23:32.32NetRipperok
23:33.56cr2maejrep[w]: what is cc,20,2,0 ?
23:34.34NetRippercr2, from wiki: cc,20,02,00 - lcd poweron related
23:35.13cr2NetRipper: yes, i've put it there :) but what does 'related' mean
23:35.20NetRipperah ;)
23:35.47maejrep[w]NetRipper: http://netripper.pastebin.com/m498a5e3f
23:36.10maejrep[w]cr2: I don't recall
23:36.52maejrep[w]NetRipper: in reality, that 0x01 and 0x79 on lines 5 and 6 are the 1st and 2nd byte
23:37.00maejrep[w]0x23 is just the data address, not really a "first byte"
23:37.44maejrep[w]NetRipper: but everything you see there is handled by i2c-msm
23:38.43maejrep[w]so, all you need to know are:  write to chip 0x66, data 0x23, buffer { 0x01, 0x79 }
23:39.09maejrep[w]and:  write to chip 0x66, data 0x33, read from chip 0x66, length 2
23:39.23maejrep[w]and the driver takes care of translating it
23:40.08NetRippermaejrep[w], ok..
23:41.29maejrep[w]does that make sense? :P
23:41.34NetRipperim trying
23:41.36maejrep[w]I can back up if you'd like
23:41.47NetRipperlet me tell you what i understand now
23:42.37NetRipperthose lines 3-6, are they by the i2c driver or by the hardware?
23:43.36NetRipperhow does the driver know what the hardware wants to tell (thus what command to send?)
23:44.16maejrep[w]c== is the hardware
23:44.20maejrep[w]b2300000 =  is from the driver
23:44.32maejrep[w]b230000c==  is from the hardware
23:44.34NetRipperok
23:44.52maejrep[w]so, +0 is send, +0xc is recv
23:45.03NetRipperyes
23:45.10maejrep[w]0x4 is the status buffer, but we don't need to deal with that
23:45.21maejrep[w]and i forgot what 0x8 is
23:45.23NetRipperok so.. an interrupt occurs.. but how does the driver know which chip to 'poll'?
23:45.35maejrep[w]it knows by the interrupt
23:45.45NetRipperan interrupt doesn't pass any data, does it?
23:45.47maejrep[w]so...  say gpio 27 interrupt is raised
23:45.59maejrep[w]the driver knows "gpio 27 is the keyboard interrupt"
23:46.02NetRipperah
23:46.05maejrep[w]so its the keyboard driver that has hooked that interrupt
23:46.16maejrep[w]therefore it is going to read ce,10 and ce,11
23:47.07NetRipperok and how does i2c know the hardware will send 2 bytes, and not 20?
23:47.30maejrep[w]it doesn't have to -- the driver knows
23:47.47maejrep[w]so, driver knows that ce,10 returns 2 bytes, therefore it tells the i2c bus driver "give me 2 bytes"
23:47.54NetRipperok
23:48.15NetRipperso the i2c bus driver simply stops after those 2 bytes as it assumes it's done
23:48.19NetRipperok
23:48.52NetRipperok and now back to the sequence.. cc,40,0f,65... you got that from my pastebin, right?
23:49.48maejrep[w]yes
23:49.52maejrep[w]and yes
23:50.00maejrep[w]line 44
23:50.05maejrep[w]is where it starts
23:50.17maejrep[w]it's all write (there is no read related to it)
23:50.31NetRipperah
23:50.36maejrep[w]the only reads you'll see on chip 0x66 (cc) is most likely for either version info or ADC (light sensor)
23:50.43lavender-thello guys, anything tricky about the MSM_FB stuff in .27 ?
23:50.49maejrep[w]or to read the current LED status i guess
23:51.32maejrep[w]so, 0x100 means "chip address".  0x200 means "last byte", and 0x01 means "read"
23:51.37maejrep[w]i'm sure there are more flags
23:51.49NetRippermaejrep[w], so the first sequence is cc, 23, 1, 79? when the keyboard  is opened
23:52.01maejrep[w]yes, and it's a write
23:52.13NetRipperoh, we only care abou treads?
23:52.16NetRipperreads*
23:52.27lavender-ti realized msm_mddi0_device is not there any more ?
23:52.29maejrep[w]so you're writing 0x0179 to data address 0x23 of chip 0x66
23:52.42maejrep[w]lavender-t: it was moved i think
23:52.47NetRippermaejrep[w], ok
23:52.55maejrep[w]hmm
23:53.02maejrep[w]actually, that might be 0x7901
23:53.09maejrep[w]will have to check endianness again :p
23:53.39maejrep[w]but either way, you'd send it in that order as a byte array
23:53.43NetRipperok
23:54.11maejrep[w]so:  buffer = { 0x23, 0x01, 0x79 }; i2c_master_send( client, buffer, 3 )
23:54.41NetRippermaejrep[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.14maejrep[w]and the next one down would be:  i2c_master_send( client, "\x33", 1 );  i2c_master_recv( client, buffer, 2 );
23:55.14NetRipperthe driver should indicate somehow like 'ok give me the next byte'
23:56.04maejrep[w]I don't think so, I think its just a series of "wait_for_.." polls
23:56.24cr2lavender-t: the raph800 lcd init seems to be tricky
23:56.49maejrep[w]<PROTECTED>
23:57.05NetRipperhm ok
23:57.06maejrep[w]<PROTECTED>
23:57.07cr2lavender-t: i've put the last nail into the SD clocks story. the 19MHz clock is 19.2 and 48MHz is 32MHz ;)
23:57.07maejrep[w]etc
23:57.12NetRipperok
23:57.19NetRipperit uses the other bytes for that
23:57.43maejrep[w]actually
23:57.49maejrep[w]yes
23:57.51NetRippermaejrep[w], im starting to put it together a bit :)
23:57.52maejrep[w]but there is an interrupt
23:57.54maejrep[w]:)
23:57.55lavender-tcr2: oh that's cool :)
23:58.28NetRippermaejrep[w], thanks for your explanation
23:59.03maejrep[w]<PROTECTED>
23:59.03maejrep[w]<PROTECTED>
23:59.03maejrep[w]<PROTECTED>
23:59.03maejrep[w]<PROTECTED>
23:59.23lavender-tmaejrep[w]: after the console handover and the 2 vibras, nothing showed up on the screen
23:59.42lavender-ti wonder if you hit that in .27 as well ?
23:59.46cr2maejrep[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)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.