> 
> > Trust me the code to talk MSCP through the SII chip is very different than 
> > the code to talk MSCP through the Qbus. But again, if you feel strongly 
> > about this why not argue it like the ifnet layer on network devices? Create 
> > the virtual disk (like the virtual network interface) and simplify one's life.
> 
> but, this is because our MSCP driver comes from the bsd uda driver which is
> specific to the uda50 and its clones, and should be rewritten to be a 
> generic mscp driver, and then directed to talk over various different 
> drivers to get to devices. 
> 
Well, not really. I rewrote the MSCP stuff a couple of years ago so that
it should be abstracted away from how the uda50 works. It should now be
no problem to use it to talk to disks over CI or so.

-- Ragge