On Tue, 2016-07-26 at 10:59 +, Sheng Li (李盛) wrote:
> it is about an usb error handling in function "hid_io_error":
>
> the comments shows
>
> /* Retries failed, so do a port reset unless we lack bandwidth*/
>
> but actually the code do the opposite
>
>
> Signed-off-by:Sheng Li
Hi,
it is about an usb error handling in function "hid_io_error":
the comments shows
/* Retries failed, so do a port reset unless we lack bandwidth*/
but actually the code do the opposite
Signed-off-by:Sheng Li
drivers/hid/usbhid/hid-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
The GIGABYTE GA-970A-DS3 motherboard is broken because
Gigabyte did not qualify the hardware that they used.
The Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
does not properly handle USB hubs.
By adding a PCI-E controller card:
Renesas Technology Corp. uPD720201 USB 3.0 Host Co
On Fri, Jul 22, 2016 at 2:16 PM, Alan Stern wrote:
>> I'd suggest a comment referencing the spec then :)
>
> Don't be silly. Nobody could possibly understand the code without
> reading the spec first. There's no need to mention the spec in a
> comment; it's an obvious prerequisite.
I've managed
On Fri, 22 Jul 2016, Bruce Korb wrote:
> HI,
>
> On Fri, Jul 22, 2016 at 12:57 PM, Alan Stern
> wrote:
> > They come from the xHCI hardware.
>
> I'd suggest a comment referencing the spec then :)
Don't be silly. Nobody could possibly understand the code without
reading the spec first. Ther
HI,
On Fri, Jul 22, 2016 at 12:57 PM, Alan Stern wrote:
> They come from the xHCI hardware.
I'd suggest a comment referencing the spec then :)
> /* Completion Code - only applicable for some types of TRBs */
> #define COMP_CODE_MASK (0xff << 24)
> #define GET_COMP_CODE(p) (((p) & COMP_CODE_MASK
On Fri, 22 Jul 2016, Bruce Korb wrote:
> A few questions:
>
> 1. Where do the values for TRB completion codes come from?
> COMP_BW_ERR and COMP_2ND_BW_ERR seem to be defined
> and then only used in a switch statement.
They come from the xHCI hardware.
> 2. xhci_queue_configure_endpoint
A few questions:
1. Where do the values for TRB completion codes come from?
COMP_BW_ERR and COMP_2ND_BW_ERR seem to be defined
and then only used in a switch statement.
2. xhci_queue_configure_endpoint() seems to be the function for
sending down a command that somehow loads the "BW_E
On Thu, 21 Jul 2016, Bruce Korb wrote:
> It seems the problem is related to 64 bit Linux on Gigabyte motherboards.
> 32 bit? No problem. Windows? No problem. Another mobo? No problem.
> So much for buying the preferred Linux mobo.
> I've added the GRUB_CMDLINE_LINUX= change to /etc/default/grub
It seems the problem is related to 64 bit Linux on Gigabyte motherboards.
32 bit? No problem. Windows? No problem. Another mobo? No problem.
So much for buying the preferred Linux mobo.
I've added the GRUB_CMDLINE_LINUX= change to /etc/default/grub and
updated with "update-bootloader". I hope t
On Wed, 20 Jul 2016, Bruce Korb wrote:
> Hi Alan,
>
> I swapped the driver, so usb_device_supports_lpm() always returns "0".
> No change. Bandwidth for a Class 10 SSD, but not for a mouse or
FYI, a Class 10 SSD does not have any bandwidth requirement. If very
little bandwidth is available, th
Hi Alan,
I swapped the driver, so usb_device_supports_lpm() always returns "0".
No change. Bandwidth for a Class 10 SSD, but not for a mouse or
keyboard. There is a new message that I've not seen before,
hub_port_status failed (err = -71) === EPROTO
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Clas
Hi Alan,
On Mon, Jul 18, 2016 at 6:09 PM, Alan Stern wrote:
>> Given the repeatability, maybe I can dig into where stuff is going awry.
>> Maybe I can trace down how the bogus speed information is derived.
>
> If my guess was correct, there is no bogus speed information.
OK.
>> I do not believe
On Mon, 18 Jul 2016, Bruce Korb wrote:
> On Mon, Jul 18, 2016 at 2:24 PM, Alan Stern wrote:
> > This is not surprising, because the problem probably stems from the
> > xHCI host controller in your computer, not from the hub.
>
> Gigabyte is supposed to make reliable motherboards.
> Haven't been
On Mon, Jul 18, 2016 at 2:24 PM, Alan Stern wrote:
> This is not surprising, because the problem probably stems from the
> xHCI host controller in your computer, not from the hub.
Gigabyte is supposed to make reliable motherboards.
Haven't been trying to use USB3 until now, but still
Given t
On Mon, 18 Jul 2016, Bruce Korb wrote:
> On Sun, Jul 17, 2016 at 12:43 PM, Alan Stern
> wrote:
> > A USB-3.1 device should work okay with a USB-3 driver. However, it
> > would help if you upgrade to the latest available kernel version.
>
> It is the latest available openSUSE release.
The rele
On Sun, Jul 17, 2016 at 12:43 PM, Alan Stern wrote:
> A USB-3.1 device should work okay with a USB-3 driver. However, it
> would help if you upgrade to the latest available kernel version.
It is the latest available openSUSE release.
I've downloaded the latest Slackware release. I'll try it la
On Sun, 17 Jul 2016, Bruce Korb wrote:
> On Sun, Jul 17, 2016 at 6:57 AM, Alan Stern wrote:
> >
> > What kernel version are you using?
>
> openSUSE's latest: 4.1.27
> Someone told me that the "05e3:0610 Genesys Logic, Inc" device is a
> USB 3.1 and the driver capable of handling it was released
On Sun, Jul 17, 2016 at 6:57 AM, Alan Stern wrote:
>
> What kernel version are you using?
openSUSE's latest: 4.1.27
Someone told me that the "05e3:0610 Genesys Logic, Inc" device is a
USB 3.1 and the driver capable of handling it was released _several_
days ago now. Perhaps I'm just not up-to-d
On Sat, 16 Jul 2016, Bruce Korb wrote:
> On Sat, Jul 16, 2016 at 4:18 PM, Greg KH wrote:
> >> [13043.528023] usb 1-1.3: Product: Gaming Mouse G400
> >> [13043.528027] usb 1-1.3: Manufacturer: Logitech
> >> [13043.528309] usb 1-1.3: Not enough bandwidth for new device state.
> >> [13043.528319] us
On Sat, Jul 16, 2016 at 4:33 PM, Greg KH wrote:
> That's not how USB protocols work, they are driven from the host, not
> the device, your computer is asking that keyboard if it constantly has
> new data, it's not driven by how fast or slow you type.
Not a USB person, I didn't know. I prefer "I
On Sat, Jul 16, 2016 at 04:27:05PM -0700, Bruce Korb wrote:
> On Sat, Jul 16, 2016 at 4:18 PM, Greg KH wrote:
> >> [13043.528023] usb 1-1.3: Product: Gaming Mouse G400
> >> [13043.528027] usb 1-1.3: Manufacturer: Logitech
> >> [13043.528309] usb 1-1.3: Not enough bandwidth for new device state.
>
On Sat, Jul 16, 2016 at 4:18 PM, Greg KH wrote:
>> [13043.528023] usb 1-1.3: Product: Gaming Mouse G400
>> [13043.528027] usb 1-1.3: Manufacturer: Logitech
>> [13043.528309] usb 1-1.3: Not enough bandwidth for new device state.
>> [13043.528319] usb 1-1.3: can't set config #1, error -28
>
> That's
On Sat, Jul 16, 2016 at 12:40:43PM -0700, Bruce Korb wrote:
> [13026.604365] usb 1-1.3: USB disconnect, device number 28
> [13043.430087] usb 1-1.3: new full-speed USB device number 32 using xhci_hcd
> [13043.528010] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c245
> [13043.528018] us
I just found your address as a better one than linux-kernel:
***
My typing follows a line with a bunch of stars. That is followed by
command output.
***
I have a USB 3.0 hub and switch that I need to use to switch devices
between a Linux desktop, laptop and MacBook Pro. At first, I was
On Sun, 16 Mar 2014, Peter Fassberg wrote:
> On Sat, 15 Mar 2014, Alan Stern wrote:
>
> > You may be able to get it to work by doing
> >
> > echo 0x 0x0002 >/sys/bus/usb/drivers/usbhid/new_id
>
> As I wroter earlier it did solve the problem.
>
> However, the Report Descriptors is "unava
On Sat, 15 Mar 2014, Alan Stern wrote:
You may be able to get it to work by doing
echo 0x 0x0002 >/sys/bus/usb/drivers/usbhid/new_id
As I wroter earlier it did solve the problem.
However, the Report Descriptors is "unavailable" now.
lsusb output:
Report Descriptors:
On Sat, 15 Mar 2014, Alan Stern wrote:
On Fri, 14 Mar 2014, Peter Fassberg wrote:
Hi!
I'm using quite a few USB HID devices, but one of them fail.
I have really no idea about what is going on here, and it's an odd
card (my geothermal heat pump).
Maybe you have an idea about why it doesn't g
On Fri, 14 Mar 2014, Peter Fassberg wrote:
> Hi!
>
> I'm using quite a few USB HID devices, but one of them fail.
>
> I have really no idea about what is going on here, and it's an odd
> card (my geothermal heat pump).
>
> Maybe you have an idea about why it doesn't get recognized by the HID dr
Hi!
I'm using quite a few USB HID devices, but one of them fail.
I have really no idea about what is going on here, and it's an odd card (my
geothermal heat pump).
Maybe you have an idea about why it doesn't get recognized by the HID driver?
VID/PID: 0x / 0x0002 :(
Kernel: 3.3.8
Kernel
30 matches
Mail list logo
