Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

3 Commits   0 Branches   0 Tags   |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   1) ==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   2) USB serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   3) ==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   4) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   5) Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   6) ============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   7) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   8)   The USB serial driver currently supports a number of different USB to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   9)   serial converter products, as well as some devices that use a serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  10)   interface from userspace to talk to the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  11) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  12)   See the individual product section below for specific information about
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  13)   the different devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  15) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  16) Configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  17) =============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  18) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  19)   Currently the driver can handle up to 256 different serial interfaces at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  20)   one time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  21) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  22)     The major number that the driver uses is 188 so to use the driver,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  23)     create the following nodes::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  24) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  25) 	mknod /dev/ttyUSB0 c 188 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  26) 	mknod /dev/ttyUSB1 c 188 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  27) 	mknod /dev/ttyUSB2 c 188 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  28) 	mknod /dev/ttyUSB3 c 188 3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  29) 		.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  30) 		.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  31) 		.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  32) 	mknod /dev/ttyUSB254 c 188 254
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  33) 	mknod /dev/ttyUSB255 c 188 255
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  34) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  35)   When the device is connected and recognized by the driver, the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  36)   will print to the system log, which node(s) the device has been bound
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  37)   to.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  38) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  39) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  40) Specific Devices Supported
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  41) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  42) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  43) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  44) ConnectTech WhiteHEAT 4 port converter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  45) --------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  46) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  47)   ConnectTech has been very forthcoming with information about their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  48)   device, including providing a unit to test with.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  49) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  50)   The driver is officially supported by Connect Tech Inc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  51)   http://www.connecttech.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  52) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  53)   For any questions or problems with this driver, please contact
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  54)   Connect Tech's Support Department at support@connecttech.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  55) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  56) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  57) HandSpring Visor, Palm USB, and Clié USB driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  58) -----------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  59) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  60)   This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  61)   devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  62) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  63)   Only when the device tries to connect to the host, will the device show
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  64)   up to the host as a valid USB device. When this happens, the device is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  65)   properly enumerated, assigned a port, and then communication _should_ be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  66)   possible. The driver cleans up properly when the device is removed, or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  67)   the connection is canceled on the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  68) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  69)   NOTE:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  70)     This means that in order to talk to the device, the sync button must be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  71)     pressed BEFORE trying to get any program to communicate to the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  72)     This goes against the current documentation for pilot-xfer and other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  73)     packages, but is the only way that it will work due to the hardware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  74)     in the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  75) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  76)   When the device is connected, try talking to it on the second port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  77)   (this is usually /dev/ttyUSB1 if you do not have any other usb-serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  78)   devices in the system.) The system log should tell you which port is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  79)   the port to use for the HotSync transfer. The "Generic" port can be used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  80)   for other device communication, such as a PPP link.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  81) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  82)   For some Sony Clié devices, /dev/ttyUSB0 must be used to talk to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  83)   device.  This is true for all OS version 3.5 devices, and most devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  84)   that have had a flash upgrade to a newer version of the OS.  See the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  85)   kernel system log for information on which is the correct port to use.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  86) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  87)   If after pressing the sync button, nothing shows up in the system log,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  88)   try resetting the device, first a hot reset, and then a cold reset if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  89)   necessary.  Some devices need this before they can talk to the USB port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  90)   properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  91) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  92)   Devices that are not compiled into the kernel can be specified with module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  93)   parameters.  e.g. modprobe visor vendor=0x54c product=0x66
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  94) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  95)   There is a webpage and mailing lists for this portion of the driver at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  96)   http://sourceforge.net/projects/usbvisor/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  97) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  98)   For any questions or problems with this driver, please contact Greg
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  99)   Kroah-Hartman at greg@kroah.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) PocketPC PDA Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) -------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105)   This driver can be used to connect to Compaq iPAQ, HP Jornada, Casio EM500
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106)   and other PDAs running Windows CE 3.0 or PocketPC 2002 using a USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107)   cable/cradle.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108)   Most devices supported by ActiveSync are supported out of the box.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109)   For others, please use module parameters to specify the product and vendor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)   id. e.g. modprobe ipaq vendor=0x3f0 product=0x1125
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112)   The driver presents a serial interface (usually on /dev/ttyUSB0) over
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113)   which one may run ppp and establish a TCP/IP link to the PDA. Once this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)   is done, you can transfer files, backup, download email etc. The most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115)   significant advantage of using USB is speed - I can get 73 to 113
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116)   kbytes/sec for download/upload to my iPAQ.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)   This driver is only one of a set of components required to utilize
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119)   the USB connection. Please visit http://synce.sourceforge.net which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120)   contains the necessary packages and a simple step-by-step howto.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122)   Once connected, you can use Win CE programs like ftpView, Pocket Outlook
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123)   from the PDA and xcerdisp, synce utilities from the Linux side.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125)   To use Pocket IE, follow the instructions given at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126)   http://www.tekguru.co.uk/EM500/usbtonet.htm to achieve the same thing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127)   on Win98. Omit the proxy server part; Linux is quite capable of forwarding
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128)   packets unlike Win98. Another modification is required at least for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129)   iPAQ - disable autosync by going to the Start/Settings/Connections menu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130)   and unchecking the "Automatically synchronize ..." box. Go to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)   Start/Programs/Connections, connect the cable and select "usbdial" (or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132)   whatever you named your new USB connection). You should finally wind
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133)   up with a "Connected to usbdial" window with status shown as connected.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134)   Now start up PIE and browse away.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136)   If it doesn't work for some reason, load both the usbserial and ipaq module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137)   with the module parameter "debug" set to 1 and examine the system log.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138)   You can also try soft-resetting your PDA before attempting a connection.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140)   Other functionality may be possible depending on your PDA. According to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141)   Wes Cilldhaire <billybobjoehenrybob@hotmail.com>, with the Toshiba E570,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142)   ...if you boot into the bootloader (hold down the power when hitting the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143)   reset button, continuing to hold onto the power until the bootloader screen
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)   is displayed), then put it in the cradle with the ipaq driver loaded, open
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145)   a terminal on /dev/ttyUSB0, it gives you a "USB Reflash" terminal, which can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146)   be used to flash the ROM, as well as the microP code..  so much for needing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147)   Toshiba's $350 serial cable for flashing!! :D
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148)   NOTE: This has NOT been tested. Use at your own risk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150)   For any questions or problems with the driver, please contact Ganesh
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)   Varadarajan <ganesh@veritas.com>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) Keyspan PDA Serial Adapter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) --------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157)   Single port DB-9 serial adapter, pushed as a PDA adapter for iMacs (mostly
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158)   sold in Macintosh catalogs, comes in a translucent white/green dongle).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159)   Fairly simple device. Firmware is homebrew.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160)   This driver also works for the Xircom/Entrega single port serial adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162)   Current status:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164)    Things that work:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)      - basic input/output (tested with 'cu')
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166)      - blocking write when serial line can't keep up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167)      - changing baud rates (up to 115200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168)      - getting/setting modem control pins (TIOCM{GET,SET,BIS,BIC})
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169)      - sending break (although duration looks suspect)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171)    Things that don't:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)      - device strings (as logged by kernel) have trailing binary garbage
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173)      - device ID isn't right, might collide with other Keyspan products
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)      - changing baud rates ought to flush tx/rx to avoid mangled half characters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176)    Big Things on the todo list:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177)      - parity, 7 vs 8 bits per char, 1 or 2 stop bits
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178)      - HW flow control
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)      - not all of the standard USB descriptors are handled:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180)        Get_Status, Set_Feature, O_NONBLOCK, select()
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182)   For any questions or problems with this driver, please contact Brian
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183)   Warner at warner@lothar.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) Keyspan USA-series Serial Adapters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) ----------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)   Single, Dual and Quad port adapters - driver uses Keyspan supplied
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190)   firmware and is being developed with their support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192)   Current status:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194)     The USA-18X, USA-28X, USA-19, USA-19W and USA-49W are supported and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)     have been pretty thoroughly tested at various baud rates with 8-N-1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196)     character settings.  Other character lengths and parity setups are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197)     presently untested.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)     The USA-28 isn't yet supported though doing so should be pretty
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)     straightforward.  Contact the maintainer if you require this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201)     functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203)   More information is available at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205)         http://www.carnationsoftware.com/carnation/Keyspan.html
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207)   For any questions or problems with this driver, please contact Hugh
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)   Blemings at hugh@misc.nu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) FTDI Single Port Serial Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) ------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214)   This is a single port DB-25 serial adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216)   Devices supported include:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218)                 - TripNav TN-200 USB GPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219)                 - Navis Engineering Bureau CH-4711 USB GPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221)   For any questions or problems with this driver, please contact Bill Ryder.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) ZyXEL omni.net lcd plus ISDN TA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) -------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227)   This is an ISDN TA. Please report both successes and troubles to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)   azummo@towertech.it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) Cypress M8 CY4601 Family Serial Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) --------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234)   This driver was in most part developed by Neil "koyama" Whelchel.  It
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235)   has been improved since that previous form to support dynamic serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236)   line settings and improved line handling.  The driver is for the most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237)   part stable and has been tested on an smp machine. (dual p2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239)     Chipsets supported under CY4601 family:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) 		CY7C63723, CY7C63742, CY7C63743, CY7C64013
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243)     Devices supported:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) 		- DeLorme's USB Earthmate GPS (SiRF Star II lp arch)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) 		- Cypress HID->COM RS232 adapter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) 		Note:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) 			Cypress Semiconductor claims no affiliation with the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) 			hid->com device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252)      Most devices using chipsets under the CY4601 family should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253)      work with the driver.  As long as they stay true to the CY4601
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254)      usbserial specification.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256)     Technical notes:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258)         The Earthmate starts out at 4800 8N1 by default... the driver will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) 	upon start init to this setting.  usbserial core provides the rest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) 	of the termios settings, along with some custom termios so that the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) 	output is in proper format and parsable.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) 	The device can be put into sirf mode by issuing NMEA command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) 		$PSRF100,<protocol>,<baud>,<databits>,<stopbits>,<parity>*CHECKSUM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) 		$PSRF100,0,9600,8,1,0*0C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) 		It should then be sufficient to change the port termios to match this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) 		to begin communicating.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) 	As far as I can tell it supports pretty much every sirf command as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) 	documented online available with firmware 2.31, with some unknown
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) 	message ids.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) 	The hid->com adapter can run at a maximum baud of 115200bps.  Please note
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) 	that the device has trouble or is incapable of raising line voltage properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) 	It will be fine with null modem links, as long as you do not try to link two
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) 	together without hacking the adapter to set the line high.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) 	The driver is smp safe.  Performance with the driver is rather low when using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) 	it for transferring files.  This is being worked on, but I would be willing to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) 	accept patches.  An urb queue or packet buffer would likely fit the bill here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) 	If you have any questions, problems, patches, feature requests, etc. you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) 	contact me here via email:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) 					dignome@gmail.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) 		(your problems/patches can alternately be submitted to usb-devel)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) Digi AccelePort Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) ----------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295)   This driver supports the Digi AccelePort USB 2 and 4 devices, 2 port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296)   (plus a parallel port) and 4 port USB serial converters.  The driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297)   does NOT yet support the Digi AccelePort USB 8.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299)   This driver works under SMP with the usb-uhci driver.  It does not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300)   work under SMP with the uhci driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302)   The driver is generally working, though we still have a few more ioctls
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303)   to implement and final testing and debugging to do.  The parallel port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304)   on the USB 2 is supported as a serial to parallel converter; in other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305)   words, it appears as another USB serial port on Linux, even though
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306)   physically it is really a parallel port.  The Digi Acceleport USB 8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)   is not yet supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309)   Please contact Peter Berger (pberger@brimson.com) or Al Borchers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310)   (alborchers@steinerpoint.com) for questions or problems with this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311)   driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) Belkin USB Serial Adapter F5U103
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) --------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317)   Single port DB-9/PS-2 serial adapter from Belkin with firmware by eTEK Labs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318)   The Peracom single port serial adapter also works with this driver, as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319)   well as the GoHubs adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321)   Current status:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323)     The following have been tested and work:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325)       - Baud rate    300-230400
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326)       - Data bits    5-8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327)       - Stop bits    1-2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328)       - Parity       N,E,O,M,S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329)       - Handshake    None, Software (XON/XOFF), Hardware (CTSRTS,CTSDTR) [1]_
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330)       - Break        Set and clear
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331)       - Line control Input/Output query and control [2]_
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333)   .. [1]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334)          Hardware input flow control is only enabled for firmware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335)          levels above 2.06.  Read source code comments describing Belkin
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336)          firmware errata.  Hardware output flow control is working for all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337)          firmware versions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339)   .. [2]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)          Queries of inputs (CTS,DSR,CD,RI) show the last
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341)          reported state.  Queries of outputs (DTR,RTS) show the last
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342)          requested state and may not reflect current state as set by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343)          automatic hardware flow control.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345)   TO DO List:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346)     - Add true modem control line query capability.  Currently tracks the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347)       states reported by the interrupt and the states requested.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348)     - Add error reporting back to application for UART error conditions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349)     - Add support for flush ioctls.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350)     - Add everything else that is missing :)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352)   For any questions or problems with this driver, please contact William
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353)   Greathouse at wgreathouse@smva.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) Empeg empeg-car Mark I/II Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) --------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359)   This is an experimental driver to provide connectivity support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360)   client synchronization tools for an Empeg empeg-car mp3 player.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362)   Tips:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363)     * Don't forget to create the device nodes for ttyUSB{0,1,2,...}
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364)     * modprobe empeg (modprobe is your friend)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365)     * emptool --usb /dev/ttyUSB0 (or whatever you named your device node)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367)   For any questions or problems with this driver, please contact Gary
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368)   Brubaker at xavyer@ix.netcom.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) MCT USB Single Port Serial Adapter U232
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) ---------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374)   This driver is for the MCT USB-RS232 Converter (25 pin, Model No.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375)   U232-P25) from Magic Control Technology Corp. (there is also a 9 pin
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376)   Model No. U232-P9). More information about this device can be found at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377)   the manufacturer's web-site: http://www.mct.com.tw.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379)   The driver is generally working, though it still needs some more testing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380)   It is derived from the Belkin USB Serial Adapter F5U103 driver and its
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381)   TODO list is valid for this driver as well.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383)   This driver has also been found to work for other products, which have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384)   the same Vendor ID but different Product IDs. Sitecom's U232-P25 serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385)   converter uses Product ID 0x230 and Vendor ID 0x711 and works with this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386)   driver. Also, D-Link's DU-H3SP USB BAY also works with this driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388)   For any questions or problems with this driver, please contact Wolfgang
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389)   Grandegger at wolfgang@ces.ch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) Inside Out Networks Edgeport Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) -----------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395)   This driver supports all devices made by Inside Out Networks, specifically
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396)   the following models:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398)        - Edgeport/4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399)        - Rapidport/4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400)        - Edgeport/4t
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401)        - Edgeport/2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402)        - Edgeport/4i
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403)        - Edgeport/2i
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404)        - Edgeport/421
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405)        - Edgeport/21
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406)        - Edgeport/8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407)        - Edgeport/8 Dual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408)        - Edgeport/2D8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409)        - Edgeport/4D8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410)        - Edgeport/8i
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411)        - Edgeport/2 DIN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412)        - Edgeport/4 DIN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413)        - Edgeport/16 Dual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415)   For any questions or problems with this driver, please contact Greg
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416)   Kroah-Hartman at greg@kroah.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) REINER SCT cyberJack pinpad/e-com USB chipcard reader
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) -----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422)   Interface to ISO 7816 compatible contactbased chipcards, e.g. GSM SIMs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424)   Current status:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426)     This is the kernel part of the driver for this USB card reader.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427)     There is also a user part for a CT-API driver available. A site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428)     for downloading is TBA. For now, you can request it from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429)     maintainer (linux-usb@sii.li).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431)   For any questions or problems with this driver, please contact
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432)   linux-usb@sii.li
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) Prolific PL2303 Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) ----------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438)   This driver supports any device that has the PL2303 chip from Prolific
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439)   in it.  This includes a number of single port USB to serial converters,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440)   more than 70% of USB GPS devices (in 2010), and some USB UPSes. Devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441)   from Aten (the UC-232) and IO-Data work with this driver, as does
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442)   the DCU-11 mobile-phone cable.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444)   For any questions or problems with this driver, please contact Greg
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445)   Kroah-Hartman at greg@kroah.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448) KL5KUSB105 chipset / PalmConnect USB single-port adapter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) --------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451) Current status:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453)   The driver was put together by looking at the usb bus transactions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454)   done by Palm's driver under Windows, so a lot of functionality is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455)   still missing.  Notably, serial ioctls are sometimes faked or not yet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456)   implemented.  Support for finding out about DSR and CTS line status is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457)   however implemented (though not nicely), so your favorite autopilot(1)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458)   and pilot-manager -daemon calls will work.  Baud rates up to 115200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459)   are supported, but handshaking (software or hardware) is not, which is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460)   why it is wise to cut down on the rate used is wise for large
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461)   transfers until this is settled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463)   See http://www.uuhaus.de/linux/palmconnect.html for up-to-date
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464)   information on this driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) Winchiphead CH341 Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469)   This driver is for the Winchiphead CH341 USB-RS232 Converter. This chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470)   also implements an IEEE 1284 parallel port, I2C and SPI, but that is not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471)   supported by the driver. The protocol was analyzed from the behaviour
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472)   of the Windows driver, no datasheet is available at present.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474)   The manufacturer's website: http://www.winchiphead.com/.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476)   For any questions or problems with this driver, please contact
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477)   frank@kingswood-consulting.co.uk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479) Moschip MCS7720, MCS7715 driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480) -------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482)   These chips are present in devices sold by various manufacturers, such as Syba
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483)   and Cables Unlimited.  There may be others.  The 7720 provides two serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484)   ports, and the 7715 provides one serial and one standard PC parallel port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485)   Support for the 7715's parallel port is enabled by a separate option, which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486)   will not appear unless parallel port support is first enabled at the top-level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487)   of the Device Drivers config menu.  Currently only compatibility mode is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488)   supported on the parallel port (no ECP/EPP).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490)   TODO:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491)     - Implement ECP/EPP modes for the parallel port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492)     - Baud rates higher than 115200 are currently broken.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493)     - Devices with a single serial port based on the Moschip MCS7703 may work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494)       with this driver with a simple addition to the usb_device_id table.  I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495)       don't have one of these devices, so I can't say for sure.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497) Generic Serial driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500)   If your device is not one of the above listed devices, compatible with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501)   the above models, you can try out the "generic" interface. This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502)   interface does not provide any type of control messages sent to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503)   device, and does not support any kind of device flow control. All that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504)   is required of your device is that it has at least one bulk in endpoint,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505)   or one bulk out endpoint.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507)   To enable the generic driver to recognize your device, provide::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509) 	echo <vid> <pid> >/sys/bus/usb-serial/drivers/generic/new_id
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511)   where the <vid> and <pid> is replaced with the hex representation of your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512)   device's vendor id and product id.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513)   If the driver is compiled as a module you can also provide one id when
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 514)   loading the module::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 515) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 516) 	insmod usbserial vendor=0x#### product=0x####
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 517) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 518)   This driver has been successfully used to connect to the NetChip USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 519)   development board, providing a way to develop USB firmware without
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 520)   having to write a custom driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 521) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 522)   For any questions or problems with this driver, please contact Greg
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 523)   Kroah-Hartman at greg@kroah.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 524) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 525) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 526) Contact
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 527) =======
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 528) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 529)   If anyone has any problems using these drivers, with any of the above
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 530)   specified products, please contact the specific driver's author listed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 531)   above, or join the Linux-USB mailing list (information on joining the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 532)   mailing list, as well as a link to its searchable archive is at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 533)   http://www.linux-usb.org/ )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 534) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 535) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 536) Greg Kroah-Hartman
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 537) greg@kroah.com