On Monday 10 September 2012 08:37:55 Florian Wöhrl wrote:
> Am 10.09.2012 04:55, schrieb Oliver Neukum:
> > On Monday 10 September 2012 10:51:32 Bjørn Mork wrote:
> >> Oliver Neukum <oneu...@suse.de> writes:
> >>
> >>> On Monday 10 September 2012 10:11:15 Bjørn Mork wrote:
> >>>>> And I do not think ftdi_sio should be loaded for this device
> >>>>> since it is really not an FTDI device after all. 04d8:000a is
> >>>>> a CDC-ACM demo device from Microchip's USB Firmware
> >>>>> Framework.
> >>>> Yes, that is cleary an error which should be fixed. Microchip owns the
> >>>> vid and has AFAIK reserved that pid for single function CDC ACM devices.
> >>> If this thing at least uses the vendor specific class, we should be able
> >>> to
> >>> deal with both. Remember that we don't want to punish users for a vendor's
> >>> stupidity.
> >> Sure. But we don't know that, do we? I have not seen any descriptor
> >> dump/extract from the offending device. Just the undocumented "add more
> >> identifiers". We can of course change it to a vendor class match,
> >> hoping that will work. Should I do that instead of deleting the entry?
> > Yes.
> Hi Oliver,
>
> it seems like cdc_acm was altered, too - am I right? modinfo doesn't
> mention 04d8:000A. It just tells 04d8:000B. Did you make that patch?
DOesn't the device show the proper classes in the interface descriptors?
Why do you want a specific match?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
