public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Greg KH <greg@kroah.com>
Cc: Damir Perisa <damir.perisa@solnet.ch>,
	linux-kernel@vger.kernel.org, akpm@osdl.org,
	Archlinux Developers <arch-dev@archlinux.org>
Subject: Re: ide-cs broken / udev magic
Date: Sat, 05 Nov 2005 02:06:52 +0000	[thread overview]
Message-ID: <1131156412.8256.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20051104232854.GA21173@kroah.com>

On Fri, 2005-11-04 at 15:28 -0800, Greg KH wrote:
> On Sat, Nov 05, 2005 at 12:22:36AM +0100, Damir Perisa wrote:
> > as other distros use to ignore removable ide's. now i need to load the 
> > ide-cs module by hand (bad thing, as module should be loaded 
> > automagically with udev/hotplug) but on the other hand, no more 
> > dmesg-spamming, no freezes and also the node is created successfully 
> > after module is loaded. 
> 
> This shouldn't have changed the "autoload" capability of the module at
> all.  It should still being loaded with whatever means it was being
> loaded before.  But that's a distro specific question, not a
> linux-kernel issue.
> 
> > is there planed action to change ide-cs to work without making it being 
> > ignored ... without this exception that needs to be specified in udev 
> > rules? 
> 
> Yes, there are patches somewhere to fix this up, I'm trying to track
> them down.

This is a bug in the ide layer as CF pcmcia devices are marked as
removable but the devices (and the behaviour of ide-cs) does not fit the
Linux definition of such devices.

See this thread: http://lkml.org/lkml/2005/9/21/118

I'm hoping to work out a patch to change this in a manner acceptable to
everyone but haven't found time yet. I've not forgotten though.

Richard



  reply	other threads:[~2005-11-05  2:07 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
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 [this message]
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=1131156412.8256.76.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=akpm@osdl.org \
    --cc=arch-dev@archlinux.org \
    --cc=damir.perisa@solnet.ch \
    --cc=greg@kroah.com \
    --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