From: Alan <alan@lxorguk.ukuu.org.uk>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI driver support for pata
Date: Fri, 23 Feb 2007 15:53:06 +0000 [thread overview]
Message-ID: <20070223155306.0e8aeee5@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <45DEFC48.8060802@shaw.ca>
> Unfortunately, link order appears to have no effect when the drivers in
> question are built modular, as appears to be the typical case, unlike
> old IDE where they were generally built in because of all the other
> busted behavior if you built the drivers as modules. This means that
> userspace tools like mkinitrd, udev, etc. will need to be taught to try
> to load drivers in this order, and not to try to use pata_acpi on an
They already have to do this because of the sata_nv module for one
example where ordering matters. So it's already the case, and it has to
be dealt with run time because the resolution is dynamic and depends upon
user configurable boot settings.
> Plus there's controller hotplug - if multiple loaded drivers are listed
> as being able to drive a piece of hardware, does anything define which
> driver will get first dibs on attaching to the device when it's
> hotplugged? I don't know how this ordering will be enforced in that case.
That feature is lacking in the PCI layer at the moment which is
problematic. When the PCI layer develops this feature I'll make use of
it. In the mean time send patches to Greg KH for that if you want to hack
on it.
Alan
next prev parent reply other threads:[~2007-02-23 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.IjFXvdcBtWXV65pRZipPd0NVTOA@ifi.uio.no>
2007-02-22 5:45 ` Robert Hancock
2007-02-22 6:58 ` Jeff Garzik
2007-02-22 14:24 ` Alan
2007-02-22 17:11 ` Jeff Garzik
2007-02-22 18:29 ` Alan
2007-02-23 0:15 ` Robert Hancock
2007-02-23 9:36 ` Allen Martin
2007-02-23 12:50 ` Alan
2007-02-23 14:38 ` Robert Hancock
2007-02-23 15:53 ` Alan [this message]
2007-02-20 18:12 Alan
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=20070223155306.0e8aeee5@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.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
all inboxes | Powered by JetHome®