2012-11-27 01:17:50 +00:00
|
|
|
# $FreeBSD$
|
|
|
|
|
|
|
|
options FDT
|
|
|
|
|
2019-06-24 01:42:09 +00:00
|
|
|
# Undo options from sys/conf/NOTES that we do not want...
|
2012-11-27 01:17:50 +00:00
|
|
|
|
|
|
|
nooptions COMPAT_FREEBSD4
|
2016-03-16 15:31:09 +00:00
|
|
|
nooptions COMPAT_FREEBSD5
|
|
|
|
nooptions COMPAT_FREEBSD6
|
|
|
|
nooptions COMPAT_FREEBSD7
|
|
|
|
nooptions COMPAT_FREEBSD9
|
2019-06-24 01:42:09 +00:00
|
|
|
nooptions PPC_PROBE_CHIPSET
|
|
|
|
nooptions MAXCPU # value is set in machine/param.h
|
|
|
|
|
|
|
|
# Devices in sys/conf/NOTES for which no such hardware exists on arm,
|
|
|
|
# or the drivers don't compile...
|
2012-11-27 01:17:50 +00:00
|
|
|
|
|
|
|
nodevice sym
|
|
|
|
|
2017-05-19 22:54:45 +00:00
|
|
|
nodevice ccr
|
2015-01-16 01:39:24 +00:00
|
|
|
nodevice cxgbe
|
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
|
|
|
nodevice cxgbev
|
2012-11-27 01:17:50 +00:00
|
|
|
nodevice snd_cmi
|
2015-06-10 15:53:39 +00:00
|
|
|
|
2019-04-13 06:30:45 +00:00
|
|
|
nodevice mpr
|
|
|
|
nodevice mps
|
2019-06-24 01:42:09 +00:00
|
|
|
|
|
|
|
# Add devices which are specific to various arm platforms...
|
|
|
|
|
|
|
|
device twsi # i2c controller on Marvel and Allwinner
|