From: Bjørn Mork <bj...@mork.no> Date: Tue, 03 Oct 2017 16:01:15 +0200
> We can pretty much ignore the USB-IF and any specs, since that is what > the vendors appear to do. They provide device specific drivers for > Windows, so all they care about is that their device "works" with their > driver. > > But in Linux we prefer to create drivers for device classes whenever we > can, to avoid having to add every single device by ID. So we try to > guess future patterns based on the devices we have observed, even when > there is no clear spec. This is what Aleksander does here. He has a > device with a 'Cls=ef(misc ) Sub=04 Prot=01' function. This device > works with the rndis_host driver. That is all we know. > > We cannot prove that a class match is correct. But it does make sense to > try it. At least we know that this works for one device. > > Adding anything else, e.g. based on the table at > http://www.usb.org/developers/defined_class/#BaseClassEFh , is a bit > more risky. We don't know if a driver will work with *any* such device > until we've actually seen one. > > This is just my opinion, and probably full of bogus assumptions as > usual. I was sort of hoping that some expert would speak up so I didn't > have to :-) Ok ;-) > But FWIW: > > Reviewed-by: Bjørn Mork <bj...@mork.no> So I'll apply this for now, thanks for your feedback. -- 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
