From: Richard Purdie <rpurdie@rpsys.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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: Wed, 21 Sep 2005 19:46:25 +0100 [thread overview]
Message-ID: <1127328385.20660.45.camel@localhost.localdomain> (raw)
In-Reply-To: <1127327243.18840.34.camel@localhost.localdomain>
On Wed, 2005-09-21 at 19:27 +0100, Alan Cox wrote:
> On Mer, 2005-09-21 at 13:21 -0400, Mark Lord wrote:
> > In the case of CF cards in ide-cs, removing the card is equivalent
> > to removing the entire IDE controller, not just the media.
>
> It isn't the same as removing the entire PCMCIA controller layer. As far
> as PCMCIA is concerned there has been no change. Thus we have no media
> change event and we need ->removable = 1
CF slots have card detection and ide-cs will see a card removal event.
Have a look at ide_event() in ide-cs.c: CS_EVENT_CARD_INSERTION and
CS_EVENT_CARD_REMOVAL are what they say...
> If the PCMCIA card disappeared each time it would be different
Just the card disappears.
This along with your comments about the IDE layer having no hotplug
support suggest the code in question can be removed pending a better
replacement when hotplug is implemented.
Richard
next prev parent reply other threads:[~2005-09-21 18:46 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 [this message]
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
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=1127328385.20660.45.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--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 \
/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