>> 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.
>
So did Greg want the driver to handle only CDC-Ethernet variants?? Or did he
want the match_ids table to have CDC-Ethernet only? What I mean to say is
"Was this side effect known when the change was done ?" If yes, why has
this not been reflected in the CDC-ACM driver?
>> 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().
>
OK. Thanks for pointing out. I was just testing wheter something like this
will solve the problem. Ideally speaking though, this does not solve my
problem as my modem is supposed to work "out of the box" .. now i would have
to distribute this patch along the modem.
----------------------------------------------------
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=ick
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
-------------------------------------------------------
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_id=1356&alloc_id=3438&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
