Hi,
Pradeep Das writes:
> Hi,
>
> Posting this query again as I received some mail delivery failure
> notification on the previous attempt.
>
> I am running usbtest test cases and facing following issues:
>
> Setup:
> I am using two custom board running on Linux. One is configured as
> host a
Hi,
I got a report saying that when overcurrent happens in one of the hub
downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus,
instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the
overcurrent condition is not handled in hub_event().
The following patch solves the is
On Fri, Jul 13, 2018 at 02:22:32PM -0500, Bin Liu wrote:
> Hi,
>
> I got a report saying that when overcurrent happens in one of the hub
> downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus,
> instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the
> overcurrent condit
On Fri, 13 Jul 2018, Bin Liu wrote:
> Hi,
>
> I got a report saying that when overcurrent happens in one of the hub
> downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus,
> instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the
> overcurrent condition is not handled i
I'm reproducing the steps of Alan Ott from his ELC 2014 talk:
https://elinux.org/images/6/66/Elc_2014_usb.pdf
Alan reports up to 211 Mbit/sec when using 64kB transfers while I can
get only around 120 Mbit/sec when using 64kB transfers. My first
question is:
- is the beaglebone black expected to
