Date   : Sun, 24 Jul 2005 15:54:45 +0200
From   : "Mark Usher" <mu.list@...>
Subject: Econet interface

>We have 3 approaches suggested so far
There is a 4th as suggested by Phil 

1) a USB interface for a PC which bridges to Econet
   hardware wise this would comprise something to do the USB back to 
   parallel conversion, and a 68B54 plus line drivers. Though in principle
   USB 1.1 can go at 12Mbps, the useful throughput is limited by how much
   you send in each 1ms window.
   I've no idea where to start writing Windows/Linux network or USB drivers.

USB Driver is one of the easiest types of Windows driver to develop. In
fact, a USB serial driver is usually the first lesson when currently
learning windows driver development. Network drivers aren't necessary as an
interface would be provided by the driver, the Windows/Linux Network drivers
can then address it as per the normal network driver model. Stage 1 though
would be to interface to an app, be it a file transfer util, an emulator or
a file/print server.
This solution would enable emulators to access econet via the driver api.
Compatible with X86 Machines/MAC. Also compatible across all Acorns.

2) something along the lines of an ISA Ecolink
   just slap MiniB on a PCI card with a 68B54 and NFS. Finished.
   Again, I've no idea where to start writing Windows/Linux network or PCI
   drivers.
This seems as if it would need more hardware. PCI limitations also exist
e.g.. Couldn't be used with a laptop computer.

3) an ethernet interface for the beeb
   obviously never going to make the full 10/100/1000Mbps rate the network
   can handle, but no reason why it couldn't be built. Not sure where best
   to hang it, 1MHz bus maybe? Perhaps sitting in the 68B54 socket (though
   this would mean making a different one for the Master). Might also
   consider a serial to ethernet module, this would hang off the RS423 port.
   Software much more interesting, but a lot of it to write (protocol stacks
   and filing systems)
Problem here is with the amount of power the Beeb has to drive it, workspace
and compatibility as you say.

4) a standalone bridge unit
   Econet one side, Ethernet the other. This could get very complicated with
   the internal software to sort out the addressing and possible routing 
   implications. It would be the most invisible solution and hardware 
   independent both Acorn and PC sides. Emulators would then have to address

   OS network instead of a device directly.

Mark