From: Dominik Brodowski <linux@dominikbrodowski.net>
To: torvalds@osdl.org, akpm@osdl.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: [PATCH] pcmcia: defer ide-cs initialization after other IDE drivers started up [Was: Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)]
Date: Mon, 1 Aug 2005 14:16:55 +0200 [thread overview]
Message-ID: <20050801121655.GA3014@isilmar.linta.de> (raw)
In-Reply-To: <20050801074831.A677@flint.arm.linux.org.uk>
On Mon, Aug 01, 2005 at 07:48:31AM +0100, Russell King wrote:
> On Mon, Aug 01, 2005 at 02:01:07AM +0100, Alan Cox wrote:
> > On Sad, 2005-07-30 at 22:36 +0100, Russell King wrote:
> > > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > > longer get hotplug events to setup networking for PCMCIA network cards
> > > already inserted. Consequently, if you are relying on /sbin/hotplug to
> > > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > > startup binding the driver, it won't happen.
> >
> > So eth0 now randomly changes between on board and PCMCIA depending upon
> > whether the PCMCIA card was inserted or not, and your disks re-order
> > themselves in the same situation. That'll be funny if anyone does a
> > mkswap to share their swap between Linux and Windows. Gosh look there
> > goes the root partition.
> >
> > I'm hoping thats not what you are implying. Especially for disks,
> > network is much much less of an issue.
>
> If you have the socket driver as a module, as some (most?) distros do,
> then of course such cards won't be detected at boot time. If PCMCIA
> and the socket driver are built-in, along with the card driver, then
> I guess this possibility may well exist - it does for NE2K cards.
Linus, Andrew,
Please apply this for 2.6.13 - Thanks,
Dominik
Avoid registering PCMCIA CF cards before other IDE stuff. This means the risk
of /dev/hd* being re-ordered is lessened. The _sane_ thing to assert any
ordering is to use udev, nameif and so on, of course.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Index: 2.6.13-rc4-git1/drivers/ide/legacy/ide-cs.c
===================================================================
--- 2.6.13-rc4-git1.orig/drivers/ide/legacy/ide-cs.c
+++ 2.6.13-rc4-git1/drivers/ide/legacy/ide-cs.c
@@ -508,5 +508,5 @@ static void __exit exit_ide_cs(void)
BUG_ON(dev_list != NULL);
}
-module_init(init_ide_cs);
+late_initcall(init_ide_cs);
module_exit(exit_ide_cs);
prev parent reply other threads:[~2005-08-01 12:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 13:04 -rc4: arm broken? Pavel Machek
2005-07-30 16:13 ` Russell King
2005-07-30 16:45 ` Richard Purdie
2005-07-30 19:02 ` Pavel Machek
2005-07-30 19:15 ` Russell King
2005-07-30 19:18 ` Pavel Machek
2005-07-30 21:36 ` Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?) Russell King
2005-07-30 21:41 ` Pavel Machek
2005-07-30 21:55 ` Russell King
2005-07-30 22:30 ` Pavel Machek
2005-07-30 22:43 ` Dominik Brodowski
2005-07-30 22:17 ` Grant Coady
2005-07-30 22:26 ` Russell King
2005-07-30 23:31 ` Richard Purdie
2005-08-01 1:01 ` Alan Cox
2005-08-01 6:48 ` Russell King
2005-08-01 12:16 ` Dominik Brodowski [this message]
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=20050801121655.GA3014@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.