On Mon, Feb 11, 2008 at 11:29:07AM +0100, Holger Macht wrote: > > In the above example, even the reset sequence itself can cause hang if > > the hardware is implemented slightly differently. The reason why > > set_piomode() locks up but reset sequence doesn't is simple dumb luck. > > Another thing, whether it's poor luck or not, it worked like this than at > least 2.6.22. And it was _heavily_ tested. The above commit broke it > between 2.6.24-rc1 and 2.6.24-rc2, which is at least a regression. Not neccessarily. It may just be timing chance on your box. I agree however we should be doing the reset after the PIO0 switch if it turns out that the precise order of the two events matters. Alan - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
