> I don't know if there's enough reason to change reset semantics
> now to wait for completion, so that the next call be free of race.
> and I once had a simpler fix to let it delay another 50ms, that works
> on my box but seems not a thorough one. does it help?
BWGROUP(drive)->busy should never reach zero until the reset is
done. The 50mS miught be enough that this occurs, as might waiting
for HWGROUP(drive)->busy hitting 0. I don't yet understand why it
matters, and to fix it properly I have to figure that out.
If you need reliable reset for something like a test harness, or
IDE drive tester its a usable workaround, but I need to fix it
properly (eventually)
> + /* wait for another 50ms */
> + mdelay(50);
In your test set is HWGROUP(drive)->busy always zero after the
mdelay ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:23 EST