Joerg Schilling wrote:
Bill Davidsen <davidsen@tmr.com> wrote:Thanks for being willing to help track this, it really would be nice to understand it. I'm guessing it's not in the driver itself but in the command filter, simply because this behavior has been seen in various hardware.It is definitely not the command filter.
So are you saying that all of the drivers which show this behavior have the same bug, added by chance by the various people who wrote them, or ??? Will you share your reason for being certain that the problem is not in the shared code?
-- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979