From: Jeff Garzik <jeff@garzik.org>
To: Robert Richter <robert.richter@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Add PCI IDs for AMD Barcelona PCI devices
Date: Fri, 27 Jun 2008 18:15:06 -0400 [thread overview]
Message-ID: <4865666A.9040306@garzik.org> (raw)
In-Reply-To: <20080627140905.EBD1C83D4@erda.amd.com>
Robert Richter wrote:
> Signed-off-by: Robert Richter <robert.richter@amd.com>
> ---
> include/linux/pci_ids.h | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index eafc9d6..4a2557c 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -497,6 +497,11 @@
> #define PCI_DEVICE_ID_AMD_K8_NB_ADDRMAP 0x1101
> #define PCI_DEVICE_ID_AMD_K8_NB_MEMCTL 0x1102
> #define PCI_DEVICE_ID_AMD_K8_NB_MISC 0x1103
> +#define PCI_DEVICE_ID_AMD_10H_NB_HT 0x1200
> +#define PCI_DEVICE_ID_AMD_10H_NB_MAP 0x1201
> +#define PCI_DEVICE_ID_AMD_10H_NB_DRAM 0x1202
> +#define PCI_DEVICE_ID_AMD_10H_NB_MISC 0x1203
> +#define PCI_DEVICE_ID_AMD_10H_NB_LINK 0x1204
> #define PCI_DEVICE_ID_AMD_LANCE 0x2000
> #define PCI_DEVICE_ID_AMD_LANCE_HOME 0x2001
Are these constants going to be used in future kernels?
We don't necessarily want to create constants for each PCI ID in
existence. A more comprehensive database is kept at
http://pciids.sourceforge.net/
Jeff
next prev parent reply other threads:[~2008-06-27 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 14:04 [PATCH] x86: Add PCI IDs for AMD Barcelona PCI devices Robert Richter
2008-06-27 22:15 ` Jeff Garzik [this message]
2008-06-30 10:44 ` Robert Richter
2008-07-11 12:46 ` [osrc-patches] " Robert Richter
2008-07-12 4:56 ` Ingo Molnar
2008-07-12 5:08 ` Arjan van de Ven
2008-07-14 9:15 ` Robert Richter
2008-07-14 15:54 ` Jesse Barnes
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=4865666A.9040306@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robert.richter@amd.com \
--cc=tglx@linutronix.de \
/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.