usbhid driver gets loaded instead of the useful driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have a device (a microscope automation controller) which has a USB
port which uses a standard RS232 to USB converter, by Cypress. They
just changed their vendor id and product id from the standard cypress
ID. I added their IDs to the cypress_m8 source, compiled, and put the
updated cypress_m8.ko file in /lib/modules/.

When I plug the device the cypress_m8 driver isn't being used.
Instead, the generic usbhid driver is used, which isn't what I wanted.
If I run:

modprobe -r usbhid cypress_m8
modprobe cypress_m8
modprobe usbhid

then when I plug the device, the cypress_m8 driver is being used, and
I can use /dev/ttyUSB0, just as I wanted.

It seems that the order in which drivers are loaded affects the
priority: the driver which was loaded first gets to catch the device.
So my question is, is there a way to permanently change the driver
priority, so that the right driver will be loaded by default?

Thank you very much,
Noam
--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux