Brad Hards <[EMAIL PROTECTED]> writes: > Also found in your later post. > The reason why this is needed is that the device is advertising a non-zero > Device sub-class code. > That is, the line that says: > D: Ver= 1.10 Cls=02(comm.) Sub=02 Prot=00 MxPS= 8 #Cfgs= 1 > should read > D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > Which means that your device is wrong, if I'm reading the CDC spec correctly. > > There is no way you can fix this without contacting the manufacturer, > convincing them that they have stuffed up, and getting a firmware upgrade for > the phone... > > I think that the extra entry above is probably the best solution (although not > the only solution). You might like to add a comment saying what the > vendor/product ID is, and why you had to add it, before sending this patch to > [EMAIL PROTECTED] (who is the maintainer of the acm code).
I will contact the manufacturer, however the drivers supplied with MS Windows work. I'm almost sure they won't even listen to my input. Thanks for the suggestions and insight on getting the patch together. I will follow them. - Nick _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
