> I'd sooner see any MI asc driver be pseudo-script-based, for the same
> reasons Chris likes that design. The `esp' name is a Sparc-ism that's
> painful and counter-intuitive for machines with PROMs and/or vendor OS
> code cthat refer to an "asc" -- no less so than "asc" would be on
> Sparcs, for the same reasons.  Perhaps the right fix is allowing an
> attachment-specific override of the driver name visible to users?

I have no problems with calling the `esp' an `asc' on NetBSD/sparc,
as long as it gets the bits across the cables...

The user-visible adapter name should not be much of a concern to users,
at least not as much as disk- or network interface names are.

-pk