http://linuxexchange.org/questions/1378/forcing-a-specific-driver-for-a-device-through-udev-solved<p>My co-workers and I are trying to develop a USB device, which uses an FTDI chip as a USB-serial controller. The thing is, we would ideally like to set a cusom idVendor and idProduct on the FTDI chip. </p> <p>The problem occurs that when we set custom idVendor and idProduct values, udev(7) loads the "usb" driver. If we leave the idVendor and idProduct values to their originals, udev(7) loads the "ftdi_sio" driver. The whole reason for the custom idVendor and idProduct values is so that I can (hopefully) write a udev(7) rule to map that particular device to a specific entry in /dev.</p> <p>Is there a way to write a udev(7) rule so that you can forcefully load a particular driver for a device? Is there something else that could be done to get a similar result?</p> <p><em>EDIT: I have been searching on Google for this, for upwards of 5 hours now, so yes, I have searched if anyone cares to know. ;)</em></p>enFri, 08 Oct 2010 21:53:33 -0400http://linuxexchange.org/questions/1378/forcing-a-specific-driver-for-a-device-through-udev-solved/1380<p>I found a solution for this. Since I am not too keen on having to copy and re-work the <code>ftdi_sio</code> driver, I had to change the idVendor and idProduct values back to the FTDI defaults and catch the device with a udev rule that assigns it a specific symlink in <code>/dev</code>.</p>indienickFri, 08 Oct 2010 21:53:33 -0400http://linuxexchange.org/questions/1378/forcing-a-specific-driver-for-a-device-through-udev-solved/1380