From: Bill Davidsen <davidsen@tmr.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Wolfgang Scheicher <worf@sbox.tu-graz.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 USB storage problems
Date: Wed, 03 Nov 2004 17:02:43 -0500 [thread overview]
Message-ID: <41895583.10604@tmr.com> (raw)
In-Reply-To: <20041101164615.13a04a7c@lembas.zaitcev.lan>
Pete Zaitcev wrote:
> On Mon, 1 Nov 2004 23:19:13 +0100, Wolfgang Scheicher <worf@sbox.tu-graz.ac.at> wrote:
>
>
>>>>And: could maybe somebody put some hints into the ub help?
>>>>"This driver supports certain USB attached storage devices such as flash
>>>>keys." didn't sound so bad to me...
>>>
>>>That should definately happen. Along with a note that this blocks
>>>usb-storage from working with many devices if enabled.
>>
>>Yep. Absolutely.
>
>
> I don't like too much wordage. How about this:
>
> diff -urp -X dontdiff linux-2.6.10-rc1/drivers/block/Kconfig linux-2.6.10-rc1-ub/drivers/block/Kconfig
> --- linux-2.6.10-rc1/drivers/block/Kconfig 2004-10-28 09:46:38.000000000 -0700
> +++ linux-2.6.10-rc1-ub/drivers/block/Kconfig 2004-11-01 16:09:13.727453544 -0800
> @@ -308,6 +308,8 @@ config BLK_DEV_UB
> This driver supports certain USB attached storage devices
> such as flash keys.
>
> + Warning: Enabling this cripples the usb-storage driver.
> +
> If unsure, say N.
>
> config BLK_DEV_RAM
I just got information on this in another thread, in case you didn't see
my note there, is this behaviour a bug, design choice, or unavoidable
hardware issue? I can turn it off now, but I'm supposed to be getting a
flash key thing to test, which is why I turned it on in the first place.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-11-03 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 12:24 2.6.9-rc4 USB storage problems Wolfgang Scheicher
2004-10-12 17:51 ` bert hubert
2004-11-01 17:50 ` 2.6.9 " Wolfgang Scheicher
2004-11-01 19:10 ` Matthew Dharm
2004-11-01 19:40 ` Wolfgang Scheicher
2004-11-01 21:35 ` Matthew Dharm
2004-11-01 22:19 ` Wolfgang Scheicher
2004-11-01 23:33 ` Pete Zaitcev
2004-11-02 0:46 ` Pete Zaitcev
2004-11-03 22:02 ` Bill Davidsen [this message]
2004-11-04 9:19 ` Pete Zaitcev
2004-11-04 19:04 ` Bill Davidsen
2004-11-04 20:14 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 2:50 Chuck Ebbert
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=41895583.10604@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=worf@sbox.tu-graz.ac.at \
--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