I'm attempting to get an FTDI USB-Serial device with a custom PID to automatically (or even manually) attach to ttyUSB%n, without much success.  The device's normal VID/PID is 0403/6001.  When programmed this way, it works perfectly and automatically attaches itself to ttyUSB0 when plugged in.  Even with the driver recompiled to respect our new PID, when programmed with the custom one ttyUSB0 does not appear, but it does recognize it as an ftdi_sio device and loads the driver.I have added our PID to the header and source:// in ftdi_sio_ids.h#define FTDI_CUSTOM_PID 0xABCD // not the actual pid// then in ftdi_sio.cstatic struct usb_device_id id_table_combined [] = {    // devices....    { USB_DEVICE(FTDI_VID, FTDI_CUSTOM_PID) },    // ....Recompiled the entire kernel and reflashed the device.  When I plug the device in I get:usb 1-1: new full-speed USB device number 2 using at91_ohciusbcore: registered new interface driver usbserialusbserial: USB Serial Driver coreUSB Serial support registered for FTDI USB Serial Deviceusbcore: registered new interface driver ftdi_sioftdi_sio: v1.6.0:USB FTDI Serial Converters Driverlsusb shows the correct custom VID/PID.  The driver seems to recognize that it's supposed to use ftdi_sio with it, but doesn't attach it to ttyUSB0 like it would with the unmodified PID.  Any suggestions as to what I'm doing wrong here?
Attaching USB-Serial device with custom PID to ttyUSB0 on embedded
drivers;usb;embedded;serial port