From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Peer Chen <peerchen@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, jeff <jeff@garzik.org>
Subject: Re: [PATCH] ahci: Add MCP79 support to AHCI driver
Date: Mon, 24 Sep 2007 16:53:24 +0400 [thread overview]
Message-ID: <46F7B344.7050903@ru.mvista.com> (raw)
In-Reply-To: <200709241016214230742@gmail.com>
Hello.
Peer Chen wrote:
> Code change, remove some Device IDs.
> Signed-off-by: Peer Chen <peerchen@gmail.com>
> ---
> --- linux-2.6.23-rc7/drivers/ata/ahci.c.orig 2007-09-20 11:01:55.000000000 -0400
> +++ linux-2.6.23-rc7/drivers/ata/ahci.c 2007-09-24 10:08:03.000000000 -0400
> @@ -472,6 +472,14 @@ static const struct pci_device_id ahci_p
> { PCI_VDEVICE(NVIDIA, 0x0ad9), board_ahci }, /* MCP77 */
> { PCI_VDEVICE(NVIDIA, 0x0ada), board_ahci }, /* MCP77 */
> { PCI_VDEVICE(NVIDIA, 0x0adb), board_ahci }, /* MCP77 */
> + { PCI_VDEVICE(NVIDIA, 0x0ab8), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0ab9), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0aba), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0abb), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0abc), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0abd), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0abe), board_ahci }, /* MCP79 */
> + { PCI_VDEVICE(NVIDIA, 0x0abf), board_ahci }, /* MCP79 */
I wonder whether all of those 8 IDs belong to AHCI controllers...
MBR, Sergei
next prev parent reply other threads:[~2007-09-24 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 6:06 [PATCH] ahci: Add MCP79 support to AHCI driver Peer Chen
2007-09-21 10:39 ` Alan Cox
2007-09-24 2:02 ` Peer Chen
2007-09-24 2:16 ` Peer Chen
2007-09-24 12:53 ` Sergei Shtylyov [this message]
2007-09-25 2:58 ` Peer Chen
2007-10-02 15:31 ` Jeff Garzik
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=46F7B344.7050903@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peerchen@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.