From: Rob Browning <rlb@defaultvalue.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
"Randy.Dunlap" <rddunlap@osdl.org>, Adrian Bunk <bunk@stusta.de>,
Greg KH <greg@kroah.com>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: RFC: [2.6 patch] let BLK_DEV_UB depend on EMBEDDED
Date: Wed, 22 Dec 2004 02:10:00 -0600 [thread overview]
Message-ID: <87u0qepxd3.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <20041219223723.3e861fc5@lembas.zaitcev.lan> (Pete Zaitcev's message of "Sun, 19 Dec 2004 22:37:23 -0800")
Pete Zaitcev <zaitcev@redhat.com> writes:
> Is it that bad, really? Honestly, I could not imagine users can be
> so dumb. The option defaults to off. There is a warning in the
> Kconfig. And yet they first enable it and then complain about it. I
> don't know what to do about it, either.
Well, I presume you know this, but at least in 2.6.9, there's no
warning. When I read it, it said:
CONFIG_BLK_DEV_UB:
This driver supports certain USB attached storage devices
such as flash keys.
If unsure, say N.
which sounded potentially useful, and certainly didn't give the
impression that the driver was likely to perform terribly in common
cases (i.e. when using an external drive).
The sample Kconfig warnings I saw posted later in this thread would
certainly have given enough information to know to avoid the driver,
though if true, this might be even clearer:
Note: this driver does not coexist well with usb-storage, and
usb-storage is is often the best driver for common devices like
external drive enclosures. At the moment, usb-storage may peform
dramatically better for those devices.
If you're not certain you need this driver, you should probably
say 'N' here, and choose usb-storage instead.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2004-12-22 8:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 0:16 RFC: [2.6 patch] let BLK_DEV_UB depend on EMBEDDED Adrian Bunk
2004-12-20 0:29 ` Pete Zaitcev
2004-12-20 0:31 ` Greg KH
2004-12-20 1:35 ` Adrian Bunk
2004-12-20 4:51 ` Pete Zaitcev
2004-12-20 5:09 ` Randy.Dunlap
2004-12-20 6:20 ` Matthew Dharm
2004-12-20 6:37 ` Pete Zaitcev
2004-12-20 7:28 ` [linux-usb-devel] " Phil Dibowitz
2004-12-20 8:09 ` Matthew Dharm
2004-12-20 8:25 ` [linux-usb-devel] " Phil Dibowitz
2004-12-20 8:44 ` Pete Zaitcev
2004-12-20 8:59 ` [linux-usb-devel] " Phil Dibowitz
2004-12-20 12:02 ` Ed Tomlinson
2004-12-20 15:28 ` [linux-usb-devel] " Alan Stern
2004-12-20 15:35 ` Greg KH
2004-12-20 20:46 ` Lee Revell
2004-12-22 8:10 ` Rob Browning [this message]
2004-12-23 1:45 ` Theodore Ts'o
2004-12-20 6:43 ` David Brownell
2004-12-20 7:06 ` Pete Zaitcev
2004-12-20 16:03 ` [linux-usb-devel] " David Brownell
2004-12-20 6:30 ` Pete Zaitcev
2004-12-20 15:25 ` [linux-usb-devel] " Alan Stern
2004-12-23 2:40 ` RFC: [2.6 patch] let BLK_DEV_UB depend on USB_STORAGE=n Adrian Bunk
2005-01-19 22:07 ` Greg KH
2005-01-20 2:49 ` Matthew Dharm
2005-01-21 0:04 ` Greg KH
2005-01-24 11:48 ` David Woodhouse
2005-01-24 17:49 ` Pete Zaitcev
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=87u0qepxd3.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=rddunlap@osdl.org \
--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