IRC log for #htc-linux on 20090611

00:46.38*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
01:22.37*** join/#htc-linux l33tlinuxh4x0r (i=user@adsl-144-166-112.rmo.bellsouth.net)
01:54.31*** join/#htc-linux philster (n=philster@tb78-108-59-40.cust.teknikbyran.com)
02:09.38*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbf9417.pool.einsundeins.de)
03:09.27*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-104-39.dynamic.mnet-online.de)
03:53.51*** join/#htc-linux j0b0 (n=jobo@67.99.199.116)
04:07.43*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
04:32.12*** join/#htc-linux droid001 (n=mc@p4FDCF0A8.dip.t-dialin.net)
05:24.52*** join/#htc-linux _chab7_3 (n=kvirc@fibhost-67-206-132.fibernet.bacs-net.hu)
05:30.11*** join/#htc-linux idkfa (n=sergey@217.12.97.115)
06:25.34*** join/#htc-linux neoobs (i=neoobs@pool-173-51-144-3.lsanca.fios.verizon.net)
06:33.51*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
06:34.05SquarcHey all
06:49.05*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
07:01.26*** join/#htc-linux root (i=user@zemyna-server.ku.lt)
07:15.30*** join/#htc-linux goxboxlive (n=goxboxli@237.80-202-137.nextgentel.com)
07:15.32*** join/#htc-linux Shinto (n=John@f049088113.adsl.alicedsl.de)
07:18.04*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
07:37.21*** join/#htc-linux nebi_ (n=nebi@217.142.147.19)
07:57.46*** join/#htc-linux dcordes (n=luke@unaffiliated/dcordes)
08:13.28*** join/#htc-linux solerant-dc (n=kamikaze@adsl-99-147-78-142.dsl.hstntx.sbcglobal.net)
08:16.43*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
08:20.59*** join/#htc-linux htc-linux (i=c0725602@gateway/web/ajax/mibbit.com/x-a36c117be9fdf18e)
08:23.33*** join/#htc-linux MLM (n=mlvdmeid@5ED0BCBD.cable.ziggo.nl)
08:27.30*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
09:04.15*** join/#htc-linux ChanServ (ChanServ@services.)
09:04.15*** mode/#htc-linux [+o ChanServ] by irc.freenode.net
09:10.13*** join/#htc-linux ChanServ (ChanServ@services.)
09:10.13*** mode/#htc-linux [+o ChanServ] by irc.freenode.net
09:35.09*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
09:49.18*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfd160.pool.einsundeins.de)
09:50.19*** join/#htc-linux MethoS (n=clemens@host-091-097-243-090.ewe-ip-backbone.de)
10:00.24*** join/#htc-linux Abracadabra (n=no@62-244-191-249.cust.exponential-e.net)
10:01.57*** join/#htc-linux IamSOG (n=IamSOG@218.19.251.212)
10:24.10*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
10:49.03*** join/#htc-linux cmonex (n=xy6091@g64ae3p1xa.adsl.datanet.hu)
10:50.39*** join/#htc-linux cmonex (n=xy6091@g64ae3p1xa.adsl.datanet.hu)
10:56.44*** join/#htc-linux infidel206 (n=infidel2@unaffiliated/jenkempusher/x-35920)
10:58.41*** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
11:05.55*** join/#htc-linux MethoS (n=clemens@host-091-097-243-090.ewe-ip-backbone.de)
11:06.32*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
11:43.16*** join/#htc-linux sxe (n=sxe@ip-62-143-98-186.unitymediagroup.de)
11:52.47*** join/#htc-linux dcordes_ (n=luke@unaffiliated/dcordes)
12:11.44*** join/#htc-linux cr2 (n=cr2@ip-90-187-159-75.web.vodafone.de)
12:17.32*** join/#htc-linux TheQ (n=TheQ@brln-4db896f8.pool.einsundeins.de)
12:22.53*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
12:57.45*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
13:14.31*** join/#htc-linux fnord_ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
13:15.43*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
13:19.19*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
13:33.26AstainHellbringmorning
13:34.59*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
13:41.17dcordes_morning astain, what's the haps?
13:47.43*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
13:49.07*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
13:54.35*** join/#htc-linux MethoS- (n=clemens@host-091-096-212-246.ewe-ip-backbone.de)
14:15.29*** join/#htc-linux C-S-B (n=csb@193.061.dsl.pth.iprimus.net.au)
14:16.38C-S-BJust wanted to say that reading your posts has made getting an HTC and developing for it a serious consideration for me. I want a phone, running linux that isnt the Dream, seems you guys are on top of it. :)
14:16.46C-S-Bso thank you!
14:20.37*** join/#htc-linux Elleo (n=Elleo@libre.fm/hacker/elleo)
14:49.50*** join/#htc-linux jaSOnGg (n=IamSOG@218.19.243.97)
15:06.36*** join/#htc-linux j0b0 (n=jobo@67.99.199.116)
15:59.27*** join/#htc-linux j0b0 (n=jobo@192.42.249.7)
16:24.06*** join/#htc-linux MethoS (n=clemens@host-091-096-212-246.ewe-ip-backbone.de)
16:27.07*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
16:31.22*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
17:19.47*** join/#htc-linux stefan_schmidt (n=stefan@p5B034996.dip.t-dialin.net)
17:20.44*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
17:25.56*** join/#htc-linux onen|openBmap (n=onen@mry91-1-89-87-198-158.dsl.club-internet.fr)
17:41.52tmztonen|openBmap: did you see Liam_Ne0 in #openmoko-cdevel? he's working on a logger for android
17:42.51onen|openBmaptmzt: no. Very nice of you to mention! I poke him right away.
17:44.31onen|openBmapI may have some time tomorrow, to spend on the x800. Is there sth specific which could be good to be done?
17:45.03*** join/#htc-linux IamSOG (n=IamSOG@218.19.243.97)
17:45.26tmzt01:29 < Liam_Ne0> Hey all, has anyone managed to use
17:45.26tmzt<PROTECTED>
17:45.26tmzt<PROTECTED>
17:45.51tmztthat's when I contacted him and suggested he contact you and that you were working on a back end
17:46.28onen|openBmaptmzt: I did some research today on neighbour cells and android. But only found messages complaining about an api which had been removed...
17:47.29tmztwe also found that it's mostly implemented in java and source is available
17:48.09tmztthere doesn't seem to be a supported low-level AT command api
17:48.20onen|openBmaptmzt: "mostly" ;-) does it mean a "regular" android won't have it?
17:49.55onen|openBmaptmzt: did he say what was his idea? If he was doing this on his own, or for a project?
17:49.55tmztno, I mean parts of the ril (radio interface layer) or in java and have Apache licensed source code in android git, other parts are in a c library and don't have source for the actual implementation used on the g1
17:50.05tmztno
17:50.35onen|openBmaptmzt: that's my fear. Android is for the moment very much as open as my windows mobile phone :-(
17:51.02onen|openBmaptmzt: but I have more hope to see android one day open, than WM :-)
17:51.22onen|openBmaptmzt: ok. I am now very curious about his work!
17:51.29onen|openBmaptmzt: thanks again for pointing!
18:15.28woojI wish I could make calls on Android.
18:15.30woojweeps.
18:15.43tmztwe mean on g1
18:31.32*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
18:44.49*** join/#htc-linux jamt (n=l@67.109.32.130.ptr.us.xo.net)
18:48.03*** join/#htc-linux nebi (n=nebi@217.142.147.19)
18:51.09cr2tmzt: i have looked at the rpc router init code, and don't quite understand who is supposed to init it.
18:51.32tmztok..
18:51.36cr2tmzt: should haret send the END rpc message before killing wince ?
18:51.52tmztwhat would happen then?
18:52.06cr2the code of lavender.t is a ice hack, but the code is obviously not intended it this way.
18:52.10tmztwe aren't really a different operating system, more emulating what ce does
18:52.12cr2don't know.
18:52.17tmztfrom the amss perspective
18:52.22cr2we have 3 problems with rpc now:
18:52.34cr2the rpcrouter hangs in D state
18:52.54cr2it's not clear who should send the HELLO message to init it.
18:53.13cr2if the raph is booted with rpc active (gps on)
18:53.24cr2then it hangs during the boot process
18:53.39tmztone thing we could gain from earlyharet would be the ability to mmutrace wince startup
18:53.40cr2(debuggable only with the serial console)
18:54.04cr2have you tried it ?
18:54.04tmztsince it really uses low-level functionality of the cpu, irqs and such, it doesn't really need ce running does it?
18:54.26tmztno, I can't see how unless we could get it in the xip somehow
18:54.39tmztor make it a driver, probably hard to do without a ceddk
18:54.39cr2btw, deep suspend vs not so deep suspnd.
18:55.01cr2get in the xip ?
18:55.09tmztonly suspend I know is screen off and what ever the power settings do
18:55.10cr2xip is nk.exe
18:55.25tmztyeah, xip is that chain of different files I mean
18:55.31tmztnot the bootloader part of it
18:55.32cr2if you do a long press, it goes into deep sleep
18:55.44tmzthow long?
18:55.45cr2i need to leave for ~20min. bbl
19:23.24Elleocan anyone recommend likely causes of a kernel (and tags) crc checks failure with haret? I've tried setting a few different ramaddrs but to no effect
19:25.09tmztwhat hardware?
19:25.38tmztI've never actually seen that happen, but I guess sometimes when haret fails to boot the kernel that's the cause
19:25.48Elleoan m900 (samsung s3c6410)
19:25.57ElleoI'm attempting to add support for it to haret
19:26.18tmztoh, ok
19:26.30tmztI think there might be a branch for that chip somewhere
19:26.48Elleothere's a patch for it that laforge made on the dx900
19:26.54Elleowhich is what I'm working with
19:27.01tmztdo you know the start of ram? and can you try a very simple kernel without initrd
19:27.11tmztok, link?
19:27.11ElleoI am trying without initrd at the moment
19:27.34Elleohttp://www.gnufiish.org/trac/attachment/wiki/DX900/haret-s3c64xx-dx900.patch
19:28.20Elleoanother odd thing is that with the m900 I'm only able to disable the first 2 dma controllers (wondering if me not being able to disable the other 2 is causing some sort of memory corruption)
19:28.36Elleoattempting to read from any of the channels on the 3rd or 4th controllers results in the system hanging
19:31.00tmzthow did you find that?
19:32.23ElleoI was already following the gnufiish project (which is working on the m800, the preceeding model)
19:32.52stefan_schmidtAh, a gnufiish hacker. :)
19:32.54stefan_schmidthi Elleo
19:33.04ElleoI think it's also been submitted to the haret mailing list at some point
19:33.07Elleohey stefan_schmidt :)
19:33.43*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
19:34.05tmztI mean where are you trying to disable the dma controllers? I thought linux wasn't booting for you
19:34.27*** join/#htc-linux nebi_ (n=nebi@217.142.147.19)
19:38.09Elleotmzt: in the haret machine specific hardware shutdown stage prior to the kernel hand-off
19:38.20Elleos3c64xxShutdownDMA in cpu-s3c64xx.cpp
19:38.21tmztoh, ok
19:55.46*** join/#htc-linux sroecker (n=sroecker@BAH8d4f.bah.pppool.de)
19:58.25cr2tmzt: i'm back
19:58.33tmztok
19:59.05tmztI'm wondering if we could get device.exe or services.exe to load a small version of haret
19:59.14cr2tmzt: so, what is the "right" way to send a HELLO message ?
19:59.28tmztI really wish I knew that
20:00.02cr2we can create our own driver. there was an idea to use LoadDriver() for haret
20:00.26cr2but you should beg Kevin2 for something like that
20:01.07cr2then running linux will be an ioctl :)
20:01.17tmztah
20:02.22cr2i can imagine that hello is sent by some nontransparent mechanism, like proc_comm or from binary .so
20:02.36tmztnot in the kernel?
20:02.56cr2the msm_rpc_ioctl way was not obvious to me.
20:02.56tmztor does the g1 just not use HELLO message?
20:03.02cr2because it's not exported
20:03.19cr2it has HELLO as a cmd option.
20:03.25tmztwe never found that missing function did we?
20:03.34*** join/#htc-linux WigglerAway (n=james@92-235-224-158.cable.ubr12.stav.blueyonder.co.uk)
20:03.39cr2we found it
20:04.00cr2but lavender.t added this call to rpcrouter_probe()
20:04.27cr2which works, but imho not in the way it was intended by androeds
20:04.52cr2sometimes i really hate g1 code.
20:05.22tmztI mean the find server function
20:05.43tmztbut he found that the servers get registered by amss and annouced to arm11?
20:05.50cr2it just looks through the list
20:06.13cr2it's more or less like the smd_channel_alloc()
20:06.34tmztah, ok
20:06.38cr2which does not alloc anything, but just searches through the already setup data structure list.
20:07.10tmztso how do we get those responses and register the servers? is the code already there?
20:07.17cr2right now i have only the channel for PROG=0, VERS=0 in /dev
20:07.41tmztI wonder if we should expose this to userspace somehow so we can test code faster
20:07.44cr2which complains about the router not being initialized
20:07.57tmztparticularly if we can END and HELLO whenever we want
20:08.10cr2and the init is done in the HELLO handler code.
20:08.25tmztlocalhost ~ # ls -lh /dev/00000000\:0
20:08.26tmztcrw-rw---- 1 root root 253, 0 Jun 11 02:30 /dev/00000000:0
20:08.32cr2yes
20:08.35tmztyes, that's all
20:08.46cr2try 'od -x /dev/00000000:0
20:08.58cr2^c, and then dmesg
20:09.57cr2tmzt: about the "deep" sleep. press the pwr button for >4 sec
20:10.19tmzt[49222.238837] rpcrouter_open
20:10.19tmzt[49222.239356] rpcrouter_ioctl: cmd=21505
20:10.19tmzt[49222.239600] [RPC] READ on ept c335e420
20:10.19tmzt[49224.582130] [RR] x REMOVE_CLIENT id=1:c335e420
20:10.19cr2you will get a popup "do you really want to do that"
20:10.20tmzt[49224.582160] rpcrouter_send_control_msg(): Warning, router not initialized
20:10.27cr2exactly
20:10.30tmztoh, I only get the turn off popup
20:10.35cr2Warning, router not initialized
20:10.49cr2yes, "turn off" is deep sleep
20:11.01tmztoh, ok
20:11.11tmzthow does that help then?
20:11.12cr2and not just "power collapse"
20:11.28tmztit just vibrates and "turns on" when I press power
20:11.41cr2it does a full wakeup
20:11.41tmztcan't tell the difference between that and removing battery or pressing reset
20:11.50tmztwith ram intact?
20:12.12cr2if you press for 1 sec, you get the "light" suspend = power collapse
20:12.14cr2yes
20:12.28AstainHellbringhows it going?
20:13.07tmztcan we try the lavendar.t patch? or did you already do that?
20:13.53cr2try it.
20:14.06cr2i just wanted to know how to do it right.
20:14.27cr2AstainHellbring: deep thinking
20:14.47tmztI'll expose a sysfs to do the hello, or you mean put it in rpcrouter?
20:14.49cr2AstainHellbring: i'll probably add gps and bt to hh.org kernel
20:15.21cr2AstainHellbring: i can add the suspend/resume, but it's not very useful without lcd wakeup, which is rather complex thing.
20:16.08cr2tmzt: adding it to the rpcrouter is a hack.
20:16.24tmztsysfs then?
20:16.38tmztI'll look at the code, need to reboot anyway
20:16.48cr2ok
20:20.08cr2234         .unlocked_ioctl = rpcrouter_ioctl,
20:20.17cr2wtf is unlocked_ioctl ?
20:22.14cr2340         rpcrouter_device = device_create(msm_rpcrouter_class, NULL,
20:22.16cr2341                                          msm_rpcrouter_devno, NULL, "%.8x:%d",
20:22.17cr2342                                          0, 0);
20:22.56cr2this is 0:0 device = oncrpc
20:24.49cr2398                 initialized = 1;
20:24.59cr2in 390         case RPCROUTER_CTRL_CMD_HELLO:
20:32.32cr2tmzt: can you add the hello into _probe, and try to boot ?
20:40.50*** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk)
20:40.51*** join/#htc-linux wirelessdreamer (n=dreamer@c-71-239-79-222.hsd1.il.comcast.net)
20:59.08*** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz)
21:06.18*** part/#htc-linux WigglerAway (n=james@92-235-224-158.cable.ubr12.stav.blueyonder.co.uk)
21:13.17tmztcr2: lavender.t's is emulating a HELLO from amss, not sending it
21:19.39tmztand now I'm not so sure
21:20.31*** join/#htc-linux MethoS (n=clemens@host-091-096-212-246.ewe-ip-backbone.de)
21:25.08cr2ok, but it does not matter right now
21:28.03tmztAstainHellbring: do you have dmesg from g1?
21:28.08tmztok
21:28.16tmztwe get HELLO
21:28.23tmztwe send HELLO
21:28.35tmztwe get servers
21:28.38tmztwe send servers
21:28.40tmzt?
21:35.40AstainHellbringhuh?
21:35.51cr2[    1.095371] SMD: ch 2 OPENING -> OPENED
21:35.54AstainHellbringlemme check g1 for dmesg
21:36.06cr2[    1.113021] RPC_TIME_TOD_SET_APPS_BASES:
21:36.07cr2[    1.113051]     tick = 288838
21:36.09cr2[    1.113051]     stamp = 855639494
21:36.21AstainHellbringyes I has dmesg
21:36.47cr2[    1.375035] Creating 6 MTD partitions on "msm_nand":
21:36.49cr2[    1.375127] 0x024c0000-0x02500000 : "misc"
21:36.50cr2[    1.375950] 0x026c0000-0x02bc0000 : "recovery"
21:36.52cr2[    1.376744] 0x02bc0000-0x02e40000 : "boot"
21:36.53cr2[    1.377476] 0x02e40000-0x071c0000 : "system"
21:36.55cr2[    1.378300] 0x071c0000-0x0b540000 : "cache"
21:36.56cr2[    1.379094] 0x0b540000-0x10000000 : "userdata"
21:37.02cr2hehe. 0xc0000 for some data
21:37.33cr2[    1.702105] mmc0: MMC clock 144000 -> 20000000 Hz, PCLK 64000000 Hz
21:37.38cr2pclk 64MHz ?
21:38.15cr2[    1.746073] rs30000048:0da5b528 rs30000048:0da5b528: setting system clock ...
21:38.38cr2[    2.270000] yaffs: dev is 32505860 name is "mtdblock4"
21:39.25cr2[    1.631098] rs30000048:0da5b528 rs30000048:0da5b528: rtc core: registered msm_rtc as rtc0
21:45.57cr2tmzt: i'm comparing the g1 PROG list to ours
21:46.17cr2but having the g1 smem dump would have been really helpful.
21:47.59cr2rs3000001d:51c92bd8
21:49.05cr2rs3000005b:90380d3d
21:49.49cr2rs3000006b:0aabc7a4 OEM_RAPI
21:50.21cr2many sim toolkit rpcs
21:50.52cr2i guess we will have much less backdoors because of the unimplemented rpcs ;)
21:52.00cr2USER     PID   PPID  VSIZE RSS   WCHAN    PC         NAME
21:52.12cr2root     13    2     0     0     c003263c 00000000 D rpcrouter
21:52.41cr2hm, strange. but it seems to be ok that rpcrouter is in D state. load_avg=1
21:53.26cr2<6>[    0.340000] msm_i2c_probe: clk_ctl 35d, 100000 Hz
21:54.50cr2<4>[    3.041865] SMD: ch 0 OPENING -> OPENED
21:54.50tmztI get response timed out now
21:54.57cr2<4>[    3.043208] SMD: ch 38 OPENING -> OPENED
21:55.04cr2<4>[    3.045008] SMD: ch 39 OPENING -> OPENED
21:55.14cr24>[    3.047724] SMD: ch 40 OPENING -> OPENED
21:55.18cr2this is qmi
21:56.32cr2tmzt: the 'production' g1 kernel does not have RPC_init message ;)
21:57.45tmztwhat is D state?
21:59.43cr2Dead wait ;)
22:00.11cr2it's something to ask San
22:00.12tmztit uses a lot of wait queues
22:00.34cr2but g1 has the same "feature" too
22:01.17cr2where do you get the timeout ?
22:01.52tmztcan't see why rpcrouter would be doing something with no packets to process
22:02.36tmztfrom my sysfs file which uses audio endpoint
22:02.54tmztit also flooded dmesg the first time
22:03.19tmztdon't have the message right now
22:03.27cr2do you have new /dev entries ?
22:03.37tmztyes
22:05.49cr2pastebin ?
22:06.03cr2the dmesg will be nice too.
22:07.07tmztnot here
22:07.17tmztlost the beginning of dmesg
22:07.35cr2ok
22:07.41tmzteverything but the retries
22:08.02tmztwill have to get a clean one
22:08.33cr2<PROTECTED>
22:08.53cr2need syslogd for this one
22:08.58tmztah, right but I'm in ce now
22:09.18cr2do we have syslogd in the initrd
22:09.20cr2?
22:09.45tmztI'm using gentoo, don't know
22:09.52cr2ok
22:10.04SquarcHi there
22:10.05cr2enable the syslogd
22:10.12tmztI think it's here though
22:18.19cr2it's interesting that the vbatt_read rpc is available on blac100
22:22.11tmztdoes wince smem have fffffffe?
22:22.19tmztrpc router address
22:27.33*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
22:31.44cr2yes
22:39.30cr2usb 3-6: New USB device found, idVendor=049f, idProduct=505a
22:39.32cr2usb 3-6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
22:39.33cr2usb 3-6: Product: MSM USB
22:39.35cr2usb 3-6: Manufacturer: HTC
22:39.36cr2hmm.
22:40.02cr2Bus 003 Device 009: ID 049f:505a Compaq Computer Corp. Linux-USB "CDC Subset" Device, or Itsy (experimental)
22:40.15cr2but no usb0 ?
22:40.40cr2tmzt: lost usb after enabling rpc hello
22:40.58cr2rebooting
22:44.12cr2usb 3-6: Product: Generic RNDIS
22:44.13cr2usb 3-6: Manufacturer: HTC
22:44.25cr2usb 3-6: USB disconnect, address 10
22:44.26cr2usb 3-6: new high speed USB device using ehci_hcd and address 11
22:44.28cr2usb 3-6: configuration #1 chosen from 1 choice
22:44.29cr2usb 3-6: New USB device found, idVendor=049f, idProduct=505a
22:44.31cr2usb 3-6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
22:44.32cr2usb 3-6: Product: MSM USB
22:44.34cr2usb 3-6: Manufacturer: HTC
22:45.42cr2tmzt: where is | ?
22:45.49cr2on the keyboard
22:47.58cr2don't get <> too
22:48.44cr2ah. found >
22:51.25cr2CAPS enables the FN led
22:51.45cr2and the CAPS led does not work
22:52.24cr2hehe
22:52.33cr2od -x /dev/msm_mp3 makes oops
22:53.07tmztplan to work on a keymap, my phone should be fixed soon
22:53.23tmztand it would be good to have
22:53.39cr2oops is keybaord related, not rpc
22:53.40tmztmaejrep's driver uses raw keycodes
22:53.49tmztas well as the keyevent
22:54.08cr2audio: failed to get audioplay dsp module
22:54.27cr2audmgr rpc_thread() start
22:54.46cr2RPC read on ept XXXX
22:54.51cr2looks good.
22:54.51*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
22:55.04cr2now i only need |
22:55.13cr2to see the begin of oops
22:55.44cr2it seems rpc hello killed vbus or something.
22:57.39tmztvbus?
22:57.56tmztis it your rfkill patch?
22:58.09tmztthat broke usb for me
22:58.09cr2no. usb
22:58.13cr2?
22:58.22tmztalt settings
22:58.25cr2was working before hello
22:58.27tmztgpio-func
22:58.29tmztok
22:59.05cr2hmm. on 800 ?
22:59.27cr2the bt gpios need to be checked on 500 too
22:59.32cr2wiki is empty
22:59.48cr2the values i have entered are for raph100
23:01.17cr2hm. dmesg is cut here too, because of the nand ;)
23:01.32cr2>[    6.778735] rpcrouter_create_server: rs3000000e:d10ca2da
23:01.33cr2[    6.779010] rpcrouter_create_server: rs3000006a:00000000
23:01.35cr2[    6.779254] rpcrouter_create_server: rs30000068:00000000
23:01.36cr2[    6.779498] rpcrouter_create_server: rs30000067:00000000
23:01.38cr2[    6.779742] rpcrouter_create_server: rs30000048:00000000
23:01.47cr2[    6.780200] [RR] x NEW_SERVER id=1:d7860380 prog=3000000b:0
23:01.48cr2[    6.784503] rpcrouter_create_server: rs3000000a:00000000
23:01.50cr2[    6.784869] rpcrouter_create_server: rs30000066:00000000
23:01.51cr2[    6.895587] [RPC] READ on ept d7860380
23:02.51cr2rs3000000e:d10ca2da wtf is that ?
23:03.29Kevin2cr2: Hi
23:03.35cr2hi Kevin2
23:03.58Kevin2I think you were looking for me a few days back - but we haven't been able to synch up.
23:04.25cr2Kevin2: i have some patches for haret (minor)
23:04.46cr2and there was some talk about the s3c64xx and pxa3xx patches
23:05.56Kevin2Okay.  I haven't seen any patches on the mailing list.  What's the thought with ltg?
23:06.16Kevin2Was dcordes going to open a repo, or should I request it?
23:06.51cr2i think it's better when you will do it
23:07.28Kevin2Okay - let me see if I can do that now.
23:08.04cr2ok
23:09.52*** join/#htc-linux infidel206 (n=infidel2@unaffiliated/jenkempusher/x-35920)
23:09.56cr2tmzt: yeah. the oops comes from pressing CAPS
23:12.44cr2tmzt: cat > /dev/msm_pcm_out does something
23:13.51cr2cat /linuxrc > /dev/msm_pcm_out
23:13.53cr2hangs
23:15.47cr2tmzt: the only regression is the broken usb cdc_ether
23:15.55*** join/#htc-linux surge (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
23:16.07Kevin2cr2: Okay - request went in.
23:16.46cr2Kevin2: good
23:17.17cr2Kevin2: will your htc-spi-kbd driver work on 2.6.30 ?
23:18.00cr2Kevin2: after pH5 made the asic3_mmc work with 2.6.30 i'd like to return to the ATI SD driver
23:18.07Kevin2I don't know.  I haven't followed kernel development in the last year.
23:18.15cr2ok
23:18.42Kevin2The high-level principles haven't changed.  I'm sure it will require some tweaking though.
23:19.44cr2pH5 works on the asic3-spi driver and the spi keyboard connected to it.
23:19.51cr2i expect some overlap here.
23:20.47*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
23:20.49cr2tmzt: dumped /dev list to SD
23:21.08tmztdo sound though?
23:21.10cr2tmzt: have 38 rpc servers
23:21.11tmztno
23:21.19cr2no. not yet.
23:21.26cr2but it looks much better now.
23:21.48cr2i guess that we can send rpc messages now. and maybe get the responses
23:21.52tmztthink audiopara will help?
23:21.56AstainHellbringdid you need that dmesg from g1
23:22.11cr2now i only need to fix usb. the kbd is too litlle
23:22.36cr2tmzt: i think it's something else
23:22.50tmztwhat happened to usb?
23:23.01cr2tmzt: the adsp_5200.c needs to be verified, and maybe compared to the vogue changes.
23:23.17cr2i can't connect anymore
23:23.22tmztwell, snd.c need to register client with audmgr
23:23.49tmztand set the correct endpoint
23:23.50cr2tmzt: the vogue vs g1 has some adsp_XXXX.c changes
23:24.06cr2maybe we just talk to different ADSP queues
23:24.51cr2but it's very difficult to debug for me without usb
23:25.18cr2AUDPPTASK
23:25.19cr2AUDPREPROCTASK
23:25.21cr2AUDRECTASK
23:25.22cr2JPEGTASK
23:25.24cr2LPMTASK
23:25.25cr2QCAMTASK
23:25.27cr2VDEC_LP_MODE
23:25.28cr2VFETASK
23:25.30cr2VIDEOTASK
23:25.31cr2XOR
23:25.33cr2i have these in /dev
23:25.49cr2qcam& vfe & video will not work. yet.
23:26.20tmztyeah
23:26.53cr23000001d:00000000
23:27.17cr23000001f:00000000 SECUTIL
23:27.24cr2hehe
23:27.46tmztmtd?
23:27.51cr23000003b:00000000 DIAG
23:28.00tmztoh
23:28.15tmztso it has to be enaled with rpc?
23:28.38cr230000048:00000000
23:28.41cr2time is there.
23:28.47cr2what ?
23:29.13cr2hahaha
23:29.16cr2MISC_MODEM_APIS_NONWINMOB  0x30000053
23:29.35tmztDIAG
23:30.15cr2gpio_tlmm is there.
23:31.01cr2ok, all the servers i need are there.
23:31.09cr2so we can talk to them
23:32.04cr23000000e:d10ca2da
23:32.18cr2this is the only versioned RPC PROG
23:32.38cr2NV  0x3000000e   nv_*
23:32.49cr2never seen it in action though.
23:33.26tmztI think AT+HTCDM is used instead
23:33.35*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
23:33.35tmztbut maybe bootloader
23:33.54cr2htcdm is cdma-only thing
23:34.04tmztok
23:34.26cr2[  188.172167] BUG: sleeping function called from invalid context at kernel/mutex.c:88
23:34.27cr2[  188.172229] in_atomic():1, irqs_disabled():128
23:34.59cr2some tasklet bug
23:35.04cr2[  188.172564] [<c019e01c>] (micropksc_set_led+0x0/0x90) from [<c019421c>] (microp_keypad_led_event+0x34/0x4
23:35.05cr2[  188.172625]  r7:00000003 r6:d4a4e800 r5:00000001 r4:d4a4e800
23:35.07cr2[  188.172686] [<c01941e8>] (microp_keypad_led_event+0x0/0x40) from [<c018fa48>] (input_handle_event+0x47c/0
23:35.08cr2[  188.172747] [<c018f5cc>] (input_handle_event+0x0/0x4c4) from [<c019099c>] (input_inject_event+0x78/0xc0)
23:35.10cr2[  188.172778] [<c0190924>] (input_inject_event+0x0/0xc0) from [<c014e004>] (kbd_bh+0xf0/0x158)
23:35.11cr2[  188.172839] [<c014df14>] (kbd_bh+0x0/0x158) from [<c004d1dc>] (tasklet_action+0x74/0xcc)
23:35.13cr2[  188.172900]  r6:0000000a r5:c030f7e8 r4:00000000
23:35.14cr2for CAPS led
23:35.24cr2which enables FN led actually
23:35.35tmztinput-report-key?
23:36.31cr2something for j0b0
23:36.32stefan_schmidtKevin2: btw, cegcc changed the executable names. wince removed from the name. http://pastebin.com/fa921f48
23:37.08stefan_schmidtcr2: You know where the pxa3xx pacthes for haret are?
23:37.15stefan_schmidtwould like to take a look.
23:37.15cr2stefan_schmidt: no
23:37.20stefan_schmidthi all, btw
23:37.27stefan_schmidtcr2: hmm, ok
23:37.37cr2stefan_schmidt: wince is removed only in the "recent" cegcc CVS
23:37.57stefan_schmidtSeems as if oilver ford has done some, but his server is done the last two weeks
23:38.14stefan_schmidtcr2: Also in the 0.5.5 release it seems.
23:38.21stefan_schmidtThat's what I downloaded.
23:38.21cr2ok
23:38.25tmztremoved?
23:38.34cr2i used some older CVS
23:38.55stefan_schmidtDate: 2009-05-08 04:57
23:38.55stefan_schmidtSummary: CeGCC 0.55 is out
23:40.02cr2tmzt: you may check the adsp_*.c patch by dzo
23:40.25cr2tmzt: i don't really know how to debug/trace it right now.
23:40.47tmztah, ok
23:41.25cr2tmzt: but i guess that it should be possible to write the gps rpc handler now. and other misc handler.s
23:41.52tmztok
23:42.17cr2you may also ask San why are we forced to send HELLO for init.
23:42.23cr2and how g1 does it.
23:43.10tmztI think amss sends it first
23:43.11cr2i'm curious what is broken with the usb ;)
23:43.18tmztafter boot up
23:43.44cr2ok, but how do we force amss to do it for us ? dex ? gpio ?
23:44.17tmztwe don't
23:44.19cr2need to dig in the nk.exe
23:44.33tmztlavender.t's code fakes it
23:44.45tmztthen we respond with HELLO
23:45.33tmztthe function he calls is for processing received packets
23:45.50cr2btw, i think we can try to patch the battery rpc
23:46.06tmztit's only otherwise called by do_read
23:46.29cr2wince does not use it, but the server is there. so we may try to query it for the data.
23:47.06cr2will be a good test for rpc
23:50.20cr2tmzt: the wince dmesg provides the same rpc numbers
23:50.26cr2Line: 188. rpc_router_database: dup server registration. Prog: 3000ffff, Ver: 0.
23:50.28cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000000, Ver: 0.
23:50.29cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100003a, Ver: 0.
23:50.31cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000016, Ver: 0.
23:50.32cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000019, Ver: 0.
23:50.34cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100003c, Ver: 0.
23:50.35cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000002, Ver: 0.
23:50.37cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000014, Ver: 0.
23:50.38cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000013, Ver: 0.
23:50.40cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000003, Ver: 0.
23:50.41cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100005b, Ver: 0.
23:50.43cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100001d, Ver: 0.
23:50.44cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000010, Ver: 0.
23:50.46cr2Line: 188. rpc_router_database: dup server registration. Prog: 31000012, Ver: 0.
23:50.47cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100005f, Ver: 0.
23:50.49cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100006b, Ver: 0.
23:50.50cr2Line: 188. rpc_router_database: dup server registration. Prog: 3100006c, Ver: 0.
23:52.32Kevin2stefan_schmidt: When they release a version (with rpms), I'll convert haret.
23:52.48cr2$$$ +adsp_rtos_app_to_modem cmd 2, module 2
23:53.02cr2$$$ +adsp_rtos_app_to_modem cmd 2, module 4
23:53.42stefan_schmidtKevin2: It is released. "In versions prior to 0.55, these were called arm-wince-mingw32ce and arm-wince-cegcc but we changed this in agreement with other projects, to facilitate feedback of patches."
23:54.03stefan_schmidtKevin2: anyway, was just an heads up
23:56.10Kevin2stefan_schmidt: Ahh - I missed the release last month.  So, yes, haret should change.
23:56.18Kevin2Thanks.
23:56.35stefan_schmidtKevin2: No problem. With the posted patch it built fine for me
23:57.08stefan_schmidtNow I have to dig more into it to see how I could add pxa3xx support
23:57.49stefan_schmidtDocs are public now so it will be mainly dully work to write the stuff
23:58.45*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)

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