From: Dave Jones <davej@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James.Bottomley@SteelEye.com, zaitcev@redhat.com
Subject: Re: [patch] 2.6 -- add IOI Media Bay to SCSI quirk list
Date: Fri, 13 Aug 2004 00:39:50 +0100 [thread overview]
Message-ID: <20040812233950.GA26970@redhat.com> (raw)
In-Reply-To: <411BF6A5.2030306@tuxdriver.com>
On Thu, Aug 12, 2004 at 07:00:53PM -0400, John W. Linville wrote:
> Patrick Mansfield wrote:
>
> >We seem to be getting quite a few of these. In theory we could add a line
> >like this for every multi-lun SCSI device.
> Isn't that what the quirk list is for?
>
> >Can you instead try booting with scsi_mod.max_luns=8 (or such) or build
> >with SCSI_MULTI_LUN enabled?
>
> That works for my box, but what about for others? Like those who may
> have both a multi-lun device and a single-lun device that hangs on a
> non-zero lun? What about the average luser who can't be bothered to
> hack-up his startup scripts or *gasp* rebuild his kernel?
>
> It seems like the quirk list is there for a reason. If we start
> rejecting certain devices, then what is the criteria for a device to
> actually make it on the list?
I hit the same problem when I tried to get James to merge around a half dozen
or so entries (thats since grown to almost double that). One possibility
is to fix this in the USB storage layer. (Assume all USB SCSI devices are
capable of handling MULTI_LUN without problem).
I believe Pete Zaitcev was writing an alternative usb-storage driver
that did something along these lines, but I'm not sure of the details.
Dave
next prev parent reply other threads:[~2004-08-12 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 21:37 [patch] 2.6 -- add IOI Media Bay to SCSI quirk list John W. Linville
2004-08-12 22:51 ` Patrick Mansfield
2004-08-12 23:00 ` John W. Linville
2004-08-12 23:39 ` Dave Jones [this message]
2004-08-13 0:27 ` Patrick Mansfield
2004-08-13 1:21 ` John W. Linville
2004-08-13 21:32 ` Marcelo Tosatti
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=20040812233950.GA26970@redhat.com \
--to=davej@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=patmans@us.ibm.com \
--cc=zaitcev@redhat.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