mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Russell King <rmk@arm.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: clean up the IDE iops, add ones for a dead iface
Date: 21 Feb 2003 09:13:00 +0000	[thread overview]
Message-ID: <1045818779.5856.6.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302190853180.18995-100000@home.transmeta.com>

On Wed, 2003-02-19 at 16:56, Linus Torvalds wrote:
> On 19 Feb 2003, Benjamin Herrenschmidt wrote:
> > Hrm... I tend to agree with Russell here... 0x7f is the "safe" value
> > for IDE. IDE controllers with nothing wired shall have a pull down
> > on D7. The reason is simple: busy loops in the IDE code waiting for
> > BSY to go down.
> 
> But that's a BUG.
> 
> We've seen that before: try unplugging a PCMCIA IDE card unexpectedly. 
> 
> Guess what? It will start returning 0xff. And the machine dies, because 
> the PCMCIA interrupt happened due to the removal event will also be shared 
> by the IDE driver, so the IDE driver will react badly even before anybody 
> has had a chance to tell it that the hardware no longer exists.

Er, actually they make the card detect pins a different length for a
reason -- not just so they look pretty :) 

You are guaranteed a certain amount of time between the card detect
firing to signal removal, and the actual disconnection of the device.

And you can't rely on getting 0xFF; sometimes your box just locks up
hard if you try to access the missing hardware any time after the
'warning period' has expired and the device has actually gone.

Admittedly that's a fairly screwed box -- but I have them and was
expected to make them userproof.

-- 
dwmw2

  parent reply	other threads:[~2003-02-21  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 18:03 Alan Cox
2003-02-18 23:09 ` Russell King
2003-02-19  1:53   ` Alan Cox
2003-02-19  9:39     ` Benjamin Herrenschmidt
2003-02-19 14:25       ` Alan Cox
2003-02-19 16:56       ` Linus Torvalds
2003-02-19 17:06         ` Benjamin Herrenschmidt
2003-02-19 18:22           ` Alan Cox
2003-02-19 17:26             ` Benjamin Herrenschmidt
2003-02-21  9:13         ` David Woodhouse [this message]
2003-02-20 13:16 ` Geert Uytterhoeven
2003-02-20 14:40   ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1045818779.5856.6.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®