d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0ac341f145
freebsd-dev/sys/arm/conf/NOTES

82 lines
1.4 KiB
Plaintext
Raw Normal View History

Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
# $FreeBSD$
machine arm
cpu CPU_ARM9E
files "../mv/files.mv"
files "../mv/discovery/files.db78xxx"
files "../mv/kirkwood/files.kirkwood"
files "../mv/orion/files.db88f5xxx"
files "../mv/orion/files.ts7800"
Default to armv5te in LINT on arm. This should fix building LINT there.
2018-08-06 14:40:45 +00:00
makeoptions CONF_CFLAGS+="-march=armv5te"
Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
makeoptions LDFLAGS="-zmuldefs"
makeoptions KERNPHYSADDR=0x00000000
options FDT
options SOC_MV_DISCOVERY
options SOC_MV_KIRKWOOD
options SOC_MV_ORION
arm: enable ARM_MANY_BOARD in NOTES for LINT build Added in r238189, ARM_MANY_BOARD adds support for multiple ARM boards in a single kernel. Include it for LINT builds to avoid duplicate symbol errors when linking with lld. Sponsored by: The FreeBSD Foundation
2017-08-11 19:49:29 +00:00
options ARM_MANY_BOARD
We need nand now that the boards reference it.
2014-01-20 19:57:30 +00:00
device nand
Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
Create the twsi device option in preparation to move the driver to a common location. The device is also found in Allwinner SoCs. Sponsored by: ABT Systems Ltd
2016-02-14 23:42:07 +00:00
# IIC
device twsi
Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
nooptions SMP
nooptions MAXCPU
nooptions COMPAT_FREEBSD4
Remove old COMPAT_FREEBSD options from the ARM kernel configs. We replaced the ABI in 10.0, and have removed support for the old ABI in 11. As such any of these options to provide compatibility prior to 10 are unneeded. Sponsored by: ABT Systems Ltd
2016-03-16 15:31:09 +00:00
nooptions COMPAT_FREEBSD5
nooptions COMPAT_FREEBSD6
nooptions COMPAT_FREEBSD7
nooptions COMPAT_FREEBSD9
ARM: option PPC_PROBE_CHIPSET is applicable only for x86. Don't enable it for ARM LINT config. Approved by: kib (mentor)
2015-12-15 12:51:58 +00:00
nooption PPC_PROBE_CHIPSET
Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
nodevice fdc
nodevice sym
nodevice ukbd
nodevice sc
nodevice blank_saver
nodevice daemon_saver
nodevice dragon_saver
nodevice fade_saver
nodevice fire_saver
nodevice green_saver
nodevice logo_saver
nodevice rain_saver
nodevice snake_saver
nodevice star_saver
nodevice warp_saver
Exclude ccr(4) from arm LINT since it excludes cxgbe(4).
2017-05-19 22:54:45 +00:00
nodevice ccr
Plug cxgbe(4) back into !powerpc && !arm builds, instead of building it on amd64 only.
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
Add NOTES and Makefile in order to generate LINT. NOTES contains pretty much all the union of all the kernel configuration files, including all the CPU types, Marvell SOC types and at91 board types. Any device not supported (read: does not compile) has been removed, which is a fairly small set actually. As such, LINT gives us very good coverage without having to build a zillion kernels.
2012-11-27 01:17:50 +00:00
nodevice snd_cmi
Allow DTrace to be compiled-in to the kernel. This will require for AArch64 as we dont have modules yet. Sponsored by: HEIF5 Sponsored by: ARM Ltd. Differential Revision: https://reviews.freebsd.org/D1997
2015-06-10 15:53:39 +00:00
#
# Enable the kernel DTrace hooks which are required to load the DTrace
# kernel modules.
#
options KDTRACE_HOOKS
# DTrace core
# NOTE: introduces CDDL-licensed components into the kernel
#device dtrace
# DTrace modules
#device dtrace_profile
#device dtrace_sdt
#device dtrace_fbt
#device dtrace_systrace
#device dtrace_prototype
#device dtnfscl
#device dtmalloc
# Alternatively include all the DTrace modules
#device dtraceall
Reference in New Issue Copy Permalink