From: Jason Gaston <jason.d.gaston@intel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.11.6 1/6] irq and pci_ids: patch for Intel ESB2
Date: Wed, 6 Apr 2005 08:57:31 -0700 [thread overview]
Message-ID: <200504060857.31890.jason.d.gaston@intel.com> (raw)
In-Reply-To: <200504050800.44117.jason.d.gaston@intel.com>
Hello,
Do I also need to create and submit these patches for 2.6.12-rc2 in order to get them into 2.6.12 or will these make it into 2.6.12 as is?
Thanks,
Jason Gaston
On Tuesday 05 April 2005 08:00, Jason Gaston wrote:
> Hello,
>
> This patch adds the Intel ESB2 DID's to the irq.c and pci_ids.h files. This patch was built against the 2.6.11.6 kernel.
> If acceptable, please apply.
>
> Thanks,
>
> Jason Gaston
>
> Signed-off-by: Jason Gaston <Jason.d.gaston@intel.com>
>
> --- linux-2.6.11.6/arch/i386/pci/irq.c.orig 2005-03-28 08:44:26.350888632 -0800
> +++ linux-2.6.11.6/arch/i386/pci/irq.c 2005-03-28 08:49:38.961364616 -0800
> @@ -495,6 +495,7 @@
> case PCI_DEVICE_ID_INTEL_ICH6_1:
> case PCI_DEVICE_ID_INTEL_ICH7_0:
> case PCI_DEVICE_ID_INTEL_ICH7_1:
> + case PCI_DEVICE_ID_INTEL_ESB2_0:
> r->name = "PIIX/ICH";
> r->get = pirq_piix_get;
> r->set = pirq_piix_set;
> --- linux-2.6.11.6/include/linux/pci_ids.h.orig 2005-03-28 09:09:51.343054584 -0800
> +++ linux-2.6.11.6/include/linux/pci_ids.h 2005-03-28 09:29:16.883865448 -0800
> @@ -2260,6 +2260,25 @@
> #define PCI_DEVICE_ID_INTEL_ICH6_17 0x266d
> #define PCI_DEVICE_ID_INTEL_ICH6_18 0x266e
> #define PCI_DEVICE_ID_INTEL_ICH6_19 0x266f
> +#define PCI_DEVICE_ID_INTEL_ESB2_0 0x2670
> +#define PCI_DEVICE_ID_INTEL_ESB2_1 0x2680
> +#define PCI_DEVICE_ID_INTEL_ESB2_2 0x2681
> +#define PCI_DEVICE_ID_INTEL_ESB2_3 0x2682
> +#define PCI_DEVICE_ID_INTEL_ESB2_4 0x2683
> +#define PCI_DEVICE_ID_INTEL_ESB2_5 0x2688
> +#define PCI_DEVICE_ID_INTEL_ESB2_6 0x2689
> +#define PCI_DEVICE_ID_INTEL_ESB2_7 0x268a
> +#define PCI_DEVICE_ID_INTEL_ESB2_8 0x268b
> +#define PCI_DEVICE_ID_INTEL_ESB2_9 0x268c
> +#define PCI_DEVICE_ID_INTEL_ESB2_10 0x2690
> +#define PCI_DEVICE_ID_INTEL_ESB2_11 0x2692
> +#define PCI_DEVICE_ID_INTEL_ESB2_12 0x2694
> +#define PCI_DEVICE_ID_INTEL_ESB2_13 0x2696
> +#define PCI_DEVICE_ID_INTEL_ESB2_14 0x2698
> +#define PCI_DEVICE_ID_INTEL_ESB2_15 0x2699
> +#define PCI_DEVICE_ID_INTEL_ESB2_16 0x269a
> +#define PCI_DEVICE_ID_INTEL_ESB2_17 0x269b
> +#define PCI_DEVICE_ID_INTEL_ESB2_18 0x269e
> #define PCI_DEVICE_ID_INTEL_ICH7_0 0x27b8
> #define PCI_DEVICE_ID_INTEL_ICH7_1 0x27b1
> #define PCI_DEVICE_ID_INTEL_ICH7_2 0x27c0
> @@ -2285,6 +2304,18 @@
> #define PCI_DEVICE_ID_INTEL_ICH7_22 0x27e0
> #define PCI_DEVICE_ID_INTEL_ICH7_23 0x27e2
> #define PCI_DEVICE_ID_INTEL_82855PM_HB 0x3340
> +#define PCI_DEVICE_ID_INTEL_ESB2_19 0x3500
> +#define PCI_DEVICE_ID_INTEL_ESB2_20 0x3501
> +#define PCI_DEVICE_ID_INTEL_ESB2_21 0x3504
> +#define PCI_DEVICE_ID_INTEL_ESB2_22 0x3505
> +#define PCI_DEVICE_ID_INTEL_ESB2_23 0x350c
> +#define PCI_DEVICE_ID_INTEL_ESB2_24 0x350d
> +#define PCI_DEVICE_ID_INTEL_ESB2_25 0x3510
> +#define PCI_DEVICE_ID_INTEL_ESB2_26 0x3511
> +#define PCI_DEVICE_ID_INTEL_ESB2_27 0x3514
> +#define PCI_DEVICE_ID_INTEL_ESB2_28 0x3515
> +#define PCI_DEVICE_ID_INTEL_ESB2_29 0x3518
> +#define PCI_DEVICE_ID_INTEL_ESB2_30 0x3519
> #define PCI_DEVICE_ID_INTEL_82830_HB 0x3575
> #define PCI_DEVICE_ID_INTEL_82830_CGC 0x3577
> #define PCI_DEVICE_ID_INTEL_82855GM_HB 0x3580
>
next prev parent reply other threads:[~2005-04-06 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 15:00 Jason Gaston
2005-04-06 15:57 ` Jason Gaston [this message]
2005-04-06 22:35 ` Andrew Morton
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=200504060857.31890.jason.d.gaston@intel.com \
--to=jason.d.gaston@intel.com \
--cc=linux-kernel@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
Powered by JetHome