irclog2html for #htc-linux on 20061117

00:02.36cr2010.050010 irq 21(BTUART)
00:02.54cr2010.045919-010.048607 write: '\x01\x13\x0c\xf8Pocket_PC\x00
00:03.02cr2interesting.
00:30.49Kevin2Hi
00:43.15Speedy2I have windows
00:51.51lkcloh ok.
00:52.17lkclSpeedy: would you be able to coordinate with cr2, we need to extract nk.exe from the hw6915 rom
00:55.14Speedy2Sure.  cr2, let me know how I can help
00:55.19lkclah ha!
00:55.21Speedy2Note:  I have no PocketPC or WINCE access
00:55.21lkclftp://ftp.compaq.com/pub/softpaq/sp33501-34000/sp33733.exe
00:55.42lkclit's the german ROM update for hw6900 series, dated 15sep2006
00:56.25lkclwheeeeee :)
00:56.31lkclohh that's okayyy
00:56.32Speedy2That's good?
01:01.48lkclok - i have CEOS.nbf
01:02.00lkclok now i need that nbf extracter program....
01:31.31*** join/#htc-linux psokolovsky (n=psokolov@239.usernat.ip.net.ua)
01:52.17*** join/#htc-linux psokolovsky (n=psokolov@239.usernat.ip.net.ua)
02:02.39*** join/#htc-linux psokolovsky_ (n=psokolov@239.usernat.ip.net.ua)
02:26.04*** join/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com)
02:47.04pofcr2: i've your testwm5 custom build ready, could not reply before cos I went out for beers...
02:47.22pofand now xda-dev seems downw :(
03:00.12lkclwiki.xda-developers.com is up, fine
03:32.45lkcli got the crc16 algorithm.
03:33.44lkclthe length header stupidly _isn't_ included in the crc check ha ha
03:33.47lkclwhich is really dumb.
03:44.44*** join/#htc-linux Ubuntos (n=ref@nl4-out.vpn-service.us)
03:45.07*** part/#htc-linux Ubuntos (n=ref@nl4-out.vpn-service.us)
04:19.02Speedy2Are you talking on your HTC in Linux now lkcl?
04:32.01*** join/#htc-linux Ubuntos (n=ref@195.222.64.209)
05:10.14*** join/#htc-linux psokolovsky_ (n=psokolov@239.usernat.ip.net.ua)
06:35.13*** join/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com)
06:36.01*** part/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com)
07:11.34*** join/#htc-linux LunohoD_ (n=alex@e180102122.adsl.alicedsl.de)
08:10.03*** join/#htc-linux dullard (n=jim@adsl-static-1-30.uklinux.net)
08:12.17*** join/#htc-linux Fossi (n=cmewes@195.177.48.115)
10:56.58lkclspeedy2: que? there's a lot needs to be done before that: making a call from wince and tracing the gpio; getting the sound chip to work etc.
11:04.37cr2lkcl: hi. so it's crc16. have you extracted nk.exe ?
11:04.46lkclallo cr2.
11:04.56lkclno cos i can't decode the nbf
11:05.07cr2hmm. ask itsme
11:05.25cr2there is some 'nbh' format.
11:06.02cr2i'm not sure you need the sound chip for the phone.
11:06.27lkclwell i need it to know when a call is coming in but at least we know that vibrate works and that i suppose would do
11:06.42cr2the phone speaker on the universal is under the BB control, says goxboxlive
11:08.05lkclooo
11:09.17cr2curious about the mic. if it is controlled by gpio-only, or also with AT command.
11:11.18lkclwell - i think i have to go set up my other laptop, cos i am out of space on this one to set up openembedded.org
11:12.44cr2hehe.
11:13.58cr2i have a TI BT binary protocol, it is similar to what you have on the phone. binary structured commands mixed with AT commands.
11:14.43lkclo joy.  that makes four separate protocols.
11:28.23cr2lkcl: have your tried alpinenbfdecode.pl on your nbf ?
11:31.52lkclthe alpine one, no.
11:32.07lkcloh.  yes. i  have.
11:32.12lkclsorry got name wrong.
11:32.32lkclneed a password.  top 300 or so bytes are garbage.  it's a WM 5 rom
11:56.25lkclok.  touchscreen.
12:20.00*** join/#htc-linux WizMaui_ (n=WizMaui@62.112.90.179)
12:22.42*** join/#htc-linux psokolovsky_ (n=psokolov@239.usernat.ip.net.ua)
13:23.45*** join/#htc-linux JTRipper (n=jtripper@p54B1F778.dip.t-dialin.net)
13:52.34*** join/#htc-linux vitb (n=vitb@85.21.88.2)
14:25.24vitbhi guys! anyone around to clarify some ba progress details?
14:38.35*** join/#htc-linux psokolovsky (n=psokolov@239.usernat.ip.net.ua)
14:38.56*** join/#htc-linux pH5 (n=ph5@e178233172.adsl.alicedsl.de)
15:12.31lkclbtw whats procedure for mapping keys?
15:12.48*** part/#htc-linux Kevin2 (n=Kevin@207-237-52-30.c3-0.avec-ubr12.nyr-avec.ny.cable.rcn.com)
15:14.22lkclvitb: bluangelprogress page on xda wiki
15:14.34vitblkcl: I saw it
15:14.51vitbwondering what sound thing is misbehaving
15:15.51vitbpondering to buy BA device guessing it could be usable with linux as for now
15:15.56lkclredesign of pxa alsa soc code is a mess
15:16.03lkclbeen useable for a year
15:16.53vitbbut headset is no-way, right?
15:18.14cr2vitb: needs some work, probably.
15:18.47vitbbasically I see it is OK for GSM calls + SMS + some music + gprs
15:20.13cr2i heard that gprs works with some tricks. because you need first to connect, send some AT commands, and then connect pppd to /dev/ttyS8.
15:20.50cr2is certainly broken in the current hh.org CVS. worked with xadanux.sf.net .12 kernel.
15:21.55vitbcr2: hmm, ba progress page says gprs is nearly quite happy on  this gadget
15:22.23cr2yes, with .12 kernel
15:22.26vitbassuming all the preparation and pppd invoke by hand, heh
15:23.54vitbcr2: and, erm, what's wrong with ts driver - too much responsive?
15:24.13vitbwiki says needs debounce
15:26.02cr2vitb: didn't use BA for a long time, but it was ok for me before.
15:26.48vitbok, thanks.
15:29.00cr2it's a good phone for linux. just needs some minor work.
15:34.32cr2:)
15:35.42*** join/#htc-linux booba (n=booba@AAnnecy-256-1-60-138.w90-10.abo.wanadoo.fr)
15:38.16WizMaui_isn't mvista thta company who developed a bit around the omap platform ?
15:39.54cr2WizMaui_: mvista developed a lot of linux stuff.
16:45.11*** part/#htc-linux centrino (n=centrino@linux.fjfi.cvut.cz)
16:57.04*** join/#htc-linux ivor_ (n=ivor@kde/developer/ivor)
17:05.34*** join/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com)
17:50.39*** part/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com)
18:10.36cr2ba friends here ?
18:25.30*** join/#htc-linux pleemans (n=peter@d51A5E421.access.telenet.be)
18:36.11vitbWizMaui_: actually yes, there are plenty of stuff developed here, and Mot linux platform kernel part too for instance. But we have almost none of 'private' bits, all submitted & merged to the stock kernel unless it was done under NDA as in Mot case.
18:39.25*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
19:07.18*** join/#htc-linux FossiFoo (n=Fossi@e176122008.adsl.alicedsl.de)
19:35.54cr2hmm. at seems i have found a bug in the blueangel_audio. maybe that's the reason it did not want to work without pushing from wince.
19:36.35goxboxliveok
19:37.45goxboxlivecr2: IN Opie-console i have found a dialpad that use AT commands (for using a modem). Shouldnt it be a way to rewrite it so it would implement some of our AT commands?
19:46.47cr2we can, because universal does not use strange binary protocol.
19:47.11cr2but we need an integrated solution. for this and other problems.
19:49.19goxboxliveok
19:56.55psokolovskyHi!
19:56.59psokolovskyOk, so I assume noone objects to my asic3_base cleanup patch?
20:00.10*** join/#htc-linux kung (n=kung@dslb-084-058-217-010.pools.arcor-ip.net)
20:00.12kunghi
20:02.54cr2pskolovsky: the CLOCKS management is really fscked in asic3_base and many don't care because of that. so buggy drivers appear ...
20:03.36kungI'm considering to get an xda neo (which would equal an htc prophet) is there any experience with linux on this device?
20:07.22pH5kung: as I understand, it is similar to the wizard - did you see linwizard.sf.net?
20:07.34kungnot yet..
20:08.48kungwell the wizard got a keyboard, right?
20:09.00kungand the neo actually dosen't (dont know if that matters)
20:09.10FossiFookung: i have one
20:09.32pH5FossiFoo: does linux run on it?
20:09.34kungwizzard? or neo?
20:09.42FossiFookernel boots, i'll try to get the touchscreen running this weekend
20:09.42cr2if it's omap850, you'll have hard time.
20:09.46vitbkung: linux boots on that box but that's all for now
20:09.48FossiFooneo
20:09.53FossiFooie prophet
20:10.11FossiFoocr2: because?
20:10.15kungwell I wouldn't need the telephone funciton, if thats the entire problem
20:10.29kungI just have zero experience with embedded devices...
20:10.43kungcr2 it is
20:10.45cr2FossiFoo: to get the phone running.
20:11.41pierroxlkcl: i made some progress on the g500
20:12.30pierroxlkcl: when i try to use the spi bus, the screen get a red tint :-) funny
20:12.36vitbcr2: oh, forgot to ask - does himalaya support phone calls or only BA is blessed for now?
20:12.58psokolovskycr2, let's fix those clocks issues ;-)
20:14.14pH5cr2: is there something that could be used as a template that has better clock handling? like asic2/samcop?
20:14.55FossiFoocr2: yes, but why?
20:15.36FossiFooand yeah, the phone isn't really a priority for me either
20:15.50FossiFooas long as i can boot wince once in a while to check my mailbox
20:16.03FossiFoobut touchscreen would be nice ;)
20:16.59vitbFossiFoo: because phone stuff is controlled by DSP which needs stuff to be loaded with afaik
20:18.15vitblinux on 850 without phone is doable, phone functionality - nothing is impossible but I'd call it sci-fi unless TI would release something to public
20:20.08lkclpierrox: oooo :)
20:22.28lkclvitb: cr2 and i discovered that the himalaya has the same sound chip as the BA.  so, i tried to get sound to work: i had limited success, but it was over a year ago.
20:22.38lkclgomunicator at least ran and accepted incoming calls etc.
20:24.18vitblkcl: so gsm calls are OK but headset/speakers might require some alsa surgery, right?
20:26.21cr2vitb: himalaya is "small" blueangel (without wifi). the support is even worse that of blueangel.
20:26.49lkclvitb: yep
20:26.51cr2pH5: the hx4700_pcmcia is definitely broken.
20:27.00lkclno it ain't, cr2!  i love my himalaya
20:27.59cr2psokolovsky: the blueangel_bl is seriously wrong, the asic3_pwm needs much more initialization.
20:28.15lkclhttp://en.wikipedia.org/wiki/Embedded_Linux
20:28.29lkcllet me edit it, let me edit it pleeeeease
20:28.50psokolovskycr2, that's to asylumed, I guess
20:29.07cr2ok.
20:29.13psokolovskycr2, but I guess it works if booted from HaRET, hw must have tested it
20:29.15cr2about the clocks: http://wiki.xda-developers.com/index.php?pagename=ASIC3
20:29.31cr2there are six devices fighting for EX1 clock, for example
20:29.56cr2how it is supposed to be suspended ?
20:31.08cr2psokolovsky: it works, only because wince has properly setup the pwm. boot without wince, and the device will be dead. happily, these registers seem to survive the suspend. SL-A300 (mis)uses that fact ;)
20:32.00psokolovskycr2, heh. you know, we likely have such issue (dependence of wince as bootloader) for quite a number of devices. h4000 is one to start with ;-F
20:32.10cr2lkcl: we will certainly support himalaya, even just to show the middle finger :D but after the ba .
20:32.31psokolovskycr2, but well, what to say, if in some htc phones's code asic3 device is called h3900_asic3? ;-)
20:32.51cr2psokolovsky: himalaya can wait ;)
20:32.57psokolovsky;-)
20:33.16cr2i'll correct some issues in blueangel.
20:33.17psokolovskycr2: So, I agree, we need to do full and proper setup
20:33.54cr2the *_pcmcia, where * is h4700 & h4000 is completely wrong. i'm surprised it works after suspend.
20:34.08psokolovskycr2, caveat: for many not very finished ports, complete reset of chips setup on linux load would mean no sound, no BT, no WiFi, etc. that's why it is that way now...
20:34.28cr2the blueangel copies the hx4700, and is broken too.
20:34.34psokolovskycr2, I can't pledge h4000's works after suspend ;-)
20:35.10psokolovskycr2, it's nice that you caught that issue, but yes, we need to start with tetsing any fixes on hx4700, I guess
20:35.29psokolovskyand I personally don't even have CF card in the house ;-(
20:35.35cr2i have looked at the pcmcia.dll from blueangel, the CF_SLEEP and CDEX_* things are a bit different than in hx4700 code. but hx4700 code is not correct too.
20:35.43psokolovskygot rid of all of them when baught h4000 ;-)
20:36.03cr2can you check hx4700 with corrected asic3 CDEX bits ?
20:36.20psokolovskynothing to check with so far ;-)
20:36.34psokolovskywill try to pick up some CF card soon (== within 2 weeks)
20:36.35cr2i've posted the patch to the kernel list.
20:36.49cr2well, not the patch, but you get the idea.
20:36.55psokolovskyotherwise, need to ask bd2, pH5 and other folks
20:37.03psokolovskycr2: yes, I saw, thanks!
20:37.05cr2PCMCIA is used by wifi ?
20:37.11cr2on hx4700
20:37.18cr2and on blueangel it seems.
20:37.24lkclhimalaya, blueangel, hw6915, universal - those are the major ones
20:37.28cr2and i think on some axim too.
20:40.21cr2btw, axim x30 does not have asic3, but this port seems to be abandoned now.
20:41.58psokolovskycr2, on hx4700 - no, wifi is at CS. so, only for CF
20:42.26psokolovskycr2: maybe abandoned, need to find some guy with it ;-)
20:42.40cr2pH5: you are an expert on clean drivers :) how do we fix the monster named hx4700_power ?
20:43.09pH5ahhh
20:43.48cr2psokolovsky: ok. but we need some refcounting on CDEX clocks. RSN.
20:43.59pH5we need to adapt the soon-to-be common ds1wm driver
20:44.02psokolovskycr2, go for it! ;-)
20:44.05cr2pH5: i don't have much experience myself.
20:44.24cr2pH5: clocks/gpios, reset ?
20:44.35cr2it is all asic3-specific.
20:44.50cr2the ds1wm driver is really good, that's true.
20:45.26cr2psokolovsky: trying to concentrate on the areas where i know better ;)
20:45.36pH5the ds1wm driver could use some error handling, but it's much better than the hx4700_power monolith
20:46.13pH5I'm already using it on the magician, too - I only need to connect it to the battery sysfs class.
20:46.23cr2hx4700_power is awful :) it's comparable to the original zaurus source.
20:47.12pH5there are two hooks for turning on/off the ds1wm clock in the driver that would  have to be filled with the asic3 specific parts
20:49.17psokolovskycr2, Ok ;-). But I have to say that I don't know about code patterns for clock control either. Matt Reimer mentions such stuff again and again too, I guess would need to chekc with him on ideas.
20:49.37psokolovskypH5, Could you adapt ds1wm to hx4700 also?
20:50.03psokolovskycr2, so well, let's have asic3 clock ctrl in "common queue" for now
20:50.38lkclhttp://en.wikipedia.org/wiki/Embedded_Linux#Wince_Mobiles_that_have_been_hacked_into_submission_to_run_Linux
20:52.17pH5psokolovsky: I'm going to try, although I didn't touch anything asic3 yet.
20:52.41cr2lkcl: now we need a full hw support on them
20:52.46lkcl.he
20:53.18psokolovskypH5, at least you're the one who knows most of w1 among us here, I guess ;-)
20:53.19cr2pH5: the hx4700_power does everything like wince is doing it. i've checked, the hw control stuff is correct.
20:53.56pH5psokolovsky: yeah, but the w1 part is already done correctly by mreimer ;)
20:54.07pH5cr2: ok, that's good to know
20:54.27psokolovskypH5, so you know what to expect from it hwen it runs correct/incorrect at least ;-P
20:54.33pH5true
20:54.56cr2psokolovsky: i think that exporting the "raw" clock access from asic3_base is not very good in general, the drivers should not be able just to shutdown the clock in their suspend code.
20:55.26pH5cr2: how about some refcounting?
20:55.30cr2pH5: it even supports the undocumented 1<<6 clock.
20:55.42cr2pH5: per driver ?
20:58.31cr2hmm. 1<<6 is an EXTCF bit. why didn't they simply publish the datasheet ;)
20:58.38pH5something like this.
20:58.50pH5from reading linux/clk.h, it looks like clk_enable/disable do that already
20:59.18cr2looking.
21:01.11cr2implemented only for omap and sh ?
21:02.04pH5arch/arm/mach-pxa/clock.c
21:02.30pH5clk->enabled is a reference counter
21:02.35cr2heh. i was in include/
21:02.40cr2ok.
21:04.04pH5the hh.org tree has some changes here that are not in mainline (yet?)
21:04.05pH5http://en.pastebin.ca/251175
21:04.57cr2yes, the code is there, but not in include/
21:06.08cr2gpio27 ? i thought it is relevant only on sa11x0 ?
21:07.42cr2*  linux/arch/arm/mach-sa1100/clock.c
21:07.52cr2the origin of the file.
21:09.15pH5cr2: you think it was a copy&paste job?
21:09.46cr2at least partially.
21:10.13cr2do we have a pxa27x RTC driver ?
21:10.41cr2afaik, there is still no support for lccr4/lccr5 in pxafb.
21:11.00cr2and we  need them on universal and sable.
21:11.02cr2hmm.
21:11.04pH5we use the sa rtc driver
21:11.11pH5what about lccr4/5?
21:11.38cr2"double" bit in lccr4
21:11.43*** join/#htc-linux RoEn_PC (n=roen@p54A671E3.dip.t-dialin.net)
21:12.02cr2is used on these two phones.
21:12.06lkclpierrox: are ya dead, dude?
21:12.23lkcli need to know if you know the chipset used in the Eten g500
21:12.25lkclfor GPS
21:12.35cr2pH5: pxa27x has much more advanced rtc than sa ;)
21:12.47lkclah got it - SiRF III
21:12.51cr2lkcl: sirf3 ?
21:12.58cr2ok.
21:12.59lkclyeh SiRF Star III
21:13.22pH5cr2: I had no idea.
21:13.26cr2they intentionally fscked the firmware (sic!)
21:14.07cr2lkcl: sirf does not use spi ;)
21:14.11lkclgooood
21:14.37cr2lkcl: we should write an asic3_spi driver.
21:15.01lkclcr2: i wrote an ssp driver - it got lost.
21:15.02cr2then you can just send the 0xc0 command in linux, and grab the response :)
21:15.21cr2lkcl: look at...
21:15.50cr2drivers/spi/pxa2xx_spi.c
21:16.06kungif I would try linux on an xda neo would it be possible to restore windoze, if linux fails?
21:16.29cr2kung: flashing linux is only supported on some ipaqs.
21:16.35pH5kung: as long as you start it with haret, just reset and wince is back
21:16.43cr2there you have a chance to brick the device.
21:17.35kunghmm, guess I'll get such a pda (since I can't afford another one)...;)
21:17.41kungand then I'll just try
21:18.09cr2kung: used blueangel is the best friend of a linux hacker.
21:19.43kungthe thing is I cant get that one..I' can afford an xda neo, since I'd finance it over 2 years by my mobile phone contract..;)
21:20.04kungit only got a crappy 200MHz cpu, but at least it got wlan and an sdio slot.:)
21:20.13cr2kung: i did it with all my "linux" phones :)
21:20.22*** join/#htc-linux RoEn_PC (n=roen@p54A671E3.dip.t-dialin.net)
21:20.29cr2sdio is not supported in linux.
21:20.47kungdamn
21:20.50lkclsdio is _sort_ of supported - grudgingly.  a little bit.
21:20.54lkclreally slowly.
21:20.56cr2it should be easy to support it with asic3
21:20.58lkclwith no encryption.
21:21.06cr2but it's the device drivers that are the problem.
21:21.10lkclyes.
21:21.18cr2it's like pcmcia.
21:21.39cr2lkcl: encryption ?
21:22.04cr2i have a sdio gps, it should be easy to support in linux, imho.
21:22.32lkclyes - the sdio specification includes some sort of encryption.  you can't get the specification unless you sign your life away.
21:22.32lkclprobably is.
21:22.32kungsince that would be my first pda I have no experience so far with these types of devices.
21:22.46cr2lkcl: not sdio, but sd. just don't use these commands.
21:22.57lkcloh.  right.
21:23.58cr2sdio is not documented (openly) too, but we have 'wi', thanks to Kevin2 :D
21:24.39cr2and cpq documented the sdio controller register layout for us.
21:27.53lkclyehhhh!
21:28.09cr2lkcl: you got the crc16 working, can you dial now ?
21:28.34pH5lkcl: just find that damn acx memory address
21:28.35lkclcr2: yes i have the crc16, no - i'm writing up my article because it's been a week now already.
21:28.55cr2lkcl: it's a problem on ba too.
21:28.56cr2ok.
21:29.13lkclhttp://hands.com/~lkcl/linux.phones.html - review appreciated!
21:29.43cr2lkcl: does greenphone have a cam ?
21:29.56lkclyep
21:30.02cr2gps ? umts ?
21:30.09cr2wifi ?
21:31.16lkclno, no and no
21:31.26cr2ok.
21:31.29lkclit's a commodity-level phone, with reduced-cost hardware inside
21:31.41lkclabout the only thing that _isn't_ commodity-level is the touchscreen.
21:31.57cr2is the kernel source available ?
21:31.58lkcleverything else is exactly what you could expect on a high street phone
21:32.06lkclyes, probably.  i haven't opened the cd yet.
21:32.20lkclgo away i want to do what ph5 tells me!
21:32.24cr2then open. i'm interested in the cam api.
21:32.29cr2<PROTECTED>
21:35.18*** join/#htc-linux NickBee (i=HydraIRC@221.134.52.117)
21:36.06cr2<PROTECTED>
21:36.19cr2unlike the 2.6.18 it worked.
21:37.08cr2<PROTECTED>
21:37.27cr2do you really need it ? i can look.
21:37.58cr2>(easily done with i2cdetect)
21:38.07cr2if the chip is powered up
21:38.41NickBeeHi Cr2
21:40.00NickBeeCongratulations, I see that the GSM status has gone Green
21:40.06NickBeeon Universal
21:40.56ljpmost of greenphones kernel sources will be available
21:41.11cr2ljp: cam api ?
21:41.17ljpopen
21:41.42cr2hmm. can lkcl just open his cd ?
21:41.46ljponly things not open are DOC and modem
21:41.59cr2ljp: DOC is g3/g4 ?
21:42.00ljpkernel sources are not available yet
21:42.07ljp3
21:42.15pH5ok, lkcl, you may do what you want now ;)
21:42.16cr2heh. i'm working on it.
21:43.00lkcli'm a little bit tied up dealing with koen on #openezx - apparently he's pretty pissed about the 2nd draft of my linux phones article
21:43.23cr2http://wiki.xda-developers.com/index.php?pagename=HTC_DiskOnChip
21:44.40ljplinux phones article?
21:45.29cr2lkcl: i'll leave this kernel vs. userspace stuff aside, but openezx produced not very much for a project that had access to the full motorola source code.
21:45.37cr2compared to what we have done.
21:47.52cr2now they moved to openmoko, and praise closed-source gps library for something gpstk will do, and the same TI phone we have on BA/hima/magician ?
21:52.15cr2NickBee: but not UMTS .
21:52.37NickBeeI am sure you guys will crack it as well
21:52.45NickBeebut can you use phone without the sounds?
21:53.10cr2NickBee: i mean the data channel.
21:53.20cr2videophone & internet.
21:53.35NickBeeOk
21:53.40lkclcr2: haralde's working for FIC - he's doing a decent job, instead.
21:53.47lkclmotorola made a bit of a pig's ear.
21:55.03cr2ok. but i will prefer the source code over press releases ;)
21:56.03ljpkoen has a problem with lots of things
21:56.13cr2;)
21:56.59cr2motorola has not published only the doc g3 code. the pxa-mmc code was not really necessary.
21:57.23cr2the mux_cli is also not your friend, obviously .
21:58.45cr2i think the g3 raw read access will be relatively easy. once we will have raw write access, the whole g3 issue will go away.
21:59.21goxboxliveljp will there be a phone app for opie?
21:59.42ljpi hope so.
22:00.03goxboxlivebut for opie 2 or opie 1.2.x?
22:00.21ljpopie 2 most likely, as no one is really working on opie 2
22:00.25ljperr opie1
22:00.46cr2goxboxlive: i wish it's plain qt.
22:00.54cr2ljp: you mean 1.2
22:01.01ljpya. current opie
22:01.05cr2ok.
22:01.10goxboxlivecr2: i dont care as long i can use it with opie
22:01.38cr2i prefer debugging on a amd64 machine.
22:02.29goxboxliveok
22:03.37cr2it's a pity florian has no time. it is possible to strip down 'itsutils' doc code, and trace it with 'wi'.
22:04.29cr2we are missing the wince audio access lib, and a way to tap into the UMTS serial port now, to finish with the universal.
22:07.07lkclhttp://www.handhelds.org/hypermail/kernel-discuss/19/1961.html
22:08.15*** join/#htc-linux florian_ (n=fuchs@84.245.185.102)
22:09.52florianre
22:09.57cr2lkcl: i have read it, but it's not enough.
22:11.06cr2we need video, audio, usb and uart multiplexing on universal.
22:15.32cr2ljp: forgive me my ignorance about the greenphone, which bluetooth chipset is it using, and is there a bt headset support ?
22:21.08*** join/#htc-linux scatterp (n=deminish@212.32.67.196)
22:23.57lkclcr2: what isn't enough, dude?
22:28.10cr2lkcl: hix mux_cli driver.
22:28.20cr2s/hix/his/
22:28.27*** join/#htc-linux FossiFoo (n=Fossi@e176122008.adsl.alicedsl.de)
22:28.45lkclah right
22:29.51cr2lkcl: do you know the bt chipsets in greenphone and openmoko ?
22:29.59lkcl<PROTECTED>
22:30.42*** join/#htc-linux willwork4foo (n=bjdemora@82-33-99-181.cable.ubr10.azte.blueyonder.co.uk)
22:30.48cr2greenphone has bcm2121 as the baseband, that's something new for us.
22:31.23willwork4foohiya - has xda-developers gone down or something? I can still get to the ftp server, but I get nothing from http
22:31.41cr2lkcl: your article is a book. it can't be read at once.
22:32.23cr2willwork4foo: works for me.
22:32.49willwork4foocr2: dammit. Why can't I get that site here then
22:32.56lkclyeh ziffdavis _did_ suggest splitting it into 3 articles
22:33.03willwork4fooyou can get to forum.xda-developers.com
22:33.40willwork4fooit times out for me
22:33.47*** join/#htc-linux markit (n=konversa@host119-245-static.72-81-b.business.telecomitalia.it)
22:34.24cr2willwork4foo: change the provider ;)
22:35.01willwork4foo??
22:35.11willwork4foochange provider - as in - change ISP?
22:35.17cr2yes.
22:35.33*** join/#htc-linux RoEn_PC (n=roen@p54A671E3.dip.t-dialin.net)
22:35.46cr2i have 2.5MByte link to the site.
22:36.10willwork4foothat doesn't do it either. I couldn't access it from work's internet connection either. (I remote desktopped onto my work machine and tried from there)
22:36.17willwork4foothey use a different ISP, in a different area
22:36.21willwork4fooexactly the same result
22:37.10cr2<PROTECTED>
22:37.14cr2<PROTECTED>
22:37.18cr2<PROTECTED>
22:37.23cr2<PROTECTED>
22:37.23cr210  asd2-rou-1001.NL.eurorings.net (134.222.231.194)  17.228 ms   17.649 ms   17.636 ms
22:37.23cr211  134.222.231.250 (134.222.231.250)  17.774 ms   17.755 ms   17.663 ms
22:37.23cr212  134.222.97.18 (134.222.97.18)  17.553 ms   17.694 ms   17.479 ms
22:37.23cr213  0.so-2-0-0.cr1.3d12.xs4all.net (194.109.5.74)  18.325 ms   17.978 ms   17.829 ms
22:37.35cr2DE->NL link works.
22:37.40willwork4fooI can ping
22:37.45willwork4fooping works fine for me
22:38.04cr2then somebody filters http
22:38.13pofwhois willwork4foo
22:38.19pofoops :P
22:38.28willwork4foocr2: what on earth are you talking about
22:39.07willwork4foopof: hi
22:39.47cr2if you can't access the site over http, and i can...
22:39.58pofwillwork4foo: i was checking your IP address to see if it's in xda-dev ban list
22:40.01pofbut it's not
22:40.03cr2then your link is filtered. logical ?
22:40.22pofrecently we've been banning some ip addresses because of spam
22:40.29willwork4foocr2: not really. it's not just *my* link. I can't access it from my work IP either.
22:40.44willwork4foowhich is on a totally different ISP
22:41.09willwork4fooand I was accessing the site from that same IP earlier today- then it stopped working. I come home, and I can't access it from home either
22:41.10cr2maybe xs4all.net filters you, i don't know.
22:41.22willwork4foocr2: both my home and work IP addresses?
22:41.29willwork4fooat the same time?
22:41.38willwork4fooI am thinking that is fairly unlikely
22:41.41pofweird... try livehttp headers to see if you get any answer from the server
22:41.44cr2why not ? but afaik xs4all is not known for filtering.
22:41.55willwork4foopof: ???
22:42.10*** join/#htc-linux Stephmw (n=steph@212.69.51.139)
22:42.14Stephmwhowdy
22:42.23pofwillwork4foo: this are the blocked IP addresses in xda-dev firewall:
22:42.24pof82.205.243.46
22:42.24pof83.229.92.5
22:42.24pof196.3.63.252
22:42.24pof196.47.90.18
22:42.24pof212.247.71.34
22:42.26pof216.139.164.85
22:42.28pof85.144.155.124
22:43.00willwork4foopof: none of those are mine. Neither are any of those my work's IP addresss
22:43.37willwork4foothis is absurd. I should be able to access the forum at http://forum.xda-developers.com shouldn't I?
22:43.45willwork4fooI can get to the FTP server
22:43.47willwork4foono problems
22:45.03willwork4foopof: any idea what might be causing this?
22:45.24poftry telneting to forum.xda-developers.com:80
22:45.57pofthen type GET / HTTP/1.0
22:46.05pofand two CR+LF
22:46.27willwork4fooI get nothing
22:47.21willwork4fooI get "Trying 82.94.251.230..." and that's it
22:47.22*** join/#htc-linux rejon (n=rejon@adsl-75-5-124-98.dsl.pltn13.sbcglobal.net)
22:47.26willwork4foono connection
22:47.33*** part/#htc-linux rejon (n=rejon@adsl-75-5-124-98.dsl.pltn13.sbcglobal.net)
22:48.01willwork4foointerestingly enough, I just got a friend of mine in London to try the site (around 180 miles away from me here in Bristol), and it times out on him too
22:48.03FossiFoobut you can ping it? that's weird
22:48.08willwork4fooso it's NOT JUST ME!
22:49.22*** part/#htc-linux Stephmw (n=steph@212.69.51.139)
22:49.32cr2willwork4foo: then the uk is blocked. ask lkcl to try.
22:49.40FossiFooi asked a uk guy
22:49.46willwork4fooI can ping it, I can access the FTP - but anything to do with the web site doesn't work
22:50.06FossiFoohe's on btcentralplus and it works for him
22:50.25FossiFoosec
22:50.26willwork4fooI've just got four of my UK mates to try - one in Manchester, one in London, one in Cornwall, and another in Bristol - it times out for ALL of them
22:50.27FossiFoomessup
22:51.19FossiFoook, works for him
22:51.29willwork4foolucky him
22:51.47cr2yes, it times out from lkcl's machine.
22:51.47willwork4fooobviously there is a problem here somewhere along the line with the website.
22:53.12FossiFoofunny that it works for my friend :)
22:53.29willwork4fooFossiFoo: your friend must be very special.
22:53.29cr2it's bt conspiracy :)
22:53.40willwork4fooit's timing out across the rest of the UK for everyone else I know.
22:53.48FossiFoohe's on BT, what do you use?
22:54.23willwork4fooI've got Telewest Cable internet here. My friend in London is on Wanadoo, and I don't know what ISP other guys are on
22:55.24willwork4foowork uses a business ISB
22:55.25willwork4fooISP
22:55.40willwork4fooand I can't access the site from there either
22:56.06willwork4foocr2: so - do we accept that there might be a problem with the website?
22:56.15willwork4fooor is it still a problem "at my end"
22:57.30FossiFoomaybe try some other xs4all sites?
22:57.54willwork4fooxs4all?
22:57.59cr2willwork4foo: it's an ISP-level problem.
22:58.14cr2somebody drops port 80 packets.
22:58.26*** join/#htc-linux Ro_En_PC (n=roen@p54A66EC5.dip.t-dialin.net)
22:58.31FossiFoowww.xs4all.nl
22:58.50willwork4foocr2: ISP-level? across MULTIPLE ISPs?
22:58.56willwork4foosimultaneously?
22:59.32willwork4fooFossiFoo: I can get to that site
23:00.15willwork4foodoes anyone here actually have admin access to the xda-dev site?
23:00.52willwork4footo the extent that they can have a look to see what's going on - or is it just going to be left from now on that most of the UK cannot access xda-dev on the web
23:01.50FossiFoowillwork4foo: well, if it's an isp/net problem there's not much that people can do
23:01.59FossiFooif they can, i guess they'll try now
23:01.59willwork4fooif
23:06.45*** join/#htc-linux Kevin2 (n=Kevin@207-237-52-30.c3-0.avec-ubr12.nyr-avec.ny.cable.rcn.com)
23:07.00goxboxlivecr2: Are getting closer at solution to have working sound?
23:09.04cr2goxboxlive: not really.
23:09.16goxboxlivei c
23:09.30goxboxlivedidnt the lm_sensor apps helped you either?
23:11.03*** join/#htc-linux TripleDES (n=sergio@84.77.161.251)
23:20.06lkclcr2: 0xab00 0000 _does_ look suspiciously like the acx100 address...
23:20.25lkclab000730 | 00000000 0000c524 00000000 00000000 | ....$...........
23:20.25lkclab000740 | 00000000 00000098 000053fe 000053fe | .........S...S..
23:20.25lkclab000750 | 00000000 0000c4ac 2d001400 00000000 | ...........-....
23:20.25lkclab000760 | 00000000 0000007c 00000000 00000000 | ....|...........
23:20.25lkclab000770 | 00000000 0000c524 00000000 00000000 | ....$...........
23:21.16lkclok now i gotta try wireless off... hum... mmm....
23:21.42cr2they should be at 2 certain offsets
23:21.54cr2your data looks strange.
23:22.07cr2i'll look at your old dumps for universal.
23:23.31lkclok.
23:25.38lkclhttp://hands.com/~lkcl/hp6915/wireless.memdump.off.txt
23:27.08cr2http://hands.com/~lkcl/universal/typescript.15jan2006.pd.txt
23:27.14lkcl<PROTECTED>
23:27.17cr2looks familiar :)
23:27.18*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
23:28.34lkclok xxxx it let's just try it.
23:29.20cr2yeah. the same address as on universal.
23:29.44lkclhuh.  how do you set that address?
23:29.51cr2where ?
23:30.12cr2include/asm/arch-pxa/htcuniversal-gpio.h
23:30.17lkclahh.
23:30.36lkclahh - htcuniversal_acx.c in drivers/net/wireless
23:30.54cr2#define HTCUNIVERSAL_EGPIO_BASE PXA_CS2_PHYS+0x02000000
23:31.08cr2hmm.
23:31.12cr2ok.
23:33.04lkcljoy.  now gotta do an asic3 thingy whilst _not_ connected via wireless....
23:33.44cr2it should log to the screen ?
23:33.53lkclargh i gotta remove some of these startN.txt files
23:34.04lkclis there a log-to-file version of wasic3?
23:34.10cr2no.
23:34.13lkclit's a pretty small screen
23:34.26cr2hmm. true. i always think universal.
23:34.31lkclhuh.  that's a bit weird.
23:34.42lkcl:)
23:35.08lkclok, only 5 gpios to find, anyway :)
23:35.29lkclplus one irq.  shouldn't be too hard.
23:35.46*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
23:35.48cr2try to stop wifi while running. you'll see the rest on the screen.
23:36.06cr2i think there was a command for that...
23:36.14cr2no. i commented it out.
23:39.21goxboxliveis the htcsable nearly at our status now?
23:40.29cr2yes, the hardware is very similar, and lkcl found out the phone protocol.
23:41.02goxboxliveok, do he gps working to?
23:41.03cr2many gpios are at the same place, and the wince memory address spaces are the same.
23:41.09lkcld3, c8 and b5 so far
23:41.11cr2no :)
23:41.24lkclgps - well i _could_ talk to the gps, if i tried.
23:41.28cr2it will be the most fun to make it owrk.
23:41.42lkcland then gnuharet crashed.
23:41.55goxboxliveok
23:42.36cr2goxboxlive: we will get some binary data from gps, and it will be necessary to convert it into the coordinates.
23:42.43lkclhmmm can you get an ethernet connection over bluetooth using wince?
23:42.55cr2if we will succeed, it will piss off a _lot_ of people.
23:43.06cr2lkcl: yes.
23:43.12cr2bnep
23:43.13goxboxlive:)
23:43.15lkclb15 c8 d3
23:44.04cr2wifi irq is FE
23:44.27goxboxlivelkcl BT ethernet is not an option in wm5
23:45.19cr2goxboxlive: ?
23:45.36cr2somebody told me he has connected to haret.
23:45.56cr2imho, it was not an option in wince2003
23:45.59lkclo bugger.
23:46.02cr2ah.
23:46.21cr2not bnep, but serial-over-bluetooth.
23:46.40lkclok what else.  so b15 c8 and d3 i now know about: so i remove them with set ii
23:46.53goxboxliveok, then it has to be the new rom, or with the other bt stack (no ms)
23:47.17cr2lkcl: switch bt on, and do 'hcitool scan' on the notebook.
23:47.35cr2write down the btaddr
23:47.39lkclnaaah - this is more fun, the hard way.
23:48.00cr2keep in mind, that on my universal the _wince_ bt addr is different from _linux_ bt addr.
23:48.26goxboxlivethat is strange
23:48.56pofyes ... very weird
23:49.11pofhave u looked at the BDR from diagnostics image?
23:49.12cr2two upper bytes are different
23:49.27cr2the four lower are the same.
23:50.04cr2maybe it can be just overwriteen by a bts command, or just some BT ram messup :)
23:50.10lkclb15 d3 c8 b14
23:50.33cr2lkcl: reset should be called twice.
23:50.51lkclyeh i think i noticed that on the first run and missed it
23:51.09lkclcos gnuharet crashed
23:51.23cr2wjich one do you use ?
23:51.25lkclahh - there's a scrollbar in the gnuharet watch window
23:51.37cr2hehe.
23:51.40lkclcompiled it myself couple of weeks ago
23:51.44cr2ok.
23:52.26lkclnope - b15, d3, c8.
23:53.56lkclhuh. will keep trying...
23:54.07goxboxlivelkcl what are testing? BT or wifi?
23:54.24lkclwifi (acx).  got bt going (really easy) a week ago
23:54.35goxboxliveok
23:55.06goxboxlivei a, using the acx now, with opie-irc :)
23:55.11lkclyaay! :)
23:55.29lkclthat was really funny when rob_w did that over bluetooth from the himalaya
23:55.44lkclahh is that where you get the [stupid] word-completion feature from?
23:55.54goxboxliveyes i guess
23:56.17cr2lkcl: i see gpiob and gpioc refs in your (broken) pcmcia.dll
23:56.36lkclno wonder so many people on these lists complain about word-completion: they're daft enough to use what they work on :)
23:56.53lkcli am delighted to hear that, cr2.  hooray.
23:57.29cr2gpioc : 0x100
23:57.38cr2it's probably the reset.
23:57.55lkcl0x100 -> c8
23:58.21lkclhmm, you reckon there's only two power-pins and that c8 is the reset one?
23:58.25cr2yes. it's the reset.
23:58.40cr2wait, not so fast.
23:58.45lkclhe he
23:58.53lkcl_what_? :)
23:59.11cr2sleep 0x64 in between
23:59.29lkclyes - i saw that - from the thingy.  htc_universal_acx.c
23:59.34cr2sleep 0x32 after reset
23:59.45cr2no. it's your sable.

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.