From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Aaron Dewes <aaron.dewes@web.de>, linux-usb@vger.kernel.org
Subject: Re: A question about UAS
Date: Sat, 6 Mar 2021 12:20:13 -0500 [thread overview]
Message-ID: <20210306172013.GE74411@rowland.harvard.edu> (raw)
In-Reply-To: <YEO1t63SQw1Ui4ce@kroah.com>
On Sat, Mar 06, 2021 at 06:02:47PM +0100, Greg KH wrote:
> On Sat, Mar 06, 2021 at 05:34:32PM +0100, Aaron Dewes wrote:
> > Hello!
> >
> > Sorry if this suggestion/question sounds stupid, I don't have experience
> > with the kernel code and this mailing list.
> >
> > I'm a contributor to Umbrel (getumbrel.com), and we provide a software
> > that allows to run a bitcoin node easily, and we've run into many people
> > having UAS issues
>
> What specific UAS issues? And why not just fix those instead?
Indeed. It's always better to fix a problem than to cover it up.
> > , and we were manually adding quirks in this case. Now
> > I'm wondering if it is possible to disable UAS for all devices in the
> > kernel cmdline.
>
> Sure, just blacklist the uas kernel module, that prevents it from being
> loaded and hopefully the device will degrade to the
> old-school-and-dirt-slow usb-storage protocol.
In fact it won't. The usb-storage driver will see that the device can
be managed by the uas driver, so it won't bind. Then nothing will
manage the device.
You actually have to turn off CONFIG_USB_UAS when the kernel is built.
Alan Stern
next prev parent reply other threads:[~2021-03-06 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 16:34 A question about UAS Aaron Dewes
2021-03-06 17:02 ` Greg KH
2021-03-06 17:20 ` Alan Stern [this message]
2021-03-06 17:27 ` Aaron Dewes
2021-03-06 18:25 ` Alan Stern
[not found] ` <1e60a591-7b7e-ca80-41cf-16fa440d7248@web.de>
2021-03-06 18:39 ` Aaron Dewes
2021-03-06 18:54 ` Greg KH
2021-03-08 13:39 ` Oliver Neukum
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=20210306172013.GE74411@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=aaron.dewes@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
/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