On Sat, 14 Feb 2004 22:14 pm, Prashanth Acharya wrote:
> I have basically narrowed down the problem to this line of code
>
> version 0.98.6
> // We only try to claim CDC Ethernet model devices */
> static struct usb_device_id CDCEther_ids[] = {
> { USB_INTERFACE_INFO(USB_CLASS_COMM, 6, 0) },
> { }
> };
>
> version 0.98.4
> /* Take any CDC device, and sort it out in probe() */
> static struct usb_device_id CDCEther_ids[] = {
> { USB_DEVICE_INFO(USB_CLASS_COMM, 0, 0) },
> { } /* Terminating null entry */
> };
>
>
> Now my question is " Any particular reason as to why this change was made?"
> With this change the driver can now support a pure CDC-Ethernet device only
> i.e. if all the configurations are CDC-Ethernet variants only. Sadly for
> me, RNDIS is a CDC-ACM variant :(
>
> Am I right in this analysis or am I missing something?
This is what Greg K-H wanted.
> I found that if I add { USB_DEVICE_INFO(USB_CLASS_COMM, 0, 0) } as
> the second entry in the table for version 0.98.6 everything works fine!!
Don't do that. Just add a specific entry for your vendor and product (using
the USB_DEVICE() macro, instead of USB_DEVICE_INFO().
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
