Hi,
The 53C9x won't be that hard, but you'll have to write register access code
going through NUBUS instead of memory mapped IO. The NUBUS ethernet drivers
should have plenty of sample code. Leaves the exercise of locating the chip
in the slot address space :-)
Well, I did buy the card with the intent of getting a Linux driver working
at some point. It's just not that close to the top of my list. I also have
not really looked at the esp code (either the old or new version) other
than a superficial look at mac_esp.c when Finn was making some fixes. It
The new esp code is much cleaner and should be easier to adapt to a new bus
model (I won't deny Nubus might not have quirks of its own there - bus width may
be an issue, bytes may come spaced by null bytes, you name it, Apple thought of
it).
doesn't sound too bad from the way you describe it. If it's as easy as
taking mac_esp.c and copying it to nubus_esp.c and writing a new probe
function to detect and setup the card, that shouldn't take long. I notice
that mac_esp.c already uses nubus functions to do some of the work, and
the address space the driver uses for PDMA is in a range normally used
by the nubus code while the device registers are in regular IO space.
No idea how PDMA would work - may there is a DMA chip even?
This could also be an excuse to dig in to nubus.c as well and get a real
device model framework there.
The best excuse :-)
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
