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.52 | MikeKnoop | Lots of people in here... was expecting a smaller crowd |
02:29.41 | *** join/#htc-linux |Jason8| (i=JayAte@server1.tiltshellz.org) |
02:32.58 | MikeKnoop | Is anyone here currently working on the android port? |
02:33.44 | *** join/#htc-linux SOG (n=IamSOG@218.20.219.3) |
02:33.51 | MikeKnoop | Specifically, for the Diamond/Raphael |
02:39.44 | miknix | MikeKnoop, Diamond? is that an omap850? |
02:43.32 | *** join/#htc-linux g55 (n=g55@rgnb-5d87ceed.pool.einsundeins.de) |
02:45.55 | MikeKnoop | No, 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.03 | miknix | ah, its a msm |
02:57.23 | miknix | I'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.02 | chavonbravo | hey |
04:35.19 | chavonbravo | anyone 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.34 | xperia | dcordes are you here |
09:36.26 | dcordes | xperia, yes |
09:36.36 | xperia | great :-) |
09:36.56 | xperia | i have a question about the i2c chip addresses on the xperia |
09:37.40 | dcordes | shoot |
09:38.10 | xperia | i 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.29 | xperia | i have some strange logs in dmesg |
09:39.21 | xperia | or 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.11 | xperia | here is some output of the dmesg text |
09:42.19 | xperia | [ 15.724667] microp-klt: probe of 0-0066 failed with error -524 |
09:42.40 | xperia | [ 15.661679] microp-ksc: Registering MicroP-KEY driver |
09:42.42 | xperia | [ 15.669522] microp-klt: Registering MicroP-LED driver |
09:42.43 | xperia | [ 15.677335] microp-klt: Initializing MicroP-LED chip driver at addr: 0x66 |
09:42.45 | xperia | [ 15.694730] microp-klt: This hardware is not yet supported: 0000 |
09:47.10 | dcordes | xperia, don't worry. we found out that the i2c address in the present driver is correct- it's a gpio question only |
09:47.55 | dcordes | xperia, 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.14 | xperia | ok thanks for the info. P.S Do you know the Nick of the Person |
09:53.32 | dcordes | yes it is Aiv. Stick around. he will be online later |
09:53.53 | dcordes | the wiki.htc-linux.org was also updated if you want to read something already |
09:59.09 | xperia | nice. 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.23 | IceBone | http://www.youtube.com/watch?v=WTFlFFrfEB0 |
11:29.00 | *** join/#htc-linux Nirvana (n=noneavai@freecode-project/hacker/LordInquisitor) |
12:04.18 | dcordes | bbl |
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.20 | q_tpro_ | hi |
16:50.46 | q_tpro_ | dcordes: fyi. there is one potential problem with the bluetooth clock setup |
16:52.36 | q_tpro_ | dcordes: it is sourced from ACPU_PLL_0 with the prescaler 4, M/N divisor and baud divisor =16 |
16:53.59 | q_tpro_ | dcordes: google has a different setup, because they operate the base clock at 4X speed (different baud divisor settings) |
16:55.43 | q_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.20 | Aiv | hello |
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.52 | xperia | hello aiv hello dcordes hello to all |
19:15.52 | MikeKnoop | Hey there |
19:16.49 | Aiv | hey |
19:17.29 | xperia | aiv you are here great :-) |
19:17.39 | Aiv | yes ? ;] |
19:18.30 | *** join/#htc-linux q_tpro (n=q_tpro@host-2-146-66-217.spbmts.ru) |
19:18.32 | xperia | how does you progress with the xperia port. I ahve some problems at the moment with tracing the i2c chip adresses |
19:18.46 | q_tpro | hi |
19:19.15 | q_tpro | dcordes: the MSM_CLK wiki is correct, only the clock-wince.c is wrong |
19:19.28 | Aiv | u can download my x1-pack and check this your self ;] |
19:19.48 | q_tpro | s2= arg6 = Ns&0x7 |
19:20.40 | q_tpro | and in clock-wince.c |
19:20.44 | q_tpro | #define MSM_CLOCK_REG(frequency,a1,a2,a3,a4,a5,a6,a7) { \ |
19:20.57 | q_tpro | <PROTECTED> |
19:20.57 | xperia | hmmm where i didnt find something till yet. do i need to get it from the git sorces. |
19:21.35 | q_tpro | 0x3 & (a6) should be replaced by 0x7 & (a6) |
19:21.52 | Aiv | i u want to check my kernel version u can download pack 02 here: http://aiv-dev.info/opensource/xperiax1/ |
19:25.13 | Aiv | s/^i/if/ |
19:25.20 | Aiv | ;] |
19:25.54 | xperia | hey that is very interessting. i am downloading just right for testing. do i need some speciall boot option in haret. |
19:26.19 | Aiv | u have all in zip file |
19:26.31 | Aiv | just extract it anywhere and run haret-x1 and press run |
19:26.52 | Aiv | if booting stop at calibrating delay loop - w8 |
19:27.07 | Aiv | if booting stop and msmfb_probe() u need to reboot |
19:27.15 | Aiv | s/and/at/ |
19:28.37 | q_tpro | Aiv: x1 has the 7201A cpu ? |
19:29.04 | Aiv | q_tpro 7200A |
19:29.27 | q_tpro | 0A ? |
19:29.33 | Aiv | yes |
19:29.42 | q_tpro | strange |
19:29.50 | Aiv | whty? |
19:29.54 | Aiv | why? |
19:30.00 | q_tpro | do you have bluetooth working ? |
19:30.15 | q_tpro | because there are 7500A and 7201A versions |
19:30.22 | Aiv | i didn't test |
19:30.27 | Aiv | http://pdadb.net/index.php?m=cpu&id=a7200a&c=qualcomm_msm7200a |
19:30.40 | q_tpro | 7200A had some patent problems with broadcom |
19:31.19 | q_tpro | Aiv: hmm. pdadb is not really an authoritave data source :) |
19:31.49 | q_tpro | you need to check the bit in gpio block to see if it's 7200 or 7201 |
19:32.00 | q_tpro | i think it's documented in htc-linux wiki |
19:32.07 | Aiv | q_tpro but i have x1 on my desk ;] |
19:32.43 | Aiv | under windows it's present as 7200A |
19:33.08 | Aiv | http://www.phonewreck.com/wiki/images/b/b2/Xperia_x1_pcb_1.jpg |
19:33.09 | Aiv | ;] |
19:33.27 | Aiv | a little proof ;] |
19:33.46 | q_tpro | http://htc-linux.org/wiki/index.php?title=RaphaelMemoryMapPg2 |
19:34.18 | q_tpro | <PROTECTED> |
19:35.08 | q_tpro | you can check if it's true with haret :) |
19:35.27 | q_tpro | imho there is no difference between them. |
19:35.34 | Aiv | how to read this address from haret? |
19:36.00 | Espenfjo | What codebase are you guys using? the kernel/msm.git from android.git.kernel.org, or something different? |
19:36.24 | q_tpro | pd 0xa9000270 4 |
19:36.58 | xperia | q_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.06 | q_tpro | Espenfjo: the 2.6.27 branch at git.linuxtogo.org |
19:37.34 | q_tpro | xperia: it can't work because the clock settings are wrong |
19:37.51 | Espenfjo | ok, that might explain why the branch from kernel.org seemed so.. unusable :> |
19:38.29 | q_tpro | xperia: 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.11 | q_tpro | xperia: you also need to know the power and reset gpios (for htc raphael they are known) and the ADM channels |
19:40.05 | Aiv | q_tpro a9000270 | 201700e1 |
19:40.41 | q_tpro | Aiv: ok, so the top bit is not set, it's 7200A |
19:41.07 | Aiv | ;] |
19:41.23 | q_tpro | :) |
19:41.52 | Aiv | good empirical evidence ;] |
19:42.21 | q_tpro | Aiv: do you know the bluetooth gpios, and ADM channel used by wince ? |
19:42.22 | q_tpro | yeah |
19:43.28 | q_tpro | Aiv: btw, can you dump 1 more register in haret ? |
19:43.48 | Aiv | http://htc-linux.org/wiki/index.php?title=Kovsky_GPIO we have only this from dcordes, and my updates |
19:43.49 | Aiv | sure |
19:43.54 | Aiv | i have still connected |
19:44.25 | xperia | aiv 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.52 | Aiv | u can use usb0 to connect to internet |
19:44.55 | Aiv | u can test ppp |
19:45.11 | q_tpro | Aiv: 0x104 in the CSR block |
19:46.21 | q_tpro | xperia: wifi also needs power gpios, SD alt functions and the VREG bits |
19:47.10 | q_tpro | Aiv: pd 0xc0100104 4 |
19:47.25 | Aiv | q_tpro c0100104 | 00000007 |
19:47.33 | Aiv | i was afk |
19:47.59 | Aiv | q_tpro in my kernel we have full working sd |
19:48.14 | q_tpro | ok, div=4 and SRC1 clock |
19:48.29 | q_tpro | Aiv: SD channel for wifi is different |
19:49.19 | Aiv | q_tpro "div=4 and src1 clock" ? ;] |
19:49.46 | q_tpro | it's the ARM11 clock setting for AHB bus |
19:50.02 | q_tpro | acpuclock.c |
19:50.47 | q_tpro | there are no wifi gpios in Kovsky_GPIO |
19:51.34 | Aiv | so give me 5 minutes, i will update check this via haret |
19:51.54 | q_tpro | http://htc-linux.org/wiki/index.php?title=MSM_VREG |
19:52.19 | q_tpro | wifi usually uses 2 vregs (0xc and 0xd in wince) |
19:52.56 | q_tpro | msmp and msme1 |
19:53.02 | q_tpro | at least on raph |
19:54.06 | Aiv | wifi on kovsky: in2-8(232)=1 in2-9(233)=1 in2-10(234)=1 in2-11(235)=1 in2-12(236)=1 |
19:55.07 | Aiv | and flooding on in2-13 when it's turned on |
19:55.32 | q_tpro | ok, it's like on raph |
19:55.57 | Aiv | good |
19:56.02 | q_tpro | but you also need the alt data for drive strength |
19:56.23 | q_tpro | you may hope that it's the same for you as on raph |
19:57.02 | Aiv | btw on raph do u have access do buil-in flash? |
19:57.37 | q_tpro | yes |
19:57.56 | Aiv | hmm, what default device name? |
19:57.58 | q_tpro | but there are some problems with ECC |
19:58.08 | Aiv | like sdX , mmcblk, etc? |
19:58.30 | q_tpro | cr2 has written that you need a partition table and a haret patch |
19:58.39 | q_tpro | no, it's /dev/mtd/* |
19:59.02 | Aiv | k |
19:59.14 | q_tpro | the msm_nand driver does not support non-2K aligned access. |
19:59.38 | q_tpro | so you'll have problems with ext2 |
20:01.11 | xperia | it 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.53 | xperia | q_tpro i mean changes in the raph sources |
20:01.53 | q_tpro | afaik nobody managed to get wifi working on raph |
20:02.03 | q_tpro | but the gpios and VREGs are known |
20:02.26 | xperia | so we dont have any wifi on the modern htc devices till yet |
20:02.31 | q_tpro | you need the gpios and vregs first. |
20:02.47 | q_tpro | yes, but it's the same chip |
20:03.09 | q_tpro | another headache is the different firmware between wince and googl.e |
20:03.21 | q_tpro | don't know which we should use |
20:04.16 | q_tpro | xperia Aiv : check the bt and wifi power gpios |
20:04.26 | q_tpro | they are easy to trace |
20:06.07 | Aiv | k, booting to win again |
20:06.17 | xperia | what 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.36 | q_tpro | xperia: you are oversimplifying things |
20:08.08 | q_tpro | we don't have any msm7201A docs, and we can't even trace many things |
20:08.31 | q_tpro | the drivers are very cpu and hardware specific |
20:08.54 | q_tpro | mmutrace in haret comes as much as possible to the hardware debugger |
20:09.35 | q_tpro | afaik from the haret docs, you can trap the on-cpu virtual memory accesses |
20:09.46 | q_tpro | on the pxa cpu |
20:10.01 | q_tpro | it's as close to the real hardware as it is possible |
20:10.57 | q_tpro | hmm. where has dcordes disappeared ? |
20:11.14 | Aiv | i don't know |
20:12.00 | xperia | it 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.26 | Aiv | when 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.46 | Aiv | when 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.50 | descention | i'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.58 | q_tpro_ | disconnected |
20:17.09 | q_tpro_ | damn gprs |
20:17.44 | xperia | and 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.24 | MikeKnoop | Yup, 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.06 | q_tpro_ | xperia: wince does not really speak to the hardware |
20:19.46 | q_tpro_ | xperia: it's not _that_ level of hardware abstraction |
20:20.04 | q_tpro_ | git pull over gprs is deadly ;) |
20:22.42 | xperia | well 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.58 | q_tpro_ | it's what haret is trying to do |
20:25.15 | q_tpro_ | softice for arm ? |
20:25.29 | q_tpro_ | and we have multiple arm cpus |
20:25.46 | q_tpro_ | they are even not really cpus, but microcontrollers |
20:26.07 | q_tpro_ | how are you going to trace $random_cpld for example ? |
20:26.29 | q_tpro_ | the only weak part in haret is the DMA tracing |
20:26.42 | q_tpro_ | everything else is more or less usable |
20:27.52 | *** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net) |
20:29.36 | xperia | softice 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.32 | Aiv | and what about google msm kernel? |
20:31.52 | Aiv | there is nothing for us? |
20:31.59 | q_tpro_ | xperia: i don't get your logic |
20:32.29 | q_tpro_ | xperia: google source is only one part of the story, because of the arm11/arm9=amss |
20:33.17 | q_tpro_ | with all the amss interfaces we are fucked in the same way as with wince |
20:33.34 | q_tpro_ | it's the same binary-only closed source software |
20:34.11 | q_tpro_ | which is very difficult to reverse engineer because it runs on a separate cpu, within different security domain and so on |
20:35.09 | q_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.31 | q_tpro_ | just diff the raphael source with the trout kernel source |
20:36.02 | mickey_jaw | does anyone else here have a universal? |
20:36.49 | xperia | ofcourse 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.55 | q_tpro__ | uh |
20:42.08 | xperia | :-) bad connection |
20:42.19 | q_tpro__ | [23:36] <q_tpro_> xperia: so this work in unavoidable |
20:42.21 | q_tpro__ | [23:36] <q_tpro_> xperia: ok, i tell you that wince accesses the register 0xa9100304 |
20:42.22 | q_tpro__ | [23:37] <q_tpro_> does it tell you anything without the cpu docs ? what is your point ? |
20:42.58 | q_tpro__ | yeah. in the middle of nowhere. still better than nothing :) |
20:44.50 | xperia | i am not a xpert in asm but in every cpu you have registers |
20:45.10 | xperia | getting the data to this register is all we need |
20:45.58 | xperia | and this can be done by a another driver tha hijack the right driver |
20:47.31 | xperia | a 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.40 | xperia | x85 |
20:47.46 | xperia | x86 |
20:47.56 | MikeKnoop | how exactly are you planning on using these registeres? |
20:48.39 | MikeKnoop | every 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.43 | MikeKnoop | besides writing some sort of software to that affect would be much harder than the alternatives |
20:50.31 | xperia | this hard i know but the it is the most succefull possibility |
20:50.57 | descention | i 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.46 | q_tpro | descention: the hardware drivers depend on the hw manufacturer |
20:54.02 | descention | ok |
20:54.36 | q_tpro | even if you have a driver , you need to know how and where it is wired. gpios, address spaces, i2c addresses (if configurable) |
20:54.59 | q_tpro | vregs on a compation chip, used for MSM cpus |
20:55.10 | q_tpro | s/tion/nion/ |
20:55.40 | descention | wish our bot did that ^ |
20:55.43 | q_tpro | only htc knows that., and we can once trace it or disassemble the .dlls |
20:55.53 | xperia | this 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.32 | q_tpro | xperia: not always |
20:57.15 | xperia | why not the driver is a software that runs on the cpu and interact only with the registers of the cpu |
20:57.21 | q_tpro | xperia: the vregs are controlled by the arm11->arm9 ipc, and you will sink in the data volume needed to decode it |
20:57.53 | q_tpro | in theory, you are right. |
20:58.13 | q_tpro | but you are underestimating the amount of RE work, and the data |
20:58.48 | q_tpro | we are actually rather fast for a new unknown cpu |
20:58.56 | descention | heh |
21:00.31 | q_tpro | ok, i have a git diff for the clock-wince.c |
21:00.42 | q_tpro | will try to paste it somewhere. |
21:02.45 | q_tpro | descention: i'd like to know how much $$$$ htc has spent developing msm7201A support, for qualcomm NDA and such things. |
21:02.54 | Espenfjo | You all use gnueabi? |
21:03.32 | xperia | it 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.36 | q_tpro | descention: so our $/developer will be excellent i guess :) |
21:03.54 | q_tpro | xperia: good night |
21:04.14 | xperia | bye |
21:04.51 | Espenfjo | q_tpro: You use normal gcc, or eabi to compile? |
21:05.25 | q_tpro | eabi |
21:05.34 | Espenfjo | ok, yeah |
21:05.49 | q_tpro | Espenfjo: i think non-eabi is not used for several years |
21:06.27 | Espenfjo | That might be true, ARM did the change to the new format some years ago. So this also might explain my hangs :P |
21:07.37 | Espenfjo | rdhi, 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.12 | q_tpro__ | can't use pastebin. |
21:23.17 | *** join/#htc-linux xperia (n=chatzill@77-56-92-125.dclient.hispeed.ch) |
21:24.12 | MikeKnoop | pastie.org |
21:26.15 | xperia | i 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.20 | xperia | bye |
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.52 | q_tpro | hangs at POST too |
21:30.11 | q_tpro | evil gprs |
21:30.33 | MikeKnoop | what are you psting? |
21:30.49 | q_tpro | a small patch |
21:31.31 | MikeKnoop | If 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.28 | mickey_jaw | does anyone here have experience with lirc? |
21:41.09 | ali1234 | yes a little |
21:41.32 | dcordes | hi. sorry was afk |
21:42.45 | mickey_jaw | i was wondering if anyone has tried to build the zaurus config for lirc lately |
21:43.04 | mickey_jaw | can |
21:43.15 | *** join/#htc-linux q_tpro_ (n=q_tpro@host-2-146-66-217.spbmts.ru) |
21:43.21 | dcordes | Espenfjo: http://www.htc-linux.org/wiki/index.php?title=Kernel |
21:43.23 | dcordes | q_tpro_: hi |
21:43.51 | Espenfjo | dcordes: Yeah, have been looking at it :) |
21:44.09 | mickey_jaw | as zaurus has same IR setup on PXA270 UART as htc universal |
21:45.07 | dcordes | mickey_jaw: I've been using akita zaurus extensively but never tried IR |
21:45.33 | dcordes | mickey_jaw: maybe in #angstrom they can help you. what image do you use? |
21:45.52 | mickey_jaw | running debian lenny |
21:46.09 | q_tpro_ | dcordes: can't paste the patch |
21:46.23 | mickey_jaw | but with hh.org 2.6.21-hh20 kernel from Titchy |
21:48.10 | dcordes | q_tpro_: why what's the problem? |
21:48.35 | mickey_jaw | when i query the uarts with setserial there's no port address just irq's |
21:49.09 | mickey_jaw | so 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.50 | q_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.33 | dcordes_ | q_tpro: if you are here tomorrow we can apply it manually |
23:54.01 | dcordes_ | good night |