I tried a handful of modules but nothing would bind to it. So I'm wondering how hard it would be to get it to bind to a port with an existing module or new module, or if I'm completely thinking in the wrong direction.
Short of changing a few device IDs in the code per peoeple here I haven't really looked into linux's usb code, but ya gotta start somewhere, right?
The cable itself is a USB device, most likely a USB<->serial converter. You can try to bind the generic driver to it using module parameters.
While I'm at it, I thought I'd try and figure out why the driver doesn't automatically recognize the device -- there doesn't seem to be an usual_devs.h for serial though.
usb-serial.c says:
/* There is no MODULE_DEVICE_TABLE for usbserial.c. Instead the MODULE_DEVICE_TABLE declarations in each serial driver cause the "hotplug" program to pull in whatever module is necessary via modprobe, and modprobe will load usbserial because the serial drivers depend on it. */
Which in theory makes sense - but I don't think any serial driver is needed in this instance, but I could be wrong.
-- Phil Dibowitz [EMAIL PROTECTED] Freeware and Technical Pages Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759
signature.asc
Description: OpenPGP digital signature
