l.org'
Subject: RE: Request to add EMC Invista to the v2.6.x SCSI Blacklist...
On Thu, 2005-08-11 at 11:45 -0400, conway, heather wrote:
> The information that I was provided is that the default for the Invista is
> to report back as SCSI-3 compliant.
> Hope this helps.
Well, actuall
On Thu, 2005-08-11 at 11:45 -0400, conway, heather wrote:
> The information that I was provided is that the default for the Invista is
> to report back as SCSI-3 compliant.
> Hope this helps.
Well, actually, now I'm confused. REPORT_LUNS is mandatory for a SCSI3
compliant device, and if the devi
: 'linux-scsi@vger.kernel.org'
Subject: Re: Request to add EMC Invista to the v2.6.x SCSI Blacklist...
On Wed, 2005-07-27 at 10:22 -0400, conway, heather wrote:
> I'd like to request that the enclosed patch to scsi_devinfo.c be
considered
> for inclusion in the v2.6.x kernel. T
On Wed, 2005-07-27 at 10:22 -0400, conway, heather wrote:
> I'd like to request that the enclosed patch to scsi_devinfo.c be considered
> for inclusion in the v2.6.x kernel. This would add support for sparse LUNs
> and large LUNs for the EMC Invista product.
For 2.6, I assume this device report
Hi,
I'd like to request that the enclosed patch to scsi_devinfo.c be considered
for inclusion in the v2.6.x kernel. This would add support for sparse LUNs
and large LUNs for the EMC Invista product.
Thanks for your consideration.
Heather
<>
scsi_devinfo_invista.patch
Description: Binary data
5 matches
Mail list logo
