From: Jeff Garzik <jeff@garzik.org>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: no need to add new DID's to AHCI driver?
Date: Wed, 22 Aug 2007 15:19:13 -0400 [thread overview]
Message-ID: <46CC8C31.3040502@garzik.org> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE0701AE8117@orsmsx420.amr.corp.intel.com>
Gaston, Jason D wrote:
> Hello,
>
> Now that the AHCI driver has support for all controllers with the 0x0106
> (AHCI) class code, I am not planning on adding controller DeviceID's for
> AHCI controllers. I want to verify that this is the correct course of
> action.
>
> Note: I still will have to add the Intel SW "RAID" controller
> DeviceID's as they have a 0x0104 (RAID) class code.
Yep, that's fine -- and the encouraged direction.
The ideal situation for users is when new hardware is "automagically"
supported, without needing any driver PCI ID modifications at all.
Jeff
next prev parent reply other threads:[~2007-08-22 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:19 no need to add new DID's to AHCI driver? Gaston, Jason D
2007-08-22 19:19 ` Jeff Garzik [this message]
2007-08-23 0:53 ` Tejun Heo
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=46CC8C31.3040502@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=jason.d.gaston@intel.com \
--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).