00:00.00 | NetRipper | is it |
00:00.14 | NetRipper | so it says 48mhz but in fact it's 32? so it's a displaying issue? |
00:00.15 | cr2 | it is 32 |
00:00.27 | NetRipper | <PROTECTED> |
00:00.34 | cr2 | the divisors are for 32MHz |
00:00.38 | NetRipper | ok |
00:00.45 | cr2 | so you can change it |
00:00.54 | NetRipper | so should change it to MSM_CLOCK_REG(32000000, 1, 0x0c, 0x06, 1, 3, 1, 1), /* 32MHz */ |
00:01.00 | cr2 | don't need to cheat like htc |
00:01.04 | NetRipper | lol |
00:01.04 | cr2 | yes |
00:01.21 | cr2 | and the 19 should be 19.2 |
00:01.33 | NetRipper | ok |
00:01.35 | dcordes | android git has a broadcomm sdio wifi |
00:02.18 | cr2 | wee :) |
00:02.21 | cr2 | <PROTECTED> |
00:02.45 | NetRipper | cr2, i'll commit this stuff after i done j0b0's patches.. |
00:02.53 | cr2 | ok |
00:03.06 | cr2 | you use 8GB sd card ? |
00:03.07 | NetRipper | i think wifi is ok enough to commit.. it can be tweaked afterwards |
00:03.10 | NetRipper | yes |
00:03.15 | cr2 | ok |
00:03.30 | dcordes | I hope with the j0b0 patches the micro* works on kovsky |
00:03.46 | dcordes | noooooo don't commit the wifi |
00:03.57 | NetRipper | eh? |
00:03.59 | cr2 | dcordes: the command set is different |
00:04.03 | NetRipper | dcordes, why not |
00:04.49 | dcordes | cr2, the kernel paniced for a different reason |
00:05.46 | cr2 | NetRipper: the 11Mbit is hardcoded in the driver ? |
00:06.02 | cr2 | afair wince starts wifi detect at 144kHz |
00:06.04 | NetRipper | cr2, i dont know, havent memorized the source |
00:06.04 | NetRipper | ;) |
00:06.11 | NetRipper | yes it does detect at 144khz |
00:06.22 | cr2 | 11MHz, not Mbit |
00:06.26 | NetRipper | see dmesg.. it first sets 144khz.. after that it changes to 11mhz |
00:06.41 | cr2 | for SD |
00:06.43 | NetRipper | when the module is loading |
00:06.46 | NetRipper | no, for wifi |
00:06.57 | NetRipper | for sd it detects at 144khz, then changes to 48mhz/32mhz |
00:07.04 | cr2 | [ 58.891730] clk_set_rate 19:11000000 |
00:07.05 | cr2 | [ 58.950324] clock-wince: set_sdcc_host_clock( 19, 12000000 ) |
00:07.09 | NetRipper | yes |
00:07.17 | NetRipper | 19 = SDC1 = wifi |
00:07.18 | cr2 | it's wifi ? |
00:07.29 | NetRipper | 21 = SDC2 = sd card |
00:07.38 | cr2 | why it starts at 12 ? |
00:08.14 | NetRipper | 11mhz is not defined |
00:08.20 | NetRipper | so it uses 12mhz |
00:08.23 | NetRipper | weird logic though |
00:08.23 | dcordes | NetRipper, I'll take care of the tiwlan vs git thing. |
00:08.24 | NetRipper | i guess |
00:08.34 | dcordes | my rtc says I want sleep |
00:08.36 | dcordes | gnight |
00:08.42 | NetRipper | dcordes, is it a legal issue that i cant commit it |
00:08.59 | NetRipper | or is it a preference? |
00:08.59 | NetRipper | :) |
00:09.01 | cr2 | NetRipper: ? |
00:09.07 | cr2 | tiacx is gpl |
00:09.40 | NetRipper | well i was confused by dcordes' < dcordes> noooooo don't commit the wifi |
00:09.43 | cr2 | but i don't understand why it starts at 11MHz |
00:09.51 | NetRipper | it starts at 144khz, look further back |
00:10.05 | NetRipper | [ 1.317908] clk_set_rate 19:144000 |
00:10.10 | NetRipper | [ 1.467536] clk_set_rate 21:144000 |
00:10.15 | NetRipper | then it detects |
00:10.30 | cr2 | but not on module load ? |
00:10.56 | NetRipper | no, when module loads, it probably detects it can go faster. so it issues a 11mhz request |
00:11.00 | cr2 | wtf it starts so early ? |
00:11.21 | NetRipper | take a breath cr2 |
00:11.36 | NetRipper | the mmc is compiled in.. so mmc0 and mmc1 are created at bootup |
00:11.53 | NetRipper | mmc0 is wifi, mmc1 is sd card |
00:12.13 | NetRipper | mmc1 inits first, it's compiled into the kernel... it changes clock to 48/32mhz |
00:12.31 | cr2 | ok |
00:12.33 | NetRipper | well, the msm_sdcc driver does, not mmc |
00:12.41 | NetRipper | after that wlan.ko loads |
00:13.03 | cr2 | so is the 11MHz hardcoded ? |
00:13.21 | maejrep[w] | its in pdata |
00:13.23 | NetRipper | it probably (im using probably, as i havent inspected the code) detects the device on mmc0.. and also detects it can go at a different frequency (or it might be hardcoded).. |
00:13.34 | cr2 | i dont know the clock matching algorithm, but imho it should take the first slower rate |
00:13.43 | maejrep[w] | trout sets it to 20000000 in pdata |
00:13.46 | maejrep[w] | we could try the same |
00:14.00 | maejrep[w] | and no, it takes the next faster rate |
00:14.09 | cr2 | weird |
00:14.09 | maejrep[w] | (so 11MHz selects 12MHz as the rate) |
00:14.16 | maejrep[w] | I didn't write the code :p |
00:14.24 | cr2 | hehe |
00:14.31 | maejrep[w] | if you think it should be the slower one, that can be done easily |
00:14.34 | cr2 | this is a strange logic |
00:14.46 | NetRipper | i think it's googles |
00:14.54 | cr2 | to take higher frequency |
00:14.59 | NetRipper | yes |
00:15.10 | maejrep[w] | actually I think it was from vogue |
00:15.23 | maejrep[w] | as google doesn't have to cycle through hard coded clock params |
00:15.35 | cr2 | ok |
00:15.41 | maejrep[w] | NetRipper: why does dcordes not want wifi in git? |
00:15.46 | NetRipper | i dont know |
00:15.50 | NetRipper | he left before explaining |
00:16.12 | maejrep[w] | [19:08:23] <dcordes> NetRipper, I'll take care of the tiwlan vs git thing. |
00:16.13 | maejrep[w] | :x |
00:16.26 | cr2 | i'll check what speed wince uses |
00:16.45 | maejrep[w] | NetRipper: regardless, you should be able to commit the -mmc file, and wlan.ko can just be inserted separately |
00:16.51 | cr2 | it starts with 144, that's for sure. but then switches to 12 i think. but i need to check |
00:17.03 | NetRipper | maejrep[w], i guess yea but i comitted it locally already, just didnt push ;) |
00:17.04 | lupine_85 | well, if you're requesting a particular frequency, it's just 'at least this speed', presumably? |
00:17.05 | maejrep[w] | it doesn't work well to compile it into the kernel (and is hard-coded as obj-m +=, so you can't just select "M") |
00:17.07 | NetRipper | now i need to roll back |
00:17.24 | maejrep[w] | lupine_85: usually not |
00:17.30 | maejrep[w] | usually it's "at most this speed" |
00:17.31 | cr2 | maejrep[w]: do you reset the wifi by toggling the 0x86 and 0x87 gpios ? |
00:17.45 | maejrep[w] | cr2: if that's 102 and 103, I think so |
00:17.47 | lupine_85 | see, that seems odd to me :D |
00:18.08 | maejrep[w] | lupine_85: what if you select 48MHz, but the only rates are 45MHz and 96MHz |
00:18.10 | *** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com) |
00:18.13 | maejrep[w] | do you really want to try 96? |
00:18.21 | cr2 | lupine_85: taking a higher frequency is asking for a crash usually |
00:18.26 | maejrep[w] | ^ |
00:18.49 | maejrep[w] | cr2: I know I use 102 and 103 on poweron/off, but I think I might have not implemented the phy_reset yet (?) |
00:18.55 | maejrep[w] | dont have the code in front of me right now |
00:19.09 | cr2 | maejrep[w]: there is no obvious wifi reset on raph, but |
00:19.10 | lupine_85 | well, I asm unused to k |
00:19.16 | lupine_85 | am* unused to kernerl coding |
00:19.36 | maejrep[w] | cr2: yeah, I don't think I've ever seen it "reset", but I see power on and power off |
00:19.40 | cr2 | wince does 86=0, 87=0, msleep, 86=1,87=1 vreg:c, vreg,d |
00:19.42 | maejrep[w] | so I guess power off, then on, should reset? |
00:19.45 | lupine_85 | but if your clock goes faster than you want, you can always drop some ticks; if it goes slower than you want, there's no obvious way to compensate? |
00:19.47 | maejrep[w] | makes sense |
00:19.53 | lupine_85 | shrugs, 'tis his bedtime |
00:20.52 | cr2 | maejrep[w]: "obvious" as in pin=0,msleep,pin=1 |
00:20.52 | maejrep[w] | yeah |
00:20.52 | maejrep[w] | cr2: did you see I got battery info on raph800? |
00:20.52 | maejrep[w] | it might not be the same on raph100 though, it wasn't the same location as documented in the wiki |
00:20.57 | maejrep[w] | had to use smem+fc140 |
00:21.06 | maejrep[w] | @14 bytes |
00:21.07 | cr2 | lupine_85: if you set too high SD clock, the device may not be able to proceed. but if you set 144kHz it will always work |
00:21.17 | maejrep[w] | just very slowly ;p |
00:21.27 | maejrep[w] | I agree it should take the next slower rate |
00:21.44 | cr2 | maejrep[w]: yes, it may be raph800 specific. i'll check. how did you find it out ? |
00:21.50 | maejrep[w] | battery.dll |
00:21.57 | maejrep[w] | (not battdrv) |
00:22.02 | cr2 | ok |
00:22.14 | maejrep[w] | but it does some weird things ;| |
00:22.32 | cr2 | maejrep[w]: i think that the next big thing is to fix the clk api |
00:22.55 | cr2 | i'll calculate the Md/Ns for uart2DM |
00:23.07 | maejrep[w] | it uses it as a struct (1B, 1B, blank 2 B, 4B, 4B, etc) for some debug messages showing things like "CDMA band, technology", etc |
00:23.07 | cr2 | for 115200 and 4mbit |
00:23.15 | cr2 | yeah |
00:23.17 | maejrep[w] | but the vogue code does a strange calculation to get Volts and Temp out of it |
00:23.24 | cr2 | i was surprised too |
00:23.38 | maejrep[w] | and I think the dll does too |
00:23.53 | cr2 | maejrep[w]: and polaris talks diret to the battery i2c monitor chip |
00:23.56 | maejrep[w] | the part where I got the addresses and debug messages indicating what they mean was just hte beginning of the function |
00:24.03 | cr2 | ok |
00:24.14 | maejrep[w] | the rest of the function had a huge logic tree |
00:24.28 | cr2 | loading |
00:24.41 | maejrep[w] | cr2: you mentioned that most of the clocks are documented, but I don't think we have the "wince index" documented for them |
00:24.46 | maejrep[w] | is that wrong? |
00:25.10 | maejrep[w] | specifically, what makes the clock ena bit |
00:25.21 | maejrep[w] | and we need that to be able to add it to the clock api |
00:25.42 | cr2 | don't have batery.dll |
00:25.58 | maejrep[w] | http://wiki.xda-developers.com/index.php?pagename=MSM_CLK |
00:26.09 | maejrep[w] | I can send you mine, but its from raph800 ;) |
00:26.31 | cr2 | maejrep[w]: wince "uses" only the documented clocks. |
00:26.49 | maejrep[w] | btw, tried testing the RPC clock from google, and the rpc server didn't work |
00:26.56 | cr2 | ok, send it. i'll check the nk.exe for the battery data |
00:27.00 | maejrep[w] | even changing it from 30000001 to 30000005 |
00:27.06 | cr2 | because it may be different from spl |
00:27.11 | NetRipper | maejrep[w], that htcraphael_reset doesn't work btw, it hangs after the dex.. crashes arm9.. doesn't get to gpio ;) |
00:27.31 | cr2 | maejrep[w]: use vogue rpc code |
00:27.48 | maejrep[w] | http://privatepaste.com/a70Vo2xlUW#battery.dll |
00:27.59 | maejrep[w] | NetRipper: using 0x22 ? |
00:28.07 | maejrep[w] | it works for me :x |
00:28.15 | NetRipper | struct msm_dex_command dex = { .cmd = PCOM_RESET_ARM9 }; |
00:28.18 | NetRipper | that one |
00:28.24 | NetRipper | which command do you use to reset? |
00:28.27 | cr2 | notify a9 to reboot |
00:28.27 | NetRipper | reboot -f? |
00:28.36 | maejrep[w] | just `reboot` |
00:28.42 | NetRipper | 'reboot' does nothing |
00:28.43 | NetRipper | for me |
00:28.45 | NetRipper | well |
00:28.47 | maejrep[w] | it works every time for me |
00:28.48 | NetRipper | im in the android initrd |
00:28.55 | maejrep[w] | dunno if that matters |
00:29.08 | maejrep[w] | might just be a different api for raph100? doubtful though.. |
00:29.12 | cr2 | fc13c and dex8e |
00:29.17 | NetRipper | when i do reboot -f, it tells me right after the dex, "ARM9 has CRASHED" |
00:29.20 | maejrep[w] | fc13c ? |
00:29.26 | maejrep[w] | cr2: 0x8e didn't work for me |
00:29.45 | cr2 | yes, in this "notify a9 to reboot" |
00:29.47 | maejrep[w] | NetRipper: I'm not sure if I trust that crash detection |
00:30.00 | NetRipper | maejrep[w], well afterwards it hangs, no soft reset is done |
00:30.04 | maejrep[w] | cr2: it didn't work for me.. but everything else, plus the 0x22 dex command did work |
00:30.13 | cr2 | maejrep[w]: is checked if it's =0 |
00:30.20 | maejrep[w] | if what's 0? |
00:30.34 | maejrep[w] | wait |
00:30.38 | cr2 | dex8e is called if it's != 0 |
00:30.45 | cr2 | fc13c |
00:30.58 | maejrep[w] | if fc13c is not 0, then call 0x8e |
00:31.03 | maejrep[w] | plus set the gpio to 0? |
00:31.45 | maejrep[w] | cr2: I just do: dex(0x22); sleep(); gpio_configure(25, OWNER_ARM11); gpio_direction_output(25, 0) |
00:31.47 | maejrep[w] | and it works |
00:32.09 | cr2 | 22 ? |
00:32.13 | maejrep[w] | yes |
00:32.19 | cr2 | what is 22 ? |
00:32.35 | maejrep[w] | "restart arm9 |
00:32.37 | maejrep[w] | :P |
00:32.48 | maejrep[w] | 8e is " notify arm9 reboot " |
00:32.51 | cr2 | 8e is "notify" |
00:32.53 | cr2 | yes |
00:33.03 | maejrep[w] | but it doesn't "notice" when I notify it |
00:33.03 | maejrep[w] | :p |
00:33.40 | cr2 | lol |
00:34.48 | cr2 | maejrep[w]: fc110+ here for the battery |
00:34.52 | maejrep[w] | NetRipper: I generally do "reboot & exit" on the command line, just so my ssh session doesn't hang forever ;p |
00:34.58 | maejrep[w] | not for raph800 |
00:35.05 | maejrep[w] | i think that's for diam and raph100 |
00:35.37 | maejrep[w] | I can check it again to be sure, as I already have the htc_battery code working |
00:35.38 | cr2 | ok |
00:35.59 | cr2 | maejrep[w]: i look at nk.exe |
00:36.17 | maejrep[w] | you're looking at it for 100 or 800? |
00:36.35 | NetRipper | just committed your wifi stuff, without the driver |
00:36.58 | maejrep[w] | cool |
00:37.04 | maejrep[w] | does it work for you? |
00:37.12 | NetRipper | http://netripper.pastebin.com/m145589cf |
00:37.13 | maejrep[w] | at least, detecting cards, setting clocks, etc |
00:37.16 | NetRipper | that's what my dmesg looks like |
00:37.21 | NetRipper | you tell me if it works ;) |
00:37.29 | *** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca) |
00:37.30 | NetRipper | i thought it looked healthy |
00:38.31 | maejrep[w] | yep, same as mine |
00:38.35 | NetRipper | ok |
00:38.35 | NetRipper | great |
00:38.36 | maejrep[w] | dunno what the misfire means |
00:38.43 | maejrep[w] | (i get it too) |
00:38.46 | NetRipper | ok |
00:38.53 | maejrep[w] | and can't really tell if the wifi "actually" works, without the config utilities |
00:38.53 | NetRipper | think it might just be timing |
00:39.04 | NetRipper | yea but we still need to load firmware |
00:39.07 | maejrep[w] | you're running android? |
00:39.08 | NetRipper | appearantly |
00:39.16 | NetRipper | im using the android initrd, but not android itself |
00:39.24 | maejrep[w] | does that include the libs? |
00:39.25 | NetRipper | as i sitll got the grafhpics issues |
00:39.41 | maejrep[w] | cause I compiled the wifi utilities from the tiwlan directory |
00:39.48 | NetRipper | i dont know, does it? :) |
00:39.50 | maejrep[w] | I just haven't tried them in android yet |
00:39.52 | NetRipper | i'll check it out another day though |
00:40.02 | NetRipper | its past my bedtime already |
00:40.02 | NetRipper | :) |
00:40.12 | maejrep[w] | and cr2 said we should be able to get the firmware from nv/nand |
00:40.25 | maejrep[w] | lol |
00:40.34 | maejrep[w] | you guys always go to bed before I get off work ;) |
00:40.39 | NetRipper | yea |
00:40.44 | NetRipper | its 1.40 am here |
00:40.46 | maejrep[w] | ouch |
00:40.56 | maejrep[w] | sounds like me ;s |
00:41.03 | cr2 | maejrep[w]: i have eidted the wiki for raph100 bat |
00:41.06 | NetRipper | so like when i wake up in the morning |
00:41.09 | NetRipper | and i see you chatting |
00:41.13 | NetRipper | im thinking the same |
00:41.49 | NetRipper | anywayz, good night :) |
00:42.09 | cr2 | god night |
00:42.49 | maejrep[w] | haha |
00:42.52 | maejrep[w] | good night :p |
00:43.19 | maejrep[w] | cr2: btw, added what I found in battery.dll to the bottom of: http://wiki.xda-developers.com/index.php?pagename=RaphaelDEX as a note |
00:44.31 | maejrep[w] | cr2: hmm, ok.. so maybe the odd debug messages in battery.dll are just misinforming |
00:44.43 | cr2 | maejrep[w]: but what does it have to do with the battery ? |
00:44.47 | maejrep[w] | I ended up using vogue's battery formula for creating temp, volts, current, etc |
00:44.57 | maejrep[w] | cr2: that's a great question ;( |
00:45.39 | cr2 | ok, the raph100 stores 5 battery params in the middle of dex area. fc110+ |
00:45.58 | maejrep[w] | I only see 4 |
00:46.15 | maejrep[w] | actually |
00:46.17 | cr2 | id,temp,volt,charge,discharge |
00:46.28 | maejrep[w] | vogue code uses 4 ints (4-byte) |
00:46.36 | maejrep[w] | your list shows 4 halfwords |
00:46.36 | cr2 | all 16bit values |
00:46.46 | maejrep[w] | and I'm fetching 4 ints |
00:46.51 | maejrep[w] | 32-bit |
00:47.04 | cr2 | sorry, it's an error. i'll fix it |
00:47.40 | maejrep[w] | also don't see "Volt" there (is that charge?) |
00:48.03 | cr2 | no |
00:48.05 | maejrep[w] | other thing I need to figure out is that the battery code disables my USB ether :P |
00:48.22 | maejrep[w] | presumably because it shuts off USB when it's at 100% charge |
00:48.26 | maejrep[w] | but I haven't confirmed that |
00:48.26 | cr2 | Charge is in Coulomb=A*s |
00:48.37 | maejrep[w] | yeah I saw the conversion |
00:49.04 | cr2 | so it's more current related, not voltage |
00:49.31 | maejrep[w] | v = values[2] + (values[4] / 7) - (values[3] / 28); |
00:49.59 | maejrep[w] | hmm... that means it uses 5 32-bit integers :| |
00:50.09 | cr2 | ok, wiki fixed |
00:50.58 | maejrep[w] | ok, i'll try those locations with raph800.. would be nice if it's correct there too |
00:51.18 | maejrep[w] | could be that we're running both 0x8a and 0x8b, and fc140 is data for one command, and fc110 is for the other command |
00:51.41 | maejrep[w] | I don't like the formula dzo does for volts :p |
00:51.55 | maejrep[w] | sorry, capacity* |
00:52.06 | maejrep[w] | capacity = battery_table[i-1] + ((v - battery_table[i-2]) * (battery_table[i+1] - battery_table[i-1])) / (battery_table[i]-battery_table[i-2]); |
00:52.36 | cr2 | charge is the integral current over time |
00:52.54 | cr2 | q=\int I(t)dt |
00:53.11 | maejrep[w] | been a few years since calculus |
00:53.16 | cr2 | or I=dq/dt |
00:53.24 | maejrep[w] | ok |
00:53.48 | maejrep[w] | he only arrives at capacity being 0, 10, 25, 35, 100% |
00:54.11 | cr2 | he is probably using some calibration table |
00:54.16 | maejrep[w] | yes |
00:54.26 | maejrep[w] | static int battery_table[] |
00:54.28 | cr2 | to approximate the real change |
00:54.34 | cr2 | s/change/charge/ |
00:54.37 | maejrep[w] | with 7 pairs |
00:55.35 | maejrep[w] | cr2: so fc110 is the result of 0x8a or 0x8b? |
00:55.38 | maejrep[w] | 8b is "get battery id" |
00:55.44 | maejrep[w] | 8a "get battery data" |
00:56.02 | maejrep[w] | when tracing dex in haret, it runs both commands every 10 seconds |
00:56.23 | cr2 | i'll check |
00:56.37 | cr2 | yes, 10 sec is usual for wince |
00:57.24 | cr2 | dex_get_batt_slope |
00:57.55 | cr2 | battery.dwVendor |
00:58.31 | cr2 | what is fc0dc ? |
00:59.08 | maejrep[w] | +0xfc0dc battery id |
00:59.09 | maejrep[w] | ;) |
00:59.34 | cr2 | HTC_SMEM_BATTERY_ID |
01:00.18 | cr2 | it's the result of 8b |
01:00.26 | maejrep[w] | only that? |
01:00.32 | maejrep[w] | it doesn't do anything else? |
01:00.54 | maejrep[w] | also, does wince clear out that data after it's read? or arm9? |
01:01.04 | maejrep[w] | always seemed strange that it was all 0's when I'd read it from haret |
01:03.13 | maejrep[w] | cr2: so what's fc110 then? |
01:03.18 | maejrep[w] | battery id also? |
01:03.48 | cr2 | hmm. |
01:03.57 | *** join/#htc-linux alberink (n=alberink@cc206592-b.ensch1.ov.home.nl) |
01:04.02 | cr2 | what do you have at these locations ? |
01:04.11 | cr2 | ill check my smem dump |
01:05.04 | maejrep[w] | sec |
01:05.43 | maejrep[w] | 000fc0d0 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| |
01:05.51 | maejrep[w] | 000fc110 2c 71 35 fd 00 00 00 00 01 00 00 00 00 00 00 00 |,q5.............| |
01:05.57 | maejrep[w] | 000fc140 02 03 00 00 00 00 00 00 01 00 00 00 97 ff 0a 00 |................| |
01:06.27 | cr2 | gpio 1c - removed battery |
01:06.57 | maejrep[w] | 28 0x1c 12 I irq MBAT_IN, battery |
01:07.20 | maejrep[w] | that's in htc-battery.c as battery_detection_gpio |
01:07.53 | maejrep[w] | #define GPIO_BATTERY_DETECTION 28 |
01:07.54 | cr2 | e8 01 00 00 |
01:07.54 | maejrep[w] | #define GPIO_BATTERY_CHARGER_EN 77 |
01:07.54 | maejrep[w] | #define GPIO_BATTERY_CHARGER_CURRENT 1 |
01:08.14 | maejrep[w] | what location is that? |
01:09.19 | cr2 | dc |
01:09.31 | maejrep[w] | hmm, i should write a haret companion app that just telnets to localhost 9999, and runs certain commands so you can do smem dumps, etc, without needing a connection ;p |
01:09.32 | cr2 | i have some values at 110 |
01:09.53 | cr2 | default.txt |
01:09.59 | maejrep[w] | ah true |
01:11.09 | maejrep[w] | anything at fc140? |
01:11.59 | cr2 | no |
01:12.12 | cr2 | fc13c=1 dex_ready |
01:12.21 | maejrep[w] | o.0 |
01:12.21 | cr2 | then zeros |
01:12.44 | maejrep[w] | hmm |
01:12.49 | maejrep[w] | why did I never notice fc13c |
01:13.04 | maejrep[w] | that could fix an issue I was having before |
01:13.21 | maejrep[w] | not being able to tell whether proc comm was ready for a command |
01:13.43 | cr2 | checking dex8a |
01:13.55 | maejrep[w] | ok, so battery is gonna be another platform nightmare :( |
01:14.08 | maejrep[w] | let's just branch raph800 |
01:14.10 | maejrep[w] | ;D |
01:14.39 | maejrep[w] | ok, bbiab |
01:17.46 | cr2 | yes, 8a saves at +0x10, +0x12, ... |
01:21.45 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
01:23.14 | *** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca) |
01:30.22 | *** join/#htc-linux alberink (n=alberink@cc206592-b.ensch1.ov.home.nl) |
01:37.41 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) |
01:38.37 | *** part/#htc-linux Solitary_Sock1 (n=solitary@227.145.72-86.rev.gaoland.net) |
01:41.01 | cr2 | good night |
01:47.19 | *** part/#htc-linux Balsat (n=kll@87.72.13.87) |
01:48.50 | *** join/#htc-linux zycho_ (n=zycho@a89-183-94-176.net-htp.de) |
02:05.40 | *** join/#htc-linux ALoGeNoff (n=alogeno@205.pool80-103-168.dynamic.orange.es) |
02:21.41 | *** join/#htc-linux MrFeetio (n=MrFeetio@pool-98-117-23-186.hrbgpa.fios.verizon.net) |
02:49.18 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
03:05.09 | *** join/#htc-linux deeproot (n=tony@68-112-216-255.dhcp.slid.la.charter.com) |
03:26.55 | *** join/#htc-linux sdt555 (n=titus@70.114.152.91) |
03:28.26 | *** join/#htc-linux fnord_ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |
03:37.14 | *** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca) |
04:19.23 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
04:25.17 | *** join/#htc-linux ykut_johny1 (n=ykut_joh@mitsa.org.my) |
04:30.14 | *** join/#htc-linux ykut_johny1 (n=ykut_joh@mitsa.org.my) |
04:47.28 | *** join/#htc-linux shoragan (n=shoragan@debian/developer/shoragan) |
05:37.18 | maejrep | cr2: seems my battery definitely works differently ;x 0x8a and 0x8b both read out of +fc140 |
05:38.12 | maejrep | http://www.privatepaste.com/80shbHLXIF <-- reading from fc140-fc150 after both 8a and 8b commands |
05:38.58 | maejrep | so that's what those CDMA/tech/1xhdr/etc lines were from |
05:39.06 | maejrep | 8b, not 8a |
05:46.04 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
06:05.36 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
06:17.29 | maejrep | http://www.privatepaste.com/f7UGbV734w - with more accurate battery data (not 100% correct yet) |
06:24.31 | *** join/#htc-linux bs2 (n=kra@87.72.13.87) |
06:27.58 | *** join/#htc-linux hollo (n=hollo@3e6b025d.rev.stofanet.dk) |
06:41.43 | *** join/#htc-linux t3chi3 (n=blarg@ip24-250-212-67.ga.at.cox.net) |
06:51.26 | *** join/#htc-linux PoohbaLT (n=BlkPoohb@69.141.71.249) |
06:53.37 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
07:07.11 | *** join/#htc-linux kiozen (n=oeichler@p5492211C.dip0.t-ipconnect.de) |
07:14.13 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-32-72.web.vodafone.de) |
07:15.16 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
07:15.21 | Untouchab1e | Good morning ^^ |
07:17.02 | cr2 | morning |
07:22.01 | Untouchab1e | how are you+ |
07:22.02 | Untouchab1e | ?* |
07:27.10 | *** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
07:28.39 | cr2 | leaving to work |
07:47.38 | Untouchab1e | Have a nice one ^^ |
07:52.32 | *** join/#htc-linux PoohbaLT1 (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net) |
07:59.50 | *** join/#htc-linux maejrep (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net) |
08:05.37 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
08:11.47 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
08:14.05 | *** part/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
08:23.19 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
08:43.33 | *** join/#htc-linux Babel1 (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
08:49.59 | *** join/#htc-linux TeringTu1y (n=Maarten@195-241-125-243.ip.telfort.nl) |
08:55.08 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
08:55.55 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
09:09.17 | Untouchab1e | New Android build for the Raph posted at connect-utb |
09:09.37 | Untouchab1e | Need confirmation that it works |
09:12.49 | *** join/#htc-linux kiozen (n=oeichler@p5492211C.dip0.t-ipconnect.de) |
09:15.54 | tmzt | Untouchab1e: what's connect-utb? |
09:16.22 | *** join/#htc-linux timebomb (n=tb@e176096224.adsl.alicedsl.de) |
09:16.44 | Untouchab1e | Connect-utb.com |
09:16.55 | Untouchab1e | where all the full builds for Android and raph are hosted |
09:17.29 | tmzt | don't know, it would good to have someone try and report back here though |
09:17.33 | *** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl) |
09:18.56 | *** join/#htc-linux konsta (n=asds@host81-157-60-163.range81-157.btcentralplus.com) |
09:21.17 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
09:24.07 | Untouchab1e | dont know what? |
09:27.09 | *** join/#htc-linux kiozen (n=oeichler@p5492211C.dip0.t-ipconnect.de) |
09:50.35 | *** join/#htc-linux ewasx (n=Armin@armin-dev.ict.tno.nl) |
10:01.35 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089163.pool.mediaWays.net) |
10:18.43 | *** join/#htc-linux Moonlit (i=mooonlit@mario.dreamhost.com) |
10:28.04 | *** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) |
10:49.58 | *** join/#htc-linux Moonlit (i=mooonlit@mario.dreamhost.com) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux timebomb (n=tb@e176096224.adsl.alicedsl.de) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux TeringTu1y (n=Maarten@195-241-125-243.ip.telfort.nl) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux kaze (n=kaze@ABordeaux-152-1-53-252.w82-125.abo.wanadoo.fr) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux Sti_0231 (n=Where_is@179.213-65-87.adsl-dyn.isp.belgacom.be) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux thinko (n=jdoe6alp@smaug.rackdragon.com) [NETSPLIT VICTIM] |
10:49.58 | *** join/#htc-linux wasabi (n=wasabi@ubuntu/member/wasabi) [NETSPLIT VICTIM] |
11:20.13 | *** join/#htc-linux MethoS- (n=lem@host-091-097-241-242.ewe-ip-backbone.de) |
11:47.18 | *** join/#htc-linux xutywx_ (n=pawel@195.205.38.95) |
11:48.12 | xutywx_ | hi everybody again ;) |
11:48.31 | xutywx_ | i have a question about g900 linux |
11:48.47 | xutywx_ | does anybody know something about |
11:48.48 | xutywx_ | http://www.youtube.com/watch?v=m4nlTKFI9aU |
11:49.04 | xutywx_ | i need only kernel ;) |
11:52.50 | *** join/#htc-linux MrFeetio (n=MrFeetio@pool-98-117-23-186.hrbgpa.fios.verizon.net) |
12:06.44 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
12:28.04 | *** join/#htc-linux TheOther (n=nahh@108.84-49-166.nextgentel.com) |
12:30.20 | *** join/#htc-linux TeringTuby (n=Maarten@195-241-125-243.ip.telfort.nl) |
12:42.46 | *** join/#htc-linux Woetermelon (n=woeterma@78-27-33-6.dsl.alice.nl) |
12:42.48 | Woetermelon | Hi |
12:42.56 | Woet | Android is working fine on my phone |
12:43.06 | Woet | but I have to disabled networking and such before booting into Android |
12:43.11 | Woet | else it'll freeze at 100% at HATRED |
12:43.20 | Woet | which means I can't call/text inside android |
12:43.23 | Woet | how can I resolve this? |
12:45.53 | *** join/#htc-linux spacemud (n=dynamite@unaffiliated/spacemud) |
12:45.55 | Woet | :3 |
12:46.00 | spacemud | :3 |
12:51.58 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
12:53.07 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
13:04.45 | *** join/#htc-linux xutywx (n=pawel@195.205.38.95) |
13:06.49 | xutywx | hello ;) is anybody here? |
13:09.52 | Woet | no, you're seeing ghosts. |
13:15.26 | xutywx | nice ;P does anybody know something about linux on g900 |
13:15.54 | xutywx | i've posted a link to yt before my internet connection went down ;/ |
13:33.26 | *** join/#htc-linux MethoS-- (n=lem@host-091-096-215-178.ewe-ip-backbone.de) |
14:01.09 | *** join/#htc-linux ALoGeNoff (n=alogeno@205.pool80-103-168.dynamic.orange.es) |
14:10.20 | NetRipper | j0b0, i've just applied your patches and pushed them onto ltg git |
14:11.07 | NetRipper | j0b0, there's a compiler warning in your navi file... you don't check the result of request_irq() calls.. can you add failure handling in there? |
14:11.23 | *** join/#htc-linux PoohbaLT (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net) |
14:12.48 | NetRipper | maejrep, can you please check if the latest git also works for raph800? |
14:13.06 | maejrep | k |
14:13.08 | NetRipper | keyboard, its backlight led and navi in particular |
14:18.06 | *** join/#htc-linux zycho (n=zycho@a89-183-94-176.net-htp.de) |
14:27.02 | *** join/#htc-linux pawel_ (n=pawel@195.205.38.95) |
14:31.03 | j0b0 | NetRipper thanks. and yes, I shall fix that warning. |
14:31.39 | tmzt | NetRipper: maejrep: do you know about this connect-utb thing Untouchable asked about? |
14:31.42 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-021.ewe-ip-backbone.de) |
14:32.56 | j0b0 | that is where Untouchab1e hosts stuff |
14:33.20 | j0b0 | kernels and file system images that work as package |
14:36.25 | tmzt | ah so that was Untouchable's stuff, I thought was asking about it |
14:39.34 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
14:40.22 | xutywx | how should sd card for android look like? |
14:40.44 | tmzt | xutywx: I have less information than you on g900, sorry |
14:41.00 | tmzt | and that depends what init scripts you use |
14:41.38 | xutywx | http://translate.google.pl/translate?prev=hp&hl=en&u=http%3A%2F%2Fwww.portegeclub.ru%2Fforum%2Fviewtopic.php%3Ft%3D1464%26start%3D195&sl=ru&tl=pl |
14:41.41 | xutywx | look here |
14:42.22 | tmzt | didn't translate very well |
14:42.25 | xutywx | on that page is kernel source, in it is kernel and initram for g900 ;) |
14:42.45 | xutywx | it works - fb is working and it boots ;P |
14:42.57 | xutywx | but it hangs on "waiting for sd card" |
14:43.00 | tmzt | http://goandroid.net/kernel.tar.gz |
14:43.04 | xutywx | yes |
14:43.12 | xutywx | thats the archive |
14:43.17 | tmzt | are you using a initrd? |
14:43.21 | xutywx | yes |
14:43.32 | tmzt | what is it trying to boot? |
14:43.34 | tmzt | mount |
14:43.50 | tmzt | /dev/mmcblk0pX |
14:44.07 | xutywx | i dont know - it hangs on kernel booting with no information ;/ |
14:44.23 | xutywx | i'm trying to wait longer |
14:44.44 | xutywx | on the main page of that site is a video of g900 using android |
14:45.10 | *** join/#htc-linux timebomb (n=tb@e176096224.adsl.alicedsl.de) |
14:45.19 | tmzt | check your default.txt and paste the CMDLINE line here |
14:53.25 | Woet | [13:43:00] <Woet> Android is working fine on my phone |
14:53.26 | Woet | [13:43:10] <Woet> but I have to disabled networking and such before booting into Android |
14:53.26 | Woet | [13:43:15] <Woet> else it'll freeze at 100% at HATRED |
15:18.24 | NetRipper | woet, which device |
15:18.33 | NetRipper | for raphael/diamond it's a known issue |
15:18.38 | Woet | kaiser |
15:20.18 | Woet | any idea, NetRipper? |
15:20.27 | Woet | i really like android, but using it for calling would be nice :p |
15:20.54 | dcordes | Woet: haret=hatred is not the unfunniest typo I've seen |
15:21.40 | Woet | oh, I see :p |
15:24.13 | dcordes | Woet: which kernel do you use? |
15:24.59 | Woet | [23:31:38] <Rogro82> http://www.rocknrollcoffeehouse.com/shadowline/AndroidSMS1-23.zip |
15:25.01 | Woet | that one |
15:25.03 | dcordes | Woet: probably you have a messed up radio version. try a different one |
15:25.16 | Woet | I got that one atm |
15:25.21 | Woet | which one do you suggest I should try? |
15:25.25 | dcordes | hmm organic coffee |
15:25.40 | dcordes | I don't know. a different one |
15:25.44 | Woet | okay |
15:25.51 | Woet | where can I find a different one? |
15:25.57 | dcordes | basically any should work now. but it's worth a try. |
15:26.08 | Woet | since I tried a different one earlier (the one suggested by the wiki), and it crashed too |
15:26.20 | dcordes | http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs |
15:26.53 | dcordes | well you never know who build the coffeehouse zip. does it work for other people? |
15:27.01 | dcordes | it's best to build your own kernel and filesystem |
15:31.10 | dcordes | Woet: let me know if it worked. I need kebab byebye |
15:31.44 | Woet | dcordes: an explaination how to build my own kernel would be nice |
15:33.19 | toer | http://letmegooglethatforyou.com/?q=how+to+build+kaiser+kernel |
15:35.15 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
16:03.37 | *** join/#htc-linux metter (n=metter@44-178.203-62.cust.bluewin.ch) |
16:09.06 | *** join/#htc-linux zycho_ (n=zycho@a89-182-2-79.net-htp.de) |
16:27.48 | *** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com) |
16:51.48 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c909.pool.einsundeins.de) |
16:59.18 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
17:00.14 | *** join/#htc-linux Pure4Real (n=pure4rea@89-97-140-219.ip17.fastwebnet.it) |
17:07.28 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
17:14.58 | xutywx | how to unpack initrd? |
17:15.48 | Balsat | <PROTECTED> |
17:16.00 | j0b0 | cat ../initrd | gunzip | cpio -imd |
17:16.12 | j0b0 | oh ok :) |
17:17.20 | xutywx | thx ;) |
17:17.39 | Balsat | Jobo : your new patch make a error and hangs on diam100, if i touch the navi pad |
17:18.13 | Balsat | mutex.c:135 ??? |
17:18.37 | xutywx | so how to pack it again? |
17:18.53 | Balsat | find . | cpio -o -H newc > ../newinitrd ; cd .. ; gzip newinitrd |
17:19.03 | xutywx | thx |
17:19.05 | j0b0 | xutywx: find . | cpio -o -H newc | gzip -9 > ../initr |
17:19.07 | j0b0 | d |
17:19.51 | j0b0 | Balsat i have just fetched the latest git and will confirm now, but i have no diamond |
17:20.18 | Balsat | Ok.. i will pull that |
17:24.31 | *** join/#htc-linux MethoS-- (n=lem@host-091-097-244-033.ewe-ip-backbone.de) |
17:24.42 | j0b0 | current git is good on raph100 |
17:28.10 | j0b0 | Balsat do you get a backtrace with that error? |
17:29.16 | Balsat | yes, but i have rebooted my device now... i will give it a try again |
17:32.45 | Balsat | Warning at kernel/mutex.c:135 __mutex_lock_slowpath+0x9c/0x230() |
17:34.30 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
17:35.10 | Balsat | Is the backtrace saved anyware? it is to small for my eyes |
17:37.05 | Balsat | but something whit the micropklt_set_led_states+0x0/0xb0 from [<c004c800>] |
17:38.01 | tmzt | xutywx: is it working? |
17:38.51 | xutywx | hmm yes and no |
17:38.59 | xutywx | i cant use sd card |
17:39.33 | xutywx | so i'm trying to built in all data of os to initramfs ;P |
17:40.41 | tmzt | why can't you use the sd card? |
17:40.53 | xutywx | kernel doesnt finds it |
17:40.59 | tmzt | I think the only android that's going to fit is the dzo 0.8 |
17:41.05 | tmzt | really old |
17:41.16 | tmzt | what chipset is your device based on again? |
17:41.27 | xutywx | pxa270 as i remember |
17:41.44 | tmzt | why doesn't pxamci work, you don't have the gpios traced in haret? |
17:42.11 | tmzt | you had some other people in here but I couldn't really understand what they where trying to say |
17:42.34 | xutywx | i'm trying to run some ther guy's project so i dont know ;P |
17:43.02 | xutywx | is any initrd size limit? |
17:43.14 | xutywx | only the platform memory? |
17:43.16 | tmzt | whatever limit haret and ce ram sets for it |
17:43.30 | tmzt | if haret can't allocate the ram it won't work |
17:43.39 | xutywx | haret can boot from sd card? |
17:44.05 | tmzt | linux kernel has to support your card |
17:44.29 | tmzt | which it should if you have pxamci sd host, but you need to find the gpio to detect or powerup the card |
17:44.52 | xutywx | but now ive biult in the android rootfs into the initrd |
17:45.02 | tmzt | try it |
17:46.12 | xutywx | it has 35MB... kernel 1,5MB it should be working |
17:46.28 | tmzt | you have to include initrd in that |
17:46.43 | xutywx | im afraid about init scripta |
17:46.47 | xutywx | *scripts |
17:46.55 | tmzt | why? |
17:47.32 | xutywx | beacuse i replaced /init from old initrd with init from the rootfs |
17:48.10 | tmzt | take the .img's and extract them to initrd |
17:48.32 | tmzt | make sure the init.rc or /init (script) does not mount any images from sd card |
17:49.10 | tmzt | dzo: do you have a 1.0 initrd or does the working diamond sd make that unneccessary? |
17:50.14 | xutywx | init should be a script or it can be elf? |
17:52.58 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089163.pool.mediaWays.net) |
17:54.12 | tmzt | android init is a program, if you are using a script like the one from dzo or dcordes bootkit, it will call the android init as /init2 |
17:55.19 | xutywx | largest size for haret is 25MB ;/ |
17:59.22 | j0b0 | Balsat can you tell from dmesg whether microp-klt fails to initialize? |
18:06.18 | Balsat | [ 1.459163] microp-klt: This hardware is not yet supported: 0b01 [ 1.470424] microp-klt: probe of 0-0066 failed with error -524 |
18:06.18 | Balsat | <PROTECTED> |
18:07.31 | j0b0 | right. it would probably be good to set micropklt_t back to zero in fail: then.. |
18:07.47 | j0b0 | in the probe function |
18:09.20 | Balsat | Is worked with the .25 kernel |
18:09.42 | j0b0 | can you try that and see if it helps |
18:10.01 | Balsat | Where shall i do that? |
18:12.18 | j0b0 | at the bottom of micropklt_probe() |
18:14.03 | NetRipper | Balsat, by < Balsat> Jobo : your new patch make a error and hangs on diam100, if i touch the navi pad |
18:14.13 | NetRipper | by hang do you mean a BUG / kernel oops? |
18:14.34 | NetRipper | it shouldn't hang the device actually |
18:14.39 | NetRipper | just print a kernel oops |
18:14.43 | j0b0 | NetRipper micropklt_t does not get put back on zero if micropklt_probe() fails |
18:14.49 | NetRipper | ah |
18:14.51 | Balsat | Netripper it completly died |
18:14.52 | j0b0 | set_led_state() checks for zero |
18:14.57 | NetRipper | right |
18:15.06 | NetRipper | make a patch ;) |
18:15.19 | NetRipper | im gone in a few minutes |
18:15.20 | j0b0 | fail: |
18:15.20 | j0b0 | kfree(data); |
18:15.20 | j0b0 | micropklt_t = 0; // <--- try adding this |
18:15.20 | j0b0 | return r; |
18:15.21 | j0b0 | } |
18:15.34 | Balsat | one moment |
18:17.18 | NetRipper | let me know if that fixed it |
18:17.19 | NetRipper | i gtg |
18:17.20 | NetRipper | later |
18:17.25 | j0b0 | ok ttyl |
18:21.05 | Balsat | Jobo : that worked, but the led on the navi pad dosent work now |
18:23.18 | j0b0 | ok, so the crash is explained. i dont know why the led driver fails tho |
18:23.51 | j0b0 | but it failing no longer crashes the navi... |
18:25.47 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
18:27.17 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
18:37.00 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
18:48.06 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfef5e.pool.einsundeins.de) |
18:57.56 | *** join/#htc-linux kritter223 (n=kritter2@cpe-24-210-192-74.woh.res.rr.com) |
18:58.30 | *** part/#htc-linux kritter223 (n=kritter2@cpe-24-210-192-74.woh.res.rr.com) |
18:59.17 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
19:02.22 | dcordes | did somebody deal with the legal situation of hosting ready made android filesystems? especially reagarding the ril etc. |
19:02.43 | dcordes | lupine_85: are you around? |
19:05.25 | *** join/#htc-linux vmpu (n=pui@89-33-138-94.u-nite.ro) |
19:08.51 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
19:21.08 | ginge | dcordes: not that I know of. I think everyone just ignores it |
19:26.15 | dcordes | yea it's obvious everyone ignores it. that's why I stumbled across the question |
19:26.16 | *** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl) |
19:34.40 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
19:37.43 | RZK333 | what zimage i must use on nike to run android without power button? |
19:48.57 | *** join/#htc-linux Bomberik (n=Bomberik@host-78-14-225-188.cust-adsl.tiscali.it) |
19:49.05 | Bomberik | hi |
19:54.35 | *** join/#htc-linux cr2 (n=cr2@ip-90-186-236-239.web.vodafone.de) |
19:59.27 | lupine_85 | dcordes: yep |
19:59.45 | lupine_85 | dcordes: note that I'm not a lawyer :) |
20:00.03 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
20:01.20 | lupine_85 | dcordes: also also note that hosting copyrighted material is technically illegal, but meh. nobody cares until a takedown notice appears |
20:04.44 | konsta | i know that people have better things to do than answer questions, but if anyone doesn't mind... I've been curious for about a month now as to whether work is progressing on the /dev/smds. I struggle to understand a lot of what floats by on this chan! If not, is that because other things are being dealt with first, or because it's really hard? Wondering whether I should give up checking all this stuff for a couple of months |
20:07.17 | konsta | oh and on the copyright concerns - in the UK and US, most of copyright infringment is classed as civil offences. means worst case scenario is a fine, and like lupine said, no one really cares without the notice these days! |
20:08.40 | cr2 | konsta: smd depends on the cpu, amss and gsm/cdma |
20:09.30 | konsta | so those have to be done first then? |
20:10.02 | cr2 | i think there are 3 different implementations |
20:10.09 | cr2 | maybe even 2 |
20:10.37 | lupine_85 | is happy to host any and all illegal-to-distribute content on his server, incidentally |
20:10.59 | konsta | i always used to think i was computer literate untill i started watching people discuss kernel development |
20:11.23 | konsta | in fact i thought i was a 3 Star Nerd |
20:11.33 | konsta | apparently there are higher echelons |
20:11.40 | cr2 | lupine_85: lol. what do you mean ? |
20:12.40 | cr2 | lupine_85: there are no logs, and i've missed the beginning |
20:13.48 | lupine_85 | cr2: regarding copyrighted stuff related to this project |
20:13.59 | lupine_85 | i.e., stuff we don't have permission to distribute |
20:15.36 | cr2 | ok. |
20:17.16 | cr2 | btw, how do i enable the tv out in raph ? |
20:17.27 | cr2 | i don#t have the cable, but anyway |
20:17.31 | *** join/#htc-linux Xime (n=xime@bankize.net) |
20:19.14 | cr2 | kiozen: i dont' remember, have you seen this one : http://garmin.blogs.com/pr/2009/01/introducing-basecamp-garmins-new-tool-for-planning-and-reviewing-all-of-your-outdoor-adventures.html |
20:21.10 | kiozen | cr2: yes I have seen, who cares what Garmin does ;) |
20:21.20 | cr2 | lol |
20:21.36 | cr2 | but they learn from you :) |
20:21.46 | kiozen | and magellan |
20:21.52 | kiozen | and delorm |
20:22.07 | kiozen | the others are just to stupid to keep their customers |
20:22.34 | cr2 | kiozen: where do we buy triton ? you know i m a luddite and don't have a credit card |
20:22.46 | kiozen | lol!!! |
20:23.08 | kiozen | I am currently on the magellan forum to investigate about their map formats |
20:23.37 | cr2 | what gps chipset do they use ? |
20:23.40 | kiozen | if that leads to something usable i buy one |
20:23.44 | kiozen | sirf |
20:23.59 | cr2 | good |
20:25.45 | kiozen | they use a Raima 4.5 database for their maps |
20:27.28 | kiozen | there are plenty of tools, but as usual nobody wants to talk |
20:27.35 | kiozen | and those talking have no clue |
20:29.46 | cr2 | hmm. |
20:30.00 | cr2 | what is raima4.5 ? |
20:30.29 | cr2 | do they use some db with 256x256 jpeg tiles ? |
20:31.35 | lupine_85 | cr2: OEM_Misc.dll deals with the TV-Out |
20:31.47 | lupine_85 | in WinMo, it has an app that pops up and asks how you want it configuring |
20:32.34 | cr2 | lupine_85: only on the software side |
20:32.49 | kiozen | cr2: relational database |
20:32.49 | dcordes | cr2: 20:02 < dcordes> did somebody deal with the legal situation of hosting ready made android filesystems? especially reagarding the ril etc. |
20:33.09 | kiozen | cr2: for vectormaps |
20:33.12 | dcordes | (that's what raised the illegal hosting question) |
20:33.28 | dcordes | BabelO: ping |
20:33.42 | cr2 | dcordes: why not document the api and AT commands, and reimplement it ? |
20:33.44 | cr2 | kiozen: ok |
20:34.02 | dcordes | cr2: as you know there is msm modem in frameworkd. |
20:34.28 | cr2 | dcordes: don't know what is frameworkd |
20:34.37 | dcordes | cr2: I want to extend it by providing access to audio routing |
20:34.56 | cr2 | dcordes: devspecific ? |
20:35.02 | dcordes | yea |
20:35.17 | cr2 | ril_devspecific was provided by htc since ages |
20:35.27 | cr2 | for the at@foobar commands |
20:35.54 | cr2 | you can see a lot of weird at@ commands in amss |
20:37.16 | dcordes | cr2: http://www.freesmartphone.org http://www.freesmartphone.org/index.php/Implementations |
20:37.30 | dcordes | cr2: is there any amss where we can set audio routing state by AT ? |
20:38.13 | cr2 | i know that fm radio on raph uses some at@audiopath, or something like that |
20:38.39 | dcordes | cr2: http://git.freesmartphone.org/?p=framework.git;a=tree;h=refs/heads/master;hb=refs/heads/master here is the framework source |
20:39.42 | dcordes | cr2: here is the msm specifc part for the ogsmd (modem api) http://git.freesmartphone.org/?p=framework.git;a=tree;f=framework/subsystems/ogsmd/modems/qualcomm_msm;hb=refs/heads/master |
20:40.08 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
20:40.45 | dcordes | it works on A and non A. the 7200 have speaker audio routing state ootb so you can make calls there. |
20:44.04 | j0b0 | NetRipper i made a diff that adds failure handling to navi probe and one that zeroes on fail and one more check to microp-klt,-ksc |
20:44.04 | j0b0 | they are there --> http://tibook.jb.b4m.com/j0b0/diffs-commits/ |
20:46.46 | *** join/#htc-linux timebomb (n=tb@e176096224.adsl.alicedsl.de) |
20:47.44 | cr2 | dcordes: .py ?? |
20:48.22 | dcordes | cr2: why not? |
20:48.34 | dcordes | java ?? |
20:48.48 | cr2 | more or less the same :) |
20:49.21 | cr2 | if i have the source code, i can use a compiler |
20:49.47 | dcordes | so.. |
20:52.14 | kiozen | wiseass says: python need no compiler |
20:53.44 | dcordes | cr2: you think there are performance problem using python? |
20:56.12 | cr2 | no |
20:56.31 | cr2 | but it's nice to have a unified infrastructure |
20:56.57 | *** join/#htc-linux opennandra (n=opennand@afrodita.advanet.sk) |
20:57.02 | cr2 | and i don't understand why you would like to write such lowlevel software in highlevel language |
20:57.45 | cr2 | there was gsmd, why reinvent the wheel ? |
20:57.55 | dcordes | I'm no wiseass but one reason I can see and already experienced is it's easier to try out things. which is very useful for the many different targets |
20:58.05 | dcordes | I don't know why they dropped gsmd |
20:58.10 | opennandra | hi I'm trying to port linux on htc oxygen but have a problems with display. I have values for TIMING registers but could you point me to some script whichcan parse and result will be values for lcd_panel structure? |
20:58.11 | dcordes | maybe because it was too static |
20:58.24 | dcordes | hence the modular structure of framework |
20:59.19 | cr2 | opennandra: omap850 ? |
20:59.27 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
20:59.27 | opennandra | yeah |
20:59.37 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089163.pool.mediaWays.net) |
20:59.38 | cr2 | dcordes: i use 'cu' and 'pon' for UMTS :) |
20:59.53 | kiozen | dcordes: that's what python is good for |
21:00.09 | cr2 | opennandra: 99% of the dicussion here is about msm these days... |
21:00.10 | kiozen | dcordes: large projects become a PITA |
21:00.55 | kiozen | can tell maintaining python stuff > 10000 lines of code |
21:01.04 | opennandra | ok I don't want to discuss just need script :) |
21:01.12 | cr2 | kiozen: and the error handling is usually suboptimal |
21:01.30 | kiozen | well, actually it's very good on python |
21:01.40 | kiozen | but as there is no compiler |
21:02.00 | kiozen | you won't get an exception until you reach the code line |
21:02.19 | cr2 | opennandra: i've written something for pxa, but not omap850 |
21:02.44 | opennandra | could you also get a pixel_clock with your script? |
21:02.44 | kiozen | and that is bad for testing and releasing |
21:02.51 | cr2 | yeah. |
21:03.14 | opennandra | if you could share I can modify for omap850 |
21:07.06 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-033.ewe-ip-backbone.de) |
21:07.27 | *** join/#htc-linux acsviluppo (n=acsvilup@94.163.141.11) |
21:09.25 | opennandra | cr2:marek.belisko@open-nandra.com |
21:13.19 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
21:18.49 | miknix | opennandra, http://pastebin.com/d11c27638 <-- to convert lcd registers into omap_lcd structure params |
21:20.40 | opennandra | miknix: it's possible to get also pixel_clock somehow? |
21:21.50 | miknix | opennandra, look at PRINT pcd |
21:22.00 | miknix | its pixel clock divisor |
21:23.20 | miknix | look at omap_lcd sources to know what the divisor value is, so you can calculate the real pixel clock |
21:25.48 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
21:26.13 | opennandra | I'll already look but is my assumption correct? omap clock = 195Mhz, pcd=29 =>195000000/29/1000=6724khz is pixel_clock? |
21:26.26 | dcordes | cr2: kiozen it seems to work well though |
21:27.57 | kiozen | dcordes: yes python is great, but it's suffers the bad parts as any script lnguage |
21:28.20 | cr2 | opennandra: the pxa code can't be of any use for you |
21:28.37 | miknix | opennandra, yes |
21:28.48 | opennandra | cr2 thanks miknix point me to script |
21:29.40 | miknix | ali1234 has one haret script that does the same if im not wrong |
21:32.36 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-033.ewe-ip-backbone.de) |
21:34.15 | *** join/#htc-linux acsviluppo (n=acsvilup@151.67.25.61) |
21:35.55 | ali1234 | http://al.robotfuzz.com/~al/wizard/lcdcalc.html |
21:36.16 | opennandra | ali1234 thanks |
21:36.17 | ali1234 | paste in the output from haret. it does the same as miknix' C code, except with a few more things |
21:38.37 | miknix | ali1234, is it php? |
21:38.43 | ali1234 | javascript |
21:39.05 | miknix | ali1234, dont want to move it to the linwizard.sfnet page? |
21:39.42 | ali1234 | i don't know how |
21:39.53 | opennandra | whats the meaning of last line IOE = 0PHSVSRF = 0PHSVS = 1 |
21:40.04 | ali1234 | can't remember :) |
21:40.11 | opennandra | ;) |
21:43.06 | *** join/#htc-linux MethoS-- (n=lem@host-091-096-211-037.ewe-ip-backbone.de) |
21:55.01 | *** join/#htc-linux MethoS- (n=lem@host-091-096-211-037.ewe-ip-backbone.de) |
21:58.24 | *** part/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl) |
22:07.38 | dcordes | cr2: do you have OE ? |
22:18.01 | cr2 | no |
22:19.08 | dcordes | you can make fso-image or fso-csoneole-image with OE which has everything needed to try frameworkd on raph |
22:22.59 | *** join/#htc-linux acsviluppo (n=acsvilup@151.67.25.61) |
22:29.41 | dcordes | Das neue T-Mobile G1 mit Googel |
22:30.16 | lama | http://www.pocket-lint.co.uk/news/news.phtml/21961/22985/video-film-megawhat-toshiba-tg01.phtml |
22:30.26 | lama | 1Ghz :P |
22:30.38 | lama | huge huge screen |
22:31.48 | AstainZZZZZZ | too bad its qualcomm |
22:32.38 | dcordes | AstainZZZZZZ: which chipset is it? |
22:32.48 | cr2 | lama: huge huge screen. LOL |
22:33.53 | AstainZZZZZZ | dcordes Snapdragon |
22:34.08 | lama | there aren't many 4.1 screens in such "small" devices |
22:34.22 | AstainZZZZZZ | the new athena is bigger lama |
22:34.46 | lama | yes it is bigger :P |
22:34.48 | lama | much bigger |
22:35.10 | dcordes | AstainZZZZZZ: is there some non marketing name for it? |
22:35.13 | lama | this is close to touch hd and iphone size device |
22:36.51 | AstainZZZZZZ | prefers the tegra chipset by nvidia |
22:37.29 | lama | is there any info about real devices upcoming this year with tegra? |
22:37.48 | dcordes | I guess it's a 7xxxA with higher clocks |
22:40.38 | *** join/#htc-linux Xime (n=xime@bankize.net) |
22:40.40 | dcordes | QSD8672 |
22:41.10 | cr2 | wtf? |
22:42.38 | dcordes | so there is the ARM notebook I've been waiting for |
22:43.56 | *** join/#htc-linux zenned (n=azenned@41.224.222.105) |
22:48.47 | *** join/#htc-linux MethoS-- (n=lem@dyndsl-085-016-166-065.ewe-ip-backbone.de) |
22:50.10 | *** join/#htc-linux Xime (n=xime@bankize.net) |
22:53.37 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
22:54.02 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
23:13.23 | *** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca) |
23:14.51 | *** join/#htc-linux dcordes (n=dcordes_@f054219095.adsl.alicedsl.de) |
23:16.16 | *** join/#htc-linux dcordes_ (n=dcordes_@f054219095.adsl.alicedsl.de) |
23:25.08 | *** join/#htc-linux acsviluppo (n=acsvilup@151.67.25.61) |
23:29.33 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-165-097.ewe-ip-backbone.de) |
23:33.06 | *** join/#htc-linux smile30 (n=smile30@78.130.73.22.rev.optimus.pt) |
23:35.14 | *** join/#htc-linux bs2 (n=kra@87.72.13.87) |
23:39.02 | NetRipper | j0b0, pushed your last two patches |
23:41.36 | j0b0 | thanks i shall pull them |
23:51.55 | *** join/#htc-linux Kuma (n=John@g227119032.adsl.alicedsl.de) |
23:57.10 | *** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com) |
23:58.48 | cr2 | maejrep[w]: i have 3 clock settings for uartDM now |
23:59.06 | cr2 | trying to decode... |