Re: CDC_ACM, TU4310 and odd behaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Oct 23, 2010 at 06:15:36PM +0200, Paul-Kenji Cahier Furuya wrote:
> On 10/23/2010 17:57, Greg KH wrote:
>> This sounds like the device is broken, especially due to this:
> That is my guess too.
>
>> How does other operating systems handle this device?  Do they use the
>> HID interface, or the cdc-acm interface?
> Well, under linux itself, all debugging&programming kits use the hid 
> interface, but the serial interface is still used for testing/actual 
> production/applications. Same under windows.
> Please note that the windows driver does seem to also have that issue at 
> times, so it's most definitely likely to be a problem of that device.
> (I did find other references to it)
>
> I am guessing worst case I could try creating a permanent read-drain proxy 
> of some sort. Any more debugging I might be able to provide? Or solutions?

If you always leave a program reading from the device, does it work
fine?  Perhaps you could do that from userspace, or worse case, hack the
cdc-acm driver to always drain the endpoint as well.

Have you contacted TI about this?

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux