From: Jeff Garzik <jeff@garzik.org>
To: David Milburn <dmilburn@redhat.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream-fixes v2] ahci: add device IDs for Ibex Peak ahci controllers
Date: Tue, 28 Jul 2009 21:10:11 -0400 [thread overview]
Message-ID: <4A6FA173.4030905@garzik.org> (raw)
In-Reply-To: <20090722201556.GB10049@dhcp-210.hsv.redhat.com>
David Milburn wrote:
> Add device IDS for Ibex Peak SATA AHCI Controllers
>
> Signed-off-by: Jaroslav Kysela <jkysela@redhat.com>
> Signed-off-by: David Milburn <dmilburn@redhat.com>
> ---
> drivers/ata/ahci.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> index 336eb1e..958c1fa 100644
> --- a/drivers/ata/ahci.c
> +++ b/drivers/ata/ahci.c
> @@ -515,10 +515,14 @@ static const struct pci_device_id ahci_pci_tbl[] = {
> { PCI_VDEVICE(INTEL, 0x3a05), board_ahci }, /* ICH10 */
> { PCI_VDEVICE(INTEL, 0x3a22), board_ahci }, /* ICH10 */
> { PCI_VDEVICE(INTEL, 0x3a25), board_ahci }, /* ICH10 */
> + { PCI_VDEVICE(INTEL, 0x3b22), board_ahci }, /* PCH AHCI */
> + { PCI_VDEVICE(INTEL, 0x3b23), board_ahci }, /* PCH AHCI */
> { PCI_VDEVICE(INTEL, 0x3b24), board_ahci }, /* PCH RAID */
> { PCI_VDEVICE(INTEL, 0x3b25), board_ahci }, /* PCH RAID */
> + { PCI_VDEVICE(INTEL, 0x3b29), board_ahci }, /* PCH AHCI */
> { PCI_VDEVICE(INTEL, 0x3b2b), board_ahci }, /* PCH RAID */
> { PCI_VDEVICE(INTEL, 0x3b2c), board_ahci }, /* PCH RAID */
> + { PCI_VDEVICE(INTEL, 0x3b2f), board_ahci }, /* PCH AHCI */
>
> /* JMicron 360/1/3/5/6, match class to avoid IDE function */
> { PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
applied
prev parent reply other threads:[~2009-07-29 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 20:15 [PATCH #upstream-fixes v2] ahci: add device IDs for Ibex Peak ahci controllers David Milburn
2009-07-29 1:10 ` Jeff Garzik [this message]
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=4A6FA173.4030905@garzik.org \
--to=jeff@garzik.org \
--cc=dmilburn@redhat.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).