public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, damir.perisa@solnet.ch,
	akpm@osdl.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch] Re: 2.6.14-rc5-mm1 - ide-cs broken!
Date: Wed, 09 Nov 2005 15:56:09 -0500	[thread overview]
Message-ID: <43726269.7020600@tmr.com> (raw)
In-Reply-To: <1131557221.8506.76.camel@localhost.localdomain>

Richard Purdie wrote:
> On Wed, 2005-11-09 at 11:41 -0500, Bill Davidsen wrote:
> 
>>Richard Purdie wrote:
>>
>>>This patch stops CompactFlash devices being marked as removable. They
>>>are not removable (as defined by Linux) as the media and device are 
>>>inseparable. When a card is removed, the whole device is removed from 
>>>the system and never sits in a media-less state.
>>
>>Having used CF devices for some years (since RH 8.0) I'm not sure what 
>>problem you're addressing here. Could you describe what problem you're 
>>having, and also note what current functionality this will change?
> 
> 
> I'll try the explanation once more assuming you failed to understand the
> previous messages in this thread and those linked to in the link I
> provided to a thread about this.

Given the large number of possible valid configurations, I'm trying to 
determine which you are trying to fix and if that will break the others.
> 
> Block devices have a "removable" flag. This flag is defined to indicate
> devices where the media can change. A property of these devices is that
> the device node and device stay around and media may or may not be
> present at any one time. Examples of such devices are floppy and ide cd
> drives.
> 
> When you remove a CF card, the controller is removed with the card and
> nothing to do with the CF card or the device exists anymore. They are
> therefore not removable devices in the linux definition of the term.
> 
> Currently the removable flag is set for CF cards. This is incorrect as a
> CF device and interface either exists or doesn't. There is no media-less
> state.
> 
> This incorrect setting causes loops with udev scripts requiring
> userspace hacks to stop things looping. 
> 
> The patch therefore correctly sets the removable flag and removes some
> unneeded code. 
> 
> This shouldn't break anything in userspace apart from anything that
> incorrectly interprets the removable flag as being something its not.
> 
There are, at minimum, three possible hardware attach cases, each of 
which may be on a distribution which uses udev or not. I'm assuming that 
if this is a udev problem is would be fixed at the udev level, but your 
comment on "userspace hacks" does sound like fixes to userspace bugs.

The three attach methods are pcmcia, direct plugin slots (laptops only 
AFAIK), and USB devices.

It seems that the pcmcia cases for laptops and desktops are the same, 
and the whole media and device go away as a unit with the card. But for 
USB and direct plug-in, the "device" seems to be present even without 
media. I can't easily check that for laptop before tonight, but attached 
USB devices show up as sdX currently, with or without media. That's on 
an older kernel, I'll check 2.6.13 tonight.
-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-11-09 20:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051103220305.77620d8f.akpm@osdl.org>
2005-11-04  7:19 ` 2.6.14-rc5-mm1 - ide-cs broken! Greg KH
2005-11-04 15:14   ` Alan Cox
2005-11-04 16:37     ` Greg KH
2005-11-09 10:17       ` [patch] " Richard Purdie
2005-11-09 12:08         ` Alan Cox
2005-11-09 16:41         ` Bill Davidsen
2005-11-09 17:27           ` Richard Purdie
2005-11-09 20:56             ` Bill Davidsen [this message]
2005-11-09 21:37               ` Richard Purdie
2005-11-09 22:55                 ` Bill Davidsen
2005-11-09 23:02                   ` Damir Perisa
2005-11-09 21:48               ` Damir Perisa
2005-11-10 14:57         ` Mark Lord
2005-11-10 15:03           ` Richard Purdie
2005-11-04 23:22   ` ide-cs broken / udev magic Damir Perisa
2005-11-04 23:28     ` Greg KH
2005-11-05  2:06       ` Richard Purdie
2005-11-05 12:36         ` Damir Perisa

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=43726269.7020600@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=damir.perisa@solnet.ch \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --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