From: Dave Jones <davej@redhat.com>
To: akpm@osdl.org
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org, mail@hboeck.de
Subject: Re: [patch 1/1] Whitelist-Entry (FORCELUN) for SGS Thomson Microelectronics Cytronix 6in1 card reader in scsi_devinfo.c
Date: Wed, 9 Mar 2005 13:34:21 -0500 [thread overview]
Message-ID: <20050309183420.GA12748@redhat.com> (raw)
In-Reply-To: <200503090903.j2993vjp022052@shell0.pdx.osdl.net>
On Wed, Mar 09, 2005 at 01:03:32AM -0800, Andrew Morton wrote:
>
> From: Hanno Boeck <mail@hboeck.de>
>
> I have a usb-cardreader here that needs some FORCELUN-entries in
> scsi_devinfo.c.
>
> lsusb says about the device:
>
> Bus 001 Device 003: ID 0483:1307 SGS Thomson Microelectronics Cytronix 6in1 card reader
>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
The problem with these devices is there are so many of them,
(The Fedora kernel had over a dozen additions to the whitelist at one point),
and there were still devices getting reported that weren't detected.
There's no way to stay on top of the amount of these things that are being produced.
There are only two sane solutions that I see
1) Have usb-storage tell the scsi layer "Its a card reader, scan all luns"
or
2) enable scanning of all luns, and blacklist any devices that misbehave.
I chose (2) in the Fedora kernel, and so far, only 1 device got picked up
that needed adding to the blacklist.
Dave
prev parent reply other threads:[~2005-03-09 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 9:03 [patch 1/1] Whitelist-Entry (FORCELUN) for SGS Thomson Microelectronics Cytronix 6in1 card reader in scsi_devinfo.c akpm
2005-03-09 16:05 ` Patrick Mansfield
2005-03-09 18:34 ` Dave Jones [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=20050309183420.GA12748@redhat.com \
--to=davej@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mail@hboeck.de \
/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