USB: remove staging quatech_usb2 driver

Now that we have a "real" driver for the quatech devices, we can remove
the drivers/staging/quatech_usb2/ driver as it is no longer needed.

Thanks to Bill Pemberton for writing the new driver.

Cc: Richard Ash <richard@audacityteam.org>
Cc: Bill Pemberton <wfp5p@virginia.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Greg Kroah-Hartman 2012-05-10 14:09:16 -07:00
parent f88e6a30da
commit 38902cf9f6
6 changed files with 0 additions and 1977 deletions

View File

@ -68,8 +68,6 @@ source "drivers/staging/octeon/Kconfig"
source "drivers/staging/serqt_usb2/Kconfig"
source "drivers/staging/quatech_usb2/Kconfig"
source "drivers/staging/vt6655/Kconfig"
source "drivers/staging/vt6656/Kconfig"

View File

@ -25,7 +25,6 @@ obj-$(CONFIG_TRANZPORT) += frontier/
obj-$(CONFIG_IDE_PHISON) += phison/
obj-$(CONFIG_LINE6_USB) += line6/
obj-$(CONFIG_USB_SERIAL_QUATECH2) += serqt_usb2/
obj-$(CONFIG_USB_SERIAL_QUATECH_USB2) += quatech_usb2/
obj-$(CONFIG_OCTEON_ETHERNET) += octeon/
obj-$(CONFIG_VT6655) += vt6655/
obj-$(CONFIG_VT6656) += vt6656/

View File

@ -1,15 +0,0 @@
config USB_SERIAL_QUATECH_USB2
tristate "USB Quatech xSU2-[14]00 USB Serial Driver"
depends on USB_SERIAL
help
Say Y here if you want to use a Quatech USB2.0 to serial adaptor. This
driver supports the SSU2-100, DSU2-100, DSU2-400, QSU2-100, QSU2-400,
ESU2-400 and ESU2-100 USB2.0 to RS232 / 485 / 422 serial adaptors.
Some hardware has an incorrect product string and announces itself as
ESU-100 (which uses the serqt driver) even though it is an ESU2-100.
Check the label on the bottom of your device.
To compile this driver as a module, choose M here: the module will be
called quatech_usb2 .

View File

@ -1 +0,0 @@
obj-$(CONFIG_USB_SERIAL_QUATECH_USB2) += quatech_usb2.o

View File

@ -1,8 +0,0 @@
Incomplete list of things that this driver does not yet implement completely or
at all. some of these may not be possible to implement because the hardware
support does not exist. Others may be possible, but the magic control codes to
make them happen are unknown, and some may just need the driver support to
implement them writing.
* Mark/Space parity is not implemented (reported back correctly)
* IXANY flow control mode is not implemented (flag ignored completely)

File diff suppressed because it is too large Load Diff