Hi,

   in a machine-dependent module.  In some cases (e.g. the LANCE), this
   may even be sufficient; most of the access after initialization is
   through memory.

Others have mentioned various ways it may get uglier. I will note that for
the DECstations, there are three different ways the cpu sees memory that
apears contiguous to the LANCE. (alternate 16bit word, 16bit gap,...)

I handled it with macros and architecture dependent memory copy functions,
but this isn't necessarily a good way to do it.

Good luck with it, rick