Bug#918800: PROBLEM: USB 3.0 NIC operates only at USB 2.0 speed on Odroid HC1

2019-04-27 Thread Steinar H. Gunderson
merge 925167 918800 thanks On Sat, Apr 27, 2019 at 03:12:35PM +0200, Steinar H. Gunderson wrote: > Now I have; I rebuilt the Debian kernel with > > USB=y > USB_XHCI_HCD=y > CONFIG_USB_XHCI_PLATFORM=y > > and the NIC still comes up at 480M. So, no go. Correction: After a hard reset, it wor

Processed: Re: Bug#918800: PROBLEM: USB 3.0 NIC operates only at USB 2.0 speed on Odroid HC1

2019-04-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 925167 918800 Bug #925167 [src:linux] add a modules softdep to dwc3 to fix it on odroid Bug #925167 [src:linux] add a modules softdep to dwc3 to fix it on odroid Marked as found in versions linux/4.19.12-1. Added tag(s) upstream. Bug #918800

Bug#918800: PROBLEM: USB 3.0 NIC operates only at USB 2.0 speed on Odroid HC1

2019-04-27 Thread Steinar H. Gunderson
On Wed, Apr 24, 2019 at 01:25:54PM +0200, Steinar H. Gunderson wrote: > I have the same problem with the ODROID XU4, which also includes a dwc3 and > an 8152 (it's probably dwc3-specific; the driver has been problematic > before). I haven't checked whether CONFIG_USB_XHCI_PLATFORM=y helps, though.

Bug#918800: PROBLEM: USB 3.0 NIC operates only at USB 2.0 speed on Odroid HC1

2019-04-24 Thread Steinar H. Gunderson
On Sat, Feb 02, 2019 at 01:39:06PM +0100, Benjamin Drung wrote: > The Odroid HC1 ARM board contains a JMicron JMS578 USB 3.0 to SATA > Bridge and a Realtek Gbps Ethernet device connected to an USB 3.0 host. > The SATA bridge works correctly at USB 3.0 speed, but the Ethernet > controller operates o

Bug#918800: PROBLEM: USB 3.0 NIC operates only at USB 2.0 speed on Odroid HC1

2019-02-02 Thread Benjamin Drung
Hi, The Odroid HC1 ARM board contains a JMicron JMS578 USB 3.0 to SATA Bridge and a Realtek Gbps Ethernet device connected to an USB 3.0 host. The SATA bridge works correctly at USB 3.0 speed, but the Ethernet controller operates only at USB 2.0 speed. I tracked this behaviour down to the CONFIG_U