linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Henning Schmiedehausen <hps@intermeta.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux IDE Mailingliste <linux-ide@vger.kernel.org>
Subject: Re: PCI Constants Update for SATA Driver
Date: Wed, 02 Mar 2005 12:46:30 +1100	[thread overview]
Message-ID: <1109727990.5610.75.camel@gaston> (raw)
In-Reply-To: <1109526163.19325.2.camel@forge.intermeta.de>

On Sun, 2005-02-27 at 18:42 +0100, Henning Schmiedehausen wrote:
 static struct pci_device_id k2_sata_pci_tbl[] = {
-       { 0x1166, 0x0240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
-       { 0x1166, 0x0241, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
-       { 0x1166, 0x0242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
+       { PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_K2_240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
+       { PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_K2_241, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
+       { PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_K2_242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
        { }

I'm not sure the "K2" in the names here it correct. K2 is Apple's G5 IO
chip, which happens to include a serverworks controller. Jeff should
probably fix the constants to the real cell names :) Besides, K2 afaik
only ever contains a 240...
Ben.



      parent reply	other threads:[~2005-03-02  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 17:42 PCI Constants Update for SATA Driver Henning Schmiedehausen
2005-02-27 18:08 ` Jeff Garzik
2005-02-27 19:20   ` Henning Schmiedehausen
2005-02-27 19:52     ` Jeff Garzik
2005-02-27 20:05       ` Henning Schmiedehausen
2005-02-27 20:07         ` Jeff Garzik
2005-03-02  1:47   ` Benjamin Herrenschmidt
2005-03-02  5:49     ` Jeff Garzik
2005-03-02  1:46 ` Benjamin Herrenschmidt [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=1109727990.5610.75.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=hps@intermeta.de \
    --cc=jgarzik@pobox.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).