2001-04-27 21:28:02 +00:00
|
|
|
<!--
|
|
|
|
|
|
|
|
|
|
The "Supported Devices" section of the release notes.
|
|
|
|
|
Generally processor-independent, with conditional text
|
|
|
|
|
inclusion handling any architecture-dependent text.
|
|
|
|
|
|
|
|
|
|
Within each subsection describing a class of hardware
|
|
|
|
|
(i.e. Ethernet interfaces), list broad groups of devices
|
|
|
|
|
alphabetically as paragraphs sorted alphabetically (frequently
|
|
|
|
|
these groups will be arranged by manufacturer, i.e. 3Com
|
|
|
|
|
Ethernet interfaces). In cases where a group of devices
|
|
|
|
|
consists of multiple models (such as the 3C501, 3C503, etc.),
|
|
|
|
|
least each specific model or set of closely-related models as
|
|
|
|
|
a separate item in an itemized list, sorted alphabetically.
|
|
|
|
|
Where applicable, a "Miscellaneous" section may follow all
|
|
|
|
|
other named sections.
|
|
|
|
|
|
|
|
|
|
These guidelines are not hard-and-fast rules, and exceptions
|
|
|
|
|
will occur. Following these guidelines (vague as they may be)
|
|
|
|
|
is highly recommendations to try to keep the formatting of
|
|
|
|
|
this section consistent.
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
We give manpage references using the &man entities where
|
|
|
|
|
possible. If a driver has no manpage (and consequently no
|
|
|
|
|
&man entity, we simply give the name of the driver).
|
|
|
|
|
Please avoid doing &man entity conversions unless you
|
|
|
|
|
know for sure that an entity and manpage exist; sweeps through
|
|
|
|
|
this file to fix "missed" conversions are likely to break the
|
|
|
|
|
build.
|
2001-04-27 21:28:02 +00:00
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
<sect1>
|
2001-05-14 22:31:51 +00:00
|
|
|
<sect1info>
|
|
|
|
|
<pubdate>$FreeBSD$</pubdate>
|
|
|
|
|
</sect1info>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<title>Supported Devices</title>
|
|
|
|
|
|
|
|
|
|
<para>This section describes the devices currently known to be
|
2001-10-24 16:01:40 +00:00
|
|
|
supported by with &os; on the &arch.print; platform. Other configurations
|
2001-04-27 21:28:02 +00:00
|
|
|
may also work, but simply have not been tested yet. Feedback,
|
|
|
|
|
updates, and corrections to this list are encouraged.</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Where possible, the drivers applicable to each device or class
|
|
|
|
|
of devices is listed. If the driver in question has a manual page
|
|
|
|
|
in the &os; base distribution (most should), it is referenced here.</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<sect2>
|
|
|
|
|
<title>Disk Controllers</title>
|
2001-10-19 20:56:31 +00:00
|
|
|
<para arch="i386,alpha,sparc64,ia64">IDE/ATA controllers (&man.ata.4 driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Acerlabs Aladdin</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-10-05 23:52:15 +00:00
|
|
|
<para>AMD 756, 766</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CMD 646, 648 ATA66, and 649 ATA100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Cypress 82C693</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Cyrex 5530</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HighPoint HPT366, HPT370</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel PIIX, PIIX3, PIIX4</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel ICH, ICH2</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Promise ATA100 OEM chip (pdc20265)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-10-05 23:52:15 +00:00
|
|
|
<para>Promise Fasttrak-33, -66, -100, -100 TX2/TX4</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Promise Ultra-33, -66, -100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ServerWorks ROSB4 ATA33</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SiS 5591</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>VIA 82C586, 82C686a, 82C686b</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Adaptec SCSI Controllers
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Adaptec 1535 ISA SCSI controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Adaptec 154x series ISA SCSI controllers
|
|
|
|
|
(&man.aha.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Adaptec 164x series MCA SCSI controllers (&man.aha.4;
|
|
|
|
|
driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Adaptec 174x series EISA SCSI controller in standard
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
and enhanced mode (&man.aha.4; and &man.ahb.4; dirver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Adaptec 19160/274x/284x/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x
|
|
|
|
|
series EISA/VLB/PCI SCSI controllers, including
|
|
|
|
|
Narrow/Wide/Twin/Ultra/Ultra2 variants (&man.ahc.4;
|
|
|
|
|
driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, AIC7880,
|
|
|
|
|
and AIC789x on-board
|
|
|
|
|
SCSI controllers (&man.ahc.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Adaptec 1510 series ISA SCSI controllers (not for
|
|
|
|
|
bootable devices)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Adaptec 152x series ISA SCSI controllers (&man.aha.4;
|
|
|
|
|
driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Adaptec AIC-6260 and AIC-6360 based boards, which
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
includes the AHA-152x and SoundBlaster SCSI cards
|
|
|
|
|
(&man.aic.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-08-30 21:37:09 +00:00
|
|
|
<para arch="i386">Adaptec 2100S/32x0S/34x0S SCSI RAID
|
2001-04-27 21:28:02 +00:00
|
|
|
controllers (&man.asr.4; driver)</para>
|
|
|
|
|
|
2001-08-30 21:37:09 +00:00
|
|
|
<para arch="i386">Adaptec 2000S/2005S Zero-Channel RAID controllers
|
|
|
|
|
(&man.asr.4; driver)</para>
|
|
|
|
|
|
2001-05-09 05:56:49 +00:00
|
|
|
<para arch="i386">Adaptec 2400A ATA-100 RAID controller
|
|
|
|
|
(&man.asr.4; driver)</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para arch="i386">Adaptec FSA family RAID controllers (&man.aac.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Adaptec AAC-2622</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Adaptec AAC-364</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-30 21:37:09 +00:00
|
|
|
<para>Adaptec SCSI RAID 5400S</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 2/QC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 2/Si</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 3/Di</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 3/QC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 3/Si</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HP NetRAID-4M</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>AdvanSys SCSI controllers (all models, &man.adv.4; and
|
|
|
|
|
&man.adw.4; drivers)</para>
|
|
|
|
|
|
|
|
|
|
<para>BusLogic MultiMaster <quote>W</quote> Series Host Adapters
|
|
|
|
|
(&man.bt.4; driver):
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-948</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-958</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-958D</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>BusLogic MultiMaster <quote>C</quote> Series Host Adapters
|
|
|
|
|
(&man.bt.4; driver):
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-946C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-956C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-956CD</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-445C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-747C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-757C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-757CD</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-545C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-540CF</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>BusLogic MultiMaster <quote>S</quote> Series Host Adapters
|
|
|
|
|
(&man.bt.4; driver):
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-445S</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-747S</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-747D</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-757S</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-757D</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-545S</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-542D</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-742A</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-542B</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>BusLogic MultiMaster <quote>A</quote> Series Host Adapters
|
|
|
|
|
(&man.bt.4; driver):
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-742A</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BT-542B</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<note>
|
|
|
|
|
<para>BusLogic/Mylex <quote>Flashpoint</quote> adapters are not yet
|
|
|
|
|
supported.</para>
|
|
|
|
|
</note>
|
|
|
|
|
<note>
|
|
|
|
|
<para>AMI FastDisk controllers that are true BusLogic
|
|
|
|
|
MultiMaster clones are also supported.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<note arch="i386">
|
|
|
|
|
<para>The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B
|
|
|
|
|
and SDC3211F Microchannel (MCA) bus adapters are also
|
|
|
|
|
supported.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<para>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
|
|
|
|
|
SmartRAID IV SCSI/RAID controllers (&man.dpt.4; driver)</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">DPT SmartRAID V and VI SCSI RAID controllers
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
(&man.asr.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM1554</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM2554</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM2654</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM2865</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM2754</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM3755</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PM3757</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>AMI MegaRAID Express and Enterprise family RAID controllers
|
|
|
|
|
(&man.amr.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Series 418</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Enterprise 1200 (Series 428)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Enterprise 1300 (Series 434)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Enterprise 1400 (Series 438)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Enterprise 1500 (Series 467)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Enterprise 1600 (Series 471)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Elite 1500 (Series 467)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Elite 1600 (Series 493)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Express 100 (Series 466WS)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Express 200 (Series 466)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Express 300 (Series 490)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MegaRAID Express 500 (Series 475)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 2/SC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 2/DC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Dell PERC 3/DCL</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HP NetRaid-1si</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HP NetRaid-3si</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HP Embedded NetRaid</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<note arch="i386">
|
|
|
|
|
<para>Booting from these controllers is supported. EISA
|
|
|
|
|
adapters are not supported.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<note arch="alpha">
|
|
|
|
|
<para>Booting from these controllers is not supported due to SRM
|
|
|
|
|
limitations.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<para>Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x
|
|
|
|
|
and 5.x firmware (&man.mlx.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960P</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960PD</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960PDU</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960PL</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960PJ</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DAC960PG</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AcceleRAID 150</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AcceleRAID 250</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>eXtremeRAID 1100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<note>
|
|
|
|
|
<para>Booting from these controllers is supported. EISA adapters
|
|
|
|
|
are not supported.</para>
|
|
|
|
|
|
|
|
|
|
<para arch="alpha">Booting from these controllers is not
|
|
|
|
|
supported due to SRM limitations. This list includes
|
|
|
|
|
controllers sold by Digital/Compaq in Alpha systems in the
|
|
|
|
|
StorageWorks family, e.g. KZPSC or KZPAC.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">Mylex PCI to SCSI RAID controllers with 6.x firmware
|
|
|
|
|
(&man.mly.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AcceleRAID 160</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AcceleRAID 170</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AcceleRAID 352</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>eXtremeRAID 2000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>eXtremeRAID 3000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<note>
|
|
|
|
|
<para>Compatible Mylex controllers not listed should work, but
|
|
|
|
|
have not been verified.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
|
|
|
|
<para>3ware Escalade ATA RAID controllers (&man.twe.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>5000 series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>6000 series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>7000 series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825,
|
|
|
|
|
53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, 53C895, 53C895a,
|
|
|
|
|
53C896, 53C1010-33, 53C1010-66, 53C1000, 53C1000R PCI
|
|
|
|
|
SCSI controllers, either embedded on motherboard or on add-on
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
boards (&man.ncr.4; and &man.sym.4; drivers)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ASUS SC-200, SC-896</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Data Technology DTC3130 (all variants)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DawiControl DC2976UW</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Diamond FirePort (all)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NCR cards (all)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Symbios cards (all)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and
|
|
|
|
|
390U3W</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Tyan S1365</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">NCR 53C500 based PC-Card SCSI host adapters (ncv
|
|
|
|
|
driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IO DATA PCSC-DV</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Macnica Miracle SCSI-II mPS110</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Media Intelligent MSC-110, MSC-200</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC PC-9801N-J03R</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>New Media Corporation BASICS SCSI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic Fast SCSI</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RATOC REX-9530, REX-5572 (as SCSI only)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">TMC 18C30, 18C50 based ISA/PC-Card SCSI host
|
|
|
|
|
adapters (stg driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Future Domain SCSI2GO</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IBM SCSI PCMCIA Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ICM PSC-2401 SCSI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco IFC-SC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RATOC REX-5536, REX-5536AM, REX-5536M,
|
|
|
|
|
REX-9836A</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-10-19 20:56:31 +00:00
|
|
|
<para arch="i386,alpha,ia64">QLogic controllers and variants (&man.isp.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic 1020, 1040 SCSI and Ultra SCSI host
|
2001-04-27 21:28:02 +00:00
|
|
|
adapters</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic 1240 dual Ultra SCSI controllers</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD
|
2001-04-27 21:28:02 +00:00
|
|
|
controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic 12160 Ultra3 LVD controllers</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-08-31 21:50:09 +00:00
|
|
|
<para>QLogic 2100 and QLogic 2200 Fibre Channel SCSI
|
|
|
|
|
controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>QLogic 2300 and QLogic 2312 2-Gigabit Fibre Channel SCSI
|
2001-04-27 21:28:02 +00:00
|
|
|
controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Performance Technology SBS440 ISP1000 variants</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Performance Technology SBS450 ISP1040 variants</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Performance Technology SBS470 ISP2100 variants</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Antares Microsystems P-0033 ISP2100 variants</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">DTC 3290 EISA SCSI controller in 1542 emulation mode.</para>
|
|
|
|
|
|
|
|
|
|
<para>Tekram DC390 and DC390T controllers, maybe other cards based
|
|
|
|
|
on the AMD 53c974 as well (&man.amd.4; driver)</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Workbit Ninja SCSI-3 based PC-Card SCSI host
|
|
|
|
|
adapters (nsp driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Alpha-Data AD-PCS201</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IO DATA CBSC16</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Parallel to SCSI interfaces (&man.vpo.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AIC 7110 SCSI controller (built-in to Iomega ZIP drive)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Iomega Jaz Traveller interface</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Iomega MatchMaker SCSI interface (built-in to Iomega
|
|
|
|
|
ZIP+ drive)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>With all supported SCSI controllers, full support is
|
|
|
|
|
provided for SCSI-I, SCSI-II, and SCSI-III peripherals, including
|
|
|
|
|
hard disks, optical disks, tape drives (including DAT, 8mm
|
|
|
|
|
Exabyte, Mammoth, and DLT), medium changers, processor target
|
|
|
|
|
devices and CD-ROM drives. WORM devices that support CD-ROM
|
|
|
|
|
commands are supported for read-only access by the CD-ROM drivers
|
|
|
|
|
(such as &man.cd.4;). WORM/CD-R/CD-RW writing support is provided
|
2001-08-17 15:16:12 +00:00
|
|
|
by &man.cdrecord.1;, which is a part of the
|
|
|
|
|
<port>sysutils/cdrtools</port> port in the Ports Collection.</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
|
|
|
|
<para>The following CD-ROM type systems are supported at this
|
|
|
|
|
time:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SCSI interface (also includes ProAudio Spectrum and
|
|
|
|
|
SoundBlaster SCSI) (&man.cd.4;)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Matsushita/Panasonic (Creative SoundBlaster)
|
|
|
|
|
proprietary interface (562/563 models) (&man.matcd.4;)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Sony proprietary interface (all models) (&man.scd.4;)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ATAPI IDE interface (&man.acd.4;)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">The following drivers were supported under the old SCSI
|
|
|
|
|
subsystem, but are not yet supported under the new CAM SCSI
|
|
|
|
|
subsystem:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NCR5380/NCR53400 (<quote>ProAudio Spectrum</quote>)
|
|
|
|
|
SCSI controller</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>UltraStor 14F, 24F and 34F SCSI controllers.
|
|
|
|
|
<note>
|
|
|
|
|
<para>There is work-in-progress to port the
|
|
|
|
|
UltraStor driver to the new CAM SCSI framework, but no
|
|
|
|
|
estimates on when or if it will be completed.</para>
|
|
|
|
|
</note>
|
|
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Seagate ST01/02 SCSI controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Future Domain 8xx/950 series SCSI controllers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>WD7000 SCSI controller</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">The following device is unmaintained:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Mitsumi proprietary CD-ROM interface (all
|
|
|
|
|
models) (&man.mcd.4;)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
<sect2 id="ethernet">
|
|
|
|
|
<title>Ethernet Interfaces</title>
|
|
|
|
|
|
|
|
|
|
<para>Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec
|
|
|
|
|
AIC-6915 Fast Ethernet controller chip (&man.sf.4 driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ANA-62011 64-bit single port 10/100baseTX adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ANA-62022 64-bit dual port 10/100baseTX adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ANA-62044 64-bit quad port 10/100baseTX adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ANA-69011 32-bit single port 10/100baseTX
|
|
|
|
|
adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ANA-62020 64-bit single port 100baseFX adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Allied-Telesis AT1700 and RE2000 cards
|
|
|
|
|
(&man.fe.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
|
|
|
|
<para>Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon
|
|
|
|
|
1 and Tigon 2 chipsets (&man.ti.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3c985-SX (Tigon 1 and 2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Alteon AceNIC (Tigon 1 and 2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Alteon AceNIC 1000baseT (Tigon 2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Asante PCI 1000BASE-SX Gigabit Ethernet Adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Asante GigaNIX1000T Gigabit Ethernet Adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DEC/Compaq EtherWORKS 1000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Farallon PN9000SX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC Gigabit Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netgear GA620 (Tigon 2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netgear GA620T (Tigon 2, 1000baseT)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Silicon Graphics Gigabit Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>AMD PCnet NICs (&man.lnc.4; and &man.pcn.4; drivers)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AMD PCnet/PCI (79c970 & 53c974 or 79c974)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AMD PCnet/FAST</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PCnet/FAST+</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PCnet/FAST III</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PCnet/PRO</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PCnet/Home</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HomePNA</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-06-22 21:43:14 +00:00
|
|
|
<para arch="i386">SMC 83c17x (EPIC)-based Ethernet NICs (&man.tx.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC EtherPower II 9432 series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
|
|
|
|
|
<para arch="i386">SMC Ethernet NICs (&man.ed.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Elite 16 WD8013 Ethernet interface</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Most WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S,
|
|
|
|
|
WD8003SBT and WD8013EBT based clones</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC Elite Ultra</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">RealTek RTL 8002 Pocket Ethernet (&man.rdp.4;
|
|
|
|
|
driver)</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>RealTek 8129/8139 Fast Ethernet NICs (&man.rl.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Accton <quote>Cheetah</quote> EN1207D (MPX 5030/5038;
|
|
|
|
|
RealTek 8139 clone)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Allied Telesyn AT2550</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Allied Telesyn AT2500TX</para>
|
|
|
|
|
</listitem>
|
2001-07-23 19:11:33 +00:00
|
|
|
<listitem>
|
2001-07-23 23:35:31 +00:00
|
|
|
<para>D-Link DFE-538TX</para>
|
2001-07-23 19:11:33 +00:00
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Genius GF100TXR (RTL8139)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>KTX-9130TX 10/100 Fast Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NDC Communications NE100TX-E</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netronix Inc. EA-1210 NetEther 10/100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>OvisLink LEF-8129TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>OvisLink LEF-8139TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC EZ Card 10/100 PCI 1211-TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Kingston KNE110TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys EtherFast LNE100TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Matrox FastNIC 10/100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NetGear FA310-TX Rev. D1</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast
|
|
|
|
|
Ethernet NICs (&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Accton EN1217 (98715A)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Adico AE310TX (98715A)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compex RL100-TX (98713 or 98713A)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CNet Pro120A (98713 or 98713A)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CNet Pro120B (98715)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NDC Communications SFA100A (98713A)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SVEC PN102TX (98713)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs
|
|
|
|
|
(&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys EtherFast LNE100TX Version 2</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Winbond W89C840F Fast Ethernet NICs (&man.wb.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Trendware TE100-PCIE</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>VIA Technologies VT3043 <quote>Rhine I</quote> and VT86C100A
|
|
|
|
|
<quote>Rhine II</quote> Fast Ethernet NICs (&man.vr.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AOpen/Acer ALN-320</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DFE-530TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Hawking Technologies PN102TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast
|
|
|
|
|
Ethernet NICs (&man.sis.4; driver)</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>National Semiconductor DP83815 Fast Ethernet NICs
|
|
|
|
|
(&man.sis.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NetGear FA311-TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NetGear FA312-TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-05-12 04:19:26 +00:00
|
|
|
<para>National Semiconductor DP83820 and DP83821 Gigabit Ethernet
|
|
|
|
|
NICs (&man.nge.4 driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Addtron AEG320T</para>
|
|
|
|
|
</listitem>
|
2001-09-14 15:34:06 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T
|
|
|
|
|
(64-bit PCI)</para>
|
|
|
|
|
</listitem>
|
2001-05-12 04:19:26 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DGE-500T</para>
|
|
|
|
|
</listitem>
|
2001-07-12 18:42:41 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit PCI)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netgear GA622T</para>
|
|
|
|
|
</listitem>
|
2001-05-12 04:19:26 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>SMC EZ Card 1000 (SMC9462TX)</para>
|
|
|
|
|
</listitem>
|
2001-07-12 18:42:41 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Surecom Technology EP-320G-TX</para>
|
|
|
|
|
</listitem>
|
2001-09-14 15:34:06 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2
|
|
|
|
|
(64-bit PCI)</para>
|
|
|
|
|
</listitem>
|
2001-05-12 04:19:26 +00:00
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Sundance Technologies ST201 PCI Fast Ethernet NICs
|
|
|
|
|
(&man.ste.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DFE-550TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>SysKonnect SK-984x PCI Gigabit Ethernet cards (&man.sk.4 drivers)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SK-9821 1000baseT copper, single port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SK-9822 1000baseT copper, dual port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SK-9841 1000baseLX single mode fiber, single port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-04-30 16:06:46 +00:00
|
|
|
<para>SK-9842 1000baseLX single mode fiber, dual port</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-04-30 16:06:46 +00:00
|
|
|
<para>SK-9843 1000baseSX multimode fiber, single port</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SK-9844 1000baseSX multimode fiber, dual port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Texas Instruments ThunderLAN PCI NICs (&man.tl.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100
|
|
|
|
|
Dual-Port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI
|
|
|
|
|
UTP/Coax, 10/100 TX UTP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Racore 8165 10/100baseTX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Racore 8148 10baseT/100baseTX/100baseFX
|
|
|
|
|
multi-personality</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (&man.dc.4;
|
|
|
|
|
driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (&man.dc.4;
|
|
|
|
|
driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys EtherFast LNE100TX v4.0/4.1</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>ADMtek Inc. AN986-based USB Ethernet NICs (&man.aue.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Billionton USB100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DSB-650TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys USB100TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco Inc. LUA-TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC 2202USB</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>CATC USB-EL1210A-based USB Ethernet NICs (&man.cue.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Belkin F5U011</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Belkin F5U111</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CATC Netmate</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CATC Netmate II</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs
|
|
|
|
|
(&man.kue.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3c19250</para>
|
|
|
|
|
</listitem>
|
2001-05-17 18:32:18 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Abocom URE 450</para>
|
|
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>ADS Technologies USB-10BT</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ATen UC10T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Corega USB-T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DSB-650</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Entrega NET-USB-E45</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys USB10T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netgear EA101</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Peracom USB Ethernet Adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC 2102USB</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC 2104USB</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>ASIX Electronics AX88140A PCI NICs (&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Alfa Inc. GFC2204</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CNet Pro110B</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">DEC EtherWORKS II NICs (DE200, DE201, DE202, and
|
2001-04-27 21:28:02 +00:00
|
|
|
DE422) (&man.le.4; driver)</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">DEC EtherWORKS III NICs (DE203, DE204, and DE205)
|
2001-04-27 21:28:02 +00:00
|
|
|
(&man.le.4; driver)</para>
|
|
|
|
|
|
2001-06-22 17:26:02 +00:00
|
|
|
<para arch="i386">DEC Etherworks NICs (DE305) (&man.ed.4; driver)</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143
|
|
|
|
|
based NICs (&man.de.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Asante</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Cogent EM100FX and EM440TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DEC DE425, DE435, DE450, and DE500</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC Etherpower 8432T, 9332, and 9334</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ZYNX ZX 3xx</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>DEC/Intel 21143 based Fast Ethernet NICs (&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DEC DE500-BA</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq Presario 7900 series built-in Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DFE-570TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Kingston KNE100TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Davicom DM9100 and DM9102 PCI Fast Ethernet NICs (&man.dc.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Jaton Corporation XpressNet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Fujitsu MB86960A/MB86965A based Fast Ethernet NICs
|
2001-04-27 21:28:02 +00:00
|
|
|
(&man.fe.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CONTEC C-NET(PC)C Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Eiger Labs EPX-10BT</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303
|
|
|
|
|
Ethernet PCMCIA</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Fujitsu Towa LA501 Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HITACHI HT-4840-11</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NextCom J Link NC5310</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RATOC REX-5588, REX-9822, REX-4886, REX-R280</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">HP PC Lan+ cards (model numbers: 27247B and 27252A)
|
|
|
|
|
(&man.ed.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
|
|
|
|
<para>Intel EtherExpress NICs
|
|
|
|
|
<itemizedlist>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Intel EtherExpress 16 (&man.ie.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Intel EtherExpress Pro/10 and Pro/10+ Ethernet
|
|
|
|
|
(&man.ex.4; driver)</para>
|
|
|
|
|
</listitem>
|
2001-10-19 20:56:31 +00:00
|
|
|
<listitem arch="i386,alpha,ia64">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Intel EtherExpress Pro/100B PCI Fast Ethernet
|
|
|
|
|
(&man.fxp.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel InBusiness 10/100 PCI Network Adapter
|
|
|
|
|
(&man.fxp.4 driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel PRO/100+ Management Adapter (&man.fxp.4 driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<!-- XXX ie.4 cards that are not 3C507 or EtherExpress 16 XXX -->
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Isolan AT 4141-0 (16 bit)</para>
|
|
|
|
|
|
|
|
|
|
<para>Isolink 4110 (8 bit)</para>
|
|
|
|
|
|
|
|
|
|
<para>Novell NE1000, NE2000, and NE2100 Ethernet interface
|
|
|
|
|
(&man.ed.4; driver)</para>
|
|
|
|
|
|
|
|
|
|
<para>Novell NE2000 clones (&man.ed.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NetVin 5000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RealTek 8029</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Surecom NE-34</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>VIA VT86C926</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Winbond W89C940</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>3Com Ethernet and Fast Ethernet NICs
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>3C450-TX HomeConnect adapter (&man.xl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>3C501 (&man.el.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3C503 Etherlink II (&man.ed.4; driver)</para>
|
|
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>3C507 Etherlink 16/TP (&man.ie.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>3C509 (&man.ep.4; driver)</para>
|
|
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>3C529 MCA (&man.ep.4; driver)</para>
|
|
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>3C579 EISA (&man.ep.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3C589/589B/589C/589D/589E/XE589ET/574TX/574B
|
|
|
|
|
PC-card/PCMCIA (&man.ep.4; driver)</para>
|
|
|
|
|
</listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<listitem arch="i386">
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>3C590/592/595 (&man.vx.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>3C900/905/905B/905C PCI (&man.xl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>3C556/556B MiniPCI (&man.xl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3C575TX/575B/XFE575BT/575C/656/656B/656C (Cardbus)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>EISA (Fast) Etherlink III / (Fast) Etherlink XL</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>3c980/3c980B Fast Etherlink XL server adapter
|
|
|
|
|
(&man.xl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>3cSOHO100-TX OfficeConnect adapter (&man.xl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Crystal Semiconductor CS89x0-based NICs
|
|
|
|
|
(&man.cs.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IBM Etherjet ISA</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">NE2000 compatible PC-Card (PCMCIA) Ethernet and
|
|
|
|
|
FastEthernet cards (&man.ed.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AR-P500 Ethernet card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Accton EN2212/EN2216/UE2216(OEM)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Allied Telesis CentreCOM LA100-PCM_V2</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AmbiCom 10BaseT card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BayNetworks NETGEAR FA410TXC Fast Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CNet BC40 adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compex Net-A adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CyQ've ELA-010</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>D-Link DE-650/660</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Danpex EN-6200P2</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Elecom Laneed LD-CDL/TX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IO DATA PCLATE</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IBM Creditcard Ethernet I/II</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IC-CARD Ethernet/IC-CARD+ Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card
|
|
|
|
|
(PCMPC100 V2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NDC Ethernet Instant-Link</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>National Semiconductor InfoMover NE4100</para>
|
|
|
|
|
</listitem>
|
2001-07-26 04:40:58 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>NetGear FA-410TX</para>
|
|
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Network Everywhere Ethernet 10BaseT PC Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Planex FNW-3600-T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Socket LP-E</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Surecom EtherPerfect EP-427</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Telecom Device SuperSocket RE450T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Megahertz X-Jack Ethernet PC-Card CC-10BT (sn
|
|
|
|
|
driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
|
|
|
|
<para arch="i386">Xircom X3201 (Cardbus) based Ethernet cards, including the following:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>IBM EtherJet Cardbus Adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel PRO/100 Mobile Cardbus (versions that use the
|
|
|
|
|
X3201 chipset)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom Cardbus Realport</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom Cardbus Ethernet 10/100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom Cardbus Ethernet II 10/100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Xircom CreditCard adapters (16 bit) and
|
|
|
|
|
workalikes (xe driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Accton EN2226/Fast EtherCard (16-bit verison)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq Netelligent 10/100 PC Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel EtherExpress PRO/100 Mobile Adapter (16-bit
|
|
|
|
|
verison)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom 10/100 Network PC Card adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom Realport card + modem(Ethernet part)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom CreditCard Ethernet 10/100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom CreditCard 10Base-T <quote>CreditCard Ethernet
|
|
|
|
|
Adapter IIps</quote> (PS-CE2-10)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Xircom CreditCard Ethernet 10/100 + modem (Ethernet
|
|
|
|
|
part)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">National Semiconductor DP8393X (SONIC) Ethernet
|
|
|
|
|
cards (snc driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC PC-9801-83, -84, -103, and -104</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC PC-9801N-25 and -J02R</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-08-24 00:30:50 +00:00
|
|
|
<para>Gigabit Ethernet cards based on the Level 1
|
2001-06-01 16:29:21 +00:00
|
|
|
LXT1001 NetCellerator controller (&man.lge.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
2001-07-23 19:11:33 +00:00
|
|
|
<para>D-Link DGE-500SX</para>
|
2001-06-01 16:29:21 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SMC TigerCard 1000 (SMC9462SX)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-07-30 18:28:27 +00:00
|
|
|
<para>Ethernet and Fast Ethernet NICs based on the 3Com
|
2001-07-24 01:14:00 +00:00
|
|
|
3XP Typhoon/Sidewinder (3CR990) chipset (&man.txp.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990-TX-95</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990-TX-97</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990B-SRV</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990B-TXM</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990SVR95</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3CR990SVR97</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-09-28 00:45:31 +00:00
|
|
|
<para>Gigabit Ethernet NICs based on the Broadcom BCM570x
|
2001-10-19 15:01:54 +00:00
|
|
|
(&man.bge.4; driver)
|
2001-09-28 00:45:31 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 3c996-T</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SysKonnect SK-9D21 and 9D41</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Built-in Gigabit Ethernet NICs on DELL PowerEdge 2550
|
|
|
|
|
servers</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
2001-10-19 15:01:54 +00:00
|
|
|
|
|
|
|
|
<para>Gigabit Ethernet NICs based on the Intel 82542 and 82543
|
|
|
|
|
controller chips (&man.gx.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel PRO/1000 Gigabit Ethernet</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>FDDI Interfaces</title>
|
|
|
|
|
<para>DEC DEFPA/DEFEA FDDI NICs (&man.fpa.4; driver)</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>ATM Interfaces</title>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Efficient Networks, Inc. ENI-155p ATM PCI Adapters
|
|
|
|
|
(hea driver)</para>
|
|
|
|
|
<para>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>The ATM support in &os; supports the following signaling
|
|
|
|
|
protocols:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>The ATM Forum UNI 3.1 signaling protocol</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>The ATM Forum UNI 3.0 signaling protocol</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>The ATM Forum ILMI address registration</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>FORE Systems' proprietary SPANS signaling protocol</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Permanent Virtual Channels (PVCs)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Support for the IETF <quote>Classical IP and ARP over
|
|
|
|
|
ATM</quote> model is provided, compliant with the following RFCs
|
|
|
|
|
and Internet Drafts:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 1483, <quote>Multiprotocol Encapsulation over ATM
|
|
|
|
|
Adaptation Layer 5</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 1577, <quote>Classical IP and ARP over ATM</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 1626, <quote>Default IP MTU for use over ATM
|
|
|
|
|
AAL5</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 1755, <quote>ATM Signaling Support for IP over ATM</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 2225, <quote>Classical IP and ARP over ATM</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>RFC 2334, <quote>Server Cache Synchronization Protocol
|
|
|
|
|
(SCSP)</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Internet Draft
|
|
|
|
|
<filename>draft-ietf-ion-scsp-atmarp-00.txt</filename>, <quote>A
|
|
|
|
|
Distributed ATMARP Service Using SCSP</quote></para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Support for an ATM sockets interface is also provided.</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>Wireless Network Interfaces</title>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">NCR / AT&T / Lucent Technologies WaveLan T1-speed
|
|
|
|
|
ISA/radio LAN cards (&man.wl.4; driver)</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA
|
2001-04-27 21:28:02 +00:00
|
|
|
standard speed (2Mbps) and turbo speed (6Mbps) wireless network
|
|
|
|
|
adapters and workalikes (&man.wi.4; driver)
|
|
|
|
|
<note>
|
|
|
|
|
<para>The ISA versions of these adapters are actually PCMCIA
|
|
|
|
|
cards combined with an ISA to PCMCIA bridge card, so both kinds
|
|
|
|
|
of devices work with the same driver.</para>
|
|
|
|
|
</note>
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NCR WaveLAN/IEEE 802.11</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-05-10 23:38:32 +00:00
|
|
|
<para>3COM 3crwe737A AirConnect Wireless LAN PC Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Addtron AWA100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Cabletron RoamAbout 802.11 DS</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Compaq WL100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Corega KK Wireless LAN PCC-11</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ELECOM Air@Hawk/LD-WL11/PCC</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Farallon Skyline 11Mbps Wireless</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ICOM SL-1100</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Laneed Wireless card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco Airconnect WLI-PCM-L11</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC Wireless Card CMZ-RT-WP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PLANEX GeoWave/GW-NS110</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>TDK LAK-CD011WL</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Aironet 802.11 wireless adapters (&man.an.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Aironet 4500/4800 series
|
|
|
|
|
(PCMCIA, PCI, and ISA adapters are all supported)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-07-02 16:56:12 +00:00
|
|
|
<para>Cisco Systems Aironet 340 and 350 series
|
|
|
|
|
(PCMCIA, PCI, and ISA adapters are all supported)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">Raytheon Raylink 2.4GHz wireless adapters (&man.ray.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Webgear Aviator</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Webgear Aviator Pro</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Raylink PC Card</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-05-18 00:41:10 +00:00
|
|
|
<para>AMD Am79C930 and Harris (Intersil) based 802.11 cards (awi driver)
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BayStack 650 and 660</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Farallon SkyLINE Wireless</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Icom SL-200</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco WLI-PCM</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEL SSMagic</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Netwave AirSurfer Plus and AirSurfer Pro</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ZoomAir 4000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2 arch="i386">
|
|
|
|
|
<title>ISDN Interfaces</title>
|
|
|
|
|
<para>AcerISDN P10 ISA PnP (experimental)</para>
|
|
|
|
|
<para>Asuscom ISDNlink 128K ISA</para>
|
2001-05-25 17:25:47 +00:00
|
|
|
<para>ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>AVM
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>A1</para>
|
|
|
|
|
</listitem>
|
2001-05-25 17:25:47 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>B1 ISA (tested with V2.0)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>B1 PCI (tested with V4.0)</para>
|
|
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>Fritz!Card classic</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Fritz!Card PnP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Fritz!Card PCI</para>
|
|
|
|
|
</listitem>
|
2001-05-25 17:25:47 +00:00
|
|
|
<listitem>
|
|
|
|
|
<para>T1</para>
|
|
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Creatix
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ISDN-S0</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ISDN-S0 P&P</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Dr. Neuhaus Niccy Go@ and compatibles</para>
|
|
|
|
|
<para>Dynalink IS64PH</para>
|
2001-05-25 17:25:47 +00:00
|
|
|
<para>Eicon Diehl DIVA 2.0 and 2.02</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>ELSA
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ELSA PCC-16</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>QuickStep 1000pro ISA</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MicroLink ISDN/PCI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>QuickStep 1000pro PCI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>ITK ix1 Micro ( < V.3, non-PnP version )</para>
|
|
|
|
|
<para>Sedlbauer Win Speed</para>
|
|
|
|
|
<para>Siemens I-Surf 2.0</para>
|
|
|
|
|
<para>TELEINT ISDN SPEED No.1 (experimental)</para>
|
|
|
|
|
<para>Teles
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>S0/8</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>S0/16</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>S0/16.3</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>S0/16.3 PnP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>16.3c ISA PnP (experimental)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Teles PCI-TJ</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Traverse Technologies NETjet-S PCI</para>
|
|
|
|
|
<para>USRobotics Sportster ISDN TA intern</para>
|
|
|
|
|
<para>Winbond W6692 based PCI cards</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>Multi-port Serial Interfaces</title>
|
|
|
|
|
<para>AST 4 port serial card using shared IRQ</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">ARNET serial cards (&man.ar.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ARNET 8 port serial card using shared IRQ</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ARNET (now Digiboard) Sync 570/i high-speed serial</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Boca multi-port serial cards
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Boca BB1004 4-Port serial card (Modems
|
|
|
|
|
<emphasis>not</emphasis> supported)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Boca IOAT66 6-Port serial card (Modems supported)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Boca BB1008 8-Port serial card (Modems
|
|
|
|
|
<emphasis>not</emphasis> supported)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Boca BB2016 16-Port serial card (Modems supported)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Comtrol Rocketport card (rp driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Cyclades Cyclom-y serial board (&man.cy.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
|
|
|
|
|
<para>STB 4 port card using shared IRQ</para>
|
|
|
|
|
|
|
|
|
|
<para>DigiBoard intelligent serial cards (&man.dgb.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DigiBoard PC/Xe series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DigiBoard PC/Xi series</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">SDL Communication serial boards
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>SDL Communications Riscom/8 Serial Board (rc driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SDL Communications RISCom/N2 and N2pci high-speed sync
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
serial boards (&man.sr.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Stallion Technologies multiport serial boards
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>EasyIO (&man.stl.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>EasyConnection 8/32 (&man.stl.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>EasyConnection 8/64 (&man.stli.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>ONboard 4/16 (&man.stli.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Brumby (&man.stli.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Specialix SI/XIO/SX multiport serial cards, with both the
|
|
|
|
|
older SIHOST2.x and the new <quote>enhanced</quote> (transputer
|
|
|
|
|
based, aka JET) host cards (ISA, EISA and PCI are supported)
|
|
|
|
|
(&man.si.4; driver)</para>
|
|
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>Audio Devices</title>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Advance (&man.sbc.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Asound 100 and 110</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Logic ALS120 and ALS4000</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>CMedia sound chips
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CMI8338/CMI8738</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Crystal Semiconductor (&man.csa.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CS461x/462x Audio Accelerator</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CS428x Audio Controller</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>ENSONIQ (&man.pcm.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AudioPCI ES1370/1371</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>ESS
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>ES1868, ES1869, ES1879 and ES1888 (&man.sbc.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Maestro-1, Maestro-2, and Maestro-2E</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Maestro-3/Allegro</para>
|
|
|
|
|
<note>
|
|
|
|
|
<para>The Maestro-3/Allegro cannot be compiled into the
|
2001-09-21 03:06:46 +00:00
|
|
|
&os; kernel due to licensing restrictions. To use this driver, add
|
2001-04-27 21:28:02 +00:00
|
|
|
the following line to
|
|
|
|
|
<filename>/boot/loader.conf</filename>:</para>
|
|
|
|
|
|
2001-09-29 02:56:11 +00:00
|
|
|
<screen><userinput>snd_maestro3_load="YES"</userinput></screen>
|
2001-04-27 21:28:02 +00:00
|
|
|
</note>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>ForteMedia fm801</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Gravis (&man.gusc.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>UltraSound MAX</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>UltraSound PnP</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
2001-07-03 08:19:06 +00:00
|
|
|
<para arch="i386">Intel 443MX, 810, 815, and 815E integrated sound
|
|
|
|
|
devices (&man.pcm.4; driver)</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>MSS/WSS Compatible DSPs (&man.pcm.4; driver)</para>
|
|
|
|
|
<para>NeoMagic 256AV/ZX (&man.pcm.4; driver)</para>
|
|
|
|
|
<para>OPTi 931/82C931 (&man.pcm.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>S3 Sonicvibes</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Creative Technologies SoundBlaster series (&man.sbc.4; driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster Pro</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster AWE-32</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster AWE-64</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster AWE-64 GOLD</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SoundBlaster ViBRA-16</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Trident 4DWave DX/NX (&man.pcm.4; driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>VIA Technologies VT82C686A</para>
|
|
|
|
|
<para>Yamaha
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DS1</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>DS1e</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>Camera and Video Capture Devices</title>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Brooktree Bt848/849/878/879-based frame grabbers (&man.bktr.4;
|
|
|
|
|
driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AverMedia cards</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Hauppauge Wincast TV and WinTV boards (PCI)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel Smart Video Recorder III</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Miro PC TV</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>STB TV PCI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Video Highway XTreme</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>VideoLogic Captivator PCI</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Connectix QuickCam</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para arch="i386">Cortex1 frame grabber (ctx driver)</para>
|
|
|
|
|
<para arch="i386">Creative Labs Video Spigot frame grabber (spigot driver)</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Matrox Meteor Video frame grabber (&man.meteor.4; driver)</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2 id="usb">
|
|
|
|
|
<title>USB Devices</title>
|
|
|
|
|
|
|
|
|
|
<para>A range of USB peripherals are supported; devices known to
|
|
|
|
|
work are listed in this section. Owing to the
|
|
|
|
|
generic nature of most USB devices, with some exceptions any
|
|
|
|
|
device of a given class will be supported, even if not explicitly
|
|
|
|
|
listed here.</para>
|
|
|
|
|
|
|
|
|
|
<note>
|
|
|
|
|
<para>USB Ethernet adapters can be found in the section listing <link
|
|
|
|
|
linkend="ethernet">Ethernet interfaces</link>.</para>
|
|
|
|
|
</note>
|
|
|
|
|
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Host Controllers (&man.ohci.4; and &man.uhci.4; drivers)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ALi Aladdin-V</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AMD-756</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>CMD Tech 670 & 673</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel 82371SB (PIIX3)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
2001-05-29 00:10:32 +00:00
|
|
|
<para>Intel 82371AB and EB (PIIX4)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel 82801AA (ICH)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel 82801AB (ICH0)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel 82801BA/BAM (ICH2)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Intel 82443MX</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC uPD 9210</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>OPTi 82C861 (FireLink)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SiS 5571</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>VIA 83C572 USB</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>UHCI or OHCI compliant motherboard chipsets (no
|
|
|
|
|
exceptions known)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>USB host controllers (PCI)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ADS Electronics PCI plug-in card (2 ports)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Entrega PCI plug-in card (4 ports)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Hubs
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Andromeda hub</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MacAlly self powered hub (4 ports)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NEC hub</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Keyboards (&man.ukbd.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Apple iMac keyboard</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>BTC BTC7935 keyboard with PS/2 mouse port</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Cherry G81-3504 keyboard</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Logitech M2452 keyboard</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MacAlly iKey keyboard</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Microsoft keyboard</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Miscellaneous
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ActiveWire I/O Board</para>
|
|
|
|
|
</listitem>
|
2001-05-14 22:03:11 +00:00
|
|
|
<listitem>
|
2001-09-27 20:51:07 +00:00
|
|
|
<para>Diamond Rio 500, 600, and 800 MP3 players (&man.urio.4; driver)</para>
|
2001-05-14 22:03:11 +00:00
|
|
|
</listitem>
|
2001-04-27 21:28:02 +00:00
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Modems (umodem driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>3Com 5605</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Metricom Ricochet GS USB wireless modem</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Mice (&man.ums.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Agiler Mouse 29UO</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Apple iMac Mouse</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Belkin Mouse</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Chic mouse</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Cypress mouse</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Genius Niche mouse</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Kensington Mouse-in-a-Box</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Logitech wheel mouse (3 buttons)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Logitech PS/2 / USB mouse (3 buttons)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>MacAlly mouse (3 buttons)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Microsoft IntelliMouse (3 buttons)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Trust Ami Mouse (3 buttons)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Printers and parallel printer conversion cables (ulpt driver)
|
2001-04-27 21:28:02 +00:00
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>ATen parallel printer adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Belkin F5U002 parallel printer adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Entrega USB-to-parallel printer adapter</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Scanners (through SANE) (&man.uscanner.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Perfection 636U</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>HP ScanJet 4100C, 5200C, 6300C</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
<para>Storage (&man.umass.4; driver)
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Iomega USB Zip 100Mb (primitive support still)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Matshita CF-VFDU03 floppy drive</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Microtech USB-SCSI-HD 50 USB to SCSI cable</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Panasonic floppy drive</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Y-E Data floppy drive (720/1.44/2.88Mb)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2>
|
|
|
|
|
<title>Miscellaneous</title>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">FAX-Modem/PCCARD
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Melco IGM-PCM56K/IGM-PCM56KH</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Floppy drives (&man.fd.4; driver)</para>
|
|
|
|
|
<para>Genius and Mustek hand scanners</para>
|
|
|
|
|
<para>GPB and Transputer drivers</para>
|
|
|
|
|
<para>HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R
|
|
|
|
|
drives</para>
|
|
|
|
|
<para>Keyboards including:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>AT-style keyboards</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PS/2 keyboards</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>USB keyboards (specific instances are listed in the
|
|
|
|
|
section describing <link linkend="usb">USB devices</link>)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
<para>Loran-C receiver (Dave Mills experimental hardware, loran driver).</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Mice including:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>Bus mice (&man.mse.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>PS/2 mice (&man.psm.4; driver)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Serial mice</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem arch="i386">
|
|
|
|
|
<para>USB mice (specific instances are listed in the
|
|
|
|
|
section describing <link linkend="usb">USB devices</link>)</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Parallel ports</para>
|
|
|
|
|
|
|
|
|
|
<para>PC-compatible joysticks (&man.joy.4 driver)</para>
|
|
|
|
|
|
|
|
|
|
<para arch="i386">PHS Data Communication Card/PCCARD
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>NTT DoCoMo P-in Comp@ct</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Panasonic KX-PH405</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>SII MC-P200</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>Serial ports</para>
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
|
|
|
|
|
<para arch="i386">X-10 power controllers (&man.tw.4 driver)</para>
|
|
|
|
|
|
2001-04-27 21:28:02 +00:00
|
|
|
<para>Xilinx XC6200-based reconfigurable hardware cards compatible
|
|
|
|
|
with the HOT1 from <ulink url="http://www.vcc.com/">Virtual
|
General corrections and fixings of the hardware list:
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
2001-05-14 05:05:13 +00:00
|
|
|
Computers</ulink> (xrpu driver).</para>
|
2001-04-27 21:28:02 +00:00
|
|
|
</sect2>
|
|
|
|
|
</sect1>
|
