From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Conke Hu <conke.hu@amd.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: AHCI should try to claim all AHCI controllers
Date: Wed, 01 Nov 2006 00:35:09 -0500 [thread overview]
Message-ID: <4548320D.5090601@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610312120200.25218@g5.osdl.org>
Linus Torvalds wrote:
>
> On Wed, 1 Nov 2006, Jeff Garzik wrote:
>> For the benefit of others, some background: we should not be -removing- any
>> PCI IDs due to this, because quite often the PCI class code will be RAID or
>> something else, yet still be drive-able with this ahci driver.
>
> Well, it might obviously be worthwhile removing the PCI ID's that actually
> do say that they are AHCI. Maybe that's not all of them, but I wouldn't be
> surprised if it's actually the majority of them..
The same PCI ID maps to either RAID or AHCI. The PCI ID only changes
when it's no longer in AHCI mode (IDE/legacy mode).
To confuse matters even further, sometimes you can use AHCI even though
it claims it is in IDE mode. And the reverse is -often- true: you can
usually use legacy IDE mode even if the PCI ID and class code claim AHCI
mode.
Who knows what beasts lurk behind the same PCI ID...
> (We had the same issue with "PCI IDE controller". Some PCI IDE controllers
> are clearly exactly that from a programming interface standpoint, but
> because they support RAID in hardware, they claim to be RAID controllers,
> since that is more "glamorous". Gaah ;^).
Heck these days 'RAID' is a marketing requirement for your hardware,
regardless of its capabilities...
Jeff
next prev parent reply other threads:[~2006-11-01 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 15:06 AHCI should try to claim all AHCI controllers Conke Hu
2006-11-01 5:07 ` Jeff Garzik
2006-11-01 5:22 ` Linus Torvalds
2006-11-01 5:35 ` Jeff Garzik [this message]
2006-11-01 12:23 ` Alan Cox
2006-11-01 14:37 ` Mark Lord
2006-11-01 5:11 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 13:39 Conke Hu
2006-11-02 13:15 ` Martin Waitz
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=4548320D.5090601@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=conke.hu@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).