| 00:00.13 | maejrep | 0x100 is, but not the others |
| 00:01.27 | tmzt | what's 0x8/9 ? |
| 00:01.40 | dcordes_ | stefan_schmidt: ping |
| 00:01.46 | maejrep | dunno, haven't seen them used yet |
| 00:06.21 | *** join/#htc-linux vizo (n=vizo@c-71-58-216-245.hsd1.nj.comcast.net) |
| 00:07.29 | stefan_schmidt | dcordes_: pong |
| 00:07.40 | oliwan | I'm missing this file from the repo. "htcdiamond_defconfig" Anyone know where to get it? |
| 00:07.47 | dcordes_ | stefan_schmidt: frameworkd on g1 will be no problem |
| 00:08.01 | stefan_schmidt | dcordes_: cool, that's good news |
| 00:08.19 | dcordes_ | at communication works in the same way |
| 00:08.35 | stefan_schmidt | dcordes_: What about audio? |
| 00:08.44 | stefan_schmidt | dcordes_: Also ootb like on the kaiser? |
| 00:08.53 | *** join/#htc-linux gh0ul (n=asds@host81-154-247-76.range81-154.btcentralplus.com) |
| 00:09.32 | dcordes_ | it only works ootb on kaiser because kaiser AMSS uses the speaker automatically during calls when no other audio routing is set |
| 00:10.20 | stefan_schmidt | dcordes_: The question is now if this is the same on G1 :) |
| 00:10.35 | dcordes_ | I don't think so |
| 00:10.36 | tmzt | stefan_schmidt: I think the audio routing on g1 is done through a special file and a userspace library |
| 00:10.53 | dcordes_ | tmzt: swetland said rpc routing |
| 00:10.57 | tmzt | the special file just exposes the registers to userspace |
| 00:10.57 | stefan_schmidt | ok, thanks |
| 00:11.02 | dcordes_ | the userspace library is audio flinger? |
| 00:11.04 | tmzt | ok |
| 00:11.08 | tmzt | no, something from htc |
| 00:11.12 | stefan_schmidt | urgs |
| 00:11.14 | tmzt | or qct |
| 00:11.22 | stefan_schmidt | audio driver in userspace *sigh* |
| 00:11.37 | dcordes_ | binary |
| 00:11.39 | tmzt | it may be possible to build a asoc driver but google has not done it yet |
| 00:12.02 | dcordes_ | like everything on g1 that interfaces with arm9 |
| 00:12.03 | stefan_schmidt | Anyway, that is not my problem. The tester will take care about the kernel side. And thus also the audio driver. :) |
| 00:12.18 | stefan_schmidt | hmm, ok |
| 00:12.40 | tmzt | dcordes_: you might be right about the routing though, the library is for echo cancellation or something |
| 00:12.59 | tmzt | is there a way to do rpc? |
| 00:15.07 | dcordes_ | tmzt: only know swetland said audio routing in g1 is set with rpc. what does rpc stand for? |
| 00:15.43 | tmzt | remote procedure call, but it's just a generic term |
| 00:18.16 | mdrobnak | tmzt: Has anyone implemented anything for the keyboard stuff for RAPH in a kernel yet? |
| 00:20.18 | tmzt | don't think so |
| 00:21.22 | mdrobnak | Ok. |
| 00:21.55 | mdrobnak | I'm switching to my laptop - going to start installing Windows 7 Beta on a HD I've got lying around...Then I'll try HaRET special key debugging again.. |
| 00:22.03 | dcordes_ | stefan_schmidt: who's the tester? openmoko inc. employee? |
| 00:22.17 | mdrobnak | Be back in a few. |
| 00:22.34 | stefan_schmidt | dcordes_: no, the LWN Author |
| 00:22.44 | dcordes_ | stefan_schmidt: btw kernel changes don't affect those things. they are based on the arm9 software |
| 00:22.50 | dcordes_ | LWN? |
| 00:22.58 | stefan_schmidt | Linux Weekly news |
| 00:23.06 | stefan_schmidt | http://lwn.net/ |
| 00:24.46 | vizo | does wifi work on android 1.0 for the kaiser? |
| 00:25.19 | dcordes_ | no |
| 00:25.52 | dcordes_ | it works in no android because the driver is not done yet |
| 00:25.59 | vizo | oh |
| 00:26.05 | vizo | thanks |
| 00:26.10 | dcordes_ | np |
| 00:26.12 | vizo | first day trying it |
| 00:28.15 | vizo | well I got my hands on a kaiser, a rapheal and a g1 dev phone. I dont nowenogh to be very helpful but i can try stuff if anybody wants |
| 00:28.32 | vizo | nowenogh = know enough |
| 00:29.48 | maejrep | tmzt, is it a bad idea to hook INT_GPIO_GROUP2 for the keyboard? |
| 00:30.27 | tmzt | yeah |
| 00:30.38 | tmzt | why is it called that or is that only in haret? |
| 00:30.58 | maejrep | that's on the wiki and in haret |
| 00:30.58 | tmzt | Kevin2: how do we add the proper gpio mux to haret for msm? |
| 00:31.27 | maejrep | 000.497 IRQS IRQ1: GPIO2(33)=1 |
| 00:31.27 | maejrep | 000.722 IRQS IRQ1: GPIO2(33)=1 |
| 00:32.16 | maejrep | if I add gpios to traces, I get GPIO 1-11, but its normally high, and pulls low when a key is pressed |
| 00:32.46 | maejrep | but 1-11 is in the wiki as "irq (Y) wakeup, Ukey" |
| 00:32.51 | maejrep | and I don't know what that means :| |
| 00:33.02 | NetRipper | gpio supports irqs as well |
| 00:33.23 | NetRipper | we use a gpio irq for the sd card slot detection |
| 00:33.28 | maejrep | right, I could hook MSM_GPIO_TO_IRQ(27) on IRQF_FALLING |
| 00:33.39 | NetRipper | exactly |
| 00:33.40 | maejrep | but I want to be sure that its only being used for keybaord |
| 00:33.49 | maejrep | and I can't tell that from cr2's description on the wiki ;x |
| 00:34.22 | NetRipper | if you use irq 33 (gpio2) you will get an interrupt on any irq fired on that bank ;) |
| 00:34.26 | NetRipper | i think |
| 00:34.40 | maejrep | that was my understanding too, so I think I'll avoid that :p |
| 00:34.52 | NetRipper | i think it's claimed already by the msm_gpio |
| 00:35.16 | maejrep | do you know what the description for gpio 27 means? is it safe to use for keyboard? |
| 00:35.50 | *** join/#htc-linux mdrobnak (n=mdrobnak@pool-96-232-187-37.nycmny.fios.verizon.net) |
| 00:35.50 | NetRipper | no i dont know what the description means exactly |
| 00:35.59 | tmzt | it should be claimed by msm_gpio, what does it use to decode those? |
| 00:36.01 | NetRipper | arent there other gpio's fired? maybe ones that have more to do |
| 00:36.33 | maejrep | no, just 1-11 (goes low then reset high), and 3-18 to enable the keybaord backlight |
| 00:36.53 | NetRipper | maejrep, then i think you dont have much choice ;) |
| 00:37.15 | maejrep | that or polling i guess ;/ |
| 00:37.29 | NetRipper | i doubt polling is the wya |
| 00:37.30 | NetRipper | way* |
| 00:37.33 | maejrep | agreed |
| 00:37.55 | mdrobnak | Back. OK, so first problem with Win7 is a IDE card that's too old. Ugh. |
| 00:38.25 | NetRipper | cr2, can you clearify gpio 27? is it only used for keyboard or did you find it used for other things? |
| 00:38.33 | maejrep | 003.102 TRACES in1: in1-11(203)=0 @~03f6744c |
| 00:38.34 | maejrep | 003.102 IRQS IRQ1: GPIO2(33)=1 |
| 00:38.34 | maejrep | 003.102 TRACES in1: in1-11(203)=1 @~78042ab8 |
| 00:39.36 | dcordes_ | mdrobnak: win7? what's that |
| 00:39.50 | maejrep | its fired on both press and release, which is exactly what I need |
| 00:40.03 | maejrep | but for some reason, it only fires once, and never fires after that |
| 00:40.26 | maejrep | even if I pull it high manually with gpio_set_value(27, 1) |
| 00:41.27 | maejrep | i'm just getting stuck on the irq part of the driver :/ |
| 00:42.18 | NetRipper | dcordes_, the windows 7 beta probably |
| 00:42.58 | NetRipper | maejrep, the irq is only called once in linux you mean? |
| 00:43.00 | dcordes_ | how exciting :) |
| 00:43.08 | maejrep | right |
| 00:43.29 | NetRipper | maejrep, you probably must set a reset or 'read' bit somewhere |
| 00:43.30 | maejrep | I can insert the module, press a key and my printk runs, but then never runs again |
| 00:44.08 | mdrobnak | dcordes_: Windows 7 Public Beta is out...Downloaded the 64 Bit version... |
| 00:44.09 | maejrep | I was trying to find an example of clearing or resetting the irq in other drivers, but can't find anything :s |
| 00:44.50 | NetRipper | maejrep, i think it's device-specific.. signalling that the irq is handled is done by the msm_gpio driver |
| 00:44.52 | maejrep | I even used j0b0's gpiotest concept of setting a timer for 0ms for handling it |
| 00:45.30 | maejrep | so its not the irq ack() that I'm missing? it's some other clear flag I need to find? |
| 00:45.34 | NetRipper | maejrep, some drivers just fire an irq.. then wait for you to handle the data and signal when ready.. so that it wont fire again until you're done |
| 00:45.35 | mdrobnak | maejrep: Would that explain some of the keyboard weirdness I was having while testing under HaRET last night (that was with you, right?) |
| 00:46.11 | maejrep | it was, yes, but no that wouldn't explain what you were seeing |
| 00:46.23 | maejrep | everything works fine in wince |
| 00:46.26 | NetRipper | maejrep, the low level irq ack is done by the existing drivers afaik.. |
| 00:46.27 | maejrep | (for me) |
| 00:46.29 | mdrobnak | I'm going to try testing again shortly |
| 00:46.41 | NetRipper | maejrep, you just have to return IRQ_HANDLED in your interrupt handler |
| 00:46.47 | maejrep | right |
| 00:46.55 | maejrep | hmm ;s |
| 00:47.56 | maejrep | could it be because I'm not reading from i2c at the time its fired? i would think that shouldn't matter as far as the irq is concerned |
| 00:48.47 | maejrep | that is, if I enable the code to read from i2c, it tends to freeze the phone when the irq gets fired and I don't even see the printk |
| 00:49.07 | maejrep | if I disable the i2c communications, I see the printk but only once |
| 00:49.43 | NetRipper | while an irq is being handled you're not allowed to do everything |
| 00:50.03 | NetRipper | i.e. you cannot use mdelay() and the sort |
| 00:50.08 | NetRipper | (which requires irqs as well) |
| 00:50.27 | maejrep | but my handler is just starting a 0ms timer and returning |
| 00:50.54 | NetRipper | you should perhaps do it theway the touchscreen drivers (intended) to do it... |
| 00:51.03 | NetRipper | when the irq fires, schedule a work item |
| 00:51.26 | maejrep | k, I'll try that .. I had a workqueue setup before, and just kept running into problems with freezing, so I stripped the driver down |
| 00:51.42 | NetRipper | maejrep, and you can try request_irq()'ing with IRQF_DISABLED flag.. |
| 00:51.52 | maejrep | NOAUTOEN ? |
| 00:51.56 | NetRipper | no |
| 00:52.07 | maejrep | hmm ok |
| 00:52.15 | NetRipper | <PROTECTED> |
| 00:52.39 | maejrep | so what, that removes the need to disable_irq() and enable_irq() ? |
| 00:53.05 | NetRipper | also, for gpio irqs, maybe you should use IRQF_SHARED flag, as gpio irqs share the same general GPIO2 irq |
| 00:53.09 | NetRipper | and GPIO1 irq |
| 00:53.28 | NetRipper | though the msm_gpio might already handle that |
| 00:53.45 | maejrep | k, seems like when I tried IRQF_SHARED my request_irq() was failing |
| 00:53.53 | maejrep | but that might have been on a different attempt |
| 00:54.00 | NetRipper | no doesn't remove the need for disable_irq and enable_irq.. although, you dont need to disable and enable_irq at all (only disable_irq at de-init) |
| 00:54.21 | NetRipper | request_irq() automatically enables afaik |
| 00:55.18 | maejrep | that's what I meant -- normally you need to disable the irq in the handler, then enable it when you're done handling |
| 00:55.46 | maejrep | it does automatically enable, unless you use IRQF_NOAUTOEN |
| 00:56.24 | *** part/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
| 00:56.59 | mdrobnak | marjrep: Where's haretconsole again? |
| 00:56.59 | mdrobnak | *maejrep, rather |
| 00:57.27 | maejrep | <tmzt> handhelds.org/~koconnor/haret/ |
| 00:57.31 | NetRipper | i think you only need to disable_irq and enable_irq again when you use IRQF_DISABLED... not the other way around |
| 00:57.33 | mdrobnak | Thanks. |
| 00:57.55 | maejrep | hmm |
| 01:02.18 | NetRipper | im really off now ;) gnite again ;) |
| 01:02.26 | mdrobnak | night |
| 01:02.33 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
| 01:02.48 | maejrep | nite |
| 01:06.03 | mdrobnak | hmm |
| 01:06.04 | mdrobnak | looks like rndis on Ubuntu isn't enough for Haret |
| 01:06.12 | mdrobnak | and I hit run by accident oops |
| 01:06.19 | maejrep | i've done that :p |
| 01:10.01 | dcordes_ | dream_kill: still around? |
| 01:13.40 | maejrep | hmmm |
| 01:13.54 | maejrep | I just made my screen very unhappy :x |
| 01:14.17 | maejrep | I saw someone else last night with this problem as well |
| 01:14.28 | maejrep | checks git commits :x |
| 01:15.12 | maejrep | oh, it fixed itself |
| 01:17.18 | maejrep | and it broke again :| |
| 01:20.38 | maejrep | strange, calibrating seems to fix it... |
| 01:20.51 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
| 01:27.17 | *** join/#htc-linux mdrobnak (n=mdrobnak@pool-96-232-187-37.nycmny.fios.verizon.net) |
| 01:28.09 | mdrobnak | Oops. Stupid USB network. |
| 01:28.23 | mdrobnak | Ok, what were the two addresses to listen for? |
| 01:28.31 | mdrobnak | <mdrobnak> I remember ibit 0..999 and wbit 33 I think? Then wirq 5 and hit a key.. |
| 01:28.43 | mdrobnak | I didn't see anything after that.. |
| 01:31.20 | Mullins | anyone know where the Angstrom X is told to do a calibrate on startup? |
| 01:39.12 | maejrep | mdrobnak, 0xb2300000 and 0xb230000c |
| 01:39.22 | mdrobnak | Ah, thanks. |
| 01:43.35 | *** join/#htc-linux zycho (n=zycho@a89-182-6-233.net-htp.de) |
| 01:45.56 | mdrobnak | maejrep: Ok, so Fn key doesn't affect things, huh? |
| 01:46.03 | mdrobnak | Cause my "9" key is Fn+k |
| 01:46.09 | mdrobnak | and I get the keycode for k |
| 01:46.15 | maejrep | no, its the driver that interprets fn/shift locks |
| 01:46.16 | mdrobnak | (according to your wiki entry) |
| 01:47.02 | maejrep | so its not like a laptop keyboard where Fn+x sends a different keycode from the hardware |
| 01:47.21 | maejrep | all the keys are controlled independently as just simple buttons as far as the hardware is concerned |
| 01:47.27 | mdrobnak | ok |
| 01:47.27 | mdrobnak | so |
| 01:47.38 | mdrobnak | my Windows key is "1" on your keyboard, @ is "2" etc |
| 01:47.44 | mdrobnak | That seems to be OK. |
| 01:48.35 | mdrobnak | BKSP is "40" for me |
| 01:49.11 | mdrobnak | Enter is 20 for me too, though |
| 01:49.42 | maejrep | hmm, so is bksp in the top right corner? |
| 01:49.48 | maejrep | not next to 'P'? |
| 01:51.43 | mdrobnak | it is |
| 01:51.43 | mdrobnak | 1 row down |
| 01:51.53 | maejrep | hrm, that's odd |
| 01:52.01 | maejrep | I thought they would at least map to the same physical location |
| 01:52.16 | maejrep | but my backspace is next to 'P' on the 2nd row |
| 01:52.19 | mdrobnak | addlist mmutrace 0xb230000c 1 |
| 01:52.21 | mdrobnak | err |
| 01:52.26 | mdrobnak | 000.877 7805d5f0: 05852000(str) # b2300000 =00000200 |
| 01:52.31 | mdrobnak | errrrrr |
| 01:52.32 | mdrobnak | damnit |
| 01:52.42 | maejrep | and keycode '0x40' is my equal sign, which is on the top row, far right |
| 01:52.49 | mdrobnak | 000.877 7805d5f4: e5933000(ldr) # b230000c==00000040 |
| 01:53.47 | mdrobnak | I get 0x10 for my top row, far right key, which is - |
| 01:54.17 | mdrobnak | So the Fuze will have a different layout, thats for certain. |
| 01:54.27 | mdrobnak | But that's not really that big of a deal. |
| 01:56.01 | mdrobnak | 000.712 7805d5f4: e5933000(ldr) # b230000c==00000036 is my "Deathstar" (Aka AT&T) key |
| 01:56.16 | mdrobnak | I dunno what was up with my results last night |
| 01:56.52 | maejrep | I rearranged the table columns on the wiki, if you'd like to add RAPH110 with your results |
| 01:56.59 | mdrobnak | "0x047" is Email Key |
| 01:57.18 | maejrep | same |
| 01:58.06 | maejrep | I'd say, anything that's the same just leave blank or '--' or something, so the column only shows keys that are different |
| 01:58.52 | mdrobnak | k |
| 02:15.05 | dcordes_ | Mullins: because it is designed for non keyboard devices where a good calibration is inevitable |
| 02:15.39 | dcordes_ | Mullins: the calibration is not called if /etc/pointercal is present |
| 02:16.00 | dcordes_ | Mullins: ts_calibrate outputs /etc/pointercal |
| 02:19.50 | *** part/#htc-linux Balsat (n=kll@87.72.13.87) |
| 02:22.19 | tmzt | maejrep: do you have a i2c driver for the keyboard? |
| 02:22.38 | maejrep | been working on it for a couple days :( |
| 02:22.49 | maejrep | still can't get it to fire more than once on the irq |
| 02:22.50 | tmzt | are you using tsc2003 or similar? |
| 02:23.00 | tmzt | what does that mean |
| 02:23.12 | maejrep | i've read several drivers to look for clues |
| 02:23.18 | maejrep | what does what mean? |
| 02:23.25 | maejrep | the irq fires once and then won't fire again after that |
| 02:23.34 | tmzt | when you press a key? |
| 02:23.38 | tmzt | what irq? |
| 02:23.57 | maejrep | MSM_GPIO_TO_INT(27) => 91 |
| 02:24.05 | maejrep | and yes when I press a key |
| 02:24.15 | tmzt | how are you requesting it? |
| 02:25.18 | maejrep | request_irq(client->irq, atmelkbd_interrupt, IRQF_TRIGGER_FALLING | IRQF_DISABLED | IRQF_SHARED, client->dev.driver->name, client) |
| 02:26.01 | oliwan | Hey guys, I'm trying to build but can't find the file htcdiamond_defconfig. Does anyone know where this is? |
| 02:28.14 | maejrep | tmzt, ok, so it seems like I just confirmed it's related to gpio 27 not being set back high after its handled |
| 02:28.32 | maejrep | any idea why: gpio_direction_output(27, 1); wouldn't do that? |
| 02:29.13 | Mullins | dcordes: yeah dcordes I thought there may have been a config to disable it but it doesnt matter cos if its not working for the calibration it wont work in X |
| 02:29.42 | dcordes_ | Mullins: try my tslib configuration |
| 02:30.36 | Mullins | ok. I will try with your pointercal |
| 02:30.37 | dcordes_ | there is /etc/ts.conf and /etc/profile.d/tslib.sh |
| 02:31.19 | dcordes_ | make sure tslib.sh points to the correct input device |
| 02:31.33 | dcordes_ | should be /dev/input/event0 |
| 02:32.23 | Mullins | TSLIB_TSDEVICE=/dev/input/touchscreen0 |
| 02:32.35 | Mullins | dcordes: no good? |
| 02:32.48 | dcordes_ | if that's a symlink to event0 it's ok |
| 02:33.06 | dcordes_ | just set it to /dev/input/event0 to make sure |
| 02:33.11 | mdrobnak | maejrep, expect some differences in this layout, btw.. |
| 02:33.23 | mdrobnak | q isn't q lol |
| 02:33.52 | maejrep | ? |
| 02:34.40 | Mullins | in initrd/dev is no input folder |
| 02:34.48 | mdrobnak | it's like shifted over one cause of a caps lock key |
| 02:35.04 | Mullins | until I boot it I suppose :) |
| 02:37.04 | *** part/#htc-linux exco (n=exco@e181123024.adsl.alicedsl.de) |
| 02:41.09 | dcordes_ | Mullins: does that work? |
| 02:42.05 | *** join/#htc-linux buster (n=buster@lostmind.org) |
| 02:46.33 | maejrep | tmzt, found more stuff changing on keypress: |
| 02:46.35 | maejrep | 001.130 IRQS IRQ1: GPIO2(33)=1 |
| 02:46.35 | maejrep | 001.130 TRACES nirq1: GPIO27(43)=1 @~8001d730 |
| 02:46.36 | maejrep | 001.130 TRACES in1: in1-11(75)=0 @~8001d730 |
| 02:46.36 | maejrep | 001.130 TRACES intr1_en: intr1_en-11(203)=0 @~03f53ea4 |
| 02:46.36 | maejrep | 001.130 TRACES in1: in1-11(75)=1 @~78042ab8 |
| 02:46.36 | maejrep | 001.195 TRACES nirq1: GPIO27(43)=0 @~78042ab8 |
| 02:46.38 | maejrep | 001.195 TRACES intr1_en: intr1_en-11(203)=1 @~78042ab8 |
| 02:50.35 | Mullins | dcordes: touchscreen0 is set to event0 |
| 02:50.46 | *** part/#htc-linux p3t3r__ (n=peter@134.245.164.105) |
| 02:51.30 | Mullins | dcordes: I can see all the printk messages from tsc2003.c so I know it is working |
| 02:51.57 | tmzt | what's nirq1? |
| 02:52.26 | dcordes_ | Mullins: try only running Xfbdev and see if you can move the cursor |
| 02:54.02 | Mullins | dcordes: no, where should pointercal be /etc ? |
| 02:54.22 | dcordes_ | yes |
| 02:54.56 | Mullins | dcordes: what can we do about tslib expecting raw values and Android expecting scaled? |
| 02:55.10 | Mullins | could use an Android CONFIG? |
| 02:55.55 | maejrep | damn my mouse just died |
| 02:56.04 | dcordes_ | we could do it vice versa and temporarily add a config no-android that includes the refresh thread and ts patch |
| 02:56.08 | maejrep | tmzt, intr1 is 0xa9300c60 |
| 02:56.25 | maejrep | it was commented out in regs_msm.py but I uncommented it |
| 02:57.18 | maejrep | tmzt, and in gpio_hw.h, that address is GPIO_INT_EN_1 (interrupt enable?) |
| 02:57.23 | Mullins | dcordes: I had no pointercal in etc. Will try it now |
| 02:57.58 | maejrep | no, nevermind, that's intr1_en :x |
| 02:58.36 | maejrep | nirq1 is 0xa9300c70, which is GPIO_INT_STATUS_1 |
| 02:59.11 | mdrobnak | maejrep: I mapped out the keys, not sure about the ones like shift, caps, and Fn |
| 02:59.28 | maejrep | mdrobnak, did you update the wiki? |
| 02:59.38 | Mullins | dcordes: I forgot to mention I took out the refresh and tslib patch, and X started up without the refresh patch |
| 02:59.40 | mdrobnak | Not yet. I have a text file here. |
| 02:59.47 | maejrep | ah ok |
| 02:59.56 | dcordes_ | Mullins: it might start up, draw one frame, freeze. |
| 03:00.01 | maejrep | if you don't want to do it, put it on privatepaste.com and I'll do it when I get time |
| 03:00.20 | Mullins | dcordes: of course, I dont know cos I can't interact. Good point |
| 03:00.25 | dcordes_ | Mullins: so you see a picture of the calibration screen/checkered background/whatever |
| 03:01.11 | mdrobnak | marjrep: I'll also add in what the Fn + Keys do |
| 03:01.38 | mdrobnak | damnit, typo again |
| 03:01.42 | dcordes_ | I don't know how X behaves with the htc-vogue msm_fb because I didn't try yet. in the other kernels it sometimes showed a black screen with only a few lines drawn, sometimes one frame and froze |
| 03:07.08 | mdrobnak | maejrep, http://www.privatepaste.com/2axF91BG1w |
| 03:07.15 | *** join/#htc-linux piusvelte (n=irchon@71.175.8.29) |
| 03:10.55 | mdrobnak | maejrep, The keys are the exact same scancodes (as expected) |
| 03:11.02 | mdrobnak | maejrep, Just the different layout |
| 03:11.10 | maejrep | k |
| 03:12.09 | *** join/#htc-linux pickles (n=clmbngbk@75-25-130-222.lightspeed.sjcpca.sbcglobal.net) |
| 03:13.08 | Mullins | dcordes: I was going to try incorporate Dzos stuff into 2.6.27 as a lot has changed with it and he has already found some of it to be useful. What do you think? |
| 03:14.05 | dcordes_ | sounds great |
| 03:14.30 | Mullins | cool, I have 2 days off Mon and Tues. should be able to do it then |
| 03:14.55 | *** join/#htc-linux KeePette (n=chatzill@vit94-1-87-90-37-127.dsl.club-internet.fr) |
| 03:15.09 | *** join/#htc-linux clmbngbkng (n=clmbngbk@75-25-130-222.lightspeed.sjcpca.sbcglobal.net) |
| 03:15.17 | dcordes_ | nice. I think it would be good to stay as close to google as possible |
| 03:15.34 | dcordes_ | sees some windows7 presentation |
| 03:16.23 | dcordes_ | impressive :) |
| 03:16.32 | mdrobnak | lol |
| 03:17.31 | dcordes_ | eyecandy, touchscreen, social networking |
| 03:18.12 | mdrobnak | It's pretty fast, I must say. |
| 03:18.19 | mdrobnak | (Faster then Vista it seems anyway) |
| 03:18.22 | mdrobnak | But that's easy |
| 03:18.23 | mdrobnak | lol |
| 03:18.43 | *** join/#htc-linux Kuma (n=John@e179103019.adsl.alicedsl.de) |
| 03:21.05 | *** join/#htc-linux Mullins07 (n=bw@89.204.243.3) |
| 03:21.23 | *** join/#htc-linux nato (n=templarn@adsl-76-200-75-47.dsl.frs2ca.sbcglobal.net) |
| 03:21.53 | dcordes_ | they show a suped up blueangel at ces |
| 03:22.17 | mdrobnak | 20 second boot after bios post, 7 seconds to show desktop |
| 03:24.01 | dcordes_ | where's the htcs |
| 03:27.16 | dcordes_ | mdrobnak: how much space does it take? |
| 03:27.43 | mdrobnak | hmm |
| 03:28.00 | mdrobnak | 12 GBs used. :: gulp :: |
| 03:28.05 | mdrobnak | (Ultimate Edition) |
| 03:28.42 | dcordes_ | ouch |
| 03:29.43 | mdrobnak | dcordes_: Mind you that includes 4 GB between Paging and Hiberation file. |
| 03:36.00 | mdrobnak | Nice. File copy speeds arent dog slow lol |
| 03:46.45 | *** join/#htc-linux ionstorm (n=ion@ip68-227-226-5.ph.ph.cox.net) |
| 04:01.35 | maejrep | god this is really frustrating :| |
| 04:03.43 | *** join/#htc-linux addman3333 (n=skool@cpe-67-9-134-92.austin.res.rr.com) |
| 04:13.05 | mdrobnak | Ok I'm gonna try and get to bed early tonight, see ya everyone. |
| 04:44.05 | *** join/#htc-linux evildarknight (n=charles@41.207.133.235) |
| 04:57.07 | *** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl) |
| 05:16.19 | *** join/#htc-linux Iumentum (n=Iumenrum@3908ds1-ynoe.0.fullrate.dk) |
| 05:17.08 | Iumentum | Good evening(whatever else) folks |
| 05:17.36 | Iumentum | im so suprised to see so many people in here |
| 05:17.50 | Iumentum | but nice to to all of you :) |
| 05:18.01 | tmzt | hello |
| 05:18.33 | Iumentum | well i just came around here for once after thinking of it many times |
| 05:18.46 | Iumentum | many years since iøve been on IRC :) |
| 05:19.13 | Iumentum | but i've been following the topic at XDA for a while |
| 05:20.01 | Iumentum | and finaliy see some request from the developers about splitiing the topic into developing and suport topics |
| 05:20.58 | Iumentum | and im a developer myself but dont have time to study about getting linux to work on specific phones |
| 05:21.09 | Iumentum | but thhoguh that i can help testing |
| 05:21.10 | Iumentum | but |
| 05:21.19 | Iumentum | beside that i would like to help with support |
| 05:21.54 | Iumentum | and if you decide to split of topics at xda |
| 05:22.01 | Iumentum | i would love to help out |
| 05:22.10 | Iumentum | been holding my tounge manhy times |
| 05:22.51 | Iumentum | cause i didnt want to fill up the topics with crap posts, where you could actiaææy get the answer in the wiki |
| 05:23.27 | Iumentum | and deffently want to help out in the getting android running on my diamond |
| 05:23.39 | Iumentum | so i finaly decided to come around here |
| 05:23.44 | tmzt | ah, is diam working now? |
| 05:23.56 | Iumentum | well its working :) |
| 05:24.02 | Iumentum | but its freexing |
| 05:24.13 | Iumentum | but a lot of thing is working now :) |
| 05:24.44 | Iumentum | its seems like the last few weeks a lot of progress |
| 05:25.16 | Iumentum | but also a lot of support messages on the forum on xda |
| 05:26.09 | Iumentum | and no need for hard core developers to focus on support on getting there linux kernel to run on diamond/raphael |
| 05:26.23 | Iumentum | if they can focus on makinf things worl for us :) |
| 05:26.42 | Iumentum | im not really working on it |
| 05:26.50 | Iumentum | what im here for is more to support |
| 05:27.12 | tmzt | what's freezing? |
| 05:27.12 | Iumentum | and want to help if you're gonna split the topics into development and support |
| 05:27.39 | Iumentum | cause im been holding my tounge cause i dont want to fill out topic with crap support |
| 05:27.42 | tmzt | if they do it I assume the support section will be open for everyone to post |
| 05:27.56 | Iumentum | its just the android freezinf after a while |
| 05:28.06 | Iumentum | but its nt impotant to me :) |
| 05:28.12 | tmzt | do you have diam100 or diam800? |
| 05:28.26 | Iumentum | i got diam100 |
| 05:28.43 | tmzt | ok |
| 05:28.50 | Iumentum | but not important at all |
| 05:29.03 | Iumentum | im following the developemt close |
| 05:29.06 | Iumentum | silently :) |
| 05:29.18 | Iumentum | but want to help one way or another |
| 05:29.26 | Iumentum | and see that i can help with support |
| 05:29.41 | Iumentum | so if you split the topics i might wanna post things |
| 05:29.52 | Iumentum | cause im been holding my tounge many times |
| 05:30.18 | Iumentum | most of all cause i dont wanna answer question already answered in wiki |
| 05:30.50 | Iumentum | and want to hold to thread clean as posible |
| 05:30.56 | Iumentum | for the developers |
| 05:31.43 | Iumentum | and hink it will be a good idea with a sopport topic |
| 05:32.04 | Iumentum | so people who wanna try android can post shit there |
| 05:32.15 | Iumentum | and people like me who want to help can answer |
| 05:35.58 | Iumentum | well no matter what, im pretty drunk right now and probably should just hit the sack :D |
| 05:36.30 | Iumentum | but i just came here to tell if i can help in supportor something else i will be more than willing :) |
| 05:36.57 | Iumentum | i know a lot of guys is doing a great efort making things i want posible |
| 05:49.44 | parmaster | dcordes_: suped up ba at CES? |
| 05:50.11 | parmaster | another start-up hangers on? |
| 06:31.42 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 07:01.21 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 07:08.10 | maejrep | i never thought i'd have this much trouble with an irq :( |
| 07:11.56 | *** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com) |
| 07:12.02 | tmzt | is it doing the same things as the ts? |
| 07:13.19 | tmzt | <PROTECTED> |
| 07:13.31 | tmzt | how did you get that to work? |
| 07:16.12 | maejrep | uncommented it on regs_msm.py, and added the address to traces |
| 07:16.24 | maejrep | yeah, it's still only firing once after booting |
| 07:17.01 | maejrep | its negative polarity (at least in wince), so firing the irq pulls the bit low, then in wince when it gets cleared it goes high again |
| 07:17.05 | tmzt | are you using msm_gpio from trout? |
| 07:17.08 | maejrep | but in linux, I can't get it to reset high |
| 07:17.18 | maejrep | what specifically are you referring to? |
| 07:17.40 | maejrep | I use MSM_GPIO_TO_INT..? and gpio.c (not trout's implementation, which is board-trout-gpio.c) |
| 07:17.52 | tmzt | not that |
| 07:18.31 | maejrep | then I'm not sure what you're asking |
| 07:18.45 | tmzt | <PROTECTED> |
| 07:18.47 | tmzt | 22:20 < maejrep> any idea why: gpio_direction_output(27, 1); wouldn't do that? |
| 07:18.57 | tmzt | I missed a conversation earlier |
| 07:19.13 | maejrep | yeah, I found out why output is wrong |
| 07:19.40 | maejrep | problem is there's no mechanism for forcing the IN reg high, which is what's necessary for it to be triggered again |
| 07:25.22 | tmzt | check the msm_gpio source, it should handle the irq 33 and find the appropriate gpio that fired the irq |
| 07:26.00 | tmzt | what is triggered on TRIGGER_FALLING |
| 07:26.01 | tmzt | ? |
| 07:26.08 | maejrep | well, i'm hooking gpio 27, not INT_GPIO2 |
| 07:27.13 | maejrep | how do you mean? the keyboard gpio goes from high to low when a key is pressed, then returns high again. I'm requesting the IRQ as TRIGGER_FALLING so I only get the interrupt at the point it goes from high to low |
| 07:29.45 | maejrep | hmm |
| 07:30.29 | maejrep | if I assume that haret's tracing is fairly accurate in terms of sequence, it looks like it might actually be the act of reading the i2c data that causes gpio 27 to go high again :x |
| 07:30.47 | maejrep | 001.090 TRACES stat1: GPIO27(43)=1 @~8001d730 |
| 07:30.47 | maejrep | 001.090 TRACES in1: in1-11(75)=0 @~8001d730 |
| 07:30.47 | maejrep | 001.090 TRACES intr1_en: intr1_en-11(203)=0 @~03f53ea4 |
| 07:30.47 | maejrep | 001.090 7803d720: str r3, [r5] # b2300000 =000001ce |
| 07:30.48 | maejrep | 001.090 7803d790: str r3, [r5] # b2300000 =00000010 |
| 07:30.48 | maejrep | 001.090 7803d878: str r3, [r5] # b2300000 =000001cf |
| 07:30.50 | maejrep | 001.090 TRACES in1: in1-11(75)=1 @~78042ab8 |
| 07:30.54 | maejrep | 001.090 7803d940: streq r2, [r5] # b2300000 =00000200 |
| 07:30.56 | maejrep | 001.090 7803d944: ldr r3, [r3] # b230000c==00000095 |
| 07:30.58 | maejrep | 001.090 7803d944: ldr r3, [r3] # b230000c==00000000 |
| 07:31.04 | tmzt | you can't know unless you disable the ce driver, would a longer wirq work? |
| 07:31.07 | maejrep | right after the 1cf to i2c is when the gpio goes high again |
| 07:31.40 | tmzt | in1-11 is the kbd? |
| 07:31.55 | maejrep | work for what? and disable what driver? you mean if the keyboard is disabled, and it doesn't read from i2c, i should expect 1-11 to stay low? |
| 07:32.06 | maejrep | yes, that's my best guess at this point |
| 07:32.39 | tmzt | you are saying the hardware handles it, I think wirq will prevent ce from running if the timer is ibit'd |
| 07:32.49 | tmzt | sorry |
| 07:33.38 | tmzt | I see what you're saying now |
| 07:33.39 | maejrep | I'm saying its a possibility :P for being a programmer, and even a C programmer, I'm a total newb when it comes to this :) |
| 07:34.16 | maejrep | but in linux, I get the irq to fire once on pressing a key. after that, gpio 27 never goes high in order to fire a second time |
| 07:34.42 | maejrep | if this trace is to be trusted, it looks like the hardware is bringing the gpio high again after reading the key data |
| 07:34.55 | tmzt | then why doesn't it work in linux? |
| 07:35.00 | maejrep | which I know you mentioned a few days ago, I've just been so focused on getting the irq to fire properly first |
| 07:35.23 | tmzt | it this irq attached as the i2c irq? |
| 07:35.24 | maejrep | well, before when I had the i2c code in the irq handler, it would freeze the phone as soon as I tried to read from i2c |
| 07:35.34 | maejrep | is there an i2c irq? |
| 07:35.43 | tmzt | what does your pdata say? |
| 07:35.57 | maejrep | ah, there is.. irq 34 = INT_PWB_I2C |
| 07:36.05 | tmzt | PWB? |
| 07:36.14 | tmzt | wbit 34 and try it |
| 07:36.32 | maejrep | my pdata on adding the i2c device? I'm setting .irq=MSM_GPIO_TO_INT(27) |
| 07:36.49 | tmzt | is that used by your driver or the i2c host? |
| 07:36.51 | maejrep | I'm currenting wbit'ed on everything except the annoying ones (47,3,6,16,19) |
| 07:37.29 | maejrep | is what used? the .irq is used by the driver (and can even be ignored if I choose not to use it) |
| 07:38.05 | maejrep | I don't know what PWB_I2C is meant to be :x |
| 07:38.06 | tmzt | ok, is there a gpio in the chips[] you register? |
| 07:39.02 | maejrep | the i2c chip? I set the irq, but i don't think there's a gpio property |
| 07:39.24 | tmzt | are you using i2c_register_board_info like in halibut? |
| 07:39.29 | tmzt | board-halibut |
| 07:39.58 | maejrep | yes |
| 07:40.17 | maejrep | and it's called with: |
| 07:40.19 | maejrep | static struct i2c_board_info i2c_devices[] = { |
| 07:40.19 | maejrep | <PROTECTED> |
| 07:40.19 | maejrep | <PROTECTED> |
| 07:40.19 | maejrep | <PROTECTED> |
| 07:40.19 | maejrep | <PROTECTED> |
| 07:40.21 | maejrep | <PROTECTED> |
| 07:40.46 | tmzt | try disabling that MSM_GPIO_TO_INT |
| 07:41.13 | tmzt | it's commented out in the board-trout |
| 07:41.25 | tmzt | board-halibut |
| 07:42.15 | maejrep | yeah and in board-trout, but for the camera driver I think |
| 07:42.47 | maejrep | and the led driver (both have no .irq) |
| 07:43.05 | maejrep | probably because they use /dev nodes to read data |
| 07:43.19 | tmzt | your using request_irq though, so you driver gets called? |
| 07:43.48 | tmzt | you have the MODULE_NAME?? in your driver? |
| 07:43.49 | maejrep | yeah the driver definitely gets called |
| 07:44.10 | tmzt | that matches _i2c_devices[] ? |
| 07:44.14 | maejrep | I'm plastering printk's all over the place ;) so I know it's being called |
| 07:44.14 | maejrep | yes |
| 07:44.45 | tmzt | you say the i2c has data when the gpio_irq is low? |
| 07:45.00 | maejrep | that's what it looks like |
| 07:45.19 | tmzt | check I2C_BOARD_INFO and see if there is another field in the struct for negation |
| 07:45.50 | maejrep | based on the trace, the gpio is normally high. when I press a key, GPIO2 irq is fired, gpio 27 is pulled low, then it reads from i2c. as soon as the 1ce+1 (read) is sent, gpio 27 drives high again |
| 07:46.02 | maejrep | negation as in negative polarity? |
| 07:46.11 | tmzt | yes |
| 07:46.47 | maejrep | I don't think i2c uses the .irq property in itself - its only used to pass the data to the driver, which is responsible for using the data however it needs to |
| 07:47.14 | tmzt | it has to be able to tell which chip driver to call |
| 07:47.45 | tmzt | it's always RISING |
| 07:47.54 | tmzt | drivers/i2c/busses/i2c-msm.c |
| 07:48.16 | maejrep | it has unsigned short flags; |
| 07:48.44 | maejrep | that's the i2c irq |
| 07:49.43 | tmzt | ok, trying to see where chips are registered |
| 07:51.46 | maejrep | msm_i2c_resources registers the i2c-msm device |
| 07:51.57 | maejrep | and that's where the irq is set: .start = INT_PWB_I2C, |
| 07:52.17 | maejrep | so that irq is different from the keyboard irq |
| 07:52.56 | maejrep | I think I'm gonna try reading from it again.. hopefully I've fixed enough issues that it doesn't cause the device to freeze anymore :/ |
| 07:53.22 | maejrep | I just have a feeling that's what is driving the input high again |
| 07:53.23 | tmzt | that just means data is available it looks like |
| 07:53.26 | tmzt | that irq |
| 07:54.47 | maejrep | right |
| 08:04.01 | *** join/#htc-linux Xime (n=xime@bankize.net) |
| 08:05.36 | maejrep | btw, were you here last night when someone posted a picture of a raph (800 i think) with a screwed up fb? |
| 08:06.00 | tmzt | yeah do you need the links? |
| 08:06.08 | maejrep | I noticed mine started doing that after a git pull today, but it seems random.. like right now it looks fine, but my first kernel looked like that |
| 08:06.35 | tmzt | I think that's something j0b0 was working on |
| 08:07.03 | maejrep | ah ok |
| 08:07.17 | tmzt | changing the update code somehow |
| 08:07.18 | maejrep | not too worried about it yet cause I'm using ssh and don't even look at the screen |
| 08:07.33 | maejrep | [ 43.650884] IN: 00000800 <-- so after a fresh boot, the IN reg is high |
| 08:07.55 | maejrep | grr |
| 08:08.09 | maejrep | but as soon as I hit the key, the device freezes :| |
| 08:08.18 | maejrep | don't even see the printk I have at the top of the interrupt handler |
| 08:08.42 | maejrep | probably need to implement workqueue again |
| 08:08.45 | tmzt | all your driver does is request_irq? |
| 08:08.57 | tmzt | what do you do in the handler? |
| 08:09.33 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbf9dd7.pool.einsundeins.de) |
| 08:10.07 | maejrep | it also does gpio_request and gpio_configure |
| 08:10.22 | maejrep | (but it didn't previously and the freezes were still happening) |
| 08:10.44 | maejrep | my handler dumps the gpio regs for in1-11, and then does the i2c reading |
| 08:10.59 | maejrep | I'm pretty sure I'm supposed to move the i2c reading outside of the irq handler |
| 08:11.03 | tmzt | gpio_configure ? |
| 08:11.17 | tmzt | dumps the what? |
| 08:12.02 | tmzt | what happens if you register tsc2003 with you chip id and change the IRQF_TRIGGER_FALLING ? |
| 08:12.18 | tmzt | the upstream version not the vkeyb one |
| 08:13.19 | maejrep | gpio_configure(27, GPIOF_INPUT | IRQF_TRIGGER_FALLING | 0x10000000) |
| 08:13.22 | tmzt | you only need gpio_configure if you plan on changing the value/direction I think |
| 08:13.45 | tmzt | sorry, gpio_request |
| 08:14.04 | tmzt | if you treat it as a irq you should only need request_irq |
| 08:14.10 | maejrep | I didn't know that, and can't find any documentation :( |
| 08:14.24 | maejrep | even if INT_EN is not set for that gpio? |
| 08:14.29 | tmzt | not in Documentation/ ? |
| 08:15.30 | tmzt | Documentation/i2c/writting-clients |
| 08:21.21 | maejrep | Apparently I didn't look hard enough in Documentation/ :( |
| 08:21.29 | maejrep | gpio.txt is informative as well |
| 08:21.33 | maejrep | (for me) |
| 08:28.18 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) |
| 08:30.12 | *** join/#htc-linux daspsycho (n=Tim@HSI-KBW-082-212-005-059.hsi.kabelbw.de) |
| 08:35.07 | tmzt | maejrep: are you using i2c_set_clientdata? |
| 08:35.41 | maejrep | I've just recently added i2c stuff back into it. but I'm planning to, yes |
| 08:40.24 | tmzt | maejrep: what about spin_lock_irqsave ? |
| 08:40.58 | tmzt | looking at tsc2007.c |
| 08:47.19 | *** join/#htc-linux marci (n=chatzill@catv-80-98-42-93.catv.broadband.hu) |
| 08:52.07 | *** join/#htc-linux holycow (n=bite@S01060016b6b53675.vf.shawcable.net) |
| 08:58.21 | maejrep | hmm, something else that's strange is that the trace shows that the gpio int_status bit isn't cleared until after the i2c data is read.. |
| 09:00.56 | maejrep | http://www.privatepaste.com/5aqj1fkpln |
| 09:01.24 | maejrep | but for that to happen, wouldn't that mean the irq handler can't return IRQ_HANDLED until after it's read all the data? |
| 09:01.56 | tmzt | maybe |
| 09:06.14 | tmzt | maejrep: what happens if all your irq handler does is printk and return IRQ_HANDLED ? |
| 09:06.34 | maejrep | same (that's all its been doing) |
| 09:06.43 | tmzt | and doesn't dump the gpios |
| 09:06.45 | maejrep | it'll trigger the first time I boot from wince to linux, but after that nothing |
| 09:06.59 | tmzt | with FALLING? |
| 09:07.01 | maejrep | it does during init, and it dumps it once on the first key press |
| 09:07.10 | maejrep | right (also tried FALLING|RISING) |
| 09:07.20 | tmzt | what are you dumping? |
| 09:08.20 | maejrep | all the GPIO registers from gpio_hw.h (for 1-11) |
| 09:08.39 | maejrep | so: IN, OUT, OE, INT_EN, INT_POS, INT_EDGE, etc |
| 09:08.57 | tmzt | what is that for? |
| 09:09.44 | tmzt | sometimes reads have side-effects and sometimes things aren't readable at all (like write-only) |
| 09:10.20 | tmzt | anyway, does it crash on keypress if you don't dump any registers, just printk("key pressed\n") or something? |
| 09:11.31 | tmzt | not crash, freeze |
| 09:12.33 | maejrep | i think it did previously |
| 09:12.42 | maejrep | the freeze is definitely only when i2c is enabled though |
| 09:13.04 | maejrep | if I just do the registers, it would print fine and return normally, just wouldn't fire a second time |
| 09:24.32 | maejrep | well, it doesn't freeze, but it looks like the gpio is already low |
| 09:32.41 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 09:34.39 | tmzt | hey I need to go, if you have anything for cr2 or anyone else so we can work on this paste it |
| 09:35.40 | maejrep | np, thanks :) |
| 09:36.47 | maejrep | the code looks like ass right now, but it is essentially functional in the sense that it doesn't blow up :) and nonfunctional in the sense that it doesn't work and is unusable :D |
| 09:42.05 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 09:50.55 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 09:51.04 | *** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl) |
| 09:53.38 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 10:01.28 | *** join/#htc-linux joey_973 (n=IceChat7@ip55-83-208-87.adsl2.static.versatel.nl) |
| 10:02.48 | radem205 | hey dzo |
| 10:03.39 | radem205 | I have tried to install the new Radio 1.64.24.34 (or something like that) on my polaris but I get an error message that my phone is not compatible with this Radio ROM :( |
| 10:16.38 | *** join/#htc-linux Evelynn (n=Evelynn@smas.alcad.si) |
| 10:45.23 | *** join/#htc-linux BruteSource (n=brutesou@c-71-59-241-177.hsd1.or.comcast.net) |
| 10:45.49 | BruteSource | Anyone Alive? |
| 10:53.56 | *** join/#htc-linux timebomb (n=tb@e176120077.adsl.alicedsl.de) |
| 10:54.10 | tcccp | #define ALIVE |
| 11:00.02 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
| 11:03.40 | *** join/#htc-linux MethoS (n=clemens@host-091-097-243-030.ewe-ip-backbone.de) |
| 11:06.07 | *** join/#htc-linux blondquirk (n=vovka@ppp85-141-243-127.pppoe.mtu-net.ru) |
| 11:10.55 | BruteSource | Well any progress with Titan? |
| 11:11.06 | *** join/#htc-linux anarsoul (n=Anarchis@213.184.241.199) |
| 11:11.09 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 11:24.09 | *** part/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
| 11:40.57 | *** join/#htc-linux pichurri (n=pichurri@194.230.146.213) |
| 11:42.20 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 11:47.28 | *** join/#htc-linux exco (n=exco@e181117142.adsl.alicedsl.de) |
| 11:50.21 | *** join/#htc-linux buster (n=buster@lostmind.org) |
| 11:56.26 | *** join/#htc-linux woodyPL (i=woody@gateway/shell/blinkenshell.org/x-39159732f3a0581a) |
| 11:59.22 | *** join/#htc-linux metter (n=metter@72-187.62-81.cust.bluewin.ch) |
| 12:07.05 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 12:07.30 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 12:16.22 | *** join/#htc-linux nunzi00 (n=nunzi@cm79009.red91-117.mundo-r.com) |
| 12:17.12 | *** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com) |
| 12:18.23 | *** join/#htc-linux LunohoD (n=alex@e180078011.adsl.alicedsl.de) |
| 12:19.15 | *** part/#htc-linux LunohoD (n=alex@e180078011.adsl.alicedsl.de) |
| 12:20.35 | *** join/#htc-linux dimitris (n=dimitris@cpe-128964.ip.primehome.com) |
| 12:21.49 | *** part/#htc-linux dimitris (n=dimitris@cpe-128964.ip.primehome.com) |
| 12:24.10 | *** join/#htc-linux metter_ (n=metter@72-187.62-81.cust.bluewin.ch) |
| 12:27.37 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
| 12:29.49 | *** join/#htc-linux metter_ (n=metter@182-88.1-85.cust.bluewin.ch) |
| 12:30.41 | *** join/#htc-linux LunohoD (n=alex@e180078011.adsl.alicedsl.de) |
| 12:35.04 | *** join/#htc-linux konsta (n=asds@host81-154-247-76.range81-154.btcentralplus.com) |
| 12:36.43 | woodyPL | hello |
| 12:36.49 | woodyPL | could anybody here help me to |
| 12:36.59 | woodyPL | make framebuffer driver work on hp ipaq 514? |
| 12:47.21 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c259.pool.einsundeins.de) |
| 12:56.01 | *** join/#htc-linux br1ck (n=br1ck@xdslci212.osnanet.de) |
| 13:19.11 | *** part/#htc-linux nunzi00 (n=nunzi@cm79009.red91-117.mundo-r.com) |
| 13:32.54 | *** join/#htc-linux Loki657 (n=Loki657@82.147.51.146) |
| 13:32.56 | Loki657 | hi all |
| 13:39.20 | Loki657 | Hows it going? |
| 13:41.58 | *** join/#htc-linux _4nakin (n=Tuan@115.76.134.231) |
| 13:43.18 | _4nakin | anybody know how to port Android to Himalaya ? |
| 13:44.47 | Loki657 | I dont think many have been working on it |
| 13:45.03 | _4nakin | i have try |
| 13:45.15 | _4nakin | but it stuck at "jumping to kernel" |
| 13:47.30 | woodyPL | hi |
| 13:47.49 | woodyPL | I'll try to ask my question again |
| 13:48.03 | woodyPL | could anybody help me with getting lcd |
| 13:48.08 | woodyPL | of hp ipaq 514 to work? |
| 13:48.22 | woodyPL | it's very similar to htc wizard |
| 13:48.31 | woodyPL | and linwizard even boots fine |
| 13:48.36 | woodyPL | but fb parameters are incorrect |
| 13:50.02 | Loki657 | after typing /init.android, I get lots of "cannot find /system/bin/....." messsages |
| 13:50.03 | Loki657 | any ideas? |
| 13:53.02 | Balsat | Sure you got the images mounted? |
| 13:54.31 | Loki657 | well, I would think so? |
| 13:54.38 | Loki657 | i downloaded the newest zImage from Jobo |
| 13:55.13 | Balsat | Did i work before the new Zimage? |
| 13:55.21 | Balsat | it |
| 13:55.52 | Loki657 | Havent tried unfortunately |
| 13:56.15 | Balsat | And you have put the images under /tmp ? |
| 13:56.19 | Loki657 | yup |
| 13:56.32 | Loki657 | Do I have to edit the default.txt in any way when using the newest jobo-image? |
| 13:56.52 | Balsat | Yes |
| 13:57.11 | Loki657 | I just downloaded the newest one and checked the readme.. didnt mention anything |
| 14:00.32 | Loki657 | other than that, I just followed the guide on the Wiki and replaced the initrd.droid.cpio with the one LordKiwi made for the TouchPro |
| 14:01.23 | Balsat | Download http://www.wuala.com/Linux+and+Android+on+HTC+Diamond/Android+1.0/tmp?lang=en and try again! |
| 14:01.58 | Loki657 | ah, and just replace those files with the ones I dowloaded from the wiki? |
| 14:02.47 | Balsat | Yes, but be sure the default.txt is pointing at the right zImage |
| 14:03.15 | Loki657 | yeah.. but should I keep the initrd.droid.cpio.gz (by LordWiki) since im on a Touch Pro? |
| 14:03.37 | Balsat | Yes you can keep that file |
| 14:05.15 | Loki657 | I still need the system.ext2.img and userdata.ext2.img, right? |
| 14:07.48 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 14:08.28 | Balsat | Yes, and remember to put them under /tmp on the internal storage |
| 14:09.05 | Loki657 | yeah, I have.. I still get the samme errors though :S |
| 14:09.13 | Loki657 | really weird |
| 14:09.44 | Balsat | What does your default.txt say? |
| 14:09.51 | Loki657 | set mtype 1910 |
| 14:09.52 | Loki657 | set kernel zImage-clean-jobo |
| 14:09.52 | Loki657 | set initrd initrd.droid.cpio.gz |
| 14:09.52 | Loki657 | set ramsize 0x6000000 |
| 14:09.52 | Loki657 | set ramaddr 0x10000000 |
| 14:09.52 | Loki657 | set cmdline "mem=64M msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f" |
| 14:09.54 | Loki657 | boot |
| 14:10.06 | Loki657 | im running it on a Raph100 |
| 14:11.17 | Balsat | try to enter "mount" on the phone |
| 14:11.31 | Loki657 | before /init.android ? |
| 14:11.50 | Balsat | yes, just to check if the system mounts |
| 14:12.02 | Loki657 | ok.. 1 sec |
| 14:13.09 | Loki657 | mount: no /proc/mounts |
| 14:13.24 | *** join/#htc-linux MethoS (n=clemens@host-091-097-240-171.ewe-ip-backbone.de) |
| 14:13.38 | Balsat | hmm strange |
| 14:13.43 | Loki657 | yeah |
| 14:14.09 | woodyPL | sorry for kicking in |
| 14:14.11 | woodyPL | it seems |
| 14:14.26 | woodyPL | <PROTECTED> |
| 14:14.27 | Loki657 | I see some errors above that seems interestin though |
| 14:14.28 | woodyPL | <PROTECTED> |
| 14:14.31 | woodyPL | hasn't been mounted |
| 14:14.34 | woodyPL | itself |
| 14:14.49 | Loki657 | mount: mouinting /mmc/tmp/cache.ext2.img on /cache failed: No such file or directory |
| 14:14.55 | Loki657 | mounting* |
| 14:15.08 | Loki657 | mounting /mmc/tmp/system.ext2.img on /system failed: o such file or directory |
| 14:15.23 | Loki657 | same wiuth userdata.ext2.img |
| 14:15.30 | Balsat | do you got mmcblkp* in /dev |
| 14:16.12 | Loki657 | Not sure, really |
| 14:16.31 | Balsat | "ls /dev/mmcblk*" |
| 14:17.41 | Loki657 | cant see the * on the visual keyboard.. |
| 14:18.03 | Balsat | can't u ssh to your phone |
| 14:18.29 | Loki657 | as of yet, I have only copied the files to my internal storage in a folder called "tmp" |
| 14:18.37 | Loki657 | trying to run, and here I am.. he |
| 14:18.47 | Loki657 | on a Windows system atm.. |
| 14:18.53 | Balsat | hmm ok |
| 14:19.48 | *** join/#htc-linux _7lima (n=7lima@88-134-28-199-dynip.superkabel.de) |
| 14:20.42 | Loki657 | its weird though.. it said "no such file or directory".. doing a simple ls shows that cache, system and /data is there |
| 14:21.03 | Loki657 | so the problem must be on the /mmc/tmp/ side.. |
| 14:21.43 | Loki657 | ah, I think I see the probelm |
| 14:21.45 | Loki657 | problem* |
| 14:21.51 | Balsat | yes but system.img and data.img dont get mountet |
| 14:22.11 | Loki657 | ls /mmc shows the content of my SD-card, not my internal storage |
| 14:22.45 | Loki657 | so when it tried to find /mmc/tmp/cache.ext2.img , it wont find it as i created the tmp folder on my internal storage |
| 14:22.47 | Balsat | Yes, and you should put the tmp on the root of your SDcard |
| 14:23.00 | Loki657 | ah, That probably explains it then *doh* |
| 14:23.15 | Loki657 | sorry for wasting your time (i feel stupid now) |
| 14:23.25 | Balsat | no prob |
| 14:23.38 | Loki657 | had a Diamond earlier this week and everything worked fine, but I didnt gete that I should be placing the files on the SD card on the TP |
| 14:23.49 | Loki657 | speaking of which.. what an impressive progression these last few weeks |
| 14:24.22 | Loki657 | if the status on what works and what doesnt on the wiki is accurate, its pretty much just calls thats missing for Android to be pretty much useable (except the hardware keyboard on the TP) |
| 14:27.01 | *** part/#htc-linux Balsat (n=kll@87.72.13.87) |
| 14:33.56 | *** join/#htc-linux Loki657 (n=Loki657@82.147.51.146) |
| 14:48.19 | *** join/#htc-linux kami83 (n=kami@pD955BBCF.dip.t-dialin.net) |
| 14:51.01 | *** join/#htc-linux balsat (n=kra@87.72.13.87) |
| 14:52.25 | kami83 | hi can anyone tell me how i can change the rotation of android? i have got a HTC Diamond and trying to use jobos version |
| 14:57.00 | Loki657 | press the power button |
| 15:11.16 | *** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
| 15:14.54 | kami83 | thx works but it wont accept my sim pin? |
| 15:17.56 | Loki657 | hmm, weird.. |
| 15:18.01 | Loki657 | just deactivate the sim pi |
| 15:18.09 | Loki657 | brb |
| 15:19.26 | *** join/#htc-linux addman3333 (n=skool@cpe-67-9-134-92.austin.res.rr.com) |
| 15:21.29 | *** join/#htc-linux Loki657 (n=Loki657@82.147.51.146) |
| 15:21.39 | *** join/#htc-linux pH5 (n=ph5@p5485D104.dip.t-dialin.net) |
| 15:23.23 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
| 15:24.49 | *** join/#htc-linux [1]Loki657 (n=Loki657@82.147.51.146) |
| 15:25.29 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 15:25.37 | *** join/#htc-linux Iumentum2 (n=Iumenrum@3908ds1-ynoe.0.fullrate.dk) |
| 15:25.49 | *** join/#htc-linux timebomb (n=tb@e176120077.adsl.alicedsl.de) |
| 15:26.16 | kami83 | okay and is there anywhere else a new kernel or system then on wuala? |
| 15:26.23 | Rogro82 | hiya all |
| 15:26.54 | dcordes_ | hi Rogro82, others |
| 15:27.30 | Rogro82 | any luck on getting the new smd code to work? |
| 15:29.05 | dcordes_ | in htc-vogue ? |
| 15:29.20 | Rogro82 | yes |
| 15:29.48 | dcordes_ | I never tried new smd code in there |
| 15:30.08 | Rogro82 | u still using the kaiser-smd? |
| 15:30.20 | dcordes_ | no I'm using what's in htc-vogue. vogue-smd |
| 15:30.32 | dcordes_ | but it's a bit wonky |
| 15:31.06 | dcordes_ | Mullins will try rebasing to 2.6.27 |
| 15:31.10 | Rogro82 | does it do anything yet? i thought it wasnt working at all ( smd0/1 ) |
| 15:31.43 | dcordes_ | yes you can read and write. but it crashes the AMSS (depends on radio rom, some crash, some stay up) and the in/out isn't stable |
| 15:33.11 | Rogro82 | ill try to build a kernel for the polaris tonight based on the latest commit to see if its the same on our device |
| 15:35.31 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
| 15:36.28 | *** join/#htc-linux Loki657 (n=Loki657@82.147.51.146) |
| 15:39.15 | Rogro82 | dcordes: What radio rom version are you using? |
| 15:42.13 | dcordes_ | http://forum.xda-developers.com/showpost.php?p=3148065&postcount=1926 |
| 15:42.19 | dcordes_ | 1.65.24.36 |
| 15:44.24 | Rogro82 | using the non-pio with this radio finally gave you a stable sd card? Or still dma problems? |
| 15:45.21 | dcordes_ | yep, no dma problems |
| 15:45.47 | Rogro82 | nice, i just checked and im running 1.59.44.02 |
| 15:46.07 | dcordes_ | I think with your first approaches of polaris/kaiser > htc-vogue it would have worked too with the 1.6 radio |
| 15:46.17 | dcordes_ | but I was using 1.7 one before |
| 15:47.23 | *** join/#htc-linux Mullins (n=bw@89.204.224.37) |
| 15:47.30 | Rogro82 | too bad radio versions are causing unstable parts... hard to find out if things are working ok if one radio works on some parts and others on other parts :S |
| 15:48.24 | dcordes_ | Rogro82: yea. I don't understand how it influences SD |
| 15:48.41 | dcordes_ | maybe some differences in clock stuff? |
| 15:49.24 | dcordes_ | Mullins: hi |
| 15:49.29 | Mullins | dcordes: hi |
| 15:49.43 | Rogro82 | hi |
| 15:50.33 | Mullins | dcordes: I was thinking the problem is not the ts not being read but the frame displaying only one frame. is there someway of getting Xfbdev to run something on startup to verify the fb is refreshing |
| 15:51.35 | dcordes_ | you can always use DISPLAY=:0 gpe-something |
| 15:52.16 | dcordes_ | but if msm_fb works, Xfbdev should always give you the checkered background and the cursor pixmap, which should be able to be moved |
| 15:52.46 | dcordes_ | wait a minute.. there were some images where the kaiser ts didn't work at all with X |
| 15:53.07 | dcordes_ | I noticed that but reading the output from Xfbdev and it said it doesn't recognize the events |
| 15:53.12 | dcordes_ | are you using the sato image? |
| 15:53.16 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 15:53.18 | Mullins | I also tried the most recent Angstrom tar.gz |
| 15:53.40 | Mullins | dcordes: Link me one you know works for definite |
| 15:54.59 | dcordes_ | http://linuxtogo.org/~lgorris/builds/tgreer-special-sd-rootfs.tar.gz this is certainly not the best image but I did some tests there and it worked |
| 15:55.02 | dcordes_ | ts |
| 15:55.41 | Rogro82 | k i gotta go for a dinner... ill be back later and will try to get a new image up and running for the polaris. |
| 15:55.52 | dcordes_ | cya rogro |
| 15:55.56 | Mullins | cya later Rogro |
| 15:55.59 | Rogro82 | bye bye |
| 15:57.40 | dcordes_ | I think it's an x11-image |
| 16:00.36 | Mullins | dcordes: Are you still concerned with the status of Android 0.8, for the wiki page? Or will I just leave 1.0 status on it? |
| 16:00.49 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 16:01.20 | Mullins | dcordes: Are you still concerned with the status of Android 0.8, for the wiki page? Or will I just leave 1.0 status on it? |
| 16:14.42 | *** join/#htc-linux LunohoD_ (n=alex@e180075011.adsl.alicedsl.de) |
| 16:16.04 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 16:30.45 | *** join/#htc-linux woodson (n=CDP@c-76-101-90-149.hsd1.fl.comcast.net) |
| 16:35.08 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B037F75.dip.t-dialin.net) |
| 16:39.08 | *** join/#htc-linux imfloflo (i=5a3c0b49@gateway/web/ajax/mibbit.com/x-603600f0a8bac41e) |
| 16:42.49 | dcordes | Mullins: which wiki page? |
| 16:43.25 | Mullins | dcordes: The new one based on the Raphael one |
| 16:43.36 | dcordes | got a link? |
| 16:43.46 | Mullins | http://wiki.xda-developers.com/index.php?pagename=SandBoxBW |
| 16:43.51 | Mullins | WIP |
| 16:44.31 | dcordes | jsut leave obsolete info out I guess |
| 16:45.50 | *** join/#htc-linux buster`- (n=buster@lostmind.org) |
| 16:46.31 | dcordes | tell me when you have your outline ready. I will add info on angstrom/OE |
| 16:46.38 | dcordes | and framework |
| 16:46.41 | Mullins | yeah |
| 16:50.06 | *** join/#htc-linux jeanseb (n=jeanseb@gazypan.dyndns.org) |
| 16:55.54 | dcordes | j0b0: http://members.home.nl/j0b0/haret18.exe did you remove the max initrd size? |
| 17:00.50 | dcordes | Mullins: do you know how to disable PIO in current git rev? SD doesn't work for me |
| 17:01.00 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-44c17b344bcd611a) |
| 17:01.33 | Mullins | dcordes: no sorry |
| 17:02.11 | dcordes | does it work for you with PIO ? |
| 17:02.30 | Mullins | dcordes: I only use SD |
| 17:02.55 | dcordes | you use the older git revision? |
| 17:03.08 | Mullins | dcordes: no, the most recent |
| 17:03.26 | Mullins | dcordes: what do you mean exactly doesn't work? |
| 17:03.33 | dcordes | I can't boot |
| 17:03.46 | dcordes | I have the rootfs on SD card |
| 17:04.12 | Mullins | dcordes: thats the only method I use |
| 17:04.49 | dcordes | and it works with the unmodified most recent git version? |
| 17:05.16 | Mullins | dcordes: yes. what happens when you try? |
| 17:05.29 | dcordes | freeze after freeing init memory |
| 17:05.32 | *** join/#htc-linux t3chi3 (n=blarg@36.67.33.65.cfl.res.rr.com) |
| 17:05.37 | dcordes | I will rebuild and retry |
| 17:05.46 | Mullins | dcordes: did you see the default.txt Dzo added to GIT |
| 17:06.09 | dcordes | yes |
| 17:06.21 | dcordes | and I tried addign all the cmdline params specific to sd |
| 17:07.04 | Mullins | dcordes: want to try my current zImage here to be sure? |
| 17:07.07 | dcordes | I will try with the exact default.txt in git |
| 17:07.11 | dcordes | ok |
| 17:07.22 | Mullins | dcordes: the most recent git plus some work, but boots from SD |
| 17:08.38 | *** join/#htc-linux rmoravcik1 (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 17:09.16 | dcordes | maybe it's because I use the kaiser mtype |
| 17:09.28 | dcordes | I'll boot with the kaiser-default.txt now |
| 17:09.50 | Mullins | I have sent the zImage to your email. will send the default.txt |
| 17:11.05 | dcordes | ok thanks |
| 17:11.41 | dcordes | I just booted with the git default.txt with initrd line removed and root=/dev/mmcblk0p2 rootedlay=10 added to cmdline |
| 17:11.51 | dcordes | I get the mmc0: command timeout messages |
| 17:12.35 | dcordes | http://forum.xda-developers.com/showpost.php?p=3148065&postcount=1926 like this |
| 17:12.45 | Mullins | mine -> http://paste-it.net/public/h34a828/ |
| 17:15.48 | dcordes | same freeze on freeing init memory after ext2 / is mounted |
| 17:15.52 | dcordes | with your kern |
| 17:16.32 | dcordes | do you get the command timeout messages on boot? |
| 17:17.31 | Mullins | dcordes: I am using the 1.65.24.36 radio. are you? |
| 17:17.42 | dcordes | yes |
| 17:18.01 | dcordes | and with same radio, the non-PIO version works for me |
| 17:18.09 | Mullins | dcordes: how do you log the bootup messages to review them? |
| 17:18.52 | dcordes | I see them on display during bootup |
| 17:18.58 | Mullins | ok, I will watch |
| 17:20.38 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-ff678e87ec55b37e) |
| 17:24.20 | dcordes | Mullins: can you try adding an ext2/3 partition to your card and boot with rootfs on it? |
| 17:26.48 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-b1dd0b3342497e06) |
| 17:27.09 | Mullins | dcordes: I could yeah. Where do I start? |
| 17:28.02 | *** part/#htc-linux exco (n=exco@e181117142.adsl.alicedsl.de) |
| 17:28.10 | *** join/#htc-linux exco (n=exco@e181117142.adsl.alicedsl.de) |
| 17:31.30 | Mullins | dcordes: I have no linux PC that can access the microSD dcordes. I need that for start |
| 17:33.46 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-75613e1f8f70e8f9) |
| 17:33.56 | exco | Mullins: you can use e.g. an Ubuntu LiveCD |
| 17:34.28 | *** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231) |
| 17:35.00 | Mullins | exco: I still need a microSD card reader on the machine |
| 17:35.27 | dcordes | ok when you have one, the ubuntu livecds are good |
| 17:35.34 | exco | that'd be a good idea I suppose |
| 17:35.47 | dcordes | dzo: how to disable PIO mode in current git revision? |
| 17:36.05 | exco | Mullins where are you from? |
| 17:36.28 | Mullins | exco: Ireland |
| 17:38.05 | Mullins | dcordes: Do you not have a FAT32 partition on your card to at least try that? or have you? |
| 17:40.42 | *** join/#htc-linux WyrM (n=wyrm@189.13.215.181) |
| 17:43.14 | *** join/#htc-linux Tonny (n=chatzill@set25-1-88-166-169-49.fbx.proxad.net) |
| 17:43.15 | NetRipper | ahyone with a diam100/raph800/diam800 on? |
| 17:43.49 | Balsat | diam100 here |
| 17:44.15 | dcordes | Mullins: I always have a fat32 and an ext2 partition |
| 17:44.19 | exco | I just installed wm5torage on my mobile - and gparted does recognize the disk - so possibly you could partition your SD card in your mobile using wm5torage |
| 17:44.20 | dcordes | but didn't try the android stuff |
| 17:44.56 | NetRipper | Balsat, can you try this kernel for me? http://www.netripper.com/raphael/zImage-pcom-20090111-00 |
| 17:45.01 | NetRipper | Balsat, use MTYPE 1805 (diamond) |
| 17:45.17 | Balsat | ok, i'l try it out |
| 17:45.21 | NetRipper | thx |
| 17:48.17 | Balsat | Wow the phone was shaking on boot up |
| 17:48.28 | Balsat | boots up fine |
| 17:48.37 | NetRipper | okay great |
| 17:48.40 | NetRipper | means pcom is woring |
| 17:48.49 | NetRipper | 2 short vibrations |
| 17:48.55 | Balsat | yep... nice |
| 17:49.07 | NetRipper | think im going to keep that in as funny welcome |
| 17:49.07 | NetRipper | ;) |
| 17:49.22 | konsta | pcom? |
| 17:49.32 | NetRipper | proc_comm |
| 17:49.48 | NetRipper | used to communicate with the arm9 side |
| 17:49.51 | konsta | ah |
| 17:50.05 | Balsat | Can you make it vibrate for 5-6 min... my girlfriend need that |
| 17:50.10 | NetRipper | Balsat, lol |
| 17:50.35 | NetRipper | guess that says something about you as well Balsat |
| 17:50.36 | NetRipper | ;) |
| 17:50.45 | zycho | :> |
| 17:51.00 | Balsat | I guess so... *lol* |
| 17:52.05 | NetRipper | dinner time, bbl :) |
| 17:52.18 | Balsat | bon appetit |
| 17:52.43 | tekkdrone | NetRipper: btw that image i tried the other day on raph500 vibrated as well |
| 17:52.49 | tekkdrone | fwiw |
| 18:00.38 | *** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com) |
| 18:00.50 | *** join/#htc-linux rakeem (n=rak@n219078211036.netvigator.com) |
| 18:05.59 | zycho | http://www.netripper.com/raphael/zImage-pcom-20090111-00 works for my diam300 too |
| 18:19.58 | *** join/#htc-linux pichurri (n=pichurri@194.230.146.254) |
| 18:23.25 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
| 18:29.51 | *** join/#htc-linux [1]Loki657 (n=Loki657@82.147.51.146) |
| 18:32.01 | *** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it) |
| 18:49.29 | *** join/#htc-linux Gluck (n=Gluck@av9592.comex.ru) |
| 18:55.43 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c259.pool.einsundeins.de) |
| 18:55.50 | *** part/#htc-linux WyrM (n=wyrm@189.13.215.181) |
| 18:58.13 | toer | NetRipper: planning to commit proc com stuff today? |
| 19:10.52 | *** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl) |
| 19:24.34 | *** join/#htc-linux stefan_schmidt_ (n=stefan@p5B03747C.dip.t-dialin.net) |
| 19:24.52 | *** join/#htc-linux piusvelte (n=irchon@71.175.8.29) |
| 19:29.05 | NetRipper | toer, yep, in a minute |
| 19:29.20 | NetRipper | zycho, good to hear, didnt even know there was a diam300, what brand is it? |
| 19:29.23 | rolk | dream_kill: did you find anything on the MSM_CLK_CTL_BASE register (defined as address 0xE000A000)? For example: the 0xE000A0A8 register is supposed to be related to the SD card interface on Polaris. It is being written to by the ARM11. So apparently this part of the clocks is under control of the ARM11, not the radio ARM9. |
| 19:29.24 | NetRipper | and gsm/cdma? |
| 19:29.53 | NetRipper | tekkdrone, good to hear :) |
| 19:29.54 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 19:29.55 | zycho | its o2 from DE |
| 19:30.07 | NetRipper | ah, ok, any different specs zycho ? |
| 19:30.22 | zycho | dont think so.. gsm device |
| 19:33.03 | dcordes | Mullins: does the dzo android work for you? |
| 19:41.39 | dcordes | Mullins: it doesn't work for me. something must be wrong with pio |
| 19:42.36 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
| 19:43.15 | NetRipper | dcordes, how do you set multiple authors for a commit? comma-seperate the authors? |
| 19:44.14 | NetRipper | --author "name1 <email>, name2 <email>" ? |
| 19:44.14 | dcordes | I guess that's an option or make seperate commits |
| 19:44.20 | *** join/#htc-linux pH5 (n=ph5@p5485BD0C.dip.t-dialin.net) |
| 19:44.21 | NetRipper | well ive seen you commit for multiple authors before |
| 19:44.21 | NetRipper | ;) |
| 19:44.27 | dcordes | did it that way with the initial htc-msm-2.6.25 commits |
| 19:44.46 | NetRipper | ok |
| 19:46.15 | NetRipper | hm |
| 19:46.20 | NetRipper | multiple authors dont work |
| 19:46.34 | NetRipper | when comma seperated, it only takes the first one |
| 19:47.01 | dcordes | then use a diffeernt seperateohttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=ff547942054275b9ec4c282eafe687b39a0073a4 |
| 19:47.08 | dcordes | seperator |
| 19:47.27 | NetRipper | yea |
| 19:47.54 | NetRipper | lol even then it stops after the first e-mail address |
| 19:47.57 | dcordes | you could try "author1 <email1> and author2 <email2>" |
| 19:48.15 | NetRipper | yes i tried 'and' but it removes everything after the first email address |
| 19:48.44 | dcordes | "author1 and author2 <email1 and email2>" := ? |
| 19:49.29 | NetRipper | that works |
| 19:49.47 | NetRipper | i see it's already a feature request in git |
| 19:50.08 | dcordes | freesmartphone.org always use --author "Dr. Git" |
| 19:50.27 | NetRipper | why is that? |
| 19:50.31 | dcordes | no clue |
| 19:51.37 | Loki657 | hi all |
| 19:51.39 | Loki657 | hows it going? |
| 19:52.18 | NetRipper | be more specific :p |
| 19:53.06 | Loki657 | lol.. as in, personally :) |
| 19:53.06 | dcordes | did you discuss a rebase? |
| 19:54.13 | NetRipper | dcordes, rebase? |
| 19:54.22 | NetRipper | dcordes, the 2.6.27 tree? |
| 19:54.28 | dcordes | raphael/diamond speicifc code > 2.6.27 |
| 19:54.40 | dcordes | http://android.git.kernel.org/?p=kernel/common.git;a=shortlog;h=refs/heads/android-2.6.27 this branch |
| 19:55.19 | Loki657 | Are we far off getting the qwerty keyboard working? |
| 19:55.22 | Loki657 | on the raph |
| 19:55.43 | NetRipper | Loki657, not too far i think |
| 19:55.48 | dcordes | .25 seems stale in the google repos |
| 19:55.52 | Loki657 | cool |
| 19:55.59 | NetRipper | dcordes, yes it is.. we should move to 2.6.27 eventually |
| 19:56.00 | Loki657 | and what about calls? |
| 19:56.06 | dcordes | beyond what we based on, they only added usb gadget |
| 19:56.13 | NetRipper | Loki657, that's already possible, just no speaker/mic |
| 19:56.16 | NetRipper | (yet) |
| 19:56.24 | Loki657 | ah right.. thats what I meant.. heh |
| 19:58.29 | dcordes | NetRipper: htc-vogue is likely to rebase to the 2.6.27 goog code too. we might get a unified branch with all the devices |
| 20:00.22 | NetRipper | dcordes, ah would be a good idea |
| 20:00.27 | NetRipper | might save some work too |
| 20:01.54 | dcordes | let's see if we can get both working seperately first |
| 20:02.42 | NetRipper | where do the vogue programmers reside anyway? also on irc somewhere? |
| 20:03.03 | NetRipper | or is it mostly just dzo? |
| 20:04.13 | Loki657 | will the vga resolution cause troubles? |
| 20:05.50 | NetRipper | what kind of troubles? |
| 20:06.58 | Loki657 | thinking more of Android in general. Wondering how 3rd party apps will turn out and such |
| 20:07.24 | NetRipper | im not sure what resolution the G1 has |
| 20:07.37 | NetRipper | but so far android looks fine |
| 20:08.01 | NetRipper | and java layout managers are not pixel based (not sure which layout managers android implements though) |
| 20:08.01 | Loki657 | the G1 has 340x280 or something |
| 20:08.38 | dcordes | NetRipper: looks like it is mostly dzo |
| 20:08.41 | Loki657 | I have the G1 lying here, and you can see for instance that the built in Android wallpapers doesnt fit properly |
| 20:09.08 | dcordes | Loki657: do you have the developer g1? |
| 20:09.11 | NetRipper | Loki657, ok but wallpapers can be replaced.. i'd worry more about custom application in the way of layouting.. |
| 20:09.12 | Loki657 | yeah |
| 20:09.19 | Loki657 | NetRipper, thats my point exactly.. |
| 20:09.35 | Loki657 | and dccordes, I have the ADP1 right here |
| 20:09.39 | dcordes | Loki657: would you like to test an alternate phone api? |
| 20:09.46 | dcordes | what's ADP1 ? |
| 20:09.56 | NetRipper | Loki657, but java programmers are encouraged to use layout managers when desinging forms/panels... which are pixel independent.. |
| 20:10.21 | NetRipper | of course some java programmers use pixel-based placement anyway, but ok ;) |
| 20:10.25 | Loki657 | Android Development Phone 1 (got it from Google) |
| 20:11.31 | Loki657 | What would running an alternate phone api mean? Im kinda using it as my main phone untill the Raph100 port is fully working ^^ |
| 20:11.58 | dcordes | you need to use a different rootfs |
| 20:12.06 | dcordes | how do you setup the bootloader? |
| 20:12.23 | dcordes | any documentation on that available? |
| 20:12.43 | Loki657 | I think i read something on XDA actually |
| 20:13.11 | dcordes | is there no vendor documentation? |
| 20:13.42 | Loki657 | but I just got the phone so havent had the time to get to know how to fool around with it |
| 20:14.27 | Loki657 | Didnt get much with the phone. Just a quickstart guide |
| 20:16.07 | dcordes | NetRipper: proc_comm_wince is for the wince based AMSS versions? |
| 20:16.07 | NetRipper | dcordes, yes |
| 20:16.07 | dcordes | s/based/ / |
| 20:17.53 | dcordes | <PROTECTED> |
| 20:17.59 | dcordes | did you mess around with that? |
| 20:18.42 | NetRipper | dcordes, no not yet |
| 20:19.06 | NetRipper | dcordes, it's probably similar to vogue's though |
| 20:19.37 | dcordes | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/AudioPara.c;h=4dd6c4f65c53dd4dd182782fdd0afa67b8ae1a24;hb=refs/heads/htc-vogue |
| 20:19.45 | dcordes | we need to add that for raph/diam |
| 20:19.57 | NetRipper | yes, liek that |
| 20:20.00 | NetRipper | like |
| 20:21.07 | dcordes | what's the 0x19 in the above line? |
| 20:21.17 | NetRipper | the command |
| 20:21.18 | dcordes | wince normal state? |
| 20:21.41 | NetRipper | proc_comm(PCOM_SET_AUDIO_PATH, parm1, parm2) |
| 20:22.34 | NetRipper | on wiki you can see the ioctl equivalent, they're not 1 on 1 |
| 20:24.39 | NetRipper | dcordes, can you change the topic in here? |
| 20:28.24 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
| 20:29.38 | *** join/#htc-linux ali12341 (n=al@robotfuzz.co.uk) |
| 20:29.45 | dcordes | NetRipper: I don't know |
| 20:30.11 | *** join/#htc-linux cr2 (n=cr2@ip-77-25-49-128.web.vodafone.de) |
| 20:30.29 | *** join/#htc-linux ali12341 (n=al@robotfuzz.co.uk) |
| 20:30.46 | *** part/#htc-linux ali12341 (n=al@robotfuzz.co.uk) |
| 20:30.56 | dcordes | cr2: vf'D ? |
| 20:31.59 | cr2 | dcordes flatrate is good for year health |
| 20:32.28 | cr2 | but windows is certainly a piece of shit ;) |
| 20:32.55 | dcordes | I'll be stuck with it for the next week |
| 20:33.18 | cr2 | my usb hdd is for amd64 |
| 20:33.26 | cr2 | so it does not work |
| 20:34.06 | cr2 | i´m installing cygwin |
| 20:34.24 | cr2 | dowloaded 400MB already |
| 20:34.28 | NetRipper | since when is a hdd specific to cpu architecture? |
| 20:34.28 | NetRipper | :) |
| 20:34.52 | Loki657 | lol, was thinking the same thing |
| 20:34.58 | cr2 | NetRipper: the suse installed there |
| 20:35.09 | cr2 | for amd64 |
| 20:35.34 | cr2 | this one is the only x86 notebook/compuetr i have |
| 20:36.18 | NetRipper | cr2, so you mean your hdd actually works, but you just have amd64 suse installed on it |
| 20:36.25 | cr2 | but 300KB/s in the middle of nowhere is not bad |
| 20:36.36 | NetRipper | which you dont want to format ;) |
| 20:36.36 | cr2 | yes |
| 20:36.40 | NetRipper | :P |
| 20:37.07 | cr2 | i need to install a x86 kernel/initrd in the grub menu |
| 20:37.23 | NetRipper | j0b0, are you about? |
| 20:37.51 | cr2 | i'be seen that maejrep[w] worked on vreg |
| 20:38.34 | cr2 | maejrep[w]: the LSB for i2c means read/write |
| 20:39.17 | cr2 | hehe, now i may try edit the wiki |
| 20:40.29 | NetRipper | :p |
| 20:40.34 | zycho | http://www.bookofjesus.org/images/w1cws8pcx3hbf47ldc4.jpg |
| 20:40.36 | zycho | loool |
| 20:40.54 | tmzt | woodyPL: hey, if your still here we can dump those fb settings but you need to be able to build a kernel |
| 20:42.11 | cr2 | tmzt: the gpios are not controlled via proc_comm on non-g1 phones |
| 20:42.46 | tmzt | ah |
| 20:43.35 | tmzt | I think that was for camera/flashlight trying to make the flashlight go to full brightness |
| 20:44.40 | cr2 | flashlight gpio is known |
| 20:46.19 | woodyPL | tmzt: hi |
| 20:46.25 | woodyPL | thanks for responding |
| 20:46.29 | woodyPL | I've already dumped the values |
| 20:46.35 | woodyPL | have been messing with them since yesterday |
| 20:46.43 | tmzt | cool |
| 20:47.07 | cr2 | tmzt: we can control all gpios including the arm9 area, which androids don't want to disclose |
| 20:47.08 | tmzt | so it did work some with the linwizard kernel, it wasn't just blank? |
| 20:47.11 | woodyPL | it turned out that when you dump the registers not to a filwe |
| 20:47.19 | woodyPL | endianness is not mixed |
| 20:47.30 | woodyPL | after messing with the parameters |
| 20:47.35 | woodyPL | it looks like this |
| 20:47.41 | woodyPL | http://www.gigasik.pl/lcd_sync.avi |
| 20:48.06 | tmzt | there is a script somewhere to dump those, I'll see if I can find the name of it |
| 20:48.19 | woodyPL | ok |
| 20:48.51 | NetRipper | cr2, it was about the flashlight having a 'extra bright' setting.. which isn't controlled via gpios |
| 20:49.03 | tmzt | cr2: any idea why the kbd irq is only firing once and sometimes pressing a key is causing the kernel to freeze? |
| 20:49.26 | woodyPL | tmzt: this was necessary to amke it at least display some text for a while |
| 20:49.27 | NetRipper | cr2, when you make a picture with the camera app when flashlight is on, it momentarily increases in brightness |
| 20:49.28 | woodyPL | + OMAP_LCDC_INV_VSYNC | |
| 20:49.28 | woodyPL | + OMAP_LCDC_INV_OUTPUT_EN | |
| 20:49.31 | cr2 | which key ? |
| 20:49.44 | woodyPL | and changing the resoltuion of lcd_wiz3 in lcd_htcwizard.c |
| 20:49.46 | woodyPL | to 176x220 |
| 20:49.50 | tmzt | I think it was any hw key (except gpio_keys) |
| 20:49.51 | cr2 | hmm, i've forgot my xda-dev password ;) |
| 20:50.06 | NetRipper | mumbles keepass ;) |
| 20:50.07 | tmzt | woodyPL: you also need fp and bp and two others I can't think of |
| 20:50.24 | cr2 | NetRipper: it may be some vreg |
| 20:50.36 | cr2 | providing higher voltage |
| 20:50.41 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 20:50.46 | woodyPL | yup |
| 20:51.02 | NetRipper | cr2, what i see when i watch gpios is that it turns off the flashlight gpio, then makes the flash go brigther, and after picture is taken, the gpio is activated again fro normal brightness |
| 20:51.31 | woodyPL | tmzt: I think I know hsw,hfp,hbp,vsw,vfp,vbp from the dump |
| 20:51.41 | NetRipper | i need to go through the htccamera1.dll again to find it i think ;) |
| 20:51.44 | woodyPL | but whatever I set |
| 20:51.49 | woodyPL | it works like this |
| 20:52.03 | cr2 | NetRipper: we know the spl pmic names, g1 names and proc_comm masks. we need to find out how do they correlate with each other |
| 20:52.05 | woodyPL | one thing that varies is the reset time |
| 20:52.15 | woodyPL | which depends how high the value of pixclock is |
| 20:52.35 | NetRipper | cr2, i saw you had some vreg bitmasks already documented |
| 20:53.27 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 20:53.37 | woodyPL | tmzt: I also read an IRC log when you tried to make BruteSource's lcd work |
| 20:53.45 | woodyPL | but still no joy |
| 20:53.52 | tmzt | ok, get the c program from the end of that then |
| 20:54.08 | tmzt | pixclock should be in the dump also |
| 20:54.21 | woodyPL | which dump should I use |
| 20:54.24 | woodyPL | I mean |
| 20:54.32 | woodyPL | should I dump it to a file |
| 20:54.40 | woodyPL | and then use hexdump on my pc |
| 20:54.42 | tmzt | pwf works well |
| 20:54.43 | woodyPL | which will miux the bytes |
| 20:54.46 | *** join/#htc-linux cr2 (n=cr2@ip-77-25-49-128.web.vodafone.de) |
| 20:54.48 | woodyPL | or just dump it in haret console |
| 20:54.49 | woodyPL | *mix |
| 20:55.06 | cr2 | hehe |
| 20:55.20 | cr2 | i gave up on cygwin |
| 20:55.43 | cr2 | downloaded 500mb in 3 hours :) |
| 20:58.02 | cr2 | the proc_comm aka dex in wince uses 2 params |
| 20:58.26 | cr2 | void *in, void *out |
| 20:59.00 | cr2 | the cmd is put inside the *in |
| 20:59.15 | cr2 | depending on the number of arameters |
| 20:59.37 | NetRipper | eh? is the out not just the return value? |
| 21:00.18 | cr2 | we may avoid the redundant third param in proc_comm_wince too |
| 21:00.36 | *** join/#htc-linux puregenius (n=chatzill@brln-4d0ce0e7.pool.mediaWays.net) |
| 21:00.53 | cr2 | or just define the proc_comm_dex(void *in, void *out) |
| 21:01.57 | *** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-160-071.ewe-ip-backbone.de) |
| 21:02.51 | *** join/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
| 21:03.21 | rolk | Anyone an idea what the android ttyDCC device is? It is configured in the kernel with CONFIG_DCC_TTY option flag. |
| 21:03.47 | cr2 | NetRipper: the msm gpio demux is commented out in haret, because it's not so easy as it was thought ;) |
| 21:12.20 | dcordes | what's the best way to use kaiser as modem for debian? |
| 21:12.24 | dcordes | (with usb) |
| 21:14.34 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 21:14.48 | toer | NetRipper: your commit vibrated ok :) |
| 21:16.52 | NetRipper | glad to hear |
| 21:19.03 | NetRipper | toer, you also have a diamond? |
| 21:20.40 | *** part/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
| 21:20.53 | NetRipper | Balsat, zycho, tekkdrone, toer, can you test this kernel as well? it includes jobo's keypad.. use mtype 1910 for raphael and mtype 1805 for diamonds.. http://www.netripper.com/raphael/zImage-git-20090111-00 |
| 21:21.35 | NetRipper | works for my raph100, just need confirmation that it works properly on other devices too |
| 21:24.38 | *** join/#htc-linux t3chi3 (n=blarg@ip24-250-216-85.ga.at.cox.net) |
| 21:26.21 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
| 21:28.22 | dcordes | cr2: if you don't want to destroy your laptop os, you can always use rootfs on usb disk |
| 21:28.37 | dcordes | I do that using extlinux |
| 21:29.12 | cr2 | dcordes: my usb hdd is for amd64 |
| 21:29.28 | tekkdrone | NetRipper: the kernel boots on raph500 and gets past the handoff but I'm seeing display corruptio |
| 21:29.30 | tekkdrone | corruption |
| 21:29.30 | cr2 | i used it on 2 other notebooks |
| 21:30.10 | cr2 | tekkdrone: the epson chip init is different from toshiba |
| 21:30.28 | cr2 | tekkdrone: it is necessary doc document it first |
| 21:30.33 | tekkdrone | the osk is visible and the text is readabe so it's not as bad as some of the previous video corruption photos I've seen |
| 21:30.56 | NetRipper | tekkdrone, odd.. did you previously try one of jobo's kernel that also had the keypad? |
| 21:31.33 | tekkdrone | no, your kernel is the only one I've stuck on the raph so far, I haven't been actively following, just standing by for tests (i'm still working on apache) |
| 21:31.42 | cr2 | http://wiki.xda-developers.com/index.php?pagename=RaphaelLCD |
| 21:31.42 | NetRipper | ok |
| 21:31.51 | cr2 | this is for raph100 |
| 21:33.18 | NetRipper | cr2, the raph500 has a different lcd? |
| 21:34.52 | cr2 | 800 |
| 21:34.57 | tekkdrone | NetRipper: also got the double vibrate at boot, and now that the calibration routine ended the screen looks almost normal, only some discoloration on tux, and a green square next to the OSK |
| 21:35.17 | cr2 | 800 has the same epson chip as blackstone |
| 21:35.57 | cr2 | hmm, can't login to check 500 |
| 21:36.12 | cr2 | rsa cert is missing in this hdd ;) |
| 21:36.27 | NetRipper | tekkdrone, the green square allows you to minimize the OSK and to drag it around.. calibration can be set in kernel param so that you dont have to calibrate every time you boot up ;) |
| 21:36.50 | tekkdrone | excellent, tux looks like he's the wrong bithdepth, intended also? |
| 21:36.51 | NetRipper | msmts_calib=0x7a.0x5e.0x35a.0x37f |
| 21:36.57 | NetRipper | no, not intended |
| 21:37.03 | NetRipper | was it good on earlier kernels? |
| 21:37.12 | tekkdrone | ealier kernels wouldn't pass console handoff |
| 21:37.15 | NetRipper | oh |
| 21:37.16 | tekkdrone | nevermind showing me tux |
| 21:37.17 | tekkdrone | lol |
| 21:37.41 | NetRipper | you tried my other kernel a few hours ago, right? |
| 21:38.00 | tekkdrone | no, just the one middle of last week |
| 21:38.07 | tekkdrone | and the one you pasted a few minutes ago |
| 21:38.19 | NetRipper | ah ok |
| 21:38.23 | tekkdrone | or hours, I have timestamps off |
| 21:38.25 | NetRipper | ah right the one that vibrated for 5 sec |
| 21:38.39 | tekkdrone | aye, that one worked after you passed it to me with no console handoff |
| 21:39.03 | tekkdrone | usb being the exception |
| 21:39.16 | NetRipper | tekkdrone, ah... and the last one actually does continue booting? that's really odd, as there are no changes in the mddi part ;) |
| 21:39.49 | tekkdrone | aye, this one comes up to the calibration and osk, only thing changed is the zImage |
| 21:39.51 | cr2 | NetRipper: raph500 has the same epson chip |
| 21:39.57 | NetRipper | makes me wonder if there might be other variables at play... i.e. you must have usb set to 'activesync' mode.. and you must have usb cable plugged in.. |
| 21:40.12 | NetRipper | cr2, aha.. so raph500 should have same graphical glitches as raph800 |
| 21:40.23 | tekkdrone | netripper: it is, rndis off, usbstor off |
| 21:40.24 | cr2 | hm. even some regs are documented by names |
| 21:40.24 | NetRipper | which explains what tekk is seeing |
| 21:40.31 | cr2 | yeah |
| 21:40.57 | tekkdrone | aye, buy nothing like I was seeing in those blackstone shots |
| 21:41.08 | NetRipper | tekkdrone, rndis (=activesync) should be on ;) |
| 21:41.21 | cr2 | S1D13774 |
| 21:41.27 | tekkdrone | I thought rndis was only the advanced subset |
| 21:41.48 | tekkdrone | which I have unchecked |
| 21:41.49 | NetRipper | tekkdrone, when you plug in the usb cable, you must select "activesync" -> "done" |
| 21:41.54 | NetRipper | oh |
| 21:42.00 | NetRipper | i saw that in wiki |
| 21:42.18 | NetRipper | maybe it's true, i have advanced enabled i think, but may be neccesary for raph500/800 |
| 21:42.20 | tekkdrone | I have it set static, no prompt, activesync enabled, advanced disabled, etc |
| 21:42.26 | NetRipper | ok |
| 21:42.27 | tekkdrone | hmmmm |
| 21:42.49 | tekkdrone | last time when it would hang at console handoff tmzt and i tried every possible combination |
| 21:42.52 | cr2 | it's rather verbose |
| 21:42.59 | NetRipper | ok |
| 21:43.05 | cr2 | i'll switch on another notebook |
| 21:43.11 | tekkdrone | and I understand booting with usb plugged in, same goes for my pxa27x-udc progress on Apache |
| 21:43.18 | NetRipper | aha |
| 21:43.28 | NetRipper | can you show me your default.txt on pastebin/ |
| 21:43.29 | NetRipper | ? |
| 21:43.38 | tekkdrone | mine? sure |
| 21:43.45 | zycho | NetRipper: new kernel working fine on diam300 |
| 21:43.52 | NetRipper | zycho, thanks |
| 21:45.19 | tekkdrone | netripper: http://pastebin.com/d14a31060 |
| 21:45.37 | tekkdrone | I'm using 64M for now but I'm pretty sure my ceiling is higher |
| 21:45.37 | NetRipper | hm |
| 21:45.38 | NetRipper | ok |
| 21:45.45 | tekkdrone | that was initially necessary to get around the memory panic |
| 21:45.50 | zycho | does some know, why its not possible to save date&time settings? |
| 21:46.09 | NetRipper | zycho, RTC is not working yet |
| 21:46.28 | zycho | what does RTC mean? |
| 21:46.32 | NetRipper | real time clock |
| 21:46.42 | cr2 | NetRipper: rtc uses dex |
| 21:46.42 | zycho | ah thanks |
| 21:46.45 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
| 21:46.47 | NetRipper | but we may get it working soon, as proc_comm is working now |
| 21:47.02 | zycho | nice to see |
| 21:47.30 | cr2 | atmega48 and atmega88 |
| 21:47.53 | cr2 | hm. does it mean that the KLT and KSC are 2 different controllers ?? |
| 21:48.11 | NetRipper | i dont dare to answer |
| 21:51.32 | tmzt | cr2: do you think the lcd has to be inited through the epson chip, maybe using an i2c host on that chip or something (can't remember from ds)? |
| 21:52.16 | cr2 | not host, but some i2c and/or spi sequence |
| 21:52.27 | cr2 | it depends on the LCD type |
| 21:52.39 | cr2 | there are 5-6 LCD types in the spl |
| 21:52.47 | tmzt | ok, but the lcd still has a controller chip on it (lcm) in addition to that epson chip? |
| 21:53.19 | tmzt | does KLT have the same i2c id as the g1 led chip? |
| 21:53.37 | cr2 | evildoers. they have obfuscated the vreg interface to such an extent that i<#m really eager to disassemble the microkernel ;) |
| 21:53.58 | cr2 | tmzt: we see 3 different i2c ids |
| 21:55.04 | cr2 | NetRipper: have you ever dumped the wince dmesg after hard reset ? |
| 21:56.13 | cr2 | thes reference the microP and microP48 as separate entities |
| 21:57.11 | cr2 | and psoc |
| 21:57.21 | tmzt | is the touchpad (navi) controller a dedicated chip? |
| 21:57.48 | toer | NetRipper: boots fine on my raph100 |
| 21:57.58 | NetRipper | cr2, no i havent.. should we see something special? :) |
| 21:59.55 | cr2 | NetRipper: the psoc et al. debug data should be there |
| 22:00.11 | cr2 | tmzt: it's not yet clear |
| 22:00.35 | tmzt | have you found the firmware for the devices yet? |
| 22:03.57 | cr2 | aha. the blackstone is more verbose |
| 22:04.25 | cr2 | tmzt: didn't look that deep. it should be easier to implement the chip identification first |
| 22:06.04 | cr2 | bt,cam,usb,aux,mmc,ruim,msme,msmp,rftx,aux2,mddi,wlan,rfrx2,ruim2 |
| 22:07.39 | tmzt | msme/msmp ? |
| 22:08.58 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
| 22:10.07 | cr2 | should be in the g1 code too |
| 22:10.16 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 22:10.50 | cr2 | raph500 has 'synt' |
| 22:11.09 | cr2 | but misses some others |
| 22:11.11 | tmzt | synaptics? |
| 22:11.15 | tmzt | like on g1? |
| 22:11.32 | cr2 | without having the pmic docs it's going to be a pita ;) |
| 22:11.40 | cr2 | no, the pmic register names |
| 22:11.59 | tmzt | oh |
| 22:12.10 | tmzt | vreg is not handled through proc_comm? |
| 22:13.12 | cr2 | it is, but you need to know how which bitmask has which name |
| 22:13.37 | cr2 | dex uses bitmasks, but spl uses plaintext names |
| 22:14.00 | cr2 | and a different way to communicate them to arm9 |
| 22:14.30 | tmzt | the AT channel? |
| 22:14.37 | cr2 | g1 uses a third (different) method creating a real mess |
| 22:15.20 | cr2 | by modifying the amss the nadroid people created a lot of pain ;-) |
| 22:15.51 | cr2 | if there was the amss source code, it would have not been a problem |
| 22:16.04 | cr2 | or at least the pmic docs |
| 22:16.43 | cr2 | so the only way to resolve the problem is to find the pmic/dex arm9 parser code. |
| 22:27.23 | j0b0 | NetRipper the kernel you just posted works for me (not surprisingly, on raph100) |
| 22:27.28 | j0b0 | good evening |
| 22:28.20 | NetRipper | ok |
| 22:28.28 | NetRipper | j0b0, can you check the last patch |
| 22:28.32 | NetRipper | and see if im missings omething? |
| 22:28.52 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.25 |
| 22:29.12 | NetRipper | i recall you made some modifications in keypad.c, maybe i still had an old version |
| 22:31.20 | j0b0 | will check, but it seems everything works. up/down=menu/back, turns landscape when i slide out the keyboard, does not have the power button spoof it (which it shouldnt so thats good) |
| 22:32.54 | maejrep | <cr2> maejrep[w]: the LSB for i2c means read/write <-- yeah, I noticed that when reading i2c-msm.c |
| 22:33.38 | NetRipper | ok |
| 22:33.48 | j0b0 | in board_raphael.c, init_keypad() is called (int ffa) but in keypad.c its (void) .. a copy/paste leftover *blush* |
| 22:34.06 | NetRipper | oops |
| 22:34.11 | NetRipper | didnt notice that |
| 22:34.36 | j0b0 | it must be mine |
| 22:35.02 | Mullins | dcordes: you there? |
| 22:35.03 | NetRipper | yes i took it without thinking ;) |
| 22:35.20 | cr2 | maejrep: what do you think about creating a proc_comm_dex(void *in, void *out) ? |
| 22:35.23 | j0b0 | it doesnt hurt but its wrong |
| 22:35.51 | cr2 | maejrep: i want to sort out the vregs |
| 22:36.44 | maejrep | <cr2> void *in, void *out <-- it's not data1 and data2, like trout? |
| 22:36.47 | NetRipper | j0b0, i'd have expected the linker to complain to be honest |
| 22:36.52 | Mullins | maybe someone can help. I am using the tslib ts_print_raw to display the touch screen events. Touching the screen it shows no input, UNLESS I also press a key and hold it down on the keypad, then ts_print_raw will display the touch screen info. Like its waiting for the key event too |
| 22:37.17 | maejrep | maejrep, what would be the difference with _dex? just renaming it? |
| 22:37.21 | maejrep | wtf |
| 22:37.26 | cr2 | maejrep: no, the cmd is included in *in |
| 22:37.31 | maejrep | did I just address myself? :( |
| 22:37.36 | NetRipper | maejrep, lol |
| 22:37.37 | maejrep | that was for you :p |
| 22:37.54 | maejrep | cr2, ahh, I see |
| 22:38.24 | cr2 | maejrep: and the void * depends on the number of params |
| 22:38.41 | cr2 | the wiki entries like 2= :) |
| 22:39.57 | tmzt | Mullins: what keypad? |
| 22:40.06 | NetRipper | cr2, so how would a call look like? |
| 22:40.19 | NetRipper | and does it replace proc_comm_wince? |
| 22:40.31 | maejrep | int cmd = 0x17; msm_proc_comm_dex(cmd, 0); ? |
| 22:40.36 | dcordes | Mullins: yes |
| 22:41.03 | maejrep | or would you just want to pass the constant to *in, and have the function cast it to int |
| 22:41.06 | cr2 | NetRipper: the void * will be replaced by the appropriate struct |
| 22:41.37 | cr2 | (DEX_1_PARAM) in.cmd=0x17; |
| 22:41.43 | NetRipper | cr2, for the out part? |
| 22:41.53 | cr2 | proc_comm_dex(in,out); |
| 22:42.09 | cr2 | the out is not necessary for the most commands |
| 22:42.24 | cr2 | but i guess for the RTC call you need some output |
| 22:42.42 | cr2 | so it's only necessary to declare the right structs |
| 22:42.54 | NetRipper | cr2, hm, so arm9 will read pointers? |
| 22:43.06 | maejrep | lol |
| 22:43.23 | NetRipper | didnt expect it to work like that |
| 22:43.24 | maejrep | NetRipper, the code reads the value from memory then stuffs it into your out param |
| 22:44.02 | NetRipper | maejrep, right, so you pass a struct and arm9 will fill it |
| 22:44.35 | Mullins | tmzt: the Kaiser keypad |
| 22:45.00 | tmzt | is kaiser using one input device or two? |
| 22:45.05 | cr2 | NetRipper: no, it's just the API |
| 22:45.09 | tmzt | and can you run evtest on the ts input device? |
| 22:45.28 | cr2 | NetRipper: arm9 only needs the data at right 0x1f SMEM locations |
| 22:45.41 | Mullins | tmzt: touchscreen0 -> event0 so event0 is ts events only? |
| 22:46.05 | tmzt | cat /sys/class/input/*/name |
| 22:46.41 | NetRipper | im really confused.. i'd need to see a full example to get it i think.. as long as you and maejrep understand ;) |
| 22:46.41 | cr2 | NetRipper: i think that a wince-compatible api is better than some magic binary constants at $random places |
| 22:46.42 | maejrep | right, so the struct is only used by the proc_comm code, which copies the values to smem |
| 22:46.45 | Mullins | dcordes: the ts works in ts_print_raw but only if I hold down a key on the keypad |
| 22:48.06 | cr2 | NetRipper: ok, i'll try to write more extensive docs |
| 22:50.00 | NetRipper | cr2, so what maejrep is correct? |
| 22:50.21 | maejrep | cr2, so any thoughts what I'm doing wrong with gpio 27's irq? :) It's active-low, so in windows when pressing a key, it goes high to low, then pulled high again. but in linux, it never goes high again |
| 22:51.01 | Mullins | tmzt: kaiser-ts and kaiser-kbd are cat/sys/class/input/*/name. I will check the keyboard to see what is happening differently from our ts driver |
| 22:51.15 | NetRipper | cr2, maejrep to configure the irq in linux, do you use gpio_configure? |
| 22:51.29 | maejrep | I tried that, but I also used just request_irq |
| 22:51.32 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 22:52.00 | NetRipper | you first gpio_configure then request_irq |
| 22:52.00 | dcordes | Mullins: does the ts work in android? maybe we destroyed something in git |
| 22:52.11 | Mullins | dcordes: fine in Android yeah |
| 22:52.17 | maejrep | right, I tried that, but it didn't change |
| 22:52.28 | NetRipper | i.e. gpio_configure(23, IRQF_TRIGGER_FALLING | IRQF_TRIGGER_RISING); and to get the irq nr for request_irq() you do MSM_GPIO_TO_INT(23) |
| 22:52.39 | maejrep | i mean, it set the registers based on how i configured it .. but it didn't affect behavior |
| 22:52.47 | maejrep | right :P |
| 22:53.21 | NetRipper | i first made the mistake to also do MSM_GPIO_TO_INT for gpio_configure ;) |
| 22:53.21 | maejrep | its not a matter of triggering, its that the gpio itself (and thus irq as well) is never returned to its normal state after firing once |
| 22:53.37 | maejrep | it triggers fine .. the first time |
| 22:53.41 | NetRipper | ok |
| 22:53.44 | maejrep | but after that, its never active again |
| 22:54.17 | NetRipper | have you tried setting it to high again manually? |
| 22:54.18 | tmzt | is there a pull-up pull-down like on the mddi i2c? |
| 22:54.20 | tmzt | mdp |
| 22:54.42 | maejrep | there is no way I've found to set the input. I did try setting OE and set the output, but that didn't change it |
| 22:55.01 | cr2 | maejrep: what is gpio configure ? |
| 22:55.15 | maejrep | you mean what are the values of the registers at the time? |
| 22:55.22 | cr2 | maejrep: is the gpio_alt_conf ported from vogue already ? |
| 22:55.30 | maejrep | I don't think so |
| 22:55.40 | maejrep | but gpio_configure works on my device |
| 22:55.57 | NetRipper | cr2, gpio_configure is already working |
| 22:55.58 | cr2 | it's a core msm7x0xX function, which androids have hidden behind the PCOM*TLMM* |
| 22:56.04 | maejrep | that is, if I pass IRQF_TRIGGER_RISING|IRQF_TRIGGER_FALLING, it sets the EDGE register correctly |
| 22:56.28 | cr2 | maejrep: you need to set the ALT value properly to have an irq |
| 22:56.36 | cr2 | it's documented in wiki |
| 22:56.40 | cr2 | value=3 |
| 22:57.14 | tmzt | is that the same as the touchscreen problem? |
| 22:57.28 | tmzt | that the irq won't trigger |
| 22:57.47 | maejrep | cr2, +0x414 ALT_FN(Config2) ? |
| 22:59.16 | maejrep | and do we have to notify the arm9 after setting those (like for proc comm)? |
| 22:59.50 | NetRipper | tmzt, touchscreen problem is a normal irq.. this is about gpio irq.. i think ts irq has something to do with having to notify touchscren somewhere that we handled the irq.. although.. i donte ven get it fired the first time ;) |
| 22:59.54 | maejrep | I've traced proc comm in haret, and didn't see any activity during keypress, so i at least know its not something it has to do at each fire |
| 23:00.25 | cr2 | maejrep: check the gpio_func() in the vogue tree |
| 23:00.27 | tmzt | so it's really that g1 doesn't use the msmts at all? |
| 23:00.36 | tmzt | we don't have code for it |
| 23:00.48 | cr2 | keyboard is i2c, is have nothing to do with proc_comm |
| 23:01.06 | maejrep | I don't see gpio_func :x |
| 23:01.15 | cr2 | maejrep: try the functions mentioned in the RaphaelDEX descrioption |
| 23:01.50 | cr2 | maejrep: will you see a proc_comm action on the SD insert ? on the wifi on /off ? on the bt on/off ? |
| 23:01.59 | cr2 | hm, or do you have a diam ? |
| 23:02.06 | maejrep | i have raph |
| 23:02.07 | maejrep | 800 |
| 23:02.29 | maejrep | and yes i see proc comm activity |
| 23:02.43 | maejrep | ie, turning the camera on and off, I see activity with 0x15 and 0x16 |
| 23:02.46 | cr2 | ok, so you have an sd |
| 23:02.51 | maejrep | yes |
| 23:03.05 | cr2 | yes, i've seen the wiki docs |
| 23:03.17 | cr2 | but it may be PMDH related |
| 23:03.21 | cr2 | or the LCD |
| 23:03.24 | tmzt | 15 and 16 are vreg proc_comm's? |
| 23:03.33 | tmzt | for camera, at least in wiki |
| 23:03.43 | cr2 | yes, "generic" vreg calls |
| 23:03.58 | tmzt | and what is 0x9? |
| 23:04.10 | cr2 | tmzt: for some reason wince uses only this one, not the single funcs |
| 23:04.42 | cr2 | tmzt: look at hte RaphaelDEX wiki page |
| 23:05.54 | tmzt | I see, I had those backwards |
| 23:06.18 | tmzt | do 15 and 16 take bit offsets or sequential integers? |
| 23:06.32 | *** join/#htc-linux exco (n=exco@e181117142.adsl.alicedsl.de) |
| 23:06.40 | tmzt | I mean bit values |
| 23:07.10 | cr2 | 0x9 ? |
| 23:07.42 | tmzt | 0x8/9 are pmic cam on/off, I assume those take no parameters |
| 23:08.08 | maejrep | tmzt, appears to be bitmask |
| 23:08.34 | tmzt | so there are 32 vregs? |
| 23:08.53 | cr2 | tmzt: in the current g1 code yes |
| 23:08.56 | tmzt | including the ones cr2 listed that don't have dedicated proc_comm's known |
| 23:09.04 | cr2 | but the older versions had more |
| 23:11.39 | cr2 | maejrep: it's necessary to find the mapping between the 0x15/16 bitmask ands the plain text names used by spl and g1 |
| 23:12.09 | tmzt | is there danger in disabling vregs? |
| 23:12.27 | cr2 | tmzt: in theory |
| 23:12.33 | tmzt | like ruim1/2 on a raph to see if gsm stops working, or rx/tx |
| 23:12.49 | tmzt | raph100 I mean |
| 23:12.56 | cr2 | tmzt: the naming is a bit strange |
| 23:13.19 | tmzt | it's the sim standard for cdma, qualcomm uses it for some reason |
| 23:13.20 | cr2 | that's why i'm confused |
| 23:13.23 | tmzt | or |
| 23:13.41 | cr2 | wtf is ruim2 ? |
| 23:13.50 | tmzt | R-UIM |
| 23:13.56 | tmzt | user identity module |
| 23:14.03 | cr2 | ok |
| 23:14.15 | maejrep | never heard that with sprint :x |
| 23:14.19 | cr2 | but it still does not say anything about voltage |
| 23:14.24 | cr2 | 3.3V ? |
| 23:14.29 | tmzt | they don't use it, it's only in some indian phones |
| 23:15.00 | tmzt | http://en.wikipedia.org/wiki/R-UIM |
| 23:15.13 | cr2 | because wifi uses RUIM2 |
| 23:15.25 | cr2 | afair |
| 23:15.35 | cr2 | but it's easy to trace |
| 23:15.37 | tmzt | could it need more power than the SDHC vreg can provide? |
| 23:15.55 | tmzt | so they could just be using it as an AUX |
| 23:16.12 | cr2 | SDHC power != SD(HC) card power |
| 23:16.26 | tmzt | oh, yeah host controller |
| 23:16.39 | cr2 | "SDHC power" is for the host controller operation |
| 23:17.00 | cr2 | the card tells you through CID/CSD what it needs |
| 23:17.40 | cr2 | but the host itself needs to be powered first |
| 23:18.05 | cr2 | maejrep: do you see 15/16 activity on SD in/out |
| 23:18.06 | maejrep | cr2, any idea why the numbers listed in RaphaelDEX as "0x8a" and "0x8b" for get battery data and id don't actually return data? |
| 23:18.19 | maejrep | oh sorry, i'll check |
| 23:18.36 | cr2 | maejrep: i'm not sure about the *out layout |
| 23:18.48 | cr2 | for 0x8a and 0x8b |
| 23:19.33 | maejrep | I was tracing +0x00, 04, 08, 0c, 20, 24, 30, 34, 28, 38 |
| 23:19.36 | cr2 | some data is stored in SMEM directly, asnd it'd documented on the diamond page |
| 23:19.57 | maejrep | some of those were from the trout proc comm, and the rest from the smem wiki docs |
| 23:20.05 | maejrep | and I didn't see any output |
| 23:20.15 | maejrep | so, if it just stores it elsewhere that'd make sense |
| 23:20.21 | cr2 | forget about trout proc comm :) |
| 23:20.30 | cr2 | it's completely incmpatible |
| 23:20.37 | maejrep | I noticed ;p |
| 23:22.17 | cr2 | and many other trout* things are completely irrelevant |
| 23:22.43 | cr2 | let's finish witht hr SDHC vreg |
| 23:24.23 | maejrep | cr2, yes I do |
| 23:25.27 | maejrep | 0x800000 |
| 23:26.01 | cr2 | ok |
| 23:26.28 | cr2 | btw, can you trace the 'setlcd' for lcd on/off ? |
| 23:26.40 | maejrep | 0xe? |
| 23:26.50 | cr2 | i think bt and wifi are also interesting |
| 23:27.27 | maejrep | for some reason, pressing the power button is interrupting my haret session :| |
| 23:27.42 | tmzt | over wifi? |
| 23:27.50 | maejrep | over rndis |
| 23:29.04 | cr2 | hehe |
| 23:29.57 | j0b0 | the power button is gpi 83 |
| 23:30.23 | maejrep | was looking for lcd power proc comm |
| 23:31.50 | j0b0 | you have to let it time out then :) |
| 23:32.13 | maejrep | would it keep the usb session alive if it times out rather than turning off? |
| 23:33.53 | cr2 | listen 9998 |
| 23:34.05 | cr2 | telnet ip 9998 |
| 23:34.13 | cr2 | setlcd 1 |
| 23:34.16 | cr2 | setlcd 4 |
| 23:34.28 | cr2 | or 0, i don't rememebr# |
| 23:34.44 | maejrep | ah |
| 23:38.56 | maejrep | 0x400000 and 0x4000 |
| 23:39.14 | tmzt | mddi and lcd? |
| 23:39.54 | maejrep | that was off |
| 23:39.59 | maejrep | turning on is more interesting |
| 23:41.06 | maejrep | hmm, actually what's weird is it calls 0x1a which is set voltage. but then it doesn't pass any data to it other than the same ID |
| 23:41.15 | cr2 | there was a bt on/off command, but it's not in mainline haret afaik |
| 23:41.36 | maejrep | but its the same ids |
| 23:41.40 | cr2 | hm, interesting |
| 23:41.42 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
| 23:41.56 | maejrep | turning on it does 0x1a for id 400000 and 4000, then 0x15 for the same |
| 23:43.07 | maejrep | hmm, turning bluetooth on does not show any proc comm activity |
| 23:43.44 | maejrep | ADM_AARM and UART2DM_RX irqs fire a lot, but that's it |
| 23:43.47 | cr2 | wifi is on ? |
| 23:44.16 | cr2 | they may share some voltage sources |
| 23:44.29 | maejrep | same turning off |
| 23:44.35 | maejrep | no wifi is not on |
| 23:44.40 | cr2 | maejrep: add this data to wiki |
| 23:44.41 | maejrep | Phone and Data Connection are |
| 23:44.41 | cr2 | ok |
| 23:45.09 | tmzt | is bluetooth in the soc? |
| 23:45.16 | tmzt | Olipro said it was |
| 23:45.45 | maejrep | cr2, what about the 400000 id that is already there for "2.5V VDDIO CAM" ? |
| 23:47.04 | cr2 | tmzt: brf6350 |
| 23:47.14 | cr2 | maejrep: it's from CIF.dll |
| 23:47.28 | maejrep | heh hmm... I just hit turn off data connection while tracing, and it froze the phone :p |
| 23:47.31 | cr2 | maejrep: i guess it |
| 23:47.39 | cr2 | s just 2.5V source |
| 23:48.30 | maejrep | it should know that turning off data does not mean turn off usb :P |
| 23:49.25 | cr2 | hm |
| 23:49.26 | tmzt | cr2: I mean is it in the same chip package as the msm? |
| 23:49.28 | exco | Mullins: just fyi - I just tried it - you can edit the partitions on your (micro)SD card using WM5torage and Ubuntu |
| 23:49.42 | cr2 | you can use wifi, and trace the usb vreg |
| 23:49.52 | cr2 | tmzt: no, it |
| 23:50.05 | cr2 | 's a separate chip from TI |
| 23:50.12 | cr2 | tmzt: bt+fm+rds |
| 23:50.29 | tmzt | does the fm work? |
| 23:50.38 | cr2 | tmzt: there is a 2page doc at TI site |
| 23:50.56 | cr2 | tmzt: if you'll send the right .bts commands it should work |
| 23:52.57 | Mullins | exco: might try it then, thanks |
| 23:55.44 | exco | Mullins: you can always ask me if it doesn't work the way you want it to |
| 23:56.00 | maejrep | raph800 doesn't have fm |
| 23:56.09 | tmzt | what bluetooth does it have? |
| 23:56.37 | maejrep | TI BRF6350BL |
| 23:57.01 | maejrep | according to the sprint touch pro block diagram |
| 23:59.04 | *** join/#htc-linux n3tim (n=netim@201.82.18.39) |
| 23:59.37 | cr2 | maejrep: it's in the bt chip. but maybe they have not wired it |
