> I'd rather have Adaptec provide a source code driver for their cards 
> directly, then have Scott Long have to fight with unavailability of 
> documentation itself ... if the driver works, what do we need 
> documentation for?

To fix the driver.

A given piece of source code can only been believed correct until it is
proven to be broken (unless you're Knuth, but he did not write device
drivers).

Even if the driver API is static, the hardware you'll want to use your
particular card on isn't. New hardware may (and will) need tweaks to
work on your new Uberathlon128 system in two years.

If the driver happens to be working by chance on x86 because of, say,
some cache behaviour future (read: legacy-free) hardware won't
guarantee, what are you going to do? Beg the vendor to fix the driver
for this card while it wants you to buy the new, expensive, device
flavour which sports 128-bit bells&whistles?

Fixing a subtly broken piece of code might not be as simple as adding
bus_dmamap_sync() calls here and there.

Miod