All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Evgeni Golov <evgeni@debian.org>
Cc: "Dorau, Lukasz" <lukasz.dorau@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Patelczyk, Maciej" <maciej.patelczyk@intel.com>
Subject: Re: [PATCH] ISCI: add more PCI IDs
Date: Tue, 30 Apr 2013 10:33:37 -0700	[thread overview]
Message-ID: <51800071.1060001@intel.com> (raw)
In-Reply-To: <1367327568-12196-1-git-send-email-evgeni@debian.org>

On 04/30/2013 06:12 AM, Evgeni Golov wrote:
> These are found in e.g. the R2000GZ/GL machines.

Nack. These PCI device IDs are reserved for third party device drivers. 
Most likely that machine has a third party OROM as well.


> ---
>   drivers/scsi/isci/init.c |    4 ++++
>   1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/scsi/isci/init.c b/drivers/scsi/isci/init.c
> index 2839baa..d1ec2bd 100644
> --- a/drivers/scsi/isci/init.c
> +++ b/drivers/scsi/isci/init.c
> @@ -82,12 +82,16 @@ static DEFINE_PCI_DEVICE_TABLE(isci_id_table) = {
>   	{ PCI_VDEVICE(INTEL, 0x1D67),},
>   	{ PCI_VDEVICE(INTEL, 0x1D69),},
>   	{ PCI_VDEVICE(INTEL, 0x1D6B),},
> +	{ PCI_VDEVICE(INTEL, 0x1D6D),},
> +	{ PCI_VDEVICE(INTEL, 0x1D6F),},
>   	{ PCI_VDEVICE(INTEL, 0x1D60),},
>   	{ PCI_VDEVICE(INTEL, 0x1D62),},
>   	{ PCI_VDEVICE(INTEL, 0x1D64),},
>   	{ PCI_VDEVICE(INTEL, 0x1D66),},
>   	{ PCI_VDEVICE(INTEL, 0x1D68),},
>   	{ PCI_VDEVICE(INTEL, 0x1D6A),},
> +	{ PCI_VDEVICE(INTEL, 0x1D6C),},
> +	{ PCI_VDEVICE(INTEL, 0x1D6E),},
>   	{}
>   };
>   


-- 

Dave Jiang
Application Engineer, Storage Divsion
Intel Corp.
dave.jiang@intel.com


  reply	other threads:[~2013-04-30 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 13:12 [PATCH] ISCI: add more PCI IDs Evgeni Golov
2013-04-30 17:33 ` Dave Jiang [this message]
2013-04-30 18:26   ` Evgeni Golov
2013-04-30 20:35     ` Dave Jiang

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=51800071.1060001@intel.com \
    --to=dave.jiang@intel.com \
    --cc=evgeni@debian.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lukasz.dorau@intel.com \
    --cc=maciej.patelczyk@intel.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.