| 00:04.12 | Chris` | I have a home screen, what can I do now? :) |
| 00:04.46 | j0b0 | go to settings, display and sound, dislpay timeout, set to never timeout |
| 00:05.18 | *** join/#htc-linux WyrM (n=wyrm@20158188135.user.veloxzone.com.br) |
| 00:05.26 | j0b0 | and in spare parts, end button behaviot, set to 'go home' |
| 00:06.10 | j0b0 | the display dies when it puts it to sleep and doesnt recover |
| 00:06.35 | Chris` | So it eats the battery? :) |
| 00:07.22 | j0b0 | yes, but you cant use it as a phone anyway, as you have no audio |
| 00:07.39 | *** join/#htc-linux konsta (n=asds@host81-157-60-163.range81-157.btcentralplus.com) |
| 00:08.05 | Chris` | Not yet |
| 00:08.16 | *** part/#htc-linux exco (n=exco@e181108109.adsl.alicedsl.de) |
| 00:09.01 | j0b0 | if you had to modify anything to make this work for you, document it on the wiki along with your phone model |
| 00:09.09 | j0b0 | bed time for me .. good nite |
| 00:09.25 | Chris` | Goodnight |
| 00:18.32 | *** part/#htc-linux WyrM (n=wyrm@20158188135.user.veloxzone.com.br) |
| 00:52.49 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
| 01:26.04 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 01:37.33 | maejrep | j0b0: yeah I've been noticing that myself recently |
| 01:38.01 | maejrep | which leaves only the flushing of the buffer as being what would have reenabled the irq |
| 01:38.12 | maejrep | which makes sense I suppose |
| 01:39.04 | maejrep | anyway j0b0: I also added LED and repeat support to the keypad, and registered the klt device as an led class driver, so you can turn on LEDs from /sys/class/leds/* |
| 01:39.28 | maejrep | so i guess i'll wait till your changes are in git before making a patch, so they don't conflict |
| 01:41.34 | maejrep | actually i need to change the LED handler anyway, to use a workqueue, since it runs from interrupt context, so i can't do the i2c writes at that time (i2c driver sleeps) |
| 01:42.27 | tmzt | you said sdio is working? you mean wifi? |
| 01:44.44 | maejrep | sdio is vaguely working |
| 01:45.04 | maejrep | it detects the card, just need to finish tweaking vreg and clocks |
| 01:45.41 | maejrep | haven't actually tried wifi yet, but I'm slowly fixing the bugs as I find them |
| 01:46.14 | maejrep | right now I get: |
| 01:46.15 | maejrep | [ 9.772722] mmc1: card claims to support voltages below the defined range. These will be ignored. |
| 01:46.15 | maejrep | [ 9.785600] mmc1: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored. |
| 01:46.15 | maejrep | [ 11.927507] mmc1: error -110 whilst initialising SDIO card |
| 01:46.39 | tmzt | we got that before didn't we? |
| 01:47.10 | tmzt | when the detection didn't work right I think |
| 01:47.16 | tmzt | all the cards were SDIO |
| 01:47.40 | tmzt | this is happening the same time mmc0 works? I mean you can read write to the sd card? |
| 01:47.45 | *** join/#htc-linux Moonlit (i=mooonlit@mario.dreamhost.com) |
| 01:51.15 | maejrep | I could last night :p |
| 01:51.25 | maejrep | now it's not detecting it properly, so I need to figure out why |
| 01:51.40 | *** join/#htc-linux balsa1 (n=kll@87.72.13.87) |
| 01:51.44 | tmzt | all the clocks are implemented now? |
| 01:51.45 | maejrep | the SDIO error we got before when I was trying sdcc_id=1 |
| 01:51.48 | maejrep | no |
| 01:52.04 | tmzt | sdcc_id=1? why? |
| 01:52.06 | maejrep | the two i'm working with are |
| 01:52.13 | tmzt | 2 and 3? |
| 01:52.16 | maejrep | because no one knew for sure what id it was on ;) |
| 01:52.30 | maejrep | now we do, so the messages make more sense |
| 01:52.40 | tmzt | is there some reason we can't just add all four sdcc's and let the detect code handle it? |
| 01:52.59 | maejrep | one thing that I don't understand though is why it's detecting mmc0 as a DMA device, when it should be PIO |
| 01:53.12 | maejrep | nope, we can do that |
| 01:53.15 | tmzt | why should it be PIO? |
| 01:53.24 | maejrep | (and do away with the sdcc_id cmdline override) |
| 01:53.40 | tmzt | wifi is on sdc1? |
| 01:53.49 | maejrep | in fact, i had to remove the cmdline override anyway, because otherwise it was overriding the add() call for sdc1 |
| 01:53.51 | maejrep | yes |
| 01:54.15 | maejrep | hmm, actually |
| 01:54.20 | maejrep | no we can't just let it auto detect |
| 01:54.25 | maejrep | <PROTECTED> |
| 01:54.29 | maejrep | it requires pdata |
| 01:54.31 | tmzt | from earlier, g1 uses rmnet for mobile data, it doesn't use ppp and doesn't need a smd_tty channel for it |
| 01:54.45 | maejrep | right, it uses smd_qmi |
| 01:54.51 | tmzt | can you paste that pdata here? |
| 01:55.02 | maejrep | static struct mmc_platform_data htcraphael_wifi_data = { |
| 01:55.02 | maejrep | <PROTECTED> |
| 01:55.02 | maejrep | <PROTECTED> |
| 01:55.03 | maejrep | <PROTECTED> |
| 01:55.03 | maejrep | <PROTECTED> |
| 01:55.03 | maejrep | }; |
| 01:55.18 | tmzt | ok, it's embedded_sdio |
| 01:55.28 | maejrep | as for the PIO question, I'm basing that off a g1 dmesg |
| 01:55.32 | tmzt | why were you using the command line option which is for sd cards? |
| 01:55.44 | maejrep | <6>[ 1.031464] mmc0: Qualcomm MSM SDCC at 0x00000000e1000000 irq 24,0 dma -1 |
| 01:55.45 | maejrep | <6>[ 1.031587] mmc0: 4 bit data mode enabled |
| 01:55.45 | maejrep | <6>[ 1.031648] mmc0: MMC clock 144000 -> 20000000 Hz, PCLK 64000000 Hz |
| 01:55.45 | maejrep | <6>[ 1.031739] mmc0: Slot eject status = 1 |
| 01:55.45 | maejrep | <6>[ 1.031770] mmc0: Power save feature enable = 0 |
| 01:55.45 | maejrep | <6>[ 1.031831] mmc0: PIO transfer enabled |
| 01:55.52 | maejrep | what do you mean? sdcc_id ? |
| 01:55.57 | tmzt | yeah |
| 01:56.06 | maejrep | that is *intended* for sd cards :) |
| 01:56.26 | maejrep | but the way it was rewritten makes it override whatever you pass to msm_add_sdcc() |
| 01:56.32 | tmzt | yeah, I just wondered why you used that instead of the trout code |
| 01:56.42 | maejrep | so it worked for adding sdc3, but when i'd try to add sdc1, it would override that 1 as a 3 |
| 01:56.50 | tmzt | oh, I thought it was in the board.c |
| 01:56.51 | maejrep | ? |
| 01:57.04 | maejrep | no, the override was moved to the msm_sdcc_add() function |
| 01:57.11 | tmzt | the pdata you just pasted |
| 01:57.16 | maejrep | i think that was netripper's modification of lavender's patch |
| 01:57.17 | tmzt | yeah, I didn't know that |
| 01:57.48 | maejrep | the trout code doesn't auto detect either |
| 01:57.51 | tmzt | have you tried the trout code for wifi/sdio? |
| 01:57.52 | maejrep | but this is trout code, basically |
| 01:57.55 | maejrep | I copied trout-mmc.c |
| 01:57.58 | maejrep | ^ |
| 01:58.20 | maejrep | and as of last night, I was still able to read the sd card just fine |
| 01:58.27 | maejrep | but now it's failing for some reason, no idea why |
| 01:58.28 | tmzt | and can you disable that override in you copy of host/msm and fix your board to register sdc1 with the wifi pdata and sdc3 without it? |
| 01:58.43 | maejrep | sdc3 also has pdata |
| 01:59.03 | tmzt | just status and status_register? |
| 01:59.04 | maejrep | and I can't register sdc2 and sdc3 with the same pdata, because they both include irqs, and would be fighting over the irq |
| 01:59.13 | maejrep | and switchvdd |
| 01:59.20 | maejrep | and ocr_mask |
| 01:59.21 | tmzt | what's sdc2? |
| 01:59.45 | maejrep | nothing (well, it's sd card on raph100 and internal storage on diam 100 i think) |
| 01:59.51 | maejrep | it's nothing on raph800, not even enabled |
| 01:59.57 | tmzt | I mean for testing on raph800 |
| 02:00.10 | maejrep | what do you mean? |
| 02:00.28 | tmzt | and can you disable that override in you copy of host/msm and fix your board to register sdc1 with the wifi pdata and sdc3 without the existing sd card pdata |
| 02:00.52 | tmzt | s/without/with/ |
| 02:00.58 | maejrep | i'm not using the override now |
| 02:01.16 | maejrep | but if I don't pass the sdc3 pdata to it, it won't know that a card is inserted |
| 02:01.18 | tmzt | we should be using mtype for that anyway |
| 02:01.31 | maejrep | actually, i think it won't even accept the add, because you have to tell it how to detect if a card is inserted |
| 02:01.35 | tmzt | yes, pass the sdc3 pdata |
| 02:01.51 | maejrep | i'm already doing that |
| 02:01.56 | tmzt | ok |
| 02:13.49 | *** join/#htc-linux lifegrasp (n=ckonkel@70-138-169-80.lightspeed.hstntx.sbcglobal.net) |
| 02:16.25 | maejrep | damn it |
| 02:16.40 | maejrep | i hate when I mean to hit listen for network connections in haret, and accidentally hit run :/ |
| 02:20.30 | tmzt | yeah, use a different directory |
| 02:32.46 | maejrep | ah good idea :) |
| 03:17.26 | *** join/#htc-linux balsa1 (n=kll@87.72.13.87) |
| 03:18.12 | *** join/#htc-linux chavonbravo (n=cb@fl-71-1-235-8.dhcp.embarqhsd.net) |
| 03:26.00 | *** join/#htc-linux ppman (n=mkern@pool-71-250-18-248.nwrknj.east.verizon.net) |
| 03:26.03 | ppman | hiya |
| 03:26.19 | ppman | still no luck with kaiser battery - I might have to use rpc :( |
| 03:26.49 | ppman | can someone tell me where the code is for vogue that tells android what band it's on? |
| 03:26.58 | maejrep | have you seen windows issue the same proc comm command in haret? |
| 03:26.58 | ppman | I realize it's cdma, but still.. |
| 03:27.15 | ppman | how do I use haret to do that? |
| 03:27.41 | maejrep | addlist traces p2v(0x1ffc100) |
| 03:27.50 | maejrep | and fc104, fc120, fc124 |
| 03:28.04 | ppman | okay, and I shouldn't boot anything with that script? |
| 03:28.06 | maejrep | then wirq for at least 10 seconds |
| 03:28.22 | maejrep | no, just listen for network connections and connect to it with haretconsole |
| 03:28.22 | tmzt | what band? |
| 03:28.55 | ppman | tmzt: like 3g/etc. |
| 03:29.25 | tmzt | yeah, I think that's all in ril |
| 03:29.33 | ppman | maejrep: can I do that over wifi or rndis? |
| 03:29.42 | maejrep | either, yes |
| 03:29.43 | ppman | tmzt: thanks for the tip |
| 03:29.52 | maejrep | but you'll get a lot of irq chatter depending on which on you use |
| 03:30.05 | *** join/#htc-linux ykut_johny1 (n=ykut_joh@mitsa.org.my) |
| 03:30.09 | maejrep | if you use rndis, I always ignore these bits: ibit irqs 47 3 6 16 19 |
| 03:30.36 | maejrep | 47 is usb data, I don't know which irq bit is for wifi, but you'll notice it when you see it :) |
| 03:30.59 | maejrep | of course, this is for a raphael ... your irqs may vary |
| 03:31.08 | tmzt | we need to know that anyway, don't we? |
| 03:31.08 | maejrep | (probably will now that i think about it..) |
| 03:31.11 | tmzt | the wifi irq |
| 03:31.15 | ppman | heh |
| 03:31.17 | ppman | :P |
| 03:31.32 | maejrep | well on raph it's gpio 29 for wifi |
| 03:31.41 | maejrep | but anyway |
| 03:32.04 | maejrep | ppman: if you run wirq 1, see which bits are too spammy, and add it to the "ibit irqs .." line, then do it again |
| 03:32.17 | maejrep | and you run all those commands in haret console |
| 03:32.49 | chavonbravo | !seen rogro82 |
| 03:32.57 | ppman | 000.963 IRQS IRQ1: GPIO2(33)=1 |
| 03:32.57 | chavonbravo | seen rogro82 |
| 03:33.02 | ppman | see that line quite a bit |
| 03:33.03 | chavonbravo | :P no bots in here. :) |
| 03:34.23 | tmzt | ~seen |
| 03:34.41 | maejrep | ppman: yeah, so you'd do ibit irqs 33 if you want to ignore it |
| 03:34.47 | ppman | yep |
| 03:35.24 | maejrep | then if you do the addlist traces like above ^, and run wirq 10 (or longer), you should look for windows running a proc comm command |
| 03:35.32 | maejrep | I see it every 10 seconds, it runs 0x8a and 0x8b |
| 03:36.04 | ppman | umm... what would the line look like? |
| 03:36.46 | maejrep | 008.344 TRACES 9c0fc100(1 3 7)=8a @~f000fe50 |
| 03:36.51 | maejrep | plus several others following |
| 03:37.03 | ppman | I get 000.000 TRACES 951fc100=184 @~03fb2034 |
| 03:37.03 | ppman | 000.000 TRACES 951fc104=0 @~03fb2034 |
| 03:37.03 | ppman | 000.000 TRACES 951fc120=36b24b80 @~03fb2034 |
| 03:37.03 | ppman | 000.000 TRACES 951fc124=0 @~03fb2034 |
| 03:37.09 | maejrep | after that |
| 03:37.11 | ppman | whewn it starts, |
| 03:37.15 | maejrep | that's just the initial values |
| 03:37.25 | ppman | and only IRQS stuff about mddi after that |
| 03:37.33 | ppman | even for 20 seconds.. |
| 03:37.36 | ppman | lemme unplug it |
| 03:37.36 | maejrep | hmm, maybe your offset is different from mine? |
| 03:38.14 | maejrep | memory map has PC_COMMAND at 0x01f00000 + 0xfc100 |
| 03:38.32 | ppman | physical |
| 03:38.40 | ppman | I shouldn't do wince virtual? |
| 03:38.41 | maejrep | yeah |
| 03:38.49 | maejrep | yes it should be p2v() |
| 03:38.56 | maejrep | <maejrep> addlist traces p2v(0x1ffc100) |
| 03:39.11 | ppman | did that |
| 03:39.18 | ppman | and the other three you said |
| 03:39.43 | ppman | and it looks like I can't do battery over proc_comm? |
| 03:39.46 | maejrep | hmm, so either that's not your proc comm offset (?), or your battery data is not retrieved from proc comm |
| 03:40.08 | ppman | I'm noticing the htc-msm branch uses rpc to do it... should I try that? |
| 03:40.20 | ppman | or rather, how can I use haret to watch rpc? |
| 03:40.26 | maejrep | possibly.. what chip is it? |
| 03:40.32 | maejrep | I don't know the answer to that |
| 03:40.50 | ppman | the cpu is msm7201, the battery chip is ds2746 |
| 03:40.58 | maejrep | but presumably rpc is just a smem fifo buffer or memory register |
| 03:41.09 | ppman | hmm |
| 03:41.18 | maejrep | so that's probably closer to vogue then |
| 03:41.53 | ppman | and vogue's proc_comm stuff works - I was able to vibrate the motor with 0x17 |
| 03:42.08 | ppman | and that's at that proc_comm offset.. |
| 03:43.07 | maejrep | the one I said ^ ? |
| 03:43.49 | ppman | 0x01f00000 + 0xfc100 for command |
| 03:43.51 | maejrep | it's quite possible that the proc comm implementation is just different |
| 03:43.53 | ppman | yeah |
| 03:44.06 | ppman | but it works, though... |
| 03:44.16 | ppman | and cr2 said it was standard... |
| 03:44.20 | maejrep | well, it can work for vibrate and not for something else :) |
| 03:44.41 | maejrep | were you able to disassemble the battery driver? |
| 03:45.00 | ppman | I can't understand that... it's raw arm assembly.. |
| 03:45.15 | ppman | I did notice some references to I2C... |
| 03:45.35 | ppman | does that mean I have to interface over I2c to the ds2746 itself? |
| 03:45.40 | maejrep | tmzt: |
| 03:45.43 | maejrep | [ 172.215054] mmc0: new SDIO card at address 0002 |
| 03:45.43 | maejrep | [ 172.241239] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066) |
| 03:45.43 | maejrep | [ 172.291440] TIWLAN: Driver initialized (rc 0) |
| 03:45.43 | maejrep | [ 172.304135] TIWLAN: 1251 PG 1.2 |
| 03:45.43 | maejrep | [ 172.311154] TIWLAN: Driver loaded |
| 03:45.58 | maejrep | probably not |
| 03:46.22 | ppman | that's raph? |
| 03:46.32 | maejrep | yeah |
| 03:46.41 | ppman | and does it actually work? |
| 03:46.42 | maejrep | tmzt: get a NULL pointer dereference trying to run iwconfig :/ |
| 03:46.49 | maejrep | not yet :) |
| 03:46.51 | ppman | nice :P |
| 03:47.05 | tmzt | ifconfig |
| 03:47.47 | *** join/#htc-linux deeproot (n=tony@68-112-216-255.dhcp.slid.la.charter.com) |
| 03:47.58 | maejrep | ifconfig showed the wlan device |
| 03:48.04 | tmzt | ifconfig up |
| 03:48.08 | tmzt | then try iwconfig |
| 03:48.14 | maejrep | i'll have to reboot, sec |
| 03:48.44 | maejrep | tiwlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 |
| 03:49.18 | maejrep | still the driver should be able to detect before its gonna hit a null pointer ;x |
| 03:49.29 | ppman | no mac address, tho... |
| 03:49.39 | maejrep | not really a concern :P |
| 03:49.51 | ppman | not unless you want it to work |
| 03:51.02 | maejrep | the kernel can set a mac address, so not a concern ;) |
| 03:51.20 | ppman | the fact that you can't read it is bad, tho... |
| 03:51.45 | ppman | woah... it's late... |
| 03:51.47 | maejrep | yes, I agree |
| 03:51.52 | ppman | I've got exams in the morning.. |
| 03:52.00 | ppman | schweet |
| 03:52.12 | maejrep | tmzt: should we need to provide the firmware for it? |
| 03:55.11 | tmzt | ah, you found the i2c |
| 03:55.26 | tmzt | he left |
| 03:55.41 | tmzt | maejrep: I think so |
| 03:56.22 | maejrep | drivers/net/wireless/tiwlan1251/fw/ |
| 03:56.22 | maejrep | Android.mk tiwlan.ini |
| 03:56.25 | maejrep | hmm, i wonder |
| 03:56.57 | tmzt | the ce version should work though |
| 03:57.58 | *** join/#htc-linux deeproot (n=tony@68-112-216-255.dhcp.slid.la.charter.com) |
| 03:59.13 | maejrep | # ifconfig tiwlan0 up |
| 03:59.13 | maejrep | ifconfig: SIOCSIFFLAGS: Cannot assign requested address |
| 04:00.40 | tmzt | that's right, you need the android netcfg for this driver |
| 04:01.00 | tmzt | someone was working on it, the one who helped us a few days ago |
| 04:02.02 | maejrep | DJ something |
| 04:02.09 | tmzt | DJWillis |
| 04:02.10 | tmzt | yeah |
| 04:02.28 | *** part/#htc-linux chavonbravo (n=cb@fl-71-1-235-8.dhcp.embarqhsd.net) |
| 04:02.30 | maejrep | so that would explain why iwconfig fails |
| 04:02.38 | tmzt | I think you can just build it from the android git though, you also need a program to load the firmware |
| 04:02.38 | maejrep | i do recall him saying wireless-extensions won't work yet |
| 04:02.47 | maejrep | there is one in here |
| 04:02.49 | maejrep | just need to compile it |
| 04:02.51 | tmzt | the driver loads ok though? |
| 04:03.01 | maejrep | and i'm not sure how to build with Android.mk |
| 04:03.06 | maejrep | yeah it loads fine |
| 04:03.14 | maejrep | there's one "misfire" message, but I don't know what it means |
| 04:03.26 | maejrep | I also dropped the max transfer rate from 20M to 12M |
| 04:03.36 | maejrep | just to be safe ... it might work at 20 for all i know |
| 04:04.20 | maejrep | CUDK/tiwlan_loader/tiwlan_loader.c <-- for loading firmware |
| 04:05.25 | tmzt | they released that now? |
| 04:05.30 | tmzt | what's CUDK? |
| 04:06.00 | tmzt | I'm hoping the tool is a few .c files and only need kernel headers |
| 04:06.01 | maejrep | i would guess something related to cupcake maybe? |
| 04:06.07 | maejrep | no, it's not |
| 04:06.32 | maejrep | i mean, I think it kind of is.. |
| 04:06.44 | maejrep | but it still has a lot of dependencies |
| 04:07.00 | tmzt | neccessary ones or just for the build system? |
| 04:07.00 | maejrep | and I don't remember how to build with Android.mk anyway :p |
| 04:07.11 | maejrep | I get the feeling its just for the build system |
| 04:07.13 | *** join/#htc-linux Kewlj1313 (n=Kewlj131@pool-71-120-111-12.ipslin.dsl-w.verizon.net) |
| 04:12.48 | maejrep | copied it to android checkout |
| 04:13.06 | maejrep | it starts to compile, but fails on hardware_legacy/power.h |
| 04:14.03 | maejrep | but i have a feeling even if I compile it, it's only going to run on android |
| 04:17.03 | maejrep | hmm, i wonder what the cmda-import branch is :p |
| 04:23.14 | maejrep | wow, apparently my android repository was way out of sync :p |
| 04:23.19 | maejrep | taking a long time to repo sync |
| 04:28.32 | tmzt | I don't see that at all |
| 04:29.15 | tmzt | and you can just git pull the individual platform/system/core.git |
| 04:29.49 | tmzt | you need netcfg and libnetutils apparently |
| 04:31.39 | maejrep | this is very old.. :p |
| 04:31.51 | maejrep | i haven't synced it since playing with it on my vogue |
| 05:11.16 | *** join/#htc-linux Shinku (i=mooonlit@mario.dreamhost.com) |
| 05:52.26 | tmzt | maejrep: is it working? I'm trying to see if we can use jf1.3 as a root fs to test it |
| 06:04.21 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 06:08.07 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 06:19.45 | *** part/#htc-linux balsa1 (n=kll@87.72.13.87) |
| 06:20.31 | *** join/#htc-linux rob_w (n=bob@p549BF1B2.dip.t-dialin.net) |
| 06:48.07 | *** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net) |
| 07:06.18 | *** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
| 07:10.09 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 07:14.16 | *** join/#htc-linux kiozen (n=oeichler@p54922275.dip0.t-ipconnect.de) |
| 07:15.08 | *** join/#htc-linux lifegrasp (n=ckonkel@82.sub-70-216-166.myvzw.com) |
| 07:30.41 | *** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
| 07:34.56 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 07:43.51 | *** join/#htc-linux lifegrasp_ (n=ckonkel@70-138-169-80.lightspeed.hstntx.sbcglobal.net) |
| 07:48.49 | *** join/#htc-linux Dat30 (n=pocketir@200.92.6.112) |
| 07:49.11 | Dat30 | http://handhelds.org/moin/moin.cgi/HTC_2dPhones |
| 07:50.09 | Dat30 | sorry :D |
| 07:51.12 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
| 07:54.55 | Dat30 | any news about hermes port? |
| 07:58.11 | *** join/#htc-linux kiozen (n=oeichler@p54922275.dip0.t-ipconnect.de) |
| 08:01.11 | *** join/#htc-linux kiozen (n=oeichler@p54922275.dip0.t-ipconnect.de) |
| 08:20.53 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
| 08:21.08 | *** join/#htc-linux techie (n=blarg@ip24-250-212-67.ga.at.cox.net) |
| 09:09.15 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 09:36.13 | *** join/#htc-linux metter (n=metter@124-179.203-62.cust.bluewin.ch) |
| 09:43.17 | Abracadabra | good morning everyone |
| 09:49.28 | lupine_85 | /win/win 2 |
| 09:53.23 | *** join/#htc-linux Mullins (n=bw@89.204.227.186) |
| 09:53.30 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B0363FA.dip.t-dialin.net) |
| 09:57.26 | *** join/#htc-linux NetRipper (n=netrippe@netripper.nl) |
| 10:19.49 | *** join/#htc-linux shoragan_ (n=shoragan@sicherheitsschwankung.de) |
| 10:20.14 | *** join/#htc-linux cr2 (n=cr2@ip-90-186-22-92.web.vodafone.de) |
| 10:21.37 | cr2 | NetRipper: have you seen the wifi news from maejrep in the log ? |
| 10:22.43 | cr2 | maejrep: the firmware loader was part of thre |
| 10:22.48 | cr2 | acx100 driver |
| 10:23.24 | cr2 | so it may be added to the module |
| 10:23.48 | cr2 | maejrep: the wince firmware differs from the g1 firmware |
| 10:24.47 | cr2 | maejrep: on wince it's possible to do a eeprom-less setup ? otherwise it's necessary to read the eeprom contents from NAND |
| 10:28.13 | *** join/#htc-linux NeoS2k7 (n=neos2k7@82-136-223-208.ip.telfort.nl) |
| 10:58.05 | NetRipper | cr2, no i havent read it? can you give a 1-line summary? |
| 10:58.06 | NetRipper | :) |
| 11:02.09 | cr2 | NetRipper: the wifi sdio part is detected, and the driver is loaded |
| 11:02.18 | cr2 | kiozen: http://garmin.blogs.com/pr/2009/01/introducing-basecamp-garmins-new-tool-for-planning-and-reviewing-all-of-your-outdoor-adventures.html?activeBranchId=newsroom |
| 11:03.53 | NetRipper | cr2, ah nice |
| 11:04.18 | cr2 | NetRipper: but there are still many software bugs to be fixed. |
| 11:04.22 | NetRipper | ok |
| 11:05.17 | cr2 | NetRipper: will you be merging the new patches ? |
| 11:05.31 | NetRipper | cr2, i havent received any new patches yet |
| 11:05.31 | NetRipper | :) |
| 11:05.35 | NetRipper | but yes i will |
| 11:05.56 | NetRipper | im also still working on my ts driver.. which, because it is interrupt based now, requires work on vkeyb and msmfb driver |
| 11:06.11 | cr2 | NetRipper: you can remove the TROUT_* things from .h |
| 11:07.03 | cr2 | and it will be nice to ifdef the android specific things |
| 11:07.16 | NetRipper | which android-specific things? |
| 11:07.47 | cr2 | those that are needed to make android run properly |
| 11:08.39 | cr2 | ts calibration, onscreen keyboard, etc |
| 11:09.20 | *** join/#htc-linux x15 (n=x15@rch85-2-88-163-223-132.fbx.proxad.net) |
| 11:12.16 | NetRipper | ts calibration and onscreen keyboard are not neccesarily android-specific |
| 11:14.20 | NetRipper | vkeyb is already a Kconfig option btw |
| 11:14.27 | NetRipper | but regarding calibration i'll see what i can do |
| 11:14.27 | NetRipper | :) |
| 11:16.22 | cr2 | and i see a lot of changes needed for the lcd panel init |
| 11:16.58 | cr2 | because our toshiba setup is different from g1, and epson needs a completely different setup anyway |
| 11:17.10 | *** part/#htc-linux x15 (n=x15@rch85-2-88-163-223-132.fbx.proxad.net) |
| 11:17.35 | cr2 | maybe this 444 problem is cause by the irrelevant g1 code parts |
| 11:17.46 | cr2 | which do not apply to epson. |
| 11:24.10 | *** join/#htc-linux timebomb (n=tb@p5B3E55E9.dip.t-dialin.net) |
| 11:27.14 | cr2 | NetRipper: have you tried the g1 memory setup ? i'll try do document it and add to wiki |
| 11:32.05 | NetRipper | cr2, no still havent.. |
| 11:32.37 | *** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl) |
| 11:41.07 | *** join/#htc-linux ImCoKeMaN (n=imcokema@pool-98-111-118-30.hrbgpa.fios.verizon.net) |
| 11:58.06 | *** join/#htc-linux PhoenixMage (n=Luke@ppp254-28.static.internode.on.net) |
| 11:59.52 | cr2 | NetRipper: linux should run faster i guess, and we can free more dram |
| 12:02.48 | *** part/#htc-linux PhoenixMage (n=Luke@ppp254-28.static.internode.on.net) |
| 12:20.42 | *** join/#htc-linux cr2 (n=cr2@ip-90-186-22-92.web.vodafone.de) |
| 12:23.37 | *** join/#htc-linux zycho (n=zycho@a89-182-25-58.net-htp.de) |
| 13:09.03 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 13:10.53 | *** join/#htc-linux piusvelte (i=42e35ff0@gateway/web/ajax/mibbit.com/x-caad9701fdcc9a19) |
| 13:19.50 | *** join/#htc-linux _MasterPrenium (n=MasterPr@ALille-257-1-82-233.w83-204.abo.wanadoo.fr) |
| 13:33.40 | *** join/#htc-linux ginge_ (n=chatzill@host81-149-155-58.in-addr.btopenworld.com) |
| 13:35.30 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@pal-179-241.itap.purdue.edu) |
| 13:39.30 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@pal-179-241.itap.purdue.edu) |
| 14:06.50 | *** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215) |
| 14:18.22 | *** join/#htc-linux piusvelte (i=42e35ff0@gateway/web/ajax/mibbit.com/x-4c33fd4ca0a38b60) |
| 14:30.53 | Mullins | does anyone know which bitbake image dcordes would use as default? I am thinking console-image |
| 14:33.19 | *** join/#htc-linux sdt5551 (n=titus@147.145.40.44) |
| 14:35.58 | *** join/#htc-linux piusvelte (i=42e35ff0@gateway/web/ajax/mibbit.com/x-3ccb43110bd80ab0) |
| 14:38.24 | *** join/#htc-linux lifegrasp (n=ckonkel@63.254.171.226) |
| 14:39.57 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
| 14:47.00 | *** join/#htc-linux piusvelte (i=42e35ff0@gateway/web/ajax/mibbit.com/x-f0aabc32794b88b3) |
| 14:48.45 | *** join/#htc-linux piusvelte (i=42e35ff0@gateway/web/ajax/mibbit.com/x-fc60e279ef3636ed) |
| 14:51.18 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@pal-161-149.itap.purdue.edu) |
| 14:53.32 | *** join/#htc-linux Mullins (n=bw@89.204.227.186) |
| 15:03.20 | *** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com) |
| 15:06.37 | *** join/#htc-linux Kewlj1313-Bahh (i=Kewlj131@kb017wk00.tech.purdue.edu) |
| 15:11.29 | *** join/#htc-linux myxor (n=myxor@pdbn-4d08940e.pool.mediaWays.net) |
| 15:41.01 | *** join/#htc-linux MethoS (n=lem@host-091-097-244-130.ewe-ip-backbone.de) |
| 15:41.19 | *** join/#htc-linux H2Nox-318Ti (n=H2Nox@modemcable187.84-130-66.mc.videotron.ca) |
| 15:41.57 | H2Nox-318Ti | HTC appache please help ! Jump to kernel for eternel...... |
| 15:42.15 | H2Nox-318Ti | model pcc6700 bell |
| 15:42.16 | AstainHellbring | wow apache old stuff there |
| 15:42.29 | H2Nox-318Ti | hy say |
| 15:42.55 | H2Nox-318Ti | also you recommend wath model for linux and the best wifi chipset |
| 15:43.10 | H2Nox-318Ti | model phone |
| 15:43.16 | H2Nox-318Ti | are you recommend |
| 15:43.33 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-fe4a103d4e0e7c56) |
| 15:43.49 | H2Nox-318Ti | because i have beammer modded computer in my car with router 350N full linux |
| 15:44.12 | AstainHellbring | I don't think there is much of any support for apache running linux still |
| 15:44.18 | H2Nox-318Ti | my idea if build slax base with my script for aircrack... |
| 15:44.40 | H2Nox-318Ti | just console in phone no roaming |
| 15:45.36 | H2Nox-318Ti | <PROTECTED> |
| 15:46.23 | H2Nox-318Ti | i will try to linux for music and web navigation withmy 350n modded mobile router.... |
| 15:46.42 | H2Nox-318Ti | also Linux Hermet if not boot |
| 15:47.17 | H2Nox-318Ti | <PROTECTED> |
| 15:47.38 | AstainHellbring | H2Nox-318Ti lots of time is still needed in dev work for apache linux |
| 15:47.39 | H2Nox-318Ti | ok |
| 15:48.47 | H2Nox-318Ti | but im perseverant and say to see in my phone fedora.... im workink for booting and we reply for my conclusion ...... IF ok....... ? |
| 15:49.37 | AstainHellbring | you won't want fedora on your phone |
| 15:49.44 | AstainHellbring | its ram alone is far to low to do anything |
| 15:49.59 | H2Nox-318Ti | also im love slax for BT3 and bt3 im not secret for me... |
| 15:50.20 | AstainHellbring | and remeber your phone is an arm proc not an x86 |
| 15:51.49 | *** join/#htc-linux ykut_johny (n=ykut_joh@www.mitsa.org.my) |
| 15:51.50 | H2Nox-318Ti | yes before my accident i made it ...... im retreive document in the net ... My document with mutli hermes boot ... my brain souvenirs fedora just now.... |
| 15:52.15 | H2Nox-318Ti | ok yes for GPIO prossesor ...yes ARM .... same on my router |
| 15:52.40 | H2Nox-318Ti | jus hi have many c++ compiler for many many chips and ic.. chipset etc etc |
| 15:53.10 | H2Nox-318Ti | im working for hacking bev ... in quebec .... before my accident |
| 15:53.31 | H2Nox-318Ti | i descover the chipset and many many ic if linux script |
| 15:54.12 | H2Nox-318Ti | hi LOVE linux in general....heheheheh ok im working and we reply |
| 15:54.26 | AstainHellbring | well sounds like you're ready to start coding drivers for the apache |
| 15:55.50 | H2Nox-318Ti | for my appache because i dont have anoter phone for working in wifi .... in my contry an rescession...grrrrrrrrrrrrr alose for just info wath best phone for working linux and wifi -bluetooth |
| 15:57.40 | *** join/#htc-linux myxor (n=myxor@pdbn-4d08940e.pool.mediaWays.net) |
| 16:25.19 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
| 16:26.01 | *** part/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 16:32.41 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 16:33.08 | NetRipper | AstainHellbring, im amazed you could understand him |
| 16:33.24 | AstainHellbring | me too |
| 16:34.54 | *** join/#htc-linux techie (n=blarg@ip24-250-212-67.ga.at.cox.net) |
| 16:40.38 | AstainHellbring | so NetRipper whats new? |
| 16:43.37 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@pal-161-144.itap.purdue.edu) |
| 16:56.21 | *** join/#htc-linux frugo3000 (i=frugo300@cpp.1337.cx) |
| 16:56.29 | frugo3000 | hi ;) |
| 16:57.21 | AstainHellbring | hi frugo3000 |
| 17:13.30 | *** join/#htc-linux MasterPrenium (n=MasterPr@ALille-257-1-33-162.w83-204.abo.wanadoo.fr) |
| 17:18.22 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 17:30.35 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
| 17:33.57 | *** join/#htc-linux exco (n=exco@e181120200.adsl.alicedsl.de) |
| 17:34.47 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 17:47.10 | *** join/#htc-linux stefan_schmidt_ (n=stefan@p5B034A83.dip.t-dialin.net) |
| 17:48.15 | AstainHellbring | morning guys |
| 18:14.58 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
| 18:15.15 | Rogro82 | hi all... |
| 18:17.02 | Rogro82 | exco: finished on the backlight stuff... can now set the brightness from within android. will post up a zImage when ive tested it completely |
| 18:17.20 | exco | I've just read your post |
| 18:17.24 | exco | Great job |
| 18:17.51 | Rogro82 | thanks... its a small thing but was enough to fill the day at work :) |
| 18:18.45 | exco | any news on battery-management from ppman? |
| 18:20.27 | Rogro82 | no... ill just pick it up myself. scanned through the memory but somehow the offset the raph has on there wiki is empty.. so i just continued on the backlight because i still needed the right values from winmo so just checked that memory first |
| 18:23.00 | exco | what do you need to do to find to get battery management working - and more importand - can I help? |
| 18:23.39 | exco | *something's wrong with that sencence |
| 18:24.38 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@pal-160-066.itap.purdue.edu) |
| 18:28.26 | Rogro82 | exco: well need to find the right memory address |
| 18:28.54 | Rogro82 | exco: you know how to connect using haretconsole? |
| 18:30.13 | Rogro82 | exco: can teach you how to search through the mem |
| 18:34.30 | exco | Rogro82: that sounds good to me |
| 18:35.15 | Rogro82 | ok start up haretconsole |
| 18:36.03 | exco | connected |
| 18:36.55 | Rogro82 | ok i already have the physical smem address from msm_iomap so that makes it easier |
| 18:38.07 | exco | good |
| 18:38.19 | Rogro82 | to get the virtual address type "dump mmu 2 0x01F00000 0x2" |
| 18:38.39 | exco | done |
| 18:38.48 | Rogro82 | now you see the mappings |
| 18:39.02 | exco | <PROTECTED> |
| 18:39.02 | exco | 95100000 | 01f00000 | 1MB section | AP=1 T=7 |
| 18:39.02 | exco | b5100000 | 01f00000 | 1MB section | AP=1 T=7 |
| 18:40.12 | Rogro82 | ok type "vdump 0xb5100000 0x0000FFFF" |
| 18:40.48 | exco | running |
| 18:40.50 | Rogro82 | last parameter is the size so you can search through more... with the first you can set the start address so you can narrow down where to look |
| 18:41.07 | AstainHellbring | exco Rogro82 what device you guys working on? |
| 18:41.16 | Rogro82 | polaris |
| 18:41.54 | Rogro82 | exco: you can also make one large scan... look at the haret log created and then narrow down on your findings |
| 18:42.24 | Rogro82 | exco: a lot of things are already known and in the raph wiki ( research / memory ) |
| 18:43.01 | Rogro82 | exco: but the offset for their battery address is empty |
| 18:43.21 | exco | what are we looking for |
| 18:43.54 | exco | and no haretlog shows up so far |
| 18:44.19 | Rogro82 | exco: i dont know what the battery memory looks like... most likely cr2 or someone else here can help you |
| 18:44.27 | Rogro82 | exco: not in the haretconsole folder? |
| 18:44.38 | exco | Rogro82: nope |
| 18:44.50 | Rogro82 | hmmm maybe youll need to scan some more or turn it on |
| 18:46.05 | Rogro82 | you can also turn it on yourself.... just type LOG [filename] |
| 18:47.24 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfe7f9.pool.einsundeins.de) |
| 18:48.04 | Rogro82 | according to the vogue/raph the battery should be around 0xb51fc100 |
| 18:49.09 | Rogro82 | 0xb51fc020 is radio version |
| 18:49.12 | tmzt | are you looking for w1 host on arm11? |
| 18:49.17 | tmzt | s/for/for a/ |
| 18:51.03 | Rogro82 | tmzt: trying to find the battery status memory address |
| 18:51.15 | tmzt | in smem? |
| 18:51.31 | Rogro82 | its in smem isnt it? |
| 18:51.56 | tmzt | I don't know, I assumed the ds chip was on a w1 bus but I guess that's hidden on the arm9 |
| 18:52.43 | Rogro82 | according to the vogue code and the raph wiki it should be in smem |
| 18:53.10 | Rogro82 | but both addresses from the vogue and the raph turn up empty for me... |
| 18:53.33 | Rogro82 | while a lot of others from the raph are the same |
| 18:56.17 | Rogro82 | well actually the vogue one is showing me something... but it doesnt look it will be from the battery |
| 18:58.43 | Rogro82 | looks more like a timer... |
| 18:59.14 | exco | is the output of vogue/raphael available for comparison? |
| 19:00.01 | Rogro82 | no only the address and output for some others |
| 19:01.04 | Rogro82 | thats why im looking for someone that can tell me what it should look like... :) can identify a lot of other stuff but havent found anything that i think is actually the battery |
| 19:01.38 | exco | so to find out the address we have to dump change battery charge - dump again and look for changes? |
| 19:02.00 | exco | how big is smem? |
| 19:02.08 | Rogro82 | 1mb |
| 19:02.33 | exco | so there'll be 1000s of changes I guess |
| 19:02.52 | Rogro82 | if not more :) |
| 19:03.21 | Rogro82 | its better to rule out addresses and write the ones down and add them to a wiki page |
| 19:03.23 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87ee7c.pool.einsundeins.de) |
| 19:03.32 | Rogro82 | like the raph one |
| 19:04.40 | exco | http://wiki.xda-developers.com/index.php?pagename=RaphaelDEX ? |
| 19:04.46 | Rogro82 | yes |
| 19:05.02 | Rogro82 | no not that one |
| 19:05.05 | Rogro82 | one sec |
| 19:05.43 | Rogro82 | thats proc_comm page youll need this one http://wiki.xda-developers.com/index.php?pagename=RaphaelMemoryMap |
| 19:07.22 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
| 19:10.25 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 19:17.57 | *** join/#htc-linux techie (n=blarg@ip24-250-212-67.ga.at.cox.net) |
| 19:18.06 | exco | can't we find the right address in battery.dll? |
| 19:18.25 | exco | battdrvr.dll I mean |
| 19:21.48 | Rogro82 | havent had time to go through it yet |
| 19:22.41 | *** join/#htc-linux hollo (n=hollo@3e6b025d.rev.stofanet.dk) |
| 19:25.04 | exco | maybe faster than looking through smem without knowing what to look for ? |
| 19:29.24 | Rogro82 | ill take a look at it |
| 19:32.25 | *** join/#htc-linux Kewlj1313 (i=Kewlj131@dynamicip129.ics.purdue.edu) |
| 19:33.17 | exco | bbiab |
| 19:55.02 | *** join/#htc-linux myxor (n=myxor@pdbn-4d08940e.pool.mediaWays.net) |
| 19:57.47 | *** join/#htc-linux cr2 (n=cr2@ip-90-186-166-134.web.vodafone.de) |
| 19:59.57 | Rogro82 | cr2 how can i find the memory offset of the battery status in battdrv.dll using ida |
| 20:00.56 | Rogro82 | cr2: have been looking at the memory in smem but somehow i think the raph differs from the polaris... everything near the offset in raph wiki is empty |
| 20:01.39 | cr2 | Rogro82: where can i get battdrv ? |
| 20:01.54 | Rogro82 | from the windows folder |
| 20:02.05 | Rogro82 | want me to upload it? |
| 20:02.09 | cr2 | yes |
| 20:03.15 | Rogro82 | http://rapidshare.com/files/191264972/battdrvr.zip |
| 20:03.22 | cr2 | ok |
| 20:08.14 | *** part/#htc-linux sdt5551 (n=titus@147.145.40.44) |
| 20:09.41 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-240.ph.ph.cox.net) |
| 20:10.18 | *** join/#htc-linux cr2 (n=cr2@ip-77-25-177-78.web.vodafone.de) |
| 20:11.08 | *** join/#htc-linux techie (n=blarg@ip24-250-212-67.ga.at.cox.net) |
| 20:16.00 | cr2 | Rogro82: hm. it seems that the DS is accessed directly over i2c |
| 20:16.25 | cr2 | Rogro82: what was the exact DS number ? i think we can get the datasheet |
| 20:17.08 | Rogro82 | cr2: Ive seen the i2c stuff in there |
| 20:17.23 | *** join/#htc-linux sdt5551 (n=titus@147.145.40.44) |
| 20:17.26 | *** part/#htc-linux sdt5551 (n=titus@147.145.40.44) |
| 20:17.55 | cr2 | i'll che3ck the gpios first |
| 20:19.00 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 20:19.25 | Rogro82 | hi dcordes |
| 20:20.56 | cr2 | Rogro82: gpio1 , what is it doing ? |
| 20:21.07 | Rogro82 | which bank? |
| 20:21.13 | cr2 | 1 |
| 20:21.23 | Rogro82 | dont think its registered yet |
| 20:22.48 | *** join/#htc-linux Sti_0231 (n=Where_is@110.202-65-87.adsl-dyn.isp.belgacom.be) |
| 20:23.03 | cr2 | what is fc00c ? |
| 20:23.13 | dcordes | hi |
| 20:23.32 | Rogro82 | cr2: in smem? |
| 20:23.44 | cr2 | yes |
| 20:23.50 | dcordes | Rogro82: are the last changes still uptodate? |
| 20:23.50 | cr2 | you have cpld too ? |
| 20:23.53 | Rogro82 | shows just one |
| 20:24.37 | Rogro82 | dcordes: worked out the backlight stuff so its now possible to adjust the backlight in android but i can commit that later on |
| 20:26.05 | cr2 | Rogro82: which device do you have ? |
| 20:26.30 | Rogro82 | cr2: polaris |
| 20:27.00 | cr2 | is the cpld layout the same as on kais ? |
| 20:27.47 | Rogro82 | cr2: lemme check |
| 20:27.58 | Rogro82 | cr2: most stuff is the same as kais |
| 20:28.08 | cr2 | cpld 5,8 and 5,4. gpio1 |
| 20:28.51 | cr2 | do you remember the wince led ioctls ? |
| 20:30.15 | Rogro82 | cr2: i dont have them yet |
| 20:30.17 | dcordes | Rogro82: ok did you get the private message I sent? |
| 20:31.16 | cr2 | Rogro82: can you trace the i2c reads and writes ? |
| 20:31.46 | Rogro82 | cr2: how do i do that? |
| 20:32.13 | cr2 | dump the virtual mappings for 0xa9900000 first |
| 20:33.36 | cr2 | i2c_id 6c, hmm, probably 0x36 as usual. |
| 20:34.03 | Rogro82 | mappings are 91f00000 b1f00000 |
| 20:34.35 | cr2 | add the 0x0 4 and 0x8 4 addreeses to mmutrace |
| 20:36.45 | cr2 | hm. not 8 |
| 20:36.55 | cr2 | +0xc and +0x0 |
| 20:38.02 | cr2 | kaiserbat says ds2746 over i2c |
| 20:39.03 | cr2 | dcordes: do you support the battery monitor ? |
| 20:39.35 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 20:40.29 | *** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it) |
| 20:40.53 | dcordes | cr2: no but dzo has it working on the vogue. he said it should be possible to make it work for kaiser in no time |
| 20:41.07 | cr2 | dcordes: over i2c ? |
| 20:42.40 | cr2 | 0110110 |
| 20:42.42 | dcordes | cr2: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob_plain;f=arch/arm/mach-msm/battery.c;h=b8ef1ea8753fcb2ff48f4e83c938665cd04ae615;hb=refs/heads/htc-vogue |
| 20:42.46 | cr2 | 0x36 |
| 20:42.51 | cr2 | yes, that's the id |
| 20:45.20 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 20:45.25 | Untouchab1e | Good evening ^^ |
| 20:45.58 | cr2 | dcordes: i don't see i2c there. |
| 20:46.39 | cr2 | dcordes: and the world will be a better place if the htc-egpio is used ;) |
| 20:47.03 | cr2 | DS2746 has a good datasheet |
| 20:47.33 | *** join/#htc-linux timebomb (n=tb@e176110175.adsl.alicedsl.de) |
| 20:49.00 | dcordes | bbl |
| 20:49.11 | cr2 | i see a ds2746 driver on some chinese site. |
| 20:52.54 | cr2 | but it's not much more than i2c-tools |
| 20:59.24 | cr2 | Rogro82: the kaiser_cpld does not have battery gpios |
| 20:59.54 | cr2 | and gpio1 is light sensor input |
| 21:00.10 | cr2 | so it's completely different |
| 21:01.06 | cr2 | tmzt: is there a pwm api in linux-arm ? |
| 21:07.31 | *** join/#htc-linux pl_levy (n=chatzill@aatc24.neoplus.adsl.tpnet.pl) |
| 21:34.06 | Untouchab1e | Anyone here atm? |
| 21:36.32 | Untouchab1e | Just wondering what the difference between msmsdcc_id = 2 and 3 is |
| 21:37.55 | *** join/#htc-linux Xime (n=xime@bankize.net) |
| 21:40.43 | cr2 | Untouchab1e: if your device is properly supported, then you don't need to care about it :) |
| 21:41.03 | cr2 | look at the MSM_SDIO wiki page |
| 21:42.23 | Untouchab1e | I am thinking in regards to raph100/800 |
| 21:42.37 | Untouchab1e | some fuze users have been having problems with the default msmsdcc_id = 2 |
| 21:42.41 | Untouchab1e | and need to change to 3 |
| 21:42.49 | Untouchab1e | just trying to figure out what the difference is |
| 21:43.18 | cr2 | raph110 ? |
| 21:43.39 | AstainHellbring | yes fuze is 110 |
| 21:43.40 | Untouchab1e | raph100/110/500/800 then |
| 21:43.47 | cr2 | it's the sd controller numbers. there are 4 of them on A cpu |
| 21:43.49 | Untouchab1e | ah, the fuze is 110 ok.. |
| 21:44.21 | Untouchab1e | but bottom line, should fuze users have msmsdcc_id = 3 then? |
| 21:44.44 | cr2 | what does wiki say ? |
| 21:45.03 | cr2 | do they have microSD slot ? |
| 21:45.48 | AstainHellbring | yes fuze has microSD slot |
| 21:46.44 | *** join/#htc-linux zycho (n=zycho@a89-182-25-58.net-htp.de) |
| 21:46.45 | cr2 | AstainHellbring: is there raph110 spl somewhere ? |
| 21:47.19 | AstainHellbring | we might have one but I know for hardspl/whatever raph100 hardspl works fine on 110 |
| 21:47.57 | Untouchab1e | for instance, some fuze users (if not all?) have problems booting android with alot of various "Not found" errors when trying to load up |
| 21:48.26 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-240.ph.ph.cox.net) |
| 21:48.32 | Untouchab1e | dont know if changing msmsdcc_id from 2 to 3 would solve that |
| 21:48.43 | cr2 | Untouchab1e: unlikely |
| 21:48.57 | *** join/#htc-linux MethoS (n=lem@host-091-097-244-130.ewe-ip-backbone.de) |
| 21:49.03 | Untouchab1e | hmm, what would then? |
| 21:49.11 | Untouchab1e | i read something interessting.. h/o |
| 21:49.11 | cr2 | Untouchab1e: it may be the sd detection gpio, but the spl is needed to check it. |
| 21:49.46 | Untouchab1e | SD card being mounted as mmc0 instead of mmc |
| 21:55.41 | Untouchab1e | How would you solve it? |
| 21:56.34 | Balsat | Can't you make a symlink? |
| 22:05.02 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 22:06.23 | MethoS | what about deleteing the partition table and making the filesystem directly on mmc? |
| 22:07.47 | *** join/#htc-linux techie (n=blarg@n128-227-98-190.xlate.ufl.edu) |
| 22:18.43 | *** join/#htc-linux lifegrasp (n=ckonkel@63.254.171.226) |
| 22:20.51 | Rogro82 | cr2: sorry i had to go do some stuff... so the battery on polaris is controlled through i2c |
| 22:22.24 | *** join/#htc-linux _defcon (n=ion@ip68-227-227-240.ph.ph.cox.net) |
| 22:27.32 | imfloflo | rogro brightness working good |
| 22:28.42 | Rogro82 | thnx for the info imfloflo :) |
| 22:29.16 | Rogro82 | going to change the keypad backlight so that it will only switch on when keys are pressed... |
| 22:29.23 | Rogro82 | seems more natural |
| 22:29.43 | exco | Rogro82: backlight adjustment works fine |
| 22:29.52 | imfloflo | brightness only decrease increase screen light or keypad too ? |
| 22:30.10 | Rogro82 | only normal backlight |
| 22:30.36 | exco | Rogro82: power button still has the issue when turned off - you press power too long - it turns on and off again |
| 22:30.38 | Rogro82 | its nice to see it fade out when you press the power button. |
| 22:30.51 | Rogro82 | exco: i know... next one to finish |
| 22:30.52 | Rogro82 | :) |
| 22:31.08 | Rogro82 | ill also add the wheel to the driver this weekend |
| 22:31.34 | imfloflo | and fade in when i power on :) |
| 22:32.20 | Rogro82 | i guess ill have to add a delay so that it isnt as sensible when you touch it a bit |
| 22:33.33 | Rogro82 | the first thing we have before others :) working backlight in android :P |
| 22:34.21 | imfloflo | then the battery :p and the statut of charge or not in charge |
| 22:34.47 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-240.ph.ph.cox.net) |
| 22:35.24 | Rogro82 | hmmmm well the battery is another story.. cr2 looked at out battery driver and said its controlled by i2c... so i guess that will become a bit more work |
| 22:35.47 | exco | "add a delay" ... don't think that's the right way |
| 22:36.26 | imfloflo | off for today and tomorrow having Solaris evaluation :s, night guys |
| 22:37.57 | Rogro82 | night |
| 22:38.10 | Rogro82 | exco a delay before it gets triggered |
| 22:38.41 | Rogro82 | so you wont accidentily touch it |
| 22:38.52 | exco | imfloflo: what changed with mullins system.img? |
| 22:39.01 | Rogro82 | and scrolls all over the screen |
| 22:41.59 | Rogro82 | cr2: you asked me about fc00c... i checked yesterday and it did report 0/1 on changes of the usb connector... |
| 22:44.46 | imfloflo | exco the logo at the boot and the lastest code for sms but for me with this no call an no sms :s |
| 22:46.51 | exco | no call and no sms probably means libreference-ril.so hasn't been replaced |
| 22:47.51 | Rogro82 | already told mullins that and he replaced the system.img with a new one which has the new libreference-ril.so... look over in the kaiser thread should be there |
| 22:48.33 | imfloflo | http://muinim.com/android/ |
| 22:49.43 | Rogro82 | dont know if thats the right one... but the one i got has the right logo and sms works |
| 22:49.56 | cr2 | Rogro82: ok, so it's the usb detect |
| 22:51.10 | Rogro82 | cr2: i guess so, or could it be power supply? |
| 22:51.50 | Rogro82 | cr2: are other devices also using battery over i2c? |
| 22:54.08 | exco | Rogro82: poly_poly-man "I'm looking to write a driver for the ds2746 - doesn't look too hard, simplay a job of taking the ds2760 code, replacing all w1 stuff with i2c, and dropping the temperature readings... " |
| 22:54.08 | exco | http://forum.xda-developers.com/showpost.php?p=3199540&postcount=2201 |
| 22:54.40 | exco | so on kaiser it is also through i2c |
| 22:54.59 | cr2 | Rogro82: you need to enable different gpios, depending on usb/ac. the i2c chip is monitoring the battery |
| 22:58.51 | Rogro82 | so ill have to look in oem_misc.dll which is the i2c driver isnt it? |
| 22:59.16 | *** join/#htc-linux sdt5551 (n=titus@147.145.40.44) |
| 23:02.20 | Rogro82 | k gotta go to bed... bye all |
| 23:03.02 | exco | bye |
| 23:24.42 | *** join/#htc-linux t3chi3 (n=blarg@n128-227-67-244.xlate.ufl.edu) |
| 23:29.51 | *** join/#htc-linux balsa1 (n=kll@87.72.13.87) |
| 23:43.38 | *** part/#htc-linux exco (n=exco@e181120200.adsl.alicedsl.de) |
| 23:44.18 | cr2 | maejrep[w]: still working ?i |
| 23:51.14 | *** join/#htc-linux Moku (n=John@g227193084.adsl.alicedsl.de) |
| 23:57.00 | maejrep[w] | yeah |
| 23:57.03 | maejrep[w] | about to leave |
| 23:57.24 | cr2 | i've read about the wifi |
| 23:57.33 | balsa1 | mo |
| 23:57.42 | balsa1 | ups |
| 23:58.53 | *** join/#htc-linux lifegrasp_ (n=ckonkel@63.254.171.226) |