Re: [Ftdi-usb-sio-devel] Problem passing custom VID/PID to ftdi-sio

[Roger O. J. <ro...@pp...>]

On 20/05/2015 16:22, Roger O. Jones MIET wrote:
> We've used a custom `udev` rule on the Pi to pass the correct VID
> and  PID to the driver (as per the instructions in the "FTDI
> Technical Note  101" and the ftdi-sio webpage) and this worked
> previously on the Raspberry Pi Model B (raspbian with kernel
> 3.10.25+) but today I've  tried it on a Raspberry Pi A+ (raspbian with
> kernel 3.18.11+) but get  errors in `dmesg` from the `udev` rule and the
> device is not recognized.
> --8<----
> # dmesg | grep ftdi
> ftdi_sio: unknown parameter 'product' ignored
> ftdi_sio: unknown parameter 'vendor' ignored
> usbcore: registered new interface driver ftdi_sio
> ---->8--

OK, found that this is down to a change in the kernel 3.12 and later
that impacts on the way that custom VID and PID are sent to the driver.
We now need to load the driver and then add the new numbers to the
`/sys/bus/usb-serial/drivers/ftdi_sio/new_id` virtual file.

I've amended my `udev` rule and it seesm to work.

Here the link I found explaining the change, for anyone else that's
searching the list for the same problem:
http://techtuxwords.blogspot.co.uk/2014/12/using-ftdisio-with-linux-kernel-312-and.html

Hwyl,
Roger