**** BEGIN LOGGING AT Thu Mar 03 23:59:56 2005
Mar 04 10:49:12 <prpplague> ~seen beewoolie
Mar 04 10:49:25 <purl> beewoolie <~beewoolie@florence.buici.com> was last seen on IRC in channel #nslu2-linux, 7d 21h 45m 5s ago, saying: 'Gorx: I read that as "the suggestions on the wiki aren't working."  The wiki itself isn't the problem.  NP.'.
Mar 04 10:49:45 <prpplague> ~seen beewoolie-away
Mar 04 10:49:46 <purl> beewoolie-away <~beewoolie@florence.buici.com> was last seen on IRC in channel #openjtag, 1d 49m 45s ago, saying: 'For your amusement: <http://www.mnftiu.cc/mnftiu.cc/filing.009.html>'.
Mar 04 11:43:23 <prpplague> the bee has arrived
Mar 04 11:43:47 <beewoolie_> you knowin it.
Mar 04 11:44:19 <beewoolie_> [g2]: Have you received your fatslug?
Mar 04 11:45:16 <prpplague> beewoolie: i have spi sorta working on apex, but i'm still struggleing on how to mate it with fat driver
Mar 04 11:45:58 <[g2]> beewoolie, well that's a long story, but FatSlug 2 may be on the way soon if I don't receive it today
Mar 04 11:46:00 <beewoolie> prpplague: If you can use the driver stand-alone, dump spi:0#256, then it should be easy.
Mar 04 11:46:05 <prpplague> beewoolie: should i be doing one spi driver and one mmc driver?
Mar 04 11:46:09 <beewoolie> [g2]: ouch
Mar 04 11:46:44 <beewoolie> prpplague: I suppose that's up to you.  In APEX, the only meaningful driver is a random access, character oriented IO driver.
Mar 04 11:46:52 <beewoolie> If you can do that with spi, then so be it.
Mar 04 11:47:37 <[g2]> beewoolie, not super painful
Mar 04 11:47:38 <prpplague> beewoolie: well, i was thinking, ppl may want to have mmc implemented in other ways besides using the spi controler
Mar 04 11:48:00 <[g2]> I think rwhitby paid ka6sox-away to wait until the Beta was ready :)
Mar 04 11:48:15 <beewoolie> prpplague: I think that I only wrote eeprom drivers and didn't write an SPI driver...yeah.  Look at drv-cpld-spi.
Mar 04 11:48:36 <prpplague> beewoolie: make the mmc generic like the fat driver, and have the spi driver device specific
Mar 04 11:48:44 <prpplague> beewoolie: yea i already looked at that
Mar 04 11:49:01 <beewoolie> prpplague: It's a device-by-device issue.  The important thing to keep in mind is that the interface is stream oriented and random access.
Mar 04 11:49:15 <beewoolie> prpplague: Is mmc really a protocol in itself?
Mar 04 11:49:38 <prpplague> beewoolie: has a whole set of commands and procedures, so yea, i would qualify that as a protocol
Mar 04 11:49:53 <beewoolie> prpplague: I don't know much about mmc, so I'll defer to you.  
Mar 04 11:50:04 <prpplague> beewoolie: i mean you could implement mmc interface over address bus, or gpio
Mar 04 11:50:09 <beewoolie> prpplague: I've written code and factored pieces out when it makes sense.
Mar 04 11:50:15 <prpplague> beewoolie: or even through a cpld
Mar 04 11:50:35 <beewoolie> prpplague: Right.  But the lower-level interface needs to conform.
Mar 04 11:50:50 <beewoolie> prpplague: code sharing isn't important unless it is substantial.  
Mar 04 11:51:02 <beewoolie> prpplague: It may make more sense to write a library for mmc.
Mar 04 11:51:36 <beewoolie> prpplague: The bottom line is not to worry about it.  Unless the code is large, duplication isn't reason enough to factor it out.
Mar 04 11:51:52 <ka6sox-office> the more I look at MMC the more I like it.
Mar 04 11:52:22 <prpplague> beewoolie: ok, just trying to make the code as flexible as possible
Mar 04 11:52:32 <prpplague> ka6sox-office: yea mmc rocks
Mar 04 11:52:49 <beewoolie> wish my board had an mmc clot.
Mar 04 11:53:15 <prpplague> beewoolie: doesn't take but about 5 minutes to add one
Mar 04 11:53:43 <prpplague> beewoolie: logic pd board?
Mar 04 11:54:06 <beewoolie> prpplague: I'm pretty cautious.  I recheck the connections and want to make it clean.
Mar 04 11:54:28 <prpplague> beewoolie: ??
Mar 04 11:54:49 <beewoolie> I don't have an 80 pin ribbon cable, for example.
Mar 04 11:54:57 <prpplague> ??
Mar 04 11:55:08 <prpplague> why would you need 80 pin ribbon?
Mar 04 11:55:21 <ka6sox-office> mmc and 80 pin ribbon cables...mutually exclusive
Mar 04 11:56:21 <beewoolie> The SDK board has an 80 pin header for expansion.
Mar 04 11:57:43 <prpplague> beewoolie: all 6 pins that you need are grouped together
Mar 04 11:58:02 <prpplague> beewoolie: just need a some break away headers 
Mar 04 11:58:06 <beewoolie> prpplague: I still need to plug into the board without bending the other pins.
Mar 04 11:58:25 <prpplague> beewoolie: break away will work
Mar 04 11:58:35 <beewoolie> prpplague: Do you have a pointer?
Mar 04 11:58:51 <prpplague> beewoolie: on sec
Mar 04 12:04:05 <prpplague> beewoolie: http://www.jameco.com/webapp/wcs/stores/servlet/ProductDisplay?langId=-1&storeId=10001&catalogId=10001&productId=143953
Mar 04 12:04:18 <prpplague> beewoolie: they have little notches between the pins
Mar 04 12:04:26 <prpplague> beewoolie: so you just cut the number you need
Mar 04 12:05:08 <beewoolie> prpplague: I'll take a look.
Mar 04 12:05:11 <beewoolie> thx
Mar 04 12:05:50 <prpplague> np
Mar 04 12:06:35 <prpplague> beewoolie: tool me about 30 minutes the first time to put a mmc socket together for the LPD79520 
Mar 04 14:43:12 <[g2]> ka6sox, no FatSlug :(
Mar 04 14:44:39 <beewoolie-away> sad sad sad
Mar 04 14:44:58 <ka6sox-office> Okay let me finish soldering up the serial port.
Mar 04 14:45:02 <ka6sox-office> then I can send it.
Mar 04 14:45:05 <[g2]> ok
Mar 04 18:09:42 <beewoolie-away> Anyone know about this thing?  http://www.ovislinkcorp.com/MU-5000FS.htm
Mar 04 18:09:55 <beewoolie-away> It looks to be like the slug.
Mar 04 18:10:06 <beewoolie-away> I haven't been able to find anyone selling it.
Mar 04 18:10:26 <[g2]> yeah yeah it's a slug
Mar 04 18:10:41 <beewoolie-away> Same price?
Mar 04 18:11:08 <[g2]> iirc, it was written up / referenced in their NAS article  on Tom's Networking
Mar 04 18:11:19 <beewoolie-away> That's what I just saw.  
Mar 04 18:12:01 <beewoolie-away> Just curios if it's the same hardware or if it might be interesting to inspect.
Mar 04 19:39:21 <jacques> where's the GPL download?
Mar 04 19:39:32 <jacques> for the ovislink thing
Mar 04 19:40:13 <jacques> ah ftp://211.74.152.98/GPL5000FS.zip
Mar 04 19:40:34 <jacques> 130MB
Mar 04 19:40:57 <jacques> gonna take a while at 50kB/s
Mar 04 19:41:34 <jacques> speed's going down :-(
Mar 04 19:41:55 <ka6sox-away> what is this for?
Mar 04 19:42:04 <jacques> ah, it's in taiwan
Mar 04 19:42:15 <jacques> ka6sox-away, http://www.ovislinkcorp.com/MU-5000FS.htm
Mar 04 19:42:29 <jacques> looks like nslu2 with more featureful software
Mar 04 19:44:40 <ka6sox-away> so is the ADMtek  5120 a Arm clone?
Mar 04 19:45:21 <jacques> I have no idea - we were assuming this is same hardware as nslu2 - did you find something ?
Mar 04 19:45:48 <ka6sox-away> Hardware
Mar 04 19:45:48 <ka6sox-away> ADMtek  5120
Mar 04 19:45:48 <ka6sox-away> Flash  Memory: 4MBytes
Mar 04 19:45:48 <ka6sox-away> SDRAM:   32MBytes
Mar 04 19:46:15 <jacques> heh yeah I just saw that :-\
Mar 04 19:47:41 <ka6sox-away> brb...food
Mar 04 20:07:40 <ka6sox-away> back
Mar 04 20:10:16 <ka6sox-away> ADMtek 5120 (175MHz MIPS R4000).
Mar 04 20:10:47 <ka6sox-away> I used the R4000 20 years ago!
Mar 04 20:37:50 <jacques> ah interesting
Mar 04 20:38:03 <jacques> almost identical to nslu2 but with a mips pro
Mar 04 20:38:04 <jacques> c
Mar 04 20:38:10 <jacques> I wonder what the NIC is
Mar 04 20:55:39 <beewoolie-away> IIRC, the admtek is an integrated device.  It is used in something else we've looked up recently.
Mar 04 20:55:49 <beewoolie-away> I think there is a NIC onboard.
Mar 04 20:56:18 <beewoolie-away> In fact, I think this is in one of those wireless access point devices we were talking about a month ago.
Mar 04 20:57:14 <beewoolie-away> Have you folks found any of these for sale?
**** ENDING LOGGING AT Fri Mar 04 23:59:56 2005