From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@linux.intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, jeff@garzik.org, kay.sievers@suse.de
Subject: Re: [PATCH RFC] ata: Intel IDE-R support
Date: Thu, 19 Aug 2010 13:22:10 +0200 [thread overview]
Message-ID: <4C6D13E2.1010703@kernel.org> (raw)
In-Reply-To: <20100819110959.40312e58@linux.intel.com>
(cc'ing Kay, hi!)
Hello,
On 08/19/2010 12:09 PM, Alan Cox wrote:
>> what if ata_piix is already compiled in or already loaded but ahci is
>> not for an ich6 controller? We have priorities in the drivers, if the
>> user/admin wants to use the lower priority ones that much, he/she
>> shall. This isn't an issue. There's no way to hotplug intel IDEs
>> anyway.
>
> The PIIX4 in the IBM docking stations is hot plug - and its why I also
> have to check 0x40 and write it if zero. So the case exists.
I see. Most of the problems are solved by driver priority but yeah
that's an actual corner case. Driver priority doesn't work unless all
the matching drivers are loaded by the time driver matching starts, so
the same problem could happen with pata_acpi depending on probe order
during normal boot, so pata_acpi should be blacklisted by default.
Kay, there are a few ATA drivers with overlapping hardware support.
When all the drivers are built-in the kernel or none of them is loaded
as modules, priority among them as defined by link order is followed;
however, if one of the drivers is already loaded while other
overlapping ones are not, there's nothing which guarantees driver
probing would happen after modprobe for the device ID is complete,
right? So, the already loaded driver may be attached to the
controller even when there is a higher priority driver. Am I missing
something?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-19 11:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 15:56 [PATCH RFC] ata: Intel IDE-R support Alan Cox
2010-08-10 17:12 ` Sergei Shtylyov
2010-08-10 22:23 ` Alan Cox
2010-08-17 16:19 ` Tejun Heo
2010-08-17 16:42 ` Alan Cox
2010-08-17 16:30 ` Tejun Heo
2010-08-17 17:01 ` Alan Cox
2010-08-17 16:59 ` Tejun Heo
2010-08-17 18:23 ` Alan Cox
2010-08-18 6:19 ` Tejun Heo
2010-08-18 10:03 ` Alan Cox
2010-08-18 14:10 ` Tejun Heo
2010-08-18 15:15 ` Alan Cox
2010-08-19 9:37 ` Tejun Heo
2010-08-19 10:09 ` Alan Cox
2010-08-19 11:22 ` Tejun Heo [this message]
2010-08-19 11:35 ` Kay Sievers
2010-08-19 11:42 ` Tejun Heo
2010-08-19 12:24 ` Kay Sievers
2010-08-19 12:33 ` Tejun Heo
2010-08-19 12:52 ` Kay Sievers
2010-08-19 12:54 ` Tejun Heo
2010-08-19 13:08 ` Kay Sievers
2010-08-19 13:14 ` Tejun Heo
2010-08-19 12:56 ` Tejun Heo
2010-08-19 18:05 ` Jeff Garzik
2010-08-19 11:02 ` Tim Small
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=4C6D13E2.1010703@kernel.org \
--to=tj@kernel.org \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=kay.sievers@suse.de \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).