From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Frans Pop <elendil@planet.nl>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: No IDE drivers loaded for Toshiba Satellite 320 CDS
Date: Tue, 15 Apr 2008 11:37:26 +0900 [thread overview]
Message-ID: <480414E6.2090205@gmail.com> (raw)
In-Reply-To: <20080414145302.4239b0b9@core>
Alan Cox wrote:
>> If a driver supports a device with dual interfaces, then it better
>> reserve both sets of ports to prevent the generic driver from trying to
>> use them.
>
> That isn't the problem. The generic driver doesn't know if there is
> another valid driver for the ports - how can it - and the other driver
> may not be loaded first so cannot reserve the ports. If you load the
> generic driver last then you should be fine, and the link order for IDE
> and libata puts acpi, pci generic and legacy at the end for good reason.
>
> Libata pata_legacy has some smarts in this area but they are only good
> for the common cases.
Always loading generic or ata_generic used to be safe. It's still
pretty safe but not as much as before. Nowadays, there are good number
of controllers which have dual interfaces. Usually an ahci interface
and a legacy one but there are other controllers which also implement
dual interface.
Because PCI BARs usually contain IO regions for legacy interface in PCI
BAR 0-4, the native driver can work it out by claiming all PCI BARs on
attach, which I learned the hard way after seeing the generic driver
borking the native one on certain configurations. The thing I'm worried
about is that there are a lot of vendors making this type of controllers
nowadays and a lot of BIOS implementations for each of them. And of
course each BIOS implementation has its own many ways of configuring the
dual mode (or more thanks to fake RAIDs) controller.
I wouldn't be too surprised if one of those plethora of configurations
gets the compatible IO port and BAR configurations mismatched.
Especially when the controller is put into native mode. It's entirely
possible to leave the compatible IO ports enabled while not setting the
PCI BARs accordingly. Some of them might even think that's better to
prevent IDE drivers from attaching to it.
So, I don't really want to depend on that. I don't know. Do I sound
paranoid?
--
tejun
next prev parent reply other threads:[~2008-04-15 2:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 13:24 No IDE drivers loaded for Toshiba Satellite 320 CDS Frans Pop
2008-04-02 13:27 ` Frans Pop
2008-04-02 13:57 ` Lennart Sorensen
2008-04-02 14:29 ` Frans Pop
2008-04-02 15:46 ` Lennart Sorensen
2008-04-02 16:20 ` Frans Pop
2008-04-02 19:49 ` Lennart Sorensen
2008-04-03 17:47 ` Frans Pop
2008-04-03 19:31 ` Lennart Sorensen
2008-04-04 6:59 ` Frans Pop
2008-04-13 2:39 ` Tejun Heo
2008-04-13 13:59 ` Frans Pop
2008-04-14 13:52 ` Lennart Sorensen
2008-04-14 13:56 ` Alan Cox
2008-04-14 15:29 ` Frans Pop
2008-04-14 15:48 ` Frans Pop
2008-04-14 13:47 ` Lennart Sorensen
2008-04-14 13:53 ` Alan Cox
2008-04-15 2:37 ` Tejun Heo [this message]
2008-04-15 10:04 ` Alan Cox
2008-04-15 23:25 ` Tejun Heo
2008-04-15 14:47 ` Lennart Sorensen
2008-04-15 23:31 ` Tejun Heo
2008-04-16 18:08 ` Frans Pop
2008-04-16 22:12 ` Tejun Heo
2008-04-17 14:05 ` Lennart Sorensen
2008-04-24 3:48 ` Tejun Heo
2008-04-16 23:24 ` Alan Cox
2008-04-02 16:33 ` Ondrej Zary
2008-04-02 20:05 ` Lennart Sorensen
2008-04-02 20:10 ` Ondrej Zary
2008-04-02 20:22 ` Lennart Sorensen
2008-04-02 20:34 ` Ondrej Zary
2008-04-03 17:50 ` Alan Cox
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=480414E6.2090205@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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).