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 13:35:33 -0700 [thread overview]
Message-ID: <51802B15.2020205@intel.com> (raw)
In-Reply-To: <51800CC0.3010609@debian.org>
On 04/30/2013 11:26 AM, Evgeni Golov wrote:
> On 04/30/2013 07:33 PM, Dave Jiang 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.
> OROM = option ROM? Yes, it has the "white" C600 expansion pack, so we
> can use all 8 ports of the SAS controller. But we do not want (and
> actually cannot) use the Intel-provided megasr driver (the machines run
> Debian Wheezy with the 3.2 kernel).
>
> Can we get the controller to use the "regular" PCI ID instead?
Yes. You need an Intel Option ROM instead of the LSI. You need to talk
to whomever sold you the system and get the Intel OROM. Also just an
FYI, the isci driver didn't get a lot of the issues sorted out until
kernel 3.7. The 3.2 driver is quite old and you may run into issues.
Obviously you already know you can patch the driver to pick up those
device IDs, but I don't know what the LSI OROM does with the OEM
parameters and if will provide it to the isci driver properly.
> Regards
> Evgeni
--
Dave Jiang
Application Engineer, Storage Divsion
Intel Corp.
dave.jiang@intel.com
prev parent reply other threads:[~2013-04-30 20:35 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
2013-04-30 18:26 ` Evgeni Golov
2013-04-30 20:35 ` Dave Jiang [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=51802B15.2020205@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox