1994-05-30 19:09:18 +00:00
|
|
|
# @(#)Makefile 8.1 (Berkeley) 6/18/93
|
1999-10-30 13:17:58 +00:00
|
|
|
# $FreeBSD$
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2014-05-06 04:22:01 +00:00
|
|
|
.include <src.opts.mk>
|
2012-09-19 09:34:21 +00:00
|
|
|
|
2001-03-27 13:48:25 +00:00
|
|
|
MAN= aac.4 \
|
2013-05-24 09:22:43 +00:00
|
|
|
aacraid.4 \
|
2001-07-03 07:45:04 +00:00
|
|
|
acpi.4 \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_acpi_asus.4} \
|
Add acpi_asus_wmi(4) -- driver for random extras found on WMI-compatible
Asus laptops. It is alike to acpi_asus(4), but uses WMI interface instead
of separate ACPI device.
On Asus EeePC T101MT netbook it allows to handle hotkeys and on/off WLAN,
Bluetooth, LCD backlight, camera, cardreader and touchpad.
On Asus UX31A ultrabook it allows to handle hotkeys, on/off WLAN, Bluetooth,
Wireless LED, control keyboard backlight brightness, monitor temperature
and fan speed. LCD brightness control doesn't work now for unknown reason,
possibly requiring some video card initialization.
Sponsored by: iXsystems, Inc.
2012-07-02 08:31:29 +00:00
|
|
|
${_acpi_asus_wmi.4} \
|
2006-05-20 06:21:42 +00:00
|
|
|
${_acpi_dock.4} \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_acpi_fujitsu.4} \
|
2009-06-23 13:17:25 +00:00
|
|
|
${_acpi_hp.4} \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_acpi_ibm.4} \
|
|
|
|
|
${_acpi_panasonic.4} \
|
2014-02-04 18:54:33 +00:00
|
|
|
${_acpi_rapidstart.4} \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_acpi_sony.4} \
|
2003-12-28 23:23:16 +00:00
|
|
|
acpi_thermal.4 \
|
2019-12-10 02:19:07 +00:00
|
|
|
acpi_battery.4 \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_acpi_toshiba.4} \
|
2004-03-03 16:34:03 +00:00
|
|
|
acpi_video.4 \
|
2009-06-23 13:17:25 +00:00
|
|
|
${_acpi_wmi.4} \
|
2009-11-19 16:19:05 +00:00
|
|
|
ada.4 \
|
2017-05-06 06:01:17 +00:00
|
|
|
adm6996fc.4 \
|
2019-08-13 03:49:53 +00:00
|
|
|
ads111x.4 \
|
2008-10-04 14:21:54 +00:00
|
|
|
ae.4 \
|
2010-09-06 20:35:48 +00:00
|
|
|
${_aesni.4} \
|
2008-05-19 02:21:00 +00:00
|
|
|
age.4 \
|
2001-10-05 08:12:03 +00:00
|
|
|
agp.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ahc.4 \
|
Separate the parallel scsi knowledge out of the core of the XPT, and
modularize it so that new transports can be created.
Add a transport for SATA
Add a periph+protocol layer for ATA
Add a driver for AHCI-compliant hardware.
Add a maxio field to CAM so that drivers can advertise their max
I/O capability. Modify various drivers so that they are insulated
from the value of MAXPHYS.
The new ATA/SATA code supports AHCI-compliant hardware, and will override
the classic ATA driver if it is loaded as a module at boot time or compiled
into the kernel. The stack now support NCQ (tagged queueing) for increased
performance on modern SATA drives. It also supports port multipliers.
ATA drives are accessed via 'ada' device nodes. ATAPI drives are
accessed via 'cd' device nodes. They can all be enumerated and manipulated
via camcontrol, just like SCSI drives. SCSI commands are not translated to
their ATA equivalents; ATA native commands are used throughout the entire
stack, including camcontrol. See the camcontrol manpage for further
details. Testing this code may require that you update your fstab, and
possibly modify your BIOS to enable AHCI functionality, if available.
This code is very experimental at the moment. The userland ABI/API has
changed, so applications will need to be recompiled. It may change
further in the near future. The 'ada' device name may also change as
more infrastructure is completed in this project. The goal is to
eventually put all CAM busses and devices until newbus, allowing for
interesting topology and management options.
Few functional changes will be seen with existing SCSI/SAS/FC drivers,
though the userland ABI has still changed. In the future, transports
specific modules for SAS and FC may appear in order to better support
the topologies and capabilities of these technologies.
The modularization of CAM and the addition of the ATA/SATA modules is
meant to break CAM out of the mold of being specific to SCSI, letting it
grow to be a framework for arbitrary transports and protocols. It also
allows drivers to be written to support discrete hardware without
jeopardizing the stability of non-related hardware. While only an AHCI
driver is provided now, a Silicon Image driver is also in the works.
Drivers for ICH1-4, ICH5-6, PIIX, classic IDE, and any other hardware
is possible and encouraged. Help with new transports is also encouraged.
Submitted by: scottl, mav
Approved by: re
2009-07-10 08:18:08 +00:00
|
|
|
ahci.4 \
|
2002-09-01 07:34:47 +00:00
|
|
|
ahd.4 \
|
2010-06-25 15:32:46 +00:00
|
|
|
${_aibs.4} \
|
2002-10-24 12:22:19 +00:00
|
|
|
aio.4 \
|
2009-06-10 02:19:54 +00:00
|
|
|
alc.4 \
|
2008-11-12 10:20:29 +00:00
|
|
|
ale.4 \
|
2010-02-08 23:30:28 +00:00
|
|
|
alpm.4 \
|
MFP4: 221483, 221567, 221568, 221670, 221677, 221678, 221800, 221801,
221804, 221805, 222004, 222006, 222055, 222820, 1135077, 1135118, 1136259
Add atse(4), a driver for the Altera Triple Speed Ethernet MegaCore.
The current driver support gigabit Ethernet speeds only and works with
the MegaCore only in the internal FIFO configuration in the soon to be
open sourced BERI CPU configuration.
Submitted by: bz
MFC after: 3 days
Sponsored by: DARPA/AFRL
2013-10-18 20:44:19 +00:00
|
|
|
altera_atse.4 \
|
Add altera_avgen(4), a generic device driver to be used by hard and soft
CPU cores on Altera FPGAs. The device driver allows memory-mapped devices
on Altera's Avalon SoC bus to be exported to userspace via device nodes.
device.hints directories dictate device name, permissible access methods,
physical address and length, and I/O alignment. Devices can be accessed
using read(2)/write(2), but also memory mapped in userspace using mmap(2).
Devices attach directly to the Nexus, as is common for embedded device
drivers; in the future something more mature might be desirable. There is
currently no facility to support directing device-originated interrupts to
userspace.
In the future, this device driver may be renamed to socgen(4), as it can
in principle also be used with other system-on-chip (SoC) busses, such as
Axi on ASICs and FPGAs. However, we have only tested it on Avalon busses
with memory-mapped ROMs, frame buffers, etc.
Sponsored by: DARPA, AFRL
2012-08-25 11:07:43 +00:00
|
|
|
altera_avgen.4 \
|
Add altera_jtag_uart(4), a device driver for Altera's JTAG UART soft core,
which presents a UART-like interface over the Avalon bus that can be
addressed over JTAG. This IP core proves extremely useful, allowing us to
connect trivially to the FreeBSD console over JTAG for FPGA-embedded hard
and soft cores. As interrupts are optionally configured for this soft
core, we support both interrupt-driven and polled modes of operation,
which must be selected using device.hints. UART instances appear in /dev
as ttyu0, ttyu1, etc.
However, it also contains a number of quirks, which make it difficult to
tell when JTAG is connected, and some buffering issues. We work around
these as best we can, using various heuristics.
While the majority of this device driver is not only not BERI-specific,
but also not MIPS-specific, for now add its defines in the BERI files
list, as the console-level parts are aware of where the first JTAG UART
is mapped on Avalon, and contain MIPS-specific address translation, to
use before Newbus and device.hints are available.
Sponsored by: DARPA, AFRL
2012-08-25 11:30:36 +00:00
|
|
|
altera_jtag_uart.4 \
|
Add a device driver for the Altera University Program SD Card IP Core,
which can be synthesised in Altera FPGAs. An altera_sdcardc device
probes during the boot, and /dev/altera_sdcard devices come and go as
inserted and removed. The device driver attaches directly to the
Nexus, as is common for system-on-chip device drivers.
This IP core suffers a number of significant limitations, including a
lack of interrupt-driven I/O -- we must implement timer-driven polling,
only CSD 0 cards (up to 2G) are supported, there are serious memory
access issues that require the driver to verify writes to memory-mapped
buffers, undocumented alignment requirements, and erroneous error
returns. The driver must therefore work quite hard, despite a fairly
simple hardware-software interface. The IP core also supports at most
one outstanding I/O at a time, so is not a speed demon.
However, with the above workarounds, and subject to performance
problems, it works quite reliably in practice, and we can use it for
read-write mounts of root file systems, etc.
Sponsored by: DARPA, AFRL
2012-08-25 11:19:20 +00:00
|
|
|
altera_sdcard.4 \
|
2004-10-07 12:10:25 +00:00
|
|
|
altq.4 \
|
2010-02-08 23:30:28 +00:00
|
|
|
amdpm.4 \
|
2009-11-30 11:44:03 +00:00
|
|
|
${_amdsbwd.4} \
|
2005-12-31 11:24:36 +00:00
|
|
|
${_amdsmb.4} \
|
2017-09-05 15:13:41 +00:00
|
|
|
${_amdsmn.4} \
|
2009-10-20 13:22:54 +00:00
|
|
|
${_amdtemp.4} \
|
2012-06-27 10:07:29 +00:00
|
|
|
${_bxe.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
amr.4 \
|
|
|
|
|
an.4 \
|
2012-08-15 16:01:45 +00:00
|
|
|
${_aout.4} \
|
2011-12-20 13:49:52 +00:00
|
|
|
${_apic.4} \
|
2005-09-28 07:31:18 +00:00
|
|
|
arcmsr.4 \
|
2007-11-12 17:52:00 +00:00
|
|
|
${_asmc.4} \
|
2019-02-26 22:50:01 +00:00
|
|
|
at45d.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ata.4 \
|
2003-06-23 20:54:39 +00:00
|
|
|
ath.4 \
|
2011-05-30 10:07:46 +00:00
|
|
|
ath_ahb.4 \
|
2003-06-23 20:54:39 +00:00
|
|
|
ath_hal.4 \
|
2011-05-30 10:07:46 +00:00
|
|
|
ath_pci.4 \
|
2003-11-29 18:14:04 +00:00
|
|
|
atkbd.4 \
|
|
|
|
|
atkbdc.4 \
|
2014-02-07 15:00:08 +00:00
|
|
|
atp.4 \
|
2012-10-22 01:18:41 +00:00
|
|
|
${_atf_test_case.4} \
|
2010-09-17 08:44:54 +00:00
|
|
|
${_atrtc.4} \
|
2010-09-17 07:44:01 +00:00
|
|
|
${_attimer.4} \
|
2006-02-02 10:32:27 +00:00
|
|
|
audit.4 \
|
2006-06-05 15:26:09 +00:00
|
|
|
auditpipe.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
aue.4 \
|
2003-04-20 19:05:33 +00:00
|
|
|
axe.4 \
|
2013-11-19 00:37:53 +00:00
|
|
|
axge.4 \
|
2006-04-10 20:04:22 +00:00
|
|
|
bce.4 \
|
[bwn] [bhnd] initial support for using bhnd for if_bwn devices.
This is an initial work in progress to use the replacement bhnd
bus code for devices which support it.
* Add manpage updates for bhnd, bhndb, siba
* Add kernel options for bhnd, bhndbus, etc
* Add initial support in if_bwn_pci / if_bwn_mac for using bhnd
as the bus transport for suppoted NICs
* if_bwn_pci will eventually be the PCI bus glue to interface to bwn,
which will use the right backend bus to attach to, versus direct
nexus/bhnd attachments (as found in embedded broadcom devices.)
The PCI glue defaults to probing at a lower level than the bwn glue,
so bwn should still attach as per normal without a boot time tunable set.
It's also not fully fleshed out - the bwn probe/attach code needs to be
broken out into platform and bus specific things (just like ath, ath_pci,
ath_ahb) before we can shift the driver over to using this.
Tested:
* BCM4311, STA mode
* BCM4312, STA mode
Submitted by: Landon Fuller <landonf@landonf.org>
Differential Revision: https://reviews.freebsd.org/D6191
2016-05-04 23:38:27 +00:00
|
|
|
bcma.4 \
|
2003-09-09 18:17:23 +00:00
|
|
|
bfe.4 \
|
2001-09-27 23:55:28 +00:00
|
|
|
bge.4 \
|
2013-01-20 04:04:37 +00:00
|
|
|
${_bhyve.4} \
|
[bwn] [bhnd] initial support for using bhnd for if_bwn devices.
This is an initial work in progress to use the replacement bhnd
bus code for devices which support it.
* Add manpage updates for bhnd, bhndb, siba
* Add kernel options for bhnd, bhndbus, etc
* Add initial support in if_bwn_pci / if_bwn_mac for using bhnd
as the bus transport for suppoted NICs
* if_bwn_pci will eventually be the PCI bus glue to interface to bwn,
which will use the right backend bus to attach to, versus direct
nexus/bhnd attachments (as found in embedded broadcom devices.)
The PCI glue defaults to probing at a lower level than the bwn glue,
so bwn should still attach as per normal without a boot time tunable set.
It's also not fully fleshed out - the bwn probe/attach code needs to be
broken out into platform and bus specific things (just like ath, ath_pci,
ath_ahb) before we can shift the driver over to using this.
Tested:
* BCM4311, STA mode
* BCM4312, STA mode
Submitted by: Landon Fuller <landonf@landonf.org>
Differential Revision: https://reviews.freebsd.org/D6191
2016-05-04 23:38:27 +00:00
|
|
|
bhnd.4 \
|
2017-11-27 21:30:49 +00:00
|
|
|
bhnd_chipc.4 \
|
|
|
|
|
bhnd_pmu.4 \
|
[bwn] [bhnd] initial support for using bhnd for if_bwn devices.
This is an initial work in progress to use the replacement bhnd
bus code for devices which support it.
* Add manpage updates for bhnd, bhndb, siba
* Add kernel options for bhnd, bhndbus, etc
* Add initial support in if_bwn_pci / if_bwn_mac for using bhnd
as the bus transport for suppoted NICs
* if_bwn_pci will eventually be the PCI bus glue to interface to bwn,
which will use the right backend bus to attach to, versus direct
nexus/bhnd attachments (as found in embedded broadcom devices.)
The PCI glue defaults to probing at a lower level than the bwn glue,
so bwn should still attach as per normal without a boot time tunable set.
It's also not fully fleshed out - the bwn probe/attach code needs to be
broken out into platform and bus specific things (just like ath, ath_pci,
ath_ahb) before we can shift the driver over to using this.
Tested:
* BCM4311, STA mode
* BCM4312, STA mode
Submitted by: Landon Fuller <landonf@landonf.org>
Differential Revision: https://reviews.freebsd.org/D6191
2016-05-04 23:38:27 +00:00
|
|
|
bhndb.4 \
|
2017-11-27 21:30:49 +00:00
|
|
|
bhndb_pci.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
blackhole.4 \
|
2016-11-15 20:35:29 +00:00
|
|
|
bnxt.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
bpf.4 \
|
2009-06-25 17:24:36 +00:00
|
|
|
bridge.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
bt.4 \
|
2009-05-16 10:42:00 +00:00
|
|
|
bwi.4 \
|
2010-02-25 19:43:22 +00:00
|
|
|
bwn.4 \
|
2016-11-21 19:46:10 +00:00
|
|
|
${_bytgpio.4} \
|
2018-02-22 19:12:32 +00:00
|
|
|
${_chvgpio.4} \
|
2011-11-27 19:44:15 +00:00
|
|
|
capsicum.4 \
|
2002-07-09 05:08:49 +00:00
|
|
|
cardbus.4 \
|
2005-02-23 08:29:50 +00:00
|
|
|
carp.4 \
|
2009-06-15 18:24:04 +00:00
|
|
|
cas.4 \
|
2013-07-02 08:44:56 +00:00
|
|
|
cc_cdg.4 \
|
2011-02-21 11:56:11 +00:00
|
|
|
cc_chd.4 \
|
|
|
|
|
cc_cubic.4 \
|
2015-01-12 08:33:04 +00:00
|
|
|
cc_dctcp.4 \
|
2011-02-21 11:56:11 +00:00
|
|
|
cc_hd.4 \
|
|
|
|
|
cc_htcp.4 \
|
|
|
|
|
cc_newreno.4 \
|
|
|
|
|
cc_vegas.4 \
|
2015-01-25 04:52:48 +00:00
|
|
|
${_ccd.4} \
|
Add a driver for the Chelsio T6 crypto accelerator engine.
The ccr(4) driver supports use of the crypto accelerator engine on
Chelsio T6 NICs in "lookaside" mode via the opencrypto framework.
Currently, the driver supports AES-CBC, AES-CTR, AES-GCM, and AES-XTS
cipher algorithms as well as the SHA1-HMAC, SHA2-256-HMAC, SHA2-384-HMAC,
and SHA2-512-HMAC authentication algorithms. The driver also supports
chaining one of AES-CBC, AES-CTR, or AES-XTS with an authentication
algorithm for encrypt-then-authenticate operations.
Note that this driver is still under active development and testing and
may not yet be ready for production use. It does pass the tests in
tests/sys/opencrypto with the exception that the AES-GCM implementation
in the driver does not yet support requests with a zero byte payload.
To use this driver currently, the "uwire" configuration must be used
along with explicitly enabling support for lookaside crypto capabilities
in the cxgbe(4) driver. These can be done by setting the following
tunables before loading the cxgbe(4) driver:
hw.cxgbe.config_file=uwire
hw.cxgbe.cryptocaps_allowed=-1
MFC after: 1 month
Relnotes: yes
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D10763
2017-05-17 22:13:07 +00:00
|
|
|
ccr.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
cd.4 \
|
2005-03-22 14:52:40 +00:00
|
|
|
cdce.4 \
|
2019-08-07 18:14:45 +00:00
|
|
|
cdceem.4 \
|
2016-01-20 18:47:33 +00:00
|
|
|
cfi.4 \
|
2017-02-19 17:47:43 +00:00
|
|
|
cfumass.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ch.4 \
|
2017-02-25 14:50:53 +00:00
|
|
|
chromebook_platform.4 \
|
2002-12-30 22:54:01 +00:00
|
|
|
ciss.4 \
|
2015-08-02 14:56:30 +00:00
|
|
|
cloudabi.4 \
|
2008-03-06 08:09:45 +00:00
|
|
|
cmx.4 \
|
2007-08-23 20:05:09 +00:00
|
|
|
${_coretemp.4} \
|
2008-08-08 16:26:53 +00:00
|
|
|
${_cpuctl.4} \
|
2005-02-08 17:44:18 +00:00
|
|
|
cpufreq.4 \
|
2002-10-04 20:43:30 +00:00
|
|
|
crypto.4 \
|
2013-04-02 09:42:42 +00:00
|
|
|
ctl.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
cue.4 \
|
2007-03-14 05:12:25 +00:00
|
|
|
cxgb.4 \
|
2011-02-18 08:00:26 +00:00
|
|
|
cxgbe.4 \
|
Chelsio T4/T5 VF driver.
The cxgbev/cxlv driver supports Virtual Function devices for Chelsio
T4 and T4 adapters. The VF devices share most of their code with the
existing PF4 driver (cxgbe/cxl) and as such the VF device driver
currently depends on the PF4 driver.
Similar to the cxgbe/cxl drivers, the VF driver includes a t4vf/t5vf
PCI device driver that attaches to the VF device. It then creates
child cxgbev/cxlv devices representing ports assigned to the VF.
By default, the PF driver assigns a single port to each VF.
t4vf_hw.c contains VF-specific routines from the shared code used to
fetch VF-specific parameters from the firmware.
t4_vf.c contains the VF-specific PCI device driver and includes its
own attach routine.
VF devices are required to use a different firmware request when
transmitting packets (which in turn requires a different CPL message
to encapsulate messages). This alternate firmware request does not
permit chaining multiple packets in a single message, so each packet
results in a firmware request. In addition, the different CPL message
requires more detailed information when enabling hardware checksums,
so parse_pkt() on VF devices must examine L2 and L3 headers for all
packets (not just TSO packets) for VF devices. Finally, L2 checksums
on non-UDP/non-TCP packets do not work reliably (the firmware trashes
the IPv4 fragment field), so IPv4 checksums for such packets are
calculated in software.
Most of the other changes in the non-VF-specific code are to expose
various variables and functions private to the PF driver so that they
can be used by the VF driver.
Note that a limited subset of cxgbetool functions are supported on VF
devices including register dumps, scheduler classes, and clearing of
statistics. In addition, TOE is not supported on VF devices, only for
the PF interfaces.
Reviewed by: np
MFC after: 2 months
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D7599
2016-09-07 18:13:57 +00:00
|
|
|
cxgbev.4 \
|
2017-04-27 16:14:32 +00:00
|
|
|
cy.4 \
|
2015-07-25 18:14:35 +00:00
|
|
|
cyapa.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
da.4 \
|
|
|
|
|
dc.4 \
|
2003-10-24 15:44:10 +00:00
|
|
|
dcons.4 \
|
|
|
|
|
dcons_crom.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ddb.4 \
|
2002-12-11 23:08:19 +00:00
|
|
|
devctl.4 \
|
2002-05-29 06:59:30 +00:00
|
|
|
disc.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
divert.4 \
|
2009-09-09 09:50:31 +00:00
|
|
|
${_dpms.4} \
|
2015-03-20 19:51:24 +00:00
|
|
|
ds1307.4 \
|
2015-03-07 01:42:04 +00:00
|
|
|
ds3231.4 \
|
2017-06-10 21:13:39 +00:00
|
|
|
${_dtrace_provs} \
|
2000-07-21 10:13:46 +00:00
|
|
|
dummynet.4 \
|
2007-03-26 04:39:18 +00:00
|
|
|
edsc.4 \
|
2003-05-18 19:55:39 +00:00
|
|
|
ehci.4 \
|
2001-12-02 07:45:22 +00:00
|
|
|
em.4 \
|
2017-07-07 16:22:09 +00:00
|
|
|
ena.4 \
|
2006-06-26 22:31:26 +00:00
|
|
|
enc.4 \
|
2009-07-26 12:20:07 +00:00
|
|
|
epair.4 \
|
2004-06-21 18:20:57 +00:00
|
|
|
esp.4 \
|
2012-06-18 23:18:49 +00:00
|
|
|
est.4 \
|
2008-07-14 18:15:43 +00:00
|
|
|
et.4 \
|
2015-01-05 11:40:05 +00:00
|
|
|
etherswitch.4 \
|
2011-12-14 15:19:40 +00:00
|
|
|
eventtimers.4 \
|
2003-02-23 22:22:29 +00:00
|
|
|
exca.4 \
|
2017-05-06 06:01:17 +00:00
|
|
|
e6060sw.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
fd.4 \
|
|
|
|
|
fdc.4 \
|
2010-07-14 13:03:00 +00:00
|
|
|
fdt.4 \
|
2018-03-03 02:49:49 +00:00
|
|
|
fdt_pinctrl.4 \
|
2010-07-14 13:03:00 +00:00
|
|
|
fdtbus.4 \
|
2011-12-01 07:41:30 +00:00
|
|
|
ffclock.4 \
|
2012-06-04 22:59:06 +00:00
|
|
|
filemon.4 \
|
2002-10-25 14:34:24 +00:00
|
|
|
firewire.4 \
|
2014-05-02 05:30:49 +00:00
|
|
|
full.4 \
|
2002-11-08 03:24:32 +00:00
|
|
|
fwe.4 \
|
2004-06-14 10:55:03 +00:00
|
|
|
fwip.4 \
|
2002-10-25 14:34:24 +00:00
|
|
|
fwohci.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
fxp.4 \
|
2002-10-19 21:44:57 +00:00
|
|
|
gbde.4 \
|
2004-01-02 02:18:34 +00:00
|
|
|
gdb.4 \
|
2004-01-20 10:27:23 +00:00
|
|
|
gem.4 \
|
2002-03-27 09:58:14 +00:00
|
|
|
geom.4 \
|
2008-02-20 07:50:13 +00:00
|
|
|
geom_linux_lvm.4 \
|
2011-05-05 14:43:35 +00:00
|
|
|
geom_map.4 \
|
2006-10-08 17:05:15 +00:00
|
|
|
geom_uzip.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
gif.4 \
|
2013-09-13 19:55:40 +00:00
|
|
|
gpio.4 \
|
2013-11-27 12:17:05 +00:00
|
|
|
gpioiic.4 \
|
|
|
|
|
gpioled.4 \
|
2019-12-09 04:15:01 +00:00
|
|
|
gpioths.4 \
|
2002-09-06 17:17:22 +00:00
|
|
|
gre.4 \
|
2011-02-21 11:56:11 +00:00
|
|
|
h_ertt.4 \
|
2002-10-04 20:43:30 +00:00
|
|
|
hifn.4 \
|
2003-06-10 18:53:15 +00:00
|
|
|
hme.4 \
|
2010-09-15 04:51:07 +00:00
|
|
|
hpet.4 \
|
2011-12-28 23:26:58 +00:00
|
|
|
${_hpt27xx.4} \
|
2007-05-11 22:53:09 +00:00
|
|
|
${_hptiop.4} \
|
|
|
|
|
${_hptmv.4} \
|
2013-07-06 07:49:41 +00:00
|
|
|
${_hptnr.4} \
|
2007-12-15 00:56:17 +00:00
|
|
|
${_hptrr.4} \
|
2016-11-24 05:52:28 +00:00
|
|
|
${_hv_kvp.4} \
|
|
|
|
|
${_hv_netvsc.4} \
|
|
|
|
|
${_hv_storvsc.4} \
|
|
|
|
|
${_hv_utils.4} \
|
|
|
|
|
${_hv_vmbus.4} \
|
|
|
|
|
${_hv_vss.4} \
|
2005-04-19 04:01:25 +00:00
|
|
|
hwpmc.4 \
|
2020-02-20 06:45:51 +00:00
|
|
|
${_hwpstate_intel.4} \
|
2018-10-12 22:57:52 +00:00
|
|
|
iavf.4 \
|
2000-11-16 03:43:56 +00:00
|
|
|
ichsmb.4 \
|
2007-08-23 20:05:09 +00:00
|
|
|
${_ichwd.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
icmp.4 \
|
|
|
|
|
icmp6.4 \
|
2003-01-06 04:51:20 +00:00
|
|
|
ida.4 \
|
2017-02-06 08:49:57 +00:00
|
|
|
if_ipsec.4 \
|
2018-09-20 18:24:32 +00:00
|
|
|
iflib.4 \
|
2005-09-28 07:31:18 +00:00
|
|
|
ifmib.4 \
|
2015-05-30 12:17:18 +00:00
|
|
|
ig4.4 \
|
2009-03-09 17:53:05 +00:00
|
|
|
igmp.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
iic.4 \
|
Add support for i2c bus mux hardware.
An i2c bus can be divided into segments which can be selectively connected
and disconnected from the main bus. This is usually done to enable using
multiple slave devices having the same address, by isolating the devices
onto separate bus segments, only one of which is connected to the main bus
at once.
There are several types of i2c bus muxes, which break down into two general
categories...
- Muxes which are themselves i2c slaves. These devices respond to i2c
commands on their upstream bus, and based on those commands, connect
various downstream buses to the upstream. In newbus terms, they are both
a child of an iicbus and the parent of one or more iicbus instances.
- Muxes which are not i2c devices themselves. Such devices are part of the
i2c bus electrically, but in newbus terms their parent is some other
bus. The association with the upstream bus must be established by
separate metadata (such as FDT data).
In both cases, the mux driver has one or more iicbus child instances
representing the downstream buses. The mux driver implements the iicbus_if
interface, as if it were an iichb host bridge/i2c controller driver. It
services the IO requests sent to it by forwarding them to the iicbus
instance representing the upstream bus, after electrically connecting the
upstream bus to the downstream bus that hosts the i2c slave device which
made the IO request.
The net effect is automatic mux switching which is transparent to slaves on
the downstream buses. They just do i2c IO they way they normally do, and the
bus is electrically connected for the duration of the IO and then idled when
it is complete.
The existing iicbus_if callback() method is enhanced so that the parameter
passed to it can be a struct which contains a device_t for the requesting
bus and slave devices. This change is done by adding a flag that indicates
the extra values are present, and making the flags field the first field of
a new args struct. If the flag is set, the iichb or mux driver can recast
the pointer-to-flags into a pointer-to-struct and access the extra
fields. Thus abi compatibility with older drivers is retained (but a mux
cannot exist on the bus with the older iicbus driver in use.)
A new set of core support routines exists in iicbus.c. This code will help
implement mux drivers for any type of mux hardware by supplying all the
boilerplate code that forwards IO requests upstream. It also has code for
parsing metadata and instantiating the child iicbus instances based on it.
Two new hardware mux drivers are added. The ltc430x driver supports the
LTC4305/4306 mux chips which are controlled via i2c commands. The
iic_gpiomux driver supports any mux hardware which is controlled by
manipulating the state of one or more gpio pins. Test Plan
Tested locally using a variety of mux'd bus configurations involving both
ltc4305 and a homebrew gpio-controlled mux. Tested configurations included
cascaded muxes (unlikely in the real world, but useful to prove that 'it all
just works' in terms of the automatic switching and upstream forwarding of
IO requests).
2020-01-02 17:51:49 +00:00
|
|
|
iic_gpiomux.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
iicbb.4 \
|
|
|
|
|
iicbus.4 \
|
Add support for i2c bus mux hardware.
An i2c bus can be divided into segments which can be selectively connected
and disconnected from the main bus. This is usually done to enable using
multiple slave devices having the same address, by isolating the devices
onto separate bus segments, only one of which is connected to the main bus
at once.
There are several types of i2c bus muxes, which break down into two general
categories...
- Muxes which are themselves i2c slaves. These devices respond to i2c
commands on their upstream bus, and based on those commands, connect
various downstream buses to the upstream. In newbus terms, they are both
a child of an iicbus and the parent of one or more iicbus instances.
- Muxes which are not i2c devices themselves. Such devices are part of the
i2c bus electrically, but in newbus terms their parent is some other
bus. The association with the upstream bus must be established by
separate metadata (such as FDT data).
In both cases, the mux driver has one or more iicbus child instances
representing the downstream buses. The mux driver implements the iicbus_if
interface, as if it were an iichb host bridge/i2c controller driver. It
services the IO requests sent to it by forwarding them to the iicbus
instance representing the upstream bus, after electrically connecting the
upstream bus to the downstream bus that hosts the i2c slave device which
made the IO request.
The net effect is automatic mux switching which is transparent to slaves on
the downstream buses. They just do i2c IO they way they normally do, and the
bus is electrically connected for the duration of the IO and then idled when
it is complete.
The existing iicbus_if callback() method is enhanced so that the parameter
passed to it can be a struct which contains a device_t for the requesting
bus and slave devices. This change is done by adding a flag that indicates
the extra values are present, and making the flags field the first field of
a new args struct. If the flag is set, the iichb or mux driver can recast
the pointer-to-flags into a pointer-to-struct and access the extra
fields. Thus abi compatibility with older drivers is retained (but a mux
cannot exist on the bus with the older iicbus driver in use.)
A new set of core support routines exists in iicbus.c. This code will help
implement mux drivers for any type of mux hardware by supplying all the
boilerplate code that forwards IO requests upstream. It also has code for
parsing metadata and instantiating the child iicbus instances based on it.
Two new hardware mux drivers are added. The ltc430x driver supports the
LTC4305/4306 mux chips which are controlled via i2c commands. The
iic_gpiomux driver supports any mux hardware which is controlled by
manipulating the state of one or more gpio pins. Test Plan
Tested locally using a variety of mux'd bus configurations involving both
ltc4305 and a homebrew gpio-controlled mux. Tested configurations included
cascaded muxes (unlikely in the real world, but useful to prove that 'it all
just works' in terms of the automatic switching and upstream forwarding of
IO requests).
2020-01-02 17:51:49 +00:00
|
|
|
iicmux.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
iicsmb.4 \
|
2003-01-06 04:51:20 +00:00
|
|
|
iir.4 \
|
imcsmb(4): Intel integrated Memory Controller (iMC) SMBus controller driver
imcsmb(4) provides smbus(4) support for the SMBus controller functionality
in the integrated Memory Controllers (iMCs) embedded in Intel Sandybridge-
Xeon, Ivybridge-Xeon, Haswell-Xeon, and Broadwell-Xeon CPUs. Each CPU
implements one or more iMCs, depending on the number of cores; each iMC
implements two SMBus controllers (iMC-SMBs).
*** IMPORTANT NOTE ***
Because motherboard firmware or the BMC might try to use the iMC-SMBs for
monitoring DIMM temperatures and/or managing an NVDIMM, the driver might
need to temporarily disable those functions, or take a hardware interlock,
before using the iMC-SMBs. Details on how to do this may vary from board to
board, and the procedure may be proprietary. It is strongly suggested that
anyone wishing to use this driver contact their motherboard vendor, and
modify the driver as described in the manual page and in the driver itself.
(For what it's worth, the driver as-is has been tested on various SuperMicro
motherboards.)
Reviewed by: avg, jhb
MFC after: 1 week
Relnotes: yes
Sponsored by: Panasas
Differential Revision: https://reviews.freebsd.org/D14447
Discussed with: avg, ian, jhb
Tested by: allanjude (previous version), Panasas
2018-03-03 01:53:51 +00:00
|
|
|
${_imcsmb.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
inet.4 \
|
|
|
|
|
inet6.4 \
|
|
|
|
|
intpm.4 \
|
|
|
|
|
intro.4 \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_io.4} \
|
2015-08-24 19:32:03 +00:00
|
|
|
${_ioat.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
ip.4 \
|
|
|
|
|
ip6.4 \
|
|
|
|
|
ipfirewall.4 \
|
2014-09-25 14:18:34 +00:00
|
|
|
ipheth.4 \
|
2006-02-14 17:18:20 +00:00
|
|
|
${_ipmi.4} \
|
2003-11-11 18:48:02 +00:00
|
|
|
ips.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ipsec.4 \
|
2005-04-18 18:47:38 +00:00
|
|
|
ipw.4 \
|
2010-01-14 22:21:43 +00:00
|
|
|
ipwfw.4 \
|
2012-01-23 22:30:09 +00:00
|
|
|
isci.4 \
|
2015-07-25 20:17:19 +00:00
|
|
|
isl.4 \
|
2014-05-20 19:55:06 +00:00
|
|
|
ismt.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
isp.4 \
|
|
|
|
|
ispfw.4 \
|
2019-10-16 14:57:38 +00:00
|
|
|
${_itwd.4} \
|
2005-04-18 18:47:38 +00:00
|
|
|
iwi.4 \
|
2010-01-14 22:21:43 +00:00
|
|
|
iwifw.4 \
|
2015-08-10 10:36:08 +00:00
|
|
|
iwm.4 \
|
|
|
|
|
iwmfw.4 \
|
2008-04-29 21:36:17 +00:00
|
|
|
iwn.4 \
|
2009-05-09 19:44:23 +00:00
|
|
|
iwnfw.4 \
|
2008-09-04 20:45:32 +00:00
|
|
|
ixgbe.4 \
|
2015-01-15 22:17:11 +00:00
|
|
|
ixl.4 \
|
2018-02-22 23:18:46 +00:00
|
|
|
jedec_dimm.4 \
|
2008-05-27 02:18:17 +00:00
|
|
|
jme.4 \
|
2005-07-14 23:04:23 +00:00
|
|
|
kbdmux.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
keyboard.4 \
|
|
|
|
|
kld.4 \
|
2009-05-26 21:39:09 +00:00
|
|
|
ksyms.4 \
|
2017-05-06 06:01:17 +00:00
|
|
|
ksz8995ma.4 \
|
2001-03-09 03:43:18 +00:00
|
|
|
ktr.4 \
|
2003-11-29 18:14:04 +00:00
|
|
|
kue.4 \
|
2007-04-17 00:35:11 +00:00
|
|
|
lagg.4 \
|
2006-01-31 22:40:25 +00:00
|
|
|
le.4 \
|
2003-11-03 17:06:10 +00:00
|
|
|
led.4 \
|
2001-05-31 21:44:26 +00:00
|
|
|
lge.4 \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_linux.4} \
|
2017-09-12 23:36:58 +00:00
|
|
|
liquidio.4 \
|
2014-05-10 12:19:02 +00:00
|
|
|
lm75.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
lo.4 \
|
|
|
|
|
lp.4 \
|
|
|
|
|
lpbb.4 \
|
|
|
|
|
lpt.4 \
|
Add support for i2c bus mux hardware.
An i2c bus can be divided into segments which can be selectively connected
and disconnected from the main bus. This is usually done to enable using
multiple slave devices having the same address, by isolating the devices
onto separate bus segments, only one of which is connected to the main bus
at once.
There are several types of i2c bus muxes, which break down into two general
categories...
- Muxes which are themselves i2c slaves. These devices respond to i2c
commands on their upstream bus, and based on those commands, connect
various downstream buses to the upstream. In newbus terms, they are both
a child of an iicbus and the parent of one or more iicbus instances.
- Muxes which are not i2c devices themselves. Such devices are part of the
i2c bus electrically, but in newbus terms their parent is some other
bus. The association with the upstream bus must be established by
separate metadata (such as FDT data).
In both cases, the mux driver has one or more iicbus child instances
representing the downstream buses. The mux driver implements the iicbus_if
interface, as if it were an iichb host bridge/i2c controller driver. It
services the IO requests sent to it by forwarding them to the iicbus
instance representing the upstream bus, after electrically connecting the
upstream bus to the downstream bus that hosts the i2c slave device which
made the IO request.
The net effect is automatic mux switching which is transparent to slaves on
the downstream buses. They just do i2c IO they way they normally do, and the
bus is electrically connected for the duration of the IO and then idled when
it is complete.
The existing iicbus_if callback() method is enhanced so that the parameter
passed to it can be a struct which contains a device_t for the requesting
bus and slave devices. This change is done by adding a flag that indicates
the extra values are present, and making the flags field the first field of
a new args struct. If the flag is set, the iichb or mux driver can recast
the pointer-to-flags into a pointer-to-struct and access the extra
fields. Thus abi compatibility with older drivers is retained (but a mux
cannot exist on the bus with the older iicbus driver in use.)
A new set of core support routines exists in iicbus.c. This code will help
implement mux drivers for any type of mux hardware by supplying all the
boilerplate code that forwards IO requests upstream. It also has code for
parsing metadata and instantiating the child iicbus instances based on it.
Two new hardware mux drivers are added. The ltc430x driver supports the
LTC4305/4306 mux chips which are controlled via i2c commands. The
iic_gpiomux driver supports any mux hardware which is controlled by
manipulating the state of one or more gpio pins. Test Plan
Tested locally using a variety of mux'd bus configurations involving both
ltc4305 and a homebrew gpio-controlled mux. Tested configurations included
cascaded muxes (unlikely in the real world, but useful to prove that 'it all
just works' in terms of the automatic switching and upstream forwarding of
IO requests).
2020-01-02 17:51:49 +00:00
|
|
|
ltc430x.4 \
|
2003-01-15 02:57:39 +00:00
|
|
|
mac.4 \
|
2002-12-05 00:05:38 +00:00
|
|
|
mac_biba.4 \
|
|
|
|
|
mac_bsdextended.4 \
|
2002-12-11 01:02:26 +00:00
|
|
|
mac_ifoff.4 \
|
2003-01-08 10:30:00 +00:00
|
|
|
mac_lomac.4 \
|
2002-12-05 00:05:38 +00:00
|
|
|
mac_mls.4 \
|
2002-12-10 00:39:17 +00:00
|
|
|
mac_none.4 \
|
2018-11-14 16:18:13 +00:00
|
|
|
mac_ntpd.4 \
|
2002-12-11 03:25:35 +00:00
|
|
|
mac_partition.4 \
|
2003-03-31 08:08:59 +00:00
|
|
|
mac_portacl.4 \
|
2002-12-10 00:39:17 +00:00
|
|
|
mac_seeotheruids.4 \
|
2003-08-21 16:53:06 +00:00
|
|
|
mac_stub.4 \
|
2002-12-10 00:39:17 +00:00
|
|
|
mac_test.4 \
|
2008-04-01 07:20:04 +00:00
|
|
|
malo.4 \
|
2003-11-10 12:45:10 +00:00
|
|
|
md.4 \
|
2015-12-26 02:31:39 +00:00
|
|
|
mdio.4 \
|
2014-11-07 19:13:19 +00:00
|
|
|
me.4 \
|
2003-11-10 12:45:10 +00:00
|
|
|
mem.4 \
|
2003-12-08 02:59:34 +00:00
|
|
|
meteor.4 \
|
2006-03-29 07:35:39 +00:00
|
|
|
mfi.4 \
|
2003-11-10 12:45:10 +00:00
|
|
|
miibus.4 \
|
2009-12-25 22:01:39 +00:00
|
|
|
mk48txx.4 \
|
Merge final round of MLD changes from p4:
ip6_input.c, in6.h:
* Add netinet6-specific mbuf flag M_RTALERT_MLD, shadowing M_PROTO6.
* Always set this flag if HBH Router Alert option is present for MLD,
even when not forwarding.
icmp6.c:
* In icmp6_input(), spell m->m_pkthdr.rcvif as ifp to be consistent.
* Use scope ID for verifying input. Do not apply SSM filters here, no inpcb.
* Check for M_RTALERT_MLD when validating MLD traffic, as we can't see
IPv6 hop options outside of ip6_input().
in6_mcast.c:
* Use KAME scope/zone ID in in6_multi.
* Update net.inet6.ip6.mcast.filters implementation to use scope IDs
for comparisons.
* Fix scope ID treatment in multicast socket option processing.
Scope IDs passed in from userland will be ignored as other less
ambiguous APIs exist for specifying the link.
* Tighten userland input checks in IPv6 SSM delta and full-state ops.
* Source filter embedded scope IDs need to be revisited, for now
just clear them and ignore them on input.
* Adapt KAME behaviour of looking up the scope ID in the default zone
for multicast leaves, when the interface is ambiguous.
mld6.c:
* Tighten origin checks on MLD traffic as per RFC3810 Section 6.2:
* ip6_src MAY be the unspecified address for MLDv1 reports.
* ip6_src MAY have link-local address scope for MLDv1 reports,
MLDv1 queries, and MLDv2 queries.
* Perform address field validation *before* accepting queries.
* Use KAME scope/zone ID in query/report processing.
* Break const correctness for mld_v1_input_report(), mld_v1_input_query()
as we temporarily modify the input mbuf chain.
* Clear the scope ID before handoff to userland MLD daemon.
* Fix MLDv1 old querier present timer processing.
With the protocol defaults, hosts should revert to MLDv2 after 260s.
* Add net.inet6.mld.v1enable sysctl, default to on.
ifmcstat.c:
* Use sysctl by default; -K requests kvm(3) if so compiled.
mld.4:
* Connect man page to build.
Tested using PCS.
2009-05-27 18:57:13 +00:00
|
|
|
mld.4 \
|
2003-11-10 12:45:10 +00:00
|
|
|
mlx.4 \
|
2016-09-30 08:23:06 +00:00
|
|
|
mlx4en.4 \
|
2015-11-23 19:44:39 +00:00
|
|
|
mlx5en.4 \
|
2003-11-10 12:45:10 +00:00
|
|
|
mly.4 \
|
2007-05-27 05:01:19 +00:00
|
|
|
mmc.4 \
|
|
|
|
|
mmcsd.4 \
|
2005-05-10 16:48:03 +00:00
|
|
|
mn.4 \
|
2011-09-15 12:15:36 +00:00
|
|
|
mod_cc.4 \
|
2011-02-17 07:39:53 +00:00
|
|
|
mos.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
mouse.4 \
|
2014-05-02 20:36:20 +00:00
|
|
|
mpr.4 \
|
2010-09-14 21:40:29 +00:00
|
|
|
mps.4 \
|
2003-11-07 17:33:52 +00:00
|
|
|
mpt.4 \
|
2014-05-07 16:16:49 +00:00
|
|
|
mrsas.4 \
|
2006-12-13 02:37:48 +00:00
|
|
|
msk.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
mtio.4 \
|
2003-10-17 15:12:01 +00:00
|
|
|
multicast.4 \
|
2018-06-11 20:19:20 +00:00
|
|
|
muge.4 \
|
2010-05-02 19:28:30 +00:00
|
|
|
mvs.4 \
|
2009-06-10 03:35:40 +00:00
|
|
|
mwl.4 \
|
|
|
|
|
mwlfw.4 \
|
2019-02-26 22:50:01 +00:00
|
|
|
mx25l.4 \
|
2006-06-13 13:53:52 +00:00
|
|
|
mxge.4 \
|
2003-05-18 19:02:38 +00:00
|
|
|
my.4 \
|
2008-08-21 00:40:55 +00:00
|
|
|
${_ndis.4} \
|
2009-07-12 03:19:25 +00:00
|
|
|
net80211.4 \
|
2018-05-06 00:38:29 +00:00
|
|
|
netdump.4 \
|
2014-04-17 12:33:26 +00:00
|
|
|
netfpga10g_nf10bmac.4 \
|
2019-10-17 21:33:01 +00:00
|
|
|
netgdb.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
netgraph.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
netintro.4 \
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
netmap.4 \
|
2006-06-26 23:41:07 +00:00
|
|
|
${_nfe.4} \
|
2005-12-31 11:24:36 +00:00
|
|
|
${_nfsmb.4} \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_async.4 \
|
2004-11-02 10:46:28 +00:00
|
|
|
ngatmbase.4 \
|
2004-03-08 13:46:52 +00:00
|
|
|
ng_atmllc.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_bpf.4 \
|
2000-09-01 01:37:25 +00:00
|
|
|
ng_bridge.4 \
|
2002-11-21 00:06:08 +00:00
|
|
|
ng_bt3c.4 \
|
|
|
|
|
ng_btsocket.4 \
|
2007-05-15 16:28:54 +00:00
|
|
|
ng_car.4 \
|
2005-03-10 09:28:39 +00:00
|
|
|
ng_ccatm.4 \
|
2018-12-09 02:58:53 +00:00
|
|
|
ng_checksum.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_cisco.4 \
|
2006-12-29 13:16:43 +00:00
|
|
|
ng_deflate.4 \
|
2003-11-29 18:14:04 +00:00
|
|
|
ng_device.4 \
|
2004-01-20 10:27:23 +00:00
|
|
|
nge.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_echo.4 \
|
2004-03-10 22:25:25 +00:00
|
|
|
ng_eiface.4 \
|
2002-04-09 21:34:33 +00:00
|
|
|
ng_etf.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ng_ether.4 \
|
2008-12-25 07:34:14 +00:00
|
|
|
ng_ether_echo.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_frame_relay.4 \
|
2001-09-26 23:50:17 +00:00
|
|
|
ng_gif.4 \
|
2003-11-29 18:14:04 +00:00
|
|
|
ng_gif_demux.4 \
|
2002-11-21 00:06:08 +00:00
|
|
|
ng_h4.4 \
|
|
|
|
|
ng_hci.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_hole.4 \
|
2004-04-17 12:42:17 +00:00
|
|
|
ng_hub.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_iface.4 \
|
2005-02-05 17:53:44 +00:00
|
|
|
ng_ipfw.4 \
|
2005-09-28 07:31:18 +00:00
|
|
|
ng_ip_input.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_ksocket.4 \
|
2002-11-21 00:06:08 +00:00
|
|
|
ng_l2cap.4 \
|
2002-08-20 22:00:56 +00:00
|
|
|
ng_l2tp.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_lmi.4 \
|
|
|
|
|
ng_mppc.4 \
|
2005-05-06 15:33:12 +00:00
|
|
|
ng_nat.4 \
|
2004-09-17 19:30:39 +00:00
|
|
|
ng_netflow.4 \
|
2000-11-16 05:58:33 +00:00
|
|
|
ng_one2many.4 \
|
New netgraph node ng_patch(4). It performs data modification of packets
passing through. Modifications are restricted to a subset of C language
operations on unsigned integers of 8, 16, 32 or 64 bit size.
These are: set to new value (=), addition (+=), subtraction (-=),
multiplication (*=), division (/=), negation (= -), bitwise AND (&=),
bitwise OR (|=), bitwise eXclusive OR (^=), shift left (<<=),
shift right (>>=). Several operations are all applied to a packet
sequentially in order they were specified by user.
Submitted by: Maxim Ignatenko <gelraen.ua at gmail.com>
Vadim Goncharov <vadimnuclight at tpu.ru>
Discussed with: net@
Approved by: mav (mentor)
MFC after: 1 month
2010-06-09 12:25:57 +00:00
|
|
|
ng_patch.4 \
|
2019-10-20 20:57:57 +00:00
|
|
|
ng_pipe.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_ppp.4 \
|
|
|
|
|
ng_pppoe.4 \
|
|
|
|
|
ng_pptpgre.4 \
|
2006-12-29 13:16:43 +00:00
|
|
|
ng_pred1.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_rfc1490.4 \
|
|
|
|
|
ng_socket.4 \
|
2004-12-19 16:03:06 +00:00
|
|
|
ng_source.4 \
|
2003-11-29 18:14:04 +00:00
|
|
|
ng_split.4 \
|
2004-04-25 08:52:26 +00:00
|
|
|
ng_sppp.4 \
|
2003-10-27 11:43:20 +00:00
|
|
|
ng_sscfu.4 \
|
|
|
|
|
ng_sscop.4 \
|
2006-06-27 12:45:28 +00:00
|
|
|
ng_tag.4 \
|
2005-06-10 08:44:19 +00:00
|
|
|
ng_tcpmss.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_tee.4 \
|
|
|
|
|
ng_tty.4 \
|
2002-11-21 00:06:08 +00:00
|
|
|
ng_ubt.4 \
|
2004-01-20 10:27:23 +00:00
|
|
|
ng_UI.4 \
|
2003-11-07 09:12:07 +00:00
|
|
|
ng_uni.4 \
|
2000-07-21 10:46:58 +00:00
|
|
|
ng_vjc.4 \
|
2004-03-01 17:22:16 +00:00
|
|
|
ng_vlan.4 \
|
2001-07-08 04:36:52 +00:00
|
|
|
nmdm.4 \
|
2017-08-30 21:16:32 +00:00
|
|
|
${_ntb.4} \
|
2019-08-29 13:46:54 +00:00
|
|
|
${_ntb_hw_amd.4} \
|
2017-08-30 21:16:32 +00:00
|
|
|
${_ntb_hw_intel.4} \
|
|
|
|
|
${_ntb_hw_plx.4} \
|
2016-07-10 10:17:38 +00:00
|
|
|
${_ntb_transport.4} \
|
2017-12-21 04:23:00 +00:00
|
|
|
${_nda.4} \
|
2016-07-10 10:17:38 +00:00
|
|
|
${_if_ntb.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
null.4 \
|
Add an initial NUMA affinity/policy configuration for threads and processes.
This is based on work done by jeff@ and jhb@, as well as the numa.diff
patch that has been circulating when someone asks for first-touch NUMA
on -10 or -11.
* Introduce a simple set of VM policy and iterator types.
* tie the policy types into the vm_phys path for now, mirroring how
the initial first-touch allocation work was enabled.
* add syscalls to control changing thread and process defaults.
* add a global NUMA VM domain policy.
* implement a simple cascade policy order - if a thread policy exists, use it;
if a process policy exists, use it; use the default policy.
* processes inherit policies from their parent processes, threads inherit
policies from their parent threads.
* add a simple tool (numactl) to query and modify default thread/process
policities.
* add documentation for the new syscalls, for numa and for numactl.
* re-enable first touch NUMA again by default, as now policies can be
set in a variety of methods.
This is only relevant for very specific workloads.
This doesn't pretend to be a final NUMA solution.
The previous defaults in -HEAD (with MAXMEMDOM set) can be achieved by
'sysctl vm.default_policy=rr'.
This is only relevant if MAXMEMDOM is set to something other than 1.
Ie, if you're using GENERIC or a modified kernel with non-NUMA, then
this is a glorified no-op for you.
Thank you to Norse Corp for giving me access to rather large
(for FreeBSD!) NUMA machines in order to develop and verify this.
Thank you to Dell for providing me with dual socket sandybridge
and westmere v3 hardware to do NUMA development with.
Thank you to Scott Long at Netflix for providing me with access
to the two-socket, four-domain haswell v3 hardware.
Thank you to Peter Holm for running the stress testing suite
against the NUMA branch during various stages of development!
Tested:
* MIPS (regression testing; non-NUMA)
* i386 (regression testing; non-NUMA GENERIC)
* amd64 (regression testing; non-NUMA GENERIC)
* westmere, 2 socket (thankyou norse!)
* sandy bridge, 2 socket (thankyou dell!)
* ivy bridge, 2 socket (thankyou norse!)
* westmere-EX, 4 socket / 1TB RAM (thankyou norse!)
* haswell, 2 socket (thankyou norse!)
* haswell v3, 2 socket (thankyou dell)
* haswell v3, 2x18 core (thankyou scott long / netflix!)
* Peter Holm ran a stress test suite on this work and found one
issue, but has not been able to verify it (it doesn't look NUMA
related, and he only saw it once over many testing runs.)
* I've tested bhyve instances running in fixed NUMA domains and cpusets;
all seems to work correctly.
Verified:
* intel-pcm - pcm-numa.x and pcm-memory.x, whilst selecting different
NUMA policies for processes under test.
Review:
This was reviewed through phabricator (https://reviews.freebsd.org/D2559)
as well as privately and via emails to freebsd-arch@. The git history
with specific attributes is available at https://github.com/erikarn/freebsd/
in the NUMA branch (https://github.com/erikarn/freebsd/compare/local/adrian_numa_policy).
This has been reviewed by a number of people (stas, rpaulo, kib, ngie,
wblock) but not achieved a clear consensus. My hope is that with further
exposure and testing more functionality can be implemented and evaluated.
Notes:
* The VM doesn't handle unbalanced domains very well, and if you have an overly
unbalanced memory setup whilst under high memory pressure, VM page allocation
may fail leading to a kernel panic. This was a problem in the past, but it's
much more easily triggered now with these tools.
* This work only controls the path through vm_phys; it doesn't yet strongly/predictably
affect contigmalloc, KVA placement, UMA, etc. So, driver placement of memory
isn't really guaranteed in any way. That's next on my plate.
Sponsored by: Norse Corp, Inc.; Dell
2015-07-11 15:21:37 +00:00
|
|
|
numa.4 \
|
2012-10-10 21:38:17 +00:00
|
|
|
${_nvd.4} \
|
2019-08-24 15:38:07 +00:00
|
|
|
${_nvdimm.4} \
|
2012-10-10 21:38:17 +00:00
|
|
|
${_nvme.4} \
|
2010-01-27 00:34:52 +00:00
|
|
|
${_nvram.4} \
|
2011-04-04 22:30:12 +00:00
|
|
|
${_nvram2env.4} \
|
2012-02-17 14:02:44 +00:00
|
|
|
oce.4 \
|
2018-03-30 15:28:25 +00:00
|
|
|
ocs_fc.4\
|
2000-07-21 10:13:46 +00:00
|
|
|
ohci.4 \
|
2001-06-01 21:02:18 +00:00
|
|
|
orm.4 \
|
2015-08-27 23:33:38 +00:00
|
|
|
ow.4 \
|
|
|
|
|
ow_temp.4 \
|
|
|
|
|
owc.4 \
|
2010-02-08 21:24:12 +00:00
|
|
|
${_padlock.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
pass.4 \
|
2002-07-09 05:08:49 +00:00
|
|
|
pccard.4 \
|
|
|
|
|
pccbb.4 \
|
2010-02-08 23:30:28 +00:00
|
|
|
pcf.4 \
|
2020-03-31 06:25:43 +00:00
|
|
|
${_pchtherm.4} \
|
2003-11-29 18:14:04 +00:00
|
|
|
pci.4 \
|
2008-01-04 08:26:22 +00:00
|
|
|
pcib.4 \
|
2001-08-21 20:07:49 +00:00
|
|
|
pcic.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
pcm.4 \
|
2012-09-19 09:34:21 +00:00
|
|
|
${_pf.4} \
|
|
|
|
|
${_pflog.4} \
|
|
|
|
|
${_pfsync.4} \
|
2003-10-17 15:12:01 +00:00
|
|
|
pim.4 \
|
2015-07-24 21:48:53 +00:00
|
|
|
pms.4 \
|
2002-02-15 08:36:06 +00:00
|
|
|
polling.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ppbus.4 \
|
|
|
|
|
ppc.4 \
|
|
|
|
|
ppi.4 \
|
2013-08-28 19:49:32 +00:00
|
|
|
procdesc.4 \
|
2014-04-28 17:58:40 +00:00
|
|
|
proto.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
psm.4 \
|
2002-09-27 17:44:12 +00:00
|
|
|
pst.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
pt.4 \
|
2019-08-19 17:26:04 +00:00
|
|
|
ptnet.4 \
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
The last half year I've been working on a replacement TTY layer for the
FreeBSD kernel. The new TTY layer was designed to improve the following:
- Improved driver model:
The old TTY layer has a driver model that is not abstract enough to
make it friendly to use. A good example is the output path, where the
device drivers directly access the output buffers. This means that an
in-kernel PPP implementation must always convert network buffers into
TTY buffers.
If a PPP implementation would be built on top of the new TTY layer
(still needs a hooks layer, though), it would allow the PPP
implementation to directly hand the data to the TTY driver.
- Improved hotplugging:
With the old TTY layer, it isn't entirely safe to destroy TTY's from
the system. This implementation has a two-step destructing design,
where the driver first abandons the TTY. After all threads have left
the TTY, the TTY layer calls a routine in the driver, which can be
used to free resources (unit numbers, etc).
The pts(4) driver also implements this feature, which means
posix_openpt() will now return PTY's that are created on the fly.
- Improved performance:
One of the major improvements is the per-TTY mutex, which is expected
to improve scalability when compared to the old Giant locking.
Another change is the unbuffered copying to userspace, which is both
used on TTY device nodes and PTY masters.
Upgrading should be quite straightforward. Unlike previous versions,
existing kernel configuration files do not need to be changed, except
when they reference device drivers that are listed in UPDATING.
Obtained from: //depot/projects/mpsafetty/...
Approved by: philip (ex-mentor)
Discussed: on the lists, at BSDCan, at the DevSummit
Sponsored by: Snow B.V., the Netherlands
dcons(4) fixed by: kan
2008-08-20 08:31:58 +00:00
|
|
|
pts.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
pty.4 \
|
2002-02-16 15:12:14 +00:00
|
|
|
puc.4 \
|
2019-06-18 04:32:19 +00:00
|
|
|
pwmc.4 \
|
2013-06-25 17:50:22 +00:00
|
|
|
${_qlxge.4} \
|
2011-11-03 21:20:22 +00:00
|
|
|
${_qlxgb.4} \
|
2013-05-15 17:03:09 +00:00
|
|
|
${_qlxgbe.4} \
|
2017-04-04 06:16:59 +00:00
|
|
|
${_qlnxe.4} \
|
2005-04-18 18:47:38 +00:00
|
|
|
ral.4 \
|
2001-02-18 18:08:43 +00:00
|
|
|
random.4 \
|
2004-06-21 18:20:57 +00:00
|
|
|
rc.4 \
|
2017-05-28 17:25:47 +00:00
|
|
|
rctl.4 \
|
2003-09-09 18:30:34 +00:00
|
|
|
re.4 \
|
2011-01-15 22:07:08 +00:00
|
|
|
rgephy.4 \
|
2013-11-04 14:10:22 +00:00
|
|
|
rights.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
rl.4 \
|
2003-03-11 19:16:42 +00:00
|
|
|
rndtest.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
route.4 \
|
2001-09-05 20:14:59 +00:00
|
|
|
rp.4 \
|
2015-12-31 22:34:16 +00:00
|
|
|
rtwn.4 \
|
|
|
|
|
rtwnfw.4 \
|
rtwn(4), urtwn(4): merge common code, add support for 11ac devices.
All devices:
- add support for rate adaptation via ieee80211_amrr(9);
- use short preamble for transmitted frames when needed;
- multi-bss support:
* for RTL8821AU: 2 VAPs at the same time;
* other: 1 any VAP + 1 sta VAP.
RTL8188CE:
- fix IQ calibration bug (reason of significant speed degradation);
- add h/w crypto acceleration support.
USB:
- A-MPDU Tx support;
- short GI support;
Other:
- add support for RTL8812AU / RTL8821AU chipsets
(a/b/g/n only; no ac yet);
- split merged code into subparts:
* bus glue (usb/*, pci/*, rtl*/usb/*, rtl*/pci/*)
* common (if_rtwn*)
* chip-specific (rtl*/*)
- various other bugfixes.
Due to code reorganization, module names / requirements were changed too:
urtwn urtwnfw -> rtwn rtwn_usb rtwnfw
rtwn rtwnfw -> rtwn rtwn_pci rtwnfw
Tested with RTL8188CE, RTL8188CUS, RTL8188EU and RTL8821AU.
Tested by: kevlo, garga,
Peter Garshtja <peter.garshtja@ambient-md.com>,
Kevin McAleavey <kevin.mcaleavey@knosproject.com>,
Ilias-Dimitrios Vrachnis <id@vrachnis.com>,
<otacilio.neto@bsd.com.br>
Relnotes: yes
2016-10-17 20:38:24 +00:00
|
|
|
rtwn_pci.4 \
|
2003-05-03 10:16:56 +00:00
|
|
|
rue.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
sa.4 \
|
2003-07-21 21:52:48 +00:00
|
|
|
safe.4 \
|
2002-10-25 14:34:24 +00:00
|
|
|
sbp.4 \
|
2003-11-07 09:41:42 +00:00
|
|
|
sbp_targ.4 \
|
2006-03-30 18:39:24 +00:00
|
|
|
scc.4 \
|
2005-04-07 21:57:19 +00:00
|
|
|
sched_4bsd.4 \
|
|
|
|
|
sched_ule.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
screen.4 \
|
|
|
|
|
scsi.4 \
|
2007-10-15 08:17:12 +00:00
|
|
|
sctp.4 \
|
2009-01-07 09:50:57 +00:00
|
|
|
sdhci.4 \
|
2003-01-14 02:57:54 +00:00
|
|
|
sem.4 \
|
2010-09-19 12:54:18 +00:00
|
|
|
send.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ses.4 \
|
2011-11-28 16:25:27 +00:00
|
|
|
${_sfxge.4} \
|
2010-04-14 21:27:48 +00:00
|
|
|
sge.4 \
|
2010-01-15 19:34:40 +00:00
|
|
|
siba.4 \
|
2010-07-03 15:05:14 +00:00
|
|
|
siftr.4 \
|
2009-07-21 12:32:46 +00:00
|
|
|
siis.4 \
|
2010-07-14 13:03:00 +00:00
|
|
|
simplebus.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
sis.4 \
|
|
|
|
|
sk.4 \
|
2018-05-01 00:36:56 +00:00
|
|
|
${_smartpqi.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
smb.4 \
|
|
|
|
|
smbus.4 \
|
|
|
|
|
smp.4 \
|
2014-09-26 09:19:11 +00:00
|
|
|
smsc.4 \
|
2004-08-27 22:06:56 +00:00
|
|
|
snd_ad1816.4 \
|
|
|
|
|
snd_als4000.4 \
|
2005-11-28 07:53:29 +00:00
|
|
|
snd_atiixp.4 \
|
2004-08-27 22:06:56 +00:00
|
|
|
snd_cmi.4 \
|
|
|
|
|
snd_cs4281.4 \
|
2004-09-08 08:28:02 +00:00
|
|
|
snd_csa.4 \
|
2004-08-27 22:06:56 +00:00
|
|
|
snd_ds1.4 \
|
|
|
|
|
snd_emu10k1.4 \
|
2006-07-15 20:31:26 +00:00
|
|
|
snd_emu10kx.4 \
|
2006-06-17 16:43:21 +00:00
|
|
|
snd_envy24.4 \
|
2006-09-30 18:04:57 +00:00
|
|
|
snd_envy24ht.4 \
|
2004-08-27 22:06:56 +00:00
|
|
|
snd_es137x.4 \
|
2004-09-20 20:21:47 +00:00
|
|
|
snd_ess.4 \
|
2005-03-01 05:58:16 +00:00
|
|
|
snd_fm801.4 \
|
2004-09-08 08:28:02 +00:00
|
|
|
snd_gusc.4 \
|
2006-10-01 11:16:31 +00:00
|
|
|
snd_hda.4 \
|
2012-03-01 13:10:18 +00:00
|
|
|
snd_hdspe.4 \
|
2004-11-27 13:49:27 +00:00
|
|
|
snd_ich.4 \
|
2004-09-08 08:28:02 +00:00
|
|
|
snd_maestro3.4 \
|
2007-10-15 08:17:12 +00:00
|
|
|
snd_maestro.4 \
|
2005-10-10 17:46:43 +00:00
|
|
|
snd_mss.4 \
|
2005-02-26 21:42:43 +00:00
|
|
|
snd_neomagic.4 \
|
2004-09-08 08:28:02 +00:00
|
|
|
snd_sbc.4 \
|
2004-08-27 22:06:56 +00:00
|
|
|
snd_solo.4 \
|
2006-09-30 17:30:02 +00:00
|
|
|
snd_spicds.4 \
|
2005-08-15 17:07:37 +00:00
|
|
|
snd_t4dwave.4 \
|
2004-09-08 08:28:02 +00:00
|
|
|
snd_uaudio.4 \
|
2005-03-24 04:45:09 +00:00
|
|
|
snd_via8233.4 \
|
2005-03-09 22:39:26 +00:00
|
|
|
snd_via82c686.4 \
|
2005-03-09 22:31:56 +00:00
|
|
|
snd_vibes.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
snp.4 \
|
2018-07-11 23:59:04 +00:00
|
|
|
spigen.4 \
|
2005-11-11 09:57:32 +00:00
|
|
|
${_spkr.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
splash.4 \
|
|
|
|
|
sppp.4 \
|
|
|
|
|
ste.4 \
|
|
|
|
|
stf.4 \
|
2006-07-25 00:53:14 +00:00
|
|
|
stge.4 \
|
2019-10-11 11:13:47 +00:00
|
|
|
${_superio.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
sym.4 \
|
2002-11-23 19:43:44 +00:00
|
|
|
syncache.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
syncer.4 \
|
|
|
|
|
syscons.4 \
|
|
|
|
|
sysmouse.4 \
|
|
|
|
|
tap.4 \
|
2002-11-25 18:31:07 +00:00
|
|
|
targ.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
tcp.4 \
|
2001-03-09 20:09:28 +00:00
|
|
|
tdfx.4 \
|
Add terasic_mtl(4), a device driver for the Terasic Multi-Touch LCD,
used with Terasic's DE-4 and other similar FPGA boards. This display
is 800x480 and includes a capacitive touch screen, multi-touch
gesture recognition, etc. This device driver depends on a Cambridge-
provided IP core that allows the MTL device to be hooked up to the
Altera Avalon SoC bus, and also provides a VGA-like text frame buffer.
Although it is compiled as a single device driver, it actually
implements a number of different device nodes exporting various
aspects of this multi-function device to userspace:
- Simple memory-mapped driver for the MTL 24-bit pixel frame buffer.
- Simple memory-mapped driver for the MTL control register set.
- Simple memory-mapped driver for the MTL text frame buffer.
- syscons attachment for the MTL text frame buffer.
This driver attaches directly to Nexus as is common for SoC device
drivers, and for the time being is considered BERI-specific, although
in principle it might be used with other hard and soft cores on
Altera FPGAs.
Control registers, including touchscreen input, are simply memory
mapped; in the future it would be desirable to hook up a more
conventional device node that can stream events, support kqueue(2)/
poll(2)/select(2), etc.
This is the first use of syscons on MIPS, as far as I can tell, and
there are some loose ends, such as an inability to use the hardware
cursor. More fundamentally, it appears that syscons(4) assumes that
either a host is PC-like (i386, amd64) *or* it must be using a
graphical frame buffer. While the MTL supports a graphical frame
buffer, using the text frame buffer is preferable for console use.
Fixing this issue in syscons(4) requires non-trivial changes, as the
text frame buffer support assumes that direct memory access can be
done to the text frame buffer without using bus accessor methods,
which is not the case on MIPS. As a workaround for this, we instead
double-buffer and pretend to be a graphical frame buffer exposing
text accessor methods, leading to some quirks in syscons behaviour.
Sponsored by: DARPA, AFRL
2012-08-25 22:35:29 +00:00
|
|
|
terasic_mtl.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
termios.4 \
|
2007-12-26 11:35:07 +00:00
|
|
|
textdump.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
ti.4 \
|
2011-12-20 17:10:34 +00:00
|
|
|
timecounters.4 \
|
2010-08-13 05:01:44 +00:00
|
|
|
${_tpm.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
tty.4 \
|
|
|
|
|
tun.4 \
|
2004-04-14 18:03:30 +00:00
|
|
|
twa.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
twe.4 \
|
2011-10-04 21:40:25 +00:00
|
|
|
tws.4 \
|
2017-05-11 06:57:20 +00:00
|
|
|
udp.4 \
|
|
|
|
|
udplite.4 \
|
2015-12-01 05:12:13 +00:00
|
|
|
ure.4 \
|
2012-08-02 08:46:08 +00:00
|
|
|
vale.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
vga.4 \
|
2004-09-10 20:58:38 +00:00
|
|
|
vge.4 \
|
2010-02-08 23:30:28 +00:00
|
|
|
viapm.4 \
|
2011-12-12 09:50:33 +00:00
|
|
|
${_viawd.4} \
|
2012-01-22 13:51:20 +00:00
|
|
|
${_virtio.4} \
|
|
|
|
|
${_virtio_balloon.4} \
|
|
|
|
|
${_virtio_blk.4} \
|
2014-10-23 04:47:32 +00:00
|
|
|
${_virtio_console.4} \
|
2014-01-18 06:14:38 +00:00
|
|
|
${_virtio_random.4} \
|
2012-10-11 23:41:18 +00:00
|
|
|
${_virtio_scsi.4} \
|
2019-03-21 08:51:32 +00:00
|
|
|
${_vmci.4} \
|
2004-11-16 17:19:04 +00:00
|
|
|
vkbd.4 \
|
2001-07-28 12:27:06 +00:00
|
|
|
vlan.4 \
|
2014-10-20 14:42:42 +00:00
|
|
|
vxlan.4 \
|
2019-10-10 03:12:17 +00:00
|
|
|
${_vmd.4} \
|
2018-01-15 04:52:12 +00:00
|
|
|
${_vmm.4} \
|
2013-08-23 20:47:16 +00:00
|
|
|
${_vmx.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
vr.4 \
|
2014-05-14 21:45:16 +00:00
|
|
|
vt.4 \
|
2010-12-31 00:46:30 +00:00
|
|
|
vte.4 \
|
2012-01-22 13:51:20 +00:00
|
|
|
${_vtnet.4} \
|
2003-06-26 09:50:52 +00:00
|
|
|
watchdog.4 \
|
2012-05-30 02:02:37 +00:00
|
|
|
${_wbwd.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
wi.4 \
|
2001-03-28 12:44:30 +00:00
|
|
|
witness.4 \
|
2003-04-05 19:25:44 +00:00
|
|
|
wlan.4 \
|
2004-12-08 17:47:32 +00:00
|
|
|
wlan_acl.4 \
|
2007-06-15 04:41:15 +00:00
|
|
|
wlan_amrr.4 \
|
2004-12-08 17:47:32 +00:00
|
|
|
wlan_ccmp.4 \
|
|
|
|
|
wlan_tkip.4 \
|
|
|
|
|
wlan_wep.4 \
|
|
|
|
|
wlan_xauth.4 \
|
2017-08-19 17:00:10 +00:00
|
|
|
wmt.4 \
|
2007-11-08 22:09:37 +00:00
|
|
|
${_wpi.4} \
|
2014-02-07 15:00:08 +00:00
|
|
|
wsp.4 \
|
2010-12-13 23:26:31 +00:00
|
|
|
${_xen.4} \
|
2011-02-24 18:08:23 +00:00
|
|
|
xhci.4 \
|
2000-07-21 10:13:46 +00:00
|
|
|
xl.4 \
|
2012-01-26 16:35:09 +00:00
|
|
|
${_xnb.4} \
|
2000-07-21 10:13:46 +00:00
|
|
|
xpt.4 \
|
2016-12-28 09:32:02 +00:00
|
|
|
zero.4
|
1996-04-08 05:15:09 +00:00
|
|
|
|
2019-08-13 03:49:53 +00:00
|
|
|
MLINKS= ads111x.4 ads1013.4 \
|
|
|
|
|
ads111x.4 ads1014.4 \
|
|
|
|
|
ads111x.4 ads1015.4 \
|
|
|
|
|
ads111x.4 ads1113.4 \
|
|
|
|
|
ads111x.4 ads1114.4 \
|
|
|
|
|
ads111x.4 ads1115.4
|
|
|
|
|
MLINKS+=ae.4 if_ae.4
|
2008-11-29 18:21:31 +00:00
|
|
|
MLINKS+=age.4 if_age.4
|
|
|
|
|
MLINKS+=agp.4 agpgart.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=alc.4 if_alc.4
|
2008-11-29 18:21:31 +00:00
|
|
|
MLINKS+=ale.4 if_ale.4
|
MFP4: 221483, 221567, 221568, 221670, 221677, 221678, 221800, 221801,
221804, 221805, 222004, 222006, 222055, 222820, 1135077, 1135118, 1136259
Add atse(4), a driver for the Altera Triple Speed Ethernet MegaCore.
The current driver support gigabit Ethernet speeds only and works with
the MegaCore only in the internal FIFO configuration in the soon to be
open sourced BERI CPU configuration.
Submitted by: bz
MFC after: 3 days
Sponsored by: DARPA/AFRL
2013-10-18 20:44:19 +00:00
|
|
|
MLINKS+=altera_atse.4 atse.4
|
2012-08-26 10:38:02 +00:00
|
|
|
MLINKS+=altera_sdcard.4 altera_sdcardc.4
|
2004-10-07 12:10:25 +00:00
|
|
|
MLINKS+=altq.4 ALTQ.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=ath.4 if_ath.4
|
|
|
|
|
MLINKS+=ath_pci.4 if_ath_pci.4
|
2005-05-19 14:54:48 +00:00
|
|
|
MLINKS+=an.4 if_an.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=aue.4 if_aue.4
|
2003-12-17 10:38:40 +00:00
|
|
|
MLINKS+=axe.4 if_axe.4
|
2006-05-14 15:45:44 +00:00
|
|
|
MLINKS+=bce.4 if_bce.4
|
2003-12-17 10:38:40 +00:00
|
|
|
MLINKS+=bfe.4 if_bfe.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=bge.4 if_bge.4
|
2016-11-15 20:35:29 +00:00
|
|
|
MLINKS+=bnxt.4 if_bnxt.4
|
2009-06-25 17:24:36 +00:00
|
|
|
MLINKS+=bridge.4 if_bridge.4
|
2009-05-16 10:42:00 +00:00
|
|
|
MLINKS+=bwi.4 if_bwi.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=bwn.4 if_bwn.4
|
2012-06-27 10:07:29 +00:00
|
|
|
MLINKS+=${_bxe.4} ${_if_bxe.4}
|
2009-06-15 18:24:04 +00:00
|
|
|
MLINKS+=cas.4 if_cas.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=cdce.4 if_cdce.4
|
2016-01-20 18:47:33 +00:00
|
|
|
MLINKS+=cfi.4 cfid.4
|
2017-12-01 05:57:05 +00:00
|
|
|
MLINKS+=cloudabi.4 cloudabi32.4 \
|
|
|
|
|
cloudabi.4 cloudabi64.4
|
2004-11-30 16:16:34 +00:00
|
|
|
MLINKS+=crypto.4 cryptodev.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=cue.4 if_cue.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=cxgb.4 if_cxgb.4
|
2015-02-20 22:52:24 +00:00
|
|
|
MLINKS+=cxgbe.4 if_cxgbe.4 \
|
2016-12-06 00:01:53 +00:00
|
|
|
cxgbe.4 vcxgbe.4 \
|
|
|
|
|
cxgbe.4 if_vcxgbe.4 \
|
2015-02-20 22:52:24 +00:00
|
|
|
cxgbe.4 cxl.4 \
|
2016-12-06 00:01:53 +00:00
|
|
|
cxgbe.4 if_cxl.4 \
|
|
|
|
|
cxgbe.4 vcxl.4 \
|
|
|
|
|
cxgbe.4 if_vcxl.4 \
|
|
|
|
|
cxgbe.4 cc.4 \
|
|
|
|
|
cxgbe.4 if_cc.4 \
|
|
|
|
|
cxgbe.4 vcc.4 \
|
|
|
|
|
cxgbe.4 if_vcc.4
|
Chelsio T4/T5 VF driver.
The cxgbev/cxlv driver supports Virtual Function devices for Chelsio
T4 and T4 adapters. The VF devices share most of their code with the
existing PF4 driver (cxgbe/cxl) and as such the VF device driver
currently depends on the PF4 driver.
Similar to the cxgbe/cxl drivers, the VF driver includes a t4vf/t5vf
PCI device driver that attaches to the VF device. It then creates
child cxgbev/cxlv devices representing ports assigned to the VF.
By default, the PF driver assigns a single port to each VF.
t4vf_hw.c contains VF-specific routines from the shared code used to
fetch VF-specific parameters from the firmware.
t4_vf.c contains the VF-specific PCI device driver and includes its
own attach routine.
VF devices are required to use a different firmware request when
transmitting packets (which in turn requires a different CPL message
to encapsulate messages). This alternate firmware request does not
permit chaining multiple packets in a single message, so each packet
results in a firmware request. In addition, the different CPL message
requires more detailed information when enabling hardware checksums,
so parse_pkt() on VF devices must examine L2 and L3 headers for all
packets (not just TSO packets) for VF devices. Finally, L2 checksums
on non-UDP/non-TCP packets do not work reliably (the firmware trashes
the IPv4 fragment field), so IPv4 checksums for such packets are
calculated in software.
Most of the other changes in the non-VF-specific code are to expose
various variables and functions private to the PF driver so that they
can be used by the VF driver.
Note that a limited subset of cxgbetool functions are supported on VF
devices including register dumps, scheduler classes, and clearing of
statistics. In addition, TOE is not supported on VF devices, only for
the PF interfaces.
Reviewed by: np
MFC after: 2 months
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D7599
2016-09-07 18:13:57 +00:00
|
|
|
MLINKS+=cxgbev.4 if_cxgbev.4 \
|
|
|
|
|
cxgbev.4 cxlv.4 \
|
2016-12-06 00:01:53 +00:00
|
|
|
cxgbev.4 if_cxlv.4 \
|
|
|
|
|
cxgbev.4 ccv.4 \
|
|
|
|
|
cxgbev.4 if_ccv.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=dc.4 if_dc.4
|
|
|
|
|
MLINKS+=disc.4 if_disc.4
|
2007-04-21 03:00:19 +00:00
|
|
|
MLINKS+=edsc.4 if_edsc.4
|
2019-07-17 02:08:57 +00:00
|
|
|
MLINKS+=em.4 if_em.4 \
|
|
|
|
|
em.4 igb.4 \
|
|
|
|
|
em.4 if_igb.4
|
2008-12-15 13:19:11 +00:00
|
|
|
MLINKS+=enc.4 if_enc.4
|
2009-07-26 12:20:07 +00:00
|
|
|
MLINKS+=epair.4 if_epair.4
|
2008-07-14 18:15:43 +00:00
|
|
|
MLINKS+=et.4 if_et.4
|
2004-01-20 10:27:23 +00:00
|
|
|
MLINKS+=fd.4 stderr.4 \
|
|
|
|
|
fd.4 stdin.4 \
|
|
|
|
|
fd.4 stdout.4
|
2010-07-14 13:03:00 +00:00
|
|
|
MLINKS+=fdt.4 FDT.4
|
2005-07-13 06:08:26 +00:00
|
|
|
MLINKS+=firewire.4 ieee1394.4
|
2004-01-09 17:49:03 +00:00
|
|
|
MLINKS+=fwe.4 if_fwe.4
|
2004-06-14 10:55:03 +00:00
|
|
|
MLINKS+=fwip.4 if_fwip.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=fxp.4 if_fxp.4
|
2003-06-10 18:53:15 +00:00
|
|
|
MLINKS+=gem.4 if_gem.4
|
2003-10-23 05:27:38 +00:00
|
|
|
MLINKS+=geom.4 GEOM.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=gif.4 if_gif.4
|
2014-04-01 14:17:38 +00:00
|
|
|
MLINKS+=gpio.4 gpiobus.4
|
2019-12-09 04:15:01 +00:00
|
|
|
MLINKS+=gpioths.4 dht11.4
|
|
|
|
|
MLINKS+=gpioths.4 dht22.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=gre.4 if_gre.4
|
2003-06-10 18:53:15 +00:00
|
|
|
MLINKS+=hme.4 if_hme.4
|
2010-09-15 04:51:07 +00:00
|
|
|
MLINKS+=hpet.4 acpi_hpet.4
|
2008-02-03 16:38:44 +00:00
|
|
|
MLINKS+=${_hptrr.4} ${_rr232x.4}
|
2010-09-17 04:55:01 +00:00
|
|
|
MLINKS+=${_attimer.4} ${_i8254.4}
|
2004-09-19 06:11:45 +00:00
|
|
|
MLINKS+=ip.4 rawip.4
|
2004-01-20 10:27:23 +00:00
|
|
|
MLINKS+=ipfirewall.4 ipaccounting.4 \
|
|
|
|
|
ipfirewall.4 ipacct.4 \
|
|
|
|
|
ipfirewall.4 ipfw.4
|
2014-09-26 09:54:57 +00:00
|
|
|
MLINKS+=ipheth.4 if_ipheth.4
|
2005-04-18 18:47:38 +00:00
|
|
|
MLINKS+=ipw.4 if_ipw.4
|
|
|
|
|
MLINKS+=iwi.4 if_iwi.4
|
2015-08-10 10:36:08 +00:00
|
|
|
MLINKS+=iwm.4 if_iwm.4
|
2008-11-29 18:21:31 +00:00
|
|
|
MLINKS+=iwn.4 if_iwn.4
|
2014-01-31 23:44:54 +00:00
|
|
|
MLINKS+=ixgbe.4 ix.4
|
|
|
|
|
MLINKS+=ixgbe.4 if_ix.4
|
2008-09-04 20:45:32 +00:00
|
|
|
MLINKS+=ixgbe.4 if_ixgbe.4
|
2015-01-15 22:17:11 +00:00
|
|
|
MLINKS+=ixl.4 if_ixl.4
|
2018-10-12 22:57:52 +00:00
|
|
|
MLINKS+=iavf.4 if_iavf.4
|
2008-11-29 18:21:31 +00:00
|
|
|
MLINKS+=jme.4 if_jme.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=kue.4 if_kue.4
|
2007-04-17 00:57:54 +00:00
|
|
|
MLINKS+=lagg.4 trunk.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=lagg.4 if_lagg.4
|
2006-05-14 15:45:44 +00:00
|
|
|
MLINKS+=le.4 if_le.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=lge.4 if_lge.4
|
2002-01-07 06:48:30 +00:00
|
|
|
MLINKS+=lo.4 loop.4
|
1999-04-14 16:04:55 +00:00
|
|
|
MLINKS+=lp.4 plip.4
|
2008-11-29 18:21:31 +00:00
|
|
|
MLINKS+=malo.4 if_malo.4
|
2001-03-09 20:09:28 +00:00
|
|
|
MLINKS+=md.4 vn.4
|
1999-11-15 23:05:18 +00:00
|
|
|
MLINKS+=mem.4 kmem.4
|
2016-04-24 11:41:36 +00:00
|
|
|
MLINKS+=mfi.4 mfi_linux.4 \
|
|
|
|
|
mfi.4 mfip.4
|
2015-11-23 19:44:39 +00:00
|
|
|
MLINKS+=mlx5en.4 mce.4
|
2005-05-10 16:48:03 +00:00
|
|
|
MLINKS+=mn.4 if_mn.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=mos.4 if_mos.4
|
|
|
|
|
MLINKS+=msk.4 if_msk.4
|
|
|
|
|
MLINKS+=mwl.4 if_mwl.4
|
2006-06-18 14:08:20 +00:00
|
|
|
MLINKS+=mxge.4 if_mxge.4
|
2003-12-17 10:38:40 +00:00
|
|
|
MLINKS+=my.4 if_my.4
|
2008-08-21 00:40:55 +00:00
|
|
|
MLINKS+=${_ndis.4} ${_if_ndis.4}
|
2014-04-17 12:33:26 +00:00
|
|
|
MLINKS+=netfpga10g_nf10bmac.4 if_nf10bmac.4
|
2004-01-20 10:27:23 +00:00
|
|
|
MLINKS+=netintro.4 net.4 \
|
|
|
|
|
netintro.4 networking.4
|
2006-06-26 23:41:07 +00:00
|
|
|
MLINKS+=${_nfe.4} ${_if_nfe.4}
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=nge.4 if_nge.4
|
2015-08-27 23:33:38 +00:00
|
|
|
MLINKS+=ow.4 onewire.4
|
2003-06-05 21:12:55 +00:00
|
|
|
MLINKS+=pccbb.4 cbb.4
|
2004-09-08 08:28:02 +00:00
|
|
|
MLINKS+=pcm.4 snd.4 \
|
|
|
|
|
pcm.4 sound.4
|
2015-07-30 19:08:23 +00:00
|
|
|
MLINKS+=pms.4 pmspcv.4
|
2019-08-19 17:26:04 +00:00
|
|
|
MLINKS+=ptnet.4 if_ptnet.4
|
2005-04-18 18:47:38 +00:00
|
|
|
MLINKS+=ral.4 if_ral.4
|
2003-12-17 10:38:40 +00:00
|
|
|
MLINKS+=re.4 if_re.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=rl.4 if_rl.4
|
rtwn(4), urtwn(4): merge common code, add support for 11ac devices.
All devices:
- add support for rate adaptation via ieee80211_amrr(9);
- use short preamble for transmitted frames when needed;
- multi-bss support:
* for RTL8821AU: 2 VAPs at the same time;
* other: 1 any VAP + 1 sta VAP.
RTL8188CE:
- fix IQ calibration bug (reason of significant speed degradation);
- add h/w crypto acceleration support.
USB:
- A-MPDU Tx support;
- short GI support;
Other:
- add support for RTL8812AU / RTL8821AU chipsets
(a/b/g/n only; no ac yet);
- split merged code into subparts:
* bus glue (usb/*, pci/*, rtl*/usb/*, rtl*/pci/*)
* common (if_rtwn*)
* chip-specific (rtl*/*)
- various other bugfixes.
Due to code reorganization, module names / requirements were changed too:
urtwn urtwnfw -> rtwn rtwn_usb rtwnfw
rtwn rtwnfw -> rtwn rtwn_pci rtwnfw
Tested with RTL8188CE, RTL8188CUS, RTL8188EU and RTL8821AU.
Tested by: kevlo, garga,
Peter Garshtja <peter.garshtja@ambient-md.com>,
Kevin McAleavey <kevin.mcaleavey@knosproject.com>,
Ilias-Dimitrios Vrachnis <id@vrachnis.com>,
<otacilio.neto@bsd.com.br>
Relnotes: yes
2016-10-17 20:38:24 +00:00
|
|
|
MLINKS+=rtwn_pci.4 if_rtwn_pci.4
|
2004-01-14 13:35:15 +00:00
|
|
|
MLINKS+=rue.4 if_rue.4
|
2004-01-20 10:27:23 +00:00
|
|
|
MLINKS+=scsi.4 CAM.4 \
|
|
|
|
|
scsi.4 cam.4 \
|
|
|
|
|
scsi.4 scbus.4 \
|
|
|
|
|
scsi.4 SCSI.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=sge.4 if_sge.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=sis.4 if_sis.4
|
|
|
|
|
MLINKS+=sk.4 if_sk.4
|
1999-04-14 16:04:55 +00:00
|
|
|
MLINKS+=smp.4 SMP.4
|
2014-09-26 09:54:57 +00:00
|
|
|
MLINKS+=smsc.4 if_smsc.4
|
2006-06-17 16:43:21 +00:00
|
|
|
MLINKS+=snd_envy24.4 snd_ak452x.4
|
2007-02-17 10:30:00 +00:00
|
|
|
MLINKS+=snd_sbc.4 snd_sb16.4 \
|
|
|
|
|
snd_sbc.4 snd_sb8.4
|
2005-11-11 09:57:32 +00:00
|
|
|
MLINKS+=${_spkr.4} ${_speaker.4}
|
2003-11-29 18:14:04 +00:00
|
|
|
MLINKS+=splash.4 screensaver.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=ste.4 if_ste.4
|
|
|
|
|
MLINKS+=stf.4 if_stf.4
|
2006-07-25 00:53:14 +00:00
|
|
|
MLINKS+=stge.4 if_stge.4
|
2002-11-23 19:43:44 +00:00
|
|
|
MLINKS+=syncache.4 syncookies.4
|
1999-11-15 23:05:18 +00:00
|
|
|
MLINKS+=syscons.4 sc.4
|
2020-01-13 17:02:42 +00:00
|
|
|
MLINKS+=tap.4 if_tap.4 \
|
|
|
|
|
tap.4 vmnet.4 \
|
|
|
|
|
tap.4 if_vmnet.4
|
2006-03-03 21:37:38 +00:00
|
|
|
MLINKS+=tdfx.4 tdfx_linux.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=ti.4 if_ti.4
|
|
|
|
|
MLINKS+=tun.4 if_tun.4
|
2015-12-01 05:12:13 +00:00
|
|
|
MLINKS+=ure.4 if_ure.4
|
2004-11-24 20:31:30 +00:00
|
|
|
MLINKS+=vge.4 if_vge.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=vlan.4 if_vlan.4
|
2014-10-20 14:42:42 +00:00
|
|
|
MLINKS+=vxlan.4 if_vxlan.4
|
2013-08-23 20:47:16 +00:00
|
|
|
MLINKS+=${_vmx.4} ${_if_vmx.4}
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=vr.4 if_vr.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=vte.4 if_vte.4
|
2012-01-22 13:51:20 +00:00
|
|
|
MLINKS+=${_vtnet.4} ${_if_vtnet.4}
|
2007-10-15 08:17:12 +00:00
|
|
|
MLINKS+=watchdog.4 SW_WATCHDOG.4
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=wi.4 if_wi.4
|
2007-11-08 22:09:37 +00:00
|
|
|
MLINKS+=${_wpi.4} ${_if_wpi.4}
|
2003-02-15 22:28:33 +00:00
|
|
|
MLINKS+=xl.4 if_xl.4
|
1996-05-29 01:10:10 +00:00
|
|
|
|
2010-08-23 22:24:11 +00:00
|
|
|
.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386"
|
2008-08-21 00:40:55 +00:00
|
|
|
_acpi_asus.4= acpi_asus.4
|
Add acpi_asus_wmi(4) -- driver for random extras found on WMI-compatible
Asus laptops. It is alike to acpi_asus(4), but uses WMI interface instead
of separate ACPI device.
On Asus EeePC T101MT netbook it allows to handle hotkeys and on/off WLAN,
Bluetooth, LCD backlight, camera, cardreader and touchpad.
On Asus UX31A ultrabook it allows to handle hotkeys, on/off WLAN, Bluetooth,
Wireless LED, control keyboard backlight brightness, monitor temperature
and fan speed. LCD brightness control doesn't work now for unknown reason,
possibly requiring some video card initialization.
Sponsored by: iXsystems, Inc.
2012-07-02 08:31:29 +00:00
|
|
|
_acpi_asus_wmi.4= acpi_asus_wmi.4
|
2006-05-20 06:21:42 +00:00
|
|
|
_acpi_dock.4= acpi_dock.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_acpi_fujitsu.4=acpi_fujitsu.4
|
2009-06-23 13:17:25 +00:00
|
|
|
_acpi_hp.4= acpi_hp.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_acpi_ibm.4= acpi_ibm.4
|
|
|
|
|
_acpi_panasonic.4=acpi_panasonic.4
|
2014-02-04 18:54:33 +00:00
|
|
|
_acpi_rapidstart.4=acpi_rapidstart.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_acpi_sony.4= acpi_sony.4
|
|
|
|
|
_acpi_toshiba.4=acpi_toshiba.4
|
2009-06-23 13:17:25 +00:00
|
|
|
_acpi_wmi.4= acpi_wmi.4
|
2010-09-06 20:35:48 +00:00
|
|
|
_aesni.4= aesni.4
|
2012-08-15 16:01:45 +00:00
|
|
|
_aout.4= aout.4
|
2011-12-20 13:49:52 +00:00
|
|
|
_apic.4= apic.4
|
2010-09-17 08:44:54 +00:00
|
|
|
_atrtc.4= atrtc.4
|
2010-09-17 04:55:01 +00:00
|
|
|
_attimer.4= attimer.4
|
2010-06-25 15:32:46 +00:00
|
|
|
_aibs.4= aibs.4
|
2009-11-30 11:44:03 +00:00
|
|
|
_amdsbwd.4= amdsbwd.4
|
2005-12-31 11:24:36 +00:00
|
|
|
_amdsmb.4= amdsmb.4
|
2017-09-05 15:13:41 +00:00
|
|
|
_amdsmn.4= amdsmn.4
|
2009-03-13 16:42:24 +00:00
|
|
|
_amdtemp.4= amdtemp.4
|
2007-11-13 11:23:52 +00:00
|
|
|
_asmc.4= asmc.4
|
2012-06-27 10:07:29 +00:00
|
|
|
_bxe.4= bxe.4
|
2016-11-21 19:46:10 +00:00
|
|
|
_bytgpio.4= bytgpio.4
|
2018-02-22 19:12:32 +00:00
|
|
|
_chvgpio.4= chvgpio.4
|
2007-08-23 20:05:09 +00:00
|
|
|
_coretemp.4= coretemp.4
|
2008-08-08 16:26:53 +00:00
|
|
|
_cpuctl.4= cpuctl.4
|
2009-09-09 09:50:31 +00:00
|
|
|
_dpms.4= dpms.4
|
2011-12-28 23:26:58 +00:00
|
|
|
_hpt27xx.4= hpt27xx.4
|
2007-05-11 22:53:09 +00:00
|
|
|
_hptiop.4= hptiop.4
|
|
|
|
|
_hptmv.4= hptmv.4
|
2013-07-06 07:49:41 +00:00
|
|
|
_hptnr.4= hptnr.4
|
2007-12-15 00:56:17 +00:00
|
|
|
_hptrr.4= hptrr.4
|
2016-11-24 05:52:28 +00:00
|
|
|
_hv_kvp.4= hv_kvp.4
|
|
|
|
|
_hv_netvsc.4= hv_netvsc.4
|
|
|
|
|
_hv_storvsc.4= hv_storvsc.4
|
|
|
|
|
_hv_utils.4= hv_utils.4
|
|
|
|
|
_hv_vmbus.4= hv_vmbus.4
|
|
|
|
|
_hv_vss.4= hv_vss.4
|
2020-02-20 06:45:51 +00:00
|
|
|
_hwpstate_intel.4= hwpstate_intel.4
|
2010-09-17 04:55:01 +00:00
|
|
|
_i8254.4= i8254.4
|
2007-08-23 20:05:09 +00:00
|
|
|
_ichwd.4= ichwd.4
|
2012-06-27 10:07:29 +00:00
|
|
|
_if_bxe.4= if_bxe.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_if_ndis.4= if_ndis.4
|
2006-06-26 23:41:07 +00:00
|
|
|
_if_nfe.4= if_nfe.4
|
2009-01-23 05:53:49 +00:00
|
|
|
_if_urtw.4= if_urtw.4
|
2013-08-23 20:47:16 +00:00
|
|
|
_if_vmx.4= if_vmx.4
|
2012-01-22 13:51:20 +00:00
|
|
|
_if_vtnet.4= if_vtnet.4
|
2007-11-08 22:09:37 +00:00
|
|
|
_if_wpi.4= if_wpi.4
|
imcsmb(4): Intel integrated Memory Controller (iMC) SMBus controller driver
imcsmb(4) provides smbus(4) support for the SMBus controller functionality
in the integrated Memory Controllers (iMCs) embedded in Intel Sandybridge-
Xeon, Ivybridge-Xeon, Haswell-Xeon, and Broadwell-Xeon CPUs. Each CPU
implements one or more iMCs, depending on the number of cores; each iMC
implements two SMBus controllers (iMC-SMBs).
*** IMPORTANT NOTE ***
Because motherboard firmware or the BMC might try to use the iMC-SMBs for
monitoring DIMM temperatures and/or managing an NVDIMM, the driver might
need to temporarily disable those functions, or take a hardware interlock,
before using the iMC-SMBs. Details on how to do this may vary from board to
board, and the procedure may be proprietary. It is strongly suggested that
anyone wishing to use this driver contact their motherboard vendor, and
modify the driver as described in the manual page and in the driver itself.
(For what it's worth, the driver as-is has been tested on various SuperMicro
motherboards.)
Reviewed by: avg, jhb
MFC after: 1 week
Relnotes: yes
Sponsored by: Panasas
Differential Revision: https://reviews.freebsd.org/D14447
Discussed with: avg, ian, jhb
Tested by: allanjude (previous version), Panasas
2018-03-03 01:53:51 +00:00
|
|
|
_imcsmb.4= imcsmb.4
|
2006-02-14 17:18:20 +00:00
|
|
|
_ipmi.4= ipmi.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_io.4= io.4
|
2019-10-16 14:57:38 +00:00
|
|
|
_itwd.4= itwd.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_linux.4= linux.4
|
2017-12-21 04:23:00 +00:00
|
|
|
_nda.4= nda.4
|
2008-08-21 00:40:55 +00:00
|
|
|
_ndis.4= ndis.4
|
2006-06-26 23:41:07 +00:00
|
|
|
_nfe.4= nfe.4
|
2007-10-15 08:17:12 +00:00
|
|
|
_nfsmb.4= nfsmb.4
|
2019-08-15 16:27:04 +00:00
|
|
|
_if_ntb.4= if_ntb.4
|
|
|
|
|
_ntb.4= ntb.4
|
2019-08-29 13:46:54 +00:00
|
|
|
_ntb_hw_amd.4= ntb_hw_amd.4
|
2019-08-15 16:27:04 +00:00
|
|
|
_ntb_hw_intel.4= ntb_hw_intel.4
|
|
|
|
|
_ntb_hw_plx.4= ntb_hw_plx.4
|
|
|
|
|
_ntb_transport.4=ntb_transport.4
|
2012-10-10 21:38:17 +00:00
|
|
|
_nvd.4= nvd.4
|
|
|
|
|
_nvme.4= nvme.4
|
2010-01-27 00:34:52 +00:00
|
|
|
_nvram.4= nvram.4
|
2010-02-08 21:24:12 +00:00
|
|
|
_padlock.4= padlock.4
|
2020-03-31 06:25:43 +00:00
|
|
|
_pchtherm.4= pchtherm.4
|
2008-02-03 16:38:44 +00:00
|
|
|
_rr232x.4= rr232x.4
|
2005-11-11 09:57:32 +00:00
|
|
|
_speaker.4= speaker.4
|
2007-10-15 08:17:12 +00:00
|
|
|
_spkr.4= spkr.4
|
2019-10-11 11:13:47 +00:00
|
|
|
_superio.4= superio.4
|
2010-08-13 05:01:44 +00:00
|
|
|
_tpm.4= tpm.4
|
2009-01-23 05:53:49 +00:00
|
|
|
_urtw.4= urtw.4
|
2011-12-12 09:50:33 +00:00
|
|
|
_viawd.4= viawd.4
|
2019-10-11 12:04:38 +00:00
|
|
|
_virtio.4= virtio.4
|
|
|
|
|
_virtio_balloon.4=virtio_balloon.4
|
|
|
|
|
_virtio_blk.4= virtio_blk.4
|
|
|
|
|
_virtio_console.4=virtio_console.4
|
|
|
|
|
_virtio_random.4= virtio_random.4
|
|
|
|
|
_virtio_scsi.4= virtio_scsi.4
|
2019-03-21 08:51:32 +00:00
|
|
|
_vmci.4= vmci.4
|
2019-10-11 12:04:38 +00:00
|
|
|
_vmx.4= vmx.4
|
|
|
|
|
_vtnet.4= vtnet.4
|
2012-05-30 02:02:37 +00:00
|
|
|
_wbwd.4= wbwd.4
|
2007-11-08 22:09:37 +00:00
|
|
|
_wpi.4= wpi.4
|
2010-12-13 23:26:31 +00:00
|
|
|
_xen.4= xen.4
|
2012-01-26 16:35:09 +00:00
|
|
|
_xnb.4= xnb.4
|
2009-09-26 12:45:28 +00:00
|
|
|
|
2005-05-19 14:54:48 +00:00
|
|
|
.endif
|
|
|
|
|
|
2011-11-03 21:20:22 +00:00
|
|
|
.if ${MACHINE_CPUARCH} == "amd64"
|
2015-08-24 19:32:03 +00:00
|
|
|
_ioat.4= ioat.4
|
2019-08-24 15:38:07 +00:00
|
|
|
_nvdimm.4= nvdimm.4
|
2013-06-25 17:50:22 +00:00
|
|
|
_qlxge.4= qlxge.4
|
2011-11-03 21:20:22 +00:00
|
|
|
_qlxgb.4= qlxgb.4
|
2013-05-15 17:03:09 +00:00
|
|
|
_qlxgbe.4= qlxgbe.4
|
2017-04-04 06:16:59 +00:00
|
|
|
_qlnxe.4= qlnxe.4
|
2011-11-28 16:25:27 +00:00
|
|
|
_sfxge.4= sfxge.4
|
2018-05-01 00:36:56 +00:00
|
|
|
_smartpqi.4= smartpqi.4
|
2019-10-10 03:12:17 +00:00
|
|
|
_vmd.4= vmd.4
|
2012-06-25 21:33:45 +00:00
|
|
|
|
2013-06-25 17:50:22 +00:00
|
|
|
MLINKS+=qlxge.4 if_qlxge.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=qlxgb.4 if_qlxgb.4
|
2013-05-15 17:03:09 +00:00
|
|
|
MLINKS+=qlxgbe.4 if_qlxgbe.4
|
2017-04-04 06:16:59 +00:00
|
|
|
MLINKS+=qlnxe.4 if_qlnxe.4
|
2012-06-25 21:33:45 +00:00
|
|
|
MLINKS+=sfxge.4 if_sfxge.4
|
2015-01-26 06:44:48 +00:00
|
|
|
|
|
|
|
|
.if ${MK_BHYVE} != "no"
|
|
|
|
|
_bhyve.4= bhyve.4
|
2018-01-15 04:52:12 +00:00
|
|
|
_vmm.4= vmm.4
|
2015-01-26 06:44:48 +00:00
|
|
|
.endif
|
2011-11-03 21:20:22 +00:00
|
|
|
.endif
|
|
|
|
|
|
2011-04-04 22:30:12 +00:00
|
|
|
.if ${MACHINE_CPUARCH} == "mips"
|
|
|
|
|
_nvram2env.4= nvram2env.4
|
|
|
|
|
.endif
|
2009-11-15 18:31:57 +00:00
|
|
|
|
2018-06-07 11:25:36 +00:00
|
|
|
.if ${MACHINE_CPUARCH} == "powerpc"
|
2020-01-16 11:33:15 +00:00
|
|
|
_if_vtnet.4= if_vtnet.4
|
2018-06-07 11:25:36 +00:00
|
|
|
_nvd.4= nvd.4
|
|
|
|
|
_nvme.4= nvme.4
|
2020-01-16 11:33:15 +00:00
|
|
|
_virtio.4= virtio.4
|
|
|
|
|
_virtio_balloon.4=virtio_balloon.4
|
|
|
|
|
_virtio_blk.4= virtio_blk.4
|
|
|
|
|
_virtio_console.4=virtio_console.4
|
|
|
|
|
_virtio_random.4= virtio_random.4
|
|
|
|
|
_virtio_scsi.4= virtio_scsi.4
|
|
|
|
|
_vtnet.4= vtnet.4
|
2018-06-07 11:25:36 +00:00
|
|
|
.endif
|
|
|
|
|
|
2018-07-20 14:23:01 +00:00
|
|
|
.if empty(MAN_ARCH)
|
|
|
|
|
__arches= ${MACHINE} ${MACHINE_ARCH} ${MACHINE_CPUARCH}
|
|
|
|
|
.elif ${MAN_ARCH} == "all"
|
|
|
|
|
__arches= ${:!/bin/sh -c "/bin/ls -d ${.CURDIR}/man4.*"!:E}
|
|
|
|
|
.else
|
|
|
|
|
__arches= ${MAN_ARCH}
|
2001-02-22 15:28:57 +00:00
|
|
|
.endif
|
2018-07-20 14:23:01 +00:00
|
|
|
.for __arch in ${__arches:O:u}
|
|
|
|
|
.if exists(${.CURDIR}/man4.${__arch})
|
|
|
|
|
SUBDIR+= man4.${__arch}
|
|
|
|
|
.endif
|
|
|
|
|
.endfor
|
1994-05-30 19:09:18 +00:00
|
|
|
|
2015-11-10 13:32:05 +00:00
|
|
|
.if ${MK_BLUETOOTH} != "no"
|
|
|
|
|
MAN+= ng_bluetooth.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2015-01-25 04:52:48 +00:00
|
|
|
.if ${MK_CCD} != "no"
|
|
|
|
|
_ccd.4= ccd.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2015-04-18 21:00:36 +00:00
|
|
|
.if ${MK_CDDL} != "no"
|
2019-04-28 13:07:38 +00:00
|
|
|
_dtrace_provs= dtrace_audit.4 \
|
|
|
|
|
dtrace_io.4 \
|
2017-06-10 21:13:39 +00:00
|
|
|
dtrace_ip.4 \
|
|
|
|
|
dtrace_lockstat.4 \
|
|
|
|
|
dtrace_proc.4 \
|
|
|
|
|
dtrace_sched.4 \
|
2018-05-27 18:43:14 +00:00
|
|
|
dtrace_sctp.4 \
|
2017-06-10 21:13:39 +00:00
|
|
|
dtrace_tcp.4 \
|
2018-07-31 22:56:03 +00:00
|
|
|
dtrace_udp.4 \
|
|
|
|
|
dtrace_udplite.4
|
2019-04-28 13:07:38 +00:00
|
|
|
|
|
|
|
|
MLINKS+= dtrace_audit.4 dtaudit.4
|
2015-04-18 21:00:36 +00:00
|
|
|
.endif
|
|
|
|
|
|
2018-08-17 04:17:51 +00:00
|
|
|
.if ${MK_EFI} != "no"
|
|
|
|
|
MAN+= efidev.4
|
|
|
|
|
|
|
|
|
|
MLINKS+= efidev.4 efirtc.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2015-01-25 04:20:11 +00:00
|
|
|
.if ${MK_ISCSI} != "no"
|
2017-03-30 04:56:27 +00:00
|
|
|
MAN+= cfiscsi.4
|
2015-01-25 04:20:11 +00:00
|
|
|
MAN+= iscsi.4
|
|
|
|
|
MAN+= iscsi_initiator.4
|
2016-06-08 07:33:17 +00:00
|
|
|
MAN+= iser.4
|
2015-01-25 04:20:11 +00:00
|
|
|
.endif
|
|
|
|
|
|
2017-01-19 17:09:11 +00:00
|
|
|
.if ${MK_OFED} != "no"
|
|
|
|
|
MAN+= mlx4ib.4
|
2017-08-23 12:09:37 +00:00
|
|
|
MAN+= mlx5ib.4
|
2017-01-19 17:09:11 +00:00
|
|
|
.endif
|
|
|
|
|
|
2018-03-08 15:21:56 +00:00
|
|
|
.if ${MK_MLX5TOOL} != "no"
|
|
|
|
|
MAN+= mlx5io.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2013-11-08 14:24:47 +00:00
|
|
|
.if ${MK_TESTS} != "no"
|
2017-03-04 11:26:40 +00:00
|
|
|
ATF= ${SRCTOP}/contrib/atf
|
2012-10-22 01:18:41 +00:00
|
|
|
.PATH: ${ATF}/doc
|
|
|
|
|
_atf_test_case.4= atf-test-case.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2012-09-19 09:34:21 +00:00
|
|
|
.if ${MK_PF} != "no"
|
|
|
|
|
_pf.4= pf.4
|
|
|
|
|
_pflog.4= pflog.4
|
|
|
|
|
_pfsync.4= pfsync.4
|
|
|
|
|
.endif
|
|
|
|
|
|
2015-02-04 11:43:19 +00:00
|
|
|
.if ${MK_USB} != "no"
|
|
|
|
|
MAN+= \
|
2015-11-02 00:39:28 +00:00
|
|
|
otus.4 \
|
|
|
|
|
otusfw.4 \
|
|
|
|
|
rsu.4 \
|
|
|
|
|
rsufw.4 \
|
rtwn(4), urtwn(4): merge common code, add support for 11ac devices.
All devices:
- add support for rate adaptation via ieee80211_amrr(9);
- use short preamble for transmitted frames when needed;
- multi-bss support:
* for RTL8821AU: 2 VAPs at the same time;
* other: 1 any VAP + 1 sta VAP.
RTL8188CE:
- fix IQ calibration bug (reason of significant speed degradation);
- add h/w crypto acceleration support.
USB:
- A-MPDU Tx support;
- short GI support;
Other:
- add support for RTL8812AU / RTL8821AU chipsets
(a/b/g/n only; no ac yet);
- split merged code into subparts:
* bus glue (usb/*, pci/*, rtl*/usb/*, rtl*/pci/*)
* common (if_rtwn*)
* chip-specific (rtl*/*)
- various other bugfixes.
Due to code reorganization, module names / requirements were changed too:
urtwn urtwnfw -> rtwn rtwn_usb rtwnfw
rtwn rtwnfw -> rtwn rtwn_pci rtwnfw
Tested with RTL8188CE, RTL8188CUS, RTL8188EU and RTL8821AU.
Tested by: kevlo, garga,
Peter Garshtja <peter.garshtja@ambient-md.com>,
Kevin McAleavey <kevin.mcaleavey@knosproject.com>,
Ilias-Dimitrios Vrachnis <id@vrachnis.com>,
<otacilio.neto@bsd.com.br>
Relnotes: yes
2016-10-17 20:38:24 +00:00
|
|
|
rtwn_usb.4 \
|
2016-12-28 09:32:02 +00:00
|
|
|
rum.4 \
|
|
|
|
|
run.4 \
|
|
|
|
|
runfw.4 \
|
2015-02-04 11:43:19 +00:00
|
|
|
u3g.4 \
|
|
|
|
|
uark.4 \
|
|
|
|
|
uart.4 \
|
|
|
|
|
uath.4 \
|
|
|
|
|
ubsa.4 \
|
|
|
|
|
ubsec.4 \
|
|
|
|
|
ubser.4 \
|
|
|
|
|
ubtbcmfw.4 \
|
|
|
|
|
uchcom.4 \
|
|
|
|
|
ucom.4 \
|
|
|
|
|
ucycom.4 \
|
|
|
|
|
udav.4 \
|
|
|
|
|
udbp.4 \
|
2015-02-15 12:02:17 +00:00
|
|
|
udl.4 \
|
2015-02-04 11:43:19 +00:00
|
|
|
uep.4 \
|
|
|
|
|
ufm.4 \
|
|
|
|
|
ufoma.4 \
|
|
|
|
|
uftdi.4 \
|
|
|
|
|
ugen.4 \
|
2015-06-11 19:06:58 +00:00
|
|
|
ugold.4 \
|
2015-02-04 11:43:19 +00:00
|
|
|
uhci.4 \
|
|
|
|
|
uhid.4 \
|
|
|
|
|
uhso.4 \
|
|
|
|
|
uipaq.4 \
|
|
|
|
|
ukbd.4 \
|
|
|
|
|
uled.4 \
|
|
|
|
|
ulpt.4 \
|
|
|
|
|
umass.4 \
|
|
|
|
|
umcs.4 \
|
|
|
|
|
umct.4 \
|
|
|
|
|
umodem.4 \
|
|
|
|
|
umoscom.4 \
|
|
|
|
|
ums.4 \
|
|
|
|
|
unix.4 \
|
|
|
|
|
upgt.4 \
|
|
|
|
|
uplcom.4 \
|
|
|
|
|
ural.4 \
|
|
|
|
|
urio.4 \
|
|
|
|
|
urndis.4 \
|
|
|
|
|
${_urtw.4} \
|
|
|
|
|
usb.4 \
|
|
|
|
|
usb_quirk.4 \
|
|
|
|
|
usb_template.4 \
|
|
|
|
|
usfs.4 \
|
|
|
|
|
uslcom.4 \
|
|
|
|
|
uvisor.4 \
|
|
|
|
|
uvscom.4 \
|
2016-12-28 09:32:02 +00:00
|
|
|
zyd.4
|
2015-02-04 11:43:19 +00:00
|
|
|
|
2015-11-02 00:39:28 +00:00
|
|
|
MLINKS+=otus.4 if_otus.4
|
|
|
|
|
MLINKS+=rsu.4 if_rsu.4
|
rtwn(4), urtwn(4): merge common code, add support for 11ac devices.
All devices:
- add support for rate adaptation via ieee80211_amrr(9);
- use short preamble for transmitted frames when needed;
- multi-bss support:
* for RTL8821AU: 2 VAPs at the same time;
* other: 1 any VAP + 1 sta VAP.
RTL8188CE:
- fix IQ calibration bug (reason of significant speed degradation);
- add h/w crypto acceleration support.
USB:
- A-MPDU Tx support;
- short GI support;
Other:
- add support for RTL8812AU / RTL8821AU chipsets
(a/b/g/n only; no ac yet);
- split merged code into subparts:
* bus glue (usb/*, pci/*, rtl*/usb/*, rtl*/pci/*)
* common (if_rtwn*)
* chip-specific (rtl*/*)
- various other bugfixes.
Due to code reorganization, module names / requirements were changed too:
urtwn urtwnfw -> rtwn rtwn_usb rtwnfw
rtwn rtwnfw -> rtwn rtwn_pci rtwnfw
Tested with RTL8188CE, RTL8188CUS, RTL8188EU and RTL8821AU.
Tested by: kevlo, garga,
Peter Garshtja <peter.garshtja@ambient-md.com>,
Kevin McAleavey <kevin.mcaleavey@knosproject.com>,
Ilias-Dimitrios Vrachnis <id@vrachnis.com>,
<otacilio.neto@bsd.com.br>
Relnotes: yes
2016-10-17 20:38:24 +00:00
|
|
|
MLINKS+=rtwn_usb.4 if_rtwn_usb.4
|
2016-12-28 09:32:02 +00:00
|
|
|
MLINKS+=rum.4 if_rum.4
|
|
|
|
|
MLINKS+=run.4 if_run.4
|
2015-02-04 11:43:19 +00:00
|
|
|
MLINKS+=u3g.4 u3gstub.4
|
|
|
|
|
MLINKS+=uath.4 if_uath.4
|
|
|
|
|
MLINKS+=udav.4 if_udav.4
|
|
|
|
|
MLINKS+=upgt.4 if_upgt.4
|
|
|
|
|
MLINKS+=ural.4 if_ural.4
|
|
|
|
|
MLINKS+=urndis.4 if_urndis.4
|
|
|
|
|
MLINKS+=${_urtw.4} ${_if_urtw.4}
|
2016-12-28 09:32:02 +00:00
|
|
|
MLINKS+=zyd.4 if_zyd.4
|
2015-02-04 11:43:19 +00:00
|
|
|
.endif
|
|
|
|
|
|
1994-05-30 19:09:18 +00:00
|
|
|
.include <bsd.prog.mk>
|
