Matthijs Kooijman writes:
>
> > > It seems like you managed to resolve the issue. If so, then could you
please
> > > explain how you managed to do it.
> > It's probably not directly helpful to you since the driver is really
> > different, but I patched up the dwc_otg driver to detect this "locku
> > It seems like you managed to resolve the issue. If so, then could you please
> > explain how you managed to do it.
> It's probably not directly helpful to you since the driver is really
> different, but I patched up the dwc_otg driver to detect this "lockup"
> situation and halt a transfer that
Hi Arshad,
> The driver used by the USB controller is MUSB_HDRC.
Looking at musb_core.c, I've found the following comment:
* * Control and bulk use dedicated endpoints, and there's as
*yet no mechanism to either (a) reclaim the hardware when
*peripherals are NAKing, which
Hi Matthijs,
> What driver does the USB controller in your TI board use?
The driver used by the USB controller is MUSB_HDRC.
> This problem sounds familiar to a problem I have observed in an Ralink
> RT3052 board, which uses the dwc_otg / dwc2 driver. Here, the problem
> was that the host cont
Hi Arshad,
> Did you manage to find a fix for the problem. Could you please share it.
What driver does the USB controller in your TI board use?
This problem sounds familiar to a problem I have observed in an Ralink
RT3052 board, which uses the dwc_otg / dwc2 driver. Here, the problem
was that the
Hi Jan, all,
Did you manage to find a fix for the problem. Could you please share it.
Thanks in Advance
Arshad
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-i
Dear Oliver, all,
do you please have any comments to the described issue? I'm still trying
to find the source of the problem, but I'm stuck.
Here are the tests I have done:
- gsm module on 2514b HUB connected to the DM365: cannot open two ttyACMs
- gsm module connected directly to the DM365: c
Hi Oliver,
thank you for answer.
A trace with usbmon as described in Documentation/usb should show what IO
goes wrong.
Trace is attached bellow. It was created with following sequence
1. attach USB modem (driver is loaded, ttyACMs created by udev)
2. cat /dev/ttyACM0 & (works fine)
3 cat /d
On Friday 23 November 2012 14:40:37 Jan Pohanka wrote:
> I have tried to reproduce this behavior directly on my PC, but there it
> works like a charm - at first I thought that the problem lies in cdc_acm
> driver, but today I tried to desolder the hub and connect the USB modem
> directly to t
