Russell look at what T13 did. It gave CFA/PCMCIA there own set of opcodes
and rules. Meaning they can do it different. What is so hard to see that
they do it different and they have the resouces to do so.
It means, gee we need to go resolve the pcmcia issues in native calls.
On Sat, 24 Aug 2002, Russell King wrote:
> 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
> And yes, people _do_ use PCMCIA IDE drives with Linux.
> Russell King (firstname.lastname@example.org) The developer of ARM Linux
LAD Storage Consulting Group
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/