mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Bill Davidsen <davidsen@tmr.com>
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 21:37:14 +0000	[thread overview]
Message-ID: <1131572234.8506.130.camel@localhost.localdomain> (raw)
In-Reply-To: <43726269.7020600@tmr.com>

On Wed, 2005-11-09 at 15:56 -0500, Bill Davidsen wrote: 
> 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.

I'm primarily fixing ide-cs but the same fix equally applies to any
CompactFlash interface directly accessed as an ide device. 

> 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.

Initially I'd have blamed udev but its actually doing exactly the right
thing in this case and is definitely not at fault. (I've described this
in detail in the past if you want more information.)

> The three attach methods are pcmcia, direct plugin slots (laptops only 
> AFAIK)

These both generally use ide-cs and the patch was written with this in
mind. 

There are a small number of broken adaptors which have been discussed
and the known ones are already worked around. 

> , 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.

USB devices have secondary controllers between the card and the USB bus.
The ide interface is not exposed to the system and they're handled by a
totally different interface and driver (sd = scsidisk). This patch
doesn't change anything to do with that and their behaviour is correct.

Richard


  reply	other threads:[~2005-11-09 21:37 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 ` 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
2005-11-09 21:37               ` Richard Purdie [this message]
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=1131572234.8506.130.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=damir.perisa@solnet.ch \
    --cc=davidsen@tmr.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome