From: David Liontooth <liontooth@cogweb.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: USB devices fail unnecessarily on unpowered hubs
Date: Fri, 02 Jun 2006 12:49:39 -0700 [thread overview]
Message-ID: <44809653.9010203@cogweb.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0606021109390.7076-100000@iolanthe.rowland.org>
Alan Stern wrote:
> Trying to draw too much current from an unpowered hub can and does cause
> data loss.
>
I consider this issue closed; thank you for looking at it. The
workaround is reasonably simple for the common situation of mounting a
USB stick on a keyboard, perhaps with a mouse attached in a second port:
NUM="$(dmesg | tail -n 3 | grep -r 'new full speed USB device' | cut -b
5-9)"
echo -n 1 >/sys/bus/usb/devices/$NUM/bConfigurationValue
with the understanding this breaks USB power rules and can lead to data
loss.
Dave
next prev parent reply other threads:[~2006-06-02 19:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:18 USB devices fail unnecessarily on unpowered hubs David Liontooth
2006-05-30 20:01 ` Pavel Machek
2006-06-03 9:29 ` Oliver Neukum
2006-06-05 14:32 ` [linux-usb-devel] " David Brownell
2006-06-06 7:43 ` Oliver Neukum
2006-06-08 7:01 ` Pavel Machek
2006-06-08 8:34 ` [PATCH] limit power budget on spitz Pavel Machek
2006-06-08 8:50 ` Richard Purdie
2006-06-08 9:02 ` Pavel Machek
2006-06-08 9:22 ` Richard Purdie
2006-06-08 17:09 ` Russell King
2006-06-08 18:26 ` David Brownell
2006-06-08 20:06 ` Richard Purdie
2006-06-08 20:38 ` [linux-usb-devel] " David Brownell
2006-06-08 21:22 ` Richard Purdie
2006-06-08 21:40 ` David Brownell
2006-06-08 21:49 ` Richard Purdie
2006-06-08 23:44 ` David Brownell
2006-06-09 1:25 ` Nicolas Pitre
2006-06-09 2:03 ` David Brownell
2006-06-09 2:34 ` Nicolas Pitre
2006-06-01 10:01 ` USB devices fail unnecessarily on unpowered hubs Andrew Morton
2006-06-01 11:42 ` Daniel Drake
2006-06-01 14:58 ` Alan Stern
2006-06-01 15:09 ` linux-os (Dick Johnson)
2006-06-01 15:23 ` Lennart Sorensen
2006-06-01 21:39 ` Dagfinn Ilmari Mannsåker
2006-06-01 15:53 ` Oliver Neukum
2006-06-01 17:24 ` linux-os (Dick Johnson)
2006-06-01 16:57 ` Alan Stern
2006-06-01 16:43 ` [linux-usb-devel] " Greg KH
2006-06-02 0:03 ` David Liontooth
2006-06-02 1:53 ` [linux-usb-devel] " David Brownell
2006-06-02 7:12 ` Oliver Neukum
2006-06-02 15:11 ` Alan Stern
2006-06-02 19:49 ` David Liontooth [this message]
2006-06-01 16:59 ` Andrew Morton
2006-06-01 17:08 ` Alan Stern
2006-06-01 17:34 ` Mark Lord
2006-06-01 17:47 ` Alan Stern
[not found] <6iWP5-2gj-71@gated-at.bofh.it>
[not found] ` <6iX82-2UJ-3@gated-at.bofh.it>
2006-06-01 23:35 ` Robert Hancock
2006-06-01 23:46 ` Randy.Dunlap
[not found] <6iYGP-5hv-3@gated-at.bofh.it>
[not found] ` <6iYQx-5Jc-7@gated-at.bofh.it>
2006-06-01 23:37 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 11:07 Lee Dowling
[not found] <6kl8h-1Uf-15@gated-at.bofh.it>
2006-06-07 0:51 ` Robert Hancock
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=44809653.9010203@cogweb.net \
--to=liontooth@cogweb.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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