On Feb 28,  3:54am, Miod Vallat wrote:
}
} > } fdc@ebus needs more work, as DMA is done completely differently than
} > } for fdc@sbus. This is why the fdc@ebus attachment is commented out - I
} > } never got to finish it.
} > 
} >      It doesn't do real DMA, it just copies bytes when asked.  The ebus
} 
} I beg to differ. fdthree, i.e. fdc@ebus, behaves just like a regular isa
} fdc, and does real DMA, unlike fdc@sbus. The sparc fdc driver doesn't

     In this case, I have to ask why the OpenBSD driver has the ebus
attachment code in the same file as the sbus stuff, since the ebus
driver is going to need a different back end?

} yet, this is why there is zero chance for fdc@ebus to work at the
} moment.

     Thanks for the heads up.  I guess there is a bit of work to be
done.

}-- End of excerpt from Miod Vallat