00:01.14 | cr2 | android.git.kernel.org |
00:02.41 | *** join/#htc-linux bashir (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com) |
00:03.49 | *** part/#htc-linux bashir (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com) |
00:05.05 | lupine_85 | hmm, well <=> gpsd works |
00:05.39 | lupine_85 | and the LED is glowing |
00:05.49 | lupine_85 | the lights around the navi circle keyboard |
00:05.55 | lupine_85 | button*# |
00:08.33 | *** join/#htc-linux exco (n=exco@e181093134.adsl.alicedsl.de) |
00:09.08 | lupine_85 | ?frameworkd-devel? is doing some odd stuff |
00:09.29 | *** join/#htc-linux gh0ul (n=asds@host81-154-247-76.range81-154.btcentralplus.com) |
00:11.49 | *** part/#htc-linux exco (n=exco@e181093134.adsl.alicedsl.de) |
00:17.08 | Untouchab1e | Good night all |
00:17.10 | Untouchab1e | good luck :D |
00:28.11 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
00:29.08 | lupine_85 | humm. 'ARM9 has CRASHED' |
00:29.24 | lupine_85 | smem: DIAG '' |
00:29.31 | lupine_85 | (very helpful :D) |
00:37.27 | dream_kill | :P |
00:39.31 | *** join/#htc-linux reformatt (n=chatzill@71-37-165-208.bois.qwest.net) |
00:39.33 | lupine_85 | that was caused, I think, by init'ing the GPS then booting into linux |
00:39.44 | lupine_85 | (I ran google maps then haret) |
00:40.39 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
00:44.37 | lupine_85 | wonders if he should use phoneme or gpephone |
00:48.05 | maejrep | lupine_85: the LEDs glowing happens if you're charging it when you boot into linux |
00:48.33 | lupine_85 | fair enough |
00:48.38 | maejrep | the LED state continues when you boot out of windows, and since the "breathe" effect is controlled by the chip, it keeps doing it |
00:48.48 | lupine_85 | not sure how it managed to screw up my calibration though |
00:49.09 | maejrep | and i think i read somewhere else that NetRipper had the same issue of it crashing when you boot with gps initialized |
00:49.44 | lupine_85 | I'll try the gpsd further tomorrow, when I'm not surrounded by bricks :D |
00:51.10 | maejrep | lupine_85: want my kbd module? |
00:51.28 | maejrep | or wait for me to clean it up? :p |
00:51.50 | lupine_85 | I'll let you clean it up :) |
00:56.05 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
00:56.25 | lupine_85 | builds himself a GPE image too |
00:57.52 | BHSPitLappy | draws an image of GPE |
00:57.56 | maejrep | you have raph100 right? |
00:59.00 | maejrep | cr2: yeah in SPL, I see "MicroP-Raph (LED) v0C85" and "MicroP-Raph (KEY) v0685" |
00:59.08 | maejrep | so looks like the version ids are correct |
00:59.28 | maejrep | also see "PSOC-Raph STAGE_EVT v20" but I don't know what that means :) |
01:00.30 | lupine_85 | maejrep: yep |
01:01.14 | *** join/#htc-linux TeringTu1y (n=maarten@195-241-125-243.ip.telfort.nl) |
01:01.30 | maejrep | lupine_85: if you get a chance can you boot into SPL and tell me what those versions show for you ^ |
01:02.00 | maejrep | hold power+vol_dn and soft-reset, holding those 2 keys until you get to the tri-color SPL screen |
01:02.35 | lupine_85 | MicroP-Raph v5 |
01:02.47 | maejrep | that's it? |
01:02.48 | lupine_85 | erm |
01:02.51 | maejrep | doesn't show LED or KEY ? |
01:03.10 | lupine_85 | MicroP-Raph(LED) v13 \n MicroP-Raph(KEY) v5 |
01:03.28 | maejrep | yikes |
01:03.37 | lupine_85 | and I have a PSOC-Raph STAGE_CVT v0x36 |
01:03.54 | maejrep | very different ;x |
01:04.07 | *** part/#htc-linux NexVision (n=nunya@97.66.39.252) |
01:04.08 | maejrep | its not even 0005 ? |
01:04.10 | maejrep | just v5 ? |
01:04.13 | lupine_85 | v5 |
01:04.16 | maejrep | hmm |
01:04.30 | maejrep | guess we'll have to see what the id comes back as in the driver |
01:04.55 | lupine_85 | it's possible the SPL version-reading is bugged too ;) |
01:05.07 | maejrep | i guess |
01:07.26 | lupine_85 | so long as the versions are unique, and both sides agree on which version is which, I guess you can't really call them 'wrong' ;) |
01:08.19 | cr2 | lupine_85: raph100 ? |
01:11.02 | cr2 | maejrep: reflashing the psoc and microp may be fun. i think they use master mode. |
01:11.11 | lupine_85 | cr2: yes |
01:11.44 | cr2 | lupine_85: the numbers look good for me |
01:13.07 | maejrep | so 0685 and 0c85 are just what raph800 has i guess ;o |
01:13.18 | cr2 | maejrep: destroyed the lcd already? |
01:13.21 | cr2 | yes |
01:13.28 | maejrep | doh not yet |
01:13.34 | maejrep | was cleaning up kbd |
01:13.43 | cr2 | 85 is for 800 , and 5 is for 100 |
01:14.30 | cr2 | i've looked at the tiacx driver |
01:14.38 | maejrep | so whats the 06? |
01:15.00 | cr2 | the ugliness i |
01:15.18 | cr2 | s unbelievable |
01:15.27 | cr2 | 06 is the fw revision |
01:16.14 | cr2 | but it should be relatively easy to adapt it to raph |
01:16.30 | cr2 | i think only the wifi irq number is hardcoded |
01:16.54 | lupine_85 | nice |
01:16.56 | cr2 | and 3 trout_foobar() function names are needed |
01:18.54 | cr2 | don't know about the bt |
01:19.42 | cr2 | h2w looks interesting |
01:20.46 | cr2 | maejrep: can we move to 2.6.27 ? |
01:20.56 | maejrep | that'd be nice :p |
01:21.09 | tmzt | cr2: you mean they boot in master and expect firmware to available? |
01:22.28 | tmzt | 20:20 < lupine_85> humm. 'ARM9 has CRASHED' |
01:22.28 | tmzt | 20:21 < lupine_85> smem: DIAG '' |
01:22.28 | tmzt | 20:21 < lupine_85> (very helpful :D) |
01:22.32 | tmzt | DIAG? |
01:23.19 | tmzt | cr2: even g1 is not moved to 2.6.27 yet it appears, the cupcake build will try to build it or use existing image |
01:23.22 | tmzt | but it doesn't work |
01:23.30 | cr2 | tmzt: something like that |
01:23.42 | cr2 | ok |
01:23.45 | tmzt | there is a patch for the ril though, not in ril but in telephony, it ignores a command the htc ril won't support |
01:23.55 | tmzt | noone wants to try dzo ril on g1/adp1 I can find |
01:24.15 | maejrep | why not? sounds fun :D |
01:24.21 | tmzt | http://review.source.android.com/7699 #wifi fw loader |
01:24.34 | tmzt | http://review.source.android.com/7674 # ril |
01:25.21 | tmzt | I'm working on a protocol for testing cupcake on g1 using sd card, but it's theoretical for me |
01:25.24 | cr2 | tmzt: doesn't work == kernel does no boot ? |
01:25.30 | tmzt | don't know |
01:26.05 | tmzt | don't think that's it |
01:26.17 | tmzt | also, it appears it expects a new amss but no clear information on that |
01:26.32 | cr2 | ok |
01:26.37 | cr2 | good night |
01:26.38 | tmzt | I think it's only at command differences not smd layout |
01:26.43 | *** join/#htc-linux zycho_ (n=zycho@a89-183-78-110.net-htp.de) |
01:29.41 | *** join/#htc-linux reformatt (n=chatzill@71-37-165-208.bois.qwest.net) |
01:30.16 | reformatt | quick question how does the msmts_calib string work in default.txt. What settings from my calib screen need to be there? Im trying to get the correct settings for DIAM500 |
01:31.15 | tmzt | it should be in dmesg somewhere, otherwise look at the source (sorry) |
01:32.37 | reformatt | that is ok. Have maxx-miny and minx-maxy strings and can't figure out what order they go in. :P |
01:33.26 | tmzt | what kernel do you use on diam500? |
01:33.45 | tmzt | that is on verizon, right? |
01:34.02 | reformatt | im using the latest one that Untouchable uploaded |
01:34.10 | reformatt | no its for the sprint model |
01:34.27 | reformatt | msm_ts: maxx=03a3 miny 03ba, msm_ts: maxx=03a3 miny 03ba |
01:34.30 | tmzt | it says diam500 under battery? what is the cpu in ce settings? |
01:34.35 | tmzt | system info |
01:35.03 | reformatt | 7501a |
01:35.59 | reformatt | it does say DIAM500 under battery |
01:36.01 | tmzt | it has built-in sd card? |
01:36.15 | reformatt | yes built in sd card back of the phone has a red cover |
01:36.27 | reformatt | not sure what version the verizon model is |
01:36.40 | dream_kill | hi |
01:36.50 | tmzt | it seems strange they would have raph500 but not diam500 |
01:36.50 | dream_kill | got a raph100 too |
01:36.58 | tmzt | anyway, now I need an iDEN one |
01:36.58 | dream_kill | u need any info from it? |
01:37.13 | tmzt | don't think so |
01:37.24 | dream_kill | k |
01:37.42 | tmzt | raph100 is pretty well taken care of I think |
01:38.03 | tmzt | maejrep: close to a patch? been away a few hours mostly |
01:38.21 | maejrep | yup, just cleaning up the code so it doesn't look so bad ;p |
01:38.42 | tmzt | are you going to commit on the NetRipper stuff from yesterday? |
01:39.07 | maejrep | damn, forgot to pull those changes |
01:39.12 | maejrep | but I don't have commit access anyway |
01:39.18 | tmzt | that's what git is for |
01:39.27 | tmzt | well ok, I mean patch against those |
01:39.54 | maejrep | yes I'll do it from latest head |
01:43.33 | reformatt | tmzt: yes its crazy that the models would not match up between the touchpro and diamond. Verizon hasn't even released the diamond yet. :P |
01:44.04 | tmzt | I think they might make it an HD but that's just a guess |
01:53.47 | *** join/#htc-linux xianthax (n=xianthax@c-75-69-145-210.hsd1.ma.comcast.net) |
01:54.02 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
02:11.37 | maejrep | tmzt, NetRipper, cr2, lupine_85: http://www.privatepaste.com/e11uUWKu8G |
02:14.06 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
02:16.28 | maejrep | works still :D |
02:16.38 | maejrep | (didn't test it after my cleanup ;x until now) |
02:17.37 | tmzt | +static struct micropkbd_platform_data raphael_kbd_data |
02:17.38 | tmzt | raph800? |
02:18.19 | maejrep | yes |
02:18.33 | maejrep | which is not going to work for raph100 or 110 |
02:18.58 | maejrep | [ 44.849734] MicroP Kbd: Clamshell status: 4294967295 <-- that's "-1", but why? Shouldn't gpio_get_value() return 0 or 1? |
02:19.52 | tmzt | I think so, what does the android driver do? |
02:20.11 | tmzt | I mean how does it check that gpio? |
02:21.32 | maejrep | hmm |
02:21.33 | maejrep | static struct gpio_event_input_info trout_keypad_switch_info = { |
02:21.33 | maejrep | <PROTECTED> |
02:21.33 | maejrep | <PROTECTED> |
02:21.33 | maejrep | <PROTECTED> |
02:21.34 | maejrep | <PROTECTED> |
02:21.40 | maejrep | guess it lets gpio_event_input handle it |
02:21.46 | maejrep | probably a good idea to do it that way :) |
02:22.18 | tmzt | it has to be on the same device for android though? |
02:22.31 | maejrep | meaning what? |
02:23.02 | tmzt | try !!gpio_get_value( |
02:23.15 | tmzt | /dev/input/event1 I think |
02:24.40 | maejrep | I think trout's keypad driver registers 3 individual inputs |
02:24.47 | maejrep | static struct gpio_event_info *trout_keypad_info[] = { |
02:24.47 | maejrep | <PROTECTED> |
02:24.47 | maejrep | <PROTECTED> |
02:24.47 | maejrep | <PROTECTED> |
02:25.06 | maejrep | and the switch is the clamshell slider |
02:25.10 | tmzt | does trout driver send a value with EV_SW, or is that just used as a toggle for surfaceflinger |
02:26.14 | maejrep | it doesn't do anything with it here .. my guess is it just catches SW_LID and does something with it in userland (ie, turn off the keyboard when shut) |
02:26.35 | maejrep | probably a good way of handling it ;o |
02:28.28 | maejrep | NetRipper: ignore those last 3 changes in board-htcraphael.c :x those are the gpios I use |
02:36.01 | maejrep | cr2: |
02:36.03 | maejrep | 000f3fc0 00 00 00 00 01 00 00 00 dd 00 dd 00 da 00 da 00 |................| |
02:36.03 | maejrep | 000f3fd0 00 00 00 00 00 00 00 00 d3 03 d3 03 ec 00 ec 00 |................| |
02:37.08 | maejrep | according to vogue-smd.c, the AT head & tail are "dd00" and "da00", and the SMD1 head and tail are d303 and ec00 |
02:37.31 | maejrep | and I don't think there's anything identifying around it that can tell us where to find it |
02:38.53 | tmzt | what do you mean by the last part? |
02:40.52 | *** join/#htc-linux woodyPL (i=woody@gateway/shell/blinkenshell.org/x-c986e936b688ba54) |
02:42.59 | maejrep | he mentioned earlier that we should be able to scan some part of smem to find f3fc8 and f3fcc ^ above in order to get information about the rx/tx buffers |
02:43.15 | maejrep | but I don't think that would be an easy task |
02:48.14 | maejrep | cr2: haretlog-20090111_183605.log:004267: mem TRACES(0) 9c0fc100=0000001a (0000001a) @~f000fe50 |
02:48.17 | maejrep | so I did see 0x1a |
02:51.45 | *** join/#htc-linux woodyPL_ (i=woody@gateway/shell/blinkenshell.org/x-375c3ceac7795fbf) |
02:58.14 | maejrep | cr2: also, I really don't think the in/out thing is right :x in my trace, the 0x1a command does set both DATA1 and DATA2 |
02:59.27 | maejrep | see: http://www.privatepaste.com/280QKem6zo |
03:00.04 | maejrep | looks like it sets 0x400000 level to 0xb22, and 0x4000 level to 0xa28 |
03:01.27 | *** join/#htc-linux t3chi3 (n=blarg@ip24-250-216-85.ga.at.cox.net) |
03:08.05 | maejrep | arch/arm/mach-msm/proc_comm.c:91:4: warning: #warning WinCE compatible AMSS version selected. Default proc_comm implementation is disabled and stubbed to return -EIO. <-- I think -ENOTSUPP would be more appropriate :) |
03:12.52 | maejrep | hmm, can't remember what I did to get EXPORT_SYMBOL to work ... cause its certainly not working now :( |
03:14.38 | tmzt | from where to where? |
03:17.12 | maejrep | trying to get msm_proc_comm_wince accessible from a test module |
03:17.28 | tmzt | MODULE_EXPORT_GPL |
03:17.56 | maejrep | not found anywhere :o |
03:18.06 | maejrep | its supposed to be EXPORT_SYMBOL |
03:21.01 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
03:25.12 | maejrep | whatever |
03:25.20 | maejrep | i guess i'll just build it in.. was trying to not do that though |
03:27.15 | tmzt | and you've declared MODULE_LICENSE gpl on your module? |
03:29.31 | maejrep | hmm, possibly not |
03:30.13 | maejrep | my only reason for wanting it is so I can know at the exact moment the code executes, instead of building it into the kernel |
03:30.21 | maejrep | but i'll just setup a debugfs entry |
03:31.34 | maejrep | MODULE_LICENSE("GPL"); <- yes it was |
03:32.05 | tmzt | not sure then, your way could work though |
03:32.11 | *** join/#htc-linux woodyPL_ (i=woody@gateway/shell/blinkenshell.org/x-817e4c83b8fa16db) |
03:33.38 | tmzt | dzo: maejrep has a keyboard driver for raphael coming |
03:34.03 | tmzt | dzo: not directly interesting for kais/vogue though |
03:40.24 | maejrep | i want to get restart working too :p |
03:40.58 | maejrep | pisses me off every time I soft reset and forget to exit my ssh session ;p |
03:40.58 | tmzt | I could be a bit more awake maejrep |
03:41.29 | maejrep | lol |
03:41.39 | maejrep | drink some coffee? :p |
03:41.55 | tmzt | no, going to sleep soon |
03:43.02 | *** join/#htc-linux ionstorm (n=ion@ip68-227-226-5.ph.ph.cox.net) |
03:44.51 | *** part/#htc-linux xianthax (n=xianthax@c-75-69-145-210.hsd1.ma.comcast.net) |
03:46.22 | maejrep | he's human after all ;) |
03:46.37 | maejrep | I was beginning to think you were more insomniac than I am :p |
03:47.05 | tmzt | irssi is, I'm semi |
03:48.38 | maejrep | so, my debugfs hook to make it turn the LCD off and back on... didn't work :) |
03:51.30 | *** join/#htc-linux woodyPL (n=woody@gateway/shell/blinkenshell.org/x-6a4d95923f0d9fe5) |
03:56.35 | maejrep | can we register two i2c chip drivers for the same id? |
03:58.03 | tmzt | with different irq's? |
03:58.28 | tmzt | ah, that's a mfd |
03:58.53 | tmzt | drivers/mfd/ |
03:59.55 | maejrep | i guess the most appropriate way to do this keyboard driver would be to have two chip drivers, for ce and cc, and let the keyboard/input driver interact with the chip drivers as needed? |
04:00.20 | tmzt | can you implement read function for the channels? |
04:00.32 | maejrep | and the input driver would only use cc for setting notification request (cc,50,x) |
04:00.38 | maejrep | but also use the cc driver for setting LEDs |
04:00.46 | tmzt | read(dev->client, chanid .. |
04:00.58 | maejrep | sure, i'm already partway there |
04:01.27 | maejrep | so then the chip drivers wouldn't use irqs, but the input driver would handle the interrupts and read/set data via the chip drivers |
04:01.32 | tmzt | you want to make the notification request a proper irq, there is a way to do that but it's complicated |
04:01.43 | tmzt | then you register a handler like you would any other |
04:01.48 | maejrep | meaning what? |
04:02.41 | maejrep | where the chip driver sets up a "soft" irq that the input driver hooks? |
04:02.48 | tmzt | yeah |
04:02.49 | maejrep | I see the IRQ as being separate from the i2c chip drivers |
04:03.06 | tmzt | not the i2c chip irq, your own irq and your own irqchip |
04:03.28 | maejrep | not sure I'm following :x |
04:04.19 | tmzt | ok, drivers/mfd/twl4030-irq.c |
04:05.44 | maejrep | i don't have that file |
04:06.34 | tmzt | it's in git.openezx.org ezx/mach at least |
04:06.46 | tmzt | probably upstream |
04:08.26 | tmzt | in this case, isr mean interrupt status register |
04:08.46 | tmzt | in your case you simple enable/disable the irq on the chip |
04:08.54 | maejrep | my understanding is that the chip driver should just interact with that chip. so there'd be one microp_klt chip and a microp_ksc chip. then microp_kbd would depend on both of those, would hook the GPIO27 irq, read scancodes from ksc chip, then tell klt chip to request notifications (to reset the irq) |
04:08.56 | maejrep | would that be wrong? |
04:09.38 | maejrep | then the board would add both the ksc and klt chips to i2c_devices, and would call microp_kbd_init in its init function |
04:09.44 | tmzt | well, my understanding is you actually write your own i2c chip driver that only provides services to input/led/etc. drivers |
04:10.04 | tmzt | your i2c chip driver handles the 50,x commands transparently |
04:10.27 | maejrep | so then the klt chip would be mfd and would be shared between the kbd and led drivers? |
04:10.34 | tmzt | yeah |
04:11.22 | tmzt | the way you propose could work also of course, I think this is the preferred way by arm upstream based on some emails on linux-arm-kernel |
04:11.34 | tmzt | getting it working would be good too |
04:12.03 | maejrep | the strangeness with the current driver is that its added in the board file in i2c_devices using chip id 0xce for the ksc chip, but then it writes to chip 0xcc for the irq reset |
04:12.46 | maejrep | which means 0xcc has to be hard coded in that driver, and i wanted to avoid that |
04:13.05 | tmzt | ok, if you want to pass the others you could probably use resources with custom flags |
04:13.27 | maejrep | or pdata potentially |
04:13.36 | tmzt | yeah |
04:14.13 | tmzt | or you could code it in probe based on the id read since that cooresponds to firmware version |
04:15.47 | maejrep | yeah.. it works currently :p but i think cr2 has higher standards for a driver ;) |
04:19.46 | *** join/#htc-linux nextime (n=nextime@unaffiliated/nextime) [NETSPLIT VICTIM] |
04:19.46 | *** join/#htc-linux _workkaze (n=kaze@ABordeaux-152-1-74-161.w86-196.abo.wanadoo.fr) [NETSPLIT VICTIM] |
04:19.46 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) [NETSPLIT VICTIM] |
04:19.46 | *** join/#htc-linux ecze (n=ecze@eczema.ecze.com) [NETSPLIT VICTIM] |
04:19.46 | *** join/#htc-linux lama (i=lama@netbsd.pl) [NETSPLIT VICTIM] |
04:19.46 | *** join/#htc-linux defiant (n=add@p0pc0rn.eu) [NETSPLIT VICTIM] |
04:19.57 | maejrep | "MicroP-Raph (KEY) v0682." |
04:19.57 | maejrep | looks like even raph800 has different revisions |
04:20.04 | *** join/#htc-linux ChanServ (ChanServ@services.) |
04:20.04 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) [NETSPLIT VICTIM] |
04:20.04 | *** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-180-11.customer.ch.netstream.com) |
04:20.04 | *** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1) [NETSPLIT VICTIM] |
04:20.04 | *** join/#htc-linux Skitzo_ (n=DCLXVI@eth582.vic.adsl.internode.on.net) [NETSPLIT VICTIM] |
04:20.04 | *** join/#htc-linux infernix (i=nix@unaffiliated/infernix) [NETSPLIT VICTIM] |
04:20.04 | *** mode/#htc-linux [+o ChanServ] by irc.freenode.net |
04:21.48 | tmzt | that's why I said _probe, there is no reason to hardcode something in the board pdata that isn't board dependent, in this case it's dependent on microp fw and therefore on the spl |
04:21.53 | tmzt | radio.img |
04:25.45 | *** join/#htc-linux nextime (n=nextime@unaffiliated/nextime) [NETSPLIT VICTIM] |
04:25.45 | *** join/#htc-linux _workkaze (n=kaze@ABordeaux-152-1-74-161.w86-196.abo.wanadoo.fr) [NETSPLIT VICTIM] |
04:25.46 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) [NETSPLIT VICTIM] |
04:25.46 | *** join/#htc-linux ecze (n=ecze@eczema.ecze.com) [NETSPLIT VICTIM] |
04:25.46 | *** join/#htc-linux lama (i=lama@netbsd.pl) [NETSPLIT VICTIM] |
04:25.46 | *** join/#htc-linux defiant (n=add@p0pc0rn.eu) [NETSPLIT VICTIM] |
04:26.14 | *** join/#htc-linux ChanServ (ChanServ@services.) |
04:26.15 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) [NETSPLIT VICTIM] |
04:26.15 | *** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-180-11.customer.ch.netstream.com) |
04:26.15 | *** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1) [NETSPLIT VICTIM] |
04:26.15 | *** join/#htc-linux Skitzo_ (n=DCLXVI@eth582.vic.adsl.internode.on.net) [NETSPLIT VICTIM] |
04:26.15 | *** join/#htc-linux infernix (i=nix@unaffiliated/infernix) |
04:26.15 | *** mode/#htc-linux [+o ChanServ] by irc.freenode.net |
04:30.48 | *** join/#htc-linux woodyPL (i=woody@gateway/shell/blinkenshell.org/x-705bf255c65a1d46) |
04:39.19 | *** join/#htc-linux woodyPL_ (n=woody@gateway/shell/blinkenshell.org/x-8369b07878e5dcf2) |
04:47.57 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
05:10.54 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
05:48.24 | *** join/#htc-linux kal (n=chatzill@87-194-8-141.bethere.co.uk) |
05:51.25 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
05:53.30 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
06:20.26 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
06:31.31 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
06:44.53 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
06:45.26 | *** join/#htc-linux Moku (n=John@g227123024.adsl.alicedsl.de) |
06:46.00 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
06:46.03 | Untouchab1e | Good morning :D |
06:47.31 | *** join/#htc-linux yoyey (n=yoann@bro69-3-82-237-160-83.fbx.proxad.net) |
06:51.51 | *** join/#htc-linux woodyPL (n=woody@gateway/shell/blinkenshell.org/x-88074a60c24ba5c2) |
06:53.42 | Balsat | Good morning |
06:55.18 | *** join/#htc-linux holycow (n=bite@S01060016b6b53675.vf.shawcable.net) |
06:57.26 | maejrep | cr2: in case its useful, this is every "cc" data address I've captured in my haret logs, and the frequency of each: http://www.privatepaste.com/9b1xKD3tuf |
07:00.29 | maejrep | and every chip address: http://www.privatepaste.com/271dq0r0VX |
07:01.27 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
07:01.49 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-234-8.web.vodafone.de) |
07:12.45 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
07:13.47 | *** join/#htc-linux woodyPL_ (i=woody@gateway/shell/blinkenshell.org/x-344cc94fe8df2e7a) |
07:23.13 | cr2 | maejrep: the 118 "id" is something new |
07:25.57 | maejrep | yeah i forgot what that was from, but i recall seeing it |
07:26.23 | cr2 | maejrep: the *in *out is probably just a wince wrapup api. i'll check where the second parameter goes on the stack. if you see the unmodified voltage values in your trace , that's great |
07:27.05 | cr2 | it seems that we are going with an amazing pace :) |
07:27.08 | *** join/#htc-linux lpotter (n=ljp@58.173.176.153) |
07:27.11 | maejrep | i tried running the same pcom commands that I saw in the trace, and it froze my phone :p |
07:27.31 | maejrep | was trying to turn off and on the lcd |
07:27.34 | cr2 | maejrep: don't hardcode the gpio numeric numbers :) |
07:27.39 | cr2 | ok |
07:27.46 | maejrep | which numbers? |
07:27.50 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
07:27.52 | cr2 | in the driver |
07:27.57 | Untouchab1e | How did the lcd-power-project go? :) Ive been sleeping for a few drivers |
07:28.03 | cr2 | like gpio27, 39, and so on |
07:28.07 | Untouchab1e | few hours* |
07:28.09 | Untouchab1e | (lol) |
07:28.15 | maejrep | lol |
07:28.37 | maejrep | cr2: right, i thought I didn't, am i not using client->irq ? |
07:28.58 | cr2 | maejrep: i think it's a good idea to add .suspend and .resume, even if they'll be empty for now |
07:29.22 | Untouchab1e | Did anyone figure out the WiFi drivers? Since they are closed source and everything |
07:29.24 | maejrep | oh, you mean .irq = MSM_GPIO_TO_INT(27) ? |
07:29.31 | cr2 | the msm_touchscreen should be a platform_device , imho |
07:29.34 | cr2 | yes |
07:29.56 | cr2 | it belongs to the platform_data |
07:30.06 | maejrep | nods |
07:30.27 | cr2 | and 27 needs some good name |
07:30.41 | cr2 | in board-raphael.h |
07:30.54 | cr2 | because it does not say me anything :) |
07:30.59 | Untouchab1e | lol |
07:31.02 | maejrep | think it does something else other than keyboard? the wiki just says irq wakeup / "Ukey" |
07:31.37 | cr2 | says wince |
07:31.51 | maejrep | ah |
07:32.04 | cr2 | there are also Gkey, and some other *key |
07:32.20 | cr2 | Qkey is/was the keyboard ? |
07:32.31 | maejrep | Ukey |
07:32.39 | maejrep | 1-11 / 27 |
07:32.46 | cr2 | ok, they used Qkey name before |
07:33.24 | cr2 | hmm. if you've got vreg_level to work |
07:33.35 | cr2 | i'll loook at the epson mddi |
07:33.52 | cr2 | then we will have a sane lcd init. finally :) |
07:33.53 | maejrep | I was using straight msm_proc_comm_wince() calls to test, when it froze |
07:34.01 | maejrep | should I need any delays between them or anything? |
07:34.06 | cr2 | no |
07:34.27 | cr2 | a may be used for something else |
07:34.37 | cr2 | make wifi work :) |
07:34.43 | maejrep | lol |
07:34.51 | Untouchab1e | that would be nice :) |
07:34.56 | cr2 | c and d are not used by other subsystems |
07:35.00 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
07:35.05 | maejrep | c and d in proc comm? |
07:35.19 | cr2 | maejrep: yes, the wince ids |
07:35.26 | Untouchab1e | I have a question regard Haret.. When it boots Linux, does it shut down WinMo, or is WinMo technically idling in the backend? (As of such consuming system resources) |
07:35.47 | maejrep | it kills off wince for all intents and purposes |
07:35.58 | Untouchab1e | Ok, sounds good :) |
07:35.58 | maejrep | kinda like how a bootloader dies off after loading an OS |
07:36.05 | Untouchab1e | Ah, right! |
07:36.08 | cr2 | i find it cool that androids used 1<<vreg_id as proc_comm mask for us :) |
07:36.36 | maejrep | lol |
07:36.38 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
07:37.03 | *** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com) |
07:37.17 | cr2 | but it was not intentional i guess |
07:37.28 | cr2 | ok, must leave now |
07:37.31 | cr2 | bbl |
07:37.32 | Untouchab1e | aww :) |
07:37.33 | Untouchab1e | see you |
07:37.40 | Untouchab1e | have a nice one ^^ |
07:37.53 | Untouchab1e | maejrep, what is the top priority atm? |
07:38.09 | Untouchab1e | Mic/sound, lcd power.. or? :) |
07:38.34 | maejrep | i think cr2 really wants to get the vreg switch and levels working, cause that will enable us to move quicker |
07:38.45 | maejrep | and actually write proper init code for some devices |
07:39.11 | Untouchab1e | yeah, understandable.. :) |
07:39.28 | Untouchab1e | Im amazed on how quickly progress has been made |
07:40.05 | maejrep | i think i saw someone say that sound should just be setup via rpc, and the modem takes care of routing audio where it needs to go (at least for phone calls) |
07:40.41 | Untouchab1e | So audio for other purposes would be setup otherwise? |
07:41.23 | maejrep | yeah, though I couldn't tell you how :) i've only run linux on one other phone (vogue) and didn't touch any of the code for it |
07:41.31 | maejrep | so this is kind of a learning process for me ;p |
07:42.22 | *** join/#htc-linux pichurri (n=pichurri@users3.ilo.org) |
07:42.22 | Untouchab1e | hehe, tell me about it :) Ive been working with software development for quite a while, both asm and high-lvl programming, but I have no experience in Linux-programming |
07:43.33 | maejrep | heh I've never touched asm, but have been programming for years, done very little kernel hacking in the past, and currently a php web developer ;p |
07:43.58 | Untouchab1e | hehe, php is cool! Im mainly into .NET myself :) |
07:44.23 | Untouchab1e | but Android has taken up alot of my spare time lately.. So I wish I could contribute more in terms of coding here, but for now Im just making sure your hard work is being hosted and supported properly |
07:46.59 | Untouchab1e | Besides, I have both the DIAM100, Raph100 and the ADP1 at hand, hehe |
07:47.33 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
07:47.39 | Untouchab1e | good morning Balsat |
07:48.10 | Balsat | Goor morning UT |
07:48.14 | Balsat | good |
07:48.15 | Untouchab1e | hows things? |
07:48.31 | Untouchab1e | ;) |
07:49.54 | Balsat | Not good... i got 2 hours of sleep to night, so my head is spinning... you? |
07:50.31 | Untouchab1e | hehe, got 3 hours of sleep, so Im slightly better ^^ |
07:51.29 | Untouchab1e | just so keen on getting Android working :) |
07:51.59 | Untouchab1e | as I have the DIAM100, Raph100 and the ADP1 at hand, and I love Android, dislike the ADP1 hardware, but love teh raph Hardware.. so combining the two would be amazin |
07:52.01 | Balsat | This forum is taking a lot of my time... what to do when Android is 100% working? |
07:52.11 | Untouchab1e | hahah |
07:52.40 | Untouchab1e | Android will be develop constantly, so there will always be things to do |
07:52.45 | Untouchab1e | Cupcake for example ^^ |
07:52.56 | Balsat | Can you send SMS from from your diam100? |
07:53.03 | Untouchab1e | nope |
07:53.06 | Balsat | I can't anymore... strange |
07:53.19 | Untouchab1e | yeah, with your zImage that I tried yesterday, SMS-sending wasnt possible |
07:53.23 | Untouchab1e | havent tried it on my Raph |
07:54.09 | Balsat | I think the programmers is working on the smd0?? |
07:54.54 | Untouchab1e | really wants to get the vreg switch and levels working, as that will supposedly enable us to move quicker |
07:56.10 | Balsat | The progress looks very nice... sorry i cant help... i only know delphi, pascal |
07:57.11 | Untouchab1e | Yeah, Ive been doing a bit of ASM and alot of .NET, but never done any kernel programming |
07:58.34 | Balsat | I did som ASM long time ago, back at the Commandore 64 days.... gues thinks have change... or i hope so |
07:59.20 | Untouchab1e | hehe, the basics are probably basically the same, with variations from system to system |
08:00.01 | Balsat | Well back to work |
08:00.08 | Untouchab1e | hehe |
08:00.09 | Untouchab1e | good luck |
08:00.11 | Untouchab1e | have a good one |
08:00.21 | Balsat | u2 |
08:00.25 | Untouchab1e | thanks |
08:00.36 | Untouchab1e | My Scandinavian neighbour |
08:00.40 | Untouchab1e | ;) |
08:01.44 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
08:11.49 | *** join/#htc-linux pichurri (n=pichurri@users3.ilo.org) |
08:15.50 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
08:34.05 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
08:35.49 | *** join/#htc-linux woodyPL (n=woody@gateway/shell/blinkenshell.org/x-1f097ac9de48f2cd) |
08:40.28 | *** join/#htc-linux holycow (n=bite@S01060016b6b53675.vf.shawcable.net) |
08:42.36 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
08:51.22 | *** join/#htc-linux goxboxlive_ (n=goxboxli@185.84-48-126.nextgentel.com) |
09:16.45 | Untouchab1e | Anyone know of any really good or really bad software development projects? |
09:37.18 | *** join/#htc-linux dzo_ (n=dzo@121.98.128.127) |
09:45.24 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
10:02.42 | *** join/#htc-linux amazingdander (i=bite@gateway/tor/x-98e8e4aed282e981) |
10:16.06 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
10:18.30 | *** join/#htc-linux ionstorm (n=ion@ip68-227-226-5.ph.ph.cox.net) |
10:19.23 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B035F20.dip.t-dialin.net) |
10:21.26 | *** part/#htc-linux yoyey (n=yoann@bro69-3-82-237-160-83.fbx.proxad.net) |
10:32.07 | lupine_85 | did anyone manage to get maejraep's patch to apply? |
10:46.47 | *** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl) |
11:10.01 | Untouchab1e | Which patch was that again? the LCD-power one? |
11:12.31 | *** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk) |
11:13.13 | lupine_85 | no, the keyboard one |
11:35.27 | *** join/#htc-linux drasar (n=maik@lamer.optinet.cz) |
11:45.23 | marex | looks like some patch for htc himalaya landed in HH-kernel ML |
11:45.59 | marex | Im generally against merging it yet, it contains some problems (use checkpatch.pl for complete list) and contains changes that affect other devices with is no-go |
11:46.17 | marex | s/with/which/ |
11:48.22 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) |
11:56.37 | *** join/#htc-linux timebomb (n=tb@p5B3E56F1.dip.t-dialin.net) |
12:18.09 | *** join/#htc-linux PoohbaLT1 (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net) |
12:34.52 | *** part/#htc-linux Zinbolic (n=Zy@84.238.80.215) |
12:49.22 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
12:49.55 | *** join/#htc-linux juliusr (n=5b974d4e@lon92-8-88-165-13-120.fbx.proxad.net) |
12:57.25 | *** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net) |
12:57.32 | *** join/#htc-linux t3chi3 (n=blarg@ip24-250-216-85.ga.at.cox.net) |
13:13.28 | BabelO_ | marex: what device the htc himalaya patch use ? is it a blueangel ? i ve not the link of the ML and did not receive the patch |
13:15.57 | marex | I guess BA, yes |
13:16.07 | marex | iirc ML archive is at handhelds.org |
13:17.38 | BabelO_ | marex: ok, but i m registered on the ML and did not receive any mail :( |
13:17.44 | BabelO_ | ok i look |
13:23.00 | drasar | BabelO_: That himalaya patch is created by me |
13:23.48 | BabelO_ | drasar: i know yes :) |
13:23.56 | BabelO_ | but what did you change in blueangel driver ? |
13:24.06 | drasar | BabelO_: but I am doing some more code clean-up right now so ignore that patch please ;) |
13:24.30 | BabelO_ | drasar: ok |
13:25.05 | drasar | BabelO_: Just "Himalaya" -> "Blueangel" in some header file |
13:25.16 | BabelO_ | drasar: ok |
13:25.23 | drasar | BabelO_ |
13:25.25 | BabelO_ | drasar: so himalaya is fully working now ? |
13:26.15 | drasar | BabelO_: I mean text in a comment in head of that file. Somebody has forgtten to change it |
13:27.33 | BabelO_ | drasar: ok |
13:28.15 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net) |
13:28.18 | drasar | BabelO_: Not fully, but some of the components are working now |
13:28.55 | drasar | BabelO_: http://www.handhelds.org/hypermail/kernel-bugs/current/0236.html |
13:29.32 | *** join/#htc-linux piusvelte (n=chatzill@nat.philau.edu) |
13:29.51 | drasar | BabelO_: Have you got commit access to hh.org CVS? |
13:30.45 | BabelO_ | drasar: that is very good you update use all standard driver :) |
13:31.09 | BabelO_ | drasar: no, not me, ask cr2 when you see him in the evening :) |
13:32.54 | drasar | BabelO_: yes, cr2 should be here through weekend. I have asked him already ;) |
13:36.34 | drasar | It's a pity that kernel-bugs@handhelds.org ML seems to be dead lately |
13:51.57 | NetRipper | 04:17:12 < maejrep> trying to get msm_proc_comm_wince accessible from a test module |
13:52.38 | NetRipper | maejrep[w], i removed the export_symbol as i added the method to gpio.h instead, where all the other gpio.c functions are defined as well... so you just need to include gpio.h |
13:52.49 | NetRipper | maejrep[w], uh, wait, gpio != proc_comm |
13:53.15 | NetRipper | maejrep[w], for proc comm you need to include proc_comm_wince.h then it should work already ;) |
13:55.03 | Untouchab1e | Hi NetRipper! |
13:55.05 | Untouchab1e | Hows things? |
13:55.08 | NetRipper | hi Untouchab1e |
13:55.13 | NetRipper | things are fine |
13:55.14 | NetRipper | :) |
13:55.32 | Untouchab1e | glad to hear it :) |
13:55.51 | Untouchab1e | i dreamt about drivers.. lol |
13:56.00 | NetRipper | ouch |
13:56.02 | NetRipper | welcome to the horror |
13:56.06 | Untouchab1e | haha |
13:57.02 | NetRipper | you know the feeling, where your alarm clock goes off and you feel like you should change a flag, recompile and run it to turn it off? |
13:57.13 | Untouchab1e | hahaha |
13:57.28 | Untouchab1e | set the alarm_activate flag to 0 |
13:57.40 | NetRipper | yea and you're annoyed that you cannot do it runtime |
13:57.42 | NetRipper | stupid clock |
13:57.45 | Untouchab1e | lol |
13:58.06 | maejrep | NetRipper: doesn't work like that for a module -- get undefined symbol during modpost |
13:58.35 | NetRipper | maejrep, you can't include ../../../arch-arm/mach-msm/proc_comm_wince.h? |
13:59.11 | maejrep | that's not the problem :P I was including proc_comm_wince.h |
13:59.18 | Untouchab1e | I am curious though, are we close to another breakthrough? I know someone talked (cant remember who) about the lcd_power |
13:59.35 | maejrep | same with gpio_set_function patch -- even including gpio.h it would not work in a module |
13:59.36 | NetRipper | Untouchab1e, i'd call keyboard a breakthrough |
13:59.46 | maejrep | for a function to work in a module, you have to EXPORT_SYMBOL() that function |
13:59.51 | NetRipper | maejrep, ah |
14:00.02 | maejrep | but that wasn't working for me last night for some reason |
14:00.06 | Untouchab1e | NetRipper: which keyboarD? :) |
14:00.08 | maejrep | don't know why |
14:00.13 | Untouchab1e | keyboard* |
14:00.16 | NetRipper | Untouchab1e, maejrep made a keyboard driver, hardware keyboard |
14:00.19 | Untouchab1e | The Raph qwerty one? |
14:00.22 | NetRipper | yes |
14:00.26 | Untouchab1e | omg o.O |
14:01.09 | NetRipper | still need to think about how we are going to distinguish all those different kinds of keyboard layouts |
14:01.18 | maejrep | heh yes :P |
14:01.41 | NetRipper | maejrep, did you both use export and also the include? |
14:01.50 | *** join/#htc-linux exco (n=exco@e181083211.adsl.alicedsl.de) |
14:01.59 | maejrep | yes, still didn't work :/ |
14:02.05 | NetRipper | odd |
14:02.06 | Untouchab1e | yeah.. would be awsome if we could have an easy way to configure the keyboard layout. I have the nordic qwerty keyboard version on my Raph100, and I like the keyboard layout |
14:02.19 | maejrep | so instead i just compiled into the kernel and added a debugfs hook to test it |
14:02.22 | Untouchab1e | guess we could just edit the qwerty.kcm file like I did with the ADP1 |
14:02.28 | maejrep | anyway, most of our stuff probably won't be modules (?) |
14:02.47 | NetRipper | maejrep, did you update to the latest git by any chance? |
14:02.51 | maejrep | yes |
14:02.59 | NetRipper | maejrep, you must define CONFIG_MSM_AMSS_VERSION_WINCE |
14:03.10 | maejrep | yeah I did that :) |
14:03.11 | NetRipper | ok |
14:03.12 | NetRipper | good |
14:03.14 | maejrep | got the warning, etc |
14:03.17 | NetRipper | glad |
14:03.18 | NetRipper | :) |
14:03.46 | maejrep | that module issue is beyond me :/ dunno why it was happening, but I was only trying to test proc comm without having it in an init method |
14:04.17 | Untouchab1e | but maejrep, you said the keyboard wasnt working last night? |
14:04.22 | NetRipper | i cant think of a solution from the top of my mind either |
14:04.45 | NetRipper | maejrep, btw.. shouldnt the keymap be done in userspace instead of kernelspace? |
14:04.56 | NetRipper | i.e. that the keyboard driver only reports scancodes |
14:05.06 | NetRipper | and that userspace should convert it to the proper keys |
14:07.08 | NetRipper | or am i saying something stupid here |
14:07.09 | NetRipper | :P |
14:10.26 | maejrep | well, the kernel has to know what keys to report (think of no X) |
14:10.31 | maejrep | kernel keycodes != X keycodes |
14:10.59 | NetRipper | alright |
14:11.07 | NetRipper | so keyboard mapping is still possible in userspace |
14:11.10 | maejrep | I don't know if I can give the input subsystem raw scancodes and let it sort it out |
14:11.12 | NetRipper | you just define a 'default' in the kerenl |
14:11.13 | maejrep | of course |
14:11.14 | NetRipper | kernel* |
14:11.25 | maejrep | setkeycodes <...> |
14:11.32 | maejrep | or maybe setkeycode <.. > |
14:11.33 | NetRipper | so the qwerty.kcm method is probably still usable Untouchab1e |
14:11.49 | maejrep | yeah don't know what qwerty.kcm is ;x |
14:11.54 | NetRipper | http://forum.xda-developers.com/showthread.php?t=458473 |
14:12.02 | NetRipper | i think it's android-specific |
14:12.12 | NetRipper | Untouchab1e, do you know? |
14:12.52 | maejrep | i may be wrong about that, but was basing the code off htc-spi-kbd mostly |
14:13.27 | NetRipper | maejrep, regarding the module issue, i think the prototype may need to be specified with 'extern' |
14:13.36 | maejrep | I tried that as well ;x |
14:13.51 | NetRipper | arf |
14:14.10 | maejrep | it worked in my other module |
14:14.18 | NetRipper | so you made it extern AND export symbol? :P |
14:14.22 | maejrep | when I was using gpio_set_function |
14:14.31 | maejrep | yes, also tried without extern :p |
14:14.35 | NetRipper | ;) |
14:14.40 | NetRipper | but you cant use gpio either? |
14:15.05 | maejrep | i can use the generic gpio functions (which get mapped back to msm_gpio_* via the kernel gpio code) |
14:15.18 | maejrep | but those are exported with EXPORT_SYMBOL :) |
14:15.41 | NetRipper | ah |
14:15.49 | NetRipper | but you cant call msm_* |
14:15.55 | maejrep | right |
14:16.40 | NetRipper | so i guess you're not allowed to call anything arch-specific from a module |
14:16.40 | NetRipper | ;) |
14:16.50 | NetRipper | which seems pretty fair to me |
14:17.12 | NetRipper | but annoying nonetheless |
14:17.15 | maejrep | well, i was calling msm_gpio_set_function() in my test |
14:17.19 | maejrep | because I exported it :p |
14:17.33 | NetRipper | so export worked for that one? |
14:17.36 | maejrep | right |
14:17.40 | maejrep | that's what baffles me :P |
14:17.42 | NetRipper | just not for proc comm |
14:18.21 | Untouchab1e | I know a bit about the qwerty.kcm file.. |
14:18.35 | Untouchab1e | h/o |
14:19.00 | Untouchab1e | http://forum.xda-developers.com/showthread.php?t=468703 |
14:19.07 | Untouchab1e | basically a step-by step guide on how to do it |
14:19.52 | NetRipper | ok |
14:20.22 | NetRipper | but its android-specific |
14:20.28 | NetRipper | which is a pain |
14:20.28 | NetRipper | :) |
14:20.29 | maejrep | anyway, it wasn't a big deal but is useful to be able to unload/load a module to test something without having to reboot, recompile, copy, start haret, etc |
14:20.50 | NetRipper | maejrep, you use scp to transfer the files? |
14:20.54 | maejrep | yeah |
14:21.03 | NetRipper | it's nice indead |
14:21.08 | NetRipper | indeed* |
14:21.18 | Untouchab1e | (sorry, packing here)... but yeah, its Android specific |
14:21.22 | Untouchab1e | unfortunately |
14:21.31 | Untouchab1e | :) |
14:21.32 | maejrep | ok off to work |
14:21.36 | Untouchab1e | hehe |
14:21.39 | NetRipper | there are linux-specific solutions but not sure if it'll work in android then ;) |
14:21.43 | NetRipper | one or the other ;) |
14:21.44 | Untouchab1e | hmm.. |
14:21.51 | NetRipper | hf maejrep ;) |
14:22.06 | Untouchab1e | have a niec one Maejrep |
14:22.34 | Untouchab1e | If we get the qwerty keyboard with a standard layout, thats still awesome though, considering the qwerty keyboard on the G1 doesnt haven anything else either |
14:25.50 | lupine_85 | maejrep: the patch you posted last night failed to apply against head to me |
14:25.53 | lupine_85 | for me* |
14:29.55 | NetRipper | Untouchab1e, there are some annoying differences among devices though.. ;) check out http://wiki.xda-developers.com/index.php?pagename=RaphaelKeyboard |
14:30.59 | Untouchab1e | aah |
14:31.35 | Untouchab1e | I guess nothing is ever easy :P |
14:32.30 | NetRipper | ;) |
14:33.44 | NetRipper | we can see the difference between CDMA and GSM but we can't detect the RAPH110 (from raph100) and RAPH500 (from raph800) yet |
14:34.04 | Untouchab1e | ahh... |
14:34.34 | Untouchab1e | Never found out about any difference between the the R100 and the R110? |
14:34.36 | lupine_85 | did anyone else get it to apply? can we has it in git? |
14:46.46 | Untouchab1e | Im off for the weekend :) |
14:46.53 | Untouchab1e | Have a great weekend people :) |
14:49.47 | NetRipper | lupine_85, i'll put it in git later |
14:50.00 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
14:51.37 | NetRipper | lupine_85, you can apply it using the --rejects flag, and then merge the rejects yourself |
14:51.55 | NetRipper | flag = param... git apply --rejects <file> |
14:52.09 | lupine_85 | I'd rather have a clean patch ;) |
14:52.19 | lupine_85 | it looks like it was truncated at the end or something? |
14:52.45 | NetRipper | oh, it probably misses an empty line |
14:52.53 | NetRipper | add an empty line at the end of the downloaded file |
14:52.55 | NetRipper | see if it applies then |
14:52.59 | lupine_85 | haha |
14:53.03 | AstainHellbring | morning |
14:53.14 | NetRipper | i had it a while back as wel |
14:53.25 | NetRipper | pastebin trim()s it i guess |
14:53.37 | NetRipper | morning astain |
14:54.08 | AstainHellbring | whats new NetRipper? |
14:54.58 | lupine_85 | NetRipper: nah, it complains about trailing whitespace in places too |
14:55.02 | lupine_85 | fatal: git-apply: bad git-diff - expected /dev/null on line 106 |
14:55.40 | NetRipper | lol, that git-apply is a bit sucky |
14:55.50 | NetRipper | do a patch -p1 < file.patch |
14:55.56 | NetRipper | while in the root of your kernel tree |
14:56.02 | NetRipper | that'll complain less |
14:56.44 | NetRipper | git-apply doesn't do new files i guess.. it also doesn't include new files in diffs |
14:59.25 | NetRipper | worked for me.. wget -O microp.patch http://www.privatepaste.com/e11uUWKu8G/download && echo "" >> microp.patch && patch -p1 < microp.patch |
15:00.34 | NetRipper | i should get back to work |
15:00.35 | NetRipper | bbl |
15:00.51 | NetRipper | AstainHellbring, oh btw, keyboard is new ;) check the logs of before you joined for some info |
15:01.45 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net) |
15:01.47 | *** join/#htc-linux addman333 (n=azachars@nat/sun/x-2d773521a22f66db) |
15:01.58 | AstainHellbring | looks like the logs don't have anything for today yet |
15:02.36 | lupine_85 | aha, got it top apply :) |
15:02.45 | lupine_85 | to* |
15:05.33 | lupine_85 | I have to change the scancode data for the raph100... |
15:05.39 | lupine_85 | humm, how best to do it |
15:06.17 | NetRipper | i have the raph100 as well |
15:06.38 | NetRipper | i'm still thinking on what the best way is |
15:06.44 | NetRipper | perhaps we should do it in userspace |
15:06.57 | NetRipper | leave only one layout in kernel |
15:07.08 | NetRipper | astainhellbring, use http://irclog.iclem.net/?chan=htc-linux for logs, it's realtime |
15:07.15 | NetRipper | if i could only find someone to add that link to topic.. |
15:07.31 | AstainHellbring | that would be nice |
15:09.15 | lupine_85 | NetRipper: well, we could assume that keycodes change depending on the MicroP version |
15:09.15 | lupine_85 | (rather than model) |
15:09.18 | lupine_85 | then have maps in the kernel for different microp versions |
15:09.33 | lupine_85 | (well, different groups of microp versions) |
15:10.10 | lupine_85 | that's how I'd do it in kernelspace. Dunno how one would do it in userpace |
15:11.20 | NetRipper | how sure are we that each different keyboard layout can be identified with the microp version |
15:12.38 | lupine_85 | raph800 has a different microp kbd version to raph100 |
15:12.46 | NetRipper | ok |
15:12.50 | lupine_85 | but |
15:12.56 | NetRipper | which operator do you have lupine? |
15:13.02 | lupine_85 | I'd imagine the versions might change between operators, roms, etch |
15:13.05 | lupine_85 | voda UK |
15:13.07 | NetRipper | exactly |
15:13.19 | NetRipper | uk layout may differ from dutch |
15:13.22 | lupine_85 | hence why you'd have keycode maps for sets of versions |
15:13.49 | lupine_85 | you might get the same version of microP with different keycodes, if unlucky |
15:13.52 | NetRipper | if your raph100 reports a different version than my raph100, would be nice |
15:14.00 | lupine_85 | what version does yours say? |
15:14.01 | exco | ~seen pH5 |
15:14.01 | apt | ph5 <n=ph5@p5485D104.dip.t-dialin.net> was last seen on IRC in channel #openezx, 4d 21h 21m 40s ago, saying: 'I don't even see pxafb come up, so I guess it's time for some gpio led debugging.'. |
15:14.09 | NetRipper | i dont know, havent booted yet |
15:14.17 | NetRipper | still at wrk |
15:14.19 | lupine_85 | (I pulled my version from the SPL) |
15:14.28 | NetRipper | oh |
15:15.32 | AstainHellbring | how can one check microp version other than spl? |
15:15.37 | lupine_85 | i2c reads |
15:15.49 | lupine_85 | presumably, that's what the spl does too |
15:16.09 | AstainHellbring | interesting ok how can one check it via spl? |
15:16.26 | lupine_85 | you just soft reset with VolDown held |
15:16.37 | AstainHellbring | so just jump into bootloader? |
15:17.05 | AstainHellbring | ic cool |
15:17.28 | AstainHellbring | MicroP-Raph (LED) v13 MicroP-Raph (KEY) v5 |
15:18.17 | lupine_85 | AstainHellbring: what model/operator/country/key layout is your phone? |
15:18.36 | lupine_85 | (and what's the version for the raph100?) |
15:18.36 | AstainHellbring | its euro TP with front cam raph 100 |
15:18.58 | lupine_85 | I'm v5 also |
15:19.03 | AstainHellbring | bought it from a importer |
15:19.11 | AstainHellbring | the 800 coming in a sec |
15:19.14 | lupine_85 | AstainHellbring: do you have weird non-UK-english characters on the keyboard? |
15:19.53 | AstainHellbring | wierd characters? |
15:20.13 | lupine_85 | Åe¶ŧâââøþæÃðÄÅħklklll |
15:20.19 | lupine_85 | whoops |
15:20.37 | AstainHellbring | the raph 800 reports MicroP-Hermann (LED) v0C85 MicroP-Herman (KEY) v0685 |
15:21.10 | lupine_85 | <PROTECTED> |
15:21.11 | NetRipper | i have a UK version of the raph as well |
15:21.16 | NetRipper | so cant tell |
15:21.18 | lupine_85 | (just the last one) |
15:22.19 | NetRipper | v13/v5 here as well, but i have uk raph100.. |
15:23.28 | lupine_85 | I think the choice is using the version numbers or mtypes if we do it in kernel |
15:23.41 | *** join/#htc-linux MethoS (n=lem@host-091-096-215-140.ewe-ip-backbone.de) |
15:24.29 | AstainHellbring | will have fuze microp in a sec |
15:25.10 | AstainHellbring | looks like fuze is v5 too |
15:26.17 | lupine_85 | balls |
15:26.21 | lupine_85 | that's the end of that then :p |
15:29.54 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
15:30.34 | toer | øæå |
15:31.36 | toer | isnt the special characters fn + key on the keyboards anyway |
15:34.50 | lupine_85 | UK one, certainly |
15:35.14 | lupine_85 | OOTB versions can't distinguish between raph100 and raph1100 |
15:35.18 | lupine_85 | (anyway) |
15:35.36 | XD | microp? |
15:36.36 | AstainHellbring | <PROTECTED> |
15:36.40 | AstainHellbring | microp same |
15:37.28 | lupine_85 | doesn't really like the idea of that many mtypes |
15:38.22 | NetRipper | me neither |
15:38.50 | NetRipper | which is why i think we should solve it in userspace ;) |
15:38.54 | lupine_85 | yeah |
15:38.57 | XD | AstainHellbring, |
15:39.02 | AstainHellbring | yes? |
15:39.03 | lupine_85 | userspace input driver? |
15:39.05 | XD | no wth is a microp |
15:39.07 | XD | lol |
15:39.11 | XD | micro operating sys? |
15:39.22 | lupine_85 | XD: it's an API |
15:39.36 | lupine_85 | we talk to it via i2c to get keyboard data |
15:39.48 | XD | i see |
15:42.27 | NetRipper | raph100 | raph110 | raph500 | raph800 | diam100 | diam300 | diam500 | diam800 |
15:42.33 | NetRipper | am i missing any known types? |
15:42.40 | NetRipper | raph300 perhaps? diam110? |
15:42.45 | NetRipper | or do i have types there that dont exist |
15:43.02 | AstainHellbring | no diam110 yet or raph 300 that I have heard of |
15:43.10 | NetRipper | ok |
15:43.25 | lupine_85 | someone mentioned a raph400 but I dunno if thast was just a typo |
15:43.59 | NetRipper | anyone know the msmsdcc_id for raph110,500 and diam300,500? |
15:44.04 | AstainHellbring | lupine_85 was typo |
15:44.17 | AstainHellbring | NetRipper how one check those? |
15:44.32 | NetRipper | the msmsdcc_id passed to the kernel to get mmc working |
15:44.45 | NetRipper | you check it by experimenting (easiest way) |
15:44.54 | AstainHellbring | lol |
15:45.07 | NetRipper | i.e. when a diam500 user has android 1.0 working, which msmsdcc_id is he using ;) |
15:45.13 | NetRipper | in his default.txt |
15:45.23 | NetRipper | i know a few, but not those |
15:45.28 | XD | lupine |
15:45.34 | XD | that raph400 was me |
15:45.37 | XD | and it was a typo |
15:45.41 | XD | it's a 500 |
15:46.22 | NetRipper | XD |
15:46.27 | NetRipper | did you get android 1.0 working on your phone? |
15:46.33 | XD | nope |
15:46.39 | NetRipper | oh |
15:46.44 | NetRipper | or didnt you try? |
15:46.48 | XD | any updates in the last few days? |
15:46.51 | XD | I did |
15:46.55 | NetRipper | what happened? |
15:47.02 | XD | colors were off |
15:47.08 | NetRipper | besides that |
15:47.11 | lupine_85 | hmm. newest kernel doesn't pick up the sd card here |
15:47.24 | NetRipper | lupine_85 restart and try again |
15:47.36 | XD | screen didn't seem to work, it didn't look like the andriod I was used to |
15:48.00 | NetRipper | XD but did you get to the android screen? even though it was not proper |
15:48.04 | lupine_85 | (this is with the keyboard driver compiled in) |
15:48.06 | NetRipper | passed the loading screen |
15:48.18 | XD | ya |
15:48.26 | XD | after I went to a previous version |
15:48.28 | NetRipper | XD ok, which msmsdcc_id kernel parameter are you using in default.txt? |
15:48.35 | XD | that worked for raph500 |
15:48.51 | XD | newest vers a few days ago had kb issues |
15:49.09 | NetRipper | ok |
15:49.14 | NetRipper | check your default.txt pls |
15:49.16 | NetRipper | :) |
15:49.48 | XD | I'm trying to get my phone replaced by verizon, so I have flashed it to stock rom and cleaned it all out |
15:49.51 | XD | hehe |
15:50.10 | NetRipper | ah |
15:50.17 | NetRipper | it was on your sd card, you didnt need toc lean that ;) |
15:50.29 | XD | it wasn't |
15:50.32 | XD | it was on internal |
15:50.37 | XD | I don't have a sd yet |
15:50.38 | NetRipper | er, ok.. how could it mount then |
15:50.43 | NetRipper | aha |
15:50.45 | XD | lol |
15:50.50 | AstainHellbring | brb |
15:50.52 | XD | idk but it did |
15:50.54 | XD | o_O; |
15:50.54 | NetRipper | it's not possible that you booted android 1.0 then ;) |
15:51.05 | XD | lol |
15:51.08 | XD | I booted something |
15:51.20 | NetRipper | android 0.8 perhaps |
15:51.25 | NetRipper | old one |
15:51.27 | XD | ya |
15:51.33 | lupine_85 | right, just tried the previous zImage again and that works. time for newest again... |
15:51.36 | XD | the new one wouln't let me type |
15:51.37 | NetRipper | ok |
15:52.10 | NetRipper | lupine_85 may be caused by differences between raph800 and raph100 |
15:52.19 | NetRipper | lupine_85 oh, btw, lol |
15:52.29 | NetRipper | lupine_85 you need to ignore some changes in board-raphael.c |
15:52.42 | maejrep[w] | <PROTECTED> |
15:52.48 | NetRipper | lupine_85, it changes gpio's |
15:52.51 | lupine_85 | yeah, that'd do the trick |
15:52.59 | maejrep[w] | lupine_85: it should definitely apply against git head, cause I did a pull just before creating the diff |
15:53.06 | NetRipper | thus it probably thinks sd card is not in |
15:53.27 | lupine_85 | maejrep[w]: it wasn't a git-apply patch and/or it got a bit mangled in privatepaste |
15:53.28 | maejrep[w] | although, i accidentally included the GPIOs for raph800 in the diff ;x so you'll want to revert those last 3 changes in the board-raph file |
15:53.31 | lupine_85 | it's applied now |
15:53.38 | lupine_85 | I've updated the .keys to be raph100 |
15:53.47 | lupine_85 | it's only really the top row that differs |
15:54.12 | *** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de) |
15:54.55 | maejrep[w] | <PROTECTED> |
15:55.05 | NetRipper | cr2, http://wiki.xda-developers.com/index.php?pagename=MSM_SDIO (at bottom) i'll enter more when i know them.. may look through forum to find them out |
15:55.31 | maejrep[w] | but I guess a "major" version could be considered (ie, raph800 so far I've seen 0685 and 0682, so 0680 is at least common) |
15:55.37 | NetRipper | maejrep, we already found the raph110 returns same as raph100 ;) |
15:56.37 | maejrep[w] | oh that sucks |
15:56.39 | maejrep[w] | 0685? |
15:57.00 | maejrep[w] | if model id were actually where the research page says it should be in smem, we could use that :) |
15:57.00 | NetRipper | at least spl returns the same.. i suspect your version thingy to return the same as what spl does |
15:57.08 | maejrep[w] | yup |
15:57.39 | NetRipper | dump smem and search for it? :p |
15:57.48 | maejrep[w] | I think I have ... |
15:57.56 | maejrep[w] | I'll have to see if I can get to my home machine yet |
15:58.08 | maejrep[w] | I think my roommate changed the port forwarding ;x |
15:58.16 | NetRipper | lol |
15:58.20 | NetRipper | roommates-- |
15:58.33 | NetRipper | i gtg, talk to you later |
15:58.44 | maejrep[w] | :| |
15:59.00 | lupine_85 | reverts those three changes, recompiles |
15:59.13 | *** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com) |
16:02.09 | cr2 | NetRipper: does the phone work on raph ? |
16:03.45 | cr2 | there are only versions 5, 85 and 82. everything else will not be served |
16:05.16 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
16:05.53 | lupine_85 | it booted! |
16:05.57 | lupine_85 | but I forgot about the VDH |
16:05.59 | AstainHellbring | what did lupine_85? |
16:06.29 | lupine_85 | kernel with keyboard driver in |
16:06.31 | cr2 | lupine_85: can you compile the tiacx driver ? |
16:06.42 | AstainHellbring | nice |
16:06.58 | lupine_85 | cr2: haven't tried, am at work right now |
16:07.07 | lupine_85 | I've just got a spare 20 minutes or so |
16:07.16 | cr2 | ok |
16:07.34 | cr2 | we will soon need it :) |
16:08.02 | AstainHellbring | cr2 whats the tiacx driver do? |
16:08.08 | lupine_85 | wifi |
16:08.34 | cr2 | AstainHellbring: does the phone/ gps work ? |
16:08.51 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) |
16:08.59 | maejrep[w] | i don't know where the gps buffer is on raph800 |
16:09.26 | cr2 | maejrep[w]: do you use the vogue or the g1 driver ? |
16:09.33 | maejrep[w] | eh? |
16:09.41 | cr2 | smd |
16:09.43 | maejrep[w] | i'm talking about smem -- gps buffer doesn't appear anywhere in my smem dump |
16:09.59 | maejrep[w] | i'm not using smd at all yet, still need to do the vogue hack for AT buffer |
16:10.03 | AstainHellbring | cr2 I dont think it does not tried any of the latest kernels on either raphs yet |
16:10.33 | cr2 | maejrep[w]: the diam/raph layout is g1-like |
16:10.48 | maejrep[w] | cr2: I don't know where gps data is.. even when using the htc gps test tool (and can see/log active gps commands), and dumping all of smem, it does not show up anywhere |
16:11.26 | cr2 | ok |
16:11.58 | cr2 | maejrep[w]: the kaiser wiki has 2k+24 header for each channel |
16:12.16 | maejrep[w] | right |
16:12.19 | cr2 | maejrep[w]: and raph/diam the 0x14+8k |
16:12.27 | cr2 | 8k+20 |
16:12.51 | cr2 | g1 is 20byte header too |
16:12.52 | maejrep[w] | the AT buffer at least does not have an adjacent head like the other smd channels (even on raph800) |
16:13.04 | cr2 | all the channels are an array of that soize |
16:13.17 | maejrep[w] | yes, but only the auto-detected channels :) |
16:13.23 | maejrep[w] | and the AT buffer is not in that list |
16:13.32 | cr2 | it hason my raph100 , i've check my 1f |
16:13.45 | maejrep[w] | yes, raph100 is auto-detected |
16:13.49 | cr2 | DS ? |
16:13.53 | maejrep[w] | but raph800 is not, the buffer lives elsewhere |
16:13.59 | maejrep[w] | right, raph800 does *not* find a DS channel |
16:14.03 | maejrep[w] | it starts at "DATA2" |
16:14.05 | cr2 | weird |
16:14.12 | cr2 | ok |
16:14.15 | maejrep[w] | also finds DATA5, etc |
16:14.24 | maejrep[w] | trying to get into my home box, and I can find that for sure |
16:14.43 | cr2 | i'll try with umts |
16:14.55 | lupine_85 | hmm, keyboard doesn't appear to be working here |
16:15.01 | lupine_85 | but I can't do much debug |
16:15.02 | maejrep[w] | :o |
16:15.14 | maejrep[w] | is it the wrong gpio/irq? |
16:15.25 | cr2 | i still don't understand how to determine the array offset |
16:15.42 | cr2 | maejrep[w]: don't hardcode the gpios/irqs :) |
16:15.46 | maejrep[w] | try in haret: joinlist traces gpios, then wirq (ibit gpios as needed) |
16:16.04 | maejrep[w] | cr2: its hard coded in pdata, which as i understand it is the only/best way (?) |
16:16.07 | lupine_85 | maejrep[w]: I@m at work |
16:16.08 | lupine_85 | :p |
16:16.11 | cr2 | maejrep[w]: all the raph100 dtaa is in the wiki |
16:16.11 | maejrep[w] | oh |
16:16.13 | cr2 | ? |
16:16.28 | maejrep[w] | cr2: but it doesn't say "this is the keyboard irq lol" |
16:16.39 | *** join/#htc-linux mib_fqbppw (i=4d14b78a@gateway/web/ajax/mibbit.com/x-eba3ab96c3055280) |
16:16.57 | maejrep[w] | so gpio 27 may not be the same one on raph100 :| |
16:17.12 | lupine_85 | and which /win 2 |
16:17.33 | cr2 | ok |
16:17.49 | maejrep[w] | it doesn't show up in "show gpios" either, so you have to do it in traces & wirq |
16:18.00 | lupine_85 | I can't even get a terminal on the machine right now to play properly |
16:18.04 | lupine_85 | it might just be X |
16:18.08 | cr2 | 83 0x53 3 15 I irq (key poweron?) arm9dex related, Gkey |
16:18.13 | maejrep[w] | oh could be |
16:18.24 | maejrep[w] | i am still running the angstrom initrd |
16:18.27 | cr2 | this is the power button afaik |
16:18.34 | maejrep[w] | yeah I think that's right |
16:18.50 | maejrep[w] | I use gpio 27 though, 1-11 |
16:18.52 | maejrep[w] | labeled Ukey |
16:19.21 | cr2 | 27 0x1b 11 irq (Y) wakeup, Ukey |
16:20.26 | cr2 | ok, i don't see any other |
16:23.50 | cr2 | maejrep[w]: i don't see the bt driver for g1 ? |
16:24.08 | cr2 | btw, where can i download the closed source g1 parts? |
16:24.25 | lupine_85 | maejrep[w]: so change the .clamshell gpio to 83 ? |
16:26.00 | cr2 | NetRipper: i think that your entried are not correct |
16:27.17 | cr2 | s/entried/entries/ |
16:28.25 | cr2 | NetRipper: you have only 2 muxed SD ports, 7201A has 4 |
16:28.53 | maejrep[w] | lupine_85: no, if there's a problem it would be the .irq in board-raph's pdata |
16:28.57 | cr2 | and (i think) g1 sdcc driver does not support multiplexing |
16:29.25 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
16:29.43 | cr2 | maejrep[w]: set the pdata depending on the mtype |
16:30.05 | cr2 | don't staticlally compile it into the kernel |
16:30.10 | lupine_85 | ho hum, yay fun |
16:30.22 | cr2 | the g1 code hardcodes too much imho ;) |
16:31.54 | cr2 | btw, why doesn't NetRipper configuring the ts irq as rising edge ? |
16:32.19 | maejrep[w] | cr2: sure, but what happens if there's a difference between raph100 and raph110, etc |
16:32.28 | maejrep[w] | where we don't have mtypes |
16:32.48 | cr2 | use kernel command line parameter |
16:32.55 | maejrep[w] | :X |
16:33.05 | maejrep[w] | i'd like to make it module related |
16:33.24 | cr2 | agreed |
16:33.37 | cr2 | as modular as possible will be nice |
16:33.43 | maejrep[w] | that is, compiled as a module with module parameters |
16:33.55 | maejrep[w] | but i guess that may not be a good idea :P |
16:34.03 | cr2 | it forces good coding style :) |
16:34.14 | maejrep[w] | did you see my discussion with tmzt last night, about my thoughts on how to refactor it? |
16:34.26 | cr2 | mfd ? |
16:34.34 | maejrep[w] | that was his idea yeah |
16:34.46 | cr2 | we will get leds and bkl too |
16:35.06 | cr2 | so the microP will be close to asic3 in complexity |
16:35.23 | maejrep[w] | my thought was having 2 chip drivers for interacting with 0xce, and for 0xcc. and an input driver that a) requests the gpio27 irq, b) reads scancodes from the KSC chip driver, c) requests a notification reset from the KLT driver |
16:35.52 | cr2 | ok |
16:35.59 | cr2 | it's o the i2c side |
16:36.09 | cr2 | but you also need the subdrivers |
16:36.20 | maejrep[w] | yeah, the idea being the keyboard driver would not interact with i2c directly, but with the chip drivers |
16:36.23 | cr2 | for led(s)/backlight(s) |
16:36.25 | maejrep[w] | is that a bad way of doing it? |
16:36.50 | cr2 | why ? |
16:36.59 | maejrep[w] | why what :o |
16:37.23 | cr2 | why is it a bad way ? |
16:37.30 | maejrep[w] | I was asking if its a bad way :) |
16:38.09 | cr2 | no |
16:38.22 | drasar | Hi cr2. Have you got CVS access already? |
16:38.35 | maejrep[w] | so we'd end up with a microp_kbd driver, and two i2c chip drivers: microp_klt and microp_ksc (and others for accelerometer and so on) |
16:39.00 | cr2 | drasar: no, but i have got a different idea how i can do it. |
16:39.41 | cr2 | maejrep: and the led driver and backlight driver |
16:40.08 | drasar | cr2: Great. You can find the latest patch at http://www.handhelds.org/hypermail/kernel-bugs/current/0238.html |
16:40.11 | cr2 | maejrep[w]: you only need to sort out the module dependencies right |
16:40.20 | cr2 | drasar: ok |
16:40.48 | maejrep[w] | cr2: as in, led and backlight drivers that are also not interacting with the i2c-msm bus directly, but with the microp-led i2c chip driver, yes? |
16:41.14 | cr2 | drasar: i don't see why you can't match ba in capabilities. the only dark area is the backpack, and bt. but bt may be done too. |
16:41.52 | cr2 | maejrep[w]: yes, they need the 0xcc/2 channel |
16:43.23 | cr2 | maejrep[w]: does the haret-w.exe from j820 work on raph800 ? |
16:43.34 | maejrep[w] | cr2: but you agree that the i2c chip drivers should only expose functions for performing specific actions, not implement driver functionality (like keyboard and led behavior) |
16:43.40 | maejrep[w] | I don't know what haret-w is |
16:44.00 | cr2 | maejrep[w]: yes |
16:44.11 | cr2 | maejrep[w]: it's what mfd is about |
16:44.16 | maejrep[w] | ok, then I'll work on splitting that out then |
16:44.29 | maejrep[w] | well, if it's mfd, where would the drivers go? :P |
16:44.36 | maejrep[w] | i2c/chips/* or linux/mfd/* ? |
16:45.54 | cr2 | mfd should load the i2c/chips/ |
16:46.18 | cr2 | hmm, sf.net has broken something |
16:47.01 | cr2 | http://jornada820.sourceforge.net/files/haret/haret-w.exe |
16:47.30 | maejrep[w] | what does it do differently |
16:48.15 | cr2 | it has more commands |
16:48.26 | cr2 | to control the bt and bkl remotely |
16:48.56 | cr2 | pwrctl, btctl, irctl and wifi |
16:48.59 | maejrep[w] | downloading it now |
16:49.07 | cr2 | but wifi is not portable enought |
16:49.09 | maejrep[w] | not sure if I can get RNDIS support on os x though |
16:49.18 | cr2 | you need to know the wifi device name in wince |
16:49.24 | maejrep[w] | cr2: it doesn't find Raphael |
16:49.31 | maejrep[w] | says "Generic ARM v6" |
16:49.36 | cr2 | to switch off the wifi using this way |
16:49.38 | maejrep[w] | for raph, we needed to patch haret to find it |
16:50.09 | cr2 | maejrep[w]: hmm, but does the command itself work ? |
16:50.21 | maejrep[w] | will try, just a sec |
16:50.34 | maejrep[w] | gonna need to try wifi since rndis isn't setup here |
16:50.38 | cr2 | it's a portable part, no msm-specific things there |
16:50.49 | cr2 | ok |
16:51.25 | cr2 | i didint have time/mmod to merge it into mainline haret |
16:51.45 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
16:51.48 | cr2 | because of some strange headers |
16:52.59 | *** part/#htc-linux mib_fqbppw (i=4d14b78a@gateway/web/ajax/mibbit.com/x-eba3ab96c3055280) |
16:53.08 | *** join/#htc-linux mib_fqbppw (i=4d14b78a@gateway/web/ajax/mibbit.com/x-eba3ab96c3055280) |
16:57.15 | cr2 | maejrep: do you think that an uart may be used for ATCMD ??? not impossible, but still very strange |
16:57.59 | dream_kill | hi |
16:58.04 | maejrep[w] | I don't know anything about uart, what it is, what it does, or how it does it :) |
16:58.23 | dream_kill | what's the updates on the raph100 progress? |
16:58.25 | cr2 | ok |
16:58.51 | dream_kill | is the nand driver working for it? |
16:58.56 | cr2 | dream_kill: does the phone/gps work for you ? |
16:58.58 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
16:59.04 | maejrep[w] | i don't think anyone has worked on nand yet |
16:59.15 | cr2 | dream_kill: nand can be checked in dmesg output |
16:59.30 | dream_kill | did u tested the g1 nand driver? |
16:59.34 | dream_kill | it should work fine |
16:59.37 | dream_kill | as is same cpu |
16:59.43 | cr2 | maejrep[w]: the partitions, but the driver may id the chip itself |
16:59.44 | dream_kill | and same chip |
17:00.17 | dream_kill | i managed to full dump the g1 nand chip :D |
17:00.21 | cr2 | dream_kill: it's mainly about the partitions, not the chip driver itself. |
17:00.33 | dream_kill | the partitions is done BY the SPL |
17:00.39 | dream_kill | in G1 same |
17:00.46 | dream_kill | the partition table is done by the spl |
17:00.54 | dream_kill | it pass to kernel the partition table |
17:01.01 | cr2 | spl is irrelevant |
17:01.01 | maejrep[w] | that's odd |
17:01.08 | dream_kill | i tested it |
17:01.13 | cr2 | you need to know the byte offsets |
17:01.21 | dream_kill | got few bootloaders for g1 |
17:01.24 | cr2 | to add into the linux driver |
17:01.26 | dream_kill | and 1 is a mfg one |
17:01.42 | dream_kill | so when mfg spl i have a extra partition |
17:01.45 | dream_kill | mfg |
17:01.54 | dream_kill | when normal bootloader the mfg dissapear |
17:01.59 | drasar | cr2: What do you mean with it? |
17:02.00 | dream_kill | i found it then in the spl |
17:02.13 | dream_kill | u can manual define the partition table in the driver |
17:02.17 | dream_kill | i done it too |
17:02.31 | cr2 | maejrep[w]: do the commands work for you ? |
17:02.31 | dream_kill | all u need is the offsets, size, name |
17:02.44 | cr2 | dream_kill: yes. |
17:02.56 | dream_kill | why i asked about raphael, is that for g1 i managed to patch the oemsbl and removed the MPU protection :D |
17:03.21 | dream_kill | so i'm going to patch the raphael now to remove the MPU protection |
17:03.40 | dream_kill | then we can write the full image from g1 into it :D |
17:03.59 | AstainHellbring | dream_kill there is already a spl for that |
17:04.10 | cr2 | dream_kill: full image does not make sense |
17:04.16 | dream_kill | for writing FULL image? |
17:04.30 | dream_kill | is for writing ONLY partitons allowed :D |
17:04.43 | cr2 | dream_kill: but if the g1 amss may be installed on raph (and will work), that will be fun |
17:04.50 | dream_kill | yes |
17:04.55 | dream_kill | this is THE idea |
17:05.07 | cr2 | ok |
17:05.07 | dream_kill | anyone with a raphael in waranty still ? |
17:05.17 | lupine_85 | moi... |
17:05.20 | dream_kill | i can send him to test a radio from dream |
17:05.35 | dream_kill | i made the .nbh file already |
17:05.40 | dream_kill | so we can test to flash it |
17:05.46 | dream_kill | just the radio |
17:05.49 | AstainHellbring | you will need a sec unlocked device to flash radio |
17:05.55 | dream_kill | since we seems all msm7201a are interchangeble |
17:05.59 | dream_kill | yes |
17:06.10 | cr2 | dream_kill: but i guess that the radio must be signed |
17:06.27 | AstainHellbring | what will dream radio give that other radios wouldn't? |
17:06.29 | dream_kill | IS singed |
17:06.38 | cr2 | ok |
17:06.51 | dream_kill | it should map correctly the GPIO's for linux :D |
17:06.54 | AstainHellbring | dream_kill send me radio |
17:07.12 | dream_kill | urs is security unlocked? |
17:07.15 | cr2 | AstainHellbring: we will get rid of the vreg/clk pita |
17:07.27 | cr2 | dream_kill: map the gpios ??? |
17:07.56 | cr2 | dream_kill: but are you sure that the arm9 gpios are the same on both ? |
17:07.57 | dream_kill | did u checked the oemsbl as i told u ? |
17:08.03 | dream_kill | yes 100% |
17:08.59 | cr2 | i eman the arm9 gpio usage. i have no idea about the purpose of the arm9 gpios |
17:11.06 | dream_kill | ok uploading radio to rapidshare |
17:11.41 | dream_kill | inside still have references to raphael, diamond, nike.... |
17:12.48 | dream_kill | http://rapidshare.com/files/184399875/flash_to_g1.rar.html |
17:12.55 | dream_kill | flash this ONLY if security unlock |
17:13.01 | dream_kill | and ONLY if u still have warranty |
17:13.12 | dream_kill | as it might send your device to sleep :D |
17:14.00 | dream_kill | anyone brave? |
17:23.22 | dream_kill | ? |
17:24.12 | XD | o-o |
17:29.37 | *** join/#htc-linux AstainZZZZZZ (n=AstainHe@unaffiliated/astainhellbring) |
17:34.19 | dream_kill | no one :P ? |
17:35.52 | AstainHellbring | huh dream_kill? |
17:36.17 | dream_kill | http://rapidshare.com/files/184399875/flash_to_g1.rar.html |
17:36.21 | dream_kill | flash this ONLY if security unlock |
17:36.26 | dream_kill | and ONLY if u still have warranty |
17:36.29 | dream_kill | as it might send your device to sleep :D |
17:36.33 | dream_kill | anyone brave? |
17:36.35 | dream_kill | :P |
17:36.52 | AstainHellbring | I brave enough to give it to cmonex and see if she says it should be safe to flash |
17:43.31 | *** join/#htc-linux zycho (n=zycho@a89-183-78-110.net-htp.de) |
17:45.53 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
17:48.34 | dcordes | yo |
17:49.23 | lupine_85 | hi dcordes |
17:49.50 | dcordes | man I just looked at the raph |
17:50.01 | dcordes | didn't see it before. the keyboard is awesome |
17:50.13 | lupine_85 | not working for me on raph100 yet |
17:50.43 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
17:51.10 | dcordes | lupine_85: do you need to change tslib configuration or code to use raph ts in angstrom? |
17:51.23 | lupine_85 | dcordes: only slightly |
17:51.29 | dcordes | what do you change? |
17:51.30 | lupine_85 | it expects /dev/input/touchscreen0 |
17:51.36 | lupine_85 | (it should be /dev/input/event0) |
17:51.48 | lupine_85 | that's set in /etc/profile.d/ts.conf IIRC |
17:51.56 | dcordes | doesn't OE do a symlink? |
17:51.58 | lupine_85 | or you can symlink fix |
17:52.02 | lupine_85 | not by default AFAIK |
17:52.07 | lupine_85 | I added one |
17:52.28 | dcordes | might be the better way. let's add this to the image install |
17:52.41 | dcordes | so you get a fully working image when building for raph |
17:52.51 | dcordes | we can also add the frameworkd config |
17:53.05 | dcordes | did you do further tests with franeworkd-devel? |
17:53.50 | lupine_85 | mm, it screwed up the screen calibration somehow |
17:53.59 | lupine_85 | not sure how that worked |
17:57.36 | dcordes | it is the driver-side calibration? |
17:57.53 | *** join/#htc-linux TheOther (n=nahh@108.84-49-166.nextgentel.com) |
17:58.24 | lupine_85 | I think frameworkd changed the X server to read from the wrong device |
17:58.52 | lupine_85 | since the lack of calibration problem was similar to when it was reading from the device as ps/2 |
17:58.56 | lupine_85 | anyway, must go to salsa |
18:00.41 | *** join/#htc-linux TheOther (n=nahh@108.84-49-166.nextgentel.com) |
18:05.59 | dcordes | lupine_85: have fun |
18:06.27 | AstainHellbring | anyone know if linux support for HID devices has gotten any better in the past little while? |
18:07.56 | maejrep[w] | I haven't had any problems with HID |
18:08.19 | AstainHellbring | do you have to reconnect the device upon reboot or? |
18:08.32 | AstainHellbring | been a while since I used BT and a mouse/keyboard on linux |
18:10.50 | *** join/#htc-linux exco (n=exco@e181083211.adsl.alicedsl.de) |
18:12.21 | maejrep[w] | no, I don't |
18:12.51 | maejrep[w] | if I switch my HID device to HCI mode (done during bootup automatically), it just works |
18:13.54 | AstainHellbring | hci? |
18:14.05 | maejrep[w] | bluetooth |
18:14.23 | maejrep[w] | there's a bluez util called hid2hci |
18:14.28 | AstainHellbring | hmm cool maybe I will try kubuntu again |
18:14.48 | maejrep[w] | for devices that provide both modes (like my logitech bluetooth combo dongle) |
18:15.04 | maejrep[w] | if I don't want to mess with bluetooth, I can leave it in HID mode, and not worry about pairing, etc |
18:15.07 | AstainHellbring | ahh nice which logitech set you have? |
18:15.18 | maejrep[w] | MX5000 I think |
18:15.20 | maejrep[w] | something like that |
18:15.44 | AstainHellbring | nice I has mx5500 |
18:15.53 | maejrep[w] | maybe that's what it is..? |
18:16.07 | maejrep[w] | does it have the LCD at the top that has like temperature, calculator, etc? |
18:16.21 | maejrep[w] | and notify about new emails (if you have the software installed) |
18:16.26 | AstainHellbring | yes but both have that |
18:16.31 | maejrep[w] | oh |
18:16.52 | AstainHellbring | 5500 doesnt have the page up/down button but has scroll wheel on thumb |
18:16.54 | maejrep[w] | i know my mouse at home doesn't work with revoco to set the scroll wheel mode |
18:17.20 | maejrep[w] | yeah mine has the side wheel plus back/forward, wheel tilt, free spin wheel mode, etc |
18:17.37 | maejrep[w] | i have the same mouse at work, minus bluetooth, and revoco works with it |
18:17.52 | maejrep[w] | so I can set the wheel into free spin mode, and get access to my middle click again |
18:18.09 | maejrep[w] | but at home clicking the wheel just changes the wheel spin mode |
18:18.44 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
18:18.51 | AstainHellbring | if you connect it to a windows box and set the mode with set point it should keep the mode after change back |
18:23.27 | maejrep[w] | yeah it does, but it eventually loses it |
18:23.36 | maejrep[w] | it works from virtualbox or vmware as well |
18:23.41 | AstainHellbring | wierd |
18:24.07 | maejrep[w] | like when i put it on the charger or something like that |
18:24.32 | AstainHellbring | hmm I having issues with mine where I can't get windows 7 to connect to it via the onboard bluetooth in my lappy |
18:25.13 | *** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
18:26.13 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
18:31.40 | *** join/#htc-linux frysee (i=4d14b78a@gateway/web/ajax/mibbit.com/x-fcdcae8a7ecb6d0c) |
18:33.03 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
18:35.38 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
18:39.18 | AstainHellbring | dream_kill get anyone to flash that radio yet? |
18:42.15 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
18:44.06 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87dfb5.pool.einsundeins.de) |
18:44.23 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
18:54.22 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
18:55.12 | *** join/#htc-linux TheOther (n=nahh@108.84-49-166.nextgentel.com) |
18:57.16 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
19:02.41 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
19:09.25 | *** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
19:10.31 | NetRipper | AstainHellbring, you contacted cmonex yet? :) |
19:12.31 | *** join/#htc-linux Tintammare (n=Administ@set25-1-88-166-169-49.fbx.proxad.net) |
19:13.19 | *** join/#htc-linux Mgaveve (n=king@41.208.50.180) |
19:14.15 | *** join/#htc-linux hollo (n=hollo@3e6b025d.rev.stofanet.dk) |
19:26.14 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
19:27.13 | Tintammare | hi |
19:30.41 | *** part/#htc-linux Tintammare (n=Administ@set25-1-88-166-169-49.fbx.proxad.net) |
19:37.23 | *** join/#htc-linux NeoS20074 (n=neos2007@85.149.240.24) |
19:38.00 | NeoS20074 | hey guys |
19:40.57 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
19:41.15 | *** join/#htc-linux BHSPitLappy_ (n=BHSPitLa@ppp-70-243-200-223.dsl.rcsntx.swbell.net) |
19:47.01 | *** join/#htc-linux exco (n=exco@e181126244.adsl.alicedsl.de) |
19:48.51 | NeoS20074 | anyone got android booting on HD? |
19:50.04 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
19:51.50 | AstainHellbring | NetRipper tried nothing back yet |
19:53.39 | *** part/#htc-linux exco (n=exco@e181126244.adsl.alicedsl.de) |
19:57.32 | *** join/#htc-linux pichurri (n=pichurri@194.230.146.86) |
20:00.48 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
20:04.32 | NeoS20074 | Haret shows the loading bar but after that's full it hangs my device. i guess that's what everyone's having? |
20:11.19 | *** join/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
20:19.20 | *** join/#htc-linux Mullins (n=bw@89.204.245.91) |
20:20.17 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-3-82.web.vodafone.de) |
20:22.33 | cr2 | NetRipper: have you seen my comment about MSM_SDIO ? |
20:22.41 | cr2 | kiozen: already sleeping ? |
20:25.36 | cr2 | maejrep[w]: raph800 has "mpp" |
20:26.07 | maejrep[w] | what is mpp |
20:26.07 | cr2 | and 6 lcd configs |
20:26.08 | cr2 | no idea |
20:26.13 | maejrep[w] | :D |
20:26.20 | cr2 | some power IC like pmic |
20:26.26 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-baa2757073099e5f) |
20:26.58 | cr2 | i have found my old dumped wince dmesg |
20:27.47 | cr2 | raph500 is raph800 ? |
20:28.21 | AstainHellbring | no cr2 |
20:28.28 | AstainHellbring | raph500 is verizon raphael |
20:28.35 | AstainHellbring | raph 800 is other carriers rapherl |
20:28.52 | cr2 | are there any hardware differences ? |
20:28.57 | AstainHellbring | yes |
20:29.00 | rolk | Hi. Noticed several commits in the htc-vogue branch of ltg-git. It seems that there has been some additional progress on the SD card for Kaiser. I'm a bit confused: it seems vogue_defconfig is now actually a default kaiser config? |
20:29.01 | AstainHellbring | proc and mem |
20:29.09 | cr2 | i see raph500000 id for raph800 spl |
20:29.46 | cr2 | rolk: the sd setup should be the same |
20:29.49 | maejrep[w] | what? |
20:29.56 | maejrep[w] | in my spl dump it's "RAPH80000" |
20:30.07 | maejrep[w] | (4 0's, but its an 8, not a 5) |
20:30.30 | cr2 | rolk: even on 7201A it will be the same |
20:30.31 | *** join/#htc-linux NeoS20070 (n=neos2007@82-136-223-208.ip.telfort.nl) |
20:30.42 | cr2 | maejrep[w]: somebody dumped me this spl |
20:30.55 | cr2 | maejrep[w]: it also calls itself Raphael_C |
20:31.03 | cr2 | C is for CDMA probably |
20:31.30 | cr2 | smi size 32 or 64 |
20:31.37 | cr2 | hmm |
20:31.46 | AstainHellbring | 64 is the verizon TP 32 is sprint TP |
20:31.46 | rolk | cr2: I noticed the vogue_defconfig now both has CONFIG_MACH_HTCVOGUE and CONFIG_MACH_HTCKAISER set. That's odd, so when I build for kaiser, do I need to manually disable CONFIG_MACH_HTCVOGUE? |
20:32.19 | Mullins | rolk: no, leave as is for kaiser |
20:32.37 | Mullins | rolk: will add a kaiser_defconfig in a short while |
20:32.56 | cr2 | rolk: it's probably an unfortunate Kconfig |
20:33.05 | maejrep[w] | yes I have Raphael_C as well |
20:33.13 | maejrep[w] | cr2: I was the one who dumped raph800 spl for you |
20:33.23 | cr2 | hmm |
20:33.26 | maejrep[w] | so I don't know why you would see "raph50000" |
20:33.28 | rolk | Ok. What about polaris (I have a polaris actually). Does the current build with vogue_defconfig boot on Polaris? |
20:33.33 | maejrep[w] | I know for sure that I saw "raph80000" |
20:33.44 | maejrep[w] | it stood out because of the 2 extra 0's |
20:33.46 | cr2 | maejrep[w]: i'll check the 500 too |
20:33.58 | maejrep[w] | i think raph500 does show raph50000 |
20:34.08 | maejrep[w] | I don't know why 800 would show 50000 though :x |
20:34.23 | cr2 | hmm. |
20:34.32 | rolk | cr2: well, there are things that are probably now using CONFIG_MACH_HTCVOGUE that will be needed as well for a Kaiser/Polaris. |
20:34.44 | cr2 | raph100 uses c4,0,9 for psoc id |
20:35.07 | rolk | But also stuff that is really vogue specific, and not usable for kaiser/polaris and such. |
20:35.13 | cr2 | and this raph500000 has c4,f,3,x |
20:35.29 | maejrep[w] | 00001000 0a 00 00 ea 30 2e 33 37 2e 30 30 30 30 00 00 00 |....0.37.0000...| |
20:35.30 | maejrep[w] | 00001010 52 61 70 68 61 65 6c 5f 43 00 00 00 00 00 00 00 |Raphael_C.......| |
20:35.30 | maejrep[w] | 00001020 53 68 69 70 70 65 64 00 00 00 00 00 00 00 00 00 |Shipped.........| |
20:35.48 | cr2 | rolk: it's not the cleanest kernel tree ;) |
20:36.02 | cr2 | maejrep[w]: yes |
20:36.03 | rolk | You'd expect a Kconfig flag that represents the common denominator for Kaiser/Polaris/Vogue (probably all msm7200). Is that an idea to add? |
20:36.09 | maejrep[w] | 00081050 ff ff ff ff ff ff ff ff 00 00 00 00 54 53 45 52 |............TSER| |
20:36.09 | maejrep[w] | 00081060 55 aa aa 55 85 98 89 58 52 00 41 00 50 00 48 00 |U..U...XR.A.P.H.| |
20:36.09 | maejrep[w] | 00081070 38 00 30 00 30 00 30 00 30 00 00 00 ff ff ff ff |8.0.0.0.0.......| |
20:36.26 | maejrep[w] | rolk: I agree with that |
20:36.31 | cr2 | rolk: it's better to do the machines mutually exclusive |
20:37.04 | maejrep[w] | cr2: but something like "MSM_750x_SMD" for example, which implements smd the vogue-smd way |
20:37.33 | Mullins | rolk: at the moment, Dzo is still finding out what is common to both Kaiser and Vogue and also plans to include Polaris, so eventually it will be tidy |
20:38.03 | cr2 | maejrep[w]: it knows about PSOC-Diam |
20:38.22 | maejrep[w] | <PROTECTED> |
20:38.22 | maejrep[w] | PSOC-Diam STAGE_EVT v%x |
20:38.22 | maejrep[w] | PSOC-Diam STAGE_DVT v%x |
20:38.22 | maejrep[w] | PSOC-Diam STAGE_CVT v%x |
20:38.22 | maejrep[w] | PSOC-Diam STAGE_PVT v%x |
20:39.12 | cr2 | yes |
20:39.48 | rolk | Mullins: I know. Good stuff is happening. I'm just trying to find out how you all feel this should be set up. In any case, I think there will be plenty of shared stuff for all msm7200 based machines (irq handling, ...) which is different from the msm7201 stuff. And also specific stuff. |
20:39.48 | maejrep[w] | 00011560 25 78 0a 00 42 4f 4f 54 20 6d 6f 64 65 20 3d 20 |%x..BOOT mode = | |
20:39.48 | maejrep[w] | 00011570 25 64 0a 00 52 00 41 00 50 00 48 00 35 00 30 00 |%d..R.A.P.H.5.0.| |
20:39.48 | maejrep[w] | 00011580 30 00 30 00 30 00 00 00 49 6e 69 74 20 54 6f 70 |0.0.0...Init Top| |
20:39.48 | maejrep[w] | :O |
20:39.48 | maejrep[w] | there's a 50000 |
20:40.00 | cr2 | maejrep[w]: i guess they are very close |
20:40.18 | maejrep[w] | except 500 has much less ram, which means the smem map would probably be very different, right? |
20:40.26 | cr2 | maejrep[w]: but cdma vs. umts is rather different |
20:40.33 | cr2 | no. |
20:40.41 | rolk | If it ever is to get integrated with the other branches, to get a unified HTC branch in ltg-git, it would be good to think about how this is to be setup properly. |
20:40.50 | cr2 | smem is always the 31th SMI megabyte |
20:41.03 | cr2 | on all msm phones |
20:41.39 | cr2 | rolk: then it's necessary to write clean, portable drivers |
20:41.57 | cr2 | rolk: and not hardcoding random gpios and irqs :) |
20:42.06 | cr2 | like g1 ;) |
20:43.08 | rolk | cr2: I know, first get everything up and running, then make it beautiful. But I might be able to help out a bit in restructuring the code base, if there is a consensus on how to move forward in that area. |
20:44.45 | *** join/#htc-linux timebomb (n=tb@e176100046.adsl.alicedsl.de) |
20:45.17 | NetRipper | maejrep[w], people using the security unlock and having i.e. a blackstone radio in their raphael's will show up as blackstone, right? :) |
20:46.08 | cr2 | rolk: the clean htc-egpio driver implemented for an msm phone will be very helpful for everybody. |
20:46.24 | cr2 | rolk: even for g1 ;) |
20:46.35 | maejrep[w] | NetRipper: I would guess that to be correct ? :x |
20:46.43 | cr2 | NetRipper: no |
20:46.51 | maejrep[w] | are you saying I've flashed a raph500 radio onto my raph800? :) |
20:47.02 | cr2 | NetRipper: haret is a wince program, which picks this data from the wince kernel |
20:47.46 | cr2 | maejrep[w]: my "500" and "800" spls are different |
20:47.58 | cr2 | at least by the compilation date |
20:49.01 | NetRipper | cr2, but how does wince know it's a raphael.. it uses the radio to determine that, doesn't it? |
20:49.33 | NetRipper | and radio = arm9 part, so that controls what is written in smem |
20:49.42 | cr2 | maejrep[w]: strings -el shows 1 RAPH500000 and 2 RAPH800000 strings |
20:49.49 | rolk | OK. A clean build of ltg-git (htc-vogue branch), latest state, does not boot on polaris. I get a kernel panic. |
20:49.52 | cr2 | maejrep[w]: cut'n' paste again ? |
20:50.15 | cr2 | rolk: you have a different cpld address ? |
20:50.48 | cr2 | NetRipper: i also see another problem |
20:51.23 | cr2 | NetRipper: some gpios belong to arm9, and we don't know their function. i'm not 100% sure that these are the same everywhere, and have the same function |
20:51.41 | NetRipper | hm |
20:51.52 | cr2 | NetRipper: you see how big are the differences for the arm11 gpios |
20:52.08 | NetRipper | among the raph/diam/blackstone/xperia series the arm9 gpios are probably the same, as the radio's are interexchangeable |
20:52.38 | cr2 | ok |
20:52.48 | rolk | cr2: cpld? |
20:53.22 | cr2 | but it should not be the same for g1 |
20:53.42 | cr2 | rolk: the gpio extender |
20:54.09 | maejrep[w] | cr2: lol that'd be funny |
20:54.22 | maejrep[w] | and yes I saw the 50000 and the two 80000's as well |
20:54.30 | NetRipper | cr2, regarding the SDIO.. i thought there were 2 sdio's.. SDIO1 and SDIO2 (as written in wiki)... and each SDIO has 2 "slots".. thus the SDC1_0, SDC1_1 and SDC2_0, SDC2_1 |
20:54.35 | *** join/#htc-linux Xime (n=xime@bankize.net) |
20:54.43 | cr2 | NetRipper: on 7200 |
20:55.04 | cr2 | NetRipper: 7201A has SDC3_x and SDC4_x |
20:55.16 | cr2 | NetRipper: check Raphael_IRQ page |
20:55.25 | NetRipper | cr2, i see |
20:55.40 | NetRipper | i could swear it wasn't on memorymap wiki page a month ago |
20:55.41 | NetRipper | :P |
20:55.47 | cr2 | and the _1 are not supported |
20:55.47 | maejrep[w] | it was :P |
20:56.03 | cr2 | let swetland correct me if i'm wrong |
20:56.06 | maejrep[w] | its just not adjacent to the sdc1 and sdc2 areas, so its easy to lose them |
20:56.08 | rolk | cr2: The topmost line of the kernel log that I still can see is 'vogue_sdcc_slot_status'. Its being called in the context of 'msmsdcc_init'. This is in the kernel-panic trace. |
20:56.51 | NetRipper | 0xa04/5/6/7 seem adjacent to me |
20:57.17 | cr2 | rolk: well, that should not happen |
20:57.34 | cr2 | NetRipper: 7200 uses a03 and a04 |
20:57.49 | NetRipper | cr2, ok |
20:57.49 | cr2 | so it's a bit confusing |
20:58.05 | cr2 | because 7200 has only one uartDM, afair |
20:58.36 | NetRipper | ok so in that case |
20:58.40 | NetRipper | just my naming scheme is wrong |
20:59.09 | cr2 | NetRipper: i think that sdcc1 is SDC1_0 , sdcc2 is SDC2_0, ... |
20:59.17 | cr2 | but it's my guess :) |
20:59.48 | cr2 | you can verify it with 0xa0X area and the a0/a4, a8/ac, b0/b4 and b8/bc clocks |
21:00.12 | cr2 | and the ARM11_CLK_CTL(0) register |
21:00.19 | cr2 | bitmasks |
21:00.20 | NetRipper | cr2, well i can see it in the msm_iomap.h... SDC1/2/3/4 are mapped on the addresses are specified in wiki |
21:00.25 | NetRipper | and we're using SDC2 currently for raph |
21:00.27 | NetRipper | 100 |
21:00.31 | NetRipper | and SDC3 for cdma |
21:00.44 | rolk | cr2: The vogue_defconfig is setting both CONFIG_MACH_HTCVOGUE and CONFIG_MACH_HTCKAISER, the makefile then includes both board-htcvogue.c AND board-htckaiser.c !? |
21:00.45 | cr2 | NetRipper: what about g1 ? |
21:00.51 | NetRipper | cr2, g1 uses SDC1 |
21:00.58 | NetRipper | er |
21:01.00 | NetRipper | actually |
21:01.02 | NetRipper | let me verify that |
21:01.09 | cr2 | rolk: i have not written that code :) |
21:01.22 | rolk | I have no idea why this passes the link stage; you would bet that there are some duplicated symbols? |
21:01.27 | cr2 | NetRipper: don't forget the wifi |
21:01.50 | NetRipper | cr2, g1 uses SDC2 as well |
21:01.50 | cr2 | rolk: it seems that is not the case |
21:02.04 | NetRipper | same as raph100 |
21:02.04 | cr2 | NetRipper: add g1 to the list |
21:02.17 | cr2 | NetRipper: and wifi on SDC1 ? |
21:02.33 | NetRipper | need to check |
21:03.01 | cr2 | NetRipper: i want to document g1 in the wiki |
21:03.10 | cr2 | in the same way as other phones |
21:03.10 | NetRipper | hm |
21:03.19 | NetRipper | ah yes, wifi on 1 |
21:03.22 | cr2 | imho, it's very useful for fixing bugs |
21:03.24 | AstainHellbring | hehe I should have an eee to play with come tuesdayish |
21:04.01 | NetRipper | msm_add_sdcc(1, &trout_wifi_data); |
21:04.04 | NetRipper | <PROTECTED> |
21:04.14 | *** join/#htc-linux mrincredible (n=mincredi@70-0-118-17.pools.spcsdns.net) |
21:04.20 | cr2 | NetRipper: ok. |
21:04.27 | NetRipper | updated wiki |
21:04.35 | cr2 | NetRipper: and the 0xa4/a8 is the SDC1 ? |
21:04.49 | NetRipper | how do i verify that? |
21:05.02 | NetRipper | im not familiar with the clocks |
21:05.15 | cr2 | ok, doesn't matter now. |
21:05.26 | cr2 | g1 gpios... |
21:05.30 | cr2 | first. |
21:05.37 | cr2 | and raph800 gpios |
21:06.09 | cr2 | lupine_85: does the kbd driver work for you ? |
21:06.50 | cr2 | NetRipper: back to TSSC. why don't you declare the irq with raising edge ? |
21:07.23 | NetRipper | i think i tried MASK.. which is all |
21:07.24 | cr2 | NetRipper: there are 4 irq config options in wince, but i don't know yet which one is what. |
21:07.35 | NetRipper | on/off/rising/falling |
21:07.44 | drasar | cr2: did you try to apply my hima patch? |
21:08.03 | cr2 | NetRipper: which IRQF_ flags are available |
21:08.09 | NetRipper | cr2, sec |
21:08.25 | cr2 | drasar: no, i need to checkout the hh tree to some external machine first. |
21:08.37 | NetRipper | cr2, http://netripper.pastebin.com/m25c80267 |
21:09.02 | drasar | cr2: ok |
21:09.24 | cr2 | NetRipper: strange |
21:09.26 | NetRipper | cr2, i think i tried IRQF_TRIGGER_MASK before |
21:10.24 | *** part/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
21:10.41 | cr2 | NetRipper: try IRQF_TRIGGER_RISING |
21:10.44 | NetRipper | When requesting an interrupt without specifying a IRQF_TRIGGER, the setting should be assumed to be "as already configured", which may be as per machine or firmware initialisation. |
21:11.00 | NetRipper | ok will try |
21:11.03 | NetRipper | but a little bit later |
21:11.06 | cr2 | ok |
21:12.02 | cr2 | NetRipper: and i think it should be a platform_device, because it's a builtin msm function |
21:13.23 | NetRipper | ok |
21:14.13 | NetRipper | i'll try doing that as well |
21:15.37 | cr2 | blackstone has 2 lcds |
21:15.45 | cr2 | toppoly and sharp |
21:17.36 | cr2 | microp-blackstone (LED) |
21:18.18 | cr2 | any bstone people around ? |
21:20.15 | pichurri | cr2, yes? |
21:21.13 | cr2 | pichurri: can you start the blackstone_gpio page, like we have raphael_gpio ? |
21:21.46 | cr2 | remove the descriptions, and the alt values, but keep the numbers,banks, and such |
21:22.14 | cr2 | then i'll just fill the missing data. |
21:22.25 | pichurri | cr2, ok, but can't do it now, sorry... |
21:22.43 | cr2 | gpio 0x62 and 0x63 are lcd power for example |
21:22.43 | pichurri | cr2, tomorrow or sunday I will, :) |
21:23.07 | cr2 | and 0x1f |
21:23.10 | cr2 | ok |
21:23.25 | pichurri | cr2, I think its pretty much the same thing as raph, but different panel/screen... |
21:23.46 | pichurri | cr2, mmc its the same, android 1.0 boots but with bad output... |
21:23.47 | cr2 | vreg(a,1,a28) and (4,1,b22) |
21:24.04 | cr2 | same as what ? rapahel ? |
21:24.25 | cr2 | raph100 ? |
21:24.32 | pichurri | cr2, I mean in from hw point of view... |
21:24.36 | pichurri | yes raph100 |
21:24.37 | pichurri | no? |
21:24.40 | cr2 | ok |
21:24.51 | cr2 | yes, looks very similar |
21:25.27 | pichurri | cr2, :), |
21:25.33 | pichurri | night! cya |
21:26.29 | cr2 | gpio 0x59 is microP reset |
21:30.50 | cr2 | bt-> x13,2,10,0 ; x14,1,10,0 ; x15,1,10,0 ; x6c,2,8,1 |
21:31.08 | cr2 | uart2 |
21:31.52 | cr2 | x67 is bt power |
21:31.57 | cr2 | x65 bt reset |
21:32.07 | cr2 | 0x32 msleep |
21:36.02 | cr2 | NetRipper: what about kaiser/vogue/titan/polaris in SDIO ? |
21:39.45 | NetRipper | err i dont know, you want to add all of them? |
21:40.05 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
21:40.25 | NetRipper | guess i should flip the table ;) |
21:40.39 | cr2 | yes. just put - for SDC3 and SDC4 |
21:40.40 | cr2 | ok |
21:40.48 | NetRipper | anyway i dont know about kaiser and the others |
21:40.58 | cr2 | dcordes: ? |
21:41.08 | NetRipper | do all of them have models like raph* as well? :) |
21:41.08 | cr2 | haha |
21:41.15 | NetRipper | lol, he saw it coming |
21:41.18 | NetRipper | and ran |
21:41.34 | cr2 | hey, any 7x00 people around ? |
21:41.40 | cr2 | NetRipper: check the haret source |
21:43.19 | NetRipper | there's something about CKEN |
21:43.22 | NetRipper | no idea what it is |
21:43.36 | NetRipper | but it lists SDC1-4 |
21:43.48 | NetRipper | cken = clock enable? |
21:44.08 | cr2 | yes |
21:44.20 | cr2 | but i think it's wrong |
21:44.30 | cr2 | to call it clock enable |
21:44.36 | NetRipper | well |
21:44.51 | NetRipper | it should be clk :P makes it easier ;) |
21:44.53 | cr2 | because i2c and mddi do not have such bits |
21:45.14 | cr2 | so it can't be "enable" |
21:46.03 | maejrep[w] | cr2: the CKEN patch came from your suggestion to look at pxa ;) |
21:46.18 | cr2 | NetRipper: the machtypes.cpp or something like that |
21:46.47 | cr2 | NetRipper: in wince/ dir |
21:46.54 | NetRipper | nothing special in machlist |
21:47.00 | cr2 | maejrep[w]: yes, i'm making mistakes too :) |
21:47.10 | *** join/#htc-linux AstainHellbring (n=AstainHe@c-67-164-195-234.hsd1.ut.comcast.net) |
21:47.15 | AstainHellbring | hi again |
21:47.26 | imfloflo | hey guys i have polaris if i can help |
21:47.27 | cr2 | AstainHellbring: do you have a 7x00 device ? |
21:47.40 | AstainHellbring | yes |
21:47.44 | cr2 | imfloflo: what is your dev name ? |
21:47.47 | imfloflo | have you see this video http://www.youtube.com/watch?v=jl0LSHbUbzE debian and android on the same |
21:47.52 | imfloflo | POLA100 |
21:48.04 | cr2 | NetRipper: i have kaiser spl, i can check |
21:48.32 | cr2 | KAIS100 i think |
21:48.32 | NetRipper | imfloflo, do you know which other POLA there are? |
21:48.33 | AstainHellbring | cr2 I have kaiser titan raph800 and raph100 |
21:48.41 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
21:48.46 | cr2 | AstainHellbring: KAIS100 ? what about titan ? |
21:49.28 | imfloflo | I though there is a list on xda wiki |
21:49.30 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
21:50.03 | imfloflo | 100 & 200 |
21:50.05 | NetRipper | imfloflo, ok |
21:50.16 | rolk | Hmm...I goofed. It seems the latest build from ltg-git, branch htc-vogue does boot on Polaris, but I need to change the machine type in haret. Keys do not work as I would expect in Android. |
21:51.34 | AstainHellbring | cr2: kaiser is the att tilt modEL KAIS110 i think and titan is the sprint versioffffn |
21:51.55 | cr2 | ok |
21:52.10 | cr2 | btw, what is the blackstone id ? |
21:52.53 | AstainHellbring | I also access to a DIAM800 and soon a vogue too |
21:53.17 | cr2 | BLAC100 |
21:53.50 | NeoS20070 | me 2 |
21:54.35 | AstainHellbring | why you ask cr2? |
21:55.34 | cr2 | to use in wiki |
21:55.54 | NetRipper | http://wiki.xda-developers.com/index.php?pagename=MSM_SDIO |
21:56.47 | maejrep[w] | cr2: are you sure its not cken though? haret does show it being enabled/disabled when expected |
21:56.50 | maejrep[w] | what else would it be |
21:57.51 | NetRipper | its cken for a few devices, but not general to all devices |
21:58.21 | NetRipper | i think that's what cr2 means at least;) |
21:58.25 | cr2 | NetRipper: updated |
21:58.43 | cr2 | NetRipper: yes. |
21:58.45 | NetRipper | ok |
21:58.57 | cr2 | maejrep[w]: i2c does not have such bit, for example |
21:59.36 | cr2 | NetRipper: it's cken related for some subsystems, but not the cken itself |
21:59.44 | maejrep[w] | but i2c has its own clk_ctl register |
22:00.03 | cr2 | it's the divisor setting |
22:00.10 | cr2 | i2c has a divisor setting too |
22:00.15 | maejrep[w] | hmm |
22:00.25 | cr2 | and they are even similar to some extent |
22:00.26 | maejrep[w] | would i2c's clock be the SCL line? |
22:00.40 | cr2 | not really |
22:00.56 | cr2 | it's the clock generatror frequency behind it. |
22:01.55 | cr2 | maejrep[w]: where is wifi on raph800 ? |
22:02.07 | cr2 | SDC port ? |
22:02.35 | maejrep[w] | yes |
22:02.45 | maejrep[w] | i think sdc2, but don't quote me on that |
22:02.56 | *** join/#htc-linux Xime (n=xime@bankize.net) |
22:03.05 | cr2 | ok |
22:03.24 | cr2 | i'll look at it after blac100 |
22:15.33 | *** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net) |
22:17.12 | *** join/#htc-linux kaze_ (n=kaze@ABordeaux-158-1-27-51.w90-55.abo.wanadoo.fr) |
22:27.31 | rolk | Interesting. I'm booting the 'kaiser+vogue' defconfig, with minor changes to the Makefile in arch/arm/mach-msm and in board-htckaiser.c. I got rid of the interrupts caused by the kaiser keypad implementation (that is out of place in a polaris), and it boots fine. Keys seem to work ok now but the touchscreen is erratic and the phone switches to a black screen after a few minutes and does not wake up. |
22:30.21 | AstainHellbring | maejrep[w] can you tell me how to setup BT on kubuntu I can't seem to get it to do it right? |
22:32.11 | Mullins | rolk: Do you use tsc2003.c with Polaris too? |
22:36.09 | rolk | Mullins: I was just checking the differences in board-htcpolaris.c and board-htckaiser.c... |
22:36.24 | rolk | Concerning touchscreen interface.... |
22:36.55 | rolk | The one that previously worked for me has '.type = "voguets"' |
22:37.02 | Mullins | rolk: ah ok |
22:37.26 | rolk | While the board-htckaiser.c has '.type = "vtsc2003-ts"' |
22:37.35 | rolk | Is wrong, no? |
22:38.14 | Mullins | rolk: Kaiser doesn't use that anyway. it uses tsc2003.c although I noticed that device, it doesn't use it |
22:38.16 | rolk | Actually, I have no clue whether this .type field actually matters at all. |
22:38.29 | Mullins | rolk: I think you are right. It doesn't matter |
22:38.48 | cr2 | rolk: can you compile the tiacx ? |
22:39.00 | Mullins | dzo: Are you there? |
22:40.09 | cr2 | maejrep[w]: seems like SDC1 to me |
22:40.22 | rolk | cr2: Hum. I can, if you tell me what it is... :) |
22:40.42 | cr2 | maejrep[w]: returns controller=0 |
22:40.47 | rolk | Mullins: I'll check the kernel config. |
22:40.58 | cr2 | maejrep[w]: and controller=2 for sd |
22:41.27 | cr2 | rolk: the wifi driver from source.android git |
22:41.52 | cr2 | it's a shame that we still don't have wifi running :) |
22:42.34 | rolk | cr2: is that in the android-git kernel? |
22:43.44 | NetRipper | cr2, you made me cry |
22:43.54 | NetRipper | cr2, the touchscreen irq is firing |
22:44.06 | cr2 | rolk: http://android.git.kernel.org/?p=platform/system/wlan/ti.git |
22:44.15 | cr2 | NetRipper: lol |
22:44.34 | NetRipper | both 30 (press) and 31 (release) |
22:44.47 | cr2 | NetRipper: now you owe me remiving the weird calibration stuff from the driver. |
22:45.02 | cr2 | s/miv/mov/ |
22:45.47 | NetRipper | cr2, we'll lose the current virtual keyboard if we start using the minimal ts driver |
22:46.07 | cr2 | NetRipper: and before reading the data register , you'd check the 0x800 bit set. at least wince does it so. |
22:47.08 | cr2 | NetRipper: we have the real keybaord now ? anyway, you can make it an option. it's maybe important for the diam/blac people |
22:47.39 | NetRipper | yes especially for diam/blac people using shell and the sort |
22:48.01 | cr2 | ok |
22:48.16 | NetRipper | but i agree we should have a cleaner implementation |
22:48.27 | cr2 | yes. |
22:48.47 | NetRipper | i.e. vkeyb may be a hack.. but ts driver should not depend on msmfb nor should msmfb refer to ts driver |
22:48.50 | cr2 | NetRipper: what>'s next ? tiacx ? :) |
22:50.13 | NetRipper | dont know how hard it is to try |
22:50.52 | NetRipper | where do i find tiacx? |
22:52.27 | *** join/#htc-linux frysee (i=4d14b78a@gateway/web/ajax/mibbit.com/x-f0777cfcb626e86b) |
22:52.46 | cr2 | <PROTECTED> |
22:53.06 | cr2 | it's not easy to compile afaik |
22:53.28 | cr2 | but then we will only need some minor xhanges |
22:53.46 | cr2 | it seems that tiacx is on SDC1 everywhere |
22:55.29 | rolk | cr2: I'm making a first attempt to compile the module. |
22:55.39 | cr2 | good |
22:56.00 | *** join/#htc-linux hollo (n=hollo@3e6b025d.rev.stofanet.dk) |
22:56.15 | rolk | error: implicit declaration of function 'sdio_readb_ext'. |
22:56.28 | maejrep[w] | missing an include? |
22:58.25 | cr2 | diam210000 |
22:59.22 | *** join/#htc-linux ionstorm (n=ion@ip68-227-226-5.ph.ph.cox.net) |
22:59.32 | Mullins | who can give access to push to git.linuxtogo.org? |
23:01.02 | NetRipper | register at projects.linuxtogo.org and check the mobile linux project |
23:01.25 | NetRipper | when you're logged in there's a link somewhere in that project on the right-hand side to request participation |
23:02.24 | cr2 | maejrep[w]: this MPP is gpio -related |
23:04.04 | NetRipper | which kernel will you build against rolk ? |
23:04.47 | *** join/#htc-linux kaze_ (n=kaze@ABordeaux-158-1-27-51.w90-55.abo.wanadoo.fr) |
23:04.56 | rolk | Well, obviously ltg-git. The missing function is from drivers/mcc/core in the android kernel. |
23:06.41 | Mullins | netripper: I've done that. Can you accept my request to join the project? |
23:06.58 | NetRipper | Mullins, ph5 or Kevin2 need to do that, one of them receives the e-mail |
23:07.06 | Mullins | netripper, np, ty |
23:07.24 | cr2 | rolk: sdio is .25+ |
23:08.12 | cr2 | maejrep[w]: your sd alt confirmed |
23:09.19 | cr2 | maejrep[w]: where should i put the lcd init docs ? |
23:10.24 | rolk | cr2: What do you mean by .25+? |
23:10.35 | cr2 | raph800 -> 9,1,a5a ; 3,1,708 ; 6,1,b22 ; i2c(cc,20,29,0) |
23:10.51 | cr2 | rolk: 2.6.25+ |
23:12.17 | cr2 | raph800 -> and then 8,1,b22 ; a,1,a28 |
23:12.32 | cr2 | maejrep[w]: 5 voltages for lcd |
23:14.43 | j0b0 | evening |
23:14.53 | rolk | cr2: its in the latest ltg / htc-vogue branch. But it lacks this function. I've added it, but all the include files where missing too. Tryingt to fix that. |
23:15.17 | cr2 | rolk: which kernel version is that ? |
23:16.19 | maejrep[w] | cr2: sd alt? |
23:16.52 | j0b0 | sdio_readb_ext is in linux/mmc/sdio_func.h |
23:16.55 | cr2 | maejrep[w]:sdc3 pins on gpio |
23:17.07 | maejrep[w] | oh, how it differs from raph100? |
23:17.36 | cr2 | maejrep[w]: MSM_SDIO wiki |
23:17.44 | cr2 | hmm |
23:17.55 | cr2 | raphael_gpio for that |
23:18.49 | cr2 | do we have the code to query the toshiba gpio pins over mddi ? |
23:19.08 | maejrep[w] | no idea what that means ;o |
23:19.23 | cr2 | ok :) |
23:19.57 | cr2 | maejrep[w]: see above. you need 5 (!) pmic_level calls for your lcd |
23:20.03 | j0b0 | cr2: would board-trout-panel.c have that |
23:20.07 | rolk | cr2: Its 2.6.25 |
23:20.24 | j0b0 | it has tables with registers and values to init mddi and panel |
23:20.27 | cr2 | j0b0: it's probably somewhere in the drivers/video |
23:20.32 | maejrep[w] | cr2: all that just to turn on? or off? or both |
23:20.41 | cr2 | maejrep[w]: both |
23:20.46 | maejrep[w] | odd that I didn't see all that in my traces :x |
23:21.03 | j0b0 | trout-panel is like mddi_client_bleh but has more init code |
23:21.04 | maejrep[w] | do you have to change vreg level when turning off? |
23:21.11 | cr2 | maejrep[w]: how many did you see ? |
23:21.35 | cr2 | maejrep[w]: maybe they are set by oemsbl already |
23:21.45 | maejrep[w] | i saw 2 vreg_switch's when turning off. then when turning on, I saw 2 vreg_level's and 2 vreg_switch's |
23:21.52 | cr2 | j0b0: mddi_remote_read ? |
23:22.35 | cr2 | maejrep[w]: ok. then maybe your spl is just overzealous |
23:22.53 | j0b0 | i would think so. it has registers named GPIODATA GPIODIR GPIOSEL |
23:23.50 | cr2 | j0b0: ok, i have the raph100 version already in wiki. on raph800/blac100 it's a bit more involved |
23:24.10 | cr2 | but blac100 has only 2 lcds, while raph800 -> 6 |
23:24.41 | j0b0 | ive been putting some of that init code from trout into mddi-client-toshiba to see if it has any effect |
23:25.18 | j0b0 | the mddi init code does nothing, the panel init code makes thepanel fade to black. device keeps running |
23:28.22 | cr2 | j0b0: but getting the gpio state and calculating the panel ID is certainly non-destructive |
23:28.52 | cr2 | maejrep[w]: so the vreg_level works now too ? |
23:29.58 | j0b0 | cr2: i put the code in that processes the mddi init table and panel init table. the latter made it go black |
23:30.51 | cr2 | ok |
23:30.53 | j0b0 | but to get rig of the messed up colors on the raph800, would that take proper mddi init |
23:34.27 | cr2 | j0b0: i see a lot of toshiba code too. maybe it's identical with the raph100 init, but one should check it |
23:35.04 | j0b0 | how would one go at that |
23:35.23 | j0b0 | i guess this code gets run at device init, a time when you can not run any tracing tools |
23:37.14 | j0b0 | the mddi init table doing nothing might mean that it works as in configures what was already configured, otoh goios are generally different |
23:37.37 | j0b0 | *gpios |
23:41.51 | maejrep[w] | cr2: it froze my phone when I tried it |
23:44.27 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
23:44.44 | tmzt | 17:23 < cr2> x67 is bt power |
23:44.44 | tmzt | 17:23 < cr2> x65 bt reset |
23:44.54 | tmzt | does this mean bt power is on microp? |
23:46.01 | cr2 | maejrep[w]: ok |
23:46.32 | cr2 | tmzt: no, these are the gpios. the same as on raph100. i've already added this data into raphael_gpio |
23:48.27 | cr2 | tmzt: i'm looking for the g1 bt driver. where is it located ? |
23:55.37 | cr2 | hmm. it seems that dzo has added the _fixup function to enable discontiguous memory |
23:56.14 | cr2 | NetRipper: do oyu want to add the missing 128MB SDRAM ? |
23:59.00 | j0b0 | how dangerous is that ;) |