From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Mark Lord <liml@rtr.ca>,
LKML <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [RFC/BUG?] ide_cs's removable status
Date: Thu, 22 Sep 2005 15:36:35 +0100 [thread overview]
Message-ID: <20050922143635.GD26438@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1127398876.8242.74.camel@localhost.localdomain>
On Thu, Sep 22, 2005 at 03:21:16PM +0100, Richard Purdie wrote:
> 3. ide-cs sometimes can't/doesn't detect the removal of an ide
> controller.
This is the one I'm particularly interested in, and I think it's
responsible for a lot of problems in this area.
"can't" is correct - from what I now understand from Alan, it seems
that there are PCMCIA to CF adapters out there which tie the PCMCIA
card detect lines to ground, rather than passing them through to the
CF socket.
This means that if you leave the PCMCIA to CF adapter in the slot,
pull out the CF card, replace it with another CF card, PCMCIA will
not notice the change.
You could even plug this adapter into the slot with a CF IDE card in,
unplug the CF IDE card and replace it with a CF network card. Then
watch the fun and games when IDE tries to access the CF network card!
Therefore, it's completely unsafe to assume anything about what's
plugged in with such a broken adapter... the only way you could be
sure is to regularly check the CIS matches the PCMCIA cached version,
provided you have enough of the CIS cached.
I think this basically comes down to a buggy CF adapter which needs
bining.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-22 14:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 16:15 [RFC/BUG?] ide_cs's removable status Richard Purdie
2005-09-21 16:57 ` Alan Cox
2005-09-21 17:21 ` Mark Lord
2005-09-21 18:27 ` Alan Cox
2005-09-21 18:46 ` Richard Purdie
2005-09-22 0:18 ` Alan Cox
2002-01-01 5:18 ` Pavel Machek
2005-09-21 19:29 ` Russell King
2005-09-21 21:52 ` Richard Purdie
2005-09-22 0:06 ` Alan Cox
2005-09-22 0:10 ` Alan Cox
2005-09-22 10:22 ` Russell King
2005-09-22 13:39 ` Alan Cox
2005-09-22 13:29 ` Russell King
2005-09-22 14:41 ` Alan Cox
2005-09-22 14:21 ` Richard Purdie
2005-09-22 14:36 ` Russell King [this message]
2005-09-22 15:08 ` 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=20050922143635.GD26438@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rpurdie@rpsys.net \
/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;
as well as URLs for NNTP newsgroup(s).