How to poke USB IDs to kernel driver

neok · 2012-07-03 09:06:44

Hi,

I have an FTDI USB to RS232 converter, but it is not detected and the driver is not loaded because the vendor uses his own vendor and device ID's. I wonder if it possible to poke the ID's to the kernel driver so that the converter is detected.

My thanks in advance.

Lone_Wolf · 2012-07-03 12:43:28

An udev rule may solve your problem, but for that we need data.

Does lsusb show the device ?

What does dmesg show if you plug/unplug it ?

Last edited by Lone_Wolf (2012-07-03 12:44:30)

neok · 2012-07-03 14:55:15

Lone_Wolf wrote:

An udev rule may solve your problem, but for that we need data.
Does lsusb show the device ?
What does dmesg show if you plug/unplug it ?

Hi,

lsusb shows the device:

Bus 009 Device 002: ID 2100:9e56

Actually it is an FTDI USB to RS232 cable for an FT857 ham radio transceiver but the maker uses his own vendor and device ID's which are unknown to the kernel. The driver would normally be ftdi_sio.
dmesg shows the following for disconnect/connect:

[  833.346668] usb 9-2: USB disconnect, device number 2
[  858.109949] usb 9-2: new full-speed USB device number 3 using uhci_hcd

tomk · 2012-07-03 15:41:55

Grab the kernel source and edit drivers/usb/serial/ftdi_sio_ids.h as required - vendor id 2100 is already there, you just need to add a line for the 9e56 device.

neok · 2012-07-03 16:31:54

tomk wrote:

Grab the kernel source and edit drivers/usb/serial/ftdi_sio_ids.h as required - vendor id 2100 is already there, you just need to add a line for the 9e56 device.

Thanks, I will give it a try. Actually, I just tried an idea I found on Google, using

modprobe ftdi_sio vendor=0x2100 product=0x9e56

This produces a device /dev/ttyUSB0 which I can open through my transceiver control program, but the transceiver is not reponding.

Anyhow, thanks - we are stuck with the tricks of Windoze - only manufacturers. Wht harm will it do to be more open....they just want to sell their wares.

neok · 2012-07-03 18:51:18

neok wrote:

tomk wrote:
Grab the kernel source and edit drivers/usb/serial/ftdi_sio_ids.h as required - vendor id 2100 is already there, you just need to add a line for the 9e56 device.
Thanks, I will give it a try. Actually, I just tried an idea I found on Google, using
modprobe ftdi_sio vendor=0x2100 product=0x9e56
This produces a device /dev/ttyUSB0 which I can open through my transceiver control program, but the transceiver is not reponding.
Anyhow, thanks - we are stuck with the tricks of Windoze - only manufacturers. Wht harm will it do to be more open....they just want to sell their wares.

OK, I got it to work eventually as above. The transceiver itself had to be set up to match the baud rate in the control program.
My thanks for the help given here in the Arch forums.

Arch Linux

#1 2012-07-03 09:06:44

How to poke USB IDs to kernel driver

#2 2012-07-03 12:43:28

Re: How to poke USB IDs to kernel driver

#3 2012-07-03 14:55:15

Re: How to poke USB IDs to kernel driver

#4 2012-07-03 15:41:55

Re: How to poke USB IDs to kernel driver

#5 2012-07-03 16:31:54

Re: How to poke USB IDs to kernel driver

#6 2012-07-03 18:51:18

Re: How to poke USB IDs to kernel driver

Board footer