brintos

brintos / linux-shallow public Read only

0
0
Text · 19.7 KiB · 69586ae Raw
538 lines · plain
1==========2USB serial3==========4 5Introduction6============7 8  The USB serial driver currently supports a number of different USB to9  serial converter products, as well as some devices that use a serial10  interface from userspace to talk to the device.11 12  See the individual product section below for specific information about13  the different devices.14 15 16Configuration17=============18 19  Currently the driver can handle up to 256 different serial interfaces at20  one time.21 22    The major number that the driver uses is 188 so to use the driver,23    create the following nodes::24 25	mknod /dev/ttyUSB0 c 188 026	mknod /dev/ttyUSB1 c 188 127	mknod /dev/ttyUSB2 c 188 228	mknod /dev/ttyUSB3 c 188 329		.30		.31		.32	mknod /dev/ttyUSB254 c 188 25433	mknod /dev/ttyUSB255 c 188 25534 35  When the device is connected and recognized by the driver, the driver36  will print to the system log, which node(s) the device has been bound37  to.38 39 40Specific Devices Supported41==========================42 43 44ConnectTech WhiteHEAT 4 port converter45--------------------------------------46 47  ConnectTech has been very forthcoming with information about their48  device, including providing a unit to test with.49 50  The driver is officially supported by Connect Tech Inc.51  http://www.connecttech.com52 53  For any questions or problems with this driver, please contact54  Connect Tech's Support Department at support@connecttech.com55 56 57HandSpring Visor, Palm USB, and Clié USB driver58-----------------------------------------------59 60  This driver works with all HandSpring USB, Palm USB, and Sony Clié USB61  devices.62 63  Only when the device tries to connect to the host, will the device show64  up to the host as a valid USB device. When this happens, the device is65  properly enumerated, assigned a port, and then communication _should_ be66  possible. The driver cleans up properly when the device is removed, or67  the connection is canceled on the device.68 69  NOTE:70    This means that in order to talk to the device, the sync button must be71    pressed BEFORE trying to get any program to communicate to the device.72    This goes against the current documentation for pilot-xfer and other73    packages, but is the only way that it will work due to the hardware74    in the device.75 76  When the device is connected, try talking to it on the second port77  (this is usually /dev/ttyUSB1 if you do not have any other usb-serial78  devices in the system.) The system log should tell you which port is79  the port to use for the HotSync transfer. The "Generic" port can be used80  for other device communication, such as a PPP link.81 82  For some Sony Clié devices, /dev/ttyUSB0 must be used to talk to the83  device.  This is true for all OS version 3.5 devices, and most devices84  that have had a flash upgrade to a newer version of the OS.  See the85  kernel system log for information on which is the correct port to use.86 87  If after pressing the sync button, nothing shows up in the system log,88  try resetting the device, first a hot reset, and then a cold reset if89  necessary.  Some devices need this before they can talk to the USB port90  properly.91 92  Devices that are not compiled into the kernel can be specified with module93  parameters.  e.g. modprobe visor vendor=0x54c product=0x6694 95  There is a webpage and mailing lists for this portion of the driver at:96  http://sourceforge.net/projects/usbvisor/97 98  For any questions or problems with this driver, please contact Greg99  Kroah-Hartman at greg@kroah.com100 101 102PocketPC PDA Driver103-------------------104 105  This driver can be used to connect to Compaq iPAQ, HP Jornada, Casio EM500106  and other PDAs running Windows CE 3.0 or PocketPC 2002 using a USB107  cable/cradle.108  Most devices supported by ActiveSync are supported out of the box.109  For others, please use module parameters to specify the product and vendor110  id. e.g. modprobe ipaq vendor=0x3f0 product=0x1125111 112  The driver presents a serial interface (usually on /dev/ttyUSB0) over113  which one may run ppp and establish a TCP/IP link to the PDA. Once this114  is done, you can transfer files, backup, download email etc. The most115  significant advantage of using USB is speed - I can get 73 to 113116  kbytes/sec for download/upload to my iPAQ.117 118  This driver is only one of a set of components required to utilize119  the USB connection. Please visit http://synce.sourceforge.net which120  contains the necessary packages and a simple step-by-step howto.121 122  Once connected, you can use Win CE programs like ftpView, Pocket Outlook123  from the PDA and xcerdisp, synce utilities from the Linux side.124 125  To use Pocket IE, follow the instructions given at126  http://www.tekguru.co.uk/EM500/usbtonet.htm to achieve the same thing127  on Win98. Omit the proxy server part; Linux is quite capable of forwarding128  packets unlike Win98. Another modification is required at least for the129  iPAQ - disable autosync by going to the Start/Settings/Connections menu130  and unchecking the "Automatically synchronize ..." box. Go to131  Start/Programs/Connections, connect the cable and select "usbdial" (or132  whatever you named your new USB connection). You should finally wind133  up with a "Connected to usbdial" window with status shown as connected.134  Now start up PIE and browse away.135 136  If it doesn't work for some reason, load both the usbserial and ipaq module137  with the module parameter "debug" set to 1 and examine the system log.138  You can also try soft-resetting your PDA before attempting a connection.139 140  Other functionality may be possible depending on your PDA. According to141  Wes Cilldhaire <billybobjoehenrybob@hotmail.com>, with the Toshiba E570,142  ...if you boot into the bootloader (hold down the power when hitting the143  reset button, continuing to hold onto the power until the bootloader screen144  is displayed), then put it in the cradle with the ipaq driver loaded, open145  a terminal on /dev/ttyUSB0, it gives you a "USB Reflash" terminal, which can146  be used to flash the ROM, as well as the microP code..  so much for needing147  Toshiba's $350 serial cable for flashing!! :D148  NOTE: This has NOT been tested. Use at your own risk.149 150  For any questions or problems with the driver, please contact Ganesh151  Varadarajan <ganesh@veritas.com>152 153 154Keyspan PDA Serial Adapter155--------------------------156 157  Single port DB-9 serial adapter, pushed as a PDA adapter for iMacs (mostly158  sold in Macintosh catalogs, comes in a translucent white/green dongle).159  Fairly simple device. Firmware is homebrew.160  This driver also works for the Xircom/Entrega single port serial adapter.161 162  Current status:163 164   Things that work:165     - basic input/output (tested with 'cu')166     - blocking write when serial line can't keep up167     - changing baud rates (up to 115200)168     - getting/setting modem control pins (TIOCM{GET,SET,BIS,BIC})169     - sending break (although duration looks suspect)170 171   Things that don't:172     - device strings (as logged by kernel) have trailing binary garbage173     - device ID isn't right, might collide with other Keyspan products174     - changing baud rates ought to flush tx/rx to avoid mangled half characters175 176   Big Things on the todo list:177     - parity, 7 vs 8 bits per char, 1 or 2 stop bits178     - HW flow control179     - not all of the standard USB descriptors are handled:180       Get_Status, Set_Feature, O_NONBLOCK, select()181 182  For any questions or problems with this driver, please contact Brian183  Warner at warner@lothar.com184 185 186Keyspan USA-series Serial Adapters187----------------------------------188 189  Single, Dual and Quad port adapters - driver uses Keyspan supplied190  firmware and is being developed with their support.191 192  Current status:193 194    The USA-18X, USA-28X, USA-19, USA-19W and USA-49W are supported and195    have been pretty thoroughly tested at various baud rates with 8-N-1196    character settings.  Other character lengths and parity setups are197    presently untested.198 199    The USA-28 isn't yet supported though doing so should be pretty200    straightforward.  Contact the maintainer if you require this201    functionality.202 203  More information is available at:204 205        http://www.carnationsoftware.com/carnation/Keyspan.html206 207  For any questions or problems with this driver, please contact Hugh208  Blemings at hugh@misc.nu209 210 211FTDI Single Port Serial Driver212------------------------------213 214  This is a single port DB-25 serial adapter.215 216  Devices supported include:217 218                - TripNav TN-200 USB GPS219                - Navis Engineering Bureau CH-4711 USB GPS220 221  For any questions or problems with this driver, please contact Bill Ryder.222 223 224ZyXEL omni.net lcd plus ISDN TA225-------------------------------226 227  This is an ISDN TA. Please report both successes and troubles to228  azummo@towertech.it229 230 231Cypress M8 CY4601 Family Serial Driver232--------------------------------------233 234  This driver was in most part developed by Neil "koyama" Whelchel.  It235  has been improved since that previous form to support dynamic serial236  line settings and improved line handling.  The driver is for the most237  part stable and has been tested on an smp machine. (dual p2)238 239    Chipsets supported under CY4601 family:240 241		CY7C63723, CY7C63742, CY7C63743, CY7C64013242 243    Devices supported:244 245		- DeLorme's USB Earthmate GPS (SiRF Star II lp arch)246		- Cypress HID->COM RS232 adapter247 248		Note:249			Cypress Semiconductor claims no affiliation with the250			hid->com device.251 252     Most devices using chipsets under the CY4601 family should253     work with the driver.  As long as they stay true to the CY4601254     usbserial specification.255 256    Technical notes:257 258        The Earthmate starts out at 4800 8N1 by default... the driver will259	upon start init to this setting.  usbserial core provides the rest260	of the termios settings, along with some custom termios so that the261	output is in proper format and parsable.262 263	The device can be put into sirf mode by issuing NMEA command::264 265		$PSRF100,<protocol>,<baud>,<databits>,<stopbits>,<parity>*CHECKSUM266		$PSRF100,0,9600,8,1,0*0C267 268		It should then be sufficient to change the port termios to match this269		to begin communicating.270 271	As far as I can tell it supports pretty much every sirf command as272	documented online available with firmware 2.31, with some unknown273	message ids.274 275	The hid->com adapter can run at a maximum baud of 115200bps.  Please note276	that the device has trouble or is incapable of raising line voltage properly.277	It will be fine with null modem links, as long as you do not try to link two278	together without hacking the adapter to set the line high.279 280	The driver is smp safe.  Performance with the driver is rather low when using281	it for transferring files.  This is being worked on, but I would be willing to282	accept patches.  An urb queue or packet buffer would likely fit the bill here.283 284	If you have any questions, problems, patches, feature requests, etc. you can285	contact me here via email:286 287					dignome@gmail.com288 289		(your problems/patches can alternately be submitted to usb-devel)290 291 292Digi AccelePort Driver293----------------------294 295  This driver supports the Digi AccelePort USB 2 and 4 devices, 2 port296  (plus a parallel port) and 4 port USB serial converters.  The driver297  does NOT yet support the Digi AccelePort USB 8.298 299  This driver works under SMP with the usb-uhci driver.  It does not300  work under SMP with the uhci driver.301 302  The driver is generally working, though we still have a few more ioctls303  to implement and final testing and debugging to do.  The parallel port304  on the USB 2 is supported as a serial to parallel converter; in other305  words, it appears as another USB serial port on Linux, even though306  physically it is really a parallel port.  The Digi Acceleport USB 8307  is not yet supported.308 309  Please contact Peter Berger (pberger@brimson.com) or Al Borchers310  (alborchers@steinerpoint.com) for questions or problems with this311  driver.312 313 314Belkin USB Serial Adapter F5U103315--------------------------------316 317  Single port DB-9/PS-2 serial adapter from Belkin with firmware by eTEK Labs.318  The Peracom single port serial adapter also works with this driver, as319  well as the GoHubs adapter.320 321  Current status:322 323    The following have been tested and work:324 325      - Baud rate    300-230400326      - Data bits    5-8327      - Stop bits    1-2328      - Parity       N,E,O,M,S329      - Handshake    None, Software (XON/XOFF), Hardware (CTSRTS,CTSDTR) [1]_330      - Break        Set and clear331      - Line control Input/Output query and control [2]_332 333  .. [1]334         Hardware input flow control is only enabled for firmware335         levels above 2.06.  Read source code comments describing Belkin336         firmware errata.  Hardware output flow control is working for all337         firmware versions.338 339  .. [2]340         Queries of inputs (CTS,DSR,CD,RI) show the last341         reported state.  Queries of outputs (DTR,RTS) show the last342         requested state and may not reflect current state as set by343         automatic hardware flow control.344 345  TO DO List:346    - Add true modem control line query capability.  Currently tracks the347      states reported by the interrupt and the states requested.348    - Add error reporting back to application for UART error conditions.349    - Add support for flush ioctls.350    - Add everything else that is missing :)351 352  For any questions or problems with this driver, please contact William353  Greathouse at wgreathouse@smva.com354 355 356Empeg empeg-car Mark I/II Driver357--------------------------------358 359  This is an experimental driver to provide connectivity support for the360  client synchronization tools for an Empeg empeg-car mp3 player.361 362  Tips:363    * Don't forget to create the device nodes for ttyUSB{0,1,2,...}364    * modprobe empeg (modprobe is your friend)365    * emptool --usb /dev/ttyUSB0 (or whatever you named your device node)366 367  For any questions or problems with this driver, please contact Gary368  Brubaker at xavyer@ix.netcom.com369 370 371MCT USB Single Port Serial Adapter U232372---------------------------------------373 374  This driver is for the MCT USB-RS232 Converter (25 pin, Model No.375  U232-P25) from Magic Control Technology Corp. (there is also a 9 pin376  Model No. U232-P9). More information about this device can be found at377  the manufacturer's web-site: http://www.mct.com.tw.378 379  The driver is generally working, though it still needs some more testing.380  It is derived from the Belkin USB Serial Adapter F5U103 driver and its381  TODO list is valid for this driver as well.382 383  This driver has also been found to work for other products, which have384  the same Vendor ID but different Product IDs. Sitecom's U232-P25 serial385  converter uses Product ID 0x230 and Vendor ID 0x711 and works with this386  driver. Also, D-Link's DU-H3SP USB BAY also works with this driver.387 388  For any questions or problems with this driver, please contact Wolfgang389  Grandegger at wolfgang@ces.ch390 391 392Inside Out Networks Edgeport Driver393-----------------------------------394 395  This driver supports all devices made by Inside Out Networks, specifically396  the following models:397 398       - Edgeport/4399       - Rapidport/4400       - Edgeport/4t401       - Edgeport/2402       - Edgeport/4i403       - Edgeport/2i404       - Edgeport/421405       - Edgeport/21406       - Edgeport/8407       - Edgeport/8 Dual408       - Edgeport/2D8409       - Edgeport/4D8410       - Edgeport/8i411       - Edgeport/2 DIN412       - Edgeport/4 DIN413       - Edgeport/16 Dual414 415  For any questions or problems with this driver, please contact Greg416  Kroah-Hartman at greg@kroah.com417 418 419REINER SCT cyberJack pinpad/e-com USB chipcard reader420-----------------------------------------------------421 422  Interface to ISO 7816 compatible contactbased chipcards, e.g. GSM SIMs.423 424  Current status:425 426    This is the kernel part of the driver for this USB card reader.427    There is also a user part for a CT-API driver available. A site428    for downloading is TBA. For now, you can request it from the429    maintainer (linux-usb@sii.li).430 431  For any questions or problems with this driver, please contact432  linux-usb@sii.li433 434 435Prolific PL2303 Driver436----------------------437 438  This driver supports any device that has the PL2303 chip from Prolific439  in it.  This includes a number of single port USB to serial converters,440  more than 70% of USB GPS devices (in 2010), and some USB UPSes. Devices441  from Aten (the UC-232) and IO-Data work with this driver, as does442  the DCU-11 mobile-phone cable.443 444  For any questions or problems with this driver, please contact Greg445  Kroah-Hartman at greg@kroah.com446 447 448KL5KUSB105 chipset / PalmConnect USB single-port adapter449--------------------------------------------------------450 451Current status:452 453  The driver was put together by looking at the usb bus transactions454  done by Palm's driver under Windows, so a lot of functionality is455  still missing.  Notably, serial ioctls are sometimes faked or not yet456  implemented.  Support for finding out about DSR and CTS line status is457  however implemented (though not nicely), so your favorite autopilot(1)458  and pilot-manager -daemon calls will work.  Baud rates up to 115200459  are supported, but handshaking (software or hardware) is not, which is460  why it is wise to cut down on the rate used is wise for large461  transfers until this is settled.462 463  See http://www.uuhaus.de/linux/palmconnect.html for up-to-date464  information on this driver.465 466Winchiphead CH341 Driver467------------------------468 469  This driver is for the Winchiphead CH341 USB-RS232 Converter. This chip470  also implements an IEEE 1284 parallel port, I2C and SPI, but that is not471  supported by the driver. The protocol was analyzed from the behaviour472  of the Windows driver, no datasheet is available at present.473 474  The manufacturer's website: http://www.winchiphead.com/.475 476  For any questions or problems with this driver, please contact477  frank@kingswood-consulting.co.uk.478 479Moschip MCS7720, MCS7715 driver480-------------------------------481 482  These chips are present in devices sold by various manufacturers, such as Syba483  and Cables Unlimited.  There may be others.  The 7720 provides two serial484  ports, and the 7715 provides one serial and one standard PC parallel port.485  Support for the 7715's parallel port is enabled by a separate option, which486  will not appear unless parallel port support is first enabled at the top-level487  of the Device Drivers config menu.  Currently only compatibility mode is488  supported on the parallel port (no ECP/EPP).489 490  TODO:491    - Implement ECP/EPP modes for the parallel port.492    - Baud rates higher than 115200 are currently broken.493    - Devices with a single serial port based on the Moschip MCS7703 may work494      with this driver with a simple addition to the usb_device_id table.  I495      don't have one of these devices, so I can't say for sure.496 497Generic Serial driver498---------------------499 500  If your device is not one of the above listed devices, compatible with501  the above models, you can try out the "generic" interface. This502  interface does not provide any type of control messages sent to the503  device, and does not support any kind of device flow control. All that504  is required of your device is that it has at least one bulk in endpoint,505  or one bulk out endpoint.506 507  To enable the generic driver to recognize your device, provide::508 509	echo <vid> <pid> >/sys/bus/usb-serial/drivers/generic/new_id510 511  where the <vid> and <pid> is replaced with the hex representation of your512  device's vendor id and product id.513  If the driver is compiled as a module you can also provide one id when514  loading the module::515 516	insmod usbserial vendor=0x#### product=0x####517 518  This driver has been successfully used to connect to the NetChip USB519  development board, providing a way to develop USB firmware without520  having to write a custom driver.521 522  For any questions or problems with this driver, please contact Greg523  Kroah-Hartman at greg@kroah.com524 525 526Contact527=======528 529  If anyone has any problems using these drivers, with any of the above530  specified products, please contact the specific driver's author listed531  above, or join the Linux-USB mailing list (information on joining the532  mailing list, as well as a link to its searchable archive is at533  http://www.linux-usb.org/ )534 535 536Greg Kroah-Hartman537greg@kroah.com538