IRC log for #htc-linux on 20090613

00:25.34*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
00:45.29*** join/#htc-linux peacedog (n=peacedog@pool-71-254-86-41.lyncva.east.verizon.net)
00:46.06*** part/#htc-linux peacedog_ (n=peacedog@pool-71-254-86-41.lyncva.east.verizon.net)
00:55.43*** join/#htc-linux l33tlinuxh4x0r (n=user@adsl-144-166-112.rmo.bellsouth.net)
02:07.42*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
02:12.28woojAnyone know if there's any progress on getting calling to work on the HTC Diamond in Linux/Android?
02:27.59*** join/#htc-linux infidel206 (n=infidel2@unaffiliated/jenkempusher/x-35920)
02:29.01*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
03:08.42*** join/#htc-linux mrmoku|away (n=mrmoku@ppp-93-104-48-129.dynamic.mnet-online.de)
03:20.23*** join/#htc-linux surge (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
03:21.27tmztwooj: still working on it
03:21.52tmztwe have the rpc codes I think in the wiki
03:22.12AstainHellbringhiya
03:22.26tmzthello
03:23.02AstainHellbringhows it going?
03:23.54tmztok
03:24.33tmztmaybe we can trace rpc on g1 with the kernel define
03:28.54woojtmzt, okay, cool.  Thanks for the update :)
03:40.53woojhmm when I boot android, I can't type on the onscreen keyboard, or rather, I can, but I have to click the bottom of the screen where the onscreen keyboard isnt ;)
03:45.41*** part/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
03:53.21tmztit's not calibrated
04:04.52*** join/#htc-linux j0b0 (n=jobo@67.99.198.4)
04:11.11woojtmzt, how can I fix that?
04:14.20*** join/#htc-linux furtardo (n=mks@nat/yahoo/x-55d0fe11b9c726fc)
04:14.25tmztuh, which device is it?
04:14.52woojhtc touch diamond
04:15.10woojI just the calibration thing for the stylus in windows mobile, but somehow I doubt that makes a difference
04:17.04tmztno
04:17.09tmztwhich diam
04:17.40woojummm
04:17.46woojI dont understand
04:23.29woojCDMA Htc Touch Diamond,
04:24.48j0b0wooj, underneath the battery, it should say DIAM500 or DIAM800 (or some other number)
04:24.58woojOh let me check
04:25.55woojtmzt, j0b0, it says DIAM500
04:26.09j0b0ok, that's 'which diamond'
04:27.13woojOkay cool
04:28.32j0b0( i just dropped in 10 lines ago so i dont know what youre trying to fix )
04:30.52tmztuse the raph800 msmts line
04:30.58woojj0b0, well, when i boot android, my onscreen keyboard shows at the top of the screen, but I have to hit the bottom of the screen
04:31.00woojhmm kk
04:32.47j0b0yes. 'etx' reports here (http://forum.xda-developers.com/showpost.php?p=3914773) that raph800 ts calibration works for -500
04:35.38woojSorry if I'm noobish, I just got this thing today, specifically cause it can run linux ;)
04:36.51tmztcool
04:36.55tmztSprint?
04:37.06woojNo, I'm in Canada.  MTS, which is basically Bell.
04:38.25tmztoh
04:39.30woojaha I have android... but the colours are all wonky
04:39.31woojlol
04:39.50tmztyou have an old kernel
04:40.27woojhmm am i going to have to manually build one?
04:41.03tmztthat would be best
04:41.18tmztdon't know if updated ones are available
04:41.21woojGuess I'll go google where to get the toolchain
04:41.27tmztwith diam500 support
04:41.39j0b0the color fix is not yet in ltg git
04:41.39tmztcodesourcery.com works well
04:41.44tmztoh
04:41.58j0b0try the kernel linked to from that same post 'here is yet another kernel'...
04:42.01tmztis it just adding another mach to maejrep's code?
04:42.25tmztthe raphaelcdma part
04:42.47j0b0tmzt, no. it uses different mdp dma flags based on epson vs. toshiba, in stead of gsm vs. cdma
04:42.58woojSo I just replace my current zimage with this?
04:43.08j0b0because the 500 has the mmc id from 100 but the panel from 800
04:43.51j0b0this is how i did it: http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt but im not sure whether its the proper way. it works tho...
04:44.21j0b0wooj yes. replace/rename that kernel, that should do it
04:44.33woojOk
04:45.23woojbooting now
04:45.40woojooh the android is green
04:48.02*** join/#htc-linux droid001 (n=mc@p4FDCD1C7.dip.t-dialin.net)
04:49.42j0b0if there is nothing 'just plain wrong' about that patch we can add it to git, but i can't really judge that. tmzt, care to review it?
04:49.55woojwell I just booted that kernel
04:50.04woojgraphics are fine, but the touchscreen is still off
04:50.14woojif it touch the top of the screen, the bottom is pressed
04:50.20woojand vice versa.
04:50.41j0b0wooj did you add the ts calibration from 800 to the cmdline in your default.txt?
04:50.49woojOh, forgot.  One minute.
04:51.43woojmtype is 1805
04:52.48woojj0b0, is that what it ought to be? it seems to be from this post.
04:53.18j0b0yes. should be tha same  as diam100
04:53.30wooj"I'm using 1805 as the mtype and the touch screen calibration values from a RAPH800 and its pretty close.
04:53.30wooj" - I'm not sure where to find these calibration values.
04:53.50j0b0wooj -> http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
04:53.51woojIs that this line? - msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"
04:54.16woojok...
04:54.17woojmsmts_calib=0x81.0x393.0x358.0x7D
04:54.20woojill change it
05:02.27woojahh perfect!
05:05.29woojwell apps work
05:05.44woojcant find cell service though ;)
05:06.02woojBut I am impressed :D
05:06.10tmztyou should
05:06.25tmztdoes that work on cdma yet, except vogue?
05:06.49tmztyou have to enable SMD7500 which might reboot the diam
05:06.57woojHow do I do that?
05:07.03tmztit would be good to know if it does though
05:07.14woojI went into wireless and searched for networks, but no dice
05:07.15tmztyou do have to compile the kernel for that
05:07.29j0b0i thought cell service works for all devices
05:07.32woojahh, I'll get the stuff to do that tomorrow.
05:07.49woojj0b0, it said it couldnt find anything.
05:07.57tmztj0b0: no, maybe raph800
05:08.03woojmy phone is CDMA, not GSM, if that matters
05:09.12woojaccording to the page here, my mtype ought to be 2040, would that matter? (http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux)
05:10.18j0b0wooj, you can try it, but i think that will give you no access to mmc, so you couldnt mount any image files to boot into
05:10.33tmztI think you where using the raph800 one
05:10.51tmztoh
05:10.52woojtmzt, I was using DIAM100 mtype
05:10.59tmztis that an issue still
05:11.05woojj0b0, oh, well that wouldnt be any help.  lol :)
05:11.08tmztsuprised that worked at all
05:11.38tmztand color is right now with diam100 mtype?
05:11.45woojcorrect
05:11.51tmztodd
05:11.53j0b0with that patch i just posted, yes
05:11.57woojand with the proper calibration settings, that is all good too.
05:12.05woojim trying mtype 2040 to see what happens
05:12.06tmztI though diam100 was 18bit
05:12.39j0b0the 565 vs. 666 does not depend on mtype then
05:12.58woojyeah 2040 doesnt boot
05:12.59tmztit must
05:13.10tmzthow far does it get?
05:13.21woojto trying to load android
05:13.27woojthen it cant find anything in /system
05:13.38tmztj0b0: the DST settings are based on mtype
05:13.48tmztok, j0b0 is right
05:13.58tmztwe need to fix that
05:14.09woojSo, i'll have to recompile to get my cellular radio to work eh?
05:14.11tmztit should be a one-line change
05:14.15j0b0the mmc thing depends on mtype, but 555/565 not when you apply this  http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt
05:14.16tmztyeah
05:14.21woojkk
05:14.40tmztj): that was for testing, right?
05:14.58tmztgot to get use to hw keyboard again
05:15.06woojI have gcc and all set up on my debian install here, so I'll see what I need to cross-compile in the am... dont want to embark on a large project at midnight :)
05:15.29ltxdaEveryone go to http://www.facebook.com/username and get it setup before your name gets taken :)
05:15.29ltxdaYou are welcome!
05:16.27woojo_O
05:17.05woojOn a completely unrelated subject, what is the best app for playing movies under window mobile? :P
05:17.11woojwmp doesn't 'do' xvid.
05:18.27j0b0wooj i dont know
05:20.07j0b0tmzt, so both cell and sd depend on mtype, but 500 needs one from 100 and the other from 800
05:20.19j0b0could we detect it based on soemthng else
05:20.27j0b0to prevent mtype explosion
05:20.44tmztwe shouldn't be detecting sd slot at all
05:21.08tmztwe have mtype per device there is really no choice
05:21.33tmztI have already registered raph500 but haven't patched anything for it yet
05:21.41j0b0then machine_is_something_cdma is really the wrong name
05:22.00j0b0as 800 is also cdma
05:22.04tmztwell, the gsms were given the codename
05:22.14tmztdiam800?
05:22.21tmztor you mean raph
05:22.26j0b0both?
05:22.35tmztyeah
05:23.00j0b0machine_last_name_is_800() ;D
05:23.44tmztno
05:24.03tmztdiam500 and raph800 are msm7501A
05:24.16woojmy Diam500 has no SD slot.
05:24.25tmztraph500 and I think diam800 are msm7500A
05:24.25woojonly the 4gb internal storage
05:24.32tmztwhich is sd
05:24.36woojOh ok
05:26.25j0b0board-htcraphael-mmc.c:448 uses pdata based on whether the machine is cdma. that would fail for 500
05:27.36j0b0so if 500 uses its own mtype, _is_cdma() should return true, as it is cdma, but the sd is as in gsm
05:28.36woojif I can provide any info, let me know
05:28.59tmztit's not -is-cdma
05:29.12tmztit-s machine-is-htcraphael-cdma
05:30.02j0b0yes. and diamond_cdma, but the 500 is cdma but should use the pdata for sd that works for diam100 and raph100
05:30.16tmztno
05:30.29tmztdiam is on 3 I bevieve
05:30.54tmztI think we should enable all the sdcc slots anyway, but the current code works
05:31.14tmztactually cdma and gsm have the same sdcc setup I think
05:31.19tmztdiam
05:31.54j0b0according to the code, raph/diam gsm are both on 2 and raph/diam cdma are both on 3
05:33.28j0b0or am i looking in the wrong place? (board-htcraphael-mmc.c:448)
05:34.06j0b0and diam500 works with 1805
05:37.09tmztoh
05:37.26tmztsorry, maejrep did that I don't really remeber
05:40.18j0b0so 500 should take the 'gsm path' for sd, but cdma for cell, and on current git also cdma for panel,
05:41.34tmztyeah
05:41.42tmztI think that's right
05:41.44j0b0but it seems odd (name wise) to check for radio type to do sd or panel stuff.
05:42.17tmztwe saw it as the model subtype
05:42.42tmztlike I said, the gsms ones were already registered
05:42.52tmztbefore work on cdma began
05:43.09j0b0for sd it would look nicer to have machine_sd_slot_number(), and for panel machine_pixel_format() or something
05:43.48j0b0or use something that does not depend on mtype at all. im not sure whether that possible for sd, but it apparently is for panel
05:45.43tmztwell, we could pass those from bootloader if we want
05:46.08tmztwe might have enough information to detect the tft panel now anyway
05:46.36tmztthe modification to add diam500 is extremely minor
05:47.13tmztwe will probably clean this stuff up for 2.6.29 anyway
05:47.37j0b0also for battery (4-byte vs. 2-byte smem data layout) differs for different models, but im sure we could detect it by just looking at it
05:48.39j0b0that too would be odd to depend on cdma vs. gsm
05:51.19j0b0are we moving to .29 yet?
05:51.52tmztI'm going to ask cr2 about that
05:52.59tmztbut I would I would like to clean up the code first
05:53.25*** join/#htc-linux goxboxlive (n=goxboxli@237.80-202-137.nextgentel.com)
05:54.57tmztrather than taking over the current code
05:55.32tmztbut then I would also like are rpc/rpcrouter implementation to work
05:55.43tmztso we might just move anyway
06:01.16j0b0is it generally a good thing to not depend on mtype is a driver can probe the device and find out which path to take?
06:01.26j0b0or does that complicate things for future devices
06:05.59tmztif that's possible, yes
06:06.11tmztwe already have interest in tp2
06:07.32tmztthat's what pdata is for, so that the device specific information is not in the driver
06:07.55tmztbut htcraph-mmc is not a driver, it's a board file for five different models
06:08.08tmztpart of a board file actually
06:08.40tmztI'm hoping we can have a single htc file or set of files and less code in the boards
06:09.19tmztfor these devices it would make sense to have a type of board file just form amss specifics
06:09.41tmztso we would have:
06:09.53tmztmach-msm (includes qsd also)
06:10.25tmztboard-htcraphael raph500/800/100/110/300 diam500/800/100
06:10.43tmztboard-htctopaz etc.
06:10.57tmzthtc-hw-mmc if needed
06:11.10tmztamss5200 etc.
06:11.42tmztone thing is we pretty much have to follow what google/android does
06:12.12j0b0but we have more/different devices
06:12.45tmztyes, but we really can't maintain a parallel infrastructure/codebase
06:13.08tmztwe do now but it's mostly additions not wholesale changes
06:13.44tmztI had hoped that sapp would lead to more generalization but there's a lot of duplication instead
06:23.15woojfinally, a working media player for xvid
06:23.21wooj*cheer*
06:25.56tmztwhat?
06:26.37woojTCPMP (The Core Pocket Media Player)
06:30.11tmztyeah
06:30.47woojim just waiting for android to get to a functional level, and ill happily use only it.
06:49.37*** join/#htc-linux punkass (i=punkass@unaffiliated/punkass)
06:49.40*** join/#htc-linux lucxxx (n=root@89-115-128-35.cl.ipv4ilink.net)
07:08.03*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
07:08.35*** join/#htc-linux lucxxx (n=root@89-115-128-35.cl.ipv4ilink.net)
07:15.07*** join/#htc-linux Shinto (n=John@f049153229.adsl.alicedsl.de)
07:23.58*** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-192-228.bak.res.rr.com)
07:24.17*** join/#htc-linux dream_kill (n=nospam@87.194.186.187)
07:41.11*** join/#htc-linux omegaCD (n=omegaCyb@219-84-5-134-adsl-tpe.STATIC.so-net.net.tw)
07:47.27*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
08:27.56*** join/#htc-linux tsdogs (n=tsdogs@tsdogs.metalit.net)
08:38.15*** join/#htc-linux dream_kill (n=nospam@87-194-186-187.bethere.co.uk)
08:39.18*** join/#htc-linux dream_kill (n=nospam@89.131.127.37)
08:44.28*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
08:50.26*** join/#htc-linux onen|openBmap (n=onen@mry91-1-89-87-198-158.dsl.club-internet.fr)
08:52.25*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
08:56.27*** join/#htc-linux nebi (n=nebi@217.142.147.19)
09:21.26*** join/#htc-linux punk-ass (i=punkass@unaffiliated/punkass)
09:29.31*** join/#htc-linux IamSOG (n=IamSOG@218.19.124.241)
09:43.10*** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net)
10:04.40*** join/#htc-linux MethoS (n=clemens@host-091-097-243-193.ewe-ip-backbone.de)
10:05.37*** join/#htc-linux sroecker (n=sroecker@BAHa48a.bah.pppool.de)
10:07.13Squarchey everyone
10:07.40tcccphey you
10:33.15*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
10:38.49*** join/#htc-linux dream_kill (n=nospam@89.131.127.37)
10:49.24*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
10:58.53*** join/#htc-linux mblancom (n=mblancom@103.Red-88-17-196.dynamicIP.rima-tde.net)
10:58.59mblancomhi
11:01.04mblancomI don't know if your are following the linux kernel mailing list but recently people form google are talking about integrate their .28 branch in mainline and to me it seems they want to support as many devices as possible. It could be a good idea to try to integrate your diffs with the google repository
11:02.31lamalink
11:03.31mblancomoh, I mean .29 google branch
11:04.06woojGah my battery went from 3 bars to 1 overnight? wtf.
11:04.47Marajin_wooj: it happens
11:05.13woojMarajin_, the only thing I can think of is that I had windows live messenger running overnight.  :S
11:09.52mblancomthe thread started here: http://lkml.indiana.edu/hypermail/linux/kernel/0906.1/01522.html and a lot of discussion follows mainly related with the arm arch an their closed mailing list but i think with good attitude to incorporate contributions outside google and to merge in mainline as fast as possible
11:21.43tmztmblancom: yeah. great
11:24.13tmztWy: you here?
11:27.27woojrawr
11:34.54Squarctmzt: any news on the audio ddrivers?
11:48.20*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
12:22.27*** join/#htc-linux sxe (n=sxe@ip-62-143-98-186.unitymediagroup.de)
12:27.57tmzthttp://bobcopeland.com/android_wifi.html
12:28.06tmztnew driver for mac80211
12:29.44Squarc:)
12:46.27woojtmzt, slacker, you havent magically singlehandedly got everything working yet? its been about 8 hours!
13:06.51partmzt: which chip(s) does that cover?
13:12.26*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
13:13.31*** join/#htc-linux htc-linux (i=5745de6c@gateway/web/ajax/mibbit.com/x-e250278eeb7c670c)
13:24.09parguess its just for the dream
13:42.04*** join/#htc-linux captnoord (i=5147a47b@gateway/web/ajax/mibbit.com/x-66df6c2ac1784cbc)
13:44.34*** join/#htc-linux MLM (n=mlvdmeid@meide.xs4all.nl)
13:50.02*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
13:57.37captnoordhmmm
13:57.46captnoordlatest raphael build is doing wierd
13:57.55captnoordanyone know why?
13:59.34tmztwhat do you mean?
13:59.39tmztwhich raph?
13:59.47captnoordraph 300
14:00.07captnoordwhich is a 100
14:00.08captnoord:P
14:00.22tmztis that the same as raph100?
14:00.36captnoordyup
14:00.43captnoordhmmm
14:00.43captnoordlol
14:00.45captnoordwaiting long
14:00.52captnoordI think the framebuffer is broken
14:00.54captnoordin some way
14:01.05captnoordas I have the double rumble
14:01.07captnoordjust now
14:01.22captnoordhmmmm
14:01.31tmzthow many times did you try?
14:01.37captnoordsecond time
14:01.37tmztdid mmc timeout?
14:01.53tmztwhat build?
14:02.02captnoordpersonal-> last rev
14:02.16tmztfrom where?
14:02.43captnoordhttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.27
14:02.45captnoordthat one
14:03.42captnoordlast line of the console is: [    0.010000] console handover: boot [htc_fb-1]->real [tty0]
14:03.43tmztbuilt from git?
14:03.46captnoordyup
14:04.06captnoordmaybe I have some stuff in the command line I shouldn't have
14:06.01captnoordset cmdline "root=/dev/ram0 init=/init console=tty0 mem=82M msmsdcc_id=2 imgdevname=/dev/mmcblk0p1 imgdevnum=1 imgdir=/tmp msmts_calib=0x6D.0x5D.0x340.0x375 msmvkeyb_toggle=hide"
14:08.18captnoordi'm sure
14:08.23captnoordi'm doing something wrong again
14:09.46captnoordi'll rebuild
14:09.51captnoordmaybe I did something wrong
14:15.09tmzthow many times has it failed?
14:15.27captnoord2
14:15.30captnoordnow rebuilding
14:15.37AstainHellbringmorning
14:15.43captnoordmorning
14:19.56captnoord3e
14:22.33captnoordbut there isn't something wrong about my command line
14:22.34captnoord?
14:22.43captnoordmy last build worked perfect
14:22.46captnoordso I dono
14:22.46captnoord:S
14:24.58captnoordi'll go back in rev's
14:25.02captnoordmaybe its just me
14:26.22NetRippercaptnoord, set mem= to 76M
14:26.32captnoorddank je
14:26.56NetRipperand you don't need console=
14:27.02NetRippernor msmssdcc_id
14:27.27NetRipperunless someone re-added it to the kernel
14:27.28captnoordk
14:27.49NetRipperand use MTYPE 1910
14:28.00captnoordI am
14:28.01captnoord:D
14:28.02captnoordthanks
14:39.08*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
14:40.06*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
14:56.43*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
14:58.23*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
15:05.11*** join/#htc-linux zycho (n=zycho@dslb-088-070-049-150.pools.arcor-ip.net)
15:27.39*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
16:14.33captnoordhttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5e47c478b0b69bc9bc3ba544e4b1ca3268f98fef
16:14.34captnoordlol
16:23.38*** join/#htc-linux surgex0 (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
16:32.27*** join/#htc-linux surge (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
17:06.42*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
18:00.46*** join/#htc-linux dcordes-kais (n=dcordes-@ip-77-24-73-1.web.vodafone.de)
18:01.46dcordes-kaislol no more zImage?!?
18:06.49*** join/#htc-linux einand (n=einand@remote2.student.chalmers.se) [NETSPLIT VICTIM]
18:06.49*** join/#htc-linux elysion_ (i=kiiski3@mustatilhi.cs.tut.fi) [NETSPLIT VICTIM]
18:12.27*** join/#htc-linux cr2 (n=cr2@ip-90-186-253-78.web.vodafone.de)
18:55.45*** join/#htc-linux domi007 (i=domi007@pool-0610.adsl.interware.hu)
18:56.05domi007hi everybody
19:04.44*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
19:06.35domi007is here anybody? :D
19:22.07*** join/#htc-linux tsdogs_ (n=tsdogs@net203-187-146.mclink.it)
19:25.20dcordes-kaiscr2 hello
19:28.17domi007hi
19:32.32dcordes-kaishello domi007
19:33.12domi007actually i came here to ask something about openembedded and the htc universal, but i see
19:33.18domi007that there is almost no activity
19:33.28domi007so i will have to try later :D
19:39.14dcordes-kaisjust ask
19:40.58cr2dcordes-kais: hi
19:42.24cr2dcordes-kais: i've read the complete kernel-ML thread. if Pavel can't compile the g1 kernel, it says something about the code.
19:48.29domi007actually i read that with openembedded
19:48.43domi007it is possible to compile a very new kernel
19:48.48domi007(version 2.6.26)
19:48.58domi007but i tried
19:49.07domi007and i only got 2.6.21-hh20
19:49.36domi007so i read something fake? or what?
19:49.43cr2domi007: not yet. 2.6.26 is too old anyway.
19:50.08domi007actaully for me it would be enough
19:50.16domi007because i want to have android running on it
19:51.18cr2it does not work.
19:51.29cr2expect 2.6.31 soon
19:52.16domi007soon? it would be GREAT!
19:53.09domi007and will it be available through openembedded? or how?
20:19.35cr2domi007: nothing magic about  oe. the kernel will be in the linuxtogo.org got
20:26.14*** join/#htc-linux cr2 (n=cr2@ip-90-186-253-78.web.vodafone.de)
20:26.28cr2dcordes-kais: ping
20:40.13cr2[  266.246997] adsp: opening module AUDPREPROCTASK
20:40.14cr2[  266.247180] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
20:40.16cr2[  266.247241] [RPC] READ on ept d4a4a860
20:40.17cr2[  266.249133] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4a4a860
20:40.19cr2[  266.249896] [RPC] READ on ept d4a4a860 (24 bytes)
20:40.20cr2[  266.249957] adsp error: RPC call was not successful (3)
20:40.22cr2[  266.249987] adsp: REGISTER_APP failed
20:41.34dcordes-kaiscr2 you have raphael dsp working?
20:42.16cr2does not look like that
20:42.21cr2^^^
20:42.52cr2i guess some patches to adsp_5200.c are needed
20:44.41*** join/#htc-linux stefan_schmidt (n=stefan@p5B037781.dip.t-dialin.net)
20:44.41cr2<PROTECTED>
20:44.43cr2<PROTECTED>
20:47.20cr2<PROTECTED>
20:47.30cr2[  704.923358] audio: failed to get audplay0 dsp module
20:47.32cr2[  704.924426] audmgr_rpc_thread() start
20:47.34cr2[  704.925128] [RPC] READ on ept d4a4a6e0
20:47.51cr2i think dzo shifted them by one
20:48.11cr2<PROTECTED>
20:48.12cr2<PROTECTED>
20:48.14cr2<PROTECTED>
20:50.46cr2dcordes-kais: i've also found the deadly DEX 0x14, but its call sequence is a bit strange
20:53.16cr2[  986.191302] [<c0052498>] (msleep+0x0/0x2c) from [<c002def4>] (clk_set_rate+0x180/0x244)
20:53.18cr2[  986.191333] [<c002dd74>] (clk_set_rate+0x0/0x244) from [<c015c4dc>] (msm_hs_set_termios+0x298/0x444)
20:53.19cr2[  986.191394] [<c015c244>] (msm_hs_set_termios+0x0/0x444) from [<c01578d4>] (uart_change_speed+0x88/0x8c)
20:53.21cr2[  986.191485] [<c015784c>] (uart_change_speed+0x0/0x8c) from [<c015a7dc>] (uart_open+0x420/0x4d8)
20:53.22cr2[  986.191516]  r4:d4bc4400
20:53.24cr2[  986.191546] [<c015a3bc>] (uart_open+0x0/0x4d8) from [<c0144d8c>] (tty_open+0x198/0x30c)
21:11.16domi007cr2: thanks, i will get it as soon as it is available ;-)
21:12.24cr2dcordes-kais: what do you think about wl12xx driver ?
21:13.06domi007wow, linuxtogo has a new design? or i missed somthing? :D Now it is beautiful and seems to be usable :D
21:13.53domi007btw do you know anything about the acx driver? on the Universal it is still very buggy :(
21:14.24cr2we can try wl12xx there too
21:15.18domi007cr2: you mean on the uni?
21:15.22cr2yes
21:17.10domi007but the uni's wlan chip is not a wl12xx chipset...or the wl12xx driver is universal for all ti chips?
21:19.35cr2they are very similar i guess
21:20.35domi007it would be great to have a better driver for the uni
21:20.58domi007now it freezes in every 5-10 minutes...
21:23.43domi007actually can i try the wl12xx driver on the 2.6.21-hh20 kernel too?
21:23.52domi007is there any package or kernel module?
21:24.00cr2no
21:25.35domi007okay, then i have to wait the new kernel
21:34.47domi007does anyone work on Android porting for htc-pxa dvices?
21:34.55domi007or i am the only one?
21:35.44cr2it's not an android channel
21:35.58cr2+#define DMOV_USB_CHAN         11
21:36.01cr2hmm.
21:36.25domi007ok
21:36.30cr2[   69.240618] msm_dmov_enqueue_cmd(11), error datamover stalled, status 0
21:36.58cr2+void msm_dmov_enqueue_cmd(unsigned id, struct msm_dmov_cmd *cmd);
21:37.43cr2PRINT_ERROR("msm_dmov_enqueue_cmd(%d), error datamover stalled, status %x\n", id, status);
21:38.36cr2+int msm_dmov_exec_cmd(unsigned id, unsigned int cmdptr)
21:40.50cr2<PROTECTED>
21:48.00*** join/#htc-linux nebi (n=nebi@217.142.147.19)
21:51.20cr2112 #define DMOV_HSUART2_RX_CHAN   11
21:51.29cr2101 #define DMOV_USB_CHAN         11
21:52.02cr2why not
21:52.14domi007cr2: are you currently working on the wl12xx driver, aren't you?
21:52.21cr2no
21:53.13domi007then what are you posting here actually? :)
21:54.19*** join/#htc-linux MLM (n=mlvdmeid@meide.xs4all.nl)
21:57.09cr2<PROTECTED>
22:01.28cr2179                                 D("%s: %u, freq=%lu\n", __func__, id,
22:01.30cr2180                                   msm_clock_freq_parameters[n].freq );
22:01.42cr2<PROTECTED>
22:02.02cr2ok, seems to be a bug introduced by maejrep.
22:02.21cr2the kernel code does not like a sleep() here.
22:03.16cr2~ping maejrep
22:05.07cr2maejrep: are you still doing some hacking these days ?
22:19.15cr2dcordes-kais: still here ?
22:30.31*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
22:33.46cr20x64=100, 0xa=10
22:34.47cr21.92MHz ??
22:36.06cr27372800/19200=384
22:36.55cr2arcane google humbers ;)
22:39.22cr2rebooting
22:43.12cr2okey, now there is another bug
22:43.17cr2[  114.916217] [<c022bca0>] (schedule+0x0/0x43c) from [<c015ce60>] (msm_hs_shutdown+0xf4/0x15c)
22:43.18cr2[  114.916278] [<c015cd6c>] (msm_hs_shutdown+0x0/0x15c) from [<c0158518>] (uart_shutdown+0xe8/0x110)
22:45.19cr2root@htcraphael:~# echo $((0x1000))
22:45.21cr24096
22:46.59cr2huh ?
22:47.01cr2dd: can't open '/dev/mem': No such file or directory
22:49.02tmztit's not enabled
22:50.31cr2fcking g1
22:51.09cr2tmzt: adsp error: RPC call was not successful (3)
22:51.42cr2tmzt: it's pita to check anything without an alsa interface. or /dev/dsp
22:51.46tmztI looked at the patches to enable sdio on wl12xx, they just generalize memory access, adding a mem/pcmcia interface should be simple
22:51.57cr2ok
22:52.24cr2[  272.343615] adsp: opening module AUDPREPROCTASK
22:52.26cr2[  272.343737] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
22:52.27tmztthe question is probably going to be firmware
22:52.27cr2[  272.343798] [RPC] READ on ept d4a335c0
22:52.29cr2[  272.345690] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4a335c0
22:52.30cr2[  272.346453] [RPC] READ on ept d4a335c0 (24 bytes)
22:52.32cr2[  272.346484] adsp error: RPC call was not successful (3)
22:52.33cr2[  272.346514] adsp: REGISTER_APP failed
22:52.35cr2why ?
22:52.48cr2we have 2. g1 and wince
22:53.20cr2[  291.998248] adsp: opening module AUDPLAY0TASK
22:53.21cr2[  291.998461] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
22:53.35cr2AUDPREPROCTASK and AUDPLAY0TASK are 2 and 4 ?
22:53.48tmztit's different for different interfaces I think, maybe I'm thinking of libertas
22:53.51cr2enabled /dev/mem now
22:54.46tmztdo we know if ce amss uses the same address for rpcrouter?
22:55.02tmztfffffffe should be somewhere in the smem dump
22:55.11cr2yes, it is there
22:55.15cr2<PROTECTED>
22:55.17cr2<PROTECTED>
22:55.18cr2<PROTECTED>
22:55.20cr2<PROTECTED>
22:55.22cr2<PROTECTED>
22:55.41cr2hmm
22:55.43tmztalso, I think we have to call register client on audmgr first
22:55.50cr2QDSP_MODULE_AUDPLAY0TASK, is 2
22:56.37cr2then we need a C app, that will send appropriate ioctls
22:56.52tmztso we need a program to dump the sequence of rpc calls from memory?
22:57.02cr2somebody with g1 may have added printk's to the ioctl part
22:57.26tmztwon't strace work for that?
22:57.29cr2but since it's such a problem to enable /dev/mem, then i give up any hope ;)
22:57.42tmztlav.t was looking at playsnd.c
22:57.44cr2strace what ?
22:57.50cr2all this java crap ?
22:57.59tmztit's not java
22:58.10tmztaudioflinger
22:58.23tmztbut yeah, it's not standalone
22:58.25cr2hehe. wtf is that ?
22:58.31tmztthe playsnd is though
22:58.45tmztit's used to play startup sound
22:58.57cr2ive read about alsa for g1 at lkml
22:59.00tmztuntil they switched to playmp3
22:59.06tmztcool
22:59.18cr2maybe it will happen
22:59.20tmztsomebody has patches?
22:59.29cr2not yet
23:00.14cr2[RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
23:00.22cr2what is 0:00000001 ?
23:00.50cr2ADSPRTOSATOM  0x3000000a   adsp_*
23:00.52cr21,4 adsp_rtos_app_to_modem (1,1,2,4)
23:01.16cr2yes, the SND and AUDMGR rpcs were not sent before.
23:02.12cr2and i'd like to know why dzo commented this one out
23:02.15cr2<PROTECTED>
23:03.33tmztsystem/extras/sound/playwav.c
23:04.10cr2link ?
23:04.14cr2<PROTECTED>
23:04.16cr2<PROTECTED>
23:04.17cr2<PROTECTED>
23:04.19cr2<PROTECTED>
23:04.38cr21,1,2,4
23:04.42tmztI'm in repo but it's on git as well
23:04.56cr24 is not QDSP_MODULE_AUDPPTASK anymore ...
23:05.30tmztopen /dev/msm-pcm-out
23:05.45tmztAUDIO-GET-CONFIG
23:05.59tmztchannels = 2
23:06.06tmztsample-rate =
23:06.20tmztAUDIO-SET-CONFIG
23:06.50tmztit gets buf sz from config
23:07.00tmztprefiles it
23:07.06cr2#define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2
23:07.07cr2#define RPC_ADSP_RTOS_MODEM_TO_APP_PROC 2
23:07.12tmztthen AUDIO-START
23:08.26cr2are these ioctls in pcm ?
23:08.30cr2<PROTECTED>
23:08.31cr2<PROTECTED>
23:08.33cr2<PROTECTED>
23:08.34cr2<PROTECTED>
23:08.43cr2#define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2 !
23:08.55cr2looks like a bug here.
23:09.05cr2at least it does not match our data.
23:09.24cr2changed it to 1
23:10.59cr2i'll remove the // of dzo
23:11.14cr2dzo: are you here ?
23:12.31tmzthttp://www.netmite.com/android/mydroid/system/extras/sound/playwav.c
23:14.15cr2ok
23:16.01cr2<PROTECTED>
23:16.23cr2tmzt: can you compile this program ?
23:16.33cr2i think it should be included with initrd
23:16.42tmztlet me try, need to reboot
23:21.53cr2open("/dev/ttyHS1", O_RDWR|O_NOCTTY
23:21.56cr2blocks
23:22.19cr2yeah, the bug here.
23:22.22cr2[  109.620684] [<c022bad8>] (schedule+0x0/0x43c) from [<c015cc9c>] (msm_hs_shutdown+0xf4/0x15c)
23:22.52cr2wow
23:23.31cr2tmzt: looks like the DSP record is working
23:23.58cr2[  193.792193] adsp: opening module AUDPREPROCTASK
23:24.00cr2[  193.792315] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
23:24.01cr2[  193.792376] [RPC] READ on ept d4a331a0
23:24.03cr2[  193.794268] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4a331a0
23:24.04cr2[  193.795031] [RPC] READ on ept d4a331a0 (24 bytes)
23:24.06cr2[  193.795092] adsp: module AUDPREPROCTASK has been registered
23:24.08cr2[  193.795123] adsp: opening module AUDRECTASK
23:24.09cr2[  193.795184] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
23:24.11cr2[  193.795245] [RPC] READ on ept d4a33200
23:24.12cr2[  193.797656] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4a33200
23:24.14cr2[  193.798358] [RPC] READ on ept d4a33200 (24 bytes)
23:24.15cr2[  193.798419] adsp: module AUDRECTASK has been registered
23:24.17cr2[  193.799456] audmgr_rpc_thread() start
23:24.19cr2[  193.800219] [RPC] READ on ept d4a337a0
23:24.21cr2[  195.708911] adsp: closing module AUDRECTASK
23:24.23cr2[  195.709979] [RR] x REMOVE_CLIENT id=1:d4a33200
23:24.25cr2[  195.710772] adsp: closing module AUDPREPROCTASK
23:24.27cr2[  195.711596] [RR] x REMOVE_CLIENT id=1:d4a331a0
23:24.29cr2[  195.712237] adsp: disable interrupt
23:24.32cr2i did od -x /dev/msm_pcm_in
23:24.47cr2don't see the hexdump on the screen though.
23:25.17cr2at least i got the adsp RPC right
23:26.53cr2this one does not barf anymore:
23:26.56cr2cat /linuxrc > /dev/msm_mp3
23:27.15cr2and produces sensible output in dmesg
23:27.32cr2[  407.487963] adsp: opening module AUDPLAY0TASK
23:27.33cr2[  407.488085] [RPC] CALL to 3000000a:0 @ 0:00000001 (56 bytes)
23:27.35cr2[  407.488146] [RPC] READ on ept d4a336e0
23:27.37cr2[  407.490466] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4a336e0
23:27.38cr2[  407.491259] [RPC] READ on ept d4a336e0 (24 bytes)
23:27.40cr2[  407.491320] adsp: module AUDPLAY0TASK has been registered
23:27.41cr2[  407.492419] audmgr_rpc_thread() start
23:27.43cr2[  407.493060] [RPC] READ on ept d4a33800
23:27.44cr2[  411.089953] audio_disable()
23:27.46cr2[  411.090899] adsp: closing module AUDPLAY0TASK
23:27.47cr2[  411.091571] [RR] x REMOVE_CLIENT id=1:d4a336e0
23:27.49cr2[  411.092211] adsp: disable interrupt
23:28.52cr2tmzt: what is the purpose of /dev/msm_pcm_ctl ?
23:30.21tmztdon't know
23:30.37tmztplaywav caused a bug in audmgr-enable
23:30.50tmztbut it got through prefill and start
23:31.49tmztplaywav also has -record
23:32.09tmztit's not enough to read or write the device
23:32.25*** join/#htc-linux onen|openBmap (n=onen@mry91-1-89-87-198-158.dsl.club-internet.fr)
23:32.38tmztoh, ctl is used for set-device
23:32.47tmztand some other ioctls
23:32.56tmztbut never got those to work either
23:33.18cr2?
23:33.32cr2you need to patch the adsp code first
23:33.44tmztpatch how?
23:34.35cr2i need to create a patch
23:34.58cr2just came to my mind, tat the bt powr is disabled ;)
23:35.48cr2diff --git a/arch/arm/mach-msm/qdsp5/adsp.h b/arch/arm/mach-msm/qdsp5/adsp.h
23:35.58cr2-#define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2
23:36.00cr2+#define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 1
23:36.33cr2then you also need the HELLO patch
23:37.14cr2btw, who calls snd_set_device and snd_set_volume ?
23:37.42cr2then there is a bug in
23:37.45cr2+++ b/arch/arm/mach-msm/clock-wince.c
23:37.55cr2-                               msleep(5);
23:37.57cr2+//                             msleep(5);
23:38.31cr2at least the hsuart code makes an oops here
23:39.51tmztI think only audioflinger
23:40.06tmztplaywav didn't even setup the correct device
23:40.56cr2ok, somebody should call audmgr and snd rpcs
23:41.09cr2dzo put them into vogue-hw.c
23:42.13cr2weird. the latest gXX .29 code has
23:42.17cr2127 #define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2
23:42.19cr2128 #define RPC_ADSP_RTOS_MODEM_TO_APP_PROC 2
23:42.28cr2strange.
23:42.52cr2but ok.
23:48.04cr2why do i get such a huge delay of fb handover ?
23:48.35tmztlooks like nothing calls it???
23:51.22cr2hehe. enabled bt power, and got hardlock on hciattach ;)
23:51.35cr2still some progress :)
23:52.47cr2tmzt: check how kaiser calls SND rpc
23:55.13*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
23:55.38tmztnice
23:56.13tmztwe don't have any code in android to enable routing, just the qemu and pc version
23:56.24tmztit's in libhardware
23:56.49*** join/#htc-linux cr2 (n=cr2@ip-90-186-253-78.web.vodafone.de)

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