IRC log for #htc-linux on 20090715

00:10.40*** join/#htc-linux MethoS (n=clemens@host-091-097-245-103.ewe-ip-backbone.de)
00:42.12*** join/#htc-linux no2chem (n=no2chem@cpe-76-90-65-27.socal.res.rr.com)
01:39.08*** join/#htc-linux g55 (n=g55@rgnb-5d87cfe6.pool.einsundeins.de)
01:56.39*** join/#htc-linux darkstar62 (n=darkstar@97-126-107-190.tukw.qwest.net)
02:19.39*** join/#htc-linux surge (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
02:26.25*** join/#htc-linux MikeKnoop (n=mk@173-30-132-211.client.mchsi.com)
02:28.52MikeKnoopLots of people in here... was expecting a smaller crowd
02:29.41*** join/#htc-linux |Jason8| (i=JayAte@server1.tiltshellz.org)
02:32.58MikeKnoopIs anyone here currently working on the android port?
02:33.44*** join/#htc-linux SOG (n=IamSOG@218.20.219.3)
02:33.51MikeKnoopSpecifically, for the Diamond/Raphael
02:39.44miknixMikeKnoop, Diamond? is that an omap850?
02:43.32*** join/#htc-linux g55 (n=g55@rgnb-5d87ceed.pool.einsundeins.de)
02:45.55MikeKnoopNo, different projcet I gather. (diamond: http://forum.xda-developers.com/showthread.php?t=402002)
02:47.20*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
02:57.03miknixah, its a msm
02:57.23miknixI'm not the best person to help then :)
02:59.43*** join/#htc-linux |Jason8| (i=JayAte@server1.tiltshellz.org)
04:00.24*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
04:26.29*** join/#htc-linux Shinto (n=John@g227199255.adsl.alicedsl.de)
04:30.13*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
04:33.06*** join/#htc-linux Amaranth (n=travis@74-221-34-123.longlines.com)
04:34.58*** join/#htc-linux chavonbravo (n=cb@fl-69-68-26-177.dyn.embarqhsd.net)
04:35.02chavonbravohey
04:35.19chavonbravoanyone working on haret new version for armv7 proc yet?
04:50.08*** join/#htc-linux droid001 (n=mc@p4FDCCFF2.dip.t-dialin.net)
05:29.31*** part/#htc-linux chavonbravo (n=cb@fl-69-68-26-177.dyn.embarqhsd.net)
06:12.24*** join/#htc-linux marex (n=marex@thor.hackndev.com)
06:29.14*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
06:29.17*** join/#htc-linux kiozen (n=oeichler@p54920832.dip0.t-ipconnect.de)
06:55.51*** join/#htc-linux g55 (n=g55@rgnb-5d87cc4b.pool.einsundeins.de)
07:36.20*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
07:50.49*** join/#htc-linux pleemans (n=toi@d51A49C45.access.telenet.be)
08:04.43*** join/#htc-linux dream_kill (n=nospam@89.131.127.37)
08:09.26*** join/#htc-linux mrmoku|away (n=mrmoku@ppp-93-104-40-112.dynamic.mnet-online.de)
08:43.16*** join/#htc-linux g55 (n=g55@rgnb-5d8745b0.pool.einsundeins.de)
08:47.42*** join/#htc-linux stefan_schmidt (n=stefan@p5B03710A.dip.t-dialin.net)
09:09.03*** join/#htc-linux surgex0 (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
09:17.56*** join/#htc-linux silent-hacker (n=janus@unaffiliated/silent-hacker)
09:19.42*** join/#htc-linux dcordes (n=luke@unaffiliated/dcordes)
09:26.59*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
09:35.06*** join/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch)
09:35.34xperiadcordes are you here
09:36.26dcordesxperia, yes
09:36.36xperiagreat :-)
09:36.56xperiai have a question about the i2c chip addresses on the xperia
09:37.40dcordesshoot
09:38.10xperiai have seen in the htc-logs that you and cr2 tryed to trace the adresses. Can you tell me what are the i2c adresses especially for the keyboard
09:38.29xperiai have some strange logs in dmesg
09:39.21xperiaor at least how i can trace becouse the normal way like described dont provide very helpfull informnations
09:40.06*** join/#htc-linux MethoS (n=clemens@host-091-097-245-103.ewe-ip-backbone.de)
09:42.11xperiahere is some output of the dmesg text
09:42.19xperia[   15.724667] microp-klt: probe of 0-0066 failed with error -524
09:42.40xperia[   15.661679] microp-ksc: Registering MicroP-KEY driver
09:42.42xperia[   15.669522] microp-klt: Registering MicroP-LED driver
09:42.43xperia[   15.677335] microp-klt: Initializing MicroP-LED chip driver at addr: 0x66
09:42.45xperia[   15.694730] microp-klt: This hardware is not yet supported: 0000
09:47.10dcordesxperia, don't worry. we found out that the i2c address in the present driver is correct- it's a gpio question only
09:47.55dcordesxperia, glad you asked so you don't do double work. the author will release the code soon. it will be noted here in the logs
09:51.14xperiaok thanks for the info. P.S Do you know the Nick of the Person
09:53.32dcordesyes it is Aiv. Stick around. he will be online later
09:53.53dcordesthe wiki.htc-linux.org was also updated if you want to read something already
09:59.09xperianice. stil  a lot to be done. i will be login later about 18.00 CET. till later bye.
10:01.12*** join/#htc-linux stefan_schmidt_ (n=stefan@p5B036841.dip.t-dialin.net)
10:13.54*** join/#htc-linux mugsie (n=Administ@unaffiliated/mugsie)
10:21.21*** join/#htc-linux mugsie (n=Administ@unaffiliated/mugsie)
10:21.27*** join/#htc-linux ptitjes (n=didier@93.2.7.199)
10:22.56*** part/#htc-linux mugsie (n=Administ@unaffiliated/mugsie)
10:37.41*** join/#htc-linux apt (i=ibot@rikers.org)
10:37.41*** topic/#htc-linux is Welcome to htc-linux | Logs: http://apt.rikers.org/%23htc-linux | Livelogs: http://irclog.netripper.com/?chan=htc-linux | Wiki: http://htc-linux.org/wiki | Original project page: http://wiki.xda-developers.com/index.php?pagename=Xanadux | Please use device codenames. For aliases, see: http://wiki.xda-developers.com | Join #android for android centered discussion.
10:39.43*** join/#htc-linux marex (n=marex@thor.hackndev.com)
11:10.50*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
11:15.23IceBonehttp://www.youtube.com/watch?v=WTFlFFrfEB0
11:29.00*** join/#htc-linux Nirvana (n=noneavai@freecode-project/hacker/LordInquisitor)
12:04.18dcordesbbl
12:11.23*** join/#htc-linux parmaster_ (i=par@dipole.idlepattern.com)
12:11.24*** join/#htc-linux Espenfjo (i=espen@158.38.48.18) [NETSPLIT VICTIM]
12:11.28*** join/#htc-linux kiozen (n=oeichler@84.146.8.50) [NETSPLIT VICTIM]
12:11.29*** join/#htc-linux SOG (n=IamSOG@218.20.219.3) [NETSPLIT VICTIM]
12:11.35*** join/#htc-linux silent-hacker (n=janus@41.207.162.4) [NETSPLIT VICTIM]
12:16.06*** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) [NETSPLIT VICTIM]
12:17.58*** join/#htc-linux silent-h1cker (n=janus@41.207.162.4)
12:41.15*** join/#htc-linux repson (n=isaac@249.Red-80-33-69.staticIP.rima-tde.net)
13:39.48*** join/#htc-linux MethoS (n=clemens@host-091-097-245-103.ewe-ip-backbone.de)
13:56.02*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
14:03.02*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
15:09.13*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c026.pool.einsundeins.de)
15:17.20*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
15:41.08*** join/#htc-linux Echo31_ (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
16:00.34*** join/#htc-linux Torgin (n=fake@c83-248-0-218.bredband.comhem.se)
16:01.05*** join/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch)
16:33.36*** join/#htc-linux q_tpro (n=q_tpro@host-1-146-66-217.spbmts.ru)
16:37.50*** join/#htc-linux Torgin (n=fake@c83-248-0-218.bredband.comhem.se)
16:47.06*** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-161-252.ewe-ip-backbone.de)
16:49.02*** join/#htc-linux q_tpro_ (n=q_tpro@host-1-146-66-217.spbmts.ru)
16:50.20q_tpro_hi
16:50.46q_tpro_dcordes: fyi. there is one potential problem with the bluetooth clock setup
16:52.36q_tpro_dcordes: it is sourced from ACPU_PLL_0 with the prescaler 4, M/N divisor and baud divisor =16
16:53.59q_tpro_dcordes: google has a different setup, because they operate the base clock at 4X speed (different baud divisor settings)
16:55.43q_tpro_the easiest way to match the clock speeds is to remove the prescaler=4, but then we should hope that the M/N divider is capable of operating at 4X clock rate
16:59.35*** join/#htc-linux q_tpro__ (n=q_tpro@host-1-146-66-217.spbmts.ru)
17:07.40*** join/#htc-linux q_tpro (n=q_tpro@host-3-146-66-217.spbmts.ru)
17:11.57*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
17:15.44*** join/#htc-linux q_tpro__ (n=q_tpro@host-2-146-66-217.spbmts.ru)
17:46.11*** join/#htc-linux darkstar62 (n=darkstar@m1f0e36d0.tmodns.net)
18:02.18*** join/#htc-linux Aiv (n=aiv@office.mdsoftware.pl)
18:02.20Aivhello
18:29.05*** join/#htc-linux MikeKnoop (n=mk@99-195-162-237.dyn.centurytel.net)
18:33.44*** join/#htc-linux sxe^ (n=sxe@62.143.80.168)
18:51.05*** join/#htc-linux Aiv (n=aiv@office.mdsoftware.pl)
19:01.57*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
19:14.08*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
19:14.30*** join/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch)
19:14.52xperiahello aiv hello dcordes hello to all
19:15.52MikeKnoopHey there
19:16.49Aivhey
19:17.29xperiaaiv you are here great :-)
19:17.39Aivyes ? ;]
19:18.30*** join/#htc-linux q_tpro (n=q_tpro@host-2-146-66-217.spbmts.ru)
19:18.32xperiahow does you progress with the xperia port. I ahve some problems at the moment with tracing the i2c chip adresses
19:18.46q_tprohi
19:19.15q_tprodcordes: the MSM_CLK wiki is correct, only the clock-wince.c is wrong
19:19.28Aivu can download my x1-pack and check this your self ;]
19:19.48q_tpros2= arg6 = Ns&0x7
19:20.40q_tproand in clock-wince.c
19:20.44q_tpro#define MSM_CLOCK_REG(frequency,a1,a2,a3,a4,a5,a6,a7) { \
19:20.57q_tpro<PROTECTED>
19:20.57xperiahmmm where i didnt find something till yet. do i need to get it from the git sorces.
19:21.35q_tpro0x3 & (a6) should be replaced by 0x7 & (a6)
19:21.52Aivi u want to check my kernel version u can download pack 02 here: http://aiv-dev.info/opensource/xperiax1/
19:25.13Aivs/^i/if/
19:25.20Aiv;]
19:25.54xperiahey that is very interessting. i am downloading just right for testing. do i need some speciall boot option in haret.
19:26.19Aivu have all in zip file
19:26.31Aivjust extract it anywhere and run haret-x1 and press run
19:26.52Aivif booting stop at calibrating delay loop - w8
19:27.07Aivif booting stop and msmfb_probe() u need to reboot
19:27.15Aivs/and/at/
19:28.37q_tproAiv: x1 has the 7201A cpu ?
19:29.04Aivq_tpro 7200A
19:29.27q_tpro0A ?
19:29.33Aivyes
19:29.42q_tprostrange
19:29.50Aivwhty?
19:29.54Aivwhy?
19:30.00q_tprodo you have bluetooth working ?
19:30.15q_tprobecause there are 7500A and 7201A versions
19:30.22Aivi didn't test
19:30.27Aivhttp://pdadb.net/index.php?m=cpu&id=a7200a&c=qualcomm_msm7200a
19:30.40q_tpro7200A had some patent problems with broadcom
19:31.19q_tproAiv: hmm. pdadb is not really an authoritave data source :)
19:31.49q_tproyou need to check the bit in gpio block to see if it's 7200 or 7201
19:32.00q_tproi think it's documented in htc-linux wiki
19:32.07Aivq_tpro but i have x1 on my desk ;]
19:32.43Aivunder windows it's present as 7200A
19:33.08Aivhttp://www.phonewreck.com/wiki/images/b/b2/Xperia_x1_pcb_1.jpg
19:33.09Aiv;]
19:33.27Aiva little proof ;]
19:33.46q_tprohttp://htc-linux.org/wiki/index.php?title=RaphaelMemoryMapPg2
19:34.18q_tpro<PROTECTED>
19:35.08q_tproyou can check if it's true with haret :)
19:35.27q_tproimho there is no difference between them.
19:35.34Aivhow to read this address from haret?
19:36.00EspenfjoWhat codebase are you guys using? the kernel/msm.git from android.git.kernel.org, or something different?
19:36.24q_tpropd 0xa9000270 4
19:36.58xperiaq_tpro as i know bluetooth is not working properly till yet on x1. somebody here in the chanell the last days confirmed it. Aiv 5 seconds before booting linux :-) Espenfjo i am using the git repo from linuxtogo. See wiki blackstone linux
19:37.06q_tproEspenfjo: the 2.6.27 branch at git.linuxtogo.org
19:37.34q_tproxperia: it can't work because the clock settings are wrong
19:37.51Espenfjook, that might explain why the branch from kernel.org seemed so.. unusable :>
19:38.29q_tproxperia: there are 2 bugs in clock-wince.c : the source mask &3, and the clock prescaler should be changed from 3 to 1
19:39.11q_tproxperia: you also need to know the power and reset gpios (for htc raphael they are known) and the ADM channels
19:40.05Aivq_tpro a9000270 | 201700e1
19:40.41q_tproAiv: ok, so the top bit is not set, it's 7200A
19:41.07Aiv;]
19:41.23q_tpro:)
19:41.52Aivgood empirical evidence ;]
19:42.21q_tproAiv: do you know the bluetooth gpios, and ADM channel used by wince ?
19:42.22q_tproyeah
19:43.28q_tproAiv: btw, can you dump 1 more register in haret ?
19:43.48Aivhttp://htc-linux.org/wiki/index.php?title=Kovsky_GPIO we have only this from dcordes, and my updates
19:43.49Aivsure
19:43.54Aivi have still connected
19:44.25xperiaaiv it works great. It has booted without any problems. Keyboard works too. Great Job. On what are you working next so we can cordinate our work. WLAN having working woulnt be bad.
19:44.52Aivu can use usb0 to connect to internet
19:44.55Aivu can test ppp
19:45.11q_tproAiv: 0x104 in the CSR block
19:46.21q_tproxperia: wifi also needs power gpios, SD alt functions and the VREG bits
19:47.10q_tproAiv: pd 0xc0100104 4
19:47.25Aivq_tpro c0100104 | 00000007
19:47.33Aivi was afk
19:47.59Aivq_tpro in my kernel we have full working sd
19:48.14q_tprook, div=4 and SRC1 clock
19:48.29q_tproAiv: SD channel for wifi is different
19:49.19Aivq_tpro "div=4 and src1 clock" ? ;]
19:49.46q_tproit's the ARM11 clock setting for AHB bus
19:50.02q_tproacpuclock.c
19:50.47q_tprothere are no wifi gpios in Kovsky_GPIO
19:51.34Aivso give me 5 minutes, i will update check this via haret
19:51.54q_tprohttp://htc-linux.org/wiki/index.php?title=MSM_VREG
19:52.19q_tprowifi usually uses 2 vregs (0xc and 0xd in wince)
19:52.56q_tpromsmp and msme1
19:53.02q_tproat least on raph
19:54.06Aivwifi on kovsky: in2-8(232)=1 in2-9(233)=1 in2-10(234)=1 in2-11(235)=1 in2-12(236)=1
19:55.07Aivand flooding on in2-13 when it's turned on
19:55.32q_tprook, it's like on raph
19:55.57Aivgood
19:56.02q_tprobut you also need the alt data for drive strength
19:56.23q_tproyou may hope that it's the same for you as on raph
19:57.02Aivbtw on raph do u have access do buil-in flash?
19:57.37q_tproyes
19:57.56Aivhmm, what default device name?
19:57.58q_tprobut there are some problems with ECC
19:58.08Aivlike sdX , mmcblk, etc?
19:58.30q_tprocr2 has written that you need a partition table and a haret patch
19:58.39q_tprono, it's /dev/mtd/*
19:59.02Aivk
19:59.14q_tprothe msm_nand driver does not support non-2K aligned access.
19:59.38q_tproso you'll have problems with ext2
20:01.11xperiait looks like you have wifi working on your device. what for changes have to be done to get wifi working on the kovsky. only the gpios
20:01.53xperiaq_tpro i mean changes in the raph sources
20:01.53q_tproafaik nobody managed to get wifi working on raph
20:02.03q_tprobut the gpios and VREGs are known
20:02.26xperiaso we dont have any wifi on the modern htc devices till yet
20:02.31q_tproyou need the gpios and vregs first.
20:02.47q_tproyes, but it's the same chip
20:03.09q_tproanother headache is the different firmware between wince and googl.e
20:03.21q_tprodon't know which we should use
20:04.16q_tproxperia Aiv : check the bt and wifi power gpios
20:04.26q_tprothey are easy to trace
20:06.07Aivk, booting to win again
20:06.17xperiawhat i am asking myselft the whole time is why we are loosing such much time with hardware research. the knoweledge how to interact with the hardware is allready on the phone. From my side of view  we need to hijack a central driver in winmo that log the whole data to the hardware and we should know everything what we need. We dont have the right tools for getting the hardware information
20:06.35*** join/#htc-linux g55 (n=g55@rgnb-5d87cc05.pool.einsundeins.de)
20:07.36q_tproxperia: you are oversimplifying things
20:08.08q_tprowe don't have any msm7201A docs, and we can't even trace many things
20:08.31q_tprothe drivers are very cpu and hardware specific
20:08.54q_tprommutrace in haret comes as much as possible to the hardware debugger
20:09.35q_tproafaik from the haret docs, you can trap the on-cpu virtual memory accesses
20:09.46q_tproon the pxa cpu
20:10.01q_tproit's as close to the real hardware as it is possible
20:10.57q_tprohmm. where has dcordes disappeared ?
20:11.14Aivi don't know
20:12.00xperiait looks like we are speaking about different things. i am speaking about a pipe that let bypass the whole data transfer to the renamed driver. This way we should get easy the needed infos
20:13.22*** join/#htc-linux mickey_jaw (n=mike@78-105-123-214.zone3.bethere.co.uk)
20:13.26Aivwhen i turn bt on: out1-16(48)=1, in1-16(208)=1, in1-4(196)=0, in1-4(196)=1, in1-5(197)=0, in1-5(197)=1
20:13.46Aivwhen i turn bt off: out1-16(48)=0, in1-16(208)=0, in1-4(196)=1
20:13.49*** join/#htc-linux lucxxx (n=o_lucian@89-115-128-35.cl.ipv4ilink.net)
20:15.50descentioni've been (trying to) follow along for the past hour, and all this stuff sounds interesting to me.  I don't understand a lot of it, or how I could help, but I would be willing to start learning.
20:16.44*** join/#htc-linux q_tpro_ (n=q_tpro@host-3-146-66-217.spbmts.ru)
20:16.58q_tpro_disconnected
20:17.09q_tpro_damn gprs
20:17.44xperiaand q-tpro we dont need any infos about msm7xxxA. As we are sniffing only how winmo speak to the hardware and that are exactly the infos that we are needing for a better hardware support.
20:18.24MikeKnoopYup, I agree. I've got a bit of assembly experience and low level hardware experience but most of this stuff is outside of my scope of knowledge
20:19.06q_tpro_xperia: wince does not really speak to the hardware
20:19.46q_tpro_xperia: it's not _that_ level of hardware abstraction
20:20.04q_tpro_git pull over gprs is deadly ;)
20:22.42xperiawell okay the drivers speak to the hardware. however the driver runs on the mashine and dont tell me it is not possible to sniff how the driver interact with the hardware. i have xperience with softice i know what i am speaking about.
20:24.58q_tpro_it's what haret is trying to do
20:25.15q_tpro_softice for arm ?
20:25.29q_tpro_and we have multiple arm cpus
20:25.46q_tpro_they are even not really cpus, but microcontrollers
20:26.07q_tpro_how are you going to trace $random_cpld for example ?
20:26.29q_tpro_the only weak part in haret is the DMA tracing
20:26.42q_tpro_everything else is more or less usable
20:27.52*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
20:29.36xperiasoftice is overkill for arm i know. But you must see that the progress in porting linux is very slow becouse of the drivers. I mean how long is raphael allready on the market. Kaiser too. And we still dont have sound we dont have wifi. Something we are doing wrong for sure.
20:31.32Aivand what about google msm kernel?
20:31.52Aivthere is nothing for us?
20:31.59q_tpro_xperia: i don't get your logic
20:32.29q_tpro_xperia: google source is only one part of the story, because of the arm11/arm9=amss
20:33.17q_tpro_with all the amss interfaces we are fucked in the same way as with wince
20:33.34q_tpro_it's the same binary-only closed source software
20:34.11q_tpro_which is very difficult to reverse engineer because it runs on a separate cpu, within different security domain and so on
20:35.09q_tpro_and the g1 kernel uses different gpios, alt gpio settings, VREGs , has a cpld , etc.
20:35.16*** join/#htc-linux timebomb (n=tb@f054021058.adsl.alicedsl.de)
20:35.31q_tpro_just diff the raphael source with the trout kernel source
20:36.02mickey_jawdoes anyone else here have a universal?
20:36.49xperiaofcourse it is colsed binary sources. but you shoul be able to hijack it. imagine you are running the driver on a virtual machine and log everything what he output  and recieve. I give you right that google git kernel dont support windows mobile phone really.
20:38.49*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
20:41.45*** join/#htc-linux q_tpro__ (n=q_tpro@host-3-146-66-217.spbmts.ru)
20:41.55q_tpro__uh
20:42.08xperia:-) bad connection
20:42.19q_tpro__[23:36] <q_tpro_> xperia: so this work in unavoidable
20:42.21q_tpro__[23:36] <q_tpro_> xperia: ok, i tell you that wince accesses the register 0xa9100304
20:42.22q_tpro__[23:37] <q_tpro_> does it tell you anything without the cpu docs ? what is your point ?
20:42.58q_tpro__yeah. in the middle of nowhere. still better than nothing :)
20:44.50xperiai am not a xpert in asm but in every cpu you have registers
20:45.10xperiagetting the data to this register is all we need
20:45.58xperiaand this can be done by a another driver tha hijack the right driver
20:47.31xperiaa x85 cpu has if i am not wrong about 8 register ax bx cx dx and so on some of this register are needed for programm flow other are needed for data storing
20:47.40xperiax85
20:47.46xperiax86
20:47.56MikeKnoophow exactly are you planning on using these registeres?
20:48.39MikeKnoopevery register is typically used so you're going to have a hard time "copying" or "logging" anything off of them
20:49.30*** join/#htc-linux q_tpro (n=q_tpro@host-2-146-66-217.spbmts.ru)
20:49.43MikeKnoopbesides writing some sort of software to that affect would be much harder than the alternatives
20:50.31xperiathis hard i know but the it is the most succefull possibility
20:50.57descentioni know win CE isn't Win MO, but the Win CE kernel source is open.  am I to assume it would not help at all?
20:53.46q_tprodescention: the hardware drivers depend on the hw manufacturer
20:54.02descentionok
20:54.36q_tproeven if you have a driver , you need to know how and where it is wired. gpios, address spaces, i2c addresses (if configurable)
20:54.59q_tprovregs on a compation chip, used for MSM cpus
20:55.10q_tpros/tion/nion/
20:55.40descentionwish our bot did that ^
20:55.43q_tproonly htc knows that., and we can once trace it or disassemble the .dlls
20:55.53xperiathis can be sniffed from the registers of the cpu. everything that the driver do is executed on the cpu registers. grab the registers and you have the whole konweledge
20:56.32q_tproxperia: not always
20:57.15xperiawhy not the driver is a software that runs on the cpu and interact only with the registers of the cpu
20:57.21q_tproxperia: the vregs are controlled by the arm11->arm9 ipc, and you will sink in the data volume needed to decode it
20:57.53q_tproin theory, you are right.
20:58.13q_tprobut you are underestimating the amount of RE work, and the data
20:58.48q_tprowe are actually rather fast for a new unknown cpu
20:58.56descentionheh
21:00.31q_tprook, i have a git diff for the clock-wince.c
21:00.42q_tprowill try to paste it somewhere.
21:02.45q_tprodescention: i'd like to know how much $$$$ htc has spent developing msm7201A support, for qualcomm NDA and such things.
21:02.54EspenfjoYou all use gnueabi?
21:03.32xperiait goes for me to 23.00 i have to close the session here and do tomorrow some new stuff on kovsky port. q_tpro and Mike Knoop thanks for the conversation
21:03.36q_tprodescention: so our $/developer will be excellent i guess :)
21:03.54q_tproxperia: good night
21:04.14xperiabye
21:04.51Espenfjoq_tpro: You use normal gcc, or eabi to compile?
21:05.25q_tproeabi
21:05.34Espenfjook, yeah
21:05.49q_tproEspenfjo: i think non-eabi is not used for several years
21:06.27EspenfjoThat might be true, ARM did the change to the new format some years ago. So this also might explain my hangs :P
21:07.37Espenfjordhi, rdlo and rm must all be different - are the dozens of these something we normally should worry about?
21:10.59*** join/#htc-linux WigglerAway (n=WigglerA@92-235-224-158.cable.ubr12.stav.blueyonder.co.uk)
21:11.03*** join/#htc-linux q_tpro_ (n=q_tpro@host-1-146-66-217.spbmts.ru)
21:15.34*** join/#htc-linux q_tpro__ (n=q_tpro@host-2-146-66-217.spbmts.ru)
21:23.12q_tpro__can't use pastebin.
21:23.17*** join/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch)
21:24.12MikeKnooppastie.org
21:26.15xperiai am on the way to the bad. this here should be very easy to achieve as we can also very easy sniffing how winmo is talking to the driver ;-) http://en.wikipedia.org/wiki/Driver_wrapper that was my first Idea before the talk begann and i have losed somehow the track.
21:26.20xperiabye
21:26.45*** part/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch)
21:29.39*** join/#htc-linux q_tpro (n=q_tpro@host-1-146-66-217.spbmts.ru)
21:29.52q_tprohangs at POST too
21:30.11q_tproevil gprs
21:30.33MikeKnoopwhat are you psting?
21:30.49q_tproa small patch
21:31.31MikeKnoopIf you want, shoot me a PM and ill throw it onto a paste site and post the link here.
21:38.00*** join/#htc-linux g55 (n=g55@rgnb-5d87cc1c.pool.einsundeins.de)
21:40.28mickey_jawdoes anyone here have experience with lirc?
21:41.09ali1234yes a little
21:41.32dcordeshi. sorry was afk
21:42.45mickey_jawi was wondering if anyone has tried to build the zaurus config for lirc lately
21:43.04mickey_jawcan
21:43.15*** join/#htc-linux q_tpro_ (n=q_tpro@host-2-146-66-217.spbmts.ru)
21:43.21dcordesEspenfjo: http://www.htc-linux.org/wiki/index.php?title=Kernel
21:43.23dcordesq_tpro_: hi
21:43.51Espenfjodcordes: Yeah, have been looking at it :)
21:44.09mickey_jawas zaurus has same IR setup on PXA270 UART as htc universal
21:45.07dcordesmickey_jaw: I've been using akita zaurus extensively but never tried IR
21:45.33dcordesmickey_jaw: maybe in #angstrom they can help you. what image do you use?
21:45.52mickey_jawrunning debian lenny
21:46.09q_tpro_dcordes: can't paste the patch
21:46.23mickey_jawbut with hh.org 2.6.21-hh20 kernel from Titchy
21:48.10dcordesq_tpro_: why what's the problem?
21:48.35mickey_jawwhen i query the uarts with setserial there's no port address just irq's
21:49.09mickey_jawso i can't feed port address/irq to lirc_sir
21:53.48*** join/#htc-linux q_tpro__ (n=q_tpro@host-1-146-66-217.spbmts.ru)
21:54.50q_tpro__dcordes: maybe you can apply it manually ?
22:17.27*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
22:28.19*** join/#htc-linux |Jason8| (i=JayAte@server1.tiltshellz.org)
23:53.33dcordes_q_tpro: if you are here tomorrow we can apply it manually
23:54.01dcordes_good night

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