2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
|
# USB Serial device configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "USB Serial Converter support"
|
|
|
|
|
depends on USB!=n
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL
|
|
|
|
|
tristate "USB Serial Converter support"
|
|
|
|
|
depends on USB
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you have a USB device that provides normal serial
|
|
|
|
|
ports, or acts like a serial device, and you want to connect it to
|
|
|
|
|
your USB bus.
|
|
|
|
|
|
|
|
|
|
Please read <file:Documentation/usb/usb-serial.txt> for more
|
|
|
|
|
information on the specifics of the different devices that are
|
|
|
|
|
supported, and on how to use them.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called usbserial.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_CONSOLE
|
|
|
|
|
bool "USB Serial Console device support (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL=y && EXPERIMENTAL
|
|
|
|
|
---help---
|
|
|
|
|
If you say Y here, it will be possible to use a USB to serial
|
|
|
|
|
converter port as the system console (the system console is the
|
|
|
|
|
device which receives all kernel messages and warnings and which
|
|
|
|
|
allows logins in single user mode). This could be useful if some
|
|
|
|
|
terminal or printer is connected to that serial port.
|
|
|
|
|
|
|
|
|
|
Even if you say Y here, the currently visible virtual console
|
|
|
|
|
(/dev/tty0) will still be used as the system console by default, but
|
|
|
|
|
you can alter that using a kernel command line option such as
|
|
|
|
|
"console=ttyUSB0". (Try "man bootparam" or see the documentation of
|
|
|
|
|
your boot loader (lilo or loadlin) about how to pass options to the
|
|
|
|
|
kernel at boot time.)
|
|
|
|
|
|
|
|
|
|
If you don't have a VGA card installed and you say Y here, the
|
|
|
|
|
kernel will automatically use the first USB to serial converter
|
|
|
|
|
port, /dev/ttyUSB0, as system console.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_GENERIC
|
|
|
|
|
bool "USB Generic Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the generic USB serial driver. Please
|
|
|
|
|
read <file:Documentation/usb/usb-serial.txt> for more information on
|
|
|
|
|
using this driver. It is recommended that the "USB Serial converter
|
|
|
|
|
support" be compiled as a module for this driver to be used
|
|
|
|
|
properly.
|
|
|
|
|
|
2006-08-09 13:35:12 -06:00
|
|
|
config USB_SERIAL_AIRCABLE
|
|
|
|
|
tristate "AIRcable USB Bluetooth Dongle Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use AIRcable USB Bluetoot Dongle.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called aircable.
|
|
|
|
|
|
2005-04-25 22:46:29 -06:00
|
|
|
config USB_SERIAL_AIRPRIME
|
|
|
|
|
tristate "USB AirPrime CDMA Wireless Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a AirPrime CDMA Wireless PC card.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called airprime.
|
|
|
|
|
|
2006-05-12 12:05:29 -06:00
|
|
|
config USB_SERIAL_ARK3116
|
|
|
|
|
tristate "USB ARK Micro 3116 USB Serial Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a ARK Micro 3116 USB to Serial
|
|
|
|
|
device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ark3116
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_BELKIN
|
|
|
|
|
tristate "USB Belkin and Peracom Single Port Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a Belkin USB Serial single port
|
|
|
|
|
adaptor (F5U103 is one of the model numbers) or the Peracom single
|
|
|
|
|
port USB to serial adapter.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called belkin_sa.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_WHITEHEAT
|
|
|
|
|
tristate "USB ConnectTech WhiteHEAT Serial Driver"
|
[PATCH] TTY layer buffering revamp
The API and code have been through various bits of initial review by
serial driver people but they definitely need to live somewhere for a
while so the unconverted drivers can get knocked into shape, existing
drivers that have been updated can be better tuned and bugs whacked out.
This replaces the tty flip buffers with kmalloc objects in rings. In the
normal situation for an IRQ driven serial port at typical speeds the
behaviour is pretty much the same, two buffers end up allocated and the
kernel cycles between them as before.
When there are delays or at high speed we now behave far better as the
buffer pool can grow a bit rather than lose characters. This also means
that we can operate at higher speeds reliably.
For drivers that receive characters in blocks (DMA based, USB and
especially virtualisation) the layer allows a lot of driver specific
code that works around the tty layer with private secondary queues to be
removed. The IBM folks need this sort of layer, the smart serial port
people do, the virtualisers do (because a virtualised tty typically
operates at infinite speed rather than emulating 9600 baud).
Finally many drivers had invalid and unsafe attempts to avoid buffer
overflows by directly invoking tty methods extracted out of the innards
of work queue structs. These are no longer needed and all go away. That
fixes various random hangs with serial ports on overflow.
The other change in here is to optimise the receive_room path that is
used by some callers. It turns out that only one ldisc uses receive room
except asa constant and it updates it far far less than the value is
read. We thus make it a variable not a function call.
I expect the code to contain bugs due to the size alone but I'll be
watching and squashing them and feeding out new patches as it goes.
Because the buffers now dynamically expand you should only run out of
buffering when the kernel runs out of memory for real. That means a lot of
the horrible hacks high performance drivers used to do just aren't needed any
more.
Description:
tty_insert_flip_char is an old API and continues to work as before, as does
tty_flip_buffer_push() [this is why many drivers dont need modification]. It
does now also return the number of chars inserted
There are also
tty_buffer_request_room(tty, len)
which asks for a buffer block of the length requested and returns the space
found. This improves efficiency with hardware that knows how much to
transfer.
and tty_insert_flip_string_flags(tty, str, flags, len)
to insert a string of characters and flags
For a smart interface the usual code is
len = tty_request_buffer_room(tty, amount_hardware_says);
tty_insert_flip_string(tty, buffer_from_card, len);
More description!
At the moment tty buffers are attached directly to the tty. This is causing a
lot of the problems related to tty layer locking, also problems at high speed
and also with bursty data (such as occurs in virtualised environments)
I'm working on ripping out the flip buffers and replacing them with a pool of
dynamically allocated buffers. This allows both for old style "byte I/O"
devices and also helps virtualisation and smart devices where large blocks of
data suddenely materialise and need storing.
So far so good. Lots of drivers reference tty->flip.*. Several of them also
call directly and unsafely into function pointers it provides. This will all
break. Most drivers can use tty_insert_flip_char which can be kept as an API
but others need more.
At the moment I've added the following interfaces, if people think more will
be needed now is a good time to say
int tty_buffer_request_room(tty, size)
Try and ensure at least size bytes are available, returns actual room (may be
zero). At the moment it just uses the flipbuf space but that will change.
Repeated calls without characters being added are not cumulative. (ie if you
call it with 1, 1, 1, and then 4 you'll have four characters of space. The
other functions will also try and grow buffers in future but this will be a
more efficient way when you know block sizes.
int tty_insert_flip_char(tty, ch, flag)
As before insert a character if there is room. Now returns 1 for success, 0
for failure.
int tty_insert_flip_string(tty, str, len)
Insert a block of non error characters. Returns the number inserted.
int tty_prepare_flip_string(tty, strptr, len)
Adjust the buffer to allow len characters to be added. Returns a buffer
pointer in strptr and the length available. This allows for hardware that
needs to use functions like insl or mencpy_fromio.
Signed-off-by: Alan Cox <alan@redhat.com>
Cc: Paul Fulghum <paulkf@microgate.com>
Signed-off-by: Hirokazu Takata <takata@linux-m32r.org>
Signed-off-by: Serge Hallyn <serue@us.ibm.com>
Signed-off-by: Jeff Dike <jdike@addtoit.com>
Signed-off-by: John Hawkes <hawkes@sgi.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-01-09 21:54:13 -07:00
|
|
|
depends on USB_SERIAL
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
|
|
|
|
|
USB to serial converter device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called whiteheat.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_DIGI_ACCELEPORT
|
|
|
|
|
tristate "USB Digi International AccelePort USB Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
|
|
|
|
|
2 port (plus parallel port) and 4 port USB serial converters. The
|
|
|
|
|
parallel port on the USB 2 appears as a third serial port on Linux.
|
|
|
|
|
The Digi Acceleport USB 8 is not yet supported by this driver.
|
|
|
|
|
|
|
|
|
|
This driver works under SMP with the usb-uhci driver. It does not
|
|
|
|
|
work under SMP with the uhci driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called digi_acceleport.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_CP2101
|
|
|
|
|
tristate "USB CP2101 UART Bridge Controller"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a CP2101/CP2102 based USB to RS232
|
|
|
|
|
converter.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cp2101.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_CYPRESS_M8
|
|
|
|
|
tristate "USB Cypress M8 USB Serial Driver"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a device that contains the Cypress
|
|
|
|
|
USB to Serial microcontroller, such as the DeLorme Earthmate GPS.
|
|
|
|
|
|
|
|
|
|
Attempted SMP support... send bug reports!
|
|
|
|
|
|
|
|
|
|
Supported microcontrollers in the CY4601 family are:
|
|
|
|
|
CY7C63741 CY7C63742 CY7C63743 CY7C64013
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cypress_m8.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_EMPEG
|
|
|
|
|
tristate "USB Empeg empeg-car Mark I/II Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to connect to your Empeg empeg-car Mark I/II
|
|
|
|
|
mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
|
|
|
|
|
device node. See <file:Documentation/usb/usb-serial.txt> for more
|
|
|
|
|
tidbits of information.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called empeg.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_FTDI_SIO
|
|
|
|
|
tristate "USB FTDI Single Port Serial Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use a FTDI SIO single port USB to serial
|
|
|
|
|
converter device. The implementation I have is called the USC-1000.
|
|
|
|
|
This driver has also be tested with the 245 and 232 devices.
|
|
|
|
|
|
|
|
|
|
See <http://ftdi-usb-sio.sourceforge.net/> for more
|
|
|
|
|
information on this driver and the device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ftdi_sio.
|
|
|
|
|
|
2006-04-13 09:09:52 -06:00
|
|
|
config USB_SERIAL_FUNSOFT
|
|
|
|
|
tristate "USB Fundamental Software Dongle Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use the Fundamental Software dongle.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called funsoft.
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_VISOR
|
|
|
|
|
tristate "USB Handspring Visor / Palm m50x / Sony Clie Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to connect to your HandSpring Visor, Palm
|
|
|
|
|
m500 or m505 through its USB docking station. See
|
|
|
|
|
<http://usbvisor.sourceforge.net/> for more information on using this
|
|
|
|
|
driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called visor.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_IPAQ
|
|
|
|
|
tristate "USB PocketPC PDA Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to connect to your Compaq iPAQ, HP Jornada
|
|
|
|
|
or any other PDA running Windows CE 3.0 or PocketPC 2002
|
|
|
|
|
using a USB cradle/cable. For information on using the driver,
|
|
|
|
|
read <file:Documentation/usb/usb-serial.txt>.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ipaq.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_IR
|
|
|
|
|
tristate "USB IR Dongle Serial Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to enable simple serial support for USB IrDA
|
|
|
|
|
devices. This is useful if you do not want to use the full IrDA
|
|
|
|
|
stack.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ir-usb.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_EDGEPORT
|
|
|
|
|
tristate "USB Inside Out Edgeport Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use any of the following devices from
|
|
|
|
|
Inside Out Networks (Digi):
|
|
|
|
|
Edgeport/4
|
|
|
|
|
Rapidport/4
|
|
|
|
|
Edgeport/4t
|
|
|
|
|
Edgeport/2
|
|
|
|
|
Edgeport/4i
|
|
|
|
|
Edgeport/2i
|
|
|
|
|
Edgeport/421
|
|
|
|
|
Edgeport/21
|
|
|
|
|
Edgeport/8
|
|
|
|
|
Edgeport/8 Dual
|
|
|
|
|
Edgeport/2D8
|
|
|
|
|
Edgeport/4D8
|
|
|
|
|
Edgeport/8i
|
|
|
|
|
Edgeport/2 DIN
|
|
|
|
|
Edgeport/4 DIN
|
|
|
|
|
Edgeport/16 Dual
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called io_edgeport.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_EDGEPORT_TI
|
|
|
|
|
tristate "USB Inside Out Edgeport Serial Driver (TI devices)"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use any of the devices from Inside Out
|
|
|
|
|
Networks (Digi) that are not supported by the io_edgeport driver.
|
|
|
|
|
This includes the Edgeport/1 device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called io_ti.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_GARMIN
|
|
|
|
|
tristate "USB Garmin GPS driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to connect to your Garmin GPS.
|
|
|
|
|
Should work with most Garmin GPS devices which have a native USB port.
|
|
|
|
|
|
|
|
|
|
See <http://sourceforge.net/projects/garmin-gps> for the latest
|
|
|
|
|
version of the driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called garmin_gps.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_IPW
|
|
|
|
|
tristate "USB IPWireless (3G UMTS TDD) Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a IPWireless USB modem such as
|
|
|
|
|
the ones supplied by Axity3G/Sentech South Africa.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ipw.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_PDA
|
|
|
|
|
tristate "USB Keyspan PDA Single Port Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a Keyspan PDA single port USB to
|
|
|
|
|
serial converter device. This driver makes use of firmware
|
|
|
|
|
developed from scratch by Brian Warner.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called keyspan_pda.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN
|
|
|
|
|
tristate "USB Keyspan USA-xxx Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use Keyspan USB to serial converter
|
|
|
|
|
devices. This driver makes use of Keyspan's official firmware
|
|
|
|
|
and was developed with their support. You must also include
|
|
|
|
|
firmware to support your particular device(s).
|
|
|
|
|
|
|
|
|
|
See <http://misc.nu/hugh/keyspan.html> for more information.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called keyspan.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_MPR
|
|
|
|
|
bool "USB Keyspan MPR Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the Keyspan MPR converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA28
|
|
|
|
|
bool "USB Keyspan USA-28 Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-28 converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA28X
|
|
|
|
|
bool "USB Keyspan USA-28X Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-28X converter.
|
|
|
|
|
Be sure you have a USA-28X, there are also 28XA and 28XB
|
|
|
|
|
models, the label underneath has the actual part number.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA28XA
|
|
|
|
|
bool "USB Keyspan USA-28XA Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-28XA converter.
|
|
|
|
|
Be sure you have a USA-28XA, there are also 28X and 28XB
|
|
|
|
|
models, the label underneath has the actual part number.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA28XB
|
|
|
|
|
bool "USB Keyspan USA-28XB Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-28XB converter.
|
|
|
|
|
Be sure you have a USA-28XB, there are also 28X and 28XA
|
|
|
|
|
models, the label underneath has the actual part number.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA19
|
|
|
|
|
bool "USB Keyspan USA-19 Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-19 converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA18X
|
|
|
|
|
bool "USB Keyspan USA-18X Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-18X converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA19W
|
|
|
|
|
bool "USB Keyspan USA-19W Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-19W converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA19QW
|
|
|
|
|
bool "USB Keyspan USA-19QW Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-19QW converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA19QI
|
|
|
|
|
bool "USB Keyspan USA-19QI Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-19QI converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA49W
|
|
|
|
|
bool "USB Keyspan USA-49W Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-49W converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KEYSPAN_USA49WLC
|
|
|
|
|
bool "USB Keyspan USA-49WLC Firmware"
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include firmware for the USA-49WLC converter.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KLSI
|
|
|
|
|
tristate "USB KL5KUSB105 (Palmconnect) Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use a KL5KUSB105 - based single port
|
|
|
|
|
serial adapter. The most widely known -- and currently the only
|
|
|
|
|
tested -- device in this category is the PalmConnect USB Serial
|
|
|
|
|
adapter sold by Palm Inc. for use with their Palm III and Palm V
|
|
|
|
|
series PDAs.
|
|
|
|
|
|
|
|
|
|
Please read <file:Documentation/usb/usb-serial.txt> for more
|
|
|
|
|
information.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called kl5kusb105.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_KOBIL_SCT
|
|
|
|
|
tristate "USB KOBIL chipcard reader"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use one of the following KOBIL USB chipcard
|
|
|
|
|
readers:
|
|
|
|
|
|
|
|
|
|
- USB TWIN
|
|
|
|
|
- KAAN Standard Plus
|
|
|
|
|
- KAAN SIM
|
|
|
|
|
- SecOVID Reader Plus
|
|
|
|
|
- B1 Professional
|
|
|
|
|
- KAAN Professional
|
|
|
|
|
|
|
|
|
|
Note that you need a current CT-API.
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called kobil_sct.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_MCT_U232
|
|
|
|
|
tristate "USB MCT Single Port Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use a USB Serial single port adapter from
|
|
|
|
|
Magic Control Technology Corp. (U232 is one of the model numbers).
|
|
|
|
|
|
|
|
|
|
This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB
|
2006-05-22 23:02:32 -06:00
|
|
|
BAY, Belkin F5U109, and Belkin F5U409 devices.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called mct_u232.
|
|
|
|
|
|
2006-08-31 18:41:47 -06:00
|
|
|
config USB_SERIAL_MOS7840
|
|
|
|
|
tristate "USB Moschip 7840/7820 USB Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use a MCS7840 Quad-Serial or MCS7820
|
|
|
|
|
Dual-Serial port device from MosChip Semiconductor.
|
|
|
|
|
|
|
|
|
|
The MCS7840 and MCS7820 have been developed to connect a wide range
|
|
|
|
|
of standard serial devices to a USB host. The MCS7840 has a USB
|
|
|
|
|
device controller connected to four (4) individual UARTs while the
|
|
|
|
|
MCS7820 controller connects to two (2) individual UARTs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called mos7840. If unsure, choose N.
|
|
|
|
|
|
2006-03-17 18:40:08 -07:00
|
|
|
config USB_SERIAL_NAVMAN
|
|
|
|
|
tristate "USB Navman GPS device"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called navman.
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_PL2303
|
|
|
|
|
tristate "USB Prolific 2303 Single Port Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the PL2303 USB Serial single port
|
|
|
|
|
adapter from Prolific.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called pl2303.
|
|
|
|
|
|
2005-04-22 16:06:59 -06:00
|
|
|
config USB_SERIAL_HP4X
|
|
|
|
|
tristate "USB HP4x Calculators support"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use an Hewlett-Packard 4x Calculator.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called hp4x.
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_SAFE
|
|
|
|
|
tristate "USB Safe Serial (Encapsulated) Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_SAFE_PADDED
|
|
|
|
|
bool "USB Secure Encapsulated Driver - Padded"
|
|
|
|
|
depends on USB_SERIAL_SAFE
|
|
|
|
|
|
2006-06-30 12:17:55 -06:00
|
|
|
config USB_SERIAL_SIERRAWIRELESS
|
|
|
|
|
tristate "USB Sierra Wireless Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say M here if you want to use a Sierra Wireless device (if
|
|
|
|
|
using an PC 5220 or AC580 please use the Airprime driver
|
|
|
|
|
instead).
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called sierra.
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_TI
|
|
|
|
|
tristate "USB TI 3410/5052 Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use the TI USB 3410 or 5052
|
|
|
|
|
serial devices.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ti_usb_3410_5052.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_CYBERJACK
|
|
|
|
|
tristate "USB REINER SCT cyberJack pinpad/e-com chipcard reader (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard
|
|
|
|
|
reader. This is an interface to ISO 7816 compatible contactbased
|
|
|
|
|
chipcards, e.g. GSM SIMs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called cyberjack.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config USB_SERIAL_XIRCOM
|
|
|
|
|
tristate "USB Xircom / Entregra Single Port Serial Driver"
|
|
|
|
|
depends on USB_SERIAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a Xircom or Entregra single port USB to
|
|
|
|
|
serial converter device. This driver makes use of firmware
|
|
|
|
|
developed from scratch by Brian Warner.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called keyspan_pda.
|
|
|
|
|
|
2005-05-23 18:00:48 -06:00
|
|
|
config USB_SERIAL_OPTION
|
2006-07-12 00:35:29 -06:00
|
|
|
tristate "USB driver for GSM and CDMA modems"
|
2006-06-02 03:48:56 -06:00
|
|
|
depends on USB_SERIAL
|
2005-05-23 18:00:48 -06:00
|
|
|
help
|
2006-07-12 00:35:29 -06:00
|
|
|
Say Y here if you have a GSM or CDMA modem that's connected to USB.
|
|
|
|
|
|
|
|
|
|
This driver also supports several PCMCIA cards which have a
|
|
|
|
|
built-in OHCI-USB adapter and an internally-connected GSM modem.
|
|
|
|
|
The USB bus on these cards is not accessible externally.
|
2006-06-02 03:48:56 -06:00
|
|
|
|
2006-07-12 00:35:29 -06:00
|
|
|
Supported devices include (some of?) those made by:
|
|
|
|
|
Option, Huawei, Audiovox, Sierra Wireless, Novatel Wireless, or
|
|
|
|
|
Anydata.
|
2005-05-23 18:00:48 -06:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called option.
|
|
|
|
|
|
2006-06-02 03:48:56 -06:00
|
|
|
If this driver doesn't recognize your device,
|
|
|
|
|
it might be accessible via the FTDI_SIO driver.
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config USB_SERIAL_OMNINET
|
|
|
|
|
tristate "USB ZyXEL omni.net LCD Plus Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on USB_SERIAL && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called omninet.
|
|
|
|
|
|
|
|
|
|
config USB_EZUSB
|
|
|
|
|
bool
|
|
|
|
|
depends on USB_SERIAL_KEYSPAN_PDA || USB_SERIAL_XIRCOM || USB_SERIAL_KEYSPAN || USB_SERIAL_WHITEHEAT
|
|
|
|
|
default y
|
|
|
|
|
|
2006-08-09 13:35:12 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
endmenu
|
|
|
|
|
|