From: "O.Sezer" <sezeroz@ttnet.net.tr>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH 2.4] blacklist a device in usb-storage
Date: Mon, 16 Aug 2004 10:48:12 +0300 [thread overview]
Message-ID: <412066BC.9040503@ttnet.net.tr> (raw)
In-Reply-To: <20040815235204.0e9ec874@lembas.zaitcev.lan>
Pete Zaitcev wrote:
> On Sat, 14 Aug 2004 21:22:20 +0300
> "O.Sezer" <sezeroz@ttnet.net.tr> wrote:
>
>
>>The disk in question is VID/PID=0b86:5110 32mb JMTek/eXputer disk.
>>http://www.qbik.ch/usb/devices/showdev.php?id=1092 says it can
>>never be supported through usb-storage because it claims to be
>>usb storage compliant but is not.
>>[...]
>>If there's any other way of preventing usb-storage to take-
>>over this disk, then tell me and despise my ignorance,
>>Otherwise, Marcelo please apply ;)
>
>
> I do not understand what the objective might be. Just do not
> use that thing with Linux kernel 2.4. Why do you wish "to revent
> usb-storage from taking over this disk"?
>
> -- Pete
As I said above, I cannot prevent accidentals (VID/PIDs aren't
printed on the disk, yo know...) And usb-storage must not deal
with disks that it cannot deal with:
1. This particular disk can lead to panics as I said.
2. If someone ever writes a driver specific to this device (I
know it's less than highly unlikely), than it would be also
useful in that case if the disk isn't tried to be owned by
usb-storage. That, I think applies as a general case, too.
Ozkan Sezer
next prev parent reply other threads:[~2004-08-16 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1092508141.32379.linux-kernel2news@redhat.com>
2004-08-16 6:52 ` [PATCH 2.4] blacklist a device in usb-storage Pete Zaitcev
2004-08-16 7:48 ` O.Sezer [this message]
2004-08-16 15:07 ` Pete Zaitcev
2004-08-16 15:54 ` O.Sezer
2004-08-16 22:32 ` Pete Zaitcev
2004-08-17 11:12 ` O.Sezer
2004-08-16 16:12 ` O.Sezer
2004-08-14 18:22 O.Sezer
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=412066BC.9040503@ttnet.net.tr \
--to=sezeroz@ttnet.net.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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