irclog2html for #htc-linux on 20061123

00:05.15Kevin2cr2: The jornada haret cvs doesn't seem to do anything special with DMA in its linboot code.
00:06.06cr2yes, but it's not right ;) i did not boot with this code.
00:08.48cr2the kernel was hacked to be relocated above OHCI (at RAM+2MB) and then disabled OHCI and DMA in jornada820.c
00:08.51cr2ugly ;)
00:08.56Kevin2Oh.  Well, adding support for mainline should be pretty easy.  Just add a new machine class that sets OEMInfo[0] and PlatformType to the values you cite above in its constructor.  Then add in the necessary preHardwareShutdown and hardwareShutdown methods.
00:09.15cr2true.
00:10.07Kevin2As for the relocate stuff - can't you just add 2MBs to the memphysaddr variable?
00:10.45cr2Kevin2: if haret will disable the OHCI, there will be no reason to do nonstandard things.
00:12.36lkclcr2: do you think there could be more ASIC3 GPIO pins involved, with sound?  or more GPIO pins?
00:12.39lkcli mean, there aren't that many ASIC3 GPIO outputs _left_ :)
00:13.35cr2lkcl: maybe pxa GPIO
00:13.37Kevin2Okay.  If you get around to it, email me a patch with your support.  You should be able to checkout mainline and build it with egcc.  Building egcc should be pretty straight forward also (see the INSTALL file from haret).  Until we get cegcc fixed, you can change haret.cpp with the following patch:
00:13.39Kevin2+extern "C" void __gccmain();
00:13.39Kevin2+
00:13.39Kevin2<PROTECTED>
00:13.39Kevin2<PROTECTED>
00:13.40Kevin2<PROTECTED>
00:13.42Kevin2<PROTECTED>
00:13.43lkclD2, D7, D9, D13, C7, C11, C14, C15
00:13.44Kevin2+    __gccmain();
00:13.50Kevin2And then just add -e WinMain to LDFLAGS in the makefile.
00:14.06cr2Kevin2: ok.
00:15.35cr2lkcl: you should add the bitmask field to SableGPIO (like on universal)
00:15.54lkclGPIO 15, 20, 21, 57, 77, 99, 109, 114, 116, 119
00:15.59lkclwhat's that, dude?
00:17.01cr2http://wiki.xda-developers.com/index.php?pagename=UniversalGPIO
00:17.03lkcloops baby needs _more_ feeding!
00:17.05lkclok.
00:17.12lkclwill take a look
00:17.45lkclwhat am i looking at?
00:17.55lkcloh right.
00:18.01lkclthe 2nd column
00:19.23lkclok.  am gonna try something a bit drastic.
00:21.46lkcli'm gonna try em alll!
00:25.48cr2Kevin2: one more your advice needed. how can we trace the wince USB host communication endpoint ? i see it as the last stumbling block on the universal.
00:27.03Kevin2Heh, I liked your idea of loading a usb driver that snooped the traffic.  :-)
00:27.27Kevin2The problem with USB is that it is all dma.  So, we can't use the normal wi stuff.
00:27.55Kevin2However,  it should be possible to have the WI code trigger a snoop of the traffic.  I'd need to know the ohci spec more before commenting on how feasible this is.
00:28.26cr2i have looked at the snoopypro source, it's very intel-x86-specific
00:28.47Kevin2On a similar note, earlier today I started coding up some enhancements to wi.  I'd like the code to be able to do a "memory poll" on irq, trace, and breakpoint events.
00:29.21cr2there is something in the msdn on how you can put your own usb driver to grab data from usb host driver.
00:29.31cr2will you do the egpio too ?
00:30.11cr2yeah, it's the "memory poll".
00:30.22Kevin2This is useful for tracking down certain complex events.  For example, we could have a trace event on the serial port do a query of the gpio space.
00:30.52cr2yes.
00:31.07Kevin2egpio might fall out of that too. So, every irq event, I could poll the egpio registers and report them.
00:31.34cr2or check if they have changed.
00:31.39lkclok - how about this: if it's already 'on', then a gpio dump and asic3 dump will show up, on the 'unidentified' IOs, as 'on', right?
00:31.46cr2maybe better.
00:31.50lkcli know what i'm talking about
00:32.11Kevin2This might help with usb - if we knew where in memory the stuff was written to/from, we could have wi poll that memory on a usb trace event.
00:32.45Kevin2cr2: Right, each memory area would check for changes and would have a mask of bits to ignore.
00:32.47cr2Kevin2: on universal i know it. and the enpoint locations are also known.
00:33.08cr2try 'dump pxa27xusb'
00:33.45cr2you will see the apache ohci location
00:34.20cr2lkcl: i didn't get what you want.
00:34.34lkclcandidates are: A0, A1, B14, C15,
00:34.36lkclthat's it.
00:34.48lkclthat's all the 'unidentified' ASIC3 GPIOs that are 'on'.
00:35.00lkclcr2: it's like one of those logic games.
00:35.23lkclthe ak4641 codec and reset GPIOs are 'on' and we can't tell, in wince, what they are, right?
00:35.31lkcloh - unless in wince we can switch them off!
00:35.42Kevin2cr2: Cool.  But does it always dma out of the areas listed by the dump?  (That is, are you sure it doesn't dma to/from all over memory?)
00:35.43lkclis there a command in wince to switch off asic3 gpios?
00:36.11lkclif i flip those ones A0, A1, B14 and C15 off, and sound doesn't play, i know i've got the right ones.
00:36.14lkclright?
00:36.28*** join/#htc-linux hlbot (n=adm@82.67.76.179)
00:36.37lkclanyone know a haret command to flip GPIO / ASIC3 gpio on/off?
00:36.40cr2Kevin2: the base ohci address is constant. the EP/EDs are in a limited buffer from the data i have seen.
00:37.07cr2lkcl: by direct memory writes.
00:37.18lkcloh bog i knew you were going to say that cr2 :)
00:37.51cr2but you should be very careful ;)
00:38.02lkclcr2: to explain: there are only a few 'unidentified' ASIC3 GPIO outputs left.
00:38.18lkclthere are in fact only 4 that are set to '1' - A0, A1, B14 and C15.
00:38.37cr2find the speaker power first.
00:38.44lkclmy wishful thinking logic tells me that those _have_ to be related to sound.
00:38.44lkclA6.
00:38.47lkclgot that one already.
00:38.55cr2by tracing the LCD click.
00:38.56cr2ok.
00:38.59lkcli know that one - i've seen it go up-and-down enough times.
00:39.04Kevin2cr2: If you know where the buffers are, can you just watch reads/writes to those buffers?
00:39.13lkclok.
00:39.20cr2all inputs are excluded.
00:39.38cr2Kevin2: yes, but i'm not an usb expert too.
00:40.14cr2tracing this QCT serial datastream would have been much easier :)
00:40.36cr2i mean QCT: serial port.
00:41.42cr2lklc: can you put the "sound related" bits back to wiki ?
00:42.36lkclque?  it's missing?
00:42.38lkcloh yes of course.
00:43.46lkcldone
00:45.03cr2hmm. all three are outputs.
00:46.18*** join/#htc-linux hlbot (n=adm@iclem.net)
00:46.34lkclyep.
00:46.50lkclthey are.
00:48.41cr2there is a QCT_DIAG key in the wince registry
00:48.57cr2lkcl: one of then is the headphone power
00:49.06lkcli guessed that much.
00:49.25lkcloh - wait!  i have an MDA headphone - just arrived today!
00:50.08lkclbollocks.  it's USB.
00:50.39lkclthat would be funny if that was a USB audio device
00:50.58lkclok, where was i?
00:51.05cr2headphone
00:51.33lkcloh yes.  going to write to 0xa9200098 the value 0x8041 and then the value 0x8042
00:51.40lkcland play a sound
00:53.53lkclhuh.  nope.  sound still going
00:54.37lkcloh oops.
00:54.42lkclit's 0xa9200018 :)
00:55.08cr2phw ?
00:55.19cr2you can use physical too.
00:55.52cr2there are two serial drivers: qctusb.dll and qct.dll
00:58.49lkclhuh.  why, if i am writing to this address, is A0 and A1 still set??
00:59.26lkclo cos i got the wrong address ha ha
01:00.05lkcli got it.
01:00.35lkclsound goes off when i flip A1
01:00.41lkcland back _on_ when i switch it back on.
01:00.51lkcli'm guessing that's reset
01:03.10lkclhmm... A0 does nothing...
01:03.18lkclhas no effect
01:05.56lkclC15 is related to acx.  ha ha :)
01:06.10lkcli just accidentally powered off acx.  oops.
01:07.27lkclyep - C15 is acx-related.
01:10.19*** join/#htc-linux hlbot (n=adm@iclem.net)
01:12.04lkclit's gotta be one of those gpio pins.
01:16.10psokolovskycr2, lkcl: and via what i/f uda1380 gets audio data?
01:16.25lkcli2s i presume, off top-of-head
01:16.54lkcloh btw i'm _slowly_ working out, psoko, what the audio codec reset/power pins are
01:17.09lkcli've identified, i think, reset, as asic3 A1
01:17.19lkclby directly poking the memory address for asic3 (!)
01:17.21psokolovskylkcl, what that util you use to scan i2c bus?
01:17.27lkcli2cdetect
01:17.34lkclfrom debian
01:17.35psokolovskylkcl, cool ;-) don't fry sth tho ;-)
01:17.39psokolovskyok, thanks
01:17.51lkclhey psoko it's only a device.  i can always get another one.
01:18.07lkcland i have an htc hermes to play with if i fry it (arrived this morning)
01:18.10psokolovskylol ;-)
01:18.19psokolovskycongrats!
01:18.34lkclit's a _really_ nice-looking device, too.  small, lightweight
01:18.46lkclhtc really learned their lessons well with this one, from the universal.
01:19.03lkclutms, two cameras, samsung processor (so it has 6 days standby)
01:21.27psokolovskynice, hope S3Cxxxx devices will get nice kick soon ;-)
01:21.50cr2psokolovsky: uda1380 on the phones has very tricky setup
01:22.11psokolovskycr2, well, how it used at all? same i2s?
01:22.17cr2the input is I2S in ssp mode, and the output is via ssp
01:22.35cr2don't ask me how it ia all routed :)
01:22.53psokolovskyoh my...
01:23.02cr2there is also the bluetooth in SSP mode, and the BB :)
01:23.50cr2use 'wi' to trace i2c
01:24.16cr2set trace 0xXXXX1688
01:24.30cr2XXXXdepends on your mapping.
01:24.44lkclto clear a GPIO pin i just set the right GPCR bit(s) right?
01:25.03cr2psokolovsky: you should post your wince static memory mapping.
01:25.12cr2lkcl: yes.
01:25.14lkclok
01:25.20lkclhere goes GPIO 3 :)
01:25.38psokolovskycr2, where? ;-)
01:25.54cr2hmm. it seems i have found it.
01:25.54cr2HTC3GVT.dll
01:26.15cr2psokolovsky: you have wince2003 ?
01:26.21psokolovskyyep
01:26.33cr2heh. i have deleted it.
01:27.01psokolovskyI can post haret' dump mmu on wiki if it's useful
01:27.26cr2it's too much.
01:27.31cr2i need nk.exe
01:27.51cr2do you know where your bootloader ends ?
01:28.00cr2probably at 0x40000
01:28.07cr2as usual.
01:28.16cr2can you pastebin the
01:28.25cr2pd 0x40000 0x2000
01:28.25cr2?
01:28.33cr2sorry.
01:28.42cr2pd 0xa0040000 0x2000
01:37.53psokolovskyOk, so hereby I declare that I failed to solve hx4700 sound issue, or even proceed sufficiently to find the cause.
01:38.14psokolovskySuspects are haret boot, pxa27x, and of course, ak4641 codec
01:39.05psokolovskyThere're lots of wierd stuff there, however
01:39.33psokolovskylook for example, that machine chims for uda are not like for ak
01:39.38psokolovskyhow that could happen?
01:40.02psokolovskybut converting ak to uda's format lock up the machine
01:40.06Kevin2psokolovsky: Did you try with gnu-haret?  I'm not sure what haret could do to mess up sound.
01:40.17psokolovskyKevin2, yes, tried gnu-haret
01:40.26Kevin2Do you have a pxa27x cpu?
01:40.58psokolovskyKevin2, I'm not sure to what, but that discrepancy with my test env and what other people reported as working
01:41.08psokolovskyKevin2, the istuation is:
01:41.20psokolovskypxa255+uda1380 works,
01:41.29psokolovskypax270+ak4641 - doesn't
01:41.55psokolovskyso, we could try cris-cross testing,
01:42.23psokolovskyplus try to find out is theer pxa27x device with i2s sound working with haret boot at all
01:43.42lkclhuh.  ok.  none of the GPIOs i CLRd resulted in audio going off.
01:43.42lkclodd.
01:45.56lkcloops.  i'm looking at a dump pxa27xgpio and they're different from what's on SableGPIO.  oops.
01:47.39cr2hmm. pxa270+uda1380 does not work for pH5
01:48.03cr2lkcl: mux_cli
01:48.06cr2AT+CBST=134,1,0
01:48.17cr2http://doc.trolltech.com/qtopia2.1/html/phonelibrary.html
01:48.28cr2i have it on the universal
01:49.11cr2http://doc.trolltech.com/qtopia2.1/html/phonelibrary.html#10
01:49.15lkclgood man
01:50.40lkclbut the best bit is a document - harald will be pleased
01:52.19cr2it  may make sense to list the used/supported AV codecs.
01:52.52lkclgimme a sec...
01:53.03Speedy2Hey guys.
01:54.26psokolovskycr2, doesn't work? so, let's suspect pxa27x+haret
01:55.27psokolovskycr2, I actually did bunch of dumb things, like that ak-to-uda conversion, or unapplaying this patch: http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=99532559dc7a8e686b2cef14c780a7ad5dbd4a31
01:55.36psokolovskyor adding /proc/dma after all ;-)
01:56.13psokolovskywell, it's all the same conclusions - nothing pulls DMA
01:56.20cr2isn't /proc/dma and ISA thing ?
01:56.52psokolovskycr2, who care ;-). I found a recent patch on l-a-k and adapted it for pxa
01:57.13psokolovskyso, besides i2s, dma is used for udc, as could have been expected
01:57.17psokolovskynothing else
01:57.31cr2:)
01:57.42psokolovskyyou know, it can be anything, including me booting from nfs and thus having UDC always on...
01:57.43cr2i didn't use UDC for a long time.
01:57.45psokolovskyit's weird
01:57.56cr2FIR may use DMA.
01:58.00psokolovskydod you use wifi under linux? ;-)
01:58.02cr2and ??UART.
01:58.13cr2i use wifi. acx100
01:58.23psokolovskywell, both are likely on deman, of course, and none active for me
01:58.36cr2acx100 does not use DMA.
01:58.49cr2was a surprise for me.
01:58.50lkclok.  gpio 10, 111 and 112 i'm testing next, which are unknown GPIOs that were marked as inputs on SableGPIO but are actually outputs
01:58.58psokolovskyso well, if you confirm magacian doens't work, that's at least one constraint
01:59.18psokolovskyI'm going to wait for bd2 to test sound on native linux boot
01:59.22cr2lkcl: the list was copied from beetles ;) by you.
01:59.28lkcloh.  was it?  ha ha
01:59.36lkclthat's very funny
01:59.38cr2psokolovsky: it can be the uda1380 setup.
01:59.43cr2on magician
01:59.55psokolovskywell, maybe
01:59.56lkclso it's probably complete bullshit
02:00.05cr2as i have said, the phones using uda1380 use ssp+i2s for the data.
02:00.18psokolovskyah, damn...
02:02.18lkclah _ha_ i think i found another acx/wifi gpio :)
02:02.22lkclha ha
02:02.59lkclGPIO 111
02:03.24cr2lkcl: do you have the bitmask now ?
02:03.34lkclno - but i'm using your page :)
02:03.41cr2ok.
02:03.53lkclok.  GPIO 111 is acx related: my wifi just dropped out when i changed it.
02:03.57lkclxxxxing hooray.
02:05.58lkclthat's worth trying out.
02:10.57lkcluhhh... i think it works
02:11.10lkclabout to try ifconfig wlan0 up...
02:11.22lkclit WORKS!
02:11.27lkclah you little fucker
02:11.29lkclit works.
02:11.55lkclget_mask 0x00000000, set_mask 0x00000000 - after update
02:11.55lkclsta_list_add: sta=00:14:A5:54:34:CC
02:11.55lkclsta_list_add: sta=00:12:17:24:A3:FC
02:11.55lkclacx_i_timer: adev->status=1 (SCANNING)
02:11.55lkclcontinuing scan (1 sec)
02:11.56lkcl/lib/modules/2.6.18-hh0/kernel # iwlist wlan0 scan
02:12.00lkcliwlist wlan0 scan
02:12.02lkclwlan0     Scan completed :
02:12.04lkcl<PROTECTED>
02:12.06lkcl<PROTECTED>
02:12.08lkcl<PROTECTED>
02:12.10lkcl<PROTECTED>
02:12.12lkcl<PROTECTED>
02:12.14lkcl<PROTECTED>
02:12.16lkcl<PROTECTED>
02:13.55cr2conrgatulations :D
02:14.06cr2i'm going to bed.
02:14.11cr2good night.
02:14.43lkclok dude!
02:18.30Kevin2I just booted 2.6.18-hh0 on my apache.
02:23.02lkclKevin2: is that.. like... good, then? :)
02:28.43psokolovskylkcl, damn, congrats!!! ;-)
02:28.50lkclhe he wheeeeeeeee
02:29.00lkclnow i want that damn SOUND gpio damnit
02:29.49psokolovskyand feel really sick from those ak4641 issues ;-( cannot sleep, need to hack something out too ;D
02:30.00lkclpsoko ok
02:30.01lkclok.
02:30.12lkclwell, here's what i'm trying - and it resulted in me finding _one_ of them.
02:30.14lkclok.
02:30.27lkcldo you have a complete page listing all of the _known_ GPIOs?
02:30.42lkclfor the hx4700?
02:30.49lkcloh - yours is a DMA problem, isn't it
02:31.14psokolovskyyep, it was known to work
02:31.19lkclarse.
02:31.28lkclok then i probably have that to look forward to ha ha
02:31.56psokolovskyyep, have fun! ;-)
02:32.33lkclbtw psoko do you know any good docs on writing tty line discipline drivers?
02:33.10lkcli am considering writing one which puts 0x2 at the front, and writes a checksum at the end
02:37.50Kevin2psokolovsky: Is there anything sound related I can test on my apache?
02:38.53psokolovskyKevin2, sure, please try your luck with that ak4641 thing ;-)
02:39.09psokolovskyI see apache is also pxa27x+ak, right?
02:40.38Kevin2Yes.
02:41.10lkclKevin2: i managed to find one of the IO pins for the ak4641 by directly writing to asic3 memory.
02:41.14Kevin2psokolovsky: Is there code I should start looking at?  The apache doesn't have anything defined for sound yet.
02:41.33lkclit would be very helpful to have that as a haret command, for both asic3 and pxa gpio
02:41.38lkclbut not essential.
02:42.07Kevin2I think I have found all the gpio pins necessary.  I just don't know how to wire up the kernel to utilize it all.
02:42.12lkclbasically what i did was go through all of the as-yet-unidentified GPIO outputs that were set to '1' and pull them low.
02:42.14lkclyou have?
02:42.28lkclok, then copy sound/arm/htcuniversal_sound.c
02:42.43lkclto htcapache_sound.c
02:42.49lkclhave you got:
02:42.53psokolovskyKevin2, h4700/htcuniversal/sth else too - tehy all the same code
02:43.20lkclcodec power-up; codec reset; speaker; headphone
02:43.23lkclthat's 4
02:43.40lkclyou don't really need the headphone but if you've got it it will avoid you having to comment out code
02:44.01lkclpsoko: htc sable, and probably, very likely, the htc apache, too.
02:44.49Kevin2lkcl: Yes, I've identified those 4 pins on my apache.  (I don't have an asic3 - they're on egpio here.)
02:44.54lkclgreat.
02:44.55lkclok.
02:45.09lkclthen you're all set!
02:45.19lkclcopy the htcuniversal_sound.c
02:45.47lkclcheck sound/arm/Kconfig, look for HTCUNIVERSAL and copy the lines, s/UNIVERSAL/APACHE
02:45.54lkcldo the same for sound/arm/Makefile.
02:46.27lkclwhen you're done on that, do a make menuconfig and you'll find your new option you added to Kconfig under sound alsa somewhere
02:46.32lkclgo for it, dude.
02:46.41lkclwe need more people to test this ak4641
03:03.50Kevin2psokolovsky: What is the difference between SET_HX4700_GPIO and _N variant?
03:04.22psokolovskyone is for "normal" another for negated gpios, apparently
03:04.48lkcl_N i've always seen used to do with interrupts
03:04.51lkcloh.
03:04.54lkclno, wrong.
03:04.58lkclsorry - ignore me
03:05.30Kevin2Okay. Thanks, that is what I thought.
03:36.06Kevin2Okay.  I get: PXA2xx i2Sound: HTCApache Audio activated
03:36.13Kevin2Now for the big question -- how do I test this thing?
03:38.24Kevin2psokolovsky: How did you test to see if sound works or not?
03:39.09psokolovskyKevin2, the high-level test is to boot fam0.8.4/gpe, go to to Sound setting, and make should that test button does chirp ;-)
03:39.31psokolovskythat's porbably most accessible test unless you build images yourself
03:40.00Kevin2Okay.  I need to get fam/gpe installed then.  I'm just using a stripped down boot environment right now.
03:40.05psokolovskybut it uses OSS emu layer of ALSA, so may add some artifacts (but it should work and does work)
03:40.20psokolovskylow-level test is to use alsa utils package
03:40.25Kevin2Can you direct me to some pointers for installing/running a distribution?
03:40.27psokolovskyhttp://www.handhelds.org/moin/moin.cgi/AlsaHandheld
03:40.57psokolovskyKevin2, you probably can d/l install tarball for close device (hx4700 apaprently), and boot it with your kernel
03:41.03psokolovskymost stuff should work ;-)
03:41.15psokolovskyhttp://familiar.handhelds.org/releases/v0.8.4/install/download.html
03:41.50psokolovskyand boot via NFS or from SD card (I usually do the 1st, but again, that may give some artifacts)
03:42.04psokolovsky(well, any type of boot gives some of course ;-) )
03:42.34psokolovskyor maybe hx4700 is wrong choice if you have qvga screen
03:42.56psokolovskyall in all, I booted h2200's distro on h4000 at stoneage times ;-)
03:43.27psokolovskyyou cna be sure that there's no iwmmx optmization or something there anyway
03:44.33Kevin2I have standard 240x320 screen.
03:45.01psokolovskyh2200 may be a good choice then, it works on other devices ;-)
03:45.18Kevin2But those images look like they want to change the rom.  I need something I can just expand to a filesystem.  Then I need to run make modules_install from my kernel.
03:46.56psokolovskyKevin2, of course they provide tarball in addition to jffs2 image
03:46.59psokolovsky1sec
03:47.39psokolovskyFish here: http://familiar.handhelds.org/releases/v0.8.4/install/files/h2200/
03:49.56Kevin2Cool. In my last compile I pulled in the corgi bl stuff - my screen just blanked instead of the normal ghost to white stuff.
03:51.17psokolovskyyou mean it worked as it should or made LCD always-black?
03:52.22Kevin2No - it worked like it should - I was idle for several minutes and it went to black instead of fading to white.
03:53.03psokolovskyso, nice! that's how it should become once we started to use common stuff ;-)
03:53.33psokolovskyI really don't know what issues cr2 has on universal, but that's likely to gpio sequence, not corgi-bl per se
03:54.06psokolovskyKevin2, well, and now some less cheerful news - haret 0.4.3 doeesn't boot on h3900
03:54.14Kevin2I still need to code up the lcd enable/disable sequence.  I'm just doing a cken on / off in the stuff I cloned.
03:54.54Kevin2psokolovsky: Try the latest haret (either by building from cvs or svn).
03:54.56psokolovskyKevin2, I see. h4000 needs some cleanup too
03:55.21psokolovskyKevin2, ok, will try. just fyi
03:55.21Kevin2Create a file "earlyharetlog.txt" -- when this file is present, it should give early diagnostic messages in haretlog.txt.
03:56.00Kevin2The latest binary cr2 and I worked on is in svn as haret.exe-gccmain
03:56.08Kevin2svn://www.shadowmite.com/home/svn/ppc6700/haret
03:58.06psokolovskyok
03:58.09Kevin2psokolovsky: Does haret start, but not boot linux -- or does it not start at all?
03:58.23psokolovskywill try to build myself after all probably, but tomorrow then
03:58.53psokolovskyit hangs with logo still displayed after therrmometer is up and it should run kernel
03:59.56Kevin2Okay.  haret-0.4.3 is the original linux boot code.  I've never had much luck with it.  I'd be interested to hear if the new boot code works for you (haret >= 0.4.4).
04:00.38psokolovskyok
04:12.43psokolovskywell, at least fixed suspend/resume code for h3900 with native wince bootloader ;-)
04:13.23lkclargh A0 and A1 _are_ sound-related.
04:14.07Kevin2psokolovsky: Would you recommend testing with gpe or opie images?
04:14.09lkcljust going to try them... *sigh*
04:14.25lkcllike i thought i'd tried them a dozen times before...
04:14.29psokolovskyKevin2, I use gpe ;-)
04:14.45lkcleeuw, psoko
04:16.06psokolovskywe talk about common testing settings here ;-) you don't think ak suddenly will work with opie? ;-)
04:22.35lkclok i thought i'd best read the datasheet on the ak4641, like.
04:22.58lkclit requires a HIGH TO LOW transition on one of the pins, to perform the reset of internal registers.
04:22.59lkcloops.
04:23.14lkcland there's also a delay required
04:26.19lkcli might be getting somewhere...
04:28.20psokolovskyhope you'll discover what was itching us...
04:28.26Kevin2Cool!  TS worked out of the box on that gpe image.
04:28.48lkclyaay well done Kevin2
04:29.46psokolovskyKevin2, that's nice ;-) soon buttons will work too (in OE.dev at least). of course, if you guys support common buttonmap idea.
04:31.03lkclcool.  reboot actually works.
04:31.54lkclsaves me pulling the battery out
04:32.27lkclwish i'd known that earlier
04:32.42lkcli've taken the battery out about... 200 times so far...
04:33.02lkcli can't believe wireless works.
04:33.32psokolovskylkcl, so it really works? what's the speed?
04:33.36lkclyep.
04:33.44lkcl802.11b i think
04:33.48lkclit's acx100
04:34.02Kevin2Do you know what the default ip gpe uses?
04:34.11Kevin2(for usb link)
04:34.18psokolovskyyep, what actual throughput you get? you transferred some 100mb file, right? ;-)
04:34.28lkclpsoko: don't be daft :)
04:34.36psokolovskyKevin2, better, pass ip= on kernel command line
04:34.41lkclit's listed in /etc/network/interfaces Kevin2
04:34.44psokolovskyno default afaik, need to configure
04:41.17Kevin2psokolovsky: The "test" button is grayed out.  I think it happened because gpe started before I could load the htcapache sound module.
04:41.31Kevin2Is there a way I can tell it to restart the sound stuff?
04:41.37psokolovskyKevin2, (un)tick som checkboxes pls ;-)
04:42.00psokolovskyKevin2, ah, you load modules?
04:42.17psokolovskywell, /etc/init.d/gpe-dm stop / start
04:42.53psokolovskyit still should pick up in real time, I guess,
04:43.03psokolovskyso, that's that "automatic volume"
04:43.13psokolovskywho'd think you couldn't tets sound with it, lol
04:43.25psokolovskywince is not that braindead, after all ;-)
04:43.44Kevin2Oh, you're right - if I unset "automatic volume" than I can test.
04:44.32Kevin2Well, I don't hear anything.  But I'm not getting any useful diagnostics either.
04:45.14psokolovskyKevin2, see dmesg
04:45.53Kevin2Oooh  - the brightness meter works out of the box.
04:45.59psokolovsky;-)
04:46.03lkclKevin2 - what device is this?
04:46.25lkclo yes htc apache.
04:46.31Kevin2lkcl: HTC apache (aka xv6700 aka ppc6700)
04:47.09Kevin2How do I modify volume?
04:47.32lkcloo, you poor person you: CDMA....
04:47.52psokolovskyKevin2, slider in the same applet
04:48.09psokolovskyKevin2, anything in dmesg?
04:48.39lkclare you seriously telling me that the htc apache supports usb host???
04:49.04lkcllike... i could like... plug a usb keyboard into it??
04:49.23Kevin2psokolovsky: Unfortunately, I have my TS stuff sending debug info to dmesg -- so I can't see anything useful.  I'll need to recompile.
04:49.43Kevin2lkcl: I can network between my desktop and phone via usb.
04:49.54psokolovskyI see. or try via ssh?
04:50.06lkclthat's usb client networking, not usb host.
04:50.16Kevin2Yeah, I'm ssh'd into my phone now.
04:50.25lkclusb gadget (g_ether)
04:51.39psokolovskyKevin2, try that cat /dev/random >/dev/dsp then
04:52.21Kevin2I don't see anything from dmesg.
04:53.28psokolovskytoo bad
04:53.31lkcli'm nearly done for the night
04:53.35lkclstarting to sink...
04:53.52psokolovskybut I didn't realy do myself that cat, so cannot say
04:54.04psokolovskyALSA sound/core/pcm_native.c:1510: playback drain error (DMA or IRQ trouble?)
04:54.08Kevin2I'm going to recompile without ts debug messages - that'll help.
04:54.12psokolovskyis what both cr2 and me get
04:56.22Kevin2Is there an equivalent file for /etc/rc.local?  I need to load a keyboard map file for apache, but don't know where to add it in the startup scripts.
05:01.07lkclok i get UU in the i2cdetect box instead of XX now.
05:02.03lkcli get timeouts on the i2c bus...
05:15.38Kevin2Hrmm the only thing I get is:
05:15.41Kevin2PXA2xx i2Sound: HTCApache Audio activated
05:22.07lkclok that's good.  i think.
05:23.23lkclPM: Adding info for i2c:0-0057
05:23.26lkclthat's err... new
05:24.01lkclwhere the hell did _that_ one come from???
05:24.05lkcl0057???
05:24.10lkclo gawd i bet that's the camera.
05:25.27Kevin2Hrmm.  I didn't compile in OSS support.  If gpe wants oss, then it wont work, of course.
05:25.50lkclyou don't need OSS support you need OSS _emulation_
05:25.55lkclit's in a different area
05:26.13lkclgo into ALSA config.  don't enable OSS modules
05:26.25Kevin2Well, yeah, but I don't have either.
05:26.31lkcli think something goes wrong, here, that crashes the i2c
05:26.34lkcl??
05:27.43lkclsomehow
05:36.33lkcllast boot...
05:36.46lkcllast try at sound today
05:38.33Kevin2Okay.  When I click test, the log shows it activates the rear speaker.  The rear speaker stays on for about 10 seconds, and then it gets disabled.
05:38.43Kevin2I don't see any error messages.  I don't hear any sound either.
05:39.16Kevin2(Well, I can hear a faint buzz that's from the powered up speaker, but no sound effects.)
05:40.17lkclwell, good luck - i am very out.
05:41.21lkclload on i2cdetect (download the lm-sensors_2.10. from http://ftp.uk.debian.org and libsensors3_2.10 as well)
05:41.57lkclextract them both with dpkg-deb -X lmsensors....deb i2c
05:42.08lkcland dpkg-deb -X libsensors....deb i2c
05:42.25lkclthen tar -cvzf i2c.tgz i2c/
05:42.34lkclcopy that to your apache
05:42.42lkcland then run /usr/sbin/i2cdetect -0
05:42.52lkclhttp://www.lm-sensors.org/wiki/i2cToolsDocumentation
05:43.10lkclif you haven't got debian, GO GET IT! :)  kubuntu would do just as well
05:43.10Kevin2We've done that in the past.  There is a wiki on xda-dev with the info.
05:43.17lkclo cool.
05:43.42lkclif you have the initialisation correct, the ak4641 will show up on the i2cdetect scan.
05:44.19lkclmake sure that your htcapache.c file (or whatever does the initialisation of the asic3) _doesn't_ have the asic3 GPIO pins that you're pulling up _already_ set
05:44.33lkclcos when you boot from wince, the ak4641 remains initialised, then.
05:45.00lkclit's the only way that i accidentally managed to detect the ak4641 on the i2c bus.
05:45.43Kevin2ls -l /sys/bus/i2c/devices/
05:45.45lkclwhen i set A0 and A1 to 0 in the asic3 initialsation (line 133 of htcsable.c) then the ak4641 disappeared from the scan
05:45.50Kevin2lrwxrwxrwx    1 root     root            0 Nov 23 00:45 0-0012 -> ../../../devices/platform/pxa2xx-i2c.0/i2c-0/0-0012
05:46.04Kevin2cat /sys/bus/i2c/devices/0-0012/name
05:46.04Kevin2ak4641-i2c at 0-0012
05:46.11Kevin2So, I think it is binding on the i2c side okay.
05:46.57lkclnot necessarily.
05:47.01lkcldetect is not the same as initialised.
05:47.15lkcli have the same thing as you
05:47.37lkclbut, now that i have the name, my entire i2c bus is crap.
05:47.49lkclit doesn't help that the modules are stuffed and cannot be unloaded properly
05:47.51lkclrmmod'd
05:47.55Kevin2Okay.  I definitely clear the pins at startup.  (My printks also confirm this.)
05:48.21lkcldo an lsmod
05:48.49lkclhow many things are listed as using i2c_pxa?
05:49.04lkclis the Used by count equal to 1, but no modules listed?
05:49.19Kevin2I have i2c builtin.
05:50.06lkclahh :)
05:50.31lkclmy i2c bus is crashed.
05:50.55Kevin2It is possible I may have power/reset reversed..  I was really only guessing which was which.
05:52.44lkclhe he
05:52.51lkclyep - you'll soon find out :)
05:53.19Kevin2Good night.
05:53.38lkclnight dude
07:03.25*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.179)
07:04.44*** join/#htc-linux rob_w (n=rob_w@p549B9B81.dip0.t-ipconnect.de)
07:36.17*** join/#htc-linux rob_w (n=rob_w@p549BCB98.dip0.t-ipconnect.de)
08:03.25*** join/#htc-linux Fossi (n=cmewes@195.177.48.115)
08:11.28*** join/#htc-linux TripleDES (n=sergio@84.77.161.251)
08:24.26*** join/#htc-linux rob_w|mis (n=rob_w@p549BBF0F.dip0.t-ipconnect.de)
08:50.26*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
08:53.29goxboxlivegood morning
08:56.00Speedy2Hi
09:09.49*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
09:53.44*** join/#htc-linux TripleDE1 (n=sergio@84.77.163.149)
09:58.46goxboxlivepsokolovsky: You asked yesterday what failure message we got on our universal when sound driver is loaded during boot: Here is an output: http://pastebin.ca/255767
10:18.46*** join/#htc-linux psokolovsky_ (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com)
10:39.42*** join/#htc-linux Timmeh (n=pope@mail.ccww.co.uk)
10:49.05*** join/#htc-linux TripleDES (n=sergio@84.77.155.74)
10:56.17goxboxlivepsokolovsky_ ': I saw that you stayed up late last night. Are you awake?
11:06.16goxboxliveKevin2 / lklc /psokolovsky_ : I have made the lmsensors and som other developer stuff. You can can download them from here: http://gnulinux.biz/files//Universal/developer-stuff/
11:06.56goxboxlives/lklc/lkcl/
11:09.00*** join/#htc-linux g3gg0_ (n=g3gg0@ppp-82-135-15-150.dynamic.mnet-online.de)
11:10.00cr2goxboxlive: i have found an interesting file yesterday.
11:10.47goxboxlivewhat kind of file?
11:11.39cr2htc3gvt.dll
11:11.47cr2in \windows
11:11.47goxboxlive:-)
11:11.59goxboxlivethe let's rip apart
11:12.15cr2it's not a xip file, it can be just copied.
11:12.22goxboxlivecool
11:12.46cr2it calls AT+CBST=134,1,0
11:12.47goxboxlivecr2: I saw that Kevin2 had managed to shut of lcd
11:12.53goxboxliveok
11:13.14cr2he does not have any gpio code at all. he just have switched the clock off.
11:13.21goxboxliveok
11:13.31goxboxliveHe is also using the corgi
11:14.02cr2http://doc.trolltech.com/qtopia2.2/html/phonelibrary.html#10
11:14.47goxboxliveYes i have seen it
11:14.55cr2goxboxlive: look at the corgi-bl.c code, and you'll see a light at the end of the tunnel ;)
11:15.08goxboxliveSHall i try to run it?
11:15.54cr2if you'll run 'strings' and 'strings -el' on htc3gvt.dll you'll get many interesting things.
11:16.04cr2forget about the backlight now.
11:17.17cr2VT_Fake324M_CommDump.bin
11:17.18cr2\VT_Comm_Tx_ST.txt
11:17.18cr2\VT_Comm_Rx_ST.txt
11:17.18cr2%010lu - %010lu
11:17.18cr2\VT_Comm_Tx.Bin
11:17.18cr2\VT_Comm_Rx.Bin
11:17.29cr2these are the most interesting.
11:18.18cr2it seems to me that some logging can be enabled.
11:19.05cr2we only need to find out how.
11:19.07goxboxlivewell there where no light in that tunnel :-)
11:19.29goxboxliveok
11:20.27cr2and we can also list all the codecs. and compare with ffmpeg & co.
11:21.05goxboxliveok
11:28.10goxboxlivecr2: I did a speaker test: take a look: http://pastebin.ca/255812 why isent it permitted?
12:04.56*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
12:08.46lkclallo darlins
12:11.08*** join/#htc-linux alex-begin (n=345rt@84.232.212.62)
12:11.48goxboxlivehi lkcl
12:31.14cr2goxboxlive: because the developers did not find a better error.
12:31.34cr2the problem is the dma stall.
12:31.58goxboxlive:-)
12:31.58goxboxliveso it has nothing to do with the audio in root group
12:32.13goxboxlivei c
12:49.35*** join/#htc-linux alex-begin (n=345rt@84.232.212.62)
13:08.02*** join/#htc-linux Timmeh (n=pope@mail.ccww.co.uk)
13:09.41Timmehhi cr2 thanks for replying to my post on xda-dev (tim_programmer)
13:10.55Timmehi thought it would be alot of work...especially for me 'the newb'
13:11.11Timmehbut hey we all gotta learn somewhere :-)
13:13.41cr2hi Timmeh
13:13.48cr2goxboxlive: http://www.voip-info.org/wiki/view/Asterisk+H324M
13:16.35Timmehquick question youve got source on sourceforge and on HH.org.. are these the same or is one old etc
13:16.35cr2h263 and amr are implemented afaik.
13:16.51cr2sf.net is old, but working .12 kernel
13:17.01Timmehok great
13:17.13cr2the real work is done on blueangel .18-hh0 in hh.org
13:18.11Timmehcool will have to get that later (when i'm not supposed to be working ;-) )
13:18.26Timmehi was using the sf version
13:18.32Timmehthought it seemed a bit slim
13:18.42goxboxlivei c
13:43.05psokolovsky_Hi!
13:44.15psokolovsky_goxboxlive: fsck, what can I say! I spent whole damn night yesterday hunting within DMA and I2S area, and now you say me that it can be I2C-related? funny ;-)
13:46.43*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
13:47.33cr2goxboxlive: do you include kphone/pi in your opie image ?
13:47.53goxboxliveno i havent done that.
13:47.59goxboxliveShould i?
13:48.04cr2i think yes.
13:48.15goxboxlivei will then chief :-)
13:53.08cr2goxboxlive: we also need to removed tslib dependency on x11 and gtk. if at the end we will include asterisk in the image, we don't need any unnecessary stuff in flash.
13:54.57goxboxlivecr2: Well i have tried that before, but it ends up with no working touchscreen.
13:58.46goxboxlivecr2: I have seen that hx4700 is trying to remove the tslib, i tried also, but it didnt build.
14:01.45goxboxlivecr2: Are we able to use this: # People should consider using udev's /dev/input/touchscreen0 symlink
14:01.45goxboxlive# instead of detect-stylus
14:02.19cr2you need to remove the gtk code from detect-stylus, and the dependencies. imho, it should be a separate package.
14:03.00cr2if irdadump is a separate package, then gtk-detect-stylus which has heavy dependencies should be anyway.
14:07.02goxboxlivecr2: This is the depedencies of detect-stylus: DEPENDS = "virtual/libx11 xcursor-transparent-theme xrdb"
14:13.38psokolovsky_goxboxlive:
14:13.38psokolovsky_<psokolovsky_> Hi!
14:13.39psokolovsky_<psokolovsky_> goxboxlive: fsck, what can I say! I spent whole damn night yesterday hunting within DMA and I2S area, and now you say me that it can be I2C-related? funny ;-)
14:13.45lkclcr2: you're right about the A0 and A1 being ak4641 power and reset
14:13.54lkclhowever, i2c is fscked
14:14.41lkclpsoko, gobox: after initialising the ak4641, the entire i2c gives timeouts on devices.
14:14.46lkclnames can be detected - once.
14:14.46cr2goxboxlive: well, remove them. if the mainline oe is reluctant to remove this code, we will have our own version. we are talking about it for half of the year ;)
14:15.11lkclbrb darlings
14:16.09goxboxlivecr2: Are we able to make a symlink to /dev/input/touchscreen0 . If we are we might get rid of detect-stylus
14:16.58psokolovsky_goxboxlive, can you tell me if you do anything special to get verbose i2c logging?
14:17.15cr2there is nothing wrong in the detect-stylus itself, it's just the gtk code that has nothing to do there.
14:17.26goxboxlivecr2: ok
14:17.46goxboxlivepsokolovsky_ : I have enabled debug in the kernel .config
14:17.52psokolovsky_goxboxlive, cr2:  but getting rid of detect-stylus is direction in which OE.dev moves anyway
14:18.06psokolovsky_goxboxlive, didn't patch anything, right?
14:18.32cr2pskokolovsky_: ok.
14:18.48goxboxliveno
14:18.58psokolovsky_ok
14:19.19goxboxlivepsokolovsky i know, have have seen that the hx4700 is getting rid of it
14:19.27psokolovsky_I'll still leave it for bd2 to try it on flashed hx4700 first ;-)
14:19.35psokolovsky_yeah
14:19.53psokolovsky_and will need to do that consistently in the end ;)
14:21.32*** join/#htc-linux JTRipper (n=jtripper@p54B1D552.dip.t-dialin.net)
14:24.50goxboxlivepsokolovsky_ To get rid of detect-stylus, is there anything in udev i have to add?
14:28.49psokolovsky_goxboxlive, well, udev rule should be already there
14:28.54goxboxlivegood
14:41.20Kevin2Hi
14:54.49Kevin2Well, no luck for me with sound.  It's definitely toggling the speaker / headphone gpios in the right way ( and detecting headphones), but I hear no sound.
14:55.03Kevin2I don't get any useful diagnostic messages at all.
14:57.10*** join/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com)
14:58.59lkclpsoko: there's a stack of i2c support options
14:59.01lkcl# CONFIG_I2C_DEBUG_CORE is not set
14:59.01lkcl# CONFIG_I2C_DEBUG_ALGO is not set
14:59.01lkcl# CONFIG_I2C_DEBUG_BUS is not set
14:59.01lkcl# CONFIG_I2C_DEBUG_CHIP is not set
14:59.28lkclallo Kevin2
14:59.35lkclhmm.
14:59.56lkclKevin2: can i ask you a favour: could you possibly reply on kd@hh and explain where you're at, at the moment?
15:00.23lkcland definitely run i2cdetect once the snd-htcapache_audio module is loaded
15:01.05Kevin2lkcl: Where I am with respect to what?
15:07.36psokolovskyKevin2, Hi!
15:07.46*** join/#htc-linux RoEn_PC (n=roen@p54A67710.dip.t-dialin.net)
15:08.02psokolovskyKevin2, you likely don't have alsa logging enabled, that's why you didn't get anything in dmesg
15:10.11cr2btw, do we know something about the wifi eeprom structure from the acx code ? can we read the eeprom ? this will be a good and simple i2c test.
15:10.29goxboxlivecr2: i have build without detect-stylus, but the TS doesnt work. Was it /dev/input0 that was the TS?
15:10.59cr2the wince i2c code on the universal always checks that the asic3 gpioa0 is high. but i have never seen anything that can drop it low.
15:11.57cr2goxboxlive: detect-stylus is a program that helps to find out that the touchscreen is at /dev/input/event0. you can hardcode it in /etc/init.d/opie
15:12.25cr2the keyboard and all the buttons are hardcoded in the c++ code as /dev/input/event1
15:12.54cr2that makes me some trouble to split the gpio-keys, asic3-keys and the pxa keyboard ;-)
15:13.37cr2and i don't know what is the right solution.
15:14.35cr2so it stays as is, with buggy suspend/resume behaviour now.
15:14.43psokolovskycr2, I bet, both opie and gpe actually scan devices, and/or use some mux interface
15:15.01psokolovskyall in all, both opie & gpe work OOB with split inputs
15:15.22psokolovsky(that was my concern too, if you read my original RFC to suppott shared input device)
15:15.29cr2psokolovsky: i'm pretty sure that odevice_htc.cpp has /dev/input/event1 hardcoded.
15:15.50psokolovskyand I'm pretty sure that opie does work still ;-)
15:16.09lkclKevin2: getting sound
15:16.10psokolovskyah, odevice_htc.cpp?
15:16.19cr2yes, because we load/find the modules in the right order.
15:16.20psokolovskythen don't do that! ;-)
15:16.31lkclcr2: good point.
15:16.37cr2and don't use the usb/BT mouse/keyboard/whatever.
15:16.44psokolovskydo like rest of people do ;-)
15:17.17cr2goxboxlive has BT mouse and keyboard, and has tested them with universal :)
15:17.17lkclwell if i knew how to initialise it, i would run the i2s 'command' reading thing on it
15:17.34lkclwhat's the EEPROM used for, again?
15:17.54cr2lkcl: to store the radio type, ethernet address and such things.
15:17.58lkclok.
15:18.04cr2look in the acx code.
15:18.33cr2you can dump it from /proc
15:18.46cr2don't remember how it is implemented.
15:19.09cr2the tiacx must have its own i2c.
15:19.33cr2that's why i was surprised that we see it on the pxa i2c bus.
15:19.55cr2or pretend to see.
15:23.43Kevin2Nov 23 10:23:36 h2200 user.debug kernel: ALSA sound/core/pcm_native.c:1510: playback drain error (DMA or IRQ trouble?)
15:26.01Kevin2I don't see anything that would indicate an i2c error. I've compiled in all the i2c debug stuff, and it seems okay.  (I see reads/writes on the i2c bus with no indication of a problem.)
15:31.59cr2Kevin2: what other dma devices do we have ?
15:32.11cr2is it possible to force FFUART to use dma ?
15:35.35*** join/#htc-linux tim_ (n=pope@mail.ccww.co.uk)
15:37.09goxboxlivehmmm, touchscreen is working when i do cat /dev/input/event0 but it doesnt work when using Opie
15:37.33goxboxliveexport QWS_MOUSE_PROTO=:TPanel:/dev/input/touchscreen0
15:39.41psokolovskyatetntion please, ak4641 is speaking!
15:39.44psokolovsky------------------
15:39.45psokolovsky<bd2_> HAHA!
15:39.45psokolovsky<bd2_> sound is working! :-)
15:39.45psokolovsky<bd2_> I've soft rebooted hx4700 after dma error, insmoded snd modules, and speaker test gives white noise
15:39.46psokolovsky<psokolovsky> bd2_, DON'T TOUCH IT!
15:39.48psokolovsky<psokolovsky> let people hear that wonder first!
15:39.50psokolovsky-----------
15:40.13cr2soft rebooted ? what's that ?
15:41.27psokolovskyhe has Linux flashed
15:41.37psokolovskyso I guess, "reboot"
15:41.57cr2but that means buggy dma setup ?
15:42.16psokolovskymaybe, pls join #handhelds.org
15:42.54cr2hmm. need to go. will be back later.
15:43.03psokolovskyok
16:00.27*** part/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com)
16:23.14*** join/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com)
16:56.52*** join/#htc-linux jeanseb (n=jeanseb@88.164.32.155)
16:59.00jeansebsalut
17:05.12psokolovskyKevin2, how exactly you deal with dma in haret, in 2 words?
17:06.59*** part/#htc-linux babeloued (n=Fabrice@faim1.itesoft.com)
17:11.48*** join/#htc-linux pH5 (n=ph5@p5485F917.dip.t-dialin.net)
17:13.47cr2hi again
17:14.09cr2pH5: did you find the OWM in AIC3 ? not asic3.
17:16.55pH5hey cr2, yes I did.
17:17.57cr2do you have the code ?
17:19.36pH5cr2: yup, but now I use mreimer's ds1wm driver instead.
17:20.55cr2ok, but how do you deal with it ?
17:21.45pH5http://en.pastebin.ca/255994
17:22.31pH5I didn't have time to write the battery driver yet, so I'm missing the connection of w1_ds2760 to the battery classdev
17:24.00cr2hmm. i suspect the same in blueangel. it uses +2, +4, +6 and +8 registers.
17:25.35pH5the blueangel aic2 has the ds1wm too?
17:26.17pH5then we should write a common aic2/aic3 driver that can be connected to ds1wm and a led driver for both ba and magician
17:26.46cr2the battery uses something there. the +0xA offset has the leds.
17:26.59cr2aic2 ?
17:27.18pH5isn't it labeled AIC2 in the blueangel?
17:27.29cr2i'll look.
17:27.51cr2there is OWM irq, but i have not yet found it.
17:28.03*** join/#htc-linux pleemans (n=peter@d51A5E421.access.telenet.be)
17:28.06pH5the led driver sure is similar.
17:28.25cr2the current code uses tsc2200, and afaik there are some problems. and it's not clear where is the second battery.
17:29.54cr2yeah, looks like aic2.
17:30.26pH5does it have gpios?
17:30.41pH5(besides what the led driver uses)
17:31.30pH5the magician has a huge list of gpio registers that are setup in "InitPASIC3GPIO" or something like it in nk.exe.
17:32.07pH5But the only gpios that I found are changed during operation so far are the led gpios and the one to turn on/off the W1.
17:32.42pH5(I have no idea whether that's just a gpio connected to the EN pin of the DS1WM or perhaps some kind of cken bit)
17:32.55*** join/#htc-linux BabelOued (n=Fabrice@82.238.28.28)
17:33.07cr2i need to check the code in more detail.
17:33.16*** join/#htc-linux JTRipper86 (n=jtripper@p54B1F54C.dip.t-dialin.net)
17:33.29cr2it has 2 areas. this "battery" one, and the leds.
17:34.01cr2there is something similar also in the alpine cpld. sounds logical after all.
17:36.00psokolovskyKevin2, cegcc SVN HEAD broken?
17:37.23psokolovskynevermind, read INSTALL ;-)
17:46.21pH5cr2: http://wiki.xda-developers.com/index.php?pagename=MagicianAIC3
17:48.58cr2pH5: 4 8 c 10
17:49.32cr2yes :) i have .bus_shift=!
17:49.36cr21
17:50.06lkclKevin2: thanks for that message to hh
17:51.05lkclOK!  someone has sound on the hx4700 - cool!
17:51.29lkclok here's a possible hint/exploration.
17:51.44lkclwhen we do rev-eng we copy the gpio and asic3 params from wince.
17:51.57cr2pH5: i don't have (use) aic gpio, it seems.
17:52.01lkcl_but_ - of course - those initialisation parameters are from _running_ - post-initialisation of wince.
17:52.24pH5cr2: this register is used in the led driver at least
17:52.27lkcland the A0 and A1 are a classic example of that in action: in htcsable.c initialisation of asic3, A0 and A1 are set 'high'.
17:52.34cr2lkcl: it's pxa dma here ?
17:52.40cr2pH5: on blueangel ?
17:52.56lkclmmmm... there's a difference, isn't there...
17:53.04pH5cr2: yes, I remember i wrote the magician led driver and then looked at the ba one and found it mostly similar...
17:53.21cr2lkcl: that's why i have the 'Init' field in Foo_asic3. it is empty for sable.
17:53.35cr2pH5: platform_driver :)
17:53.35lkclack
17:54.31cr2so the current BA battery monitor code is wrong.
17:54.44cr2maybe it looks for the backup battery ?
17:55.07cr2pH5: on hx4700 it's the ts chip looking after the second battery ?
17:59.18*** join/#htc-linux WizMaui_ (n=WizMaui@62.112.90.179)
18:04.02BabelOuedhi
18:05.14cr2hi BabelOued. the battery code need some serious reshuffle. but it's taken from himalaya and is not quite right.
18:06.36BabelOuedi see your message
18:07.14BabelOuedthe two register from tsc2200 are AUX1 and AUX2
18:07.28BabelOuedbut value seem strange
18:08.44BabelOuedyou've any idea ?
18:10.17cr2i think on hx4700 the ts chip monitors the backup battery.
18:11.37psokolovskycr2, pretty true should be. but I wonder if on h4000 it monitors both if them? so far, second voltage readings were stable, surprise ;-)
18:12.30cr2and the main battery is monitored by OWM on this small CPLD.
18:12.53cr2psokolovsky: do you have some asics on h4000 ?
18:13.20psokolovskycr2, asic3 ;-P
18:13.43cr2btw, what is more interesting, that the asic3 OWM on blueangel is not used.
18:13.59cr2psokolovsky: is the OWM on on your asic3 ?
18:14.05psokolovskycr2, same appears to be for h4000
18:14.17psokolovskydunno (ashamed)
18:14.26pH5cr2: are all those asic3s the same chip, or are there different revisions?
18:14.29cr2do you have motherboard pictures ?
18:14.35psokolovskybut as i told, that driver which I posted gave onlt timeouts for me...
18:14.56psokolovskypH5, all the same, guaranteed. or we should think so.
18:15.18psokolovskycr2, me? (motherboard pix)
18:15.26cr2pH5: must be a different revision. older asic3 was .bus_shift=2, newer =1, your AIC3 also has different .bus_shift from ba.
18:15.34cr2psokolovsky: yes.
18:16.15psokolovskycr2, yep, see h4000 wiki
18:16.20cr2ok.
18:16.30psokolovskycr2, and yeah, there're whole 6 pins on the battery ;-D
18:16.48lkcli like the htc hermes so much that even though i've not got a sim card in it i'm thinking of taking it along just for show :)
18:16.55cr2psokolovsky: imho, it is on all li batteries.
18:17.21pH5lkcl: where did you get it and for how much?
18:17.24psokolovskycr2, it's proved to be not in h1910 (also asic3)
18:17.35cr2lkcl: we need dump functions for haret.
18:17.45cr2psokolovsky: i mean  the contacts :)
18:17.59psokolovskycr2, and h1910 maintainer assured me that he disassembled driver and knows that, and he thinks h4000 shoudl be the same too.
18:18.08psokolovskycr2, h1910 has 4 contacts
18:18.17psokolovsky5 is most common AFAIK
18:18.27psokolovskyIIRC those numbers correctly
18:18.35psokolovskybut the fact they are different
18:18.57cr2jornada820 has the li cells with a microcontroller, which reports something over RS232 1200bps (!)
18:18.59cr2ok.
18:19.08cr2saves them money.
18:19.24psokolovskylol ;-)
18:20.02cr2i wonder where the current ba battery code comes from ;)
18:23.09cr2psokolovsky: h3600 is strongarm ?
18:24.01psokolovskycr2, yeah!
18:24.45cr2i have some problems with the cpu-sa1100.c there, but i'll post about it later.
18:25.14cr2my values for 191MHz CPU speed are different.
18:25.30cr2with the current values the jornada820 crashes.
18:26.45cr2psokolovsky: btw, i think the h4350 spi flags are taken from ASIC2, but it looks to me that the register layout on ASIC3 is different.
18:27.36psokolovskycr2, hm, possibly. but there's only 1 bit diff with BA
18:28.24cr2ok.
18:28.35cr22408w on h4000. good.
18:29.07cr26101 is BT ?
18:29.56psokolovskyyeah, it's that pre-6150 thing
18:30.37psokolovskysame as BA per HHX
18:33.54cr2yes.
18:35.18cr2hmm. it seems the SDG bootldr makes something to DMA so it is configured properly. sounds like a kernel bug to me.
18:37.29psokolovskycr2, for me too ;-) poor leenouks kernel... ;D
18:39.49*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
18:46.40pH5hm.. I can't find anything about DMA in the sdg bootldr
18:50.25psokolovskypH5, I'd say, good reset would clear all that stuff ;-I
18:50.27cr2pH5: "numbered" gpio settings ? and the full hardware cpu reset.
18:51.26psokolovskyWell, gentlemen, I found that pxa27x dma setup in haret is a bit less comprehensive than even for pa25x. so I ported that.
18:51.33psokolovskyresults are the same ;-(
18:53.55psokolovskyanyone know anything about that "Flow through
18:53.55psokolovsky" vs "
18:53.55psokolovskyfly by" crap?
18:54.57lkclpH5: bought it on ebay.  $EUR 450.  it's brand new: the guy who sold it to me had bought two of them
18:55.30lkclcr2: what kind of dump functions, dude?
18:55.43cr2lkcl: dump pxa27x*
18:55.59cr2dump sc324xx*
18:56.08lkcloh right - of course.  ha ha
18:56.20cr2then porting will be very easy.
18:57.02cr2i don't want to know how much time was spent on rx3715 to get the register data with raw haret register access ;)
18:57.27cr2look at mach-rx3715.c
18:57.58pH5cr2: what is the quickest way to remove the RIL stuff from xanadux haret?
18:58.12cr2and there will be more samsung based phones coming.
18:58.26cr2pH5: comment out the testril() function.
18:58.52lkclyep.  it's a great processor.
18:59.00pH5cr2: thanks
19:00.11pH5lkcl: that sounds like a good deal. still too expensive for me. but it's good to know that linux will be up and running when I can afford one ;)
19:00.22lkclha ha very funny pH5
19:01.01cr2lkcl: that's not very challenging phone to port to.
19:01.14cr2ak4641 driver will be completely unusable.
19:01.55cr2i'd like to get my dirty fingers on the pseudorange data from the GL :)
19:03.07lkcl:)
19:05.10lkclhuh.  that's odd.  the i2c bus doesn't even _work_ - massive amounts of timeouts - and i haven't even loaded the ak4641 module.
19:06.03cr2do you have any working devices on the bus ?
19:14.44cr2pH5: unsigned int __iomem *iobase;
19:15.31cr2people writing such code should be fried alive ;)
19:16.43lkcldratdratdrATDRAT
19:17.40lkclok, leaving the ak4641 device up-and-running / initialised by setting A0 and A1 high in htcsable.c i can then do a detect on the i2c bus, and find the ak4641, and it's up-and-running.
19:18.02lkcli can even do an i2cdump 0 0x12 and scan it
19:20.20psokolovskywell, so yes, there appeas to be no magic bit to reset DMA subsystem in PXA ;-(
19:20.33cr2lkcl: A0 is some kind of "i2c enable" on the universal. maybe it's the same on sable ? btw, where is your RTC chip ?
19:20.49lkclcr2: oh - ah.  argh.  right
19:21.06lkcloh gawd that would do it, wouldn't it...
19:21.22lkclcr2: don't know.
19:21.31lkcl*sigh*.   i think it's time for me to put the camera back...
19:21.44lkclok am gonna do some disassembly...
19:22.00lkcli need two known devices on the bus to find out if you're right, cr2.
19:22.20lkclAH - yes.  yep.  that makes sense, cr2.  a lot of sense.
19:22.24cr2but i2cdetect does not show it ?
19:22.56cr2it is strange that you have an i2c RTC chip, and it is not connected.
19:23.02lkclno - because it's sticking out the back!!!
19:23.13cr2but it may be some evil plot. it can be connected to the BB.
19:23.22lkcli've seen two other devices on the bus - by mistake.
19:23.26lkcl0x50 and 0x57.
19:23.39cr2there is a small watch battery soldered in the motherboard on the universal.
19:23.51cr2hmm.
19:24.00cr2what was the chip name ?
19:24.13lkcl1sec...
19:24.31lkclrtc: R8564 EF096A - right next to ASIC3 drivers/i2c/chips/rtc8564.c
19:24.40cr2ok.
19:24.41lkclbrb am doing some surgery
19:24.46*** join/#htc-linux FossiFoo (n=Fossi@e176105224.adsl.alicedsl.de)
19:25.43cr2btw, this RTC driver is not in the hh.org CVS.
19:26.12cr2rtc8564.c is 0x51
19:27.04cr2the same as 2408w ?
19:27.45cr2maybe, you should trace the cam first.
19:32.31psokolovskycr2, what's that 2408w you talk about?
19:39.24cr2wifi eeprom
19:41.08lkclok let's see if i broke it
19:41.11lkclhaha
19:48.06cr2does it work ?
19:48.53lkclyehh
19:48.59lkclno smoke or anything.
19:49.04lkclgotta get ready soon am going out
19:49.12goxboxlivewhat?
19:49.23lkclstill getting UU in the 0x12 column
19:49.27goxboxliveis working?
19:49.38lkclcr2, can you do a .lst for me again on wavedev?
19:50.07lkcli'm getting exasperated with this
19:57.43cr2lkcl: done
19:57.50cr2what about the camera ?
19:59.32goxboxlivecr2: Even though i removed the depends in the detect-stylus the opie-image is still big. And especiallly after i added kphone/pi
19:59.43goxboxlive23.3 MB, but thats with all the developer stuff.
20:00.55goxboxliveYes what about the camera, lets make a driver. I can start. I choose the nake, htcuniversal_cam . Now the ball is your, you do the rest :-)
20:00.55cr2the developer stuff ?
20:01.10goxboxlivelmsensors, hcidump and so on
20:01.20cr2ok.
20:01.37cr2can asterisk be compiled too ?
20:02.07goxboxliveif it is in the oe i can. I doint knopw what it is, but i can take a look for it. hold on
20:03.10goxboxlivei am building it now
20:05.02goxboxliveit depends on libvorbis, i'll upload that to
20:05.10cr2ok.
20:11.10goxboxlivecr2: It's uploaded: asterisk where 7MB .
20:12.00cr2ok. we may reuse it later.
20:12.50goxboxliveI am trying it now. Is it a gui program??
20:21.19goxboxlivewell have no idea what it is
20:24.01goxboxlivecr2: About the the backlight. It reminds me of how it was right before you made it work in the .12. It behave the same.
20:24.04goxboxliveLike in Opie
20:25.11goxboxliveIThe backlight is dimming on/off(weak) in a cyclus i have in the opie-light-and-power.
20:30.35cr2good idea, i'll look at corgi-bl.c now.
20:34.55goxboxlivegood
20:40.19psokolovskySo well, this ak4641 thing si not conquerrable.
20:40.41psokolovskyLast thing I did, is read thru pxa27x man,
20:40.55psokolovskyfigureing out how to "reset" DMA registers,
20:41.06psokolovskyand added that code to kernel DMA init
20:41.10psokolovskystill the same...
20:42.29goxboxlivethis is strange, why did it work before?
20:46.04cr2psokolovsky: there was some dma priority patch recently ? can you revert it ?
20:46.09psokolovskygoxboxlive, when "before"?
20:46.29goxboxlivepsokolovsky , in the .12 xanadux kernel.
20:46.39psokolovskycr2, in may. i tried that. doesn't change anything accept chan# used
20:47.22psokolovskygoxboxlive, do you have binary? can you boot it right now? either way, I had a look at that code - many things have changed since then
20:47.52goxboxlivepsokolovsky: yes i bootet it a few days ago and tested the sound.
20:48.08psokolovskygoxboxlive, but if you will eb able to make that code run *now*, from source eventually, we'd have a thread to get us out of this crap
20:48.21psokolovskygoxboxlive, booted with haret?
20:48.27goxboxliveyes with haret
20:48.59psokolovskygoxboxlive, and sound worked?
20:49.25goxboxlivepsokolovsky: It is cr2 who has made the driver (or rewritten it) so i guess you bether talk to him about it.
20:49.40goxboxlivepsokolovsky: Sound worked as it should
20:50.05psokolovskygoxboxlive, well, we'd need recent first-hand witness first, you quilify ;-)
20:50.09Speedy2re
20:50.31psokolovskygoxboxlive, worked without any tricks like dancing on one leg while booting it? ;-)
20:50.32goxboxliveEven the mic worked, though it was recording kind of messy.
20:51.01goxboxlive:-) yes, right out of the kernel compilation. Cr2: What did you do with the .12 sounddriver so it worked?
20:51.50psokolovskygoxboxlive, so, you built the kernel you booted? and it was couple of days ago?
20:52.41goxboxlivepsokolovsky: I build the kernel/opie-image for about a half years ago, but nothing has changes in the .12 xanadux source three since.
20:53.17goxboxlivehere is the woeking images: http://gnulinux.biz/files//Universal/sd-mmc/2.6.12/
20:55.19psokolovskygoxboxlive, thanks, but I'd need exact tag/date of the source checkout this was built from
20:56.23goxboxlivepskolovsky: If you want, ican just recompile from cvs and try to boot it again to see if it still work?
20:57.03psokolovskygoxboxlive, actually, that would be preferred. would need fresh today's case, 100% reproducible
20:57.47psokolovskygoxboxlive, you see, xanadux appears to lack hx4700 support, so I'd need to port to it, and I want to be 100% sure it actually works now
20:58.01goxboxliveok i give it a  try
20:59.05goxboxliveok, i am updateing the cvs now. Just remember that .12 is not gcc-4.x compatibel
20:59.06goxboxliveuse 3.4 or 3.1
21:03.09*** join/#htc-linux lamikr|lap (n=chatzill@aragorn.kortex.jyu.fi)
21:03.25psokolovskygoxboxlive, yes, I have 3.4 for local builds (non-OE)
21:03.27psokolovskythanks
21:05.28goxboxlivekernel and modules successfully buildt, aplyijng them now and trying to boot :-)
21:11.46psokolovskyok, how it goes?
21:13.28goxboxliveit's booting
21:13.42goxboxlivedo you want to see some outputs?
21:14.04psokolovskyso far, I want to hear sound ;-)
21:17.11goxboxlivewell sounds works
21:17.24goxboxliveeven tapping on the opie screen is clicking
21:17.39goxboxlivesnd_pxa_i2sound_ngn_free_rate
21:17.39goxboxlivei2c_adapter i2c-0: master_send: writing 2 bytes.
21:17.39goxboxlivesnd_pxa_i2sound_ngn_free_rate
21:18.04goxboxliveis there other ways i can prove it?
21:18.32psokolovskygoxboxlive, so, it's CVS HEAD as of today, right?
21:18.37goxboxliveyes
21:19.06psokolovskygoxboxlive, and you don't changed CPU before running this, no? ;-))
21:19.23goxboxlive:-)
21:19.45goxboxlivei havnet done a thinng, just compiled and aplied to an earlier opie-image
21:19.53goxboxlivecvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/xanadux co -ko -r K2-6-12-hh2-xda0-un0 linux-2.6-xda
21:20.12psokolovskyok, so I will check out sound drivers from it and next time I'll be in mood, will try to forward port it...
21:20.15psokolovskyok, thanks
21:20.37psokolovskygoxboxlive, well, stop, you used HEAD or  -r K2-6-12-hh2-xda0-un0 ?
21:21.35goxboxliveI am using this: co -ko -r K2-6-12-hh2-xda0-un0 linux-2.6-xda but i guess cr2 is allways aplying to HEAD.
21:24.24psokolovskygoxboxlive, well, I need *exact* version which is known to work. And -r K2-6-12-hh2-xda0-un0 is even better actually.
21:24.56psokolovskySo, thanks for checking it once again for me! We'll see, how far I'll be able to go with this...
21:25.21goxboxlivewell i am using this one. The only fiffer is that i use my own username instead of anonymous cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/xanadux co -ko -r K2-6-12-hh2-xda0-un0 linux-2.6-xda
21:26.26psokolovskynp, that doesn't affect code ;-)
21:26.33goxboxlivei know
21:27.12goxboxliveeven alsamixer works, not with Opie though.
21:27.54goxboxlivepsokolovsky: xanadux has hx4700 support
21:28.34goxboxliveit might be outdated, but there is a hx4700 directory there
21:29.10psokolovskywell, I didn't see sound support exactly, but I'll check
21:29.56goxboxlivehttp://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/arch/arm/mach-pxa/hx4700/
21:40.32*** join/#htc-linux FossiFoo (n=Fossi@e176105224.adsl.alicedsl.de)
22:23.17goxboxliveWhen i run this speaker test it runs the whole thing, but when i try again it hangs. I have to reload the htcuniversal sounddriver again
22:23.19goxboxliveroot@htcuniversal:/etc/modutils$ speaker-test -D hw:0 -c2 -t sine
22:23.19goxboxlivespeaker-test 1.0.13
22:23.20goxboxlivePlayback device is hw:0
22:23.20goxboxliveStream parameters are 48000Hz, S16_LE, 2 channels
22:23.20goxboxliveSine wave rate is 440.0000Hz
22:23.21goxboxliveRate set to 48000Hz (requested 48000Hz)
22:23.23goxboxliveBuffer size range from 256 to 16384
22:23.25goxboxlivePeriod size range from 128 to 8192
22:23.27goxboxliveUsing max buffer size 16384
22:23.29goxboxlivePeriods = 4
22:23.33goxboxlivewas set period_size = 4096
22:23.36goxboxlivewas set buffer_size = 16384
22:23.37goxboxlive<PROTECTED>
22:23.39goxboxlive<PROTECTED>
22:23.41goxboxliveTime per period = 5.800739
22:23.43goxboxlive<PROTECTED>
22:23.45goxboxlive<PROTECTED>
22:23.47goxboxliveTime per period = 5.998818
22:23.49*** part/#htc-linux RoEn_PC (n=roen@p54A67710.dip.t-dialin.net)
22:23.50goxboxlive<PROTECTED>
22:23.51goxboxlive<PROTECTED>
22:23.53goxboxliveTime per period = 5.998805
22:23.56goxboxlive<PROTECTED>
22:23.57goxboxlive<PROTECTED>
22:23.59goxboxliveTime per period = 5.998805
22:24.01goxboxlive<PROTECTED>
22:24.05goxboxlive<PROTECTED>
22:24.07goxboxliveTime per period = 5.998825
22:24.09goxboxlive<PROTECTED>
22:24.11goxboxlive<PROTECTED>
22:24.13goxboxliveTime per period = 5.998867
22:24.15goxboxlive<PROTECTED>
22:24.17goxboxlive<PROTECTED>
22:24.19goxboxliveBut still no sound, juss a buzz and some ticking.
22:27.29Speedy2Is it possible the channel(s) are muted?
22:28.01goxboxlivehmm
22:28.26goxboxlivewell, when i amusing alsmixer the sound is on, buthow do i check if they are?
22:28.28Speedy2If I mute a channel on my equipment, I can hear slight ticking when the channel is activated.
22:28.40Speedy2goxboxlive:  It's possible something within the initalization of that sound chip is off
22:28.44goxboxliveIf it is that easy i throw my self down in the toilett
22:29.01Speedy2Well, I'm not saying that's what it is.  But that is a possibility.
22:29.13Speedy2What's the model chip?
22:29.18Speedy2ak something?
22:29.28goxboxlivehold on
22:30.06goxboxliveak4641
22:31.56Speedy2It has stereo out and mono out
22:32.49goxboxliveyes, the monois the phone speaker and the stereo is the main pda speaker
22:33.47Speedy2There is a "softmute" function on this unit
22:34.33goxboxliveok, and how do i activate/deactivate it.
22:35.13*** join/#htc-linux doepiedoe (n=doepiedo@84-53-96-51.fiber.unet.nl)
22:35.33cr2goxboxlive: does the lcd suspend work correctly in .12 ?
22:36.16goxboxlivecr2: Yes it shuts all off when the machine is not used for a while
22:36.27cr2ok.
22:37.52Speedy2Look at page 27 of the spec
22:37.52Speedy2one sec
22:38.00Speedy2http://www.handhelds.org/platforms/hp/ipaq-hx47xx/ak4641.pdf
22:38.27Speedy2It's 0x06 in the register control
22:40.51cr2psokolovsky: can we revive the .12 driver ?
22:41.32psokolovskycr2, well, I'm going to try that if noone else beat me on that
22:41.57psokolovskycr2, but it's not like "driver", it's the whole infrastructure, so it won't be easy...
22:42.15cr2i don't see any other option. i'm already running the .12 touchscreen driver.
22:42.17cr2hmm.
22:46.22cr2psokolovsky: you should be beaten with a big thick stick :)
22:46.43cr2asic3_set_gpio_out_b ... 1<<GPIOD_FL_PWR_ON
22:46.56psokolovskycr2, for what? ;-)
22:47.11psokolovskycr2, did I make a typo?
22:47.22cr2i want more error-resistant asic3 functions. fuck that.
22:47.33*** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
22:47.34cr2gpio_b for D gpio.
22:47.56psokolovskycr2, we should have thru-numbering, period
22:48.01psokolovskycr2, what file?
22:48.02cr2agreed.
22:48.16cr2htcuniversal_bl.c
22:49.41psokolovskycr2, aa-a-ah! ;-E poor guys. who'd know it turns out a "bear's service", speaking russian ;-)
22:49.53cr2;)
22:50.04psokolovskysorry!!
22:50.13cr2i think the api is too lowlevel.
22:50.26cr2i have made such mistakes too.
22:50.29psokolovskyyep
22:56.23cr2corgi-bl is still not doing the right thing. the proper pxa-pwm driver should handle the ALT gpio settings on resume.
23:00.06psokolovskycr2, are they reset for you or what?
23:00.36cr2goxboxlive: can you compile the newest kernel ?
23:01.06cr2i think each driver should handle its own resources itself, and not rely on some other code.
23:01.23goxboxliveyes, but do you know why my laptop is getting so damn slow after i have compiled a kernel. It's getting so slow that i have to reboot it.
23:01.50cr2dmesg ?
23:02.02psokolovskycr2, well, cpu registers across suspend should preserve CPU core code at all. so, I still don't understand what issue you have
23:02.29psokolovskycr2, Kevin2 yesterday had only good things to say after trying it on apache
23:02.48psokolovskyso I still wonder is there some bug...
23:03.22cr2well, the code is so simple there, nothing can be wrong :)
23:03.40cr2it's more about working code vs. "the right thing"
23:04.08psokolovskyyep, exactly. and for Kevin2 it out if the box worked right, better than old code (for me and other ports too)
23:04.25cr2i have problems with it being used on blueangel
23:04.52cr2the pwm setup there is much more complicated.
23:05.01psokolovskycr2, well, just one thing - only today I talked with one of palm guys, and tehy have exactly pxapwm_bl driver, which they'd like to mainline/offer for use
23:05.27psokolovskybut it's the same idea as crorgi_bl, as far as I can tell
23:06.39cr2_bl is more of some addon. the pwm is handhled now by the device-specific driver itself.
23:06.54cr2corgi_bl is calling set_intensity. that's it.
23:07.26cr2and some zaurus-specific stuff, irrelevant on other devices.
23:07.39psokolovskycr2, exactly, and that's what nice in it. I can't get what you have such that you can't do in that set_intensity()
23:09.12cr2i can, but then the purpose on corgi_bl is not really clear to me, if i do almost everything in the device-specific driver myself.
23:09.20goxboxlivecr2: You made it, the lcd swith off now when closing lid :-)
23:09.56cr2goxboxlive: great. but probably it should suspend on closing lid ?
23:10.11goxboxliveNow, that's a OPie setting
23:10.16cr2ok.
23:10.24psokolovskycr2, it's generic BL driver for PDA, that's its purposed. and it does handle some useful/important, but boring thing, saving you from that
23:10.29goxboxlivegreat work
23:10.41cr2maybe you want to run sendmail/apache on universal :)
23:11.17cr2psokolovsky: then it should be cleaned from zaurus-specific stuff.
23:12.22cr2and be located in some other directory.
23:12.33psokolovskycr2, yes, that was suggested to its maintainer, and in his q. so let's bother with cleaning up our stuff, and let him do his ;-)
23:13.09psokolovskycr2, brr, but it's in drivers/video/backlight, what's wrong with that?
23:14.10cr2really ?
23:14.42psokolovskyyep, where it should be?
23:14.54cr2ah. ok.
23:15.46cr2because all other corgi_* files are in arch/arm/mach-pxa
23:16.09cr2which is, hmm, strange.
23:17.14psokolovskycr2, they are savage people, they don't have drivers/soc/ in mainline ;-)
23:17.28goxboxliveOk, back to the sound. In .12 the kernel bootup doesnt do this: It has only reset once, not twice as here.
23:17.30goxboxlive<5>snd_htcuniversal_audio_set_codec_reset: 1
23:17.31goxboxlive<5>snd_htcuniversal_audio_set_codec_power: 1
23:17.31goxboxlive<5>snd_htcuniversal_audio_set_codec_reset: 0
23:19.27goxboxliveAnd man, there where a lot of debug message now during boot
23:19.37cr2goxboxlive: we don't have reset.
23:21.01goxboxliveBut why doesn it do this then? Why just we dont remove the reset stuff. The more taht there is in the code, the more confused we get. right?
23:23.57cr2i don't know how to call the reset. at least it can't be observed in wince.
23:24.10cr2and it works without it.
23:24.37*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.179)
23:29.51goxboxliveok
23:37.53Speedy2goxboxlive:  Any luck?
23:38.02Speedy2Can you write some code that sends the data directly over the I2S link?
23:38.06Speedy2i.e. bypass alsa.
23:38.37goxboxliveno
23:38.41Speedy2Why not?
23:40.39goxboxliveSpeddy2 I am not a programer, so i dont have the skills to do that. But explain for cr2, maybe he has some good answers. ( i just test the codes, i am kamikaze user) :-)
23:41.13Speedy2Ok.  Well cr2, my idea is to write a small program that sends the sine wave data directly to the ak CODEC via it's I2S link, bypassing ALSA and everything else
23:41.21goxboxliveAs you can see, i have a lot of typos, it wouldhave been a code that never had worked :-)
23:41.22Speedy2That will allow one to figure out if the chip is initalized correctly, etc.
23:41.58Speedy2One can just use a sinewave table and keep looping
23:42.15Speedy2If I had hardware, I would personally do this
23:44.38psokolovskySpeedy2, complexity of that is much higher than diagnoze and fix problem in existing driver which is known to work under some conditions
23:45.17psokolovskySpeedy2, so, unless someone iis 2s/i2c/sound codec wizard, it's just waste of time
23:45.43psokolovskySpeedy2, on the other hand, *Linux* should provide such ability in easy way. alas, it doesn't
23:49.28cr2psokolovsky: Kevin2 has spi.c tool in his svn. i2s is very similar.
23:50.50psokolovskycr2, I bet it is ;-) but we have driver which works for otehr people and doesn't work for us, and we can't find what's wrong. do you think that writing something anew will be easier?
23:51.03*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.179)
23:51.06cr2no.
23:52.06psokolovskyI of course would be happy to just do cat /dev/random >/dev/i2s ;-)
23:55.30Speedy2I didn't realize the driver was known to work in other conditions.
23:58.06psokolovskySpeedy2, yes, bd2, hx4700 guy, got it running on 2.6.18 with flash boot.
23:58.19Speedy2On an HTC or the hx4700?
23:58.47psokolovskyhx4700
23:59.16Speedy2Bizarre that it's not working here
23:59.25Speedy2Let me check the data sheet

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.