irclog2html for #nslu2-linux on 20061030

`00:32.08`	`*** join/#nslu2-linux kfm82ibook (n=kfm82@stanmade.dialup.fu-berlin.de)`
`00:55.34`	`*** join/#nslu2-linux kfm82 (n=kfm82@p54BEF7F7.dip.t-dialin.net)`
`00:57.40`	`GPSFan`	`[g2]: ping.. how did your bonnie tests go?`
`03:02.49`	`CIA-8`	`03rwhitby * r4333 10optware/trunk/make/libftdi.mk: libftdi: Fixed the section field.`
`03:20.03`	`GPSFan`	`[g2]: found a problem with the realtime clock. "hwclock --show" returns: # hwclock --show`
`03:20.04`	`GPSFan`	`hwclock: ioctl() to /dev/rtc to turn on update interrupts failed unexpectedly, errno=25: Inappropriate ioctl for device.`
`03:21.16`	`GPSFan`	`wheras it works ok on the supplied kernel.`
`03:24.40`	`[g2]`	`GPSFan bonnin++ runs fine`
`03:26.14`	`GPSFan`	`great! trying to track down this rtc issue.`
`03:28.09`	`GPSFan`	`[g2]: so adding the delays to the cf driver did the trick?`
`03:30.24`	`[g2]`	`GPSFan yeah`
`03:30.28`	`*** join/#nslu2-linux Dsbeerf (n=Dsbeerf@about/networking/255.255.255.255/Dsbeerf)`
`03:30.42`	`[g2]`	`I'll touch base with GW on Monday about that`
`03:31.09`	`Dsbeerf`	`Hi, someone know if unslug can run on DNS-120 device ?`
`03:31.09`	`[g2]`	`there was data corruption without them`
`03:31.58`	`[g2]`	`that's what was causting the boot issues earlier today`
`03:32.13`	`[g2]`	`s/causting/causing/`
`03:33.58`	`[g2]`	`Dsbeerf do you know what's inside the DNS-120 ? I that the dlink-box ?`
`03:34.05`	`[g2]`	`Is`
`03:34.15`	`GPSFan`	`[g2]: good to hear about th ecf driver being more stable. with the supplied kernel which looks like it uses the same rtc driver hwclock works fine, it's the 2.6.19-rc3 build that doesn't work. both are BE`
`03:34.26`	`Dsbeerf`	`Yes is a dlink but what i have to know what is inside the box what you mean ?`
`03:34.40`	`[g2]`	`Dsbeerf which processor`
`03:34.55`	`Dsbeerf`	`Oh dunno i have to open the box ?`
`03:35.17`	`[g2]`	`Dsbeerf or look on google`
`03:35.24`	`Dsbeerf`	`k thanks`
`03:39.03`	`[g2]`	`Dsbeerf http://www.dns120-linux.org/pmwiki/pmwiki.php?n=Info.Index`
`03:40.02`	`Dsbeerf`	`yeah i found that one im reading it`
`03:40.44`	`[g2]`	`Dsbeerf google is your friend :)`
`03:40.52`	`Dsbeerf`	`hehe yeah :P`
`03:42.03`	`[g2]`	`GPSFan ok so you don't have /dev/rtc setup on your rootfs`
`03:42.41`	`[g2]`	`GPSFan have you kicked the oscillator ?`
`03:43.09`	`[g2]`	`often it's not running as the RTC is in deep power down`
`03:44.55`	`GPSFan`	`[g2]: /dev/rtc is there in both cases. it is even the same rootfs. the clock runs, and either kernel can read the date/time via the /sys/class interface. However hwclock --show doesn't work on 2.6.19 and does on 2.6.15-??`
`03:45.37`	`GPSFan`	`[g2]: there seems to be something wrong with the ioctl interface on 2.6.19.`
`03:47.06`	`[g2]`	`GPSFan ok I'll take your word for it on BE 2.6.19-rc3`
`03:47.39`	`[g2]`	`<PROTECTED>`
`03:47.39`	`[g2]`	`Mon Oct 30 03:43:33 2006 -1.025484 seconds`
`03:47.44`	`[g2]`	`things run fine LE`
`03:47.56`	`[g2]`	`and it works fine on 2.6.18`
`03:48.01`	`[g2]`	`LE`
`03:48.32`	`[g2]`	`what happens when you run with the --debug option ?`
`03:49.12`	`GPSFan`	`[g2]: same error message.`
`03:49.44`	`GPSFan`	`# hwclock --debug`
`03:49.44`	`GPSFan`	`hwclock 2.4c/util-linux-2.11a`
`03:49.44`	`GPSFan`	`Using /dev/rtc interface to clock.`
`03:49.44`	`GPSFan`	`Assuming hardware clock is kept in local time.`
`03:49.44`	`GPSFan`	`Waiting for clock tick...`
`03:49.45`	`GPSFan`	`hwclock: ioctl() to /dev/rtc to turn on update interrupts failed unexpectedly, errno=25: Inappropriate ioctl for device.`
`03:50.23`	`[g2]`	`ok`
`03:51.10`	`GPSFan`	`oh well, almost time for zzz anyway. gotta get up early tomorrow. cul...`
`03:51.45`	`[g2]`	`GPSFan talk to dwery in the AM. He wrote the original driver`
`03:51.56`	`[g2]`	`and got it pushed upstream.`
`03:52.49`	`[g2]`	`joshin around ?`
`03:53.07`	`GPSFan`	`[g2]: ok, I'm hoping it's just another be/le issue I might try building a 2.6.18 version just to have a reference.`
`03:53.13`	`[g2]`	`GPSFan I'd also check with joshin as he's running BE on gentoo`
`03:53.17`	`[g2]`	`with 2.6.18`
`03:53.44`	`GPSFan`	`does his ethernet work?`
`03:53.52`	`[g2]`	`think so`
`03:54.21`	`[g2]`	`but he has a slug so the RTC is different`
`03:54.29`	`GPSFan`	`yeah, the 2.6.19 port needs some tlc.`
`03:54.55`	`GPSFan`	`ah, I can't spare either of my slugs to experiment with.`
`03:55.37`	`[g2]`	`GPSFan later this week I may get around to running BE`
`03:55.49`	`[g2]`	`I'm working on setting up my regression lab`
`03:56.19`	`[g2]`	`today I was DHCPing an IP addr from RedBoot`
`03:57.17`	`[g2]`	`so I'll be able to see when the boxes reboot as they first ask for an IP from RedBoot, then again from Linux`
`03:58.19`	`[g2]`	`GPSFan it's not in the repo, but there's an eeprom notifer patch the uses the MAC in the EEPROM`
`03:58.19`	`GPSFan`	`so redboot on the avila/loft supports giving out dhcp addresses?`
`03:58.36`	`[g2]`	`in RedBoot? sure.`
`03:58.57`	`[g2]`	`oops... giving out ?`
`03:59.23`	`[g2]`	`I'm running dnsmasq on another Loft that's giving out the addresses`
`03:59.23`	`GPSFan`	`that would be good, this random mac address is not cool when you have an eeprom on board for that purpose.`
`04:00.30`	`[g2]`	`right. The proper upstream support of that needs to be fully worked about. But this patch works fine and stuff the EEPROM addr in on the ifconfig up if it's not already sest`
`04:00.33`	`[g2]`	`set`
`04:01.36`	`GPSFan`	`so that is not the 45-eeprom-notifierxxxxx patch in svn.`
`04:02.36`	`[g2]`	`I didn't know if blaster8 pulled it out`
`04:03.50`	`[g2]`	`GPSFan I think the mac patch is missiing`
`04:04.11`	`[g2]`	`GPSFan there are two cases`
`04:04.20`	`GPSFan`	`[g2]: looking at tht 45 patch in svn, it doesn't grab the mac address`
`04:04.23`	`[g2]`	`1) when you run the IXP drivers as a module`
`04:04.38`	`[g2]`	`2) when you run built-in`
`04:05.37`	`GPSFan`	`yeah, I can see issues developing differently in each case.`
`04:06.53`	`[g2]`	`what happens is the built-in runs way before the EEPROM subystem`
`04:07.05`	`[g2]`	`so the driver is up long before the notifier runs`
`04:07.28`	`[g2]`	`consequently, it thinks there's no platform MAC and uses a random one`
`04:07.41`	`GPSFan`	`yes it would see tha mac address as undefined, all zeros/random or who knows what.`
`04:08.00`	`[g2]`	`right the test for all zeros causes the generation of the random mac`
`04:08.29`	`GPSFan`	`which can then be replaced by a script that init's the interface`
`04:08.41`	`[g2]`	`in the case of the module, by the time it runs the EEPROM notifier has already filled in the value`
`04:09.21`	`[g2]`	`well a script works if you don't mind having random mac traffic on the net for a while and bouncing the interface`
`04:10.16`	`[g2]`	`personally, I did the "wrong thing" in the patch by checking when the device interface is brought up`
`04:10.28`	`GPSFan`	`random mad addresses are not cool.`
`04:11.15`	`[g2]`	`so until the proper upstream is all worked out, I'll use the notifier + ixmac_open hack`
`04:11.24`	`GPSFan`	`question: why isn't the eeprom/i2c system real early in the kernel boot to overcome this problem?`
`04:12.25`	`[g2]`	`it's a good but somewhat mute question`
`04:12.40`	`[g2]`	`s/mute/moot/`
`04:12.54`	`GPSFan`	`yeah, I know, ours is not to reason why....`
`04:13.11`	`[g2]`	`no I don't mean that`
`04:13.55`	`[g2]`	`I mean I'm not sure exactly how the module depenancies run. I'd guess on compiler linkage`
`04:13.55`	`GPSFan`	`well, it's not in our hands to determine that kind of kernel startup sequencing.`
`04:14.24`	`[g2]`	`well for the Loft and possibly the Avila platform we might be able to tweak it`
`04:15.00`	`[g2]`	`but I haven't really seen anything in the kernel about module ordering (nor have I looked at all)`
`04:15.02`	`GPSFan`	`IIRC ther is a list built that gets run through by /init/main.c`
`04:15.52`	`[g2]`	`GPSFan I know there's a list somewhere :) either explicitly or implicity`
`04:16.39`	`GPSFan`	`I'll look at it tomorrow... uh.. maybe the next day. I've instrumented the kernel startup process before, so it shouldn't be too hard to stumble across again. ;>)`
`04:17.54`	`[g2]`	`GPSFan we'll I've got working patches for the other stuff`
`04:18.41`	`[g2]`	`that's actually the very next thing on my list now that the CF is running stable`
`04:18.43`	`*** join/#nslu2-linux mwester (n=mwester@nslu2-linux/mwester)`
`04:19.24`	`GPSFan`	`ok, good, well it's off to zz land cu tomorrow or the next day..`
`04:19.41`	`[g2]`	`sweet dreams`
`04:19.59`	`GPSFan`	`;>)`
`04:20.02`	`*** part/#nslu2-linux GPSFan (n=kenm@12.10.255.248)`
`04:46.50`	`*** join/#nslu2-linux DrZimmerman (n=theo@84-72-181-62.dclient.hispeed.ch)`
`05:13.43`	`rwhitby`	`Any developers with ssl client certs in the house today?`
`05:14.53`	`*** join/#nslu2-linux rwhitby-nslu2 (i=www-data@nslu2-linux/rwhitby)`
`05:15.06`	`*** part/#nslu2-linux rwhitby-nslu2 (i=www-data@nslu2-linux/rwhitby)`
`05:15.59`	`*** join/#nslu2-linux nSiclair73de (n=Sinclair@p54A0AA98.dip0.t-ipconnect.de)`
`05:23.57`	`[g2]`	`rwhitby you mean the ones you sent out ?`
`05:24.45`	`rwhitby`	`yep`
`05:25.31`	`rwhitby`	`can you test http://cgiirc.nslu2-linux.org (our new developer-only IRC web gateway)`
`05:26.19`	`rwhitby`	`It should ask you for your cert.`
`05:28.12`	`[g2]`	`rwhitby it doesn't it asks for a password`
`05:28.26`	`[g2]`	`did you want a https: ?`
`05:28.53`	`rwhitby`	`http:// should redirect to https://`
`05:28.54`	`[g2]`	`and there's mention that the cert is for limax not cgiirc`
`05:29.23`	`rwhitby`	`yeah, I just need to update the server cert`
`05:29.57`	`[g2]`	`I get a request for a master password`
`05:30.06`	`rwhitby`	`that's your browser`
`05:30.55`	`rwhitby`	`that's your client browser private key storage password (FireFox calls it your master password)`
`05:31.55`	`[g2]`	`yeah that thingy`
`05:32.26`	`rwhitby`	`it should get your real name from your certificate now too`
`05:32.59`	`[g2]`	`I set that like 6-9 months ago and dunno what it is`
`05:34.32`	`[g2]`	`rwhitby the cert setup for checkins and trac is nice`
`05:36.12`	`*** join/#nslu2-linux goetter_ (n=goetter@cpe-24-58-4-206.twcny.res.rr.com)`
`05:41.13`	`eno`	`rwhitby: i'm not sure i understand the question you asked me?`
`05:49.29`	`rwhitby`	`[g2]: the server cert name mismatch should be gone now`
`05:50.04`	`rwhitby`	`eno: we need a way to determine (at run-time, in an /opt/etc/init.d/SXXfoo script for instance) what optware target we are running on`
`05:50.16`	`rwhitby`	`so we can do specific stuff for specific targets.`
`05:50.36`	`rwhitby`	`e.g. for the fsg-3, you need to punch the firewall with iptables commands for certain programs.`
`05:50.48`	`[g2]`	`rwhitby the mismatch is gone`
`05:51.54`	`eno`	`ok, assuming we don't ever share binaries between optware targets`
`05:52.38`	`eno`	`during build time, we can echo $(OPTWARE_TARGET) > /opt/etc/somefile`
`05:53.38`	`eno`	`or echo "OPTWARE_TARGET=$(OPTWARE_TARGET)" > /opt/etc/somefile`
`05:53.59`	`eno`	`or prepend the above string in /opt/etc/init.d/SXXfoo`
`05:54.20`	`eno`	`then the string can check`
`05:54.21`	`rwhitby`	`aha - so for an Sxxfoo script, you could do that echo to the file, and the cat the real file after it.`
`05:54.25`	`rwhitby`	`snap`
`05:54.38`	`eno`	`s/the string/the script/`
`05:56.50`	`rwhitby`	`ok, I'll do that`
`05:57.10`	`rwhitby`	`I'll also update the template`
`06:27.27`	`CIA-8`	`03bzhou * r4334 10optware/trunk/make/libgmp.mk: libgmp: added libgmp-host-stage for swi-prolog`
`06:28.03`	`CIA-8`	`03bzhou * r4335 10optware/trunk/make/swi-prolog.mk: swi-prolog: share host build`
`07:03.03`	`*** join/#nslu2-linux Tobbe (n=tobbe@kbhn-vbrg-sr0-vl203-120.perspektivbredband.net)`
`07:05.27`	`*** join/#nslu2-linux rwhitby (n=rwhitby@nslu2-linux/rwhitby)`
`07:11.49`	`CIA-8`	`03bzhou * r4336 10optware/trunk/make/perl.mk: perl: share host build`
`07:15.55`	`eno`	`g'nite`
`07:41.21`	`*** join/#nslu2-linux blaster8 (n=blaster8@jeharrap.joh.cam.ac.uk)`
`08:31.53`	`*** join/#nslu2-linux CieD (n=CieD@host86-136-77-105.range86-136.btcentralplus.com)`
`09:15.06`	`*** join/#nslu2-linux kolla (i=kolla@firda.uninett.no)`
`09:21.23`	`*** join/#nslu2-linux bullet (n=bullet@240.29.79.83.cust.bluewin.ch)`
`09:32.24`	`*** join/#nslu2-linux blaster8 (i=www-data@limax.nslu2.osuosl.org)`
`09:33.28`	`blaster8`	`exit`
`09:47.10`	`*** join/#nslu2-linux mithro (n=tim@ppp246-117.static.internode.on.net)`
`09:48.19`	`*** join/#nslu2-linux vmaster_ (n=vmaster@p549B5EDC.dip.t-dialin.net)`
`10:58.18`	`*** join/#nslu2-linux eiffel_ (n=eiffel@pD9571201.dip0.t-ipconnect.de)`
`11:41.05`	`*** join/#nslu2-linux rwhitby (n=rwhitby@nslu2-linux/rwhitby)`
`11:42.41`	`*** join/#nslu2-linux oleo (n=leon@193.2.111.14)`
`11:45.02`	`*** join/#nslu2-linux p0g0_ (n=pogo@madwifi/support/p0g0)`
`12:09.43`	`*** join/#nslu2-linux kolla_ (i=kolla@eduroam-dhcp10.uninett.no)`
`12:43.47`	`*** join/#nslu2-linux kolla__ (n=kolla@firda.uninett.no)`
`13:08.03`	`*** join/#nslu2-linux Cheef-Daniel (n=chatzill@pD95065BB.dip0.t-ipconnect.de)`
`13:14.23`	`*** join/#nslu2-linux Cheef-Daniel (n=chatzill@pD95065BB.dip0.t-ipconnect.de)`
`13:50.09`	`*** join/#nslu2-linux [g2] (n=g2@nslu2-linux/g2)`
`15:00.22`	`*** join/#nslu2-linux jbot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt)`
`15:00.22`	`*** topic/#nslu2-linux is nslu2-linux developer channel - use #nslu2-general for end-user questions`
`15:25.19`	`*** join/#nslu2-linux ByronT (i=byron-po@nslu2-linux/ByronT)`
`15:39.04`	`CIA-8`	`03bzhou * r4337 10optware/trunk/Makefile: swi-prolog broken on mss and ts72xx`
`15:40.45`	`*** join/#nslu2-linux yvasilev (n=yvasilev@dune.math.cinvestav.mx)`
`15:58.45`	`[g2]`	`quiet morning`
`16:08.09`	`*** join/#nslu2-linux HopsNBarley (n=andy24@pool-71-116-78-114.snfcca.dsl-w.verizon.net)`
`16:17.55`	`mwester`	`It's Monday...`
`16:19.30`	`drif`	`dreaded bloody monday`
`16:33.44`	`NAiL`	`heh`
`16:33.58`	`NAiL`	`easy to remember too`
`16:34.40`	`NAiL`	`63-24-24-24N, 10-25-25-25E waits for icbm`
`16:38.46`	`*** join/#nslu2-linux kfm82ibook (n=kfm82@p54BED95A.dip.t-dialin.net)`
`16:51.52`	`*** join/#nslu2-linux Dsbeerf (n=Dsbeerf@about/networking/255.255.255.255/Dsbeerf)`
`16:55.54`	`*** join/#nslu2-linux l0c4lh0st (n=a@j147098.upc-j.chello.nl)`
`16:58.45`	`*** part/#nslu2-linux osas (n=osas@CPE0016b62ceb5a-CM000f9fa84bec.cpe.net.cable.rogers.com)`
`17:03.43`	`*** join/#nslu2-linux osas (n=osas@CPE0016b62ceb5a-CM000f9fa84bec.cpe.net.cable.rogers.com)`
`17:04.15`	`*** join/#nslu2-linux pleemans (n=peter@d51A5E421.access.telenet.be)`
`17:04.29`	`*** join/#nslu2-linux GPSFan (n=kenm@12.10.255.248)`
`18:01.21`	`*** join/#nslu2-linux CieD (n=CieD@81.168.95.39)`
`18:15.59`	`*** join/#nslu2-linux AdamBaker (n=aab@userch028.dsl.pipex.com)`
`18:16.47`	`*** join/#nslu2-linux dwery (n=dwery@nslu2-linux/dwery)`
`19:07.22`	`Kaloz`	`hmz.. anyone running on an avila board?`
`19:10.43`	`dwery`	`sorry.. only Loft here..`
`19:17.02`	`GPSFan`	`Kaloz: I'm running an avila. been working on various issues in 2.6.19-rc3`
`19:18.07`	`Kaloz`	`GPSFan: can you tell me what machtype does the redboot set on it?`
`19:19.10`	`GPSFan`	`Kaloz: my redboot sends 245 (0xf5) as the machine type, I changed mach-types for avila from 546 to 245 as a temporary fix.`
`19:20.10`	`Kaloz`	`bugger.. i knen that some vendor stupidity is playing tricks on me :p`
`19:21.19`	`nbd`	`does anybody know a nice page that describes what needs to be configured when compiling redboot for xscale?`
`19:21.23`	`GPSFan`	`g2 said the other day that he had some sort of "shim" that resolved that issue`
`19:21.54`	`nbd`	`i have a wrv54g compatible board that runs this openrg boot loader crap, which i'd like to replace`
`19:21.55`	`GPSFan`	`nbd: g2 has done it, he'd be the one to ask.`
`19:22.00`	`nbd`	`ok, thanks`
`19:22.18`	`nbd`	`[g2]? :)`
`19:22.25`	`GPSFan`	`nbd: yes..`
`19:22.55`	`nbd`	`was just writing it to get his attention when he's back :)`
`19:23.19`	`GPSFan`	`;>)`
`19:27.38`	`GPSFan`	`dwery: have you had any problems with the rtc? on loft? I'm able to read it via the /sys/class interface, but when I try to use hwclock--show I get: # hwclock --show`
`19:27.39`	`GPSFan`	`hwclock: ioctl() to /dev/rtc to turn on update interrupts failed unexpectedly, errno=25: Inappropriate ioctl for device.`
`19:28.09`	`dwery`	`GPSFan: sometimes hwclock is pesky... do you have UIE emulation turned on?`
`19:28.40`	`GPSFan`	`dwery: I'll have to check. just a min...`
`19:29.01`	`dwery`	`it's something like CONFIG_RTC_UIE`
`19:29.33`	`GPSFan`	`dwery: no I don't. I'll turn it on and try again..`
`19:30.08`	`[g2]`	`nbd ?`
`19:30.49`	`nbd`	`hi. GPSFan told me you might have some experience with compiling redboot for xscale`
`19:31.07`	`nbd`	`so i was wondering whether you could help me with it so i can get rid of this rgloader garbage`
`19:31.08`	`[g2]`	`nbd yeah I've got a full tree`
`19:31.18`	`nbd`	`it's a wrv54g compatible board`
`19:31.25`	`nbd`	`(gemtek)`
`19:31.38`	`[g2]`	`ok`
`19:32.26`	`[g2]`	`nbd running old or new 1.9x or 2.0x`
`19:33.37`	`[g2]`	`nbd do you have JTAG ?`
`19:33.45`	`nbd`	`yep`
`19:33.52`	`GPSFan`	`dwery: turning UIE emulation on worked like a charm, thanks..`
`19:34.19`	`nbd`	`i bricked this thing once, tried a few redboot binaries that didn't work, then flashed back to the old rgloader`
`19:34.24`	`[g2]`	`GPSFan congrats! dwery is THE MAN!`
`19:34.58`	`GPSFan`	`[g2]: indeed, now if I can only get the eternet & madwifi running.`
`19:35.01`	`dwery`	`GPSFan: it should work without it but sometimes hwclock is strange`
`19:35.17`	`dwery`	`it should recognize that the device has no rtc interrupts and go back polling mode`
`19:35.32`	`dwery`	`which hwclock --version do you have?`
`19:35.54`	`GPSFan`	`dwery: it worked ok on the 2.6.15-? kernel that came with the avila, but not on 2.6.19-rc3. ..go figure..`
`19:35.58`	`dwery`	`can't help with ethernet... either new microcode or driver 's author required`
`19:36.11`	`dwery`	`.15 did have my new rtc subsystem :)`
`19:36.17`	`dwery`	`s/did/did not/`
`19:36.20`	`GPSFan`	`# hwclock --version`
`19:36.20`	`GPSFan`	`hwclock 2.4c/util-linux-2.11a`
`19:37.28`	`[g2]`	`nbd so what's the plan ? I'm guessing you don't have JTAG debugging or you could just debug the Redboot`
`19:37.45`	`[g2]`	`how far does it get ? The "+" is damn early`
`19:37.46`	`nbd`	`i've never used jtag for debugging`
`19:37.49`	`GPSFan`	`dwery: thanks anyway, I'll keep plugging along. maybe [g2] can help with the madwifi issues.`
`19:38.02`	`dwery`	`GPSFan: months ago madwifi was working quite fine`
`19:38.05`	`[g2]`	`GPSFan what's the issue with madwifi ?`
`19:38.05`	`dwery`	`on my nas100d`
`19:38.06`	`nbd`	`the last image that i tried warned about missing flash settings`
`19:38.07`	`nbd`	`then hangled`
`19:38.11`	`nbd`	`hanged`
`19:38.28`	`*** join/#nslu2-linux norm- (i=norm@mind.your.own.biz.tm)`
`19:38.37`	`nbd`	`and i didn't compile it myself, so i guess it needs to be configured for the target`
`19:38.42`	`GPSFan`	`dwery: I'm sure it was, this is a 2.6.19 issue, several in fact.`
`19:38.54`	`[g2]`	`nbd well that's what boot loaders do :)`
`19:38.55`	`nbd`	`[g2]: what toolchain and redboot source would you recommend?`
`19:39.24`	`nbd`	`i want to build my own and configure it for the target to see if it works out better`
`19:40.55`	`[g2]`	`nbd I'm using ./gcc --version`
`19:40.55`	`[g2]`	`gcc (GCC) RedHat-3.3 20021213`
`19:40.55`	`[g2]`	`<PROTECTED>`
`19:41.04`	`GPSFan`	`[g2]: first issue is that the recomended version of madwifi: madwifi-ng-r1503-20060415 wants include/linux/config.h in various places. 2.6.19-rc3 has removed it.`
`19:41.08`	`[g2]`	`I haven't played with other toolchains`
`19:41.29`	`[g2]`	`GPSFan start with r 1710`
`19:41.54`	`[g2]`	`that's before the wackelf stuff`
`19:42.09`	`nbd`	`where can i get it? the intel site only links to a weird libc4-linked one that i can't get to work`
`19:42.20`	`[g2]`	`it's from RedHat`
`19:42.21`	`GPSFan`	`[g2]: I tried madwifi-ng-r1770-20061025 nd it's complaining about xscale-be-elf.hal.o uses VFP instructions, whereas /home/kenm/GW2348-4/buildroot/build_armeb/madwifi-ng-r1770-20061025/ath_hal/ath_hal.o does not`
`19:42.38`	`[g2]`	`GPS you need to run the wackelf tool`
`19:42.54`	`GPSFan`	`[g2]: wackelf??`
`19:43.04`	`Kaloz`	`GPSFan: madwifi/tools/whackef iirc`
`19:43.09`	`[g2]`	`to clean up the VFP stuff in the ELF headers`
`19:43.22`	`[g2]`	`yeah Kaloz is pointing in the right direction`
`19:43.22`	`GPSFan`	`Kaloz: ah, I'll rtfm..`
`19:46.21`	`[g2]`	`GPSFan do you have a punchlist for BE ?`
`19:46.26`	`GPSFan`	`the wackelf.c is in hal/public`
`19:47.11`	`[g2]`	`GPSFan and you've built you own cross toolchain right ?`
`19:47.22`	`GPSFan`	`[g2]: not yet, been tracking down my mistakes first. so far the major thing that would be on that list is the ethernet.`
`19:47.30`	`GPSFan`	`[g2]: yes`
`19:47.56`	`GPSFan`	`list=not yet. built gcc etc=yes`
`19:48.03`	`GPSFan`	`;>)`
`19:53.04`	`*** join/#nslu2-linux caplink811-log (n=caplink8@dslb-088-073-002-092.pools.arcor-ip.net)`
`20:00.52`	`GPSFan`	`[g2]: Kaloz: wackelf -fpa xscale-be-elf.hal.o set the correct bits to allow it to compile.`
`20:01.35`	`[g2]`	`GPSFan nod. great!`
`20:03.09`	`[g2]`	`GPSFan I forget which GCC/binuilts are you using ?`
`20:04.20`	`GPSFan`	`[g2]: gcc 3.4.5 binutils 2.16.1`
`20:06.11`	`[g2]`	`GPSFan ok thx. I'll probably go straight to 4.1.1 and 2.6.16 or mabye 17`
`20:06.55`	`[g2]`	`Kaloz your just building the XScale toolchain from the openwrt svn repo right ?`
`20:07.03`	`Kaloz`	`[g2]: yeah`
`20:07.32`	`[g2]`	`Kaloz it's a very trivial 3 line patch to shim any machine type`
`20:08.03`	`[g2]`	`nslu2-linux prepends that on about 5 or 6 arches`
`20:08.09`	`nbd`	`[g2]: what's the best way to get started with configuring redboot for this target? copy the ixdp425 stuff to a new target and modify the parameters if necessary?`
`20:08.43`	`Kaloz`	`[g2]: i know, just i though it's correctly set up on the avila :p`
`20:09.29`	`[g2]`	`Kaloz the BSP from Gateworks comes with RedBoot source iirc`
`20:09.44`	`[g2]`	`which means there's a 1 line change for the Machine ID`
`20:09.50`	`Kaloz`	`i don't have the bsp, just a board.. so no jtag and the other toys for it`
`20:10.18`	`[g2]`	`I think all there boards have a JTAG header`
`20:10.24`	`[g2]`	`s/there/their/`
`20:10.33`	`Kaloz`	`yeah, but it's no standard :)`
`20:10.46`	`Kaloz`	`s/no/not/`
`20:11.04`	`Kaloz`	`s/s/s/s/s/s/s/`
`20:11.06`	`[g2]`	`it's a production board`
`20:11.08`	`Kaloz`	`:p`
`20:12.08`	`[g2]`	`Kaloz is there a header that's not installed ?`
`20:12.16`	`[g2]`	`and where's the HW porn pics ?`
`20:13.14`	`Kaloz`	`[g2]: it's a standard avila 2348-2 or what (the one with only 2minipci slots)`
`20:13.38`	`Kaloz`	`[g2]: but probably you could use some hw porn about the pronghorn metro i have here :P but i have no camera`
`20:14.55`	`Kaloz`	`[g2]: now that's a nice board for sure :)`
`20:15.28`	`Kaloz`	`[g2]: http://www.adiengineering.com/php-bin/ecomm4/productDisplay.php?category_id=27&product_id=85`
`20:18.48`	`[g2]`	`Kaloz umm that's not really any different than the Loft's I've had for 14 months`
`20:19.15`	`nbd`	`[g2]: are there any specific board dependent settings that i should check out in this source tree?`
`20:19.20`	`[g2]`	`except I went with the USB 2.0 host controller instead of the 4th minipci`
`20:19.55`	`[g2]`	`nbd do you have a working kernel you've ported for the board ?`
`20:20.07`	`nbd`	`yes`
`20:20.19`	`[g2]`	`ok then you should know the hw layout`
`20:20.55`	`nbd`	`yeah`
`20:21.00`	`[g2]`	`you can read the current setting for flash/memory controller/gpio either from the bootloader or by mapping them in via Linux right ?`
`20:21.38`	`nbd`	`i have a kernel tree that works, but i can't boot it because the boot loader is fscked and refuses to boot anything`
`20:22.01`	`nbd`	`the boot loader itself works, but it crashes every time it tries to load a kernel image`
`20:22.26`	`[g2]`	`your RedBoot boot loader ?`
`20:22.32`	`nbd`	`no, the original one`
`20:22.39`	`nbd`	`rgloader`
`20:22.47`	`nbd`	`i don't have a redboot image yet`
`20:23.22`	`[g2]`	`how does the kernel crash when loaded ?`
`20:23.33`	`[g2]`	`does the decompress run ?`
`20:23.38`	`nbd`	`no`
`20:23.50`	`nbd`	`i flash a kernel image, tell the boot loader to load it and boom, it's dead`
`20:23.56`	`nbd`	`with known working images`
`20:24.36`	`[g2]`	`well that doesn't make much sense (the known working images part)`
`20:24.42`	`nbd`	`i know`
`20:24.53`	`nbd`	`i can't figure out what's wrong with this thing`
`20:25.25`	`[g2]`	`I mean there are the following posibilities`
`20:25.59`	`[g2]`	`1) the rgloader does something like the sercomm loader on the nslu2-linux as in checking a trailer and stop the boot`
`20:26.09`	`[g2]`	`2) the image isn't really flashed properly`
`20:26.19`	`[g2]`	`3) the wrong mach id is pass to the kernel`
`20:26.32`	`[g2]`	`s/pass/passed/`
`20:26.34`	`nbd`	`when the wrong mach id is passed, shouldn't it still print the decompression stuff?`
`20:26.44`	`nbd`	`btw. the boot loader image is from a backup of the original flash`
`20:26.47`	`[g2]`	`you usually get the first line`
`20:27.08`	`[g2]`	`ndb re the backup`
`20:27.09`	`nbd`	`when i run boot -s 2, it doesn't even get to printing the newline after i hit enter`
`20:27.25`	`nbd`	`so it dies fast`
`20:27.38`	`[g2]`	`if you can't copy out, change, and copy back and have it work the same when then the bits on the same in the flash`
`20:28.00`	`nbd`	`it wasn't a full backup, probably`
`20:28.04`	`nbd`	`i saved the mtd partitions from linux`
`20:28.12`	`nbd`	`and there's a small area on the flash that could be missing in this backup`
`20:28.25`	`nbd`	`although i don't remember actually overwriting that when bricking the box`
`20:28.26`	`[g2]`	`right we has the same issue with the sercomm trailer`
`20:28.36`	`[g2]`	`and a neutered RedBoot`
`20:28.54`	`nbd`	`hence, i just want to get rid of this crappy loader and put a self compiled redboot on`
`20:29.27`	`[g2]`	`sure, believe me I fully understand`
`20:30.47`	`nbd`	`so, can you give me a list of things that i need from the running system?`
`20:30.53`	`[g2]`	`nbd this is for the wrv54g right ?`
`20:30.57`	`nbd`	`yes`
`20:31.05`	`nbd`	`well, a fully compatible board`
`20:31.17`	`[g2]`	`the gemtek`
`20:31.20`	`nbd`	`yes`
`20:32.06`	`[g2]`	`ndb if I was in you shoes here's what I'd do`
`20:32.14`	`[g2]`	`I'd boot the bootloader`
`20:32.33`	`[g2]`	`then with JTAG break in to the processor and dump out the config regs via JTAG`
`20:33.01`	`[g2]`	`specifically, the flash/memory controller/GPIO/serial settings`
`20:33.03`	`nbd`	`can openwince jtag do that or do i need something else?`
`20:33.13`	`NAiL`	`Kaloz: ping?`
`20:33.21`	`nbd`	`because i have that one working`
`20:33.25`	`[g2]`	`I doubt it supports XScale`
`20:33.35`	`nbd`	`i used it to flash the boot loader`
`20:33.46`	`nbd`	`so it does support xscale`
`20:33.59`	`[g2]`	`no it support the chip BSDL file`
`20:34.05`	`[g2]`	`s/supports/`
`20:34.05`	`nbd`	`ah, ok`
`20:34.08`	`nbd`	`i'm still new to jtag stuff`
`20:34.21`	`[g2]`	`they are just twiddling the individual line to the flash`
`20:35.17`	`[g2]`	`it probably takes like 40 minutes to reflash`
`20:35.17`	`[g2]`	`reflash RedBoot`
`20:35.17`	`nbd`	`yeah`
`20:35.17`	`nbd`	`so what else can i use?`
`20:36.17`	`[g2]`	`I've got a different adapter we are bringing up`
`20:36.43`	`[g2]`	`it does like 4Mhz`
`20:37.01`	`[g2]`	`it talks to the Avila board from Linux`
`20:37.11`	`*** join/#nslu2-linux DrZimmerman (n=theo@84-72-181-62.dclient.hispeed.ch)`
`20:38.13`	`NAiL`	`Kaloz: Did you have a fsg-3? Booting a 2.6 kernel? :)`
`20:38.40`	`GPSFan`	`[g2]: got madwifi compiled for 2.6.19-rc3. the modules all load and iwconfig can config the ath0 interface. will test out operation after lunch..`
`20:39.04`	`nbd`	`[g2]: so there's no way to do that with a simple buffered lattice cable?`
`20:40.30`	`*** join/#nslu2-linux DrZimmerman (n=theo@84-72-181-62.dclient.hispeed.ch)`
`20:41.48`	`Kaloz`	`NAiL: i don't have an fsg :)`
`20:42.19`	`NAiL`	`ah, no... someone else on the openwrt forum had one and you mentioned Xscale.`
`20:43.20`	`[g2]`	`nbd sure it's sw that talks to the debugging side of the chip`
`20:43.34`	`[g2]`	`nbd stop by #openjtag`
`20:45.34`	`Kaloz`	`NAiL: i have a linksys rt042 (bricked) and avila 2348-2, a gateway 7001 and a pronghorn metro :)`
`20:48.10`	`*** join/#nslu2-linux DrZimmerman (n=theo@84-72-181-62.dclient.hispeed.ch)`
`20:48.49`	`NAiL`	`ah`
`20:51.06`	`Kaloz`	`ah, yes, i have a n2100 now, too :)`
`20:51.06`	`dwery`	`NAIl has yet to test my latest patches on them all :D`
`20:55.15`	`*** join/#nslu2-linux Tobbe (n=tobbe@kbhn-vbrg-sr0-vl203-120.perspektivbredband.net)`
`20:57.53`	`NAiL`	`I know`
`21:03.43`	`NAiL`	`hmm`
`21:06.53`	`*** join/#nslu2-linux barnseen1o (n=bb@81-86-57-5.dsl.pipex.com)`
`21:18.15`	`[g2]`	`Kaloz nbd you guys haven't played with the RV series at all have you ?`
`21:19.16`	`NAiL`	`dwery: did you or blaster8 look at the via_sata issue?`
`21:19.21`	`NAiL`	`(if you know)`
`21:19.46`	`dwery`	`NAiL: nope. what issue?`
`21:20.10`	`NAiL`	`support for the controller in the fsg-3`
`21:20.28`	`dwery`	`what's missing?`
`21:21.04`	`NAiL`	`It's an VT6421. Not quite sure what the problem was again`
`21:21.19`	`NAiL`	`ah yes. The PATA bit of the driver was missing`
`21:21.42`	`[g2]`	`well relating to the G600`
`21:21.53`	`[g2]`	`and a via chip`
`21:22.18`	`[g2]`	`dwery we had the G600 working with 2.6.16 and the patched code back then`
`21:22.41`	`NAiL`	`it's the same problem as the G600?`
`21:23.54`	`dwery`	`[g2]: DMS-G600 was working when I tested it months ago...`
`21:24.20`	`dwery`	`99-sata_via-add-pata.patch does not work?`
`21:24.49`	`[g2]`	`dwery nod it worked for me too`
`21:25.01`	`[g2]`	`I haven't tried the latest on the G600`
`21:26.09`	`NAiL`	`does it apply to 2.6.18/19-rc3?`
`21:28.26`	`dwery`	`don't know... never tried`
`21:28.43`	`NAiL`	`(I don't have a serial cable yet, so I can't boot the kernel on the fsg-3)`
`21:31.15`	`NAiL`	`nite all`
`21:32.36`	`dwery`	`nite`
`21:41.24`	`*** join/#nslu2-linux fcarolo (i=www-data@limax.nslu2.osuosl.org)`
`21:41.52`	`NAiL`	`hmm`
`21:41.56`	`NAiL`	`cgiirc?`
`21:43.11`	`[g2]`	`sweet dreams NAiL`
`21:43.41`	`*** join/#nslu2-linux nSi (n=Sinclair@p54A0AA98.dip0.t-ipconnect.de)`
`21:50.55`	`GPSFan`	`[g2]: This is interesting, I can get the madwifi driver to associate with an ap, and scan and find several ap's but I can't ping. If I use the Gateworks supplied kernel/driver, things work ok. So I wonder if it's the same issue as with the ethernet.`
`21:57.09`	`dwery`	`GPSFan: did you get an IP via dhcp or it statically assigned?`
`21:59.38`	`GPSFan`	`dwery: ip is static.`
`22:02.08`	`GPSFan`	`dwery: hold on, the pings think they want to go out the ethernet.`
`22:02.47`	`GPSFan`	`now it works ok!! thanks for jaring my sanity..`
`22:03.21`	`dwery`	`:-D`
`22:03.34`	`*** join/#nslu2-linux rwhitby (n=rwhitby@nslu2-linux/rwhitby)`
`22:04.33`	`dwery`	`ok, madwifi issue resolved.`
`22:06.31`	`GPSFan`	`dwery: that's the latest rev: madwifi-ng-r1770-20061025`
`22:06.46`	`dwery`	`good. will try it in the next few weeks`
`22:13.25`	`rwhitby`	`morning all`
`22:13.43`	`barnseen1o`	`hey rwhitby`
`22:14.57`	`rwhitby`	`hey barnseen1o`
`22:35.30`	`GPSFan`	`dwery: did you have anything to do with the hwmonitor driver AD7418?`
`22:35.43`	`dwery`	`maybe.`
`22:35.51`	`dwery`	`:-D`
`22:36.04`	`dwery`	`if it burned your house, not.`
`22:36.12`	`dwery`	`anything else, I'am the author :)`
`22:36.49`	`GPSFan`	`;>) it works, it's just that the gateworks driver outputs 5050 and new driver outputs 50500 for the same temperature.`
`22:37.13`	`dwery`	`mm`
`22:37.20`	`GPSFan`	`same thing for the temp max and max_hyst.`
`22:37.48`	`dwery`	`I guess we should check how sensors read that value`
`22:38.34`	`GPSFan`	`those values are cooked by the driver to read in deg C 4500 being 45C`
`22:38.55`	`GPSFan`	`that's from how the show temp program displays things`
`22:39.06`	`dwery`	`I think there's a standard somewhere that should be followed..`
`22:39.09`	`dwery`	`let me see`
`22:40.11`	`dwery`	`the unit should be millidegree celsius`
`22:40.59`	`dwery`	`so the old driver is wrong`
`22:41.33`	`GPSFan`	`dwery: the voltage reads ok, in4 reads out a hex # which when multiplied by 23.1 (from the Gateworks manual) makes 12980mv or ~13V which is what I'm putting in.`
`22:42.15`	`dwery`	`good`
`22:42.29`	`GPSFan`	`dwery: 50500 milidegrees is 50degrees :>))`
`22:43.32`	`*** join/#nslu2-linux drif (n=drif@a88-112-207-120.elisa-laajakaista.fi)`
`22:44.01`	`dwery`	`isn't that right?`
`22:45.25`	`GPSFan`	`dwery: that's perfectly correct.`
`22:45.32`	`dwery`	`ok`
`22:45.33`	`dwery`	`:)`
`22:45.58`	`GPSFan`	`s/50degrees/50.5degrees`
`22:49.36`	`drif`	`+/`
`23:01.12`	`[g2]`	`GPSFan I've got an old OpenSlug BE toolchain lying around on another computer`
`23:01.42`	`[g2]`	`I was going to build my mini jffs2 rootfs that can ping and run the ethernet driver`
`23:01.52`	`[g2]`	`BE style`
`23:02.13`	`GPSFan`	`[g2]: great, then maybe we can figure out what's going on .`
`23:02.24`	`[g2]`	`I should be able to run the same .19-rc3 build`
`23:02.48`	`[g2]`	`I just need to build the jffs2 BE and tweak that JFFS2 parameter in the .config`
`23:04.16`	`[g2]`	`GPSFan I think the temps are in 1/10ths of degrees`
`23:05.15`	`GPSFan`	`[g2]: the chip datasheet says the resolution is .25C/bit of a 10bit value inside.`
`23:07.15`	`[g2]`	`GPSFan I remember it's a 10bit range over is it -100C to +100C ?`
`23:08.54`	`GPSFan`	`[g2]: +/-128C 10 bit 2's comp`
`23:09.39`	`GPSFan`	`I was sort of supprised at it reading 50C. the board gets a bit warmer than I expected.`
`23:10.16`	`GPSFan`	`esp the Sipex TO220 chip near the CPU`
`23:17.07`	`[g2]`	`GPSFan that's right near the chip`
`23:17.13`	`[g2]`	`s/chip/cpu/`
`23:28.20`	`GPSFan`	`yes, it's right near the cpu, probably the regulator for the core voltage.`
`23:28.35`	`*** join/#nslu2-linux dwery (n=dwery@nslu2-linux/dwery)`

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.