On Tue, Dec 04, 2001 at 11:41:59AM -0800, Greg KH wrote:
> Yes, it sounds like this is the problem. Have you contacted the author
> of the mct_u232 to try to come up with a patch that works for both types
> of devices?
I was a bit confused about who was looking after this one, so thought
I'd post here and see if anyone replied :-)
Am I right in thinking that usb_serial_probe() in usbserial.c is the
function that needs to be frobbed in order to influence the default
endpoint detection ? I was thinking about a quick kludge based on
subverting this assignment...
interrupt_in_endpoint[num_interrupt_in] = endpoint;
... so that whereas currently (for the Belkin)
interrupt_in_endpoint[0] is the control/exceptions endpoint, and
interrupt_in_endpoint[1] is the regular data transfer one
We swap the two around, i.e.
interrupt_in_endpoint[0] is the regular data transfer endpoint, and
interrupt_in_endpoint[1] is the control/exceptions one
Would this be enough to fool the kernel into using the right ones?
If a hard coded kludge like this works, we can have a think about how
best to incorporate this into the proper driver!
Presumably you'd prefer to keep the driver specific stuff out of
usbserial.c and usb-serial.h as much as possible ?
Cheers,
Martin
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
