On Sun, Mar 04, 2007 at 05:00:57PM +0100, Gard Spreemann wrote: > On Sunday 04 March 2007 00:37, Greg KH wrote: > > Sure, we can add that device id to the driver itself. How about making > > a patch against the latest kernel tree and sending it to me in the > > format described in Documentation/SubmittingPatches? That way you will > > get the proper credit for the change. > > > > thanks, > > > > greg k-h > > The thing is, I just changed the FTDI_SIO_PID to my PID (0xFBFA). I reckon > this is not a permanent way to have it, so a new PID has to be defined. I > tried doing this in order to send you a patch against the latest kernel tree, > but I ran into problems weaving the new PID into the other code, such as the > device specific settings etc. I guess I was just lucky that the settings for > the SIO device worked for the 232RL, so I could just just change an already > existing PID definition instead of weaving in a new one. Or is it so that it > would be a simple matter to add a new PID? Is it enough just to add it to > id_table_combined and ftdi_chip_name?
Well, in the latest kernel version, there is only one table :) But yes, it is just as simple as adding the device to the table. Take a look at: http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-ftdi_sio-adding-vid-and-pid-for-tellstick.patch as an example of all that is needed for this. thanks, greg k-h ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
