IRC log for #htc-linux on 20100131

00:04.36*** join/#htc-linux Guest44207 (chamonix@unaffiliated/chamonix)
00:06.31*** join/#htc-linux dekar (~dekar@port-92-193-124-146.dynamic.qsc.de)
00:24.56*** join/#htc-linux leaigor (~laigor@188.134.16.241)
00:37.10*** part/#htc-linux ali1234 (~al@robotfuzz.co.uk)
00:47.57*** join/#htc-linux jumoit (~samuel@121.77.87.145)
00:53.07*** join/#htc-linux zycho (~zycho@g227176178.adsl.alicedsl.de)
01:00.48makkonenarrrghhh: that's exceedingly strange. builds fine on my end.
01:04.00*** join/#htc-linux Unholy (~IceChat7@24.227.27.77)
01:21.45polyrhythmichere's a new one
01:22.04polyrhythmicso I was booting android from haret and it segfaulted
01:22.15polyrhythmicso I soft reset my Kaiser, and I get the tri-color screen
01:25.37polyrhythmicwell it only took 3 battery removals and 8 soft resets but it has found itself again
01:27.03polyrhythmicmaybe I shouldn't take it skiing anymore.
01:54.15*** join/#htc-linux swc|666 (~infidel20@unaffiliated/swc666/x-4934821)
02:10.24*** join/#htc-linux zycho_ (~zycho@g227201218.adsl.alicedsl.de)
02:30.55*** join/#htc-linux bkero (~bkero@osuosl/staff/bkero)
02:40.49JdGordonis anyone here an OP in #replicant?
02:41.18JdGordonor can fix the sflc_log bot?
02:43.46*** join/#htc-linux Forsaken|Desk1 (~Forsaken@dslb-084-058-245-009.pools.arcor-ip.net)
02:48.26*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
02:56.46*** part/#htc-linux shakaran (~shakaran@169.Red-83-35-49.dynamicIP.rima-tde.net)
02:57.40ToAsTcfhtmzt: who was that lady u had me send those utilities to? i wanna know if she may have one i can use
02:58.57ToAsTcfhphh: vgrabber wont even work on a sapphire that has v4l2 on it. it causes it to reboot also
03:13.15*** join/#htc-linux jumoit (~samuel@121.77.87.145)
03:14.18*** join/#htc-linux arrrghhh (~arrrghhh@c-71-196-233-184.hsd1.co.comcast.net)
03:27.39*** join/#htc-linux arrrghhh_ (~arrrghhh@c-71-196-233-184.hsd1.co.comcast.net)
03:28.29*** join/#htc-linux arrrghhh (~arrrghhh@c-71-196-233-184.hsd1.co.comcast.net)
03:33.13*** join/#htc-linux StarLite` (~nnscript@s55916cb1.adsl.wanadoo.nl)
03:47.51*** join/#htc-linux Forsaken|Desk (~Forsaken@dslb-084-058-253-078.pools.arcor-ip.net)
03:59.15tmztToAsTcfh: cmonex? she's in #xda-devs
03:59.39tmztyou don't provide enough details ever, heroc is not enough
03:59.46tmztit doesn't say which driver
04:10.14ToAsTcfhtmzt: ive been trying to use v4l2
04:10.31ToAsTcfhbut yeah man thanx
04:14.32*** join/#htc-linux arrrghhh (~arrrghhh@c-71-196-233-184.hsd1.co.comcast.net)
04:15.23ToAsTcfhi wish there was a utility to to just test if msmcamera or v4l2 kernel drivers are working properly. we think were real close but we cant see what the issue is
04:15.45tmztthere are many
04:15.51ToAsTcfhlike?
04:15.52tmztthe issue is probably dma
04:15.55ToAsTcfhi searched
04:15.59tmztwe should work through this
04:16.06tmztv4l-config to start with
04:16.14tmztluvcview with mods
04:16.21tmztrecord maybe
04:16.29tmztfrom xawtv-utils package
04:16.36tmztstreamer
04:16.44ToAsTcfhv4l-config i couldnt get to compile
04:16.55tmztcat, with help from v4l-config
04:17.07tmztthen you don't have headers
04:24.13*** join/#htc-linux MrPippy (~pip@adsl-75-37-167-3.dsl.sndg02.sbcglobal.net)
05:01.59*** join/#htc-linux droid0011 (~g1@p4FDCBFE1.dip.t-dialin.net)
05:54.18*** join/#htc-linux amjad (~amjadduba@86.99.239.127)
06:00.59*** join/#htc-linux kad_ (~kad@219-89-117-161.adsl.xtra.co.nz)
06:01.40*** join/#htc-linux droid001 (~g1@p4FDCA57F.dip.t-dialin.net)
06:08.03*** join/#htc-linux Forsaken|Desk1 (~Forsaken@dslb-084-058-224-247.pools.arcor-ip.net)
06:11.26*** join/#htc-linux BHSPitLappy (~BHSPitLap@unaffiliated/bhspitmonkey)
07:26.06*** join/#htc-linux luc_ (~luc@89-115-128-35.cl.ipv4ilink.net)
07:53.32*** join/#htc-linux kiozen (~oeichler@rgnb-5d87c8ba.pool.mediaWays.net)
08:17.10*** join/#htc-linux cyberdesigner (~cyberdesi@port-92-206-189-164.dynamic.qsc.de)
08:26.43*** join/#htc-linux luc_ (~luc@89-115-128-35.cl.ipv4ilink.net)
08:29.32*** join/#htc-linux cyberdesigner (~cyberdesi@port-92-206-189-164.dynamic.qsc.de)
08:43.23*** join/#htc-linux toi (~toi@d54C2A96D.access.telenet.be)
08:44.06*** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk)
08:47.11*** join/#htc-linux Forsaken|Desk (~Forsaken@dslb-084-058-192-032.pools.arcor-ip.net)
09:01.17*** join/#htc-linux fish1209_ (~fish1209@75-92-35-227.war.clearwire-wmx.net)
09:03.53*** part/#htc-linux fish1209_ (~fish1209@75-92-35-227.war.clearwire-wmx.net)
09:04.19*** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912)
09:06.56*** join/#htc-linux malgon (~simon@ABordeaux-257-1-153-92.w90-60.abo.wanadoo.fr)
09:07.14*** join/#htc-linux MrPippy_ (~pip@adsl-75-37-167-3.dsl.sndg02.sbcglobal.net)
09:13.06*** join/#htc-linux maejrep (~madcoder@c-68-42-30-56.hsd1.pa.comcast.net)
09:21.53*** join/#htc-linux cyberdesigner (~cyberdesi@port-92-206-189-164.dynamic.qsc.de)
09:23.34*** part/#htc-linux nashpa (~dliviu@dliviu.plus.com)
09:37.35*** join/#htc-linux BabelO (~fcr@unaffiliated/babelo)
09:37.39*** join/#htc-linux leobaillard (~leobailla@leobaillard.org)
09:53.03*** part/#htc-linux mickey|dinner (~mickey@80.81.242.146)
10:06.00*** join/#htc-linux Squarc (~Squarc@82-217-32-29.cable.quicknet.nl)
10:17.29*** join/#htc-linux aabisaky (~aabisaky@79.112.231.64)
10:19.18phhany TD2/TP2 user around ?
10:34.13*** part/#htc-linux aabisaky (~aabisaky@79.112.231.64)
10:45.20chamonixhello guys
10:45.26phhhi chamonix
10:45.30phhchamonix: read your logs
10:46.24phhgroumpf, uid/gid got screwed
10:46.27phhI have to fix all perms by hand
10:46.34phhor start again from a brand new data.img
10:49.11*** join/#htc-linux M1DLGpc_ (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk)
10:51.13*** join/#htc-linux Forsaken|Desk1 (~Forsaken@dslb-084-059-011-246.pools.arcor-ip.net)
10:59.36chamonixphh: I finally figured out how to run shell commands from java and borrowed some code from terminal so reading/writing everywhere works now
10:59.44phhpfff
10:59.47phhI setted 666 perms -_-'
11:02.03phhchamonix: anyway, when do you think you'll have some cool stuff to show about that ? :p
11:04.48chamonixI'm starting right now with the basics but have to do some stuff for work today so I'm not sure I'll be done today
11:04.52*** join/#htc-linux kvaster (~kvaster@live.bn.by)
11:04.54phh:'(
11:24.51chamonixphh: it there any way to load modules with insmod despite the magic cookie mismatch?
11:25.10phhwith correct insmod tool with -f option
11:25.49chamonixok, I don't have the correct one then :-/ there's no -f
11:28.45phhwhy do you want that ?
11:28.51phhneed wifi+ramzswap modules ?
11:29.03chamonixexactly
11:29.20chamonixor Image :)
11:29.31phhchamonix: we will do with an other way.
11:30.08chamonixI looked at extracting from zImage but didn't quite get it
11:30.09phhchamonix: I'll add yaffs to the modules and then create a initramfs.gz which loads the modules from glemsom's modules
11:31.26phhtime to eat.
11:32.21chamonixbon ap'
11:35.48*** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk)
11:55.44phhchamonix: so download latest zImage +modules at http://zimages.googlecode.com/svn/autobuild_system/htc-msm-android/zImage-modules-20100131_124003.tar
11:56.37phhthen extract the modules, copy yaffs2 and mtd_* in the initramfs
11:56.43phhedit the init file of the initramfs to load the correct modules
11:56.45phhet voila.
11:59.08*** join/#htc-linux GNUtoo|oeee (~GNUtoo@host46-130-dynamic.244-95-r.retail.telecomitalia.it)
12:01.16chamonixcool! ty
12:02.56*** join/#htc-linux kvaster (~kvaster@live.bn.by)
12:03.29phhchamonix: I can make you a script if you want
12:09.52*** join/#htc-linux adamw (~adamw@S010600226b8aa2ea.vc.shawcable.net)
12:09.59phhhi adamw
12:10.06*** join/#htc-linux leaigor (~laigor@188.134.16.241)
12:11.20*** join/#htc-linux adamw (~adamw@redhat/adamw)
12:12.05adamwphh: hey
12:12.05adamwphh: ahh, i see the newer one now, i must've just grabbed it before the newer one showed up
12:12.29adamwok, gimme 5 mins i'll test with the 124003 - that one will be OK?
12:12.36phhyes
12:12.53adamwok
12:13.23*** join/#htc-linux MethoS- (~clemens@134.102.106.250)
12:16.12adamwphh: booting now
12:16.26phhchamonix: you're booting too ?
12:16.51adamwnice buildsystem btw! didn't know it existed till now
12:19.02phhyes I love it too, thanks to GlemSom :)
12:19.36adamwdamn now i have to get the soft keyboard up somehow...there's no way i can find to get a / out of the tilt2 keyboard atm hehe
12:19.53phhyou have to be in portrait
12:19.58phhand then longpress on home button
12:20.00phhhum menu button
12:20.13phhwell you see what I mean.
12:21.02*** join/#htc-linux zachy (~george@85.193.4.18)
12:21.57chamonixphh: no I'll do that later, I first want  to finish the basic service responding on battery, sms, incoming call, cell change etc
12:23.27adamwdamn, nope. that don't work. i got it up last boot by accident, can't make it happen again. grr
12:23.56adamwah got it
12:27.28adamwwhew, okay, that was annoying. with keyboard out: 562958543290368
12:28.08adamwand...seems the same with keyboard in
12:28.14phhbaahh
12:28.24phhseems or is ?
12:28.27adamwis
12:28.29phh:'(
12:28.30adamwtried it a few times
12:28.42adamwi can close out console and reload it or something?
12:28.56phhno it means my code or my guess is wrong
12:28.56adamwshouldn't change it though. if android behaves how i'd expect :)
12:29.35adamwanything else I can get you?
12:29.46phhsome ideas ? :p
12:30.54adamwheh, if this were hardware and a linux implementation I knew anything about, sure :D
12:31.26phhadamw: can you see if auto_backlight works at least ?
12:31.56phhchamonix: oh and I need a GUI to set this btw.
12:32.01adamwphh: define 'works'
12:32.18phhadamw: if writing 1 to it enables automatic backlight diming
12:32.37*** join/#htc-linux cr2_ (~cr2@ip-109-84-103-180.web.vodafone.de)
12:32.41adamwok.
12:33.22chamonixphh: generic GUI is finished, just needs testing
12:33.28cr2_hi
12:33.53adamwman, i really could do with some tab completion on this thing
12:33.54adamwalso, a tab key
12:33.58chamonix...and I need a list of all the stuff that can be written/read
12:34.08cr2_phh: can you add printk for pll settings after calling dex_1d(2) ?
12:34.25chamonixi'll grep logs for "echo.*>"
12:34.31phhcr2_: sure
12:34.44phhcr2_: I haven't seen any side effect of this dex yet though
12:35.01cr2_hm
12:35.04cr2_static unsigned int pll_get_rate(int n)
12:35.08cr2_it's static
12:35.19phhcr2_: dump_debug_stuff :p
12:36.21cr2_ok
12:36.53cr2_idx2pll can be also dumped. if we use the pll index directly
12:38.10cr2_phh: about microp
12:38.13cr2_<PROTECTED>
12:38.15cr2_<PROTECTED>
12:38.16cr2_<PROTECTED>
12:38.28cr2_do we know the bit meanings ?
12:38.31phhno
12:38.50adamwphh: um. if I do echo 1 > /dbgfs/micropklt_dbg/auto_backlight , then cat /dbgfs/micropklt_dbg/auto_backlight , it still shows 0
12:38.57phhadamw: yes it's write only
12:39.02cr2_maybe we can split the values into bitmasks ?
12:39.07cr2_phh: i think partially
12:39.29adamwphh: ah, k. so what should it do?
12:39.31phhcr2_: I haven't seen any doc/source for it yet
12:39.36cr2_lol
12:39.37phhcr2_: but you know (almost) everything ? :p
12:39.38cr2_<PROTECTED>
12:39.56phhadamw: bah see if the backlight dims when approaching a light
12:39.57cr2_i think some bits are known
12:40.14adamwphh: k
12:40.18cr2_precess_spi_table
12:40.20cr2_lol
12:40.25cr2_is it precessing ?
12:40.34phhI guess markinus meant processing
12:40.54cr2_char c0[]={spicmd,
12:40.55cr2_ok
12:41.12cr2_are all commands char ?
12:41.27phhcommand ID you mean ? it seems so yes
12:41.37cr2_unsigned ?
12:41.43cr2_no, the data too
12:41.57phhno, led takes a short
12:42.06phh(or two chars, it's a matter of point of view)
12:42.15adamwphh: I don't think it is. slightly hard to tell for sure, though.
12:42.25adamwusually i'd test by going outside, but hey, it's 4:40am :)
12:42.39phhhum ok, will be for another day
12:42.48phhadamw: can you retry the gpi stuff with http://husson.hd.free.fr/zImage ?
12:42.53cr2_ok
12:43.06adamwfrom what i can judge, though, it's basically on highest brightness setting possible even with no ambient light, when winmo would set it pretty low
12:43.20adamwphh: OK, just a sec
12:45.36phhcr2_: do you want me to complete microp wiki page with mahimahi's infos ?
12:46.41adamwi'd best make this my last test for tonight, sorry - pretty late here :)
12:46.42*** join/#htc-linux zycho (~zycho@g227201218.adsl.alicedsl.de)
12:49.16cr2_phh: maybe rebuild it as a table ?
12:49.37phhcr2_: I don't know how to do that currently, but ok
12:49.42cr2_phh: columns for r/w and device
12:50.12cr2_phh: i think data tables can be added as subpages
12:50.13adamwphh: well, um. different, but i think not better :) with new zImage it's 0 whether keyboard is in or out
12:50.20phhadamw: ok
12:50.29cr2_phh: maybe rename it MSM_MICROP ?
12:50.41cr2_phh: RaphaelDEX is certainly MSM_DEX
12:50.51phhbwah, everything is already called rapahel* :p
12:50.52phhraphael*
12:50.56cr2_because it's the same implementation on all wince
12:51.03cr2_ok
12:51.28cr2_MSM_CLK , MSM_VREG,
12:52.50phh[  314.477752] Sending arm9_low_speed 7
12:52.50phh[  314.477905] PLL0 @ f8005300: MODE=00000007 L=0000000c M=00000004 N=00000005 freq=245760000 Hz (245 MHz)
12:52.50phh[  314.478057] PLL1 @ f800531c: MODE=00000007 L=00000028 M=00000000 N=00000001 freq=768000000 Hz (768 MHz)
12:52.50phh[  314.478210] PLL2 @ f8005338: MODE=00000007 L=00000037 M=00000000 N=00000001 freq=1056000000 Hz (1056 MHz)
12:52.50phh[  314.478363] PLL3 @ f8005354: MODE=00000000 L=0000002d M=00000000 N=00000001 freq=864000000 Hz (864 MHz)
12:52.56phh[  239.183319] Sending arm9_low_speed 2
12:52.56phh[  239.183563] PLL0 @ f8005300: MODE=00000007 L=0000000c M=00000004 N=00000005 freq=245760000 Hz (245 MHz)
12:52.56phh[  239.183715] PLL1 @ f800531c: MODE=00000007 L=00000028 M=00000000 N=00000001 freq=768000000 Hz (768 MHz)
12:52.57phh[  239.183837] PLL2 @ f8005338: MODE=00000007 L=00000037 M=00000000 N=00000001 freq=1056000000 Hz (1056 MHz)
12:53.00phh[  239.184051] PLL3 @ f8005354: MODE=00000000 L=0000002d M=00000000 N=00000001 freq=864000000 Hz (864 MHz)
12:53.04phhdoesn't seem to change much.
12:53.33adamwphh: fwiw, with that latest zimage, removing and inserting the stylus seems to trigger the onscreen keyboard to open and close, rather than switching from landscape to portrait
12:53.36adamwdunno if that tells you anything
12:53.46phhadamw: not at all
12:54.12adamwwell, on home screen it still switches. but in console it triggers the soft keyboard. odd.
12:54.37phhnot linked with what I changed anyway
12:54.43cr2_phh: maybe it's really only LOCK_BUS
12:54.56phhcr2_: modem clock is directly a pll ?
12:55.00phhit's not derivated from a pll ?
12:55.02adamwhmm, now it's not doing that any more. must've just been that one freak time. oh well. it's late, i'm off to bed
12:55.09cr2_phh: mpll is pll0
12:55.25phhyes but maybe modem's clock has a MD/NS
12:55.29adamwi'm almost always online here, let me know if you need anything (simple) from my tilt2 :) thanks a lot again for your efforts
12:55.41cr2_phh: no
12:56.18phhmight also be ebi clock
12:56.18cr2_phh: at least we don't know it
12:56.19cr2_ebi is ebi
12:56.55cr2_btw, can we compare smi and ebi1 speed ?
12:57.22cr2_to know how faster is smi
12:57.42phhwith pmem it's really easy :D
13:00.12cr2_NetRipper: ping
13:00.53*** join/#htc-linux Captnoord (~Captnoord@dc5147a47b.adsl.wanadoo.nl)
13:06.20phhEBI
13:06.21phh1264943166.390000 -> 1264943166.770000
13:06.21phhSMI
13:06.21phh1264943166.770000 -> 1264943167.180000
13:06.23phhI let you do the maths
13:06.49cr2_look identic
13:06.49Captnoordhex?
13:07.05cr2_where do these numbers come from ?
13:07.13phhcr2_: quick test tool
13:07.24cr2_?
13:07.34phhhttp://pastebin.com/m277f736a
13:08.37phh(hw3dm offset 0 is in smi, pmem_adsp is ebi)
13:08.48phhoops
13:08.50cr2_i need to check the bus timings
13:08.55phhhw3dm offset 0 is ebi
13:09.03cr2_hehe :)
13:11.58phh1<<28 = 0x10000 ?
13:12.10phhI think someone (compiler or strace.) is making fun on me.
13:13.24cr2_yes. the next is 32
13:13.45cr2_16+4=20
13:14.00cr2_28 is 0x1000000
13:14.35cr2_Captnoord: what battery offsets did you find at 0x81000+ ?
13:14.50cr2_wiki says
13:14.55cr2_+0x081400  0x80  battery  struct
13:16.11Captnoordlol
13:16.12Captnoordlemme get it
13:16.22phhcr2_: 0x80 is the size ?
13:16.28cr2_yes
13:16.41cr2_0x80/4=0x20 elements
13:17.11cr2_the values are put there by battery .dll
13:17.34cr2_i guess powermon reads there
13:17.35CaptnoordLDR     R5, =0xAA0FC0E4
13:17.36CaptnoordLDR     R4, =0xAA0FC0E0
13:17.36CaptnoordCMP     R0, #0
13:17.36CaptnoordLDRNE   R2, [R5]
13:17.36CaptnoordLDRNE   R1, [R4]
13:17.36CaptnoordLDRNE   R0, =aInitbatteryset ; "!InitBatterySettings, VREF=%d,1/2 VREF="...
13:17.38Captnoordyou mean those?
13:17.40cr2_need too mmutrace the area
13:17.52CaptnoordLDR     R8, =0xA808143C
13:17.52CaptnoordMOV     R9, #0
13:17.53CaptnoordLDR     R6, =0xA8081440
13:17.54cr2_Captnoord: it's the +fc000 area
13:17.57phhcr2_: hum, hero's smem stuff has 44 entries
13:17.57Captnoordk
13:18.09cr2_phh: link ?
13:18.31cr2_Captnoord: so, +3c and +40. that looks good
13:18.32phhcr2_: you have hero's kernel source ?
13:18.37CaptnoordLDR     R8, =0xA808143C
13:18.37CaptnoordMOV     R9, #0
13:18.37CaptnoordLDR     R6, =0xA8081440
13:18.39Captnoordweoeps
13:18.40Captnoordlolz
13:18.41phhit's in arch/arm/mach-msm/htc_battery around line 600
13:18.43Captnoord22:50  Captnoord  +0xfc0e0 VREF
13:18.43Captnoord22:50 Captnoord +0xfc0e4 1/2 VREF
13:18.45cr2_Captnoord: now we only need to guess the struct names
13:19.05cr2_Captnoord: the 0xfc000 is known
13:19.10cr2_Captnoord: and documented
13:19.14Captnoordk
13:19.19Captnoordyou need the other
13:19.19Captnoordkl
13:19.22cr2_Captnoord: the +0x81000 is wince internal
13:19.31*** part/#htc-linux zachy (~george@85.193.4.18)
13:20.03cr2_phh: yes. but a gitweb link is easier. i don't need to use the editor :)
13:20.27phhi've never seen that in in a gitweb
13:20.31cr2_ok
13:20.50CaptnoordCaptnoord  LDR dwChargeFullTimeDiff, =0xA808146C
13:20.51Captnoord22:37 Captnoord LDR dwBatteryChargedCapacity, =0xA8081438
13:20.52Captnoordthose
13:21.13cr2_Captnoord: looks good
13:21.25CaptnoordBatteryLifePercent, =0xA8081482
13:21.41cr2_82 is in .power ?
13:21.58phhcr2_: http://pastebin.com/m12afb3e1
13:22.37cr2_phh: heh. this is not the memory layout, only the struct
13:22.44phhcr2_: no it's memory layout
13:22.52phhcr2_: it's used as is with a smem_alloc
13:22.57cr2_on heroc, or on wince ?
13:23.04phhhero gsm
13:23.15cr2_different amss ;)
13:23.28phhyes, but they might share some part
13:23.42Captnoordpower.BatteryLifePercent=%d battery.dwPredictPercentage=%>
13:24.03cr2_Captnoord: yes. .power
13:24.16Captnoordcrap.....
13:24.24Captnoordida doesn't makes my life easier
13:24.29Captnoordwhen a register is named
13:24.31Captnoordeverything changes
13:24.32Captnoordlolz
13:24.36cr2_Captnoord: battery.dwPredictPercentage ?
13:24.36Captnoordconfusing
13:24.42Captnoordyea
13:24.44cr2_Captnoord: which offset is that ?
13:24.51Captnoordsearching for it
13:24.51cr2_i'll edit wiki
13:25.29cr2_phh: then you only need to backtrack how they calculate these
13:25.47Captnoordcr2 it where function arguments
13:25.47phhcalculate what ?
13:25.47Captnoord:S
13:26.12cr2_BatteryLifePercent and such
13:26.26Captnoordyup
13:30.02Captnoordlol
13:30.03Captnoordnope
13:30.13Captnoordhmmmm
13:30.14Captnoordk
13:30.20CaptnoordI need to write them down
13:30.23Captnoordwould be way better
13:30.30Captnoordinstead of looking around
13:31.03cr2_battery life percent is 16bit
13:31.16cr2_Captnoord: i'm editing wiki
13:32.04cr2_http://htc-linux.org/wiki/index.php?title=RaphaelMemoryMap
13:32.25CaptnoordI know
13:32.31Captnoordbut its a personal thingy
13:32.36cr2_added your values already
13:32.37Captnoordneed to organise
13:32.41Captnoordperfect
13:32.41cr2_ok
13:32.42Captnoordthanks
13:32.42*** join/#htc-linux dcordes (~dcordes__@unaffiliated/dcordes)
13:36.36cr2_Captnoord: GetBatteryIDDetection, battery.dwVendor = 2 ?
13:38.03Captnoordthats a easy one
13:38.16dcordeshi
13:38.45Captnoordcr2_: they got them from 0xAA0FC110 stuff
13:38.58Captnoordnot from the range I am checking
13:39.01Captnoordbatt id
13:39.11Captnoordlets check vendor
13:40.24Captnoordmaybe not
13:40.35cr2_ChargeTimeEnd ?
13:40.39cr2_hi dcordes
13:40.55CaptnoordDEX_Get_Batt_Slope_Kernel
13:40.57cr2_ChargingState ?
13:40.59Captnoordis di/dt
13:41.08cr2_Captnoord: yes, this one is known.
13:41.19*** join/#htc-linux GNUtoo (~GNUtoo@host46-130-dynamic.244-95-r.retail.telecomitalia.it)
13:41.20dcordescr2_, I took some time to read all the htc-msm-2.6.27 changes
13:41.23cr2_but i'm not sure how it is used
13:41.29cr2_dcordes: all ?
13:41.42Captnoordcr2_: I have tryed to explain it once.....
13:41.50Captnoordabout the current curve and stuff
13:42.05dcordescr2_, well everything since I took a break
13:42.18cr2_Captnoord: in wince, not in theory
13:42.23cr2_dcordes: ah, ok
13:42.29dcordescr2_, I'm talking about the gitorious branch
13:42.32dcordesphh kernel
13:42.48phhdcordes: wow, you had a lot of time
13:42.52cr2_dcordes: yes, i didn't follow many things there too
13:43.33dcordesI was a bit shocked first about the commit amount but everything is very well described and not every change is elementary
13:43.57phhdcordes: I keep my commits as little as possible, that helps the number.
13:44.03dcordesphh, yea seems like you put a lot of time in that
13:44.11Captnoordsomething like tis
13:44.12Captnoordthis
13:44.13Captnoordhttp://www.limn2o4.com/battery/charger2.jpg
13:44.14dcordesbetter than huge patches..
13:44.38Captnoordhttp://www.mpoweruk.com/images/nickel_chargers.gif
13:44.54dcordesCaptnoord, that's how it works!
13:44.59dcordesinteresting
13:45.01Captnoordyup
13:45.22CaptnoordI should have know... a picture says loads more than 1000 words
13:45.26Captnoordknown*
13:46.41Captnoordcr2_: most of the +0x81000 memory stuff is beeing set by nk.exe
13:47.00Captnoordas its a temp store for it
13:47.19*** join/#htc-linux cr2_ (~cr2@ip-109-84-103-180.web.vodafone.de)
13:47.29Captnoord14:46] <Captnoord> cr2_: most of the +0x81000 memory stuff is beeing set by nk.exe
13:47.29Captnoord[14:46] *** cr2_ quit (Remote host closed the connection)
13:47.29Captnoord[14:47] <Captnoord> as its a temp store for it
13:47.40Captnoord0xA808141C
13:47.42Captnoordis vendor
13:48.19Captnoordhmmm
13:48.21Captnoordwierd
13:48.35Captnoordyup its vendor....
13:49.15CaptnoordLDR     R4, =0xA808141C
13:49.15CaptnoordMOV     R3, #2
13:49.15CaptnoordSTR     R3, [R4]
13:49.17Captnoordis evil
13:49.20phhcr2_: http://htc-linux.org/wiki/index.php?title=RaphaelMicroP
13:49.22phhsomething like that ?
13:49.30Captnoordthats why the vendor tells ya its 2
13:49.53Captnoordif 0xA8081030 == 0
13:50.04Captnoordit doesn't use smem stuff
13:50.13Captnoordthen vendorid = 2
13:50.56cr2_+0x081030 PCB XC (copy of smem)
13:51.36Captnoordso if there is no copy of smem
13:51.47cr2_it comes from smem
13:51.55cr2_there must be a copy
13:52.03cr2_at nk.exe start
13:52.11Captnoordmaybe its a failsafe
13:52.50cr2_phh: looks good
13:53.00phhI don't understand their amber/red led stuff -_-'
13:53.09CaptnoorddwADC_A, =0xA8081440
13:53.13CaptnoorddwADC_B, =0xA8081444
13:53.18cr2_phh: not used on other
13:53.25cr2_Captnoord: nice
13:53.46cr2_Captnoord: adding to wiki
13:54.38CaptnoorddwPowerOnReason = 0xA808105C
13:54.39Captnoord:S
13:55.55cr2_phh: 3c ?
13:55.59cr2_err
13:56.06cr2_Captnoord: what is 3c ?
13:56.13phhCaptnoord: any reboot reason by any chance ?
13:56.54Captnoord0xA808143c you mean?
13:57.01cr2_yes
13:57.17Captnoordharder one
13:57.26Captnoordno strings related to it as it seems
13:57.28cr2_there should be offsets for ChargeTimeEnd and ChargingState
13:57.32cr2_ok
13:57.32Captnoordbut 'll try
13:57.34Captnoordk
13:57.50CaptnoordI was wrong
13:57.52Captnoordlemme check
13:57.54Captnoordhehe
13:58.49Captnoordonly 2 entry's
13:58.51Captnoordone on init
13:59.02Captnoordand one on getinfo
13:59.41Captnoordcr2_: I think your correct
13:59.48CaptnoordI think 3c == end
13:59.56Captnoordlemme convert the math
14:00.29cr2_wow. you are a wizard :)
14:01.09Captnoordnope...
14:01.18Captnoordjust having a clear day
14:01.29cr2_ok
14:04.27Captnoordbleh arm asm 'MLA'
14:04.31Captnoordis a multiply
14:04.33CaptnoordI know
14:04.35Captnoordbleh
14:05.16Captnoordmla Rd, Rm, Rs, Rn Rd = Rm * Rs + Rn
14:05.24cr2_MLAS ?
14:05.38Captnoordthats signed
14:05.58Captnoordhehehehehehehe
14:05.59Captnoordgot it
14:06.21ToAsTcfhphh: so yeah i think my issues maybe that i dont have msm_camera in /dev. it seems that msm_register uses msm_camera. and thats where the mutex lock comes into play
14:06.55phhCaptnoord: warn me when there is something to code :p
14:07.00Captnoordhehe
14:07.02CaptnoordI will
14:07.03Captnoordlolz
14:08.43ToAsTcfhmsm_register in the msm_v4l2.c isnt defined there its defined in msm_camera.c
14:09.17ToAsTcfhand its strange because i have msm_camera in my config enabled
14:09.33ToAsTcfhand the kernel is stock
14:13.05Captnoordcr2 MLAS == substract
14:13.18Captnoordhmmmm
14:13.19Captnoordnope
14:13.22Captnoordthat was mls
14:13.51Captnoordyup my initial hunge was correct
14:13.52Captnoordits signed
14:15.28cr2_MLAS is signed MLA
14:15.40Captnoordyup
14:15.41cr2_then there was UMULL
14:15.47Captnoordyup
14:15.52Captnoordjust a longlong mull
14:16.01Captnoordr2 and r3 == uint64
14:16.11Captnoordthen you got the shift left 6
14:16.13Captnoordwhich is
14:16.14Captnoordre\lly
14:16.23Captnoordr2r3 >> 14
14:16.27Captnoordreally
14:16.36Captnoordbut the compiler does the speedup
14:16.47The-Decompiledyeah I do
14:17.19cr2_Captnoord: poweron_reason is "TSER" here !?
14:17.38cr2_phh: can you pd 0x8145c 4 ?
14:18.09cr2_err. it's different offset
14:18.58phhnot now
14:19.06Captnoordtouch screen error :P
14:20.34Captnoordcr2_: they are FOURCC's
14:20.52CaptnoordLDR     R2, ='BUTT'
14:20.59CaptnoordPower-Button pressed
14:21.09cr2_0x3dc charge capacity value
14:21.17cr2_Captnoord: yes,i've seen that
14:22.01cr2_hm it was ADC_A
14:22.14cr2_ADC_B is 0x559c
14:22.41CaptnoorddwADC_A =0xA8081440
14:22.41CaptnoorddwADC_B =0xA8081444
14:22.51Captnoordhmmm
14:22.52Captnoordk
14:23.03Captnoordthats goof
14:23.04Captnoordgood
14:23.13Captnoord21916
14:23.18cr2_0x1c504e is charge_full_time_diff
14:23.23Captnoordmicro amps maybe?
14:23.26Captnoordmeaning 21 mA
14:23.43cr2_adc is voltage ?
14:23.43Captnoordthat dt
14:23.46CaptnoordI would guess
14:23.55Captnoordcr2_: doesn't have to be
14:23.57cr2_in what units ?
14:24.01Captnoordtime
14:24.03CaptnoordI don't know
14:24.19cr2_Captnoord: voltage on a known resistance is current :)
14:24.33Captnoordv = i * r
14:24.40Captnoordbut thats not so important for now
14:24.44cr2_ok
14:24.50Captnoorda battery has a capacitance
14:24.52Captnoordlets say
14:24.57Captnoord1200 mA/h
14:24.59Captnoordmeaning
14:25.05phhmAh
14:25.06phhno /
14:25.10phh(just to say.)
14:25.13Captnoordfor 1 hour you can draw a total of 1200ma out of it
14:25.16Captnoordthen its empty
14:25.18cr2_\int I dt
14:25.35Captnoordwhen you messure current beeing drawn from a battery
14:25.39cr2_not really.
14:25.44Captnoordthe simplest thing thing you can do
14:25.47cr2_it's just full charge
14:25.56Captnoordmaybe its discharging
14:26.15Captnoordthe simplest thing would be to use a resistor.... and hook the adc over it
14:26.26Captnoordit will messure the voltage created by the current
14:26.41Captnoordyou need to know the resistors value
14:26.48Captnoordto calculate the current
14:26.51cr2_we don't have a pmic datasheet
14:26.58Captnoordwe don't have to
14:27.04Captnoordbecause all that info would be in the dll
14:27.18cr2_yeah, we only need to sort out the UMULL and MLA math
14:27.23Captnoordyup
14:27.31*** join/#htc-linux luc_ (~luc@89-115-128-35.cl.ipv4ilink.net)
14:27.42CaptnoordI think I got a important factor
14:28.03CaptnoordLDR     R8, =0xA8081440
14:28.04CaptnoordLDR     R9, =0xA8081444
14:28.04CaptnoordLDR     R10, =0x10624DD3 ; resistance?
14:28.04CaptnoordLDR     R4, [R8]        ; r4 = dwADC_A
14:28.04CaptnoordLDR     LR, [R9]        ; lr = dwADC_B
14:28.04CaptnoordMLA     R1, R4, R7, LR  ; r1 = r4 * r7 + lr
14:28.04CaptnoordUMULL   R2, R3, R1, R10 ; R2R3 = r1 * r10
14:28.05CaptnoordLDR     R1, [R9]        ; r1 = dwADC_B
14:28.05CaptnoordMOV     R7, R3,LSR#6    ; r7 = R3 >> 6
14:28.06CaptnoordMLAS    R3, R4, R7, LR  ; r3 = r4 * r7 + lr ( signed )
14:28.12Captnoordbleh
14:28.22phhcr2_: microp table finished.
14:28.23cr2_0x64 is 100% ?
14:28.24Captnoordu = i * r
14:28.41cr2_power.battery_life_percent = 0x64 here
14:28.46cr2_aka 100%
14:28.53Captnoordyup
14:28.54Captnoord:D
14:28.57Captnoordand is that correct?
14:28.58Captnoord:P
14:29.01cr2_yes
14:29.13cr2_need to 'pd' while charging
14:29.28Captnoordthe thing that is worrying me is that we don't know which things are changed by the wince driver
14:29.38Captnoordand which things are doing hardware wise
14:30.05cr2_Captnoord: smem is HW (pmic+amss+dex)
14:30.15Captnoordyup
14:30.17cr2_Captnoord: all 0x81000+ is wince calculated
14:30.22Captnoordhmm
14:30.23Captnoordokey
14:30.33Captnoordlets get the asm reversed then
14:31.01cr2_phh: they do not overlap ?
14:31.17phhcr2_: you mean mahimahi and known codes ?
14:31.44phhthey overlap only when it's the same thing
14:31.47phhthey did that really cleanly
14:31.58cr2_cc,23,02,x naviledbrightness_auto ; wr
14:31.59cr2_leo100:
14:32.01cr2_cc,23,1,0 ; init_frontlight ; wr
14:32.16phhwhat is front light ?
14:32.30cr2_back light ? :p
14:32.41phh-_-'
14:32.51Captnoordmovmi
14:32.51Captnoord:S
14:34.12cr2_phh: Write a register to gsensor (bma150)
14:34.23cr2_phh: write into gsensor register ?
14:34.37phhhum yes
14:34.43phhI let you do the fixes :p
14:34.44Captnoordmovmi == MI - Negative
14:34.53cr2_phh: later
14:34.54Captnoordmovmi r1, #1
14:34.55Captnoordis
14:34.57Captnoordr1 = -1
14:35.19CaptnoordMOVMI   R7, #0
14:35.21cr2_Captnoord: they use weird instructions
14:35.22Captnoordstrange compiler
14:35.28cr2_yeah
14:35.45CaptnoordI think its related to the fact they use the signed shit
14:35.55Captnoordby already defining it as negative
14:36.04Captnoordyou might get a bit of speed increase
14:36.05cr2_#define probably
14:36.06Captnoorddono
14:36.10Captnoordyea
14:36.14Captnoordjust guessing
14:36.25Captnoordor
14:36.26Captnoordits
14:36.30Captnoord0xFFFFFFFF
14:37.03cr2_phh: 0x80+ on rhod/topa ?
14:37.04phhchamonix: anything new ?
14:37.12phhcr2_: just a guess
14:37.26cr2_phh: not in my list
14:37.29Captnoordnope
14:37.31phhok
14:37.33Captnoordits a condition
14:37.33Captnoordlolz
14:37.56Captnoordif r7 is negative r7 = 0
14:38.05cr2_phh: leo has cc,a3,8,x -> setRotationThreshold
14:38.12Captnoordif ( r7 < 0 ) r7 = 0;
14:38.38phhCaptnoord: movmi r7 = (if (r7<0) r7=0) ?
14:40.57chamonixphh: yea, I finished my work for today and started looking at initrd.gz.2
14:41.33chamonixbasic service is finished as well, I just need to start adding all the notifications the service will receive
14:43.37*** part/#htc-linux dcordes (~dcordes__@unaffiliated/dcordes)
14:45.15Captnoordphh yup
14:45.29phhCaptnoord: I thaught ARM was a risc -_-'
14:45.33Captnoordnope
14:45.49Captnoordrisc would be easy
14:45.55Captnoord1 instruction for all
14:45.57Captnoordnah
14:46.08CaptnoordI mean everything has a single instruction....
14:46.08Captnoordbut
14:46.12Captnoordarm stuff
14:46.39Captnoordalmost all instructions can be used with condition
14:46.52Captnoordthats what makes it faster then x86
14:46.58Captnoordbut harder to decompile
14:49.26*** join/#htc-linux leviathan (~quassel@c-82-192-226-27.customer.ggaweb.ch)
14:49.48Captnoordalso nice how they have instructions to set the status flag
14:49.53Captnoordonly when its needed
14:50.06Captnoordthat way you rip it out of the chip's internal workings
14:50.10Captnoordresulting in faster code
14:50.24Captnoordbecause it doesn't have to be checked every instruction execution
14:54.07Captnoordhmmm fuck
14:54.20Captnoordphh I was wrong
14:54.21Captnoordbleh
14:54.27Captnoordits even more eviler
14:54.36phhuh ?
14:54.39phhnot possible :p
14:54.43CaptnoordMOVMI   R7, #0
14:54.46Captnoordis conditional
14:54.47Captnoordbut
14:54.55Captnoordonly related to the condition flag
14:55.02CaptnoordMLAS    R3, R4, R7, LR
14:55.11Captnoordmlas updated the conditional flag
14:55.15Captnoordlolz
14:55.20Captnoordso its not
14:55.23Captnoordif r7
14:55.24Captnoordits
14:55.33Captnoordif r3 < 0 r7 = 0;
14:55.58Captnoordbleh
14:56.04Captnoordcrap this is so confusing
15:04.16Captnoordcr2_: BatteryVoltage, =0xA8081498
15:04.22CaptnoordIsDoForceDischargeRoutine_bMainBatteryReplaced, =0xA8081438
15:04.47Captnoordlolz
15:04.49Captnoordwrong
15:04.50Captnoorddamn
15:05.15CaptnoorddwBatteryChargedCapacity =0xA8081438
15:05.23CaptnoordI wonder how they know this
15:05.43Captnoordbattery voltage is correct
15:05.43phhjust read the code ! :p
15:05.47Captnoordlol
15:07.27Captnoordmax batt voltage == 3300
15:07.48phhfor a 3.6V batt, it doesn't sound realistic.
15:07.57Captnoordis it?
15:08.23Captnoordyou think the battery is hooked up to the system without special protection
15:08.38Captnoordwhen charging
15:08.45Captnoordits protected by a diode
15:08.51Captnoordwhich cuts the voltage by 0.6v
15:08.55Captnoordor less
15:09.02Captnoordbut that related to the type used
15:09.16phhhum
15:14.12*** join/#htc-linux zachy (~george@85.193.4.18)
15:15.03*** join/#htc-linux marcin_ (~marcin@chello089077185059.chello.pl)
15:17.08*** join/#htc-linux dcordes (~dcordes@unaffiliated/dcordes)
15:23.03*** join/#htc-linux dcordes (~dcordes@unaffiliated/dcordes)
15:23.39chamonixI hate changing APIs
15:25.33phhlol
15:28.41chamonixwhy spending time to write an API if it's changed at every release without backward compat?
15:28.55phhyou think they spend a lot of time on it ? :p
15:29.01ToAsTcfhphh: where did u get that utility (vgrabber)
15:29.05phhToAsTcfh: google
15:29.15phhgoogle v4l2 tool or something like that
15:29.18chamonixI believe they make it on purpose to annoy me :)
15:29.37phhToAsTcfh: calling through a bluetooth headset works right ?
15:29.46chamonixy do u read the doc, here, u have to sources :P
15:29.49ToAsTcfhyeah
15:29.58ToAsTcfhwhy
15:30.06phhI can't see anything about it in the kernel source ...
15:30.09phhwhile it needs gpio muxing
15:30.20ToAsTcfhoh
15:30.38ToAsTcfhbut yeah it works like that
15:30.39chamonixok, my bad, they forgot to change SMS :-D
15:30.59chamonixit's still as it used to be, but call-in is gone :-/
15:31.14ToAsTcfhwhy would msm_camera be messed up out the box in .27
15:33.39ToAsTcfhphh: didnt ubackport .29 msm_camera?
15:34.00ToAsTcfhor did u just fix .27s
15:35.08ToAsTcfhor u never had an issue to begin with
15:45.04*** join/#htc-linux MethoS- (~clemens@134.102.106.250)
15:45.18*** join/#htc-linux mickeyl (~mickey@openmoko/coreteam/mickey)
15:45.29phhToAsTcfh: I backported .29
15:46.26phhchamonix: still nothing for me ? :p
15:47.02*** part/#htc-linux zachy (~george@85.193.4.18)
15:48.13ToAsTcfhphh: u got a patch?
15:49.11chamonixphh: I'm debugging in order to gather info about incoming call/SMS, if there would be a doc I would be faster :P
15:50.38chamonix... and for whatever reason my emu now tells me "no service" :-/
15:52.41ToAsTcfhphh: and did vgrabber work for u?
15:55.38phhToAsTcfh: no
15:55.51phhI haven't tried it at all.
15:56.15phhchamonix: my method is better
15:56.16phhread the source
15:58.06*** join/#htc-linux GregLem (~greg@lal69-5-88-171-98-250.fbx.proxad.net)
16:00.04chamonixwell that's what I'm doing
16:00.12phhoh right
16:00.46chamonixI stumbled across an interesting permission for apps: android.permission.BRICK (Required to be able to disable the device (very dangerous!).) lmfao
16:01.07phh-_-'
16:01.09ToAsTcfhlol
16:01.23phhchamonix: you'll try to publish an app with this permission and see how many people installs it  ? :p
16:01.43ToAsTcfhmany will
16:01.51*** join/#htc-linux xfight81 (~quassel@host106-136-dynamic.5-87-r.retail.telecomitalia.it)
16:02.07ToAsTcfhthats sic though
16:03.11chamonixsure
16:03.13chamonixadded
16:03.14chamonix:-D
16:03.37phhchamonix: anyway, I want your app for led effects to be released before the end of the day ! :p
16:03.50phh(you have the choice of the timezone though.)
16:03.55ToAsTcfhwith a brick perm
16:04.41chamonixthat won't happen :-/ my work is keeping me from coding and it's cooking day today..... gratin dauphinois... want some? :P
16:04.56phhpfffff
16:05.00chamonixlol
16:09.25chamonixcool, getting incoming call :)
16:09.29ToAsTcfhphh: vgrabber supports .ppm only?! no jpeg?
16:09.38phhToAsTcfh: yes why ?
16:09.49ToAsTcfhwouldnt that be an issue?
16:10.05ToAsTcfhi guess thats just an out put
16:10.15phhwhy would that be an issue ?
16:10.22phhyou just want to see if v4l works ...
16:11.17ToAsTcfheh idk... also i seen a guy made a vgrabbj bu it only support v4l not v4l2. its based off of vgrabber
16:11.39ToAsTcfhso i was wondering if it vgrabber supports v4l2
16:11.51ToAsTcfhand not just v4l
16:12.16phhah. I haven't checked
16:13.03ToAsTcfheh but ur right. i do wanna just see if it works. maejrep tried it on his sapphire and it crashed it also
16:13.11ToAsTcfhnot the same error though
16:14.05phhhum anyway the error you got is definitlly a bug in qualcomm's driver
16:14.15phhToAsTcfh: have you any doc about btipsd ?
16:14.31ToAsTcfhyeah and i dont have msm_camera which i need
16:14.31ToAsTcfh]
16:14.39ToAsTcfhno
16:14.56ToAsTcfhi dont even own a bt device
16:15.15ToAsTcfhi just know i had to fix it for others in my rom
16:15.29ToAsTcfhit was some lib i needed to swap
16:16.51*** join/#htc-linux c2d (~Mike@port-92-200-128-105.dynamic.qsc.de)
16:17.09ToAsTcfheh so i guess ill try to backport the msm_camera from .29. i was just hoping to find a patch to save me alot of trial and error
16:18.42*** join/#htc-linux dekar (~dekar@port-92-193-105-69.dynamic.qsc.de)
16:21.07*** join/#htc-linux Boydell (~boydell@69.49.58.28)
16:21.11chamonixI'll try to speed up things a little and pass on the yaffs module for now, building my own kernel for now... I want to  see something blinking
16:22.57*** join/#htc-linux Traveler (~traveler@69.49.58.28)
16:23.02*** part/#htc-linux Traveler (~traveler@69.49.58.28)
16:23.28*** join/#htc-linux JoshuaL (~JoshuaL@kbl-tnz2380.zeelandnet.nl)
16:23.47*** join/#htc-linux Boydell (~Boydell@69.49.58.28)
16:25.01*** join/#htc-linux arrrghhh (~arrrghhh@c-71-196-233-184.hsd1.co.comcast.net)
16:25.40*** part/#htc-linux JoshuaL (~JoshuaL@kbl-tnz2380.zeelandnet.nl)
16:32.30phhYEEEEEEEAAAAAHHHHHHAAAAAAAAAA
16:32.38Captnoord?
16:32.50Boydell?!?!
16:32.52phhCaptnoord: call routing to BT headset works
16:33.09Captnoordnice hehehehehehehee
16:33.11Captnoordgj
16:33.19Boydellsweeeeeeeeeet
16:33.26Boydellnot that I use bluetooth
16:33.27phhnow I just have to reverse this stupid propriatary userland.
16:33.45Boydellbut thats one step closer to a complete android :)
16:35.06ToAsTcfhroot@Oldschool:~/heroc_kernel# adb shell ls -l /dev/video0
16:35.06ToAsTcfhlrwxrwxrwx root     root              2010-01-31 11:32 video0 -> /dev/video20
16:35.07ToAsTcfhroot@Oldschool:~/heroc_kernel# adb shell chmod 666 /dev/video0
16:35.07ToAsTcfhUnable to chmod /dev/video0: No such file or directory
16:35.08ToAsTcfhroot@Oldschool:~/heroc_kernel# adb shell vgrabber
16:35.08ToAsTcfh/dev/video0: No such file or directory
16:35.16ToAsTcfhwtf
16:36.09arrrghhhyea i don't really use BT a lot either... i know a lot of people who want it tho :D  awesome phh.  now what about gps? :P
16:36.20phharrrghhh: I have no more idea at all about gps.
16:36.37arrrghhhbummer.  that's what i use a lot in winmo.
16:36.54Boydellreally> I never use it. Kills my batt.
16:37.01arrrghhhthe cell triangulate seems to work in andriod, and that never worked for me in winmo.
16:37.02Boydellwith what program do you use it?
16:37.07arrrghhhgoogle maps usually.
16:37.22AstainHellbringmorning
16:37.26Boydellah. But it downloads maps on the go, using up my data plan
16:37.32Boydelli dont like that so much
16:37.38arrrghhhi keep trying to find something for off-roading or at least hiking, haven't been able to find anything that's worth a crap.
16:37.45arrrghhhyea, i have unlimited data so no big deal.
16:38.05BoydellI had tomtom on there
16:38.23Boydellbut my SD is only 1 GB, and tomtom took the entire thing lol
16:38.42arrrghhhyea, i treid tomtom.  HA, yea i have an 8gb card... nothing on it but android.
16:39.59arrrghhhseems like a waste, oh well.
16:40.53Boydellbah. I would love an 8GB. They are cheap enough now.But I'm even cheaper
16:42.25arrrghhhlol.  yea, they really are getting ridiculously cheap.
16:42.53arrrghhhi bought this 8gb one with a usb converter and a couple of card changer converters for $20... and that was like a year ago.
16:44.49ToAsTcfhphh: bah now i have msm_camera and no video20
16:44.55phhToAsTcfh: huhu
16:44.55ToAsTcfhwtf
16:45.13ToAsTcfhi need a gun
16:45.23ToAsTcfhor a large hammer
16:46.05ToAsTcfhhey i did see an option it the config for msm_camera_debug
16:47.19*** join/#htc-linux dcordes (~dcordes@unaffiliated/dcordes)
16:48.18ToAsTcfhheh i can smash my hero with my old axim x50
16:48.36AstainHellbringlol
16:48.59AstainHellbringsmashes your x50 with my x51v dock with serial and vga out
16:49.45ToAsTcfhgood i hate both of my devices
16:50.05AstainHellbringToAsTcfh send me your hero
16:50.48ToAsTcfh1 yr before renewal
16:51.27ToAsTcfhi hope sprint gets some bettwer devices by then
16:51.56AstainHellbringahh you have sprint huh
16:52.05ToAsTcfhi got the dust issue and the paint is coming off my power button
16:52.20ToAsTcfhi got dust under my screen
16:52.23ToAsTcfhbad
16:52.29AstainHellbringany wimo device you'd be interested in trading that hero for?
16:52.49*** join/#htc-linux phh_ (~quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
16:52.49*** join/#htc-linux BabelO_ (~fcr@2a01:e35:2ee1:c1c0:21e:8cff:fe2d:7d3f)
16:52.49*** join/#htc-linux BabelO_ (~fcr@unaffiliated/babelo)
16:53.10ToAsTcfhhell no. android forever
16:53.31AstainHellbringlol
16:53.31ToAsTcfhno offence
16:56.24*** part/#htc-linux phh_ (~quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
16:56.43*** join/#htc-linux phh (~quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
17:02.47phhstupid userland ...
17:03.07phhdevs documented commands from 0 to 4 *bit*
17:03.12phhfor the deamon
17:03.20phhthe cli doesn't go past 4... dec.
17:03.33phhso If I want to use bit3 which is FM => A2DP
17:03.36phhI have to rewrite the tool.
17:11.14*** join/#htc-linux GregLem (~greg@lal69-5-88-171-98-250.fbx.proxad.net)
17:12.09*** part/#htc-linux jumoit (~samuel@121.77.87.145)
17:23.37Boydellphh: those patches you put in that finally work, have made the touchscreen MUCH more responsive..
17:23.48phhwhich patch ?
17:24.01phhyou mean with tssc_manager ,
17:24.01phh?
17:24.03Boydellthe ones over the last day or so
17:24.10Boydellyeah I think so
17:24.34BoydellMind you, I'm also using the new drivers
17:24.41Boydellbut its way better than before
17:24.45phhyou're using makkonen's kernel ?
17:24.50Boydellyah
17:25.01ToAsTcfhphh: this is ugly... http://pastebin.com/d3bf4686d
17:25.27phh<4>[  209.220764] msm_ioctl_config: msm_config_vfe cmd 5 returned -19.. Trying a hack to enable vfe and retry
17:27.10phhToAsTcfh: dmesg ?
17:31.14Captnoordhmm
17:33.16*** join/#htc-linux infernix (nix@unaffiliated/infernix)
17:34.27ToAsTcfhphh: yeah but /proc/kmsg
17:34.34phhwhat but ?
17:34.36*** join/#htc-linux infernix (nix@unaffiliated/infernix)
17:35.09ToAsTcfhits dmesg but its the live /proc/kmsg deal
17:35.28ToAsTcfhi like to see it all go down
17:35.32ToAsTcfhlive
17:36.08*** join/#htc-linux junalmeida (~junior@201.19.106.14)
17:37.12chamonixphh: is the display supposed to get off when I write to leds?
17:37.20*** join/#htc-linux Squarc (~Squarc@82-217-32-29.cable.quicknet.nl)
17:37.23phhchamonix: you're supposed to write to "effects" not leds
17:37.29chamonixrofl
17:37.44chamonixwriting to leds is nice too :)
17:37.59chamonixwow
17:38.06chamonixit's like xmas
17:38.09phhlol ?
17:38.24phhchamonix: some effects are one shot only though
17:38.33chamonixrotating center led is cool
17:39.04chamonixwell I have to write all that down because that means for some I need on/off and for other I need a timer to repeat
17:40.29phh[00:23:27] <phh> 0 means no effect, 1 means ringing, 2 means blinking, 3 means breathing, 4 means fading, 5 means rotating, 6 means vertical
17:40.38phh7and iirc only fading is single shot
17:40.50*** join/#htc-linux fab_ (~fab@92.102.26.55)
17:42.43*** join/#htc-linux pleemans (~toi@d54C2A96D.access.telenet.be)
17:46.10*** join/#htc-linux GNUtoo|oeee (~GNUtoo@host46-130-dynamic.244-95-r.retail.telecomitalia.it)
17:46.15*** join/#htc-linux jooprzol (~jooprzol@ip72-213-132-178.ok.ok.cox.net)
17:48.29*** join/#htc-linux GNUtoo (~GNUtoo@host46-130-dynamic.244-95-r.retail.telecomitalia.it)
18:08.20*** join/#htc-linux swc|666 (~infidel20@unaffiliated/swc666/x-4934821)
18:08.27ToAsTcfheh i suck.... im done fr now
18:08.39*** join/#htc-linux jooprzol (~jooprzol@ip72-213-132-178.ok.ok.cox.net)
18:15.44junalmeidahi people, do you know about "bad pc value" error on diamond? i don't figure out what to do. My device is DIAM100. startup have mtype 1805.
18:16.24phhjunalmeida: anything more explicit ?
18:17.17junalmeidai'm booting latest kernel image on my diamond
18:17.51junalmeidabut kernel says bad pc value and does nothing else. system gets stuck.
18:19.03*** join/#htc-linux infernix (nix@unaffiliated/infernix)
18:26.26*** join/#htc-linux zachy (~george@85.193.4.18)
18:28.53phhjunalmeida: nothing more explicit ?
18:29.03phhbad pc might be caused by billions of problems.
18:34.54*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
18:39.21junalmeidaphh: nothing more explicit
18:39.31phhyeah sure.
18:39.35phhand no backtrace while you're there.
18:40.21mickeylphh: (debufs leds) is this just for testing or final?
18:40.27mickeyls/debufs/debugfs/
18:40.43phhmickeyl: final until someone finds a proper linux-ish solution
18:40.53mickeylhmm
18:40.59mickeylso you didn't like my trigger suggestion?
18:41.06phhmickeyl: it's not that i don't like it
18:41.10phhit's just that it's not that
18:41.37phhtrigger is to set an input source to a led without userland
18:41.42phhnot to set different functions for a led
18:41.52mickeylthat's wrong
18:41.56mickeylconsider the timer trigger
18:41.59junalmeidaphh: i have a stack trace, but most os it have just memory codes.
18:42.22phhjunalmeida: you're not reading glemsom's kernel then ?
18:42.24mickeylit's set from userland to set advanced effects on the LED
18:42.31mickeylwhich is exactly that
18:42.33mickeylIMO
18:42.40phhmickeyl: no
18:42.44phhthis is still done in software
18:42.47junalmeidaphh: i 'm using  glemsom's kernel. is it bad?
18:42.50phhwhile what I want is done in hardware
18:42.58phhjunalmeida: glemsom's kernel as symbols
18:43.04mickeylit doesn't matter
18:43.15*** join/#htc-linux stinebd (~bryan@gentoo/developer/battousai)
18:43.21mickeylyou can abstract the additional effects fine behind a special trigger
18:43.24mickeylafter all it's just an abstraction
18:43.25junalmeidaphh: xdandroid's kernel algo gives me bad pc value
18:43.30mickeyland it's the one that comes closest
18:43.37phhjunalmeida: kernel algo ... ?
18:43.59phhmickeyl: hum, that's really not what I understand of the code I read... Do you know any device that has such specific things ?
18:44.04junalmeidaphh: ALSO**
18:44.06mickeylnot offhand
18:44.08junalmeidasorry
18:44.11mickeylbut it would be like
18:44.17junalmeidaphh: i have a backtrace
18:44.20mickeylecho "microplt-sfx" >trigger
18:44.25mickeylthen additional device nodes pop up
18:44.28mickeyland you can set
18:44.32mickeylecho "whatever" >effect
18:44.40junalmeidaphh: __wakeup_common
18:44.51phhjunalmeida: can't you just give ramconsole ?
18:45.11junalmeidaphh: i don't know how.
18:45.19phh~ramconsole-diam
18:45.20apthmm... ramconsole-diam is pwf dm 0x00800000 0x00100000
18:45.27phhjunalmeida: do that in haret
18:45.32phhjunalmeida: or give a snapshot
18:46.35junalmeidaphh: i will try it later. btw, haret ramdonly freezes after 100% of loading. it's a bit difficult to boot linux.
18:46.48junalmeidaphh: i need to try many and many times.
18:47.00phhmickeyl: I can't see how, a led_classdev only has a brightness and a blink callback
18:47.32phhjunalmeida: your movinand seems dead then.
18:47.36phhthere is no reason for it to be random
18:49.18*** join/#htc-linux leobaillard (~leobailla@leobaillard.org)
18:49.24AstainHellbringmorning!
18:49.29mickeylphh: did you read ledtrig-timer.c?
18:49.34mickeylphh: it shows exactly what we could do
18:49.40mickeylmaking a device specific trigger
18:49.47mickeylthat pops up the special nodes when activated
18:49.53mickeylsame as the timer trigger
18:50.03mickeyland then handles what is written into these nodes
18:51.40phhdevice specific trigger ? I can't see any device doing so
18:52.03mickeylbe a pioneer
18:52.11mickeylit's just compiling it in
18:52.19mickeylCONFIG_MICROKPLT_LED_TRIGGER=y
18:53.02mickeylmakes more sense to me than ioctls or debugfs
18:56.28*** join/#htc-linux dcordes (~dccordes@unaffiliated/dcordes)
18:56.31mickeylah well, scratch that
18:56.36mickeylif you want to keep it like that, i'm fine
18:56.44mickeyli can abstract it any way
18:56.45mickeyl*shrug*
18:56.54mickeylit's just that i though you had some mainline ambitions :)
18:57.09phhI don't want to keep that, but I don't want to make a new linux API either
18:57.39phhmainline will have many other problems before microp leds ...
18:58.01mickeyltrue
18:58.05mickeylbut it may be useful to start small
18:58.12mickeyl_if_ you're interested in mainline at all
18:58.27mickeylso basic device support, some leds, backlight etc.
18:58.30mickeylthat makes for a good start
19:00.29tmztmickey|dinner: we were talking to geist in #webos-internals last night, seems he wishes you luck on the Pre port of fso
19:00.47tmztand wonders why nobody has tried it or android yet
19:00.55*** join/#htc-linux c2d1 (~Mike@port-92-200-114-157.dynamic.qsc.de)
19:01.54dcordescr2_, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/61d3a1bd6ee464535303f61331335a7ea907e643
19:02.14dcordesmickey|dinner, any documentation on the pre thing?
19:02.42phhtmzt: still no full sources ?
19:04.09tmztof?
19:04.13tmztkernel?
19:04.16phhyes
19:04.20tmztthey're working on it
19:04.32tmztdcordes: what's that?
19:04.44dcordestmzt, the commit?
19:06.55*** join/#htc-linux Markinus (~Miranda@gtng-4db054b4.pool.mediaWays.net)
19:07.02phhwhen we talk about the wolf.
19:09.12dcordesiirc we once decided to stay as close to the goole kernel as possible
19:09.50phhwhich one ? :D
19:10.05phhseriously, every codeaurora's branch is more different that we are from the original tree ...
19:10.28*** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912)
19:11.07dcordesyes?
19:11.12Captnoordwhich one is to be considerd best?
19:11.17Captnoordor smartest...
19:11.32dcordesthe one that has the highest potential of mainlining
19:11.57phh2.6.32-testing then
19:12.16tmztwhere does it say that?
19:12.27phhtmzt: nowhere, but it's the cleanest tree
19:12.46phhI've even seen somewhere "warning, this breaks android, but needed for X" :p
19:12.51tmzttaht was to junal
19:12.57phhoh.
19:13.08tmztthat's probably chromium tree
19:13.15phhI think so yes
19:13.36tmztso, geist was telling us a little about lk which is his multithreaded bootloader kernel
19:13.52tmztgoogle has a version they use for a reference bootloader
19:14.07tmztwhich is supposed to have 7x0x support and maybe mtd
19:14.11dcordeswhere's that chromium tree?
19:14.54tmztPalm also uses it as a basis for bootie which is a bootloader used on Pre's and Pixi's(msm7x27/30)
19:15.13*** join/#htc-linux Xplod3r (Xplod3r@86.107.117.59)
19:15.49tmztit's very udev like and should allow remote hardware init over a simple ascii command language
19:15.59tmztbut we would currently need uart for that to work
19:16.46phhdcordes: https://www.codeaurora.org/gitweb/quic/le/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-2.6.31.5
19:16.48phhiirc it's this one
19:18.19*** part/#htc-linux zachy (~george@85.193.4.18)
19:18.51tmztwith that message?
19:19.26dcordesthe needed for X message?
19:20.02phhtmzt: I don't remember where it actually was
19:20.10phhI think it was this tree
19:23.14*** join/#htc-linux MrPippy (~pip@adsl-75-37-167-3.dsl.sndg02.sbcglobal.net)
19:24.26Markinusphh: Hi, did you see my sensors patch? The working one? I posted this a few days ago ...
19:24.33phhMarkinus: yes
19:24.50phhoh right I could have pushed it.
19:25.27mickeyltmzt: ya, geist is nice
19:25.43mickeylseems android-lovers are typically satisfied with their devices
19:26.02mickeylpre might not be the formfactor for 'em
19:26.10tmztyeah
19:26.16tmztyou got a g1 now?
19:26.17mickeyldcordes: what kind of docs? modem is completely undocumented
19:26.34tmzthmm, just heard there's progress on omap850 front
19:26.35phhMarkinus: you still have the link ? :D
19:26.37mickeyli had a g1 since long, but refused to root it
19:26.41mickeyli have an adp1 now
19:26.44tmztstill no gsm calls unless booted in a call
19:26.50tmztsame hw
19:26.51mickeylwhich I'm using to adjust fso for it
19:27.00Markinusphh: one Moment . .
19:27.04mickeylit's somewhat sad to see all the fragmentation
19:27.06tmzthow is X working for you?
19:27.07mickeyleven in this small space
19:27.22mickeylno idea about X, will stay console until FSO runs
19:27.37Markinusphh: http://pastebin.com/m148df681
19:28.09tmzttrying to get some information on porting qualcomm's X drivers back to 7k
19:28.40tmztone of those things we can all work on even if we diverge at other points of the stack
19:28.40Markinusphh: maybe could babijoee this in, in his builds . .
19:28.49Markinusbuild
19:29.01phhMarkinus: unluckily, he is afk for some days
19:29.17phhMarkinus: anyway I'm waiting for chamonix's app before doing any new build
19:29.40tmztit's crazy, Pixi's 7x27/30 is closer to snapdragon and the X stuff should just work there
19:29.47tmztbut 7x0x is completely different
19:29.58phhpixi is 7x30 ?
19:30.06tmztyep
19:30.07phhgroumpf then their source code is useless /o\
19:30.11tmztor 27 forget which
19:30.16*** join/#htc-linux balans (~Gebruiker@82-170-215-5.ip.telfort.nl)
19:30.24Markinusphh: ahh okay. I working now on a other kernel driver for the bma150. But I think I need some days ..
19:30.25phhwe already have full clock for 7x30 code
19:30.28tmztnot directly useful, but 7k amss is mostly the same
19:30.32tmztoh
19:30.40tmztyou thought it was snapdragon?
19:30.55*** join/#htc-linux |Jason8| (JayAte@2001:470:1f07:714::15e)
19:32.05mickeyltmzt: i see a lot of #ifdefs coming
19:32.21mickeylthis will make some drivers ugly
19:32.25tmztfor?
19:32.25mickeyle.g. backlight vs. led thing
19:32.45tmztyep, which is why I say go to a clean 2.6.32 and don't look back
19:32.57tmztbut all the momentum is around android right now
19:32.59mickeyl*nod* that will require android changes in userland
19:33.04tmztand these bounties
19:33.07mickeyland i'm not sure whether people are willing to do that
19:33.19tmztthere are open hal's
19:33.25tmztand eclair+ is more sane
19:33.25phhmickeyl: android changes aren't a problem to me
19:33.39mickeylgood
19:33.44mickeyli had a different impression
19:33.47mickeylfrom here
19:33.54dcordestmzt,  go to a clean 2.6.32 <- ack
19:33.59tmztit was harder but we have the infrastrucutre now
19:34.03phhwell, i'm not saying it will be high priority either
19:34.21tmztwe don't need binary compatibilitiy with android system libraries
19:34.24tmztexcept
19:34.33dcordesmickeyl, the problem is that lots of motivation comes from the people. and most of them want android (xda)
19:34.42tmztaudio/acoustic, video/gl
19:34.54tmztand still on pmem for fast graphics
19:34.57*** join/#htc-linux JoshuaL (~JoshuaL@cable-92-43.zeelandnet.nl)
19:35.02*** join/#htc-linux mpurcell (~mpurcell@sholes.info)
19:35.09tmztmpurcell: hey
19:35.18phhtmzt: we can break htc_acoustic quite easily
19:35.19tmzthow's things on your end
19:35.22phhactually, it's already broken.
19:35.24tmztbreak?
19:35.33mpurcellheya
19:35.35phhI mean radically change the api.
19:35.39tmztwe just need to move it to debugfs or somewhere
19:35.55tmztsupport raw table writes
19:36.01phhfor pmem, maybe there is somethuing that can be done
19:36.04mickeyldcordes: yeah, that will make it tough for our work
19:36.14phhbut I fear you want really big changes on it :p
19:36.15mickeylsince there's reluctance to change even small things
19:36.21tmztadp1 is a better starting point though
19:36.36*** join/#htc-linux malgon (~simon@ABordeaux-257-1-153-92.w90-60.abo.wanadoo.fr)
19:36.45tmztphh or gnu or somebody has an upstream tree working on it
19:36.50tmztgnutoo
19:36.57mickeylleviathan and GNUtoo|oeee have, yes
19:37.02tmztyep
19:37.02mickeylbut that tree has its own problems
19:37.05mickeyland doesn't get your fixes
19:37.06tmztlike?
19:37.07mickeylwhich is all sad
19:37.11mickeylmissing vibrator driver
19:37.17tmztdoesn't get what fixes?
19:37.21mickeylbacklight there, but somewhat broken
19:37.27mickeylthe fixes you do in your trees
19:37.28tmztthose are just pull/merges
19:37.40tmztor should be
19:37.55mickeyltrue, but it needs someone actively monitoring and understanding all that
19:37.59mickeylwhich i hope happens
19:38.32mickeylis there any docs for the AKM?
19:38.39mickeylshould check the wiki...
19:42.45mickeyldo you know any of the differences between radio firmware 1.x and 2.x?
19:43.23mickeylmy adp1 is still on 1.22 and i ponder whether to upgrade
19:48.27dcordesbbl
19:50.54cr2_Captnoord: i've added the last value too
19:52.24GNUtoo|oeeehi,I'll be back in a minute
19:53.34cr2_Captnoord: i'll go through the full ref list
19:56.00phhcr2_: I don't remember if I told you, but I successfully did a phone call through bluetooth, there is no special gpio setup to do
19:56.10phhjust snd_set_device(3) and then the correct hci commands
19:56.21cr2_phh: yes, it's about routing only
19:56.34cr2_phh: fm out was 9 and not b ?
19:56.47cr2_phh: do you have a dev= list somewhere ?
19:56.52phhcr2_: one is out to headset the other one is to speaker
19:56.58cr2_then i'll look at wavedev too
19:57.12cr2_b is what ?
19:57.47phhspeaker
19:57.56cr2_9 is headset ?
19:57.57GNUtoo|oeeeok I'm here
19:58.00phhyes
19:58.02cr2_ok
19:58.05GNUtoo|oeeemickeyl, what was the question?
19:58.20cr2_phh: added to the SND tree ?
19:58.56cr2_phh: here is my redirect list:
19:59.08cr2_0,1,2,4,3,5,a,9,b
19:59.18phhcr2_: 3 is bt
19:59.22cr2_4,5,a ?
19:59.23phhoh right
19:59.28phhI didn't see you mentioned it
20:00.12phhfor android, 4 is carkit, 5 is tty_full, 0xa is headset_and_speaker
20:00.14cr2_1,2,3,9,b are known afair
20:00.20mickeylGNUtoo|oeee: oh, i had many. but we'll come to them later. one quick question... i'd love to have a vibrator, could you grab the timed_output from another tree?
20:00.23phhwait.
20:00.23cr2_does a work ?
20:00.29phhsomething's wrong somewhere -_-'
20:00.32cr2_'0xa
20:00.40cr2_4 maybe carkit, ok
20:00.45phhah no sorry, my brain is stupid
20:01.09GNUtoo|oeeemickeyl, ok I'll look when it disapeared
20:01.20GNUtoo|oeeeand in which file it is
20:01.25GNUtoo|oeeemaybe trout board file
20:01.26phhcr2_: 0xa confirmed as speaker+headset
20:01.38cr2_ok
20:01.47cr2_what is tty_full ??
20:01.54phhabsolutely no idea.
20:01.58mickeylGNUtoo|oeee: drivers/misc/timed_output.c
20:02.02phhD/AudioHardwareMSM72XX( 2199): BT MATCH TTY_FULL
20:02.02phhD/AudioHardwareMSM72XX( 2199): BT MATCH TTY_VCO
20:02.02phhD/AudioHardwareMSM72XX( 2199): BT MATCH TTY_HCO
20:02.07phh0x5 to 0x7
20:02.37GNUtoo|oeeeok thanks
20:02.39phh(doesn't help I guess ? :p)
20:02.42*** join/#htc-linux The-Compiler (florian@unaffiliated/the-compiler)
20:03.06cr2_phh: my list is switch() from wavedev.dll
20:03.10phhok
20:03.17cr2_so they are not used
20:04.05phhi'm grepping the whole android sources with tty_full...
20:05.06*** join/#htc-linux GNUtoo (~GNUtoo@host46-130-dynamic.244-95-r.retail.telecomitalia.it)
20:06.22phh../../frameworks/base/telephony/java/com/android/internal/telephony/RILConstants.java:    int CDM_TTY_FULL_MODE = 1;
20:06.28phhthat's the only reference to a "tty_full" thing.
20:07.19cr2_cdma only ?
20:10.25phhseems so
20:10.29phh"teletype"
20:11.31phhdon't tell me they are sending faxes with a cdma phone.
20:11.37cr2_lol
20:11.51*** join/#htc-linux zachy (~george@85.193.4.18)
20:12.09GNUtoomickey|tv, what was the sys node where you echo-ed the time you want it to vibrate?
20:12.43GNUtoobtw I've this file: drivers/staging/android/timed_output.c
20:12.53phhchamonix: still not uh ? :(
20:14.13GNUtooand it seem a timed_gpios
20:14.45GNUtoohttp://pastebin.com/d18ddcfdd in the board file
20:15.30cr2_phh: utod+muld+dtou ?
20:15.42phhcr2_: I'm no arm interpreter.
20:15.57cr2_msvc++ i think
20:16.11GNUtoomickey|tv, I'll add them in my defconfig,recompile and try
20:16.18cr2_mul 2 integers in double ;
20:16.19cr2_wee
20:16.29GNUtooANDROID_TIMED_GPIO and deps
20:16.38cr2_maejrep was an expert on these
20:17.01cr2_phh: prototypes needed
20:17.24GNUtoobtw is there a howto to get GPS working?
20:17.56cr2_GNUtoo: you need to adjust our rfkill driver with data from phh
20:18.03GNUtoook
20:18.24GNUtooI'll try that after the timed gpio compilation then
20:18.41phhcr2_: we also need a proper way to give the userland the infos
20:19.03cr2_phh: /dev/smd27 ?
20:19.16GNUtooindeed that's what we have on dream
20:19.41phhcr2_: uh ? that's where data goes to ?
20:19.46cr2_yes
20:19.48cr2_nmea
20:19.53phhI thaught it was on the pdsm_get_position callback
20:20.10cr2_only on weird phones
20:20.22phhdamn, maybe GPS was working then /o\
20:20.28cr2_or if you want more raw data than nmea
20:20.43cr2_hehe
20:20.48cr2_doubt it
20:21.38phhcr2_: do we get pdsm_get_position callbacks from wince by default ?
20:21.56cr2_wince still sends pdsm_get_position rpcs
20:22.31cr2_i didn't have 100% full trace
20:22.35phhuh ?
20:22.37phhthat seems strange
20:22.47phhit asks for 9e9 fixes no ?
20:22.54cr2_arm9 sends some big callback datas
20:23.02cr2_not sure
20:23.08cr2_was only my guess
20:23.21phhok
20:24.35chamonixwtf... echo 3 > /dbgfs/micropklt_dbg/effects returns "3 > /dbgfs/micropklt_dbg/effects"
20:24.47cr2_phh: a lot depends if the battery id =1 or not. i think we have =2 here
20:25.13phhchamonix: you need to do this in a shell
20:25.18phhnot with a stupid execve
20:25.20chamonixsh -c
20:25.23ToAsTcfhphh: ok man i cant get with my skills anything better then either video20 or msm_camera. not both. i know i suck.
20:25.29phhchamonix: ah.
20:25.46chamonixstill not better, I've got to look at the env
20:26.00chamonixthat's all I've left not working for the service
20:26.02ToAsTcfhmy last attempt i managed to get niether
20:26.10cr2_phh: is +fc00c vbus also on topa/rhod ?
20:26.27phhcr2_: I have to recheck, but I think it doesn't even work on my diam
20:26.31phhit does charging, not vbus
20:26.42cr2_should be vbus
20:27.02cr2_check on a fully charged battery
20:27.10cr2_this is the only possible test
20:27.31*** join/#htc-linux dcordes (~dccordes@unaffiliated/dcordes)
20:28.39phhcr2_: oh fair enough, it's a bug on my side.
20:29.10cr2_charging is gpio
20:30.55GNUtoomickey|tv, ok it works
20:31.03GNUtooI hope he reads logs
20:31.16GNUtooit was just that I echo-ed a time that was too small
20:31.27phhlike 1ns ? :p
20:31.38GNUtoolike echo 10 > enable
20:32.00phhand I guess it's a udelay ?
20:32.06phhhum even for mdelay it's too short
20:32.15GNUtoook
20:33.49phhcr2_: I'm restarting my gps kernel, I don't know if I hope it will works or not.
20:34.19GNUtoocr2_, so do you have more details...which rfkill driver(which source file)
20:34.25GNUtooand where's the data?
20:34.28phhGNUtoo: gps-rfkill
20:34.30phhwiki
20:34.33GNUtoook thanks
20:35.20cr2_GNUtoo: but you need pdsm_init(1) and then the data from MSM_RPC wiki page
20:35.30GNUtoook thanks
20:35.37phhyou need to translate every rpc call
20:36.04phhpdsm calls
20:36.07phhdon't remember about atl ones
20:36.12cr2_phh: should be pdsm_* for the 6225 amss
20:36.20phhtrue
20:36.33cr2_GNUtoo: but it still will be a good start
20:36.46phhGNUtoo: the constants are declared in qdsp5/amss_ver.c iirc
20:36.50GNUtoook
20:36.53cr2_to init pdsm properly, and get the right return values from arm9
20:37.06cr2_we are still at this stage though.
20:37.21GNUtoook so maybe I should wait and concentrate on finishing sound?
20:37.21phhcr2_: they'll get an open gps driver before we do.
20:37.27cr2_because we crash arm9 later, when asking for the position
20:37.34cr2_phh: maybe
20:37.34GNUtoobecause leviathan did a ugly hack that I'ld like to remove
20:37.49cr2_phh: such driver works on kaiser already ;)
20:37.53phhGNUtoo: afaik your amss doesn't crash when starting gps
20:38.00GNUtoook
20:38.15phhcr2_: you mean we have the only amss that needs to reboot to get gps ?
20:38.16phhwaaa
20:38.23cr2_GNUtoo: phh traced android libgps.so
20:38.31GNUtooI heard that
20:38.41cr2_phh: not reboot, but we are doing something wrong
20:38.55*** join/#htc-linux jooprzol (~jooprzol@ip70-189-79-143.ok.ok.cox.net)
20:39.00cr2_GNUtoo: and all the data is in MSM_RPC page
20:39.00phhcr2_: you said we do exactly like wince -_-'
20:39.07GNUtoook thanks a lot
20:39.20phhGNUtoo: I'll be happy to help you about that if you need
20:39.41GNUtoook thanks a lot!!!
20:47.50*** part/#htc-linux zachy (~george@85.193.4.18)
20:51.02cr2_phh: hm. they hardcoded the same functions into nk.exe
20:51.13phhcr2_: which one ? gps ? batt ?
20:51.18cr2_batt
20:53.15cr2_hm. because they charge in sleep too
20:53.31cr2_just wakeup to test the charging
20:55.08phhwhat's the ... I no longer survives an ARM9 crash ... before I got only DEX down, but now, everything seems dead
20:56.48cr2_ADC_A and ADC_B are calculated from VREF, 1/2 VREF
20:58.04cr2_haha. 'REST' 'BUTT'
20:58.24cr2_'CQRG'
21:00.14cr2_44c batt_temp_flag
21:09.21cr2_uh. temperature is calculated too
21:10.46cr2_and current as is
21:11.28cr2_umullne :)
21:12.29MrPippycr2_: does nk calculate percentage also?
21:12.43cr2_MrPippy: yes
21:12.54cr2_MrPippy: i don't see any tables.
21:13.05MrPippyi've been going through battery.dll and it calls percentage CBI, i'm not sure if battery.dll gets percentage from nk or calculates it itself though
21:13.05cr2_MrPippy: so it's some linear math i guess.
21:13.21cr2_these are the same routines
21:13.29MrPippyok good
21:13.31phhcr2_: why not parabolic or exponential ? :p
21:14.01cr2_phh: parabolic ?
21:14.08chamonix\o/
21:14.23phhcr2_: y=x^2
21:14.55cr2_MrPippy: i have added wince data locations into wiki. we may trace them along the powermon.
21:15.04chamonixphh: I noticed when an effect is running and you touch the dpad it's voided.... is this "works as designed"?
21:15.10cr2_phh: which physics is behind that ?
21:15.18phhcr2_: maths.
21:15.23phhchamonix: uh ?
21:15.25cr2_phh: logarithmic/exponential i can understand
21:15.26phhI thaught I fixed that /o\
21:15.36MrPippyok i'll compare with my notes, i see battery.dll loading from lots of very low memory locations but i'm not sure whats there
21:15.53chamonixphh: when did u do that fix?
21:16.03phhchamonix: never according to commit list.
21:16.08chamonixlol
21:16.31cr2_MrPippy: http://htc-linux.org/wiki/index.php?title=RaphaelMemoryMap
21:16.35chamonixthen it's "works as designed" :) I was just wondering if the service was supposed to take care of that
21:16.54chamonixphh: version 0.1 is working :)
21:17.03phhchamonix: btw, there is also a auto_backlight debugfs, do you take care of it ?
21:17.04cr2_phh: back to wavedev.dll
21:17.09phh(a check box to enable/disable it)
21:17.16phhcr2_: what about it ?
21:17.20chamonix.... battery, SMS, call
21:17.32phhchamonix: and don't forget to write to sleep_leds
21:17.34cr2_phh: dev=
21:17.46phhcr2_: anything new about these ?
21:17.54cr2_i'll look
21:17.59chamonixphh: huh? what am I supposed to do with sleep_leds and auto_backlight?
21:18.03phhcr2_: I think we have all devs needed
21:18.03*** join/#htc-linux leaigor (~laigor@188.134.16.241)
21:18.40phhchamonix: a checkbox to enable or disable auto_backlight
21:18.57phhchamonix: oh right you can't handle sleep_leds.
21:19.04phhwell you can, but no.
21:19.08cr2_hm. ef438
21:19.34MrPippycr2_: i know some of the fields in that struct i can fill in
21:19.37chamonixlol
21:19.50cr2_MrPippy: missing ?
21:20.21chamonixphh: is that auto_backlight in somehow related to effects or is it a candidate for the app handling generic settings?
21:20.40phhchamonix: app handling generic settings
21:20.58chamonixgood, you will be able to add whatever you like to that anyway
21:21.07MrPippylike 081422 is percent, voltage is 081404
21:21.53cr2_phh: what is 3,1,1 ?
21:22.08phhcr2_: device 3, output unmute, input unmute ?
21:22.12phhs/unmute/mute/
21:22.20phhs/unmute/mute/g
21:22.29cr2_phh: both 1
21:22.39cr2_MrPippy: be careful, you have raph500 ?
21:22.43phhcr2_: it's a snd_set_device call ?
21:22.50phhthe arguments of it
21:22.50cr2_phh: yes
21:23.01phhthen it meants BT device, with muted output and input theorically
21:23.15cr2_phh: don in the audio init
21:23.26MrPippydiam500, i'm looking through nuebatt so it should be valid at least for cdma diam/raph
21:23.29phhmaybe to init the gpio ?
21:23.36phh(sounds stupid :()
21:23.55cr2_MrPippy: there is raph800 column there
21:24.03MrPippyyeah i'll put it there
21:24.10cr2_ok
21:24.51phhchamonix: groumpf I don't know how to fix this sleep_leds problem
21:25.12cr2_phh: audio trigger restart ? it's some audio restart routine
21:25.44chamonixwell for the time being I can enforce the effect with a timer, if it stops it will get reinforced
21:25.58cr2_phh: +0xef438   pcm module
21:26.02phhchamonix: I'm not talking about the touch problem
21:26.06cr2_phh: adsp module ??
21:26.19phhchamonix: this one is already fixed, the problem is about handling leds when going to sleep
21:26.33chamonixoh, what'S wrong with that?
21:26.47phhchamonix: you know the "led debugging" stuff ?
21:26.51chamonixyes
21:26.54phhto debug deep sleep
21:26.56phhbah that's the problem.
21:27.03phhyour effects won't stay when the phone sleeps
21:27.30phhoh I know
21:27.41phhchamonix: I'll add a sleep_effects file
21:27.50phhsame syntax as effects file, same behaviour as sleep_leds
21:30.07cr2_phh: wtf is this carkit ?
21:30.12phhdon't know
21:31.19phhcr2_: something they forgot to release maybe :p
21:33.52phhI haven't ever heard of a carkit for any android device either
21:35.22MrPippysince google maps has free navigation i think there are carkits for droid/milestone and nexus one
21:35.56chamonixphh: what should I write to /dbgfs/htc_battery/charger_state to simulate a charger not being connected? 0?
21:36.11phhchamonix: argh.
21:36.30*** join/#htc-linux luc_ (~luc@89-115-128-35.cl.ipv4ilink.net)
21:36.31phhchamonix: you mean to discharge it, or to say to android there is no AC ?
21:36.42chamonixthe second
21:36.47phhchamonix: fixes pushed btw
21:36.53chamonixit's hard to remote dbug when unplugging :)
21:37.05phhchamonix: echo 0 works, but don't update your kernel :p
21:37.13phhmy previous commit fixes this
21:37.20chamonixoO
21:37.39phhchamonix: android doesn't know "usb presence but no charger"
21:37.44phhfor it, such things doesn't exist.
21:38.06phhand I fixed usb presence detection, so...
21:38.10chamonixok
21:38.24phhbut with an old enough kernel, the echo 0 > charger_state will work
21:38.31chamonixI just need to debug that for getting breathe on as/usb loading to get working
21:38.49*** join/#htc-linux playdo (~chatzilla@p57B3EF31.dip.t-dialin.net)
21:38.56cr2_Markinus: ping
21:39.10Markinuscr2: pong
21:39.37cr2_Markinus: do you set the bits in +fc0d0 for audio ?
21:40.14cr2_+0xfc0d0   ADIE, x2=forceupd,x4=method,x8=Awake
21:40.34chamonixwell, there seem to be something broken.... I don't get any ACTION_BATTERY_CHANGED :-/
21:41.04phhchamonix: look at the upper part of your screen, there is a charging/on battery icon  :p
21:41.45cr2_Markinus: the awake bit needs to be updated, depending on some other setting
21:41.45Markinuscr2_: I set some bits which I found with Haret but I have to look which, one moment I will look . .
21:42.41cr2_after updateadietable
21:42.47*** join/#htc-linux LeTama (~IceChat7@vau06-1-82-228-252-90.fbx.proxad.net)
21:43.11cr2_audiouplink, auxbypass
21:43.15MarkinusI put it in audio_enable in audio out . .
21:43.37Markinusis this the wrong place?
21:44.40cr2_where do you put the audio (ADIE) params into smem ?
21:45.55Markinusaudio_out.c, audio_enable() / disable()
21:46.30cr2_hm. maybe
21:47.07NetRippercr2_, do you remember i'm having issues with the MDP interrupt? with the handle_bad_irq? i've just noticed that the same thing happens with i2c as well... i wonder what's up there
21:47.38NetRipperthe interrupt fires, but disable_irq within the interrupt handler causes problems
21:48.28cr2_NetRipper: strange
21:48.41cr2_NetRipper: it's the vic irq ?
21:49.30NetRipperyes, you mean in contrary to gpio?
21:49.44cr2_yes
21:50.09cr2_is it the same list as on 7201A ?
21:50.32cr2_you are decoding it from wince, so you must know :)
21:51.18NetRipperno i'm using the nexus one list
21:51.29phhNetRipper: btw, for when you're that far, clock-7x30.c should be helpful for it as their registers looks like qsd
21:51.57NetRipperINT_PWB_I2C (irq 34)
21:51.58cr2_phh: 8x50 has its own code
21:52.05cr2_NetRipper: yes. ok
21:52.06phhcr2_: he already has clock code ?
21:52.20cr2_phh: no.
21:52.29NetRipperthe current clock code doesn't fail though :x
21:52.41cr2_NetRipper: pwb ? do you see it in wince too ?
21:52.50NetRippercr2_, haven't looked at it in wince
21:52.59NetRipperbut i've definitely seen MDP
21:53.14cr2_NetRipper: you may create a vic irq table for 8x50, and mark traced irqs
21:53.24cr2_like it's done for raph.
21:53.26cr2_ok
21:53.37chamonixwaaaa, it's a bug: The platform requires android.intent.action.BATTERY_CHANGED intents to be
21:53.40chamonixregistered with broadcast receivers programmatically.  However, the API
21:53.43chamonixcurrently allows android.intent.action.BATTERY_CHANGED to be included in
21:53.45chamonixthe application manifest.
21:53.52cr2_NetRipper: switch on the cam, you'll see plenty of i2c irqs :)
21:54.16NetRippercr2_, ok
21:54.22NetRippercr2_, what kind of vic irq table do you mean?
21:54.32NetRipperlike this, but for leo? http://www.htc-linux.org/wiki/index.php?title=Raphael_IRQ
21:54.34Markinuscr2_: This is what I do
21:54.35Markinushttp://pastebin.com/dccbfda2
21:54.47Markinusfrom smsm log . .
21:54.51Markinussmem
21:55.16cr2_NetRipper: yes
21:55.18Markinuscr2_: and disable set it to 2
21:55.29NetRippercr2_, but the nexus one irq list should be identical.. it's chipset specific, not device-specific
21:56.16NetRipperdo you somehow expect differences?
21:56.26cr2_NetRipper: INT_ADSP_A11  vs NT_ADSP_A9_A11, and INT_UART2DM_RX  vs INT_UART2DM_IRQ
21:56.43cr2_NetRipper: we had a lot of troubles with these 2 irqs
21:56.57NetRipperaha
21:57.05NetRipperthey're just the same though, only differently named?
21:57.06cr2_NetRipper: g1 use vs raph use
21:57.17cr2_no,different irqs are used
21:57.20*** join/#htc-linux IceWewe (~untitled@unaffiliated/icewewe)
21:57.23NetRipperaha
21:57.32NetRipperinteresting
21:57.45cr2_g1 uses INT_ADSP_A9_A11, and we INT_ADSP_A11
21:57.52cr2_the same for bt
21:58.01cr2_fcked android g1 kernel ;)
21:58.15cr2_and their amss patches
21:58.54NetRipperhehe
21:59.18NetRipperlanguage, yough man ;)
21:59.18cr2_Markinus: hm. ok.
21:59.28cr2_lol
21:59.52NetRipperanyway i got a kernel that boots up to initrd now
22:00.07NetRipperwith almost everything disabled except fb console
22:00.09cr2_wow
22:00.31cr2_well, you need gpio alt, dex and vreg drivers now
22:00.33*** join/#htc-linux playdo (~chatzilla@p57B3EF31.dip.t-dialin.net)
22:00.34NetRippergonna push it to git in a bit
22:00.42cr2_NetRipper: and clk
22:00.49NetRipperyes
22:00.58cr2_NetRipper: add all traced vic irqs in the list
22:01.00phhcr2_: and then he is done. that's unfair.
22:01.05NetRipperalso, i removed dma2_config from htc_fb_console
22:01.08cr2_bt and adsp may be very important
22:01.11AstainHellbringNetRipper nice it boots again?
22:01.15cr2_phh: LOL!!!
22:01.30NetRipperphh, dont worry, i know more needs to be done ;) i was there at start of raphael's kernel too ;)
22:01.43phhcr2_: he already has most drivers
22:01.50NetRipperAstainHellbring, yes.. ah right i'll make a  package for you as well astain soon
22:01.54AstainHellbringcool
22:02.01cr2_phh: he was the first to boot on raph100 too
22:02.13phhhaha
22:02.27phhNetRipper: you'll be the first one for which one next ? :p
22:02.31*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
22:02.39cr2_phh: but after that he returned to wince. so you have the honor to do the dirty job :)
22:02.50NetRipperphh, lol dunno, whenever winmo 7 comes out :p
22:03.09cr2_NetRipper: haha. haret will not work there
22:03.19NetRippercr2_, that's just a challenge :)
22:03.27cr2__yes_
22:03.38NetRipperi like challenges
22:04.18cr2_phh: that's why we need a new common dex+vreg+clk driver
22:04.40cr2_NetRipper: do you already have code to configure the gpio alt ?
22:05.02NetRippercr2_, not sure
22:05.16NetRippercr2_, don't know if it's included in nexus tree?
22:05.19GNUtoomickey|tv, still watching tv
22:05.26GNUtoo?
22:05.26cr2_NetRipper: + in http://www.htc-linux.org/wiki/index.php?title=Raphael_IRQ means traced
22:05.38cr2_NetRipper: unlikely
22:06.02cr2_NetRipper: uart2dm missing there.
22:06.13cr2_NetRipper: but you should see uart1dm
22:06.40NetRipperhttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-qsd8k-2.6.29
22:06.43NetRipperthere it is
22:06.53NetRipperjust pushed the gold
22:07.06cr2_need to track it
22:07.21NetRippercr2_, in nexus bluetooth is on uart1dm but don't know about leo
22:07.23cr2_NetRipper: do they do bt ?
22:07.33cr2_NetRipper: on leo too
22:07.34NetRippercheck board-mahimahi.c
22:07.37cr2_which is strange
22:07.45NetRippercr2_, isn't bt done via amss?
22:07.50cr2_no
22:07.54NetRippersweet
22:08.09cr2_it's a serial port
22:08.29cr2_just trace its vic irq
22:08.44NetRipperi should try serial on usb
22:08.45cr2_the clock settings are known, and that it is uart1dm too.
22:08.56cr2_serial on usb is just usb
22:09.20cr2_+acer_a1                        MACH_ACER_A1            ACER_A1                 2652
22:09.25cr2_what's that
22:09.43NetRipperthats someone that added ACER_A1
22:09.45NetRipperleo is way up
22:09.54NetRipperi just updated mach-types to last version
22:09.57cr2_lol
22:09.58cr2_ok
22:10.23NetRipperHTCLEO was already added to mach-types for haret's sake ;)
22:10.34cr2_yes
22:11.48cr2_(219*1024*1024) ?
22:11.58phhcr2_: like mahimahi
22:12.08cr2_i have heard somthing about 576 :)
22:12.19NetRippercr2_, not on one bank probably
22:12.38cr2_+#define MSM_EBI1_BANK0_BASE    0x20000000
22:12.39NetRipperi just kept it to 219 as per nexusone default.. it may even be too much for leo.. havent tested it fully
22:12.43*** join/#htc-linux mastermerlin (~merlin@pD957FD63.dip.t-dialin.net)
22:12.45cr2_+#define MSM_EBI1_BANK1_BASE    0x30000000
22:13.18NetRipperyep as opposed to 0x1* and 0x2* on raphael
22:13.18cr2_i think it's contiguous
22:13.21cr2_256+256
22:13.30cr2_because of 256
22:13.41cr2_but you may have a hole in the middle
22:13.42NetRipper256+256 = 512, what happened to the other 64MB?
22:13.51cr2_smi
22:14.00NetRipperno, that wouldn't be usable in wince either
22:14.02phhcr2_: contiguous would mean they have no possible extension beyond 512 MB
22:14.05phhwhich seems quite unlikely
22:14.17cr2_phh: ?
22:14.50cr2_NetRipper: must be smi. according to your map
22:14.52phhunless the EBI base address can be changed
22:15.03cr2_NetRipper: have i looked at your amss ?
22:15.08NetRippercr2_, haven't really taken special care of the map
22:15.15cr2_phh: it's a different cpu
22:15.25NetRippercr2_, no but you can download the .nbh from the hd2 forum
22:15.29cr2_NetRipper: ok. that may explain dma problems :)
22:15.29NetRipperits the TMO2.02 radio rom
22:15.39cr2_NetRipper: i think i have already
22:16.06NetRipperi wonder why HTC only enabled 448MB memory instead of the possible 576MB
22:16.54cr2_camera/mdp buffers
22:17.07NetRippereverything still works though
22:17.15phhcr2_: VRAM ?
22:17.17NetRipperi have the 576MB mem in wince
22:17.23NetRipperall hardware still functions
22:17.26cr2_to look good
22:17.34NetRipperlol
22:17.36phhNetRipper: no way you have the fuil use of the 576MB
22:17.53NetRipperphh, that needs to be tested
22:17.54cr2_NetRipper: there is memory debug cmd in haret
22:18.05cr2_NetRipper: try to alloc 576MB, lol
22:18.11NetRipperthat'll never work
22:18.18NetRipperwince kernel won't allow it ;)
22:18.33cr2_find the max value
22:19.00NetRipperwhat's the size of a page?
22:19.02NetRipper4k?
22:19.09phhdepends
22:19.21NetRipperHaRET(2)# alloctest 2~
22:19.21NetRipperpg#: <virt>   <phys>
22:19.21NetRipper000: 5f000000 29091000
22:19.21NetRipper001: 5f001000 290a3000
22:19.23cr2_yes
22:20.03cr2_NetRipper: you use smi for fb ?
22:20.13cr2_+#define HTC_FB_PHYS            0x03800000
22:20.30cr2_pretty high
22:21.28NetRipperin fb_console?
22:21.36cr2_NetRipper: are you sure that mdp reg layout is the same as on 7201A
22:21.38cr2_yes
22:21.45NetRipperthat's what haret told me ;)
22:21.50phhcr2_: yes they are
22:21.56phhcr2_: only the commands are different
22:21.59cr2_ok, so it's traceable
22:22.02cr2_ok
22:22.08phh(I read its source code :p)
22:23.13NetRippergoogle = awesome, you can just type 576MB / 4kB in there, and it'll tell you
22:23.31NetRipperharet crashed
22:23.31phhcr2_: so vbus detection works
22:23.33NetRipper:D
22:23.43cr2_NetRipper: haret evaluates expressions too
22:23.55phhtime to sleep now
22:23.58cr2_phh: finally :)
22:24.05NetRipperyou're right
22:24.05NetRipper:(
22:24.22cr2_NetRipper: how much was allocated. and where ?
22:24.23phhcr2_: yes sorry for the mess
22:24.49cr2_phh: how usable is linux on raph ?
22:25.09*** part/#htc-linux c2d1 (~Mike@port-92-200-114-157.dynamic.qsc.de)
22:25.10cr2_phh: what should be fixed ? the panel init ?
22:25.30NetRippercan only alloc 73000 pages
22:25.34phhpanel init isn't really needed
22:25.38NetRipperbut thats with manila loaded
22:25.48cr2_phh: i'll flash it, as long as i have leo/nexus
22:26.00phhcr2_: ah. you want to flash ?
22:26.17phhit takes a lot of time to debug that :/
22:26.34NetRipperpanel init will be needed when you want to put it in standby and take it out i think
22:26.44phhNetRipper: yes but no.
22:26.54phhNetRipper: we already have >16hours battery life without its suspend
22:26.54NetRipperit remains configured when turned off?
22:26.59NetRipperah
22:27.04phhand diamond has panel on/off
22:27.13phhand it doesn't last that long at all :p
22:27.16NetRipperhehe
22:27.26NetRipperi still have a raphael lying around
22:27.28NetRipperbiting dust
22:27.31phhmaybe it's not properly shut down though
22:27.37phhNetRipper: send it to me then ! :p
22:27.38cr2_phh: something for you http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commitdiff;h=d2958f757626c46bee20971d7920cbe7a3a2a548
22:27.40NetRipperlol
22:28.01NetRipperim a businessman, you can buy it. :P
22:28.05cr2_1c4 on raph/diam/topa
22:28.21phhfunny.
22:28.28phhwas 16mA on hero
22:28.30phh2mA on wince
22:28.34NetRipperlol
22:28.41phhand is 8mA on mahimahi
22:28.41*** join/#htc-linux cr2_ (~cr2@ip-109-84-103-180.web.vodafone.de)
22:28.47chamonix<phh> chamonix: anyway, I want your app for led effects to be released before the end of the day ! :p <---- mission acomplished
22:28.55phhyes i've seen
22:29.00chamonix:)
22:29.08NetRipperled effects?
22:29.09chamonixbattery's not working tho
22:29.10phhcr2_: I guess this setting is a per-sensor setting
22:29.44cr2_yes
22:30.00phhNetRipper: on raph/diam, the center pad can make different led effects
22:31.19NetRipperah yes
22:31.22NetRipperok
22:31.43NetRipperi remember it was made to light up on touch whereever you touched it
22:31.43NetRipper:)
22:31.57cr2_phh: uplink: phone,rec,vt,voip ?
22:32.19phhcr2_: sure.
22:32.38chamonixnite guys
22:32.42phhchamonix: sources ?
22:32.52phhok tomorrow
22:32.59cr2_dnlink: phone,pb,dshow,vt,fm,voip
22:33.08cr2_phh: what is pb ?
22:33.24chamonixyea, I have to run checkstyle on the sources before releasing :P
22:33.32phhchamonix: tsss
22:33.36chamonixHeHeHe
22:33.50phhcr2_: no idea
22:36.10*** join/#htc-linux Forsaken|Desk (~Forsaken@dslb-084-058-252-187.pools.arcor-ip.net)
22:43.36cr2_audiopath2gsm. 4,1
22:48.18cr2_audiopath2pda. 4,0
22:59.09*** join/#htc-linux dekar (~dekar@port-92-193-105-69.dynamic.qsc.de)
22:59.57*** join/#htc-linux surge (surge@pool-98-118-154-21.bflony.fios.verizon.net)
23:02.24cr2_phh: dev= is called for downlink path
23:04.09cr2_+sleep 0x12c after the switch
23:06.11cr2_Markinus: do you set bit 0x8 to wakeup ADIE ?
23:08.15*** join/#htc-linux lalaleche (~jooprzol@32.170.45.129)
23:08.52Markinusno, this is what I'm now testing. I think I have to set it one times only? E.g. in the audio_open() ?
23:09.08cr2_and after sleep i think
23:10.04Markinusok, and 0x10? x2=forceupd + x8=Awake ?
23:10.52cr2_x8 is awake, x2 is force update (if needed) and x4 is method
23:13.29*** join/#htc-linux marcin_ (~marcin@chello089077185059.chello.pl)
23:14.25cr2_[D:AUD] UpdateAudioAdieTable(bAudioUplinkReq 0,bAUXBypassReq 0)
23:14.37cr2_[D:AUD] UpdateAudioAdieTable(bAudioUplinkReq 0,bAUXBypassReq 1)
23:15.19*** part/#htc-linux junalmeida (~junior@201.19.106.14)
23:16.22cr2_hm
23:16.25cr2_on topa
23:16.27cr2_[D:AUD] UpdateAudioAdieTable(bAudioUplinkReq 1,bAUXBypassReq 0,bEnableHSSD=0)
23:16.56cr2_or [D:AUD] UpdateAudioAdieTable(bAudioUplinkReq 0,bAUXBypassReq 0,bEnableHSSD=0)
23:17.05tmztwhat's new? what's this mean?
23:17.25Markinusso meny things oare diferent an Topaz's audio . ..  strange
23:18.03cr2_rhod is even more complex
23:18.05cr2_[D:AUD] CAudioPath::SetDualMicParameters, ActiveDownlinkPath(1), m_bVoiceReq(0), bIsSlideOut(1)
23:18.25Markinusohhh
23:19.25cr2_aha
23:19.28cr2_./topa100_dmesg:16:23:51 [D:AUD] UPLink ==> NONE
23:19.30cr2_./topa100_dmesg:16:23:51 [D:AUD] DNLink ==> PB
23:19.44cr2_PB is playback i guess
23:20.01cr2_[23:32] <cr2_> dnlink: phone,pb,dshow,vt,fm,voip
23:20.02cr2_[23:33] <cr2_> phh: what is pb ?
23:20.41*** join/#htc-linux junalmeida (~junior@201.19.106.14)
23:20.52cr2_[23:31] <cr2_> phh: uplink: phone,rec,vt,voip
23:23.23cr2_uplink is NONE
23:23.29*** join/#htc-linux junalmeida (~junior@201.19.106.14)
23:23.31cr2_or phone
23:23.45*** part/#htc-linux junalmeida (~junior@201.19.106.14)
23:24.05cr2_downlink is NONE or PB
23:24.41cr2_UPLink ==> PHONE
23:25.14cr2_DNLink ==> PB FM
23:25.24cr2_DNLink ==> FM
23:27.42cr2_Markinus: for the fm radio:
23:27.46cr2_14:47:20 [D:AUD] +FMAudioEnable(1,0)
23:27.47cr2_14:47:20 [D:AUD] UPLink ==> NONE
23:27.49cr2_14:47:20 [D:AUD] DNLink ==> FM
23:27.55cr2_14:47:20 [D:AUD] UpdateAudioAdieTable(bAudioUplinkReq 0,bAUXBypassReq 1)
23:28.03cr2_14:47:20 [D:AUD] +call UpdateAudioMethod 1
23:28.05cr2_14:47:20 [D:AUD] +call UpdateForceADIEAwake 1
23:28.06cr2_14:47:20 [D:AUD] +call snd_set_device(11) data:9 11043316
23:28.09*** join/#htc-linux luc_ (~luc@89-115-128-35.cl.ipv4ilink.net)
23:28.22cr2_Markinus: so they are called before the rpc
23:30.13Markinusok, thx, I will look to it
23:30.16cr2_for normal sund
23:30.20cr2_14:47:25 [D:AUD] UPLink ==> NONE
23:30.21cr2_14:47:25 [D:AUD] DNLink ==> PB
23:30.28cr2_14:47:25 [D:AUD] +call UpdateAudioMethod 1
23:30.29cr2_14:47:25 [D:AUD] +call UpdateForceADIEAwake 0
23:30.31cr2_14:47:25 [D:AUD] +call snd_set_device(2) data:12 11048453
23:31.02Markinusdevice 2? Hmm
23:31.47cr2_headset
23:31.52cr2_14:47:44 [D:AUD] +call UpdateAudioMethod 1
23:31.53cr2_14:47:44 [D:AUD] +call UpdateForceADIEAwake 0
23:31.55cr2_14:47:44 [D:AUD] +call snd_set_device(1) data:15 11067742
23:32.01cr2_it's the speaker
23:32.11Markinusokay, thx!
23:32.33cr2_and finally
23:32.36cr2_14:47:47 [D:AUD] UPLink ==> NONE
23:32.38cr2_14:47:47 [D:AUD] DNLink ==> NONE
23:32.47cr2_14:47:47 [D:AUD] +call UpdateAudioMethod 0
23:32.49cr2_14:47:47 [D:AUD] +call UpdateForceADIEAwake 0
23:32.50cr2_14:47:47 [D:AUD] +call snd_set_device(1) data:18 11070818
23:33.12cr2_it's the standard state
23:33.44cr2_what is needed to switch uplink/downlink needs to be investgated more closely
23:34.20Markinusyes, I have no Idea how I can do it . ..
23:35.35cr2_phone
23:35.38cr2_13:05:55 [D:AUD] UPLink ==> PHONE
23:35.40cr2_13:05:55 [D:AUD] DNLink ==> PHONE
23:35.47cr2_13:05:55 [D:AUD] +call UpdateAudioMethod 0
23:35.49cr2_13:05:55 [D:AUD] +call UpdateForceADIEAwake 0
23:35.50cr2_13:05:55 [D:AUD] +call snd_set_device(0) data:2 4958786
23:36.26cr2_so phone does not depend on ADIE
23:36.59cr2_hm. ok
23:37.00Markinusmaybe is this the reason why the phone is working ,  ,
23:37.02cr2_13:06:19 [D:AUD] +AudioPath2PDA
23:37.03cr2_13:06:19 [D:AUD] UPLink ==> NONE
23:37.05cr2_13:06:19 [D:AUD] DNLink ==> NONE
23:37.36cr2_and
23:37.39cr2_13:05:55 [D:AUD] +AudioPath2GSM
23:37.40cr2_13:05:55 [D:AUD] AUDIO: HAC mode enable = 0
23:37.42cr2_13:05:55 [D:AUD] UPLink ==> PHONE
23:37.43cr2_13:05:55 [D:AUD] DNLink ==> PHONE
23:38.10cr2_what did i say before ?
23:38.13cr2_[23:43] <cr2_> audiopath2gsm. 4,1
23:38.15cr2_[23:48] <cr2_> audiopath2pda. 4,0
23:38.29cr2_4 ?
23:38.41cr2_hm,some index maybe.
23:39.39cr2_NetRipper: still here ?
23:40.14Markinuscr2_: could be the UPLink and DNLink different RPC connections?
23:40.24cr2_no
23:40.32cr2_it's something else
23:40.47cr2_first they call this UP/DOWNllink functions
23:40.53cr2_then DEX, and then RPC
23:41.00Markinusok
23:41.10cr2_you can see it in the wince dmesg
23:43.57cr2_NetRipper: you missed the irq2 block in haret for 8x50
23:45.07cr2_NetRipper: this looks like a bug 179 #define NR_MSM_IRQS 64
23:45.58cr2_NetRipper: no, they split them 180 #define NR_SIRC_IRQS 23
23:50.54*** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk)
23:57.18Markinuscr2_: I searching for a place to build the switching of the ADIE Parameters in, maybe on the top of the snd_set_device() function, the parameters are always called bevor this . .
23:58.28Markinusand snd_ioctl

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