On Tue, 1 Mar 2005, Jeff Garzik wrote:
>
> A new API handles none of this.
Ehh?
The new API is what _allows_ a driver to care. It doesn't handle DMA, but
I think that's because nobody knows how to handle it (ie it's probably
hw-dependent and all existign implementations would thus be
driver-specific anyway).
And in the sense of "any general new api handles none of it", your
argument doesn't make sense. The _old_ IO API's clearly don't handle it.
So if you seem to say that "A new API" can't handle it either, then that
translates to "no API can ever handle it". Fair enough, if you think it's
impossible, but clearly you can handle some things.
And yes, CLEARLY drivers will have to do all the heavy lifting.
I don't expect most drivers to care. In fact, I expect about five to ten
drivers to be converted to really care, and then for some forseeable time
you'll have to be very picky about your hardware if you care about PCI
parity errors etc. Most people don't, and most drivers won't be written in
environments where they can be reasonably tested.
That's just a fact. Anybody who expects all drivers to suddenly start
doing IO checks is just living in a dream world.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
