On Sun, 5 Apr 2015, Steve Bangert wrote:
On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote:
Is that really all? Was there a UAS is blacklisted for this device
line in the kernel log? It looks like the usb-storage driver didn't do
anything at all with the device.
Yes that's
On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote:
Is that really all? Was there a UAS is blacklisted for this device
line in the kernel log? It looks like the usb-storage driver didn't do
anything at all with the device.
Yes that's it. Using xhci at super speed, blacklisting uas is
On Sun, Apr 05, 2015 at 06:33:44AM +0800, Chen Gang wrote:
On 4/4/15 17:54, Greg Kroah-Hartman wrote:
On Sat, Apr 04, 2015 at 05:51:21AM +0800, Chen Gang wrote:
Under blackfin, only bf527, bf548 and bf609 may use musb. The related
error with allmodconfig:
CC [M]
On 4/5/15 16:29, Greg Kroah-Hartman wrote:
On Sun, Apr 05, 2015 at 06:33:44AM +0800, Chen Gang wrote:
On 4/4/15 17:54, Greg Kroah-Hartman wrote:
On Sat, Apr 04, 2015 at 05:51:21AM +0800, Chen Gang wrote:
Under blackfin, only bf527, bf548 and bf609 may use musb. The related
error with
Hello,
I posted a bug to kernel.org and have been asked to send it to this
mailing list.
After the 3.13 Kernel series I experience that it can take an arbitrary
amount of time/retries to identify the USB devices in my system. The
issue became apparent when I could not start my new kernel
On Sun, 2015-04-05 at 10:31 -0400, Alan Stern wrote:
On Sun, 5 Apr 2015, Steve Bangert wrote:
On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote:
Is that really all? Was there a UAS is blacklisted for this device
line in the kernel log? It looks like the usb-storage driver
