**** BEGIN LOGGING AT Thu Feb 16 10:59:56 2006
Feb 16 15:08:02 <ka6sox> AchiestDragon, ping
Feb 16 15:08:11 <AchiestDragon> hi
Feb 16 15:08:18 <ka6sox> hi there 
Feb 16 15:08:32 <ka6sox> a question about those 4245's
Feb 16 15:08:49 <ka6sox> (the dual voltage guys
Feb 16 15:09:20 <ka6sox> I didn't see if we could split them and have them go 2 one direction and 2 the other direction.
Feb 16 15:09:29 <ka6sox> and I can't find the pdf doco.
Feb 16 15:09:43 <AchiestDragon> k
Feb 16 15:09:47 <AchiestDragon> 1 min 
Feb 16 15:09:59 <ka6sox> (I'm thinking about using them for a 68HC908 project I'm doing for work.
Feb 16 15:10:12 <ka6sox> (well fun work)
Feb 16 15:10:39 <ByronT> that's an oxymoron these days for moi
Feb 16 15:10:58 <ka6sox> ByronT, unfortunately ;(
Feb 16 15:11:51 <AchiestDragon> yes you can  2 in and 2 out theres 2 seperate diretion pins and 2 ce lines   , see the one on page 7 of the aztag shematics 
Feb 16 15:12:01 <ka6sox> k
Feb 16 15:12:35 <ka6sox> this will help with the tempy programer that I have to build until I get my aztag. :)
Feb 16 15:13:54 <ka6sox> thanks!
Feb 16 18:52:57 <velinp> ~seen lennert
Feb 16 18:53:08 <purl> lennert is currently on #openjtag (13d 11h 20m 43s). Has said a total of 185 messages. Is idling for 7h 56m 48s, last said: 'indeed, jtag pins on ts72xx aren't brought out ;('.
Feb 16 19:36:11 <lennert> i'm here
Feb 16 19:37:20 <velinp> hi; /msg with Yoe about distcc-cross; he not quite happy to maintain cross-builds .. 
Feb 16 19:40:44 <lennert> yeah, he said that before
Feb 16 19:40:50 <lennert> he thinks it's too much work
Feb 17 01:03:59 <lennert> http://www.math.leidenuniv.nl/~rhuizer/pong_nes/
Feb 17 01:04:11 <lennert> we implemented pong with.. the original vintage NES controllers!
Feb 17 01:04:29 <lennert> and a bunch of wires
Feb 17 01:08:12 <ka6sox-office> ewww...UBE Hackery at its finest!
Feb 17 01:08:13 <ka6sox-office> :)
Feb 17 01:08:30 <lennert> :)
Feb 17 01:45:08 <ka6sox-office> lennert, did you say that you were having problems with the TS7250?
Feb 17 02:07:02 <lennert> yeah, kind of
Feb 17 02:13:09 <ka6sox-office> is it the DoC stuff thet issue?
Feb 17 02:33:03 * NAiL kicks DoC in the nuts
Feb 17 02:53:29 <lennert> nope
Feb 17 02:53:35 <lennert> it's just my general being overloaded :-/
Feb 17 03:11:22 <beewoolie-afk> ka6sox: yo
Feb 17 03:16:57 <[g2]> hey beewoolie-afk welcome
Feb 17 03:17:03 <beewoolie-afk> [g2]: hey
Feb 17 03:17:20 <[g2]> hey could you do me a quick favor ?
Feb 17 03:17:27 <beewoolie-afk> Sure
Feb 17 03:17:28 <[g2]> can you look at a kernel log
Feb 17 03:17:31 <beewoolie-afk> Sure.
Feb 17 03:17:37 <beewoolie-afk> pastebin?
Feb 17 03:18:02 <beewoolie-afk> [g2]: BTW, I never got back to you about the CF driver.
Feb 17 03:18:17 <[g2]> setting it up 2 secs
Feb 17 03:18:23 <beewoolie-afk> I'm pretty sure that your driver is in error.
Feb 17 03:18:40 <[g2]> http://pastebin.ca/41912
Feb 17 03:19:07 <[g2]> I"m missing something with IDE
Feb 17 03:20:03 <beewoolie-afk> It's not showing partitions.
Feb 17 03:20:13 <[g2]> yeah that's what I'm missing :)
Feb 17 03:20:22 <[g2]> it shows the luns
Feb 17 03:20:24 <[g2]> P1 P2 P3
Feb 17 03:20:28 <beewoolie-afk> I wonder if you're missing the right file-system driver.
Feb 17 03:20:50 <[g2]> it's EXT2 and it's built in
Feb 17 03:21:11 <beewoolie-afk> I like this: All bugs added by David S. Miller <davem@redhat.com>
Feb 17 03:21:33 <NAiL> heh
Feb 17 03:22:35 <beewoolie-afk> Since it isn't showing partitions, that makes me think that the IDE driver isn't initializing properly.
Feb 17 03:22:47 <beewoolie-afk> You've got devfs in there, right?
Feb 17 03:23:05 <[g2]> yeah
Feb 17 03:23:27 <beewoolie-afk> I recommend that you remove things that don't help with IDE.  Just as a test.
Feb 17 03:24:19 <beewoolie-afk> I don't see anything that would stop it from working.  Ar eyou sure that the ide-disk driver is in there?
Feb 17 03:24:44 <beewoolie-afk> My guess is that you're missing something dumb.  How about pasting the .config file.
Feb 17 03:30:51 <[g2]> http://pastebin.ca/41914
Feb 17 03:31:04 * beewoolie-afk looking
Feb 17 03:31:49 <[g2]> it's been a few years since playing around on a desktop box :)
Feb 17 03:32:26 <beewoolie-afk> I don't see anything.
Feb 17 03:32:57 <beewoolie-afk> It's hard to imagine that it's broken considering that we're talking about x86
Feb 17 03:33:30 <ka6sox> it can't seem to read off the HD>
Feb 17 03:33:46 <[g2]> Oh I don't think it's broken I'm sure it's a config thing
Feb 17 03:33:56 <beewoolie-afk> It get's the IDE info, so it can read the interface just fine.
Feb 17 03:33:57 <[g2]> I boot to the HD with other kernels :)
Feb 17 03:34:00 <beewoolie-afk> It doesn't read the partitions.
Feb 17 03:34:07 <beewoolie-afk> I wonder if this is related to devfs.
Feb 17 03:34:13 <beewoolie-afk> I thought that it was deprecated.
Feb 17 03:36:32 <[g2]> Ok well THX!
Feb 17 03:36:42 <[g2]> I'll run it down 
Feb 17 03:36:54 <[g2]> I thought it might be something obvious
Feb 17 03:38:46 <NAiL> devfs was removed in 2.6.15.2, wasn't it?
Feb 17 04:27:02 <ka6sox> beewoolie-afk, are we planning on setting aside extention opcodes in the protocol?
Feb 17 04:45:15 <beewoolie-afk> ka6sox: Sorry,I haven't been paying attention.
Feb 17 04:45:27 <beewoolie-afk> The protocol has lots of room for changes.
Feb 17 04:45:38 <beewoolie-afk> I don't know what you mean about 'setting asside' opcodes.
Feb 17 04:45:50 <beewoolie-afk> Anything that isn't currently in use is reserved for extensions.
Feb 17 04:46:06 <beewoolie-afk> Is there something specific you are interested in?
Feb 17 05:09:53 <NAiL> ok, anyone that can help me flipping one bit in the ixp exp_cnfg1 register? 
Feb 17 05:40:15 <beewoolie-afk> ka6sox: Did you see my reply?
Feb 17 05:40:48 <ka6sox> unfortunately....no.
Feb 17 05:45:18 * NAiL bangs his head against the wall
Feb 17 05:48:24 * ka6sox sees a flat foreheaded NAiL 
Feb 17 05:48:35 <ka6sox> beewoolie-afk, sorry I got disconnected.
Feb 17 05:49:07 <NAiL> ka6sox: if I continue like this, it'll get bloody soon :-P
Feb 17 05:50:48 <ka6sox> ah
Feb 17 05:51:08 <NAiL>         *IXP4XX_EXP_CS0 |= IXP4XX_FLASH_WRITABLE;
Feb 17 05:51:12 <NAiL> ups
Feb 17 05:51:27 <NAiL> 05:46 < beewoolie-afk> Anything that isn't currently in use is reserved for extensions.
Feb 17 05:51:27 <ka6sox> NAiL, have you got beewoolies' response in your buffer?
Feb 17 05:51:30 <NAiL> 05:47 < beewoolie-afk> Is there something specific you are interested in?
Feb 17 05:51:37 <NAiL> I guess that answers your q ;)
Feb 17 05:51:40 <ka6sox> yes!~
Feb 17 05:51:41 <ka6sox> thanks.
Feb 17 05:51:48 <NAiL> np
Feb 17 06:10:52 <beewoolie-afk> ka6sox: So, I'm not sure about this, but I'm really concerned.
Feb 17 06:11:04 <beewoolie-afk> The performance of the FTDI2232 is really poor.
Feb 17 06:11:11 <beewoolie-afk> Specifically, the latency is really high.
Feb 17 06:11:35 <ka6sox> I was worried about this
Feb 17 06:11:41 <beewoolie-afk> If I write a command to poll the status of the output GPIO lines, it can take quite a bit of time for it to come back.
Feb 17 06:11:54 <ka6sox> (my reading said that things were going to be quite slow)
Feb 17 06:12:05 <beewoolie-afk> I cannot be sure right now because I'm also running a long compile.
Feb 17 06:12:13 <ka6sox> ah
Feb 17 06:12:22 <beewoolie-afk> However, I noticed this yesterday when I first got it running.
Feb 17 06:12:33 <beewoolie-afk> I've been messing with the USB interface library.
Feb 17 06:12:50 <beewoolie-afk> I'm replacing the crufty libftdi with a simple class in my code.
Feb 17 06:13:08 <beewoolie-afk> How has it seemed to you?
Feb 17 06:13:52 <ka6sox> quite a bit of latency
Feb 17 06:14:27 <ka6sox> not responsive using the libftdi
Feb 17 06:14:29 <beewoolie-afk> OK.  So I paused the build
Feb 17 06:14:34 <ka6sox> k
Feb 17 06:14:48 <beewoolie-afk> When I send the command to read the bits, I wait in a loop reading on the USB interface.
Feb 17 06:14:57 <beewoolie-afk> it takes a second or more for the reply.
Feb 17 06:15:17 <beewoolie-afk> I set the 'latency timer' of the FTDI to 1.  It defaults to 16.
Feb 17 06:15:33 <beewoolie-afk> What sux is that this is slower than the parallel port devices.
Feb 17 06:16:03 <beewoolie-afk> I'm going to send mail to ep1220 asking if he's seen the same thing.
Feb 17 06:16:59 <ka6sox> k
Feb 17 06:17:19 <ka6sox> sounds good.
Feb 17 06:44:20 * NAiL ponders paying someone to figure out how to properly detect the DoC on the ds101
Feb 17 06:44:56 <beewoolie-afk> NAiL: were you the one asking a question about the DoC on the arm list?
Feb 17 06:45:17 <NAiL> yes
Feb 17 06:47:49 <NAiL> What might be the problem is the cpld between the ixp and the DoC. There are working drivers for 2.4, but I can't figure out what they're doing differently. 
Feb 17 06:48:08 * beewoolie-afk is looking at the wiki on the ds101
Feb 17 06:49:18 <beewoolie-afk> NAiL: I don't see the DoC in the pictures.  Isn't it a DIP?
Feb 17 06:49:55 <NAiL> no, it's a tsop package
Feb 17 06:50:05 <NAiL> 48 pins
Feb 17 06:50:24 <NAiL> the pictures on the wiki are a rev 2.2, which has intel flash though
Feb 17 06:50:36 <beewoolie-afk> Damn.  Does this thing have pads for doubling the memory size?
Feb 17 06:50:43 <beewoolie-afk> Ah, ok.
Feb 17 06:52:03 <beewoolie-afk> Based on my experience with booting the Slug using APEX, it is very concievable that there is code tucked away somewhere in the inits that is significant, but not obvious.
Feb 17 06:52:25 <beewoolie-afk> It could be something like a GPIO line being set.
Feb 17 06:52:37 <NAiL> yeah, I've been eyeballing the sources for days ;)
Feb 17 06:52:56 <NAiL> I made some progress when I found the point where they set up CS0 correctly
Feb 17 06:54:00 <NAiL> even more progress when I hacked the DoC code to use 16-bit instead of 32bit accesses by default
Feb 17 06:54:10 <NAiL> but the bugger is still not detected
Feb 17 06:56:46 <NAiL> The only GPIO line that is free is GPIO6. Haven't found any reference to it in the code yet.
Feb 17 06:59:16 <beewoolie-afk> If only I had one...
Feb 17 06:59:35 <NAiL> hehe ;)
Feb 17 06:59:36 <beewoolie-afk> I've been thinking about getting one of the boxes that has wifi built-in.
Feb 17 07:00:28 <NAiL> nas100d?
Feb 17 07:00:38 <beewoolie-afk> I think that's the one.
Feb 17 07:01:10 <beewoolie-afk> What's with all of the different spins on the ds101?
Feb 17 07:01:25 <NAiL> spins?
Feb 17 07:01:37 <beewoolie-afk> ds101, ds101j, ds101g+
Feb 17 07:02:16 <NAiL> ah, ds101g+ is a ppc device w/gblan
Feb 17 07:02:35 <NAiL> ds101j is the slimmed-down version of the ds101
Feb 17 07:02:39 <beewoolie-afk> Right.  Is it a distingt product?
Feb 17 07:02:44 <beewoolie-afk> grr.
Feb 17 07:02:47 <beewoolie-afk> Distinct?
Feb 17 07:02:52 <beewoolie-afk> Same with the j?
Feb 17 07:03:15 <NAiL> yeah
Feb 17 07:03:39 <beewoolie-afk> They only list the J and the G on their web site.
Feb 17 07:03:52 <beewoolie-afk> And the G has SATA,.  Nice.
Feb 17 07:03:55 <NAiL> yeah
Feb 17 07:04:26 <NAiL> The DS101 appears to have been discontinued
Feb 17 07:04:40 <beewoolie-afk> Which one do you have?
Feb 17 07:04:41 <NAiL> There's another company (MicroStorage) that sells them now... A lot cheaper ;)
Feb 17 07:04:47 <NAiL> I have the DS101
Feb 17 07:04:58 <beewoolie-afk> that's a lot of HW changes.
Feb 17 07:05:21 <NAiL> the DS101 and DS101g+ use the same kernel sources
Feb 17 07:05:36 <NAiL> they're patched to hell with #ifdefs sprinkled all over
Feb 17 07:05:56 <beewoolie-afk> :-)  The picture on the microstorage site is identical to the synology one.
Feb 17 07:06:14 <NAiL> Yeah, they even use the same software for it
Feb 17 07:06:21 <NAiL> they haven't renamed it ;)
Feb 17 07:08:34 <beewoolie-afk> I haven't been able to find anyone selling it.
Feb 17 07:08:48 <NAiL> No, they're kinda hard to get a hold of
Feb 17 07:09:09 <NAiL> several of the nslu2-linux core devs were planning on buying one
Feb 17 07:09:34 <NAiL> but they couldn't get one
Feb 17 07:10:45 <NAiL> So I'm kinda struggling for myself :-P
Feb 17 07:10:53 <NAiL> dwery has helped me a lot though
Feb 17 07:11:51 <beewoolie-afk> sleeptime.
Feb 17 07:11:58 <NAiL> nite
**** ENDING LOGGING AT Fri Feb 17 10:59:56 2006