On Fri, Aug 23, 2002 at 10:02:44PM -0400, Jeff Garzik wrote:
> Basically think about the consequences of trying to handle a completely
> unknown state -- if you are going to attempt to handle this you would
> need to check for data, not just the BSY bit. And read the data into a
> throwaway buffer, if there is data to be read, or write the data it's
> expecting.
>
> So it's not just the busy bit :)
I notice everyone decided to miss replying to my mail about PCMCIA
IDE devices, which will trip you up here. Could it be because I've
identified a real problem here?
- You plug the IDE device in.
- Power gets applied.
- cardmgr loads ide_cs.
- cardmgr binds ide_cs, which registers with the IDE layer.
The above happens in 10s of milliseconds, well before the hard drive
platters have been spun up. Meanwhile, as defined by the T13 specs,
the BSY bit can be set for up to 31 seconds.
You're saying "completely unknown state". I say "T13 defines this
state extremely well, and defines what happens from the drives point
of view at the end of the power on reset sequence extremely well."
I also say that your implementation above is, in andrespeak, a "bad
host" because it doesn't follow the T13 power on reset sequence
properly.
And yes, people _do_ use PCMCIA IDE drives with Linux.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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 : Sat Aug 31 2002 - 22:00:13 EST