diff options
| author | Ralf Baechle <ralf@linux-mips.org> | 2000-02-05 06:47:02 +0000 |
|---|---|---|
| committer | Ralf Baechle <ralf@linux-mips.org> | 2000-02-05 06:47:02 +0000 |
| commit | 99a7e12f34b3661a0d1354eef83a0eef4df5e34c (patch) | |
| tree | 3560aca9ca86792f9ab7bd87861ea143a1b3c7a3 /Documentation/usb/usb-serial.txt | |
| parent | e73a04659c0b8cdee4dd40e58630e2cf63afb316 (diff) | |
Merge with Linux 2.3.38.
Diffstat (limited to 'Documentation/usb/usb-serial.txt')
| -rw-r--r-- | Documentation/usb/usb-serial.txt | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/Documentation/usb/usb-serial.txt b/Documentation/usb/usb-serial.txt new file mode 100644 index 000000000..053f18d2e --- /dev/null +++ b/Documentation/usb/usb-serial.txt @@ -0,0 +1,42 @@ +This serial driver currently only works with the Belkin and Peracom USB +Serial devices. It should also work for the Etek converter, but I do +not know the vendor id and device id of that device (if anyone does, +please let me know.) + +If your device is not compatible with the above models, you can try +out the "generic" interface. This interface does not provide any type +of control messages sent to the device, and does not support any kind +of device flow control. All that is required of your device is that +it has at least one bulk in endpoint, or one bulk out endpoint. +To enable the driver to recognize your device, build the driver as +a module and load it by the following invocation: + insmod usb-serial.o vendor=0x#### product=0x#### +where the #### is replaced with the hex representation of your device's +vendor id and product id. + +The driver can handle enumerating the device, and sending and receiving +data from the converter. However, since I do not have a spec for the Belkin, +Peracom, and eTek devices, and the raw dumps from the Win98 driver are +confusing, and eTek keeps giving me the run around, no control signals are +currently handled, and the data will most likely come through on a baud +rate that you are not expecting. So if you have these devices, do not +expect the correct data to show up at either end. + +The major number that the driver uses is 188 so to use the driver, create +the following nodes: +mknod /dev/ttyUSB0 c 188 0 +mknod /dev/ttyUSB1 c 188 1 +mknod /dev/ttyUSB2 c 188 2 +mknod /dev/ttyUSB3 c 188 3 + +then plug in a device and use your friendly terminal program to see what +happens. + +If anyone has any problems getting the device to enumerate, or data to +flow through it, please contact me. + + + +greg k-h +greg@kroah.com + |