Hi Paul,
I noticed that this bug occurs with the old dwc_otg driver (from the
Ralink SDK) as well, so it is not dwc2-specific.
However, I also ound out this bug does not occur on another (identical)
unit I have (using the old driver), so it seems likely that this is
somehow a one-off (hardware)
Hi Paul,
There's no firmware in the HSOTG core, so I don't see how running the
driver could permanently damage the core. However, if it's your only
good working unit then I guess some paranoia is understandable ;)
Well, it was just that I had only one unit where running a clean 3.10
kernel was
From: Matthijs Kooijman [mailto:matth...@stdin.nl]
I noticed that this bug occurs with the old dwc_otg driver (from the
Ralink SDK) as well, so it is not dwc2-specific.
However, I also ound out this bug does not occur on another (identical)
unit I have (using the old driver), so it seems
Hi Paul,
I did see a different issue when booting/rebooting the system.
I discovered that the DMA_BIT_MASK(31)'s in dwc2_hcd_init() were
randomly preventing the controller from working after boot. When
I changed both of them to DMA_BIT_MASK(32) the problem went away.
I am going to submit a
From: Paul Zimmerman
Sent: Monday, May 13, 2013 11:58 AM
From: Matthijs Kooijman [mailto:matth...@stdin.nl]
Sent: Wednesday, May 08, 2013 2:02 PM
I'm running into an issue with the dwc2 driver. When I power on my board
with an usb device (mass storage in this case) connected, the
From: Matthijs Kooijman [mailto:matth...@stdin.nl]
Sent: Wednesday, May 08, 2013 2:02 PM
I'm running into an issue with the dwc2 driver. When I power on my board
with an usb device (mass storage in this case) connected, the hardware
is returning transaction errors (e.g., triggering channel
