IRC log for #htc-linux on 20090110

00:04.01*** join/#htc-linux addman3333 (n=skool@cpe-67-9-134-92.austin.res.rr.com)
00:08.35*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
00:12.49lupine_85forest.dh.bytemark.co.uk :)
00:15.35*** join/#htc-linux reformatt (n=chatzill@97-121-31-187.bois.qwest.net)
00:22.50*** join/#htc-linux addman3333 (n=skool@cpe-67-9-134-92.austin.res.rr.com)
00:24.31lupine_85can people resolve forest.lupine.me.uk ?
00:25.12skoddeforest.lupine.me.uk has address 89.16.178.98
00:25.57lupine_85good good :)
00:27.39*** join/#htc-linux NetRippah (n=netrippe@netripper.nl)
00:27.41NetRippahwhat's the touchscreen driver .dll on wince? :p
00:29.09j0b0dcordes, if you're here, I tracked down the thing that makes X11 draw for me -> http://forum.xda-developers.com/showthread.php?p=3145682
00:30.33tmztj0b0: can you like to the post?
00:30.37tmztlink
00:32.06j0b0http://forum.xda-developers.com/showpost.php?p=3145682  ?
00:32.47lupine_85j0b0: ooh
00:33.01lupine_85means i can has working X angstrom
00:33.59j0b0i would like to see that confirmed, but yes it would mean that :D
00:35.51j0b0it doesnt make sense that it wouldnt work before because the hack inquestion was in place for as long as i can remeber until recently
00:36.25tmztdo you have the update calls in the tsts thread?
00:38.32*** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net)
00:40.13j0b0lupine_85 can you boot this kernel and see if X draws -> http://tibook.jb.b4m.com/j0b0/zImage-vdh-jobo
00:41.12j0b0its git + raphael gpio buttons + this fb hack
00:49.42balsat3I got the Angstrom X up on my Diamond (GSM)
00:49.55balsat3nice
00:50.33j0b0can you move the pointer?
00:51.19balsat3It just crashed
00:52.07j0b0if you just start the xfbdev without anything else, does it stay up?
00:52.16RZK333no progress with making Nike's touchscreen\hardbuttons work?
00:52.33balsat3Just a min
00:52.50lupine_85j0b0: not right now...
00:53.59j0b0np .. just curious
00:54.29balsat3What shall i run?
00:54.46balsat3It startet auto
00:54.54balsat3with the /sbin/init
00:56.06lupine_85mwahahahahahahahahahahahahahaha
00:56.10lupine_85soon though
01:00.22lupine_85boots it
01:00.52lupine_85it lets psplash work
01:00.58*** join/#htc-linux NetRipper (n=netrippe@netripper.nl)
01:03.42*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
01:03.50*** join/#htc-linux MethoS (n=clemens@host-091-097-245-045.ewe-ip-backbone.de)
01:06.00madCoder-heading home
01:07.44lupine_85j0b0: it works, but the cursor is offset
01:08.02j0b0but you can move the pointer?
01:08.10lupine_85yep
01:08.15lupine_85that's fine
01:08.20j0b0awesome
01:08.28j0b0i never got that conected right
01:08.55lupine_85I think
01:09.02lupine_85the coords are from the centre of the screen
01:09.19lupine_85the offset of the X cursor from the touchpad changes depending on where on the screen I touch
01:09.39lupine_85no, top-left
01:09.40j0b0sound like a calibration thng
01:09.45lupine_85(in portrait mode)
01:09.54lupine_85the top-left is in the right place
01:10.05lupine_85then it gets more and more off the closer to bottom right I get
01:10.13j0b0so the lcd is 2x bigger than the ts
01:10.33lupine_85I can't use the vkeyb any more either
01:10.39lupine_85(before, the offset wasn't there)
01:11.42j0b0try calibrating the ts manually after boot
01:12.18lupine_85how does one do that?
01:12.29lupine_85(I manually calibrate atm on boot)
01:12.39balsat3I can use the vkeyb under psplash
01:12.44j0b0oh thats what i mean
01:12.44lupine_85leave the calibration till after?
01:12.52lupine_85(i.e. when X is up)
01:12.53j0b0not by kernel option
01:13.00lupine_85mm, I do right now
01:13.09lupine_85and the vkeyb worked in psplash
01:13.14lupine_85so it's X-related
01:13.56j0b0thats weird because the vkeyb is ..uhm.. hard wired
01:14.22lupine_85I think X might capture/transform the pointer input somehow?
01:14.54lupine_85will try with vkeyb off, and calibrating post-x-boot
01:14.58j0b0but the vkeyb sits between the ts and the /dev/input/whatever
01:15.02lupine_85if it'll let me calibrate that late
01:15.58j0b0it will let you calibrate at any time
01:16.18j0b0even when you dont see the messages.
01:16.34j0b0the 1st 3 taps are the calibration
01:17.23lupine_85msmvkeyb_toggle, right ?
01:18.22j0b0that turns on/off or hides the vkeyb. calibrations is msmts_calib=xmin.ymin.xmax.ymax (iirc)
01:22.50NetRipperif you leave the msmts_calib param out, then you can calibrate on the console... it'll print the values you need ni your msmts_calib
01:26.10*** join/#htc-linux zycho_ (n=zycho@a89-183-89-74.net-htp.de)
01:42.30*** part/#htc-linux exco (n=exco@e181079020.adsl.alicedsl.de)
01:55.20lupine_85no vkeyb seems to mean psplash doesn't work
01:55.33tmztah
01:56.03lupine_85it might be calibration-related
01:56.09lupine_85since stuff shows up on the first taop
01:56.11lupine_85now to bed
02:01.38*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
02:12.41*** join/#htc-linux piusvelte (n=irchon@71.175.8.29)
02:15.19*** join/#htc-linux piusvelte (n=irchon@71.175.8.29)
02:21.26maejrepcr2, did you look at the navi's datasheet eyt?
02:21.28maejrepyet*
02:23.58tmzthey, cr2 has two new wiki pages
02:24.13tmztRaphaelPSOC
02:24.17tmztMSM_SDIO
02:24.40tmztI think we have all the information to write a keyboard driver for raph now
02:25.14tmzttsc2003.c is a working i2c client which is a little different then yours, it uses i2c_master_read/write instead of i2c_transfer
02:27.14maejrepah
02:27.38maejrepthe cap sensor data sheet doesn't provide any useful programming documentation
02:29.02tmztwe can get the keyboard working on work on adding that later though?
02:29.20tmzts/on work/and work/
02:29.39maejrepof course ;p
02:30.17maejrepoh, nice
02:30.52tmztyou can also add the key detect to the driver as android will expect and we can work on a true touchscreen driver for userspace later
02:31.50tmztjust to be sure of this, how many irqs do you get when touching (not pressing) the navi?
02:32.02tmzthow many times do you get the irq I mean
02:32.09tmztin haret
02:32.32maejrepit fires repeatedly IRQ1/"GPIO group 2", whenever the finger moves
02:32.48maejrepand .. the "Cap sense" gpio irq from the wiki
02:32.54tmztbut if you keep it still it stops?
02:32.57maejrepyes
02:33.32tmzthas haret been fixed to handle the gpio mux yet
02:33.50maejrepnot mine
02:34.05maejrepand I don't fully understand what that means, or I'd take a stab at it :)
02:34.41tmztif we know the address of the gpio status registers in msm we can just watch those with haret
02:35.12tmztbut it matters if you get multiple or repeated irqs from each touch
02:35.20tmztand it appears you don't
02:35.52*** join/#htc-linux Othello (i=Othello@gateway/tor/x-51528b347a5a773c)
02:38.27maejrephmm, looks like my haret dumps have some sequences that aren't listed here (for the keyboard)
02:39.04maejrepoh nevermind, that was cc (still not listed, but not as important yet :p)
02:40.10maejrepbtw, according to the teardown, the navi controller is a cypress cy8c20434
02:40.26tmztsimilar to atmega?
02:40.39tmztor is this a seperate chip
02:40.50maejrepseparate chip
02:40.53tmztok
02:41.30maejrepso I already knew how to read from the keyboard :p  question is what the data means
02:43.06tmzttreat it as a scancode
03:02.28*** join/#htc-linux daspsycho (n=Tim@HSI-KBW-082-212-005-059.hsi.kabelbw.de)
03:09.25*** join/#htc-linux AndyCR (n=Andy@71-211-39-196.clsp.qwest.net)
03:18.35*** join/#htc-linux Shinto (n=John@g227197208.adsl.alicedsl.de)
03:24.52*** join/#htc-linux swc|666 (n=coooter@unaffiliated/swc666/x-4934821)
03:57.20*** join/#htc-linux gaintdot (n=gaintdot@59.83.208.5)
04:00.06*** join/#htc-linux gaintdot (n=gaintdot@59.83.208.5)
04:14.38*** join/#htc-linux gaintdot (n=gaintdot@59.83.208.5)
04:18.48*** join/#htc-linux dzo (n=dzo@121.98.128.127)
04:35.42*** join/#htc-linux Othello (i=Othello@gateway/tor/x-761ac77d1ec56860)
04:41.10*** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net)
04:48.29*** join/#htc-linux Mullins (n=bw@89.204.244.196)
04:51.28addman3333<PROTECTED>
04:51.38addman3333mine goes into fits of static
04:54.22*** join/#htc-linux Laeed (n=laeed@87-231-160-234.rev.numericable.fr)
04:55.02tmztit's raph500
04:55.22addman3333the sprint one?
04:55.27tmztno, verizon
04:56.34addman3333mines sprint and its fine(just switched colors) for a while but then it goes staticy and then everything is shifted and wraps from one side to the other
04:56.53tmztinteresting, I haven't heard that before
04:57.02tmztwhat kernel are you using and what filesystem?
04:58.01addman3333http://members.home.nl/j0b0/zImage-clean-jobo and lavender's file system with LordKiwi initrd
04:58.18tmztfrom today?
04:59.06addman3333http://forum.xda-developers.com/showthread.php?p=3140435#post3140435
05:02.48addman3333screen shot at all useful?
05:02.55tmztyeah
05:03.05addman3333k
05:03.07tmztit's probably the update error though
05:03.41addman3333is there a new fs image/ initrd that might help?
05:04.12tmztwe might have one with a real keyboard soon which should fix most of the problems related to the on-screen keyboard
05:04.45tmztother than that j0b0 is working on the vkeyb
05:05.35addman3333cool, just thought I'd mention it sinice I hadn't seen anyone else talking about it
05:20.13addman3333Shifted: http://dl.getdropbox.com/u/18488/DSC_6715.jpg
05:21.40*** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net)
05:21.57*** join/#htc-linux mdrobnak (n=mdrobnak@pool-96-232-187-37.nycmny.fios.verizon.net)
05:27.07tmztaddman3333: what does your phone say under the battery?
05:30.06addman3333raph800
05:30.43addman3333warped version: http://dl.getdropbox.com/u/18488/DSC_6739.jpg
05:30.45tmztcan you try a different raph800 kernel?
05:30.50addman3333sure
05:30.55*** join/#htc-linux zule (n=zule@shadowmite.com)
05:31.53*** join/#htc-linux Othello (i=Othello@gateway/tor/x-3010180e80305cc2)
05:32.01maejrepthat's odd
05:33.29maejreptmzt, just documented the keycodes on the wiki
05:34.11tmztcool
05:34.18tmztwe need to get that from fuze also
05:34.27maejrep(not used to his wiki yet :/)
05:34.44maejrepyeah, I noted that these were from raph800
05:36.29mdrobnaktmzt: What do you need from the fuze?
05:37.14maejrepi'm not sure that the 13-reg stuff was correct, its kind of hard to decipher what cr2 means on the wiki some times :P
05:37.28mdrobnakIf you point me to a kernel / userspace program, I can do whatever testing you need..
05:37.35maejrepI did it in haret
05:37.49mdrobnakFor the keycodes?
05:37.55maejrepyeah
05:38.08mdrobnakOk, how do I do that?
05:38.20mdrobnakgets phone from across room
05:38.26maejrepibit the irqs you don't want, and:  addlist mmutrace 0xb2300000 1
05:38.35maejrepaddlist mmutrace 0xb230000c 1
05:38.53maejrepthen wirq
05:39.00tmztyou can ibit 0..1000
05:39.03tmztwbit <irq>
05:39.04mdrobnakok, the only thing I've used in haret is the default.txt and booting Linux :-)
05:39.05maejreptrue
05:39.13mdrobnakHow do I start?
05:39.13maejrepyou don't even need any irqs tmzt
05:39.25mdrobnakDo I need to do this over usb?
05:39.26tmztthen don't wbit
05:39.41maejrepyou can
05:39.44maejrepI do
05:40.00mdrobnakI have putty on the phone iteself, too.
05:40.02mdrobnak*itself
05:40.03maejrepconnect to your PC so you get a 169.254 IP, then hit "listen for network connections" and run haretconsole
05:40.13maejrepwon't help us :)
05:40.15mdrobnakah
05:40.33mdrobnakWait, I'm in Linux, I can do that. hehehe
05:40.34mdrobnakone sec
05:40.56mdrobnaklooks for usb cable - never around when you need it
05:41.11tmztbluetooth or wifi will work also
05:41.15maejrepright
05:41.21maejrepor evdo for that matter (in a pinch :P)
05:41.27maejrep*data
05:41.32tmztin wm?
05:41.33maejrepevdo for me ;p
05:41.36tmzthow do you do that?
05:41.43maejrepsprint doesn't block ports
05:41.58maejrepjust go to whatismyipaddress, and start up haretconsole ;x
05:42.00tmztand has public ip?
05:42.02maejrepyes
05:42.05mdrobnaklol
05:42.06mdrobnaknice.
05:42.12mdrobnakWifi
05:42.15mdrobnakI can do wifi
05:42.33mdrobnakI left my extra USB cable at work :-(
05:42.35maejrepI'm so glad I got rndis-host working on this machine :D
05:43.02maejrepI used to do it through either data or wifi, but my wifi signal here sucks, and my cell reception is even worse
05:43.35mdrobnakheh
05:43.46mdrobnakok wifi connected
05:43.50mdrobnakWhere do I get haretconsole?
05:44.06tmzthandhelds.org/~koconnor/haret/
05:44.41mdrobnakLatest version is fine?
05:44.47maejreppreferred
05:45.09tmztmatch haret and haretconsole version
05:45.46mdrobnakohhh
05:46.15mdrobnakhmm there is none with that late of a version hehe
05:46.20mdrobnakI'll use latest
05:47.15maejrepwhat i found worked best, was to turn off auto brightness adjust on the phone (since that controls the backlight via i2c, it'll get in the way), and use 'wirq 1' commands.  as soon as it starts, press a key and hold it until wirq goes back to the console (open the Notes app if you'd like :P)
05:47.35mdrobnakyay, haret.
05:48.02maejrep~the 5th line down will be the keycode:
05:48.13maejrep000.536     IRQS     IRQ1: GPIO2(33)=1
05:48.14maejrep000.536 7803d720: str    r3, [r5]       # b2300000 =000001ce
05:48.14maejrep000.536 7803d790: str    r3, [r5]       # b2300000 =00000010
05:48.14maejrep000.536 7803d878: str    r3, [r5]       # b2300000 =000001cf
05:48.14maejrep000.536 7803d940: streq  r2, [r5]       # b2300000 =00000200
05:48.14maejrep000.536 7803d944: ldr    r3, [r3]       # b230000c==00000033
05:48.23tmzthave you looked for the table in the registry?
05:48.42maejrep:|
05:48.44tmztwhat's the insn?
05:48.54maejrepinsn?
05:49.19tmztdump 7803d944
05:49.24tmztdump 7803d944 4
05:49.35maejreppdump?
05:49.49tmztis in phys?
05:49.55tmzts/in/it/
05:50.22maejrepoh that
05:50.31maejrepI don't know..  appears to be incrementing though
05:50.49maejrepI thought you were asking me to dump that heh
05:50.55maejrepand now haret is unhappy :(
05:51.39maejrepway to go tmzt you made me reboot my phone!  :P
05:51.55mdrobnaklol
05:51.58tmztmaejrep: yeah, I'm trying to see if we can add this to haretconsole
05:52.07mdrobnakUgh I need the toolchain for arm don't I?
05:52.14maejrepbut yeah, no idea what that number is
05:52.26maejrepmdrobnak, for what?
05:52.33mdrobnakI get this:
05:52.33maejrepharetconsole is python
05:52.46mdrobnaksh: arm-linux-objdump: not found
05:52.46mdrobnak000.050 7805d5f4: e5933000(ldr)         # b230000c==00000000
05:52.46mdrobnak000.050 7805d5f4: e5933000(ldr)         # b230000c==00000002
05:52.46mdrobnak000.088 7805d5f4: e5933000(ldr)         # b230000c==00000000
05:52.57maejrepo.0
05:53.04mdrobnakThat was hitting the PTT key
05:53.19mdrobnakwhich is the only thing I can think of that's different on the Fuze vs RAPH100
05:53.27maejreptry "a" :p
05:53.29mdrobnak(Not sure if I did this right)
05:53.30maejrep(start simple)
05:53.53maejrepyou'll see the "1ce,10,1cf,200,____"
05:54.41maejrepon my phone, 'a' is 11  (00000011)
05:55.33mdrobnakhttp://pastebin.com/d656fdb79
05:55.42mdrobnakI am doing something wrong, or missing something..
05:56.15maejrepibit irqs 0..999
05:56.46mdrobnakARGH
05:56.52mdrobnakI hate that the Wifi TURNS OFF with the screen
05:57.02maejreplol
05:57.05maejrepmine doesn't
05:57.21maejrepwell, i'm always plugged in when I do anything, so its charging
05:57.51mdrobnakI just said never turn off on battery :-D
05:57.53maejrepOEM='HTC-P4600'  :x
05:57.57mdrobnakYep.
05:58.02mdrobnakThat's what's under the battery.
05:58.07maejrepi think that's the first raph that doesn't report as raph
05:58.23mdrobnakAnyone else done that on a Fuze?
05:58.30maejrepdone what?
05:58.45mdrobnakconnect using Haret
05:58.56maejrepprobably..  dunno
05:59.16tmztmaejrep: that's a sprint?
05:59.27maejrepmine is, his is at&t
05:59.39maejrep(the P4600 is his, the fuze)
05:59.43tmztoh, his is a fuze?
05:59.46tmztraph110?
05:59.53maejrepno, HTC-P4600
05:59.54maejrep:)
06:00.31mdrobnaklol
06:00.40mdrobnakYeah, Fuze. I always thought it was the RAPH110
06:00.56*** join/#htc-linux zule (n=zule@shadowmite.com)
06:01.04maejrepheh it is
06:01.08maejrepI'm just being obnoxious
06:01.19mdrobnakok. Too late / early to tell any more
06:01.19mdrobnakhehe
06:02.50mdrobnakok, I did the ibit, then a wirq 1 and got even less
06:03.12mdrobnakHaRET(24)# ibit irqs 0..999
06:03.12mdrobnakHaRET(25)# wirq 1
06:03.12mdrobnakirq:8001c338@A03F43F8=811850ec abort:8000104c@A03F43F0=81185110 prefetch:8001bea8@A03F43EC=8118513c data=81144000 sizes=c:000014e4,t:000454e4
06:03.12mdrobnakBeginning memory tracing.
06:03.12mdrobnakWatching IRQS(00): Addr 95300080(@c0000080)
06:03.14mdrobnakWatching IRQS(01): Addr 95300084(@c0000084)
06:03.16mdrobnak00: Mapping b2300000(@a9900000) accesses to e1100000 (tbl a9902402)
06:03.18mdrobnakMMU table merging disabled
06:03.20mdrobnakReplacing windows exception handlers...
06:03.22mdrobnakFinished installing exception handlers.
06:03.24mdrobnak000009: mem IRQS(0) 95300080=00000000 (00000000)
06:03.26mdrobnak000009: mem IRQS(1) 95300084=00000002 (00000000)
06:03.28mdrobnakRestoring windows exception handlers...
06:03.32mdrobnakFinished restoring windows exception handlers.
06:03.34mdrobnakHandled 286 irq, 234 abort, 913 prefetch, 0 lost, 0 errors
06:03.36mdrobnak(oops, sorry about that)
06:03.38mdrobnakdidnt think it was that much text.
06:03.50mdrobnakI held down the "a" key during that
06:04.01tmztmaejrep: if we just consider the ldr line and wirq 20 or whatever, would that give us the keycodes?
06:04.14tmztwhat is the reason for doing wirq 1 for each key?
06:04.44maejrepamong other things
06:04.59maejrepwirq is because that keycode gets ORed with 0x80 on release
06:05.05maejreper, wirq 1
06:05.26maejrepso it was easier for me to get the initial key code by making sure it didn't catch the release event
06:06.20maejrepthe 'ldr' line is the response from each command.  in on key down event there are 4 command responses, each 2 bytes/lines
06:07.01maejrepmdrobnak, did you press it before starting?
06:07.24tmztok
06:07.40mdrobnakno, right after
06:10.06maejrepcause I'm not seeing what I would expect to see
06:10.20mdrobnakI dunno
06:10.25maejrepi get like 40+ lines for a key down event
06:10.26mdrobnaktouching the touch pad does stuff
06:10.31mdrobnaktouching the PTT does stuff
06:10.35maejrephmm
06:10.43mdrobnakVol Up / DOwn
06:11.01maejrepdo you see the "1ce" byte?
06:11.07maejrep000.536 7803d720: str    r3, [r5]       # b2300000 =000001ce
06:13.06maejrephttp://privatepaste.com/e4nIMI4MoF
06:13.41mdrobnakhttp://pastebin.com/d213c54f6
06:13.46mdrobnaklol
06:14.49maejreptry wbit irqs 33
06:14.53maejrepthen wirq 5
06:15.45mdrobnakNope, just lots of 000.304     IRQS     IRQ1: IRQ33(33)=1
06:15.56maejrepwhen you touch the navi, is the output scrolling by really fast?  Or it's just irqs?
06:16.16maejrepprobably a different location for i2c :x
06:16.24tmztyeah, it won't trigger without an irq
06:16.24mdrobnakscroll really fast
06:16.46maejrepbut is it the memory addresses, or IRQs?
06:16.53tmztraph100/110 should match the trout location
06:16.55mdrobnak003.519 7805d5f4: e5933000(ldr)         # b230000c==00000036
06:16.55mdrobnak003.519 7805d5f4: e5933000(ldr)         # b230000c==0000009f
06:17.00maejrepok
06:17.01mdrobnakThat type of data
06:17.04maejrepyeah that's what you want
06:17.07*** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net)
06:17.09mdrobnakThats from the Navi
06:17.11maejrepare you see the "1ce" line?
06:17.13maejrepyep
06:17.28mdrobnakI see 1c4 and 1c5 lines
06:18.22maejrep1c4 is the navi address
06:18.33tmztit will work better with the cross compiler objdump
06:18.52maejrepbut if you don't touch the screen and only hit a key on the keyboard, it should show you different ids
06:19.26mdrobnakok let me try once more
06:19.45mdrobnakabsolutely nothing
06:19.59mdrobnakanyo other possible IRQs to watch?
06:20.09mdrobnakor memory locations?
06:20.35mdrobnakand when you say keyboard, you mean the real keyboard, right?
06:20.57mdrobnaknot keypad.
06:20.57maejrepyeah, the qwerty
06:20.57maejrepslide out
06:20.57mdrobnakNevermind
06:20.59mdrobnakYou told me to hit "a"
06:21.03mdrobnak(sorry sleepy)
06:21.15maejrep:x
06:21.38mdrobnakI got about another 10 minutes in me before it's absolutely time for bed..
06:22.03maejrepso you were hitting the a key on the keyboard before right, but no output?
06:22.07mdrobnakcorrect
06:22.11maejrepinteresting
06:22.18maejreptry watch gpios 5 and do the same
06:22.27mdrobnakWTF
06:22.35maejrepwill probably need to ibit gpios 290 241 242
06:22.35maejrep:p
06:22.36mdrobnakI don't know what happened
06:22.41mdrobnakit worked this time
06:22.47maejrepheh
06:23.17mdrobnakok so what am I looking for again? lol
06:23.28maejrepabout 4-5 lines after the first "1ce" line
06:23.28mdrobnak1ce abnd 1cf
06:24.02maejrepits the first response from the b230000c address
06:24.02mdrobnak011 ?
06:24.03maejrepk, that's the same as raph800
06:24.11maejrepif you want to compare:  http://wiki.xda-developers.com/index.php?pagename=RaphaelKeyboard
06:25.22mdrobnakI'm curious to see what my "OK" button is
06:25.24maejrepthe main ones to check would be the bottom and left keys
06:25.44maejreplike TXT, SYM, Email
06:25.47maejrep(on mine)
06:25.53mdrobnakNice
06:25.59mdrobnakOK = 2f == CTRL
06:26.02maejrepi wouldn't be surprised if its just a relabeled key
06:26.05mdrobnakYep
06:26.17maejrepon the bottom left?
06:26.20mdrobnakyep
06:26.23mdrobnakb3 = calendar
06:26.37maejrepI don't have a b3 :p
06:26.49maejrepis that a FN key?
06:26.54maejrepI didn't try that :x
06:27.30mdrobnakSee
06:27.33mdrobnakargh
06:27.40mdrobnaknow I accidently got into the calendar
06:27.45mdrobnakand now the keyboard doesnt scan again
06:27.46mdrobnakwtf
06:27.52maejrephmm
06:28.08mdrobnakOops
06:28.46mdrobnakwirq 1 does NOT work
06:28.49mdrobnakmust be wirq 5
06:29.13mdrobnakok lemme try that calendar key again, with wirq 5
06:29.37maejrepits probably your wifi
06:29.47maejrep:P
06:30.30maejrepjust confirmed the modifier keys do *not* change the keycodes
06:30.49maejrepweird thing is I don't have a calendar key
06:30.56maejrepwhere is it positioned?
06:31.22mdrobnakRight next to the OK
06:31.27mdrobnakbottom row
06:31.28maejrepnot a FN key ?
06:31.34mdrobnakNo
06:31.37mdrobnakFn is over shift
06:31.46maejrepnot caps lock? :P
06:31.54mdrobnakThats above FN
06:31.57maejrephaha
06:32.38mdrobnakhttp://www.wmexperts.com/tags/touch-pro?page=3
06:32.42maejrephttp://www.phonewreck.com/images/htc_touch_pro_landscape.jpg
06:32.45mdrobnakScroll to bottom of page
06:33.21mdrobnakScancodes are probably same, layout is different
06:34.02mdrobnakWhats the scancode for your TXT key?
06:34.02mdrobnakIts probably not a keyboard scancode
06:34.03*** join/#htc-linux Othello (i=Othello@gateway/tor/x-bf5580b89b1f56e2)
06:34.12maejrep34
06:34.17maejrepthat wiki page was from my session with haret :p
06:35.40maejrepalso found what I think is initialization code for the accelerometer ;x
06:36.37mdrobnakOk, here's interesing
06:36.41mdrobnakso if I hit the special keys
06:36.46mdrobnakLike contacts
06:36.50mdrobnakit delays till haret is done
06:36.53mdrobnakbut then opens contacts
06:37.33maejrepstrange, haret should be passing everything through
06:39.08mdrobnakI'm getting frusttraded
06:39.31mdrobnakI must be missing something I did the last time by accident
06:40.36mdrobnakwhat is 1cc?
06:40.59mdrobnak230000 = 000001cc
06:43.30mdrobnakAll right, I'm going to sleep
06:43.32mdrobnakgood night
06:45.17maejrepcc is for leds and backlights
07:01.32*** join/#htc-linux Othello (i=Othello@gateway/tor/x-3ce4d18839502d77)
07:12.02*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
07:21.42XDanyone know what verizon calls it's pro
07:21.46XDvz?
07:22.00XDvzx8 something or other
07:23.09*** join/#htc-linux _workkaze (n=kaze@ABordeaux-152-1-37-213.w83-193.abo.wanadoo.fr)
07:35.08*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfe8c0.pool.einsundeins.de)
07:44.56*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
08:16.06XDcan anyone help with scott crosiers VZ rom 3.0 install? for vx6850... I'm completely lost and been reading forums for a few hours.
08:28.57*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
08:30.34*** join/#htc-linux RyoohkiNagas (n=Ryoohki@92.116.73.130)
09:18.19*** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl)
09:32.30*** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com)
09:34.51*** join/#htc-linux nooo (n=nooo@ip24-250-54-217.ri.ri.cox.net)
09:57.13*** join/#htc-linux pichurri (n=pichurri@194.230.146.53)
10:00.49*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
10:07.54*** join/#htc-linux Armand (n=Armand@SantaYnez-11-116.resnet.ucsb.edu)
10:07.56*** join/#htc-linux timebomb (n=tb@e176106254.adsl.alicedsl.de)
10:11.22*** join/#htc-linux Xime (n=xime@bankize.net)
10:13.54*** join/#htc-linux DJWillis (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:18.51*** join/#htc-linux neowangdue_ (n=neowangd@117.192.138.209)
10:19.01neowangdue_hello
10:19.10neowangdue_anyone out there
10:19.11neowangdue_?
10:19.29neowangdue_please help me ....
10:21.05neowangdue_i have HTC winCE mobile connected via USB to my linux system... i am using haRETconsole.. to get information about the phone
10:21.47neowangdue_but to use it i need to have its htc phone IP address....
10:22.06neowangdue_so can anyone tell me how to do that
10:25.02pichurrineowangdue_, usually what I do is connect via wifi, if you do it this way, you can check the ip address on the settings/info for the wifi connection...
10:25.33neowangdue_i don't know that
10:25.38neowangdue_how to do that
10:26.05neowangdue_can you please me connect
10:26.06pichurrineowangdue_, but can you connect via wifi?
10:27.08neowangdue_i went into it settings->connections
10:27.20neowangdue_there is no wifi in the list
10:27.28*** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net)
10:27.53neowangdue_beam, dialup gprs,proxy vpn
10:28.20j0b0pichurri: did you see this post by hillsdale
10:28.37pichurrij0b0,  which?
10:28.45j0b0oh sorry. http://forum.xda-developers.com/showthread.php?p=3144934
10:28.50j0b0(forgot to paste)
10:28.57j0b0havent had my coffee yet :/
10:30.41pichurrij0b0, jajaja
10:30.50pichurriwhat time is it there?
10:33.35j0b011:30 AM (CET)
10:36.12pichurrihum, where do you live?
10:36.22pichurrilike country...
10:37.47*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
10:37.57j0b0.nl
10:39.20pichurrion the capabilities I dumped I got "Mfr_Name = 4ca3" and you got "Mfr_Name = D263", so, I'm not sure about that
10:39.57pichurribut, its a good start and I'll look into it, still don't have an idea of how...:P
10:46.35*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c680.pool.einsundeins.de)
10:55.32pichurrij0b0, http://groups.google.com/group/android-kernel/browse_thread/thread/62d7670f9a543a7e
10:55.59pichurriwouldn't it be wise to move to 2.6.27 if android is going to run on it for some time?
10:56.01pichurri:p
11:06.07*** join/#htc-linux LunohoD (n=alex@e180076202.adsl.alicedsl.de)
11:06.26*** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net)
11:17.16*** join/#htc-linux MethoS (n=clemens@host-091-097-245-045.ewe-ip-backbone.de)
11:18.05*** join/#htc-linux tsdogs__ (n=tsdogs@net70-16.metalit.net)
11:19.26*** part/#htc-linux tsdogs__ (n=tsdogs@net70-16.metalit.net)
11:24.53*** join/#htc-linux tsdogs__ (n=tsdogs@net70-16.metalit.net)
11:24.55*** part/#htc-linux tsdogs__ (n=tsdogs@net70-16.metalit.net)
11:32.11*** join/#htc-linux metter (n=metter@24-81.1-85.cust.bluewin.ch)
11:38.35*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
11:55.55*** join/#htc-linux LunohoD (n=alex@e180076202.adsl.alicedsl.de)
11:56.25*** part/#htc-linux LunohoD (n=alex@e180076202.adsl.alicedsl.de)
12:00.19*** join/#htc-linux daspsycho1 (n=Tim@HSI-KBW-082-212-005-059.hsi.kabelbw.de)
12:00.40*** join/#htc-linux PoohbaLT1 (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net)
12:04.17*** join/#htc-linux timebomb (n=tb@e176106254.adsl.alicedsl.de) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfe8c0.pool.einsundeins.de) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux Shinto (n=John@g227197208.adsl.alicedsl.de) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux balsat3 (n=kll@87.72.13.87) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux maejrep (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net) [NETSPLIT VICTIM]
12:04.17*** join/#htc-linux lupine_85 (n=lupine_8@work.lupine.me.uk) [NETSPLIT VICTIM]
12:09.45*** join/#htc-linux dwaradzyn (n=chatzill@chello089079197022.chello.pl)
12:14.25dwaradzynpichurri: hi. about blackstone lcd: i think there is a clock "magic number" in mddi0_panel_power (board-raphael.c or board-blackstone.c). the number is 0x1387. i tried several other number and screen seems to be corrupted in a different way when changing this value
12:19.24*** join/#htc-linux LunohoD (n=alex@e180076202.adsl.alicedsl.de)
12:19.52dwaradzyncan anyone with diam/raph try to change this value and test if produces corruption similiar to blackstone one? (http://www.youtube.com/watch?v=NzZRxEgu440)
12:19.56*** part/#htc-linux LunohoD (n=alex@e180076202.adsl.alicedsl.de)
12:25.05dwaradzynif anyone is willing to test it, post results here. i'll check the logs for answer
12:40.49*** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl)
13:03.23*** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net)
13:24.49*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
13:48.41*** join/#htc-linux konsta (n=asds@host81-154-247-76.range81-154.btcentralplus.com)
14:00.44dcordes_lupine_85: did you try ts_calibrate ?
14:08.33*** join/#htc-linux puregenius (n=chatzill@brln-4d0ccbe7.pool.mediaWays.net)
14:19.32dcordes_lupine_85: I would try running the calibration from the raph ts driver and then calibrating using ts_calibrate or the xtscal
14:19.46*** join/#htc-linux MethoS- (n=clemens@host-091-096-215-195.ewe-ip-backbone.de)
14:26.59dcordes_~seen stefan_schmidt
14:27.00aptstefan_schmidt <n=stefan@p5B037C9B.dip.t-dialin.net> was last seen on IRC in channel #htc-linux, 14h 44m 10s ago, saying: 'And I need a buildsetup for it when we like to do more testing'.
14:35.19lupine_85dcordes_: ooh, keyboard progress
14:35.28lupine_85dcordes_: nope, didn't know that tool existed
14:35.40lupine_85will look into it
14:36.38dcordes_lupine_85: keyboard progress sounds good. did you improve the driver? the X image should have everything needed for ts cal
14:47.49*** join/#htc-linux yoyey (n=507db079@67.159.35.76)
14:50.51dcordes_dzo: are you around?
14:51.45*** join/#htc-linux yoyey (n=507db079@67.159.35.76)
14:52.12*** join/#htc-linux metter_ (n=metter@72-187.62-81.cust.bluewin.ch)
14:56.08*** join/#htc-linux yoyey (n=507db079@67.159.35.76)
15:11.06*** join/#htc-linux MethoS-- (n=clemens@host-091-097-244-195.ewe-ip-backbone.de)
15:14.18*** join/#htc-linux MethoS_ (n=clemens@host-091-097-245-077.ewe-ip-backbone.de)
15:20.40*** join/#htc-linux MethoS (n=clemens@host-091-097-241-241.ewe-ip-backbone.de)
15:20.58*** join/#htc-linux Mullins (n=bw@89.204.242.200)
15:21.41*** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk)
15:37.21*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
16:03.55*** join/#htc-linux dream_kill (n=nospam@87-194-186-187.bethere.co.uk)
16:13.39*** join/#htc-linux pichurri_ (n=pichurri@194.230.146.2)
16:19.59*** join/#htc-linux myxor (n=myxor@pdbn-4d089da5.pool.mediaWays.net)
16:20.41*** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net)
16:28.31dcordes_Mullins: hi. did you try pio?
16:32.45Mullinshi, not yet. working on it
16:33.02dcordes_I just tried it and put my results in the forum
16:33.19dcordes_doesn't seem to work
16:35.37*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
16:57.35*** join/#htc-linux mustangsal66 (n=MustangS@pool-72-82-245-90.cmdnnj.fios.verizon.net)
17:08.42*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
17:14.25*** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl)
17:15.06radem205hey dzo
17:20.29*** join/#htc-linux mickeyl (i=mickey@openmoko/coreteam/mickey)
17:29.24*** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-166-109.ewe-ip-backbone.de)
17:32.36dcordes_Mullins: I was just about to flash the 1.65.24.36 radio but the file linked to in the wiki seems broken. do you know a mirror?
17:34.17*** join/#htc-linux AndyCR (n=Andy@71-211-39-196.clsp.qwest.net)
17:34.23dcordes_nvm. the linked Thread has several mirrors available
17:37.53*** join/#htc-linux Othello (i=Othello@gateway/tor/x-74f90c9c7f3fdd68)
17:40.19*** join/#htc-linux silven (n=zmc@64.209.10.12)
17:40.25Mullinsdcordes: ok, I have it here if you need it
17:41.02dcordes_KAIS_Radio_Only_1.65.24.36_CustomRUU
17:41.07dcordes_flashing now
17:47.52dcordes_Mullins: the front keypad and arrow/softkeys on the qwerty are not mapped correctly in git
17:48.18dcordes_Mullins: did you have any luck with the touchscreen?
17:52.46*** join/#htc-linux Zinbolic (n=Zy@84.238.80.215)
17:53.57dcordes_Mullins: ok with that radio SD works well. I think my kaiser just turned to some standby mode
17:57.15Mullinsdcordes: yes, the power management. Could not get it out of that
17:57.44Mullinsdcordes: The key mapping was temp till Dzo got the cursor keys working. Want a copy of that keyoad file?
17:57.57Mullinss/keyoad/keypad/
17:58.04dcordes_yes I can put it in git
17:59.47dcordes_1.7 radio and non-PIO kernel: DMA problems
17:59.47dcordes_1.7 radio and PIO kernel: sd initializes but doesn't seem to work - can't boot from / on sd, even with 15 seconds rootdelay
17:59.50dcordes_1.65.24.36 and non-PIO kernel: no DMA problems
17:59.53dcordes_1.65.24.36 and PIO kernel: sd initializes but doesn't seem to work - can't boot from / on sd, even with 15 seconds rootdelay
18:01.20silvenAnyone here subscribed to the arm LKML?
18:05.12*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
18:10.59Mullinsdcordes: what do you use for MTYPE in default.txt?
18:11.51dcordeskaiser
18:12.15*** join/#htc-linux pH5 (n=ph5@p5485F315.dip.t-dialin.net)
18:12.49Mullinsdcordes: what is MTYPE actually used for because I have been using Vogue MTYPE?
18:13.15dcordesit tells the kernel which machine you use
18:15.29maejreppichurri_, I agree, we should move to 2.6.27
18:16.27pichurri_:)!
18:17.38pichurri_maejrep, I haven't got much time lately, but I guess once we get android 1.0 on blackstone, (mmc is the same as diamond apparently), the next would be 2.6.27...or perhaps just go straight to 2.6.27...
18:18.17maejrepI checked out 2.6.27, but didn't start porting over our patches
18:18.54pichurri_maejrep, thou, I've been looking at it, and halibut code changes a lot, and I'm kind of lost, first time doing kernel/driver stuff, so it takes me longer than most of you I guess...
18:19.28pichurri_maejrep, also, no msm experience, jajaja...
18:20.17maejrepsame for me on both accounts :p
18:20.47maejrepI've made about 3 attempts at an i2c driver, and it keeps freezing my phone and can't figure out why :p
18:21.09pichurri_maejrep, it seams that google will stick for some time to 2.6.27, we can benefit from that, as there wouldn't be any "big" changes...so
18:21.25maejrepI'm starting to realize now that certain gpios have to be acknowledged, but trying to figure out how to do that
18:28.40j0b0pichurri_ i dumped the entire mddi_info struct in mddi_add_panel() in mddi.c maybe you can tell from that what you need to add in the 0x4CA3 panel...  http://tibook.jb.b4m.com/j0b0/mddi_info-raph100.txt
18:28.46j0b0hope it helps :)
18:30.17maejrepj0b0, have any tips on that issue I'm having with irqs? :)
18:30.45pichurri_thanx! I'll look into it
18:30.54j0b0let me scroll up a bit..
18:32.48maejrepits only a few lines
18:33.17maejrepI have an i2c driver that can read and write data on i2c chip, but as soon as I add irq support to it and trigger the irq, the machine freezes
18:33.21j0b0the gpios thing? when i was fiddling with that i found that requesting an irq for certain gpios is a bad thing
18:33.57j0b0otherwise you poll on a timer?
18:36.17j0b0(and if so, did that let you control or inquire devices?)
18:37.19maejrepi2c?
18:37.35j0b0uh huh
18:37.56maejrepyeah
18:38.12pichurri_bye! have to go. Thanx.
18:38.12maejrepits just that without the irq it becomes less meaningful :p
18:39.09j0b0dude! :D do we know which device is which (like camera, leds, keyboard, vibrator, ..)
18:40.53maejrepvibrator is on proc_comm, which also works heh
18:41.02*** join/#htc-linux piusvelte (n=irchon@71.175.8.29)
18:41.02maejrepleds and keyboard yes
18:41.15*** join/#htc-linux tekkdrone (i=tekkdron@72.183.115.231)
18:41.18maejrephaven't messed with camera, other than a haret mmutrace, but not much gleaned from it yet
18:41.50maejrepexcept that it seems to send a lot of data to the bus, rather than reading from the bus
18:43.21dcordesMullins: can you confirm dzo's observations with the AMSS/modem crash with lateset git revision?
18:43.38dcordesbbiab
18:44.29Mullinsdcordes: I could not get the Kaiser SMD code to work and I had to leave it out
18:50.06Mullinsdcordes: Dzo has got Kaiser specific SMD stuff and Vogue specific stuff. I find the Vogue stuff doesn't work of course but it doesnt cause a reboot or anything. The Kaiser stuff from today started producing a lot of messages and was able issue and receive data but was not very stable and Android only started every now and then so I left it out of the zImage for the moment
18:50.16j0b0when i was playing with gpios and irqs, i wrote some testing code ( http://tibook.jb.b4m.com/j0b0/board_htcraphael-gpiotest.c.txt ) i stole the basic workings from input/misc/gpio_input (or _event or so) it has an irq handler and a timer. the irq handler disables irqs and has the timer fire at +0 then the timer re-enables the irq. i found that not doing that made the irq fire exactly once (it also has some android power suspen
18:50.17j0b0d lock around it)
18:51.18j0b0it wouldnt freeze the device tho. did you post that driver anywhere?
18:53.20maejrepno
18:53.59maejrepit seems to be a combination of using an interrupt and interacting with the i2c chip
18:54.20maejrepcause I think I also got it to work without freezing if I used the interrupt and just printed without writing to i2c
18:56.02*** join/#htc-linux MethoS-- (n=clemens@host-091-097-243-030.ewe-ip-backbone.de)
18:56.18Mullinsdcordes: because my zImage is using the Vogue machine type at the moment, it only works with MTYPE 1667 for Vogue. I have just tried it. In future I will include default.txt and will compile with Kaiser as machine type
18:56.34*** part/#htc-linux silven (n=zmc@64.209.10.12)
18:57.11maejrep004.014     IRQS     IRQ1: GPIO2(33)=1
18:57.12maejrep004.014   TRACES      in1: in1-11(203)=0 @~8001d730
18:57.12maejrep004.014 7803d720: str    r3, [r5]       # b2300000 =000001ce
18:57.12maejrep004.014 7803d790: str    r3, [r5]       # b2300000 =00000010
18:57.12maejrep004.014 7803d878: str    r3, [r5]       # b2300000 =000001cf
18:57.13maejrep004.014   TRACES      in1: in1-11(203)=1 @~78042ab8
18:57.41maejrepso, i can either watch gpio2 irq, or use gpio 1-11 when its falling
19:07.34*** join/#htc-linux balsat (n=kll@87.72.13.87)
19:07.41maejrepok, so now I'm seeing what you said about it only firing once
19:08.35j0b0like disabling the irq in the irq handler and reenabling it in the timer makes it ready to fire again
19:08.37maejrepj0b0, you saw that we can read data from the navi now (just not in a driver yet)?
19:09.22j0b0from linux or only from haret
19:09.36maejrepfrom linux I can use i2cdump to see the values
19:09.59maejrepand kind of mapped out my best guess as to what each byte means: http://wiki.xda-developers.com/index.php?pagename=Raphael_Navi
19:10.01dcordesMullins: yea I think it's better to use kaiser machine type. regarding the smd stuff: with the latest commit, the 1.65 radio and kaiser machine type, I had the same result as you described above. I was able to receive data but it seemed unstable with some errors.
19:10.32dcordesI was able to receive all of the AT data but send didn't seem to work well
19:11.24Mullinsdcordes: here is the keypad with the front keys changed for navigation -> http://paste-it.net/public/u3b8da1/
19:11.25dcordesyou say android only starts every now and then depending on smd code. it might be better to use angstrom initrd for testing since it performs no smd operations on bootup
19:11.40dcordesMullins: does it also add the direction and softkeys on the keyboard?
19:11.45Mullinsdcordes: with Dzos latest stuff too so OK for GIT if you want it in there
19:11.56Mullinsdcordes: yep
19:12.19*** join/#htc-linux silven (n=zmc@64.209.10.12)
19:12.59silvenIs there anything that would make __lookup_processor_type return 0 (invalid cpu) besides an incorrect definition in id.c?
19:13.38Mullinsdcordes: Can you briefly explain how to add tslibs to angstrom? Want to play with that a bit...
19:14.06dcordesMullins: I can build you an image with X and tslib installed
19:14.26Mullinsdcordes: That would be great thanks
19:14.45Mullinsdcordes: Nice to have the keypad working now in Angstrom :)
19:14.47dcordesdo you think we should readd arch/arm/mach-msm/AudioPara.c ?
19:15.18Mullinsdcordes: yeah, must've been taken out by mistake
19:15.20dcordesdzo: removed it on accident I believe
19:15.23dcordesok
19:15.56j0b0maejrep let me look at that a bit closer .. so that i understand whats going on :)
19:18.10*** join/#htc-linux MethoS-- (n=clemens@host-091-097-243-030.ewe-ip-backbone.de)
19:19.19*** join/#htc-linux puregenius (n=chatzill@brln-4d0ccbe7.pool.mediaWays.net)
19:19.44Mullinsdcordes: Would it be OK to go to something like this for Kaiser Android Wiki -> http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
19:19.59Mullinsdcordes: I can do it and keep the existing content maybe?
19:20.48dcordesMullins: good idea. it might be better to remove existing content and start from scratch
19:21.14Mullinsdcordes: OK
19:21.19dcordesI pushed the keypad diff and audio readd
19:21.39Mullinsdcordes: I will rob their template. They will never find out
19:21.44dcordes;P
19:24.43*** part/#htc-linux silven (n=zmc@64.209.10.12)
19:27.05*** join/#htc-linux ricky_ (n=ricky__@81-208-74-191.ip.fastwebnet.it)
19:27.50dcordesMullins: this is an initrd with X11 http://linuxtogo.org/~lgorris/builds/OE/x11-image-120708.cpio.gz
19:28.55dcordesI'm not sure if it has ts_calibrate. will build an uptodate x11 image with everything included. do you need any extra packages installed?
19:29.21*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
19:29.31Mullinsnot at the moment, thanks. Won't be needing ts_calibrate I think
19:29.56*** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde)
19:31.44*** join/#htc-linux camden (n=camden@ancnat2.apto.aptalaska.net)
19:33.10dcordesMullins: ok. all of the kaiser, diamond, raphael images at http://linuxtogo.org/~lgorris/builds/OE/ are built for the correct arch
19:33.48*** part/#htc-linux Guest61730 (n=ricky__@81-208-74-191.ip.fastwebnet.it)
19:35.38camdenwhere can I find the cupcake build?
19:36.16*** join/#htc-linux mdrobnak (n=mdrobnak@pool-96-232-187-37.nycmny.fios.verizon.net)
19:36.21mdrobnakHey everyone
19:37.04*** join/#htc-linux olemaegbaekmadse (n=olemaegb@0703ds1-ar.0.fullrate.dk)
19:37.55dcordeshi mdrobnak
19:38.08camdenhi mdrobnak
19:38.36*** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231)
19:38.49mdrobnakSo it looks like we're making progress on the keyboard stuff, but Haret was giving me some issues, and a lack of sleep didn't help lol..
19:40.54camdenI don't know much about programming but I have an HTC Fuze and I know my way around linux. anything I can do to help?
19:41.09mdrobnakcamden: Test stuff :-)
19:41.20mdrobnakcamden: That's what I'm doing at the moment for the most part..
19:41.44camdenfair enough
19:42.19mdrobnakIf you hang around here, things will go on that you can help test with
19:42.24mdrobnakwhich device do you have?
19:42.34mdrobnaknmv
19:42.36mdrobnak*nvm
19:42.59mdrobnakI have a Fuze also, and was testing out some of the keyboard stuff last night
19:43.02camdenI have successfully booted from the instructions in the wiki, and I have booted with jobo's newer zImage
19:43.15camdenanything I can help with?
19:43.40mdrobnakcamden: The one with Volume Up / Down and prelimiary keypad support?
19:43.52camdenI... think so.
19:44.29mdrobnakYeah thats the latest one I've used as well
19:44.39camden708b1b349fb07266a9bf446a095b98b8  zImage-clean-jobo
19:44.41camdenthat one
19:44.42mdrobnakwas doing some debugging with HaRET last night
19:44.55mdrobnakOh, no that's newer then then one I've used
19:45.26mdrobnakJust as a general FYI - I'm filling out my rebate form for AT&T , and it's listed as : "HTC P4600 (Fuze)"
19:45.48camdennice
19:46.06mdrobnak(We've all been going back in forth about the "official" name)
19:46.36camdenI see
19:47.04*** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl)
19:47.13camdenI dream of a day when my Fuze and my n810 live together in an Android Utopia
19:47.21mdrobnaklol
19:47.27mdrobnakI don't think it's far off, really.
19:47.36camdenneither do I
19:47.42camdennitdroid is very close to usable
19:47.57camdenand raph linux is moving and a breakneck pace
19:48.14mdrobnakI don't remember who (sorry) but someone got the preliminary data done for getting stuff like the audio routing, power management, etc going a day or two ago
19:48.24camdenthat's rad.
19:48.27mdrobnakI think within the next week, we'll see a very usable kernel in git.
19:48.38camden<glee>
19:49.30*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
19:52.55dcordes_Mullins: is the initrd with X any useful?
19:53.41mdrobnakdcordes_ If we get X working, will that allow us to use OpenMoko stuff instead of Android, as well?
19:53.55Mullinsdcordes: Have not tried it yet
19:54.07camdenthat would be cool
19:54.13*** join/#htc-linux timebomb (n=tb@e176106254.adsl.alicedsl.de)
19:54.14*** join/#htc-linux ALoGeNoff (n=alogeno@unaffiliated/alogeno)
19:54.18ALoGeNoffloo
19:55.56*** join/#htc-linux balsat (n=kll@87.72.13.87) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux pH5 (n=ph5@p5485F315.dip.t-dialin.net)
19:55.56*** join/#htc-linux Zinbolic (n=Zy@84.238.80.215) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux mustangsal66 (n=MustangS@pool-72-82-245-90.cmdnnj.fios.verizon.net) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfe8c0.pool.einsundeins.de) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux Shinto (n=John@g227197208.adsl.alicedsl.de) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux maejrep (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net) [NETSPLIT VICTIM]
19:55.56*** join/#htc-linux lupine_85 (n=lupine_8@work.lupine.me.uk)
19:56.34*** join/#htc-linux oliwan (n=oliwn@client-86-25-189-21.bsh-bng-012.adsl.virginmedia.net)
19:57.26Mullinsdcordes: does the GIT version compile for you with Kaiser config now with no errors?
19:58.10oliwanHi, I wana help get Android 1 working on Diamond. Anything I can do?
20:00.35camdenok so I read about this spare parts app, but I can't find it in my version of android
20:00.57mdrobnakcamden: Cupcake build only
20:01.10camdenwhere can I find that?
20:01.20mdrobnakeek. Somewhere on the forum :-/
20:01.38*** join/#htc-linux t3chi3 (n=blarg@36.67.33.65.cfl.res.rr.com)
20:01.44mdrobnakoliwan: Are you good with Linux , development, reverse engineering?
20:02.31camdensoo... that's wierd. with the zImage I posted above, pushing the call end button causes my device to crash.
20:02.53mdrobnakcamden: Not exactly.
20:03.03mdrobnakYou cause it to go to sleep, which doesn't work, so you lose the screen.
20:03.09camdenhuh
20:03.30mdrobnakIf you had been telnetted into the device, it will still be running :-)
20:03.39camdengotcha
20:03.46mdrobnak(Screen power management isn't done yet)
20:04.09oliwanmdrobnak: I got a bit of linux, know quite a few prog. languages and done a bit of ARM assembly a few years back.
20:04.27*** join/#htc-linux drasar (n=maik@213.192.22.2)
20:05.11camdenahh found the cupcake build
20:05.11mdrobnakoliwan: Perfect :-)
20:05.38mdrobnakoliwan: Honestly, I'm not sure where things are right now, as not everything is public...
20:05.50mdrobnak(as in, discussed outside this channel)
20:06.16mdrobnaks/discussed/not discussed/g
20:06.30oliwanmdrobnak: right, so there's no central repository of stuff at the moment?
20:06.42mdrobnakThere is a GIT repo, but not everything is commited to it.
20:07.31oliwanWhere dya rekon would be a good place to start?
20:07.49*** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl)
20:10.06oliwanmdrobnak: How do i get to the GIT repo, I could then take a look.
20:14.38balsathttp://wiki.xda-developers.com/index.php?pagename=BuildTheRaphaelKernel
20:15.01oliwannice1 cheers.
20:17.45*** join/#htc-linux piusvelte (n=irchon@71.175.8.29)
20:18.03mdrobnakThanks balsat, was afk for a sec
20:18.06camdenhmm.. seems like cupcake takes much longer to boot.
20:18.12mdrobnakOnly first boot
20:18.18camdengotcha
20:18.20mdrobnakIt's repopulating some cache
20:18.32camdenmang I gotta start my car... sooo cold
20:18.50mdrobnakcamden: Where are you?
20:18.59camdenAnchorage, Alaska
20:19.08mdrobnakOh, it's kinda cold there lol
20:19.19camden-5 F today, which isn't too bad
20:19.31camdenit's been -20 for 3 or 4 days
20:19.43mdrobnakHere I am thinking 20 F in NY is cold hehe
20:19.51dcordes_Mullins: sorry I was afk.
20:20.09MullinsdcordesL its ok, I was missing something
20:20.20dcordes_Mullins: it only builds when I have vogue and vogue-smd activated. without vogue-smd I get undefined proc_comm references
20:20.40dcordes_so I build with both, kaiser and vogue
20:20.50Mullinsdcordes: yeah, exactly. we need a kaiser_defconfig
20:20.53dcordes_mdrobnak: yes
20:21.12dcordes_mdrobnak: in cmdline openmoko can make calls on kaiser already
20:21.34dcordes_Mullins: and maybe rename vogue-smd to msm7200-smd
20:21.54mdrobnakdcordes_: Very cool.
20:23.09*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
20:24.09camdenawright, guys, time to roll out home. have a good saturday, and good luck
20:24.50*** part/#htc-linux balsat (n=kll@87.72.13.87)
20:31.27*** join/#htc-linux XD (i=t3st1fy@ircop.com)
20:32.55Mullinsdcordes: have you used that x cpio image with the latest zImage? Goes to a black screen for me
20:33.40dcordes_no but it should work. iirc j0b0 tried it on the raphael. you might try one of the .tgz images with X
20:34.05Mullinsdcordes: is there anything specific in the default.txt I need maybe?
20:35.07dcordes_except for setting the initrd, no
20:35.31dcordes_there is a problem with the msm_fb that causes X to not refresh
20:35.55Mullinsdcordes: I will try one of the tgz images too
20:35.57dcordes_dwaradzyn made a small refresh deamon
20:37.10dcordes_http://linuxtogo.org/~lgorris/builds/OE/htcraphael/htcraphael/Angstrom-x11-sato-image-glibc-ipk-2008.1-test-20081207-htcraphael.rootfs.tar.gz
20:37.40dcordes_you should remove xserver-kdrive or gpe-dm from init
20:37.58dcordes_so it doesn't start X automatically and you boot to the console
20:39.49dcordes_Mullins: http://linuxtogo.org/~lgorris/diffs/kaiser-fb-refresh.diff this fixes the X problem for me in the htc-msm kernel
20:40.07*** join/#htc-linux balsat1 (n=kll@87.72.13.87)
20:40.31Mullinsdcordes: ah cool, I will try that
20:43.14*** join/#htc-linux Marajin (n=marajin@87-194-102-189.bethere.co.uk)
20:46.07dcordes_Mullins: I don't know if it works in the new branch. also I don't know if it's the most elegant way to work around the refresh problem.
20:47.05Mullinsdcordes: wel, i got the calibration screen which is good
20:47.32Mullinsdcordes: but does not respond to the touch
20:48.06Mullinsdcordes: there was another patch for tsc2003 for tslib?
20:48.20Mullinsdcordes: maybe now I need that?
20:50.29*** part/#htc-linux balsat1 (n=kll@87.72.13.87)
20:50.55dcordes_Mullins: http://linuxtogo.org/~lgorris/misc/tslib-kaiser/tsc2003-kaiser-tslib.diff
20:51.44dcordes_the same directory has the tslib configuration I used
20:53.14Mullinsdcordes: of course, tslib is using raw values. nice patch
20:53.41dcordes_it's from tmzt
20:54.37dcordes_did you get to the calibration screen with or without the refresh patch added?
20:54.56Mullinsdcordes: with the refresh patch
20:55.35*** join/#htc-linux Gluck (n=Gluck@av9592.comex.ru)
20:56.20dcordes_Mullins: can you think of a different solution to the refresh problem which can be used globally for all the msm htcs and which does not interfer with android?
20:57.07dcordes_think the kaiser touchscreen driver is not the best spot to put it
20:57.10Mullinsdcordes: don't know tbh. I will look into it at some stage for you
21:00.24*** join/#htc-linux t3chi3 (n=blarg@36.67.33.65.cfl.res.rr.com)
21:07.34tmztdcordes_: hey, the right way would be to use the same update method as android in X
21:10.50*** join/#htc-linux Kensan_ (n=ken@gw.ptr-80-238-205-102.customer.ch.netstream.com)
21:16.07*** join/#htc-linux balsat1 (n=kll@87.72.13.87)
21:18.28*** join/#htc-linux Kensan__ (n=ken@gw.ptr-80-238-235-66.customer.ch.netstream.com)
21:21.28*** join/#htc-linux MethoS (n=clemens@host-091-097-243-030.ewe-ip-backbone.de)
21:26.37dcordes_tmzt: hi. do you know where that can be found in pixel/surfaceflinger?
21:26.54tmztI did
21:27.53tmztwe could use surfaceflinger and make X work over that also, that would help on the android/g1 but would also require at least binder in the kernel
21:28.20tmztbut it also means we can use hw3d/libhgl on at least raph/diam I think (maybe not raph500)
21:29.04tmztpixelflinger only requires the msmfb driver from trout, is there any reason that won't work on the other devices?
21:29.55tmztwhat do you mean by 2.6.27, the one from android-git?
21:31.12dcordes_that wasn't me with 2.6.27. I wonder if we can get the hw3d/libhgl to work on the msm7200
21:32.10tmztI don't know, we will probably have the same type of problem as xda
21:32.35tmzthow is the 1.0 build working on kaiser?
21:33.15dcordes_I never tried it. but sounds like it works well with the htc-vogue kernel
21:34.14tmztvogue smd doesn't work on kaiser?
21:35.30dcordes_it does put with problems
21:36.05dcordes_but
21:37.58*** part/#htc-linux balsat1 (n=kll@87.72.13.87)
21:43.14mdrobnakbbiaf
21:46.48dcordes_tmzt: I can't read from smd0. cat /dev/smd0 just terminates
21:48.43*** join/#htc-linux balsat (n=kra@87.72.13.87)
21:49.33*** join/#htc-linux dzo (n=dzo@121.98.128.127)
21:55.48*** join/#htc-linux Bally3 (n=chatzill@cpc2-blac6-0-0-cust871.manc.cable.ntl.com)
21:57.09Bally3hi dzo .. see you've got busy already :)
21:58.02dzohi Bally3, yes, I don't have a lot of time at the moment but have made some progress.
21:58.21*** join/#htc-linux Bally3 (n=chatzill@cpc2-blac6-0-0-cust871.manc.cable.ntl.com)
21:58.41tmzt17:49 < dzo> hi Bally3, yes, I don't have a lot of time at the moment
21:58.41tmzt<PROTECTED>
21:58.43dzodoes the radio work on polaris?
21:59.02Bally3thanks tmzt :)
21:59.37Bally3no-ones tried it yet .. if you mean the nike one?
22:00.18dzono, i mean can you send and receive commands on the AT channel.
22:00.51dcordes_dzo: on kaiser smd0 seems unstable
22:01.08Bally3nope
22:01.53dcordes_dzo: in the older kaiser kernels where it works well, cat /dev/smd0 stays open, outputinng everything written to the buffer
22:02.20dzoyes, after a few commands AMSS crashes, I think that could be the problem with newer radios too, it's just that 1.65.24 lets it carry on after a crash.
22:02.25dcordes_with the htc-vogue smd, it outputs the content if something is in the buffer, then closes
22:02.48dcordes_I'm running the radio recommended in the forums now
22:03.30Bally3so does this mean only the 1.65.24.36 radio will work for the SD Card?
22:03.56dzoI thing that radio has problems too, if you read smd0 it reboots with a long AMSS error message.
22:03.57tmztdzo: are you setting clocks with proc_comm?
22:03.58dcordes_sd works perfectly for me with 1.65.24.36 radio
22:04.39dzotmzt: no, i set the bits directly.
22:05.10dzodcordes_: it seems to work but I think it still crashes the radio.
22:05.32Bally3dcordes_: dont know if anyones tested that radio with polaris
22:05.39*** join/#htc-linux mdrobnak (n=mdrobnak@pool-96-232-187-37.nycmny.fios.verizon.net)
22:05.40dzomy feeling is that its overwriting some memory used by the radio somehow.
22:05.46dcordes_I think nike and polaris smd/sd equal kaiser smd/sd
22:06.06dzoyes, they are the same.
22:07.08dcordes_I think at some stage with kaiser-smd we had amss crashes too
22:07.25dcordes_that was when we were coping with the buffer locations (head/tail etc)
22:07.43dzohas the smd driver ever worked on kaiser (ie have you been able to make calls)
22:08.07dcordes_yes. the kaiser-smd.c in htc-msm works perfectly
22:08.25dcordes_also smd1 for ppp purpose
22:08.54dzoI can't get it work with the 1.65.24 radio.
22:08.54mdrobnakdcordes_ Just a random question, how well does the Kaiser stuff work on Hermes (the Cingular 8525)?
22:09.15dcordes_mdrobnak: hermes and kaiser only look similar
22:09.20mdrobnak:-(
22:09.40dcordes_dzo: the older kaiser kernel?
22:10.05tmztmdrobnak: hermes is very different, what are you asking?
22:10.07dzook, got to go now, bye. i'll mess with the smd driver a bit.
22:10.14dcordes_bye
22:10.24radem205Is it possible to run the radio 1.65.24.36 on my polaris without making damages to test something?
22:10.30dcordes_dzo: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/kaiser-smd.c;h=dbb56879a6bd2136ee84bf6e47b3f29ef2700161;hb=refs/heads/htc-msm that works well
22:10.36mdrobnaktmzt: I have a friend with an 8525, and was wondering how well the kernel was working on that..
22:10.51dcordes_radem205: flashing radio never caused any damage here
22:11.01Bally3so do we know why sd only works with that particular radio yet?
22:11.05Bally3night dzo
22:11.26*** join/#htc-linux exco (n=exco@e181123024.adsl.alicedsl.de)
22:12.11radem205ok, but when the radio isn't working on my polaris I can switch to an older radio without any problems? Then I will try running it on my polaris
22:12.27dcordes_yea that will be no problem
22:12.51dcordes_the xda devs recommend security unlocking your phone before flashing
22:13.07Bally3would flashing an incorrect radio brick the device or cause any damage?
22:13.09excoradem205: hard spl before updating your radio!
22:13.35radem205I have flashed different radio's already, but because the radio is not specific for the polaris I wondered if it could damage my phone :)
22:13.36*** join/#htc-linux p3t3r__ (n=peter@134.245.164.105)
22:14.48Bally3radem205: have you tried 1.65.24.36 yet?
22:14.49excoradem205: which version are you trying to get on your Polaris? (1.65.24.36?)
22:14.52tmztradem205: kaiser radio?
22:14.56radem205I will try it now
22:15.01Bally3lol
22:15.02radem205could you give me the link please?
22:15.30radem205Because I can't find it anymore
22:15.35tmztmsm devices won't boot if the amss won't, the arm9 boots first
22:15.43excoBally3: I tried getting the 1.65.24.36 on my Polaris using Custom RUU the other day - but I couldn't even get it on the device - let me know if it works for you
22:16.15excohttp://www.4shared.com/file/54728367/855c6f49/NEON_Radio_1652436.html
22:16.27excoif that's the one you're looking for
22:16.32Bally3exco: I'll try it through the sd card and post results on the  on the forum
22:17.03excoare you trying right now?
22:17.31excois there already a new kernel with dzo's latest changes to try on Polaris?
22:18.41Bally3Tell me if I'm wrong.. but 1.65.24.36 is a NIKE radio right?
22:18.49excoyes
22:19.26Bally3and so it will only be compatible with roms that are NIKE bassed?
22:19.44excoBally3: afair not
22:19.53Bally3ok
22:19.59excoBally3: http://forum.xda-developers.com/showthread.php?t=393182
22:22.03radem205where can I find the latest android files for the kaiser (with the updates of dzo)?
22:22.10*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
22:23.25p3t3r__Hi, has there been any work on HTC Universal lately?
22:23.37Bally3exco: "I would also ensure that you have the correct SPL in regards to the build of the ROM"
22:24.26excoSPL in regards to the build of the ROM ... well for Polaris there's only one (hard) SPL afik
22:24.33exco*afaik
22:25.19Bally3this is the issue.. I came across this with a new radio - a kaiser one which only worked with specific roms
22:25.57excop3t3r__: Last edited by bosjo; 23-09-2008 at 09:02 PM.. http://forum.xda-developers.com/showthread.php?t=251584&highlight=linux ?  
22:26.04Bally3I've got a feeling its about the build.. the xip etc..
22:27.05Bally3its mentioned somewhere that the 1.65.24.36 radio works with all diamond builds...
22:27.58excoradem205: http://rapidshare.de/files/41237182/android1.0_kaiser.rar.html + http://forum.xda-developers.com/showpost.php?p=3147333&postcount=1924 I think
22:28.07tmztp3t3r__: some, but moving to a newer kernel is waiting on some things
22:29.47excoBally3: I don't really know if a diamond build is of help to us MSM7500 <-> MSM7200
22:32.04Bally3exco: I know :(
22:32.43Bally3im downloading the radio now.. using a slow 3g connection
22:32.46excobtw what's the correct syntax to update your local copy of git.ltg...?
22:36.19radem205Radio 1.65.24.36 will not work on the polaris :(
22:36.34excoyou can't flash it either?
22:37.07radem205at 5% i get the message that my device is not compatible with the radio rom
22:39.04*** join/#htc-linux timebomb (n=tb@e176106254.adsl.alicedsl.de)
22:40.05Bally3thats us buggered then
22:40.41radem205that sucks :P
22:40.50Bally3wonder why it works on Kaiser and Vogue but not on Polaris? :S
22:41.18Bally3I thought the Nike shared more similiarities to the  Polaris
22:41.26Bally3or so someone mentioned
22:41.38mdrobnakIs the phone Security Unlocked (SuperCID) ?
22:41.50radem205I think not
22:42.12Bally3mdrobnak: how do you do that sorry.. no heard of that before
22:42.32p3t3r__exco, tmzt: thanks.
22:42.32radem205http://forum.xda-developers.com/showthread.php?t=361236
22:42.50mdrobnakFrom what I understand, you can't flash from another device unless it has its restrictions removed..
22:43.17tmztBally3: what works on vogue?
22:43.26tmztBally3: the exact same radio?
22:43.50Bally31.65.24.36 - I thought that was  true?
22:44.22tmztvogue is cdma, it's very unlikely the gsm radio would work
22:44.23radem205I thought that the vogue wasn't depend on a specific radio ROM
22:44.58mdrobnakOh, yah, GSM != CDMA, thats for sure...
22:45.17radem205but there is for now not a solution for the polaris to security unlock the phone, right?
22:45.54tmztdoes uSPL work?
22:47.36radem205I don't know but I won't try it until I know it's safe :)
22:49.02Bally3Tried the 1.65.24.36 radio with the SD card method.. it wont even pick it up as a rom - just shows some numbers in red in SPL where it detects the NBH file on the card.. so I assume it wont work
22:49.05Mullinsdcordes: what is command to compress the cpio back up please?
22:49.42Bally30058002 - after the loading screen in SPL
22:50.02dcordes_Mullins: cpio -i < file.cpio
22:50.22Mullinsdcordes: the other way
22:50.38Mullinsdcordes: back to cpio
22:50.57NetRippersec
22:51.32dcordes_find ./ | cpio -H newc -o | gzip > ../initrd.cpio.gz
22:51.42NetRipperhttp://netripper.pastebin.com/d62c446db
22:51.46tmztNetRipper: have you seen the RaphaelPSOC wiki?
22:51.46NetRipperthat's what i use
22:52.08NetRippertmzt, no ididnt
22:53.20NetRippernice
22:53.47NetRipperthough i have no clue what the 3 things are in front of each line? i.e. ce,13,14
22:54.15dcordes_yo NetRipper
22:54.16tmztit looks like we have everything to make keyboard work now and I think maejre*p is working on a driver
22:54.24NetRippernice
22:54.30tmzti2c address, register, value I think
22:54.43NetRipperah
22:55.00NetRipperseems complex
22:55.07tmztwe need a a keymap for raph100 which can be done with haret
22:55.19NetRipperkeymap is already there
22:55.20NetRipperon wiki
22:55.25NetRipperoh
22:55.27tmztok
22:55.32NetRipperyou mean it may differ from raph800
22:55.45NetRipperbottom of psoc page links to: http://wiki.xda-developers.com/index.php?pagename=RaphaelKeyboard
22:56.03NetRipperhi dcordes_ btw :)
22:56.28mdrobnakNetRipper: Tried to do some testing last night on my Fuze,err HTC P-4600 :-), and had some issues with HaRET....didn't help it was 1AM local time..
22:56.36mdrobnakOh, and Hi :-)
22:56.44NetRipperhi ;)
22:56.50NetRipperwhat kind of testing?
22:57.02mdrobnakTrying to determine keycode differences or similarities
22:57.05NetRipperah
22:57.06mdrobnakI think the main keys will be fine.
22:57.15mdrobnakNumbers might be an issue, didn't test.
22:57.19NetRipperyes but there's a diference in the special keys
22:57.22NetRippernext to the space
22:57.30mdrobnak(The numbers on the Fuze are in a telephone pattern)
22:57.37mdrobnakYes, those didn't give me Keycode
22:57.44mdrobnakthey showed up as a different button
22:57.48NetRipperthe bottom row is different between fuze/raph
22:58.02mdrobnakNot just the bottom row.
22:58.07NetRipperi have ctrl, fn, sms/mms, mail, sym, space
22:58.43NetRipperanyway i think that's just details
22:58.45mdrobnakhttp://www.wmexperts.com/articleimages/2008/moved/08/08/fuze1.JPG
22:58.50*** join/#htc-linux timebomb (n=tb@e176106254.adsl.alicedsl.de)
22:58.57NetRipperif we have a driver, keymap is easily adjustable
22:59.00mdrobnakargh
22:59.14NetRipper/moved/ indeed
22:59.15NetRipper;)
22:59.39mdrobnakhmm
22:59.44mdrobnakit worked from the article
22:59.56NetRipperhotlinking prevention possibly?
22:59.58mdrobnakhttp://www.wmexperts.com/tags/touch-pro?page=3
23:00.06mdrobnakBottom of page
23:00.09mdrobnakPerhas.
23:00.12mdrobnakPerhaps
23:00.58NetRipperah
23:01.20NetRipperyou dont have a ctrl key??
23:01.28mdrobnakNope
23:01.34mdrobnakSame keycode as "ok" key though
23:01.34NetRipperha!
23:01.37mdrobnakYah. :-/
23:01.46mdrobnakI'd rather control, being a *nix guy
23:01.50NetRipperyes
23:01.56j0b0tmzt re i2c, did that take any hacking to msm_i2c or just the correct chip/address/control ?? values
23:01.56NetRipperwell
23:02.02NetRipperplus side is that you can remap any key to be ctrl ;)
23:02.04mdrobnakThat being said, it's not that bad of a layout.
23:02.06mdrobnakYah :-)
23:02.22j0b0and does that also mean that things like leds and gsensor and backlight are around the corner
23:02.25*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
23:02.33NetRipperthat'd be sweet
23:02.39NetRipperi want to control those leds
23:02.42NetRippermake a disco
23:02.45mdrobnaklol
23:02.59mdrobnakDinner time, bbl.
23:03.12NetRipperman i wish i was in uk
23:03.14NetRipperuh
23:03.15NetRipperus
23:03.22NetRipperhave a good dinner
23:03.41j0b0haha you can have a midnite dinner now
23:03.45tmztj0b0: don't think it did
23:03.46mdrobnaklol. Thanks.
23:04.15*** join/#htc-linux stefan_schmidt (n=stefan@p5B037F75.dip.t-dialin.net)
23:04.20tmztj0b0: some of what we did was with i2cdump which just required enabling I2CDEV
23:06.07j0b0is the keyboard now just work or still investigation to do
23:08.27NetRipperj0b0, that "dirty hack" is required for X then it seems?
23:08.50j0b0yes.
23:08.59NetRipperalthough
23:09.13NetRipperprobably it only works because touchscreen and vkeyb are still working on timer base, instead of interrupt base
23:09.14dcordes_j0b0, NetRipper: did you try the kaiser-X-workaround instead of the 'dirty hack' ?
23:09.32NetRipperdcordes_, im not familiar with the kaiser-X-workaround, got a link?
23:09.48j0b0is that the loop that keeps updating everything?
23:10.10NetRipperj0b0, the msm_ts driver is polling for touch data.. as the interrupt is not working
23:10.14NetRipperit does so 20 times a second
23:10.42j0b0i mean the X work around
23:10.47NetRipperoh ;)
23:11.03NetRipperman i've been spending time in getting the irq to fire
23:11.06NetRipperfor touchscreen
23:11.30j0b0both the X workaround and the VDH are ..uhm.. not nice
23:11.52tmztvdh?
23:11.59j0b0very dirty hack
23:12.25j0b0in msm_fb.c~180
23:12.29dcordes_j0b0: yes the loop thing
23:12.54NetRipperw#ifdef CONFIG_MACH_HTCRAPHAEL x = 0; y = 0; w = pi->width; h = pi->height; // XXX - VERY ugly hack so we can draw in fbram
23:12.57NetRipper#endif
23:12.58NetRipperthat's the vdh
23:12.58NetRipper;)
23:12.59j0b0i guess X draws by just poking in the FB
23:13.13dcordes_btw did somebody from the 7201a faction try making ts work precisely in X ?
23:13.30tmztI think the keyboard can be made to work with what we have but I'm having trouble interpreting cr2's wiki
23:13.48NetRipperthe nice way would be to write a X graphical driver.. that uses the msm_fb driver
23:13.50tmztthe tsc2003.c driver should work as a template for the driver
23:14.07maejreptmzt, heh same ;p
23:14.13j0b0the drawing and blitting unctions in msmbf mark the dirty are using msmfb_pan_update(,,,,0)
23:14.28j0b0which doesnt trigger the dma, just expands the dirty area
23:14.40j0b0it would be nice if X could do the same
23:14.52maejrepthough the i2c channel that we use for navi cap sense seems to be the same address that trout uses for LEDs
23:15.05NetRipperthe "fbdev" driver simply updates the framebuffer.. there's no mechanism to signal a driver..
23:15.21dcordes_NetRipper: this is the kaiser-X-workaround http://linuxtogo.org/~lgorris/diffs/kaiser-fb-refresh.diff
23:15.23NetRipperan "msmfb" driver should be built for X
23:15.24maejrepbtw, just updated the wiki camera page with what proc comm is doing on init/deinit of the camera
23:15.47j0b0the VDH is a performance loss, and the loop thing too, unless you update less frequently, which makes stuff sluggish
23:16.02dcordes_xserver-kdrive-msm
23:16.23tmztmaejrep: I think cr2 said he found the vregs for camera
23:16.35j0b0would it be possible for user space fb drawing functions to somehow tell the kernel to invalidate a region
23:16.50maejrepi don't know what vreg is :)
23:17.05NetRipperdcordes_, my god why is that thread in the touchscreen driver instead of the msm_fb? :P
23:17.27maejrephttp://wiki.xda-developers.com/index.php?pagename=RaphaelDEX
23:17.44maejrepI see 0x15 and 0x16 on init/deinit of the camera
23:20.09dcordes_tmzt: proposes to include the update function android uses in the X
23:20.15dcordes_instead of hacking the kernel
23:20.44dcordes_I think fixing it in msm_fb has some advantages
23:21.31NetRipperdcordes_, as i said.. a driver should be written for X, so that you dont have to use "fbdev"
23:21.34tmztmaejrep: voltage regulator, generically meaning the voltage (vdd) used for a device
23:21.53dream_killhi
23:22.05maejrepis that something we need to initialize on each use, or at startup?
23:22.11dream_killany updated kernels for raphael and kaiser (just fixed my kasier :P )
23:22.14dream_killso i can test :D ?
23:22.16NetRippertmzt, hm, could that also be the way how the flashlight led works? as it has a normal and a 'brighter' setting
23:22.17maejrepcause I don't see anything other than 0x15 on camera init (run 4 times)
23:22.36dcordes_dream_kill: yea check the htc-vogue branch (for kaiser)
23:22.59dream_killis the pdf helped :P ?
23:23.08dcordes_which pdf?
23:23.11tmztNetRipper: maybe, is it controlled through the camera module, through a gpio on msm, or pwm on the atmel?
23:23.52NetRippertmzt, via htccamera1.dll, but the normal flashlight led can be enabled via gpio.. just to make it brighter is not via gpio
23:24.00*** join/#htc-linux Balsat1 (n=kll@87.72.13.87)
23:24.16tmztcould there be a second gpio to make it brighter?
23:24.35NetRipperi dont think so but i should trace that
23:26.39*** join/#htc-linux t3chi31 (n=blarg@36.67.33.65.cfl.res.rr.com)
23:28.40maejrepNetRipper, brightness should be controlled by i2c
23:29.02maejrephow do you enable the flashlight?  I'm already tracing right now
23:29.38maejrepfound it
23:30.18NetRipperflashlight is already documented
23:32.14maejrepI meant re the brightness
23:32.21NetRipperaha
23:32.36NetRipperso it is via i2c then?
23:34.09rolkdream_kill: That info you have is really nice. Do you have something that describes the interrupt handling on the ARM11, and the clock domains?
23:35.33maejrepturning it on is not
23:35.44maejrepbut setting the brightness might be
23:35.46rolkdream_kill: With clock domains I mean, the peripherals can be switched off (unclocked) so that they do not consume power when not needed. The USB OTG controller for example. It is still unclear how to setup the proper timing of those peripheral blocks.
23:36.51NetRippermaejrep, it seems the camera driver turns off the normal flashlight via the gpio, and uses some other way to get it bright
23:36.55NetRipperanyway
23:37.04NetRipperdont spend much time on it.. it's not that important (at least not to me)
23:37.12NetRipperwas just curious :)
23:37.26maejrepit turns it off?
23:37.42maejrepwhen I turned on flash, I saw the gpio go high
23:37.48NetRipperyes
23:37.54NetRipperbut when you make a picture
23:37.57maejrepahhh
23:37.59NetRipperthe flash goes extra bright
23:38.02maejrepgot it
23:38.23NetRipperat that point it disables the gpio, sets the bright mode, then when picture is done, it re-enables the gpio
23:38.32rolkdream_kill: are you still awake?
23:38.58dream_killyes
23:39.01dream_kill2 sec
23:42.01maejrepthe camera also enables the accelerometer :p
23:42.49NetRipperhm
23:43.02NetRipperso thats why i saw gpio activitywhen i simply picked up the phone
23:43.02NetRipper;)
23:45.04maejrepnifty idea .. probably used to stabilize the image
23:45.06maejrep001.814 7803dad4: str    r3, [r6]       # b2300000 =00000118
23:45.07maejrep001.814 7803db0c: str    r3, [r6]       # b2300000 =00000001
23:45.07maejrep001.814 7803db48: str    r3, [r6]       # b2300000 =00000200
23:45.18maejrep^ that's the only thing out of the norm that I see when taking the picture
23:45.25maejrepand i don't know what id 18 is yet
23:45.38maejrepbut the led/backlight chip should be at cc
23:45.56NetRipperwell we'll play around with that later i guess ;)
23:46.38NetRipperim too tired now anyway, im off to bed ;)
23:46.45NetRippernight :)
23:46.46*** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com)
23:47.10maejrepgnite
23:47.16tmztdo we know what camera it is?
23:47.36maejrepits on the same i2c reg as the camera in trout
23:47.43maejrepwould be a good guess I think
23:48.04tmztbut 18 is not the camera?
23:48.05maejrephttp://wiki.xda-developers.com/index.php?pagename=RaphaelCameras
23:48.24maejrepno, 6c appears to be
23:49.00maejrepso if the wiki is right, then it is the same camera as trout
23:49.37tmztI think that just got contributed upstream also
23:49.53maejrepabout mid-oct i think
23:50.06maejrephttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=4e6a687ee8998ebbe1c3ea7c2d6397346e152237
23:50.18tmztcool
23:50.35tmztthe trout/g1 still uses a userspace library to access the camera
23:51.36maejrepmain thing is the contribute i2c driver calls the trout config_camera_on_gpio function, which uses proc comm to setup the cam gpios
23:52.00maejrepbut on my phone, the only pcom chatter I saw was the 4 0x15 calls noted on that wiki page
23:54.06tmztis that a vreg command or gpio?
23:54.12tmzt15 and 16
23:54.48maejrepproc_comm
23:55.00tmztyeah, which command?
23:55.07maejrep<PROTECTED>
23:55.07maejrep<PROTECTED>
23:55.17tmztthat would be vreg
23:55.35*** join/#htc-linux t3chi3 (n=blarg@36.67.33.65.cfl.res.rr.com)
23:55.52tmztwhat's the 3c part?
23:55.57maejrepwell, it enables 0x100, 0x200000, 0x8000, and 0x20
23:56.04maejrep"ioctl" on the wiki
23:56.14maejrepnot sure what its used for
23:56.20tmztwhat wiki?
23:56.36maejrepoh heh
23:56.46tmztthose are the parameters to the proc_comm call, not seperate registers
23:56.50maejrephttp://wiki.xda-developers.com/index.php?pagename=RaphaelDEX
23:57.00maejrepI know
23:57.28maejrepit sends: 0x15 (0x100, 0)
23:57.56tmztoh sorry
23:58.02tmztI thought it passed the whole array
23:58.38tmztso these must be bits in a 32bit register?
23:59.02maejrepthat's my guess, yeah
23:59.46maejrepI don't see all my numbers listed for his vreg documentation list either

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