Re: [Ftdi-usb-sio-devel] Non-standard Product ID (PID)

[Bill R. <br...@pa...>]

Hi

John Wilkins wrote:

>However, the ftdi-based convertor exhibits a different Product ID (PID)
>to the ones suggested in the .h file (it reports 0xfe38 instead of
>0x6001).  So when the device is plugged in, or the module insmod'ed the
>device is not recognised by the driver.
>
>I've got around this by adding the PID to the .h file and added a new
>entry to the usb_device_id tables at the top of the .c file.  This works
>well and now the device is recognised by the driver.  However, I want
>to get away from having to patch the ftdi driver if possible - 
>especially as the rest of the operation uses the 8U232AM code exactly
>(that's what the convertor is based on).
>

As I understand the problem this is because the vid and pid are 
statically initialised when the module is compiled and statically added 
to the list of devices. This *seems* to preclude the possibility of 
doing it at run time (which is what you are doing if you pass the pid 
and vid to a module as arguments).

>My question is, should I ask for the PID/VID codes for this device to
>be added to the maintained sources or is there a way to "alias" the 
>VID/PID so that my device's codes get "translated" to the standard ones
>defined in the .h?
>

So the normal way is to get the vid/pid's added to the driver. Quite 
annoying really!

>
>Hope that makes sense!
>

It does and has been an annoyance for a while.

I still haven't figured out a way to do this nicely.

---
Bill