irclog2html for #htc-linux on 20060502

06:07.24*** join/#htc-linux goxboxlive (n=goxboxli@ti500710a080-14919.bb.online.no)
06:38.39*** join/#htc-linux rob_w|mis (n=rob_w@p549BC136.dip0.t-ipconnect.de)
07:16.37*** join/#htc-linux awelux (n=awelux__@dslb-084-058-168-026.pools.arcor-ip.net)
09:36.28*** join/#htc-linux geers_ (n=DevzMan@c51008F31.inet.catch.no)
12:14.49*** join/#htc-linux leOn (n=xxx@mathilda.ci.fct.unl.pt)
12:14.55leOnhello
12:15.25leOndoes anyone know if the xdadev_all_unlock tool works with the Qtek S200 ?
12:56.09rob_w|misno
14:27.50*** join/#htc-linux goxboxlive (n=goxboxli@ti500710a080-14919.bb.online.no)
17:34.27*** join/#htc-linux BabelOued (n=BabelOue@lun34-2-82-238-28-28.fbx.proxad.net)
17:43.04*** join/#htc-linux awelux (n=awelux__@dslb-084-058-168-026.pools.arcor-ip.net)
17:53.45goxboxlivecr2: I have made e new Opie image. What to fix in it? You said last time that i had several bugz. What do i need to do to fix them?
18:43.28*** join/#htc-linux husam (n=kvirc@217.206.111.105)
19:00.55*** join/#htc-linux immolo (i=fwxhmt@cpc3-cosh1-4-0-cust151.cos2.cable.ntl.com)
19:11.05aweluxwhat is the status of the touchscreen nonlinearity issues? I've heared you created a modified ts library? Maybe the current TS system is not very suitable at all for the TI2046 chip? It looks like we need more samples for a stable position.
19:16.11*** join/#htc-linux immolo (i=fmahjvr@cpc3-cosh1-4-0-cust151.cos2.cable.ntl.com)
19:48.46goxboxliveawelux: How is the touchscreen on magican? Os it bether that on the uni?
19:49.09aweluxnot really better
19:49.28goxboxlivei c, is it wlan on the magican?
19:49.47aweluxthe distortion seams to be very similar in principle.
19:49.50aweluxno wlan on magician
19:50.01goxboxliveok
19:50.22aweluxonly bluetooth
19:51.22goxboxliveok, but what is it called? Is it the S100 device?
19:51.35aweluxI'm having a VPA compact
19:51.39aweluxfrom vodafon
19:51.46aweluxit's the refresh actually
19:52.05aweluxsame hardware as magician witha nslightly different case.
19:52.45goxboxliveok
19:53.18aweluxand since about 24h it's running with opie ^^
19:53.56aweluxAnd I discovered that you can really empty your batteries with linux
19:54.08goxboxliveThat's cool.
19:54.25goxboxliveYes it drains a lot of the batteries.
19:55.01aweluxa better TS calibration and power management is high on the list
19:57.41goxboxliveYes, and a 2.6.16 port.
20:00.46aweluxQuestion about TS. I notice that the T2046 has a lot of internal modes what to meassure. Do you think we use the right setting there?
20:07.10goxboxliveI have no idea. I am not a developer, just a regular linux user who helps out with testing :-)
20:11.00aweluxhehe
20:11.15aweluxI've just read that 2.6.17 will have a new wlan stack.
20:13.42goxboxliveok
21:01.28*** join/#htc-linux cr2 (n=konversa@crpl22.physik.uni-wuppertal.de)
21:06.44cr2hi awelux
21:15.10aweluxhi cr2
21:15.18aweluxI've just read that 2.6.17 will have a new wlan stack.
21:18.45cr2i don't think it will help us
21:19.55aweluxand about the ts. I've noticed that the TI2046 has a lot of internal switches and modes. Are we sure we are using the right mode ?
21:20.38cr2yes.
21:20.52cr2the driver is strange a bit.
21:21.02cr2in a way it operates
21:21.21cr2there is ads7846 driver with the same interface.
21:21.26aweluxok. I had hoped we just have to use the right reference settings for x or y measurements.
21:21.26cr2in 2.6.16
21:21.33aweluxoh. ok
21:21.51cr2there is also corgi_ts.c driver for 7846
21:22.15cr2you can try to compile the usb host support
21:22.17aweluxyou read the part about writing "PD1=0" after power up?
21:22.36cr2and look if you will see the bt
21:22.41aweluxto get into ADS7843 compatibility mode ?
21:22.55cr2we don't care about power right now.
21:23.13aweluxso the bt is not on the btuart but on the usb bus ?
21:23.20cr2thr ts interface is quite primitive.
21:23.31cr2ask for x ; get x ; ask for y ; get x
21:23.43cr2yes. bt is on usb.
21:23.48cr2on magician
21:24.18aweluxI don't see it with lsusb when my pc is the host
21:24.29cr2?
21:24.46cr2you should run lsusb on magician
21:24.51cr2but it is not there.
21:24.53aweluxif it's on the same bus shouldn't I see it in on the pc ?
21:24.58cr2mount usbfs
21:25.07cr2and cat /proc/bus/usb/devices
21:25.16cr2i can see the phone this way.
21:25.28aweluxok.
21:25.30cr2it's on another port.
22:24.07cr2awelux, i have dumped the first 4MB RAM (in wince) and see some interesting thing.
22:28.22husamguys does anybody here knows about jtags !!!!
22:29.08cr2JTag is a Java ID3 tagger
22:29.20cr2http://jtag.sourceforge.net/
22:29.57husamyes ... I manage to overwrite the firmware in my device ... when I was testing mdoc+ driver :(
22:30.28cr2hmm.
22:30.31cr2http://openwince.sourceforge.net/jtag/
22:30.43husamso I'm trying to find the connecteter in our board
22:31.12cr2you need to find the pins
22:31.47cr2http://wiki.xda-developers.com/index.php?pagename=WallabyJTAG
22:31.52husamhow one can look for these
22:32.29cr2http://openwince.sourceforge.net/jtag/iPAQ-3600/
22:33.34cr2they are marked on the motherboard
22:34.26husamohh I see ... I guess I will have to open up my device ... but looks good ... are they standerd
22:35.01cr2yes.
22:35.20husamthanks
22:53.17husamcr2: i think i found the connector http://www.handhelds.org/moin/moin.cgi/HpIpaqH6315?action=AttachFile&do=get&target=BackSchematic.jpg
22:53.56aweluxcr2, what do you see?
22:56.44aweluxhmm. for some strange reason I can't reproduce the no booting with flight mode with my modified kernel
23:12.27cr2i see the bootloader remnants at the bottom of the RAM.
23:15.07aweluxoh
23:15.53aweluxso we could disassemble parts of it to find the very early hardware initialisation ?
23:19.13aweluxfor the flight mode thing it's probably best to follow your ideas of a memory scan.
23:19.51aweluxThat's easy compared to the rest.
23:20.00cr2you have wince2003?
23:20.08aweluxyes
23:20.30cr2ok. but the bootloader is still tricky.
23:20.33cr2pxa272 ?
23:20.37aweluxyes
23:20.54cr2can you dump the first ROM megabyte ?
23:21.10cr2pwf rom 0x0 0x100000
23:21.29cr2flash megabyte.
23:24.05cr2i'm also curious what is saved on my zero RAM page.
23:25.46aweluxok. got the rom
23:26.32cr2hmm. looks good.
23:26.36cr2<PROTECTED>
23:26.37cr2<PROTECTED>
23:27.23cr2this is the vmem->pmem table
23:27.27cr2<PROTECTED>
23:27.27cr2<PROTECTED>
23:27.28cr2<PROTECTED>
23:27.28cr2<PROTECTED>
23:27.28cr2<PROTECTED>
23:27.28cr2<PROTECTED>
23:27.53aweluxhttp://home.arcor.de/awelux/tmp/rom
23:28.14cr2gpio and friends
23:28.17cr2<PROTECTED>
23:28.17cr2<PROTECTED>
23:28.18cr2<PROTECTED>
23:28.18cr2<PROTECTED>
23:28.18cr2<PROTECTED>
23:28.19aweluxyou need toi fix your dcc sends
23:30.03aweluxhow do you disassemble raw code ?
23:31.09cr2yes. what you see above is my bootloader.
23:31.20cr2and rom is your bootloader.
23:31.40cr2<PROTECTED>
23:31.42aweluxI mean. objdump doesn't seam to work
23:31.47aweluxah. thx
23:31.54cr2will also work with linux objdump
23:33.15cr2task 46
23:33.33cr2bt test
23:34.59cr2the bootloader is 256K
23:35.05cr2a bit less
23:35.19cr2at 0x40000 starts the wince kernel nk.xe
23:38.03cr2i'm tired now. good night.
23:39.07aweluxgn8

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.