From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Richard Purdie <rpurdie@rpsys.net>,
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 13:21:58 -0400 [thread overview]
Message-ID: <433196B6.8000607@rtr.ca> (raw)
In-Reply-To: <1127321829.18840.18.camel@localhost.localdomain>
Alan Cox wrote:
>
> I can't comment on the MMC layer or its core requirements as I don't
> know them well. IDE PCMCIA does however encompass removal devices. The
> removable flag is set so that we get removable media behaviour - that is
> the media can change under us and we must not cache partition data. The
> current behavioiur in that sense is correct.
Mmm.. I'm not so sure about that.
In the case of CF cards in ide-cs, removing the card is equivalent
to removing the entire IDE controller, not just the media.
So "media change" is not what happens here.
But yes, it still should be managed as a removable device,
but we currently seem to be using this bit to mean two things,
as explained by Russell in the given link.
> http://lkml.org/lkml/2005/1/8/165
Cheers
next prev parent reply other threads:[~2005-09-21 17:22 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 [this message]
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
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=433196B6.8000607@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--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