1999-11-18 18:02:44 +00:00
|
|
|
$FreeBSD$
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Copyright (c) 1998 The NetBSD Foundation, Inc.
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* This code is derived from software contributed to The NetBSD Foundation
|
|
|
|
|
* by Lennart Augustsson (augustss@carlstedt.se) at
|
|
|
|
|
* Carlstedt Research & Technology.
|
|
|
|
|
*
|
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
|
* are met:
|
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
|
* This product includes software developed by the NetBSD
|
|
|
|
|
* Foundation, Inc. and its contributors.
|
|
|
|
|
* 4. Neither the name of The NetBSD Foundation nor the names of its
|
|
|
|
|
* contributors may be used to endorse or promote products derived
|
|
|
|
|
* from this software without specific prior written permission.
|
|
|
|
|
*
|
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
|
|
|
|
|
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
|
|
|
|
|
* TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
|
|
|
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
|
|
|
|
|
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
|
|
|
|
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
|
|
|
|
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
|
|
|
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
|
|
|
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
|
|
|
* POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* List of known USB vendors
|
|
|
|
|
*/
|
|
|
|
|
|
2000-01-05 18:25:53 +00:00
|
|
|
vendor AOX 0x03e8 Aox Inc.
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor HP 0x03f0 Hewlett Packard
|
|
|
|
|
vendor NEC 0x0409 NEC
|
|
|
|
|
vendor KODAK 0x040a Eastman Kodak Corp.
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
vendor MELCO 0x0411 Melco Inc.
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor CATC 0x0423 Computer Access Technology Corp.
|
|
|
|
|
vendor GRAVIS 0x0428 Advanced Gravis Computer Tech. Ltd.
|
|
|
|
|
vendor LEXMARK 0x043d Lexmark International Inc.
|
|
|
|
|
vendor NANAO 0x0440 NANAO Corp.
|
|
|
|
|
vendor THRUST 0x044f Thrustmaster
|
|
|
|
|
vendor TI 0x0451 Texas Instruments
|
|
|
|
|
vendor KYE 0x0458 KYE Systems Corp.
|
|
|
|
|
vendor MICROSOFT 0x045e Microsoft
|
|
|
|
|
vendor PRIMAX 0x0461 Primax Electronics
|
|
|
|
|
vendor CHERRY 0x046a Cherry Mikroschalter GmbH
|
|
|
|
|
vendor LOGITECH 0x046d Logitech Inc.
|
|
|
|
|
vendor BTC 0x046e Behavior Tech. Computer
|
|
|
|
|
vendor PHILIPS 0x0471 Philips
|
|
|
|
|
vendor CONNECTIX 0x0478 Connectix Corp.
|
|
|
|
|
vendor LUCENT 0x047e Lucent
|
|
|
|
|
vendor STMICRO 0x0483 STMicroelectronics
|
|
|
|
|
vendor ACER 0x04a5 Acer Peripheral Inc.
|
|
|
|
|
vendor CANON 0x04a9 Canon Inc.
|
|
|
|
|
vendor CYPRESS 0x04b4 Cypress Semiconductor
|
|
|
|
|
vendor EPSON 0x04b8 Seiko Epson Corp.
|
2000-01-05 04:27:24 +00:00
|
|
|
vendor 3COMUSR 0x04c1 U.S. Robotics
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor KONICA 0x04c8 Konica Corp.
|
|
|
|
|
vendor ALTEC 0x04d2 Altec Lansing
|
|
|
|
|
vendor SHUTTLE 0x04e6 Shuttle Technology
|
|
|
|
|
vendor CHICONY 0x04f2 Chicony Electronics Co., Ltd.
|
|
|
|
|
vendor BROTHER 0x04f9 Brother Industries Corp.
|
|
|
|
|
vendor DALLAS 0x04fa Dallas Semiconductor
|
2000-01-05 04:27:24 +00:00
|
|
|
vendor 3COM 0x0506 3Com Corp.
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor BELKIN 0x050d Belkin Components
|
|
|
|
|
vendor KAWATSU 0x050f Kawatsu Semiconductor, Inc.
|
|
|
|
|
vendor APC 0x051d American Power Conversion
|
|
|
|
|
vendor AKS 0x0529 Fast Security AG
|
|
|
|
|
vendor UNIACCESS 0x0540 Universal Access
|
|
|
|
|
vendor ANCHOR 0x0547 Anchor Chips Inc.
|
|
|
|
|
vendor VISION 0x0553 VLSI Vision Ltd.
|
|
|
|
|
vendor ATEN 0x0557 ATEN International Corp. Ltd.
|
|
|
|
|
vendor MUSTEK 0x055f Mustek Systems Inc.
|
|
|
|
|
vendor TELEX 0x0562 Telex Communications Inc.
|
|
|
|
|
vendor PERACOM 0x0565 Peracom Networks Inc.
|
|
|
|
|
vendor WACOM 0x056a WACOM Corp. Ltd.
|
|
|
|
|
vendor ETEK 0x056c e-TEK Labs
|
|
|
|
|
vendor EIZO 0x056d EIZO
|
|
|
|
|
vendor ELECOM 0x056e Elecom Corp. Ltd.
|
|
|
|
|
vendor ROCKFIRE 0x0583 Rockfire
|
|
|
|
|
vendor IOMEGA 0x059b Iomega Corp.
|
|
|
|
|
vendor OMNIVISION 0x05a9 OmniVision
|
|
|
|
|
vendor INSYSTEM 0x05ab In-System Design
|
|
|
|
|
vendor APPLE 0x05ac Apple Computer
|
|
|
|
|
vendor QTRONIX 0x05c7 Qtronix Corp
|
|
|
|
|
vendor ELSA 0x05cc ELSA Gmbh
|
|
|
|
|
vendor EIZONANAO 0x05e7 EIZO Nanao
|
2000-01-05 18:25:53 +00:00
|
|
|
vendor KLSI 0x05e9 Kawasaki LSI
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor PIENGINEERING 0x05f3 P.I. Engineering
|
|
|
|
|
vendor CHIC 0x05fe Chic Technology
|
|
|
|
|
vendor MACALLY 0x0618 Macally
|
|
|
|
|
vendor MULTITECH 0x06e0 MultiTech
|
|
|
|
|
vendor ADS 0x06e1 ADS Technologies
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
vendor SMC 0x0707 Standard Microsystems Corp
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor MIDIMAN 0x0763 Midiman
|
|
|
|
|
vendor SANDISK 0x0781 SanDisk Corp
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
vendor ADMTEK 0x07a6 ADMtek Inc.
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor SIIG 0x07cc SIIG
|
|
|
|
|
vendor HANDSPRING 0x082d Handspring Inc.
|
|
|
|
|
vendor ACTIVEWIRE 0x0854 ActiveWire Inc.
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
vendor NETGEAR 0x0846 BayNETGEAR Inc.
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
vendor BILLIONTON 0x08DD Billionton Systems
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor MOTOROLA 0x1063 Motorola
|
|
|
|
|
vendor PLX 0x10b5 PLX
|
|
|
|
|
vendor INSIDEOUT 0x1608 Inside Out Networks
|
|
|
|
|
vendor ENTREGA 0x1645 Entrega
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
vendor DLINK 0x2001 D-Link Corp
|
1999-11-18 18:02:44 +00:00
|
|
|
vendor INTEL 0x8086 Intel
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* List of known products. Grouped by vendor.
|
|
|
|
|
*/
|
|
|
|
|
|
2000-01-05 18:25:53 +00:00
|
|
|
/* AOX Inc. products */
|
|
|
|
|
product AOX USB101 0x0008 USB ethernet controller engine
|
2000-01-05 04:27:24 +00:00
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* HP products */
|
|
|
|
|
product HP 4100C 0x0101 Scanjet 4100C
|
|
|
|
|
product HP 6300C 0x0601 Scanjet 6300C
|
|
|
|
|
|
|
|
|
|
/* NEC products */
|
|
|
|
|
product NEC HUB 0x55aa hub
|
|
|
|
|
product NEC HUB_B 0x55ab hub
|
|
|
|
|
|
|
|
|
|
/* Kodak products */
|
|
|
|
|
product KODAK DC260 0x0110 Digital Science DC260
|
|
|
|
|
product KODAK DC240 0x0120 Digital Science DC240
|
|
|
|
|
product KODAK DC280 0x0130 Digital Science DC280
|
|
|
|
|
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
/* Melco products */
|
|
|
|
|
product MELCO LUATX 0x0001 LU-ATX Ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* CATC products */
|
|
|
|
|
product CATC ANDROMEDA 0x1237 Andromeda hub
|
|
|
|
|
product CATC CHIEF 0x000d USB Chief Bus & Protocol Analyzer
|
|
|
|
|
|
|
|
|
|
/* Gravis products */
|
|
|
|
|
product GRAVIS GAMEPADPRO 0x4001 GamePad Pro
|
|
|
|
|
|
|
|
|
|
/* Lexmark products */
|
|
|
|
|
product LEXMARK S2450 0x0009 Optra S 2450
|
|
|
|
|
|
|
|
|
|
/* Thrustmaster products */
|
|
|
|
|
product THRUST FUSION_PAD 0xa0a3 Fusion Digital Gamepad
|
|
|
|
|
|
|
|
|
|
/* Texas Intel products */
|
|
|
|
|
product TI UTUSB41 0x1446 UT-USB41 hub
|
|
|
|
|
|
|
|
|
|
/* (KYE) Genius products */
|
|
|
|
|
product KYE NICHE 0x0001 Niche mouse
|
|
|
|
|
product KYE FLIGHT2000 0x1004 Flight 2000 joystick
|
|
|
|
|
|
|
|
|
|
/* Microsoft products */
|
|
|
|
|
product MICROSOFT INTELLIMOUSE 0x0009 IntelliMouse
|
|
|
|
|
product MICROSOFT NATURALKBD 0x000b Natural Keyboard Elite
|
|
|
|
|
product MICROSOFT DDS80 0x0014 Digital Sound System 80
|
|
|
|
|
|
|
|
|
|
/* Primax products */
|
|
|
|
|
product PRIMAX COMFORT 0x4d01 Comfort
|
|
|
|
|
product PRIMAX MOUSEINABOX 0x4d02 Mouse-in-a-Box
|
|
|
|
|
|
|
|
|
|
/* Cherry products */
|
|
|
|
|
product CHERRY MY3000KBD 0x0001 My3000 keyboard
|
|
|
|
|
product CHERRY MY3000HUB 0x0003 My3000 hub
|
|
|
|
|
|
|
|
|
|
/* Behavior Technology Computer products */
|
|
|
|
|
product BTC BTC7932 0x6782 Keyboard with mouse port
|
|
|
|
|
|
|
|
|
|
/* Philips products */
|
|
|
|
|
product PHILIPS DSS350 0x0101 DSS 350 Digital Speaker System
|
|
|
|
|
product PHILIPS DSS 0x0104 DSS XXX Digital Speaker System
|
|
|
|
|
product PHILIPS HUB 0x0201 hub
|
|
|
|
|
product PHILIPS DSS150 0x0471 DSS XXX Digital Speaker System
|
|
|
|
|
|
|
|
|
|
/* Connectix products */
|
|
|
|
|
product CONNECTIX QUICKCAM 0x0001 QuickCam
|
|
|
|
|
|
|
|
|
|
/* Lucent products */
|
|
|
|
|
product LUCENT EVALKIT 0x1001 USS-720 evaluation kit
|
|
|
|
|
|
|
|
|
|
/* STMicroelectronics products */
|
|
|
|
|
product STMICRO COMMUNICATOR 0x7554 USB Communicator
|
|
|
|
|
|
|
|
|
|
/* Acer products */
|
|
|
|
|
product ACER ACERSCAN_C310U 0x12a6 Acerscan C310U
|
|
|
|
|
|
|
|
|
|
/* Canon Inc. products */
|
|
|
|
|
product CANON S10 0x3041 PowerShot S10
|
|
|
|
|
|
|
|
|
|
/* Cypress Semiconductor products */
|
|
|
|
|
product CYPRESS MOUSE 0x0001 mouse
|
|
|
|
|
product CYPRESS THERMO 0x0002 thermometer
|
|
|
|
|
|
|
|
|
|
/* Epson products */
|
|
|
|
|
product EPSON PRINTER3 0x0003 ISD USB Smart Cable
|
|
|
|
|
|
|
|
|
|
/* 3Com products */
|
2000-01-05 04:27:24 +00:00
|
|
|
product 3COMUSR USR56K 0x3021 U.S.Robotics 56000 Voice Faxmodem Pro
|
1999-11-18 18:02:44 +00:00
|
|
|
|
|
|
|
|
/* Konica Corp. Products */
|
|
|
|
|
product KONICA CAMERA 0x0720 Digital Color Camera
|
|
|
|
|
|
|
|
|
|
/* Altec Lansing products */
|
|
|
|
|
product ALTEC ASC495 0xff05 ASC495 Speakers
|
|
|
|
|
|
|
|
|
|
/* Shuttle Technology products */
|
|
|
|
|
product SHUTTLE EUSB 0x0001 E-USB Bridge
|
|
|
|
|
|
|
|
|
|
/* Chicony products */
|
|
|
|
|
product CHICONY KB8933 0x0001 KB-8933 keyboard
|
|
|
|
|
|
|
|
|
|
/* Brother Industries products */
|
|
|
|
|
product BROTHER HL1050 0x0002 HL-1050 laser printer
|
|
|
|
|
|
|
|
|
|
/* Dallas Semiconductor products */
|
|
|
|
|
product DALLAS J6502 0x4201 J-6502 speakers
|
|
|
|
|
|
2000-01-05 04:27:24 +00:00
|
|
|
/* 3Com products */
|
|
|
|
|
product 3COM 3C19250 0x03E8 3C19250 Ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* Kawatsu products */
|
|
|
|
|
product KAWATSU MH4000P 0x0003 MiniHub 4000P
|
|
|
|
|
|
|
|
|
|
/* American Power Conversion products */
|
|
|
|
|
product APC UPSPRO500 0x0002 Back-UPS Pro 500
|
|
|
|
|
|
|
|
|
|
/* AKS products */
|
|
|
|
|
product AKS USBHASP 0x0001 USB-HASP 0.06
|
|
|
|
|
|
|
|
|
|
/* Universal Access products */
|
|
|
|
|
product UNIACCESS PANACHE 0x0101 Panache Surf USB ISDN Adapter
|
|
|
|
|
|
|
|
|
|
/* Anchor products */
|
|
|
|
|
product ANCHOR EZUSB 0x2131 EZUSB
|
|
|
|
|
|
|
|
|
|
/* Vision products */
|
|
|
|
|
product VISION VC6452V002 0x0002 VC6452V002 Camera
|
|
|
|
|
|
|
|
|
|
/* ATen products */
|
|
|
|
|
product ATEN UC1284 0x2001 Parallel printer adapter
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
product ATEN UC10T 0x2002 10Mbps ethernet adapter
|
1999-11-18 18:02:44 +00:00
|
|
|
|
|
|
|
|
/* Mustek products */
|
|
|
|
|
product MUSTEK MDC800 0xa800 MDC-800 digital camera
|
|
|
|
|
|
|
|
|
|
/* Telex Communications products */
|
|
|
|
|
product TELEX MIC1 0x0001 Enhanced USB Microphone
|
|
|
|
|
|
|
|
|
|
/* Peracom products */
|
|
|
|
|
product PERACOM SERIAL1 0x0001 Serial Converter
|
2000-01-05 04:27:24 +00:00
|
|
|
product PERACOM ENET 0x0002 Ethernet adapter
|
|
|
|
|
product PERACOM ENET2 0x0005 Ethernet adapter
|
1999-11-18 18:02:44 +00:00
|
|
|
|
|
|
|
|
/* Wacom products */
|
|
|
|
|
product WACOM CT0405U 0x0000 CT-0405-U Tablet
|
|
|
|
|
|
|
|
|
|
/* e-TEK Labs products */
|
|
|
|
|
product ETEK 1COM 0x8007 Serial port
|
|
|
|
|
|
|
|
|
|
/* EIZO products */
|
|
|
|
|
product EIZO HUB 0x0000 hub
|
|
|
|
|
product EIZO MONITOR 0x0001 monitor
|
|
|
|
|
|
|
|
|
|
/* Agiler products */
|
|
|
|
|
product ELECOM MOUSE29UO 0x0002 mouse 29UO
|
|
|
|
|
|
|
|
|
|
/* Rockfire products */
|
|
|
|
|
product ROCKFIRE GAMEPAD 0x2033 gamepad 203USB
|
|
|
|
|
|
|
|
|
|
/* Iomega products */
|
|
|
|
|
product IOMEGA ZIP100 0x0001 Zip 100
|
|
|
|
|
|
|
|
|
|
/* OmniVision Technologies Inc. products */
|
|
|
|
|
product OMNIVISION OV511 0x0511 OV511 Camera
|
|
|
|
|
|
|
|
|
|
/* In-System products */
|
|
|
|
|
product INSYSTEM F5U002 0x0002 Parallel printer adapter
|
|
|
|
|
product INSYSTEM ISD110 0x0200 IDE adapter
|
|
|
|
|
|
|
|
|
|
/* Qtronix products */
|
|
|
|
|
product QTRONIX 980N 0x2011 Scorpion-980N keyboard
|
|
|
|
|
|
|
|
|
|
/* Elsa products */
|
|
|
|
|
product ELSA MODEM1 0x2265 ELSA Modem Board
|
|
|
|
|
|
|
|
|
|
/* Logitech products */
|
|
|
|
|
product LOGITECH M2452 0x0203 M2452 keyboard
|
|
|
|
|
product LOGITECH M4848 0x0301 M4848 mouse
|
|
|
|
|
product LOGITECH QUICKCAM 0x0801 QuickCam
|
|
|
|
|
product LOGITECH QUICKCAMPRO 0x0810 QuickCam Pro
|
|
|
|
|
product LOGITECH N48 0xc001 N48 mouse
|
|
|
|
|
product LOGITECH MBA47 0xc002 M-BA47 mouse
|
|
|
|
|
|
|
|
|
|
/* P.I. Engineering products */
|
|
|
|
|
product PIENGINEERING PS2USB 0x020b PS2 to Mac USB Adapter
|
|
|
|
|
|
|
|
|
|
/* Chic Technology products */
|
|
|
|
|
product CHIC MOUSE1 0x0001 mouse
|
|
|
|
|
|
|
|
|
|
/* Macally products */
|
|
|
|
|
product MACALLY MOUSE1 0x0101 mouse
|
|
|
|
|
|
|
|
|
|
/* MultiTech products */
|
|
|
|
|
product MULTITECH ATLAS 0xf101 MT5634ZBA-USB modem
|
|
|
|
|
|
|
|
|
|
/* ADS products */
|
|
|
|
|
product ADS ENET 0x0008 Ethernet adapter
|
|
|
|
|
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
/* SMC products */
|
|
|
|
|
product SMC 2102USB 0x0100 10Mbps ethernet adapter
|
|
|
|
|
product SMC 2202USB 0x0200 10/100 ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* Entrega products */
|
|
|
|
|
product ENTREGA 1S 0x0001 1S serial connector
|
|
|
|
|
product ENTREGA 2S 0x0002 2S serial connector
|
|
|
|
|
product ENTREGA 1S25 0x0003 1S25 serial connector
|
|
|
|
|
product ENTREGA 4S 0x0004 4S serial connector
|
2000-01-05 04:27:24 +00:00
|
|
|
product ENTREGA E45 0x0005 E45 Ethernet adapter
|
1999-11-18 18:02:44 +00:00
|
|
|
product ENTREGA CENTRONICS 0x0006 Centronics connector
|
|
|
|
|
product ENTREGA 1S9 0x0093 1S9 serial connector
|
|
|
|
|
product ENTREGA EZUSB 0x8000 EZ-USB
|
|
|
|
|
product ENTREGA SERIAL 0x8001 DB25 Serial connector
|
|
|
|
|
product ENTREGA SERIAL_DB9 0x8093 DB9 Serial connector
|
|
|
|
|
|
|
|
|
|
/* Midiman products */
|
|
|
|
|
product MIDIMAN MIDISPORT2X2 0x1001 Midisport 2x2
|
|
|
|
|
|
|
|
|
|
/* SanDisk products */
|
|
|
|
|
product SANDISK IMAGEMATE 0x0001 USB ImageMate
|
|
|
|
|
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
/* ADMtek products */
|
|
|
|
|
product ADMTEK PEGASUS 0x0986 AN986 USB Ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* SIIG products */
|
|
|
|
|
product SIIG DIGIFILMREADER 0x0004 DigiFilm-Combo Reader
|
|
|
|
|
|
|
|
|
|
/* Handspring Inc. */
|
|
|
|
|
product HANDSPRING VISOR 0x0100 Handspring Visor
|
|
|
|
|
|
|
|
|
|
/* ActiveWire Inc. products */
|
|
|
|
|
product ACTIVEWIRE IOBOARD 0x0100 I/O Board
|
|
|
|
|
product ACTIVEWIRE IOBOARD_FW1 0x0101 I/O Board, rev. 1 firmware
|
|
|
|
|
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
/* Netgear products */
|
|
|
|
|
product NETGEAR EA101 0x1001 Ethernet adapter
|
|
|
|
|
|
This commit adds device driver support for the ADMtek AN986 Pegasus
USB ethernet chip. Adapters that use this chip include the LinkSys
USB100TX. There are a few others, but I'm not certain of their
availability in the U.S. I used an ADMtek eval board for development.
Note that while the ADMtek chip is a 100Mbps device, you can't really
get 100Mbps speeds over USB. Regardless, this driver uses miibus to
allow speed and duplex mode selection as well as autonegotiation.
Building and kldloading the driver as a module is also supported.
Note that in order to make this driver work, I had to make what some
may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer()
function will use tsleep() for synchronous transfers that don't complete
right away. This is a problem since there are times when we need to
do sync transfers from an interrupt context (i.e. when reading registers
from the MAC via the control endpoint), where tsleep() us a no-no.
My hack allows the driver to have the code poll for transfer completion
subject to the xfer->timeout timeout rather that calling tsleep().
This hack is controlled by a quirk entry and is only enabled for the
ADMtek device.
Now, I'm sure there are a few of you out there ready to jump on me
and suggest some other approach that doesn't involve a busy wait. The
only solution that might work is to handle the interrupts in a kernel
thread, where you may have something resembling a process context that
makes it okay to tsleep(). This is lovely, except we don't have any
mechanism like that now, and I'm not about to implement such a thing
myself since it's beyond the scope of driver development. (Translation:
I'll be damned if I know how to do it.) If FreeBSD ever aquires such
a mechanism, I'll be glad to revisit the driver to take advantage of
it. In the meantime, I settled for what I perceived to be the solution
that involved the least amount of code changes. In general, the hit
is pretty light.
Also note that my only USB test box has a UHCI controller: I haven't
I don't have a machine with an OHCI controller available.
Highlights:
- Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part.
- Updated usbdevs and regenerated generated files
- Updated HARDWARE.TXT and RELNOTES.TXT files
- Updated sysinstall/device.c and userconfig.c
- Updated kernel configs -- device aue0 is commented out by default
- Updated /sys/conf/files
- Added new kld module directory
1999-12-28 02:01:18 +00:00
|
|
|
/* Billionton products */
|
|
|
|
|
product BILLIONTON USB100 0x0986 USB100 Ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* Motorola products */
|
|
|
|
|
product MOTOROLA MC141555 0x1555 MC141555 hub controller
|
|
|
|
|
|
|
|
|
|
/* PLX products */
|
|
|
|
|
product PLX TESTBOARD 0x9060 test board
|
|
|
|
|
|
|
|
|
|
/* Inside Out Networks products */
|
|
|
|
|
product INSIDEOUT EDGEPORT4 0x0001 EdgePort/4 serial ports
|
|
|
|
|
|
Add the vendor and device IDs for a whole bunch of additional USB
ethernet adapters that are supported by the aue and kue drivers.
There are actually a couple more out there from Accton, Asante and
EXP Computer, however I was not able to find any Windows device
drivers for these on their servers, and hence could not harvest
their vendor/device ID info. If somebody has one of these things
and can look in the .inf file that comes with the Windows driver,
I'd appreciate knowing what it says for 'VID' and 'PID.'
Additional adapters include: the D-Link DSB-650 and DSB-650TX, the
SMC 2102USB, 2104USB and 2202USB, the ATen UC10T, and the Netgear EA101.
These are all mentioned in the man pages, relnotes and LINT.
Also correct the date in the kue(4) man page. I wrote this thing
on Jan, 4 2000, not 1999.
2000-01-07 22:18:49 +00:00
|
|
|
/* D-Link products */
|
|
|
|
|
product DLINK DSB650C 0x4000 10Mbps ethernet adapter
|
|
|
|
|
product DLINK DSB650TX 0x4002 10/100 ethernet adapter
|
|
|
|
|
product DLINK DSB650TX_PNA 0x4003 1/10/100 ethernet adapter
|
|
|
|
|
|
1999-11-18 18:02:44 +00:00
|
|
|
/* Intel products */
|
|
|
|
|
product INTEL TESTBOARD 0x9890 82930 test board
|
