On Mon, Dec 12, 2011 at 11:30:24PM +0100, Dennis Hilmar wrote: > Hi guys > > I just created my first USB driver using the usb-skeleton.c file! > > The unfortunate thing is that the device is recognized as a CDC_ACM devices > and this driver can't function right with the protocol running on the > device :'( > Linux is Not wrong in this assumption but the protocol running on the > device is unfortunately really difficult to change so instead we've made > customized drivers for this purpose. > My only workaround right now is to rmmod the cdc_acm module, which makes my > driver come first, but this is just not a very stylish solution. > > When I look inside the cdc-acm.c the vid and pid are not there. > I would really like the cdc_acm module to live side-by-side with my module > > My question: *"Is it possible to add a USB module to the kernel that will > be prioritized to catch this device before the cdc_acm driver?"* Add your vendor/device ids to the blacklist in the cdc-acm driver and you should be fine. But I'd ask the larger question, why is your device saying it can follow the CDC ACM protocol spec, yet it really can not? Isn't that a violation of the USB spec itself? > Another question: *"Might it be because there is a priority in where the > .ko file is located?" Nope, if the driver is a module, all bets are off as to which one "wins". If the drivers are built into the kernel, then it depends on the link order. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
