Vojtech Pavlik wrote:
> > Do these devices not have suitable comm. class interface descriptors?
>
> They do. In some of their configurations. Default is of course
> vendor-specific interfaces.
OK, I see why my logic failed - the multiple configurations problem. My acm
modem only has one config:
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=06ea ProdID=0002 Rev= 1.00
S: Manufacturer=Sirius Technologies
S: Product=Roadster II 56 USB
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=400mA
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=acm
E: Ad=81(I) Atr=02(Bulk) MxPS= 16 Ivl= 0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 16 Ivl= 0ms
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=acm
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=128ms
I have reverted back to device descriptors, for both CDC drivers. See attached
patch (acm-desc.patch)
In some ways, I would like to continue to use interface descriptors (more
cleanly), and to use vendor / product IDs for those few devices that break
(like the Actiontec 56K USB) - see attached acm-ideas.patch.
This would avoid needless hotplug loading of modules and probing on
interfaces. However it would be more maintenance load. Any views on this?
Brad
acm-desc.patch
acm-ideas.patch
