Bug #1882
open
Idea for handling new USB vendor/device codes
Added by bmk about 14 years ago.
Updated about 14 years ago.
Description
This is just an idea / wish.
Have a config file called /etc/usb_hotwire.conf
e.g.:
- This file allows you to map a new unsupported usb vendor/device code
- to an existing usb vendor/device code supported by a driver.
- File Format:
- <unsupported vendor code>:<unsupported device code> <supported vendor
code>:<supported device code>
- The following makes my unsupported USB wireless adapter use the same driver
(rum) as a D-Link DWL-G122
0x1044:0x2573 0x07d1:0x3c03
As an after thought, /etc/usb_hotwire.conf would only be checked before falling
back to the ugen driver, that way it would not interfere with supported devices.
On Wed, Oct 20, 2010 at 11:09:27AM +0000, Brendan Kosowski (via DragonFly issue tracker) wrote:
Brendan Kosowski <bmk@bmk.com.au> added the comment:
As an after thought, /etc/usb_hotwire.conf would only be checked before falling
back to the ugen driver, that way it would not interfere with supported devices.
I would prefer to see all vendor/device IDs in a file which maps
each device to its driver. I think having a device claim to be
something it isn't will only cause confusion.
Handling non-trivial device additions would still require digging into
the driver code. However being able to easily add support for new
devices which may differ only in device ID would be a really nice
feature.
Joe
Also available in: Atom
PDF
Updated by 
Updated by