1993-08-22 02:59:49 +00:00
|
|
|
|
#
|
2000-06-26 10:04:00 +00:00
|
|
|
|
# NOTES -- Lines that can be cut/pasted into kernel and hints configs.
|
1993-08-22 02:59:49 +00:00
|
|
|
|
#
|
2002-04-03 18:09:17 +00:00
|
|
|
|
# This file contains machine dependent kernel configuration notes. For
|
|
|
|
|
# machine independent notes, look in /sys/conf/NOTES.
|
2000-09-09 16:33:48 +00:00
|
|
|
|
#
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
# $FreeBSD$
|
1993-08-22 02:59:49 +00:00
|
|
|
|
#
|
|
|
|
|
|
2004-01-29 21:07:54 +00:00
|
|
|
|
#
|
2004-03-13 00:56:11 +00:00
|
|
|
|
# We want LINT to cover profiling as well.
|
2002-09-19 03:04:07 +00:00
|
|
|
|
profile 2
|
|
|
|
|
|
2010-06-18 18:51:09 +00:00
|
|
|
|
#
|
|
|
|
|
# Enable the kernel DTrace hooks which are required to load the DTrace
|
|
|
|
|
# kernel modules.
|
|
|
|
|
#
|
|
|
|
|
options KDTRACE_HOOKS
|
|
|
|
|
|
2015-06-10 15:53:39 +00:00
|
|
|
|
# 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
|
|
|
|
|
|
1997-04-26 11:46:25 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# SMP OPTIONS:
|
|
|
|
|
#
|
2003-11-11 15:52:31 +00:00
|
|
|
|
# The apic device enables the use of the I/O APIC for interrupt delivery.
|
|
|
|
|
# The apic device can be used in both UP and SMP kernels, but is required
|
|
|
|
|
# for SMP kernels. Thus, the apic device is not strictly an SMP option,
|
|
|
|
|
# but it is a prerequisite for SMP.
|
1997-04-26 11:46:25 +00:00
|
|
|
|
#
|
|
|
|
|
# Notes:
|
|
|
|
|
#
|
2003-11-11 17:14:26 +00:00
|
|
|
|
# HTT CPUs should only be used if they are enabled in the BIOS. For
|
|
|
|
|
# the ACPI case, ACPI only correctly tells us about any HTT CPUs if
|
|
|
|
|
# they are enabled. However, most HTT systems do not list HTT CPUs
|
|
|
|
|
# in the MP Table if they are enabled, thus we guess at the HTT CPUs
|
|
|
|
|
# for the MP Table case. However, we shouldn't try to guess and use
|
2004-06-14 18:37:23 +00:00
|
|
|
|
# these CPUs if HTT is disabled. Thus, HTT guessing is only enabled
|
2003-11-11 17:14:26 +00:00
|
|
|
|
# for the MP Table if the user explicitly asks for it via the
|
|
|
|
|
# MPTABLE_FORCE_HTT option. Do NOT use this option if you have HTT
|
|
|
|
|
# disabled in your BIOS.
|
|
|
|
|
#
|
2005-06-14 14:21:25 +00:00
|
|
|
|
# IPI_PREEMPTION instructs the kernel to preempt threads running on other
|
|
|
|
|
# CPUS if needed. Relies on the PREEMPTION option
|
1997-04-26 11:46:25 +00:00
|
|
|
|
|
|
|
|
|
# Mandatory:
|
2003-11-03 22:47:19 +00:00
|
|
|
|
device apic # I/O apic
|
2003-11-11 17:14:26 +00:00
|
|
|
|
|
|
|
|
|
# Optional:
|
2005-02-28 00:58:06 +00:00
|
|
|
|
options MPTABLE_FORCE_HTT # Enable HTT CPUs with the MP Table
|
2005-06-14 14:21:25 +00:00
|
|
|
|
options IPI_PREEMPTION
|
2003-03-25 23:29:44 +00:00
|
|
|
|
|
2005-02-28 00:55:16 +00:00
|
|
|
|
#
|
|
|
|
|
# Watchdog routines.
|
|
|
|
|
#
|
|
|
|
|
options MP_WATCHDOG
|
|
|
|
|
|
2005-04-30 20:01:00 +00:00
|
|
|
|
# Debugging options.
|
|
|
|
|
#
|
2005-11-22 22:54:42 +00:00
|
|
|
|
options COUNT_XINVLTLB_HITS # Counters for TLB events
|
|
|
|
|
options COUNT_IPIS # Per-CPU IPI interrupt counters
|
2005-04-30 20:01:00 +00:00
|
|
|
|
|
|
|
|
|
|
1997-03-23 11:08:28 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# CPU OPTIONS
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# You must specify at least one CPU (the one you intend to run on);
|
|
|
|
|
# deleting the specification for CPUs you don't need to use may make
|
Stop doing runtime checking on i386 cpus for cpu class. The cpu is
slow enough as it is, without having to constantly check that it really
is an i386 still. It was possible to compile out the conditionals for
faster cpus by leaving out 'I386_CPU', but it was not possible to
unconditionally compile for the i386. You got the runtime checking whether
you wanted it or not. This makes I386_CPU mutually exclusive with the
other cpu types, and tidies things up a little in the process.
Reviewed by: alfred, markm, phk, benno, jlemon, jhb, jake, grog, msmith,
jasone, dcs, des (and a bunch more people who encouraged it)
2001-01-16 09:10:34 +00:00
|
|
|
|
# parts of the system run faster.
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
1999-04-24 21:45:44 +00:00
|
|
|
|
cpu I486_CPU
|
|
|
|
|
cpu I586_CPU # aka Pentium(tm)
|
|
|
|
|
cpu I686_CPU # aka Pentium Pro(tm)
|
1997-03-23 11:08:28 +00:00
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Options for CPU features.
|
|
|
|
|
#
|
2002-02-12 21:13:02 +00:00
|
|
|
|
# CPU_ATHLON_SSE_HACK tries to enable SSE instructions when the BIOS has
|
|
|
|
|
# forgotten to enable them.
|
|
|
|
|
#
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# CPU_BLUELIGHTNING_3X enables triple-clock mode on IBM Blue Lightning
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# CPU if CPU supports it. The default is double-clock mode on
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# BlueLightning CPU box.
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
2004-01-19 01:07:18 +00:00
|
|
|
|
# CPU_BLUELIGHTNING_FPU_OP_CACHE enables FPU operand cache on IBM
|
|
|
|
|
# BlueLightning CPU. It works only with Cyrix FPU, and this option
|
|
|
|
|
# should not be used with Intel FPU.
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
2004-01-19 01:07:18 +00:00
|
|
|
|
# CPU_BTB_EN enables branch target buffer on Cyrix 5x86 (NOTE 1).
|
1997-06-27 13:46:19 +00:00
|
|
|
|
#
|
1997-10-06 08:08:41 +00:00
|
|
|
|
# CPU_CYRIX_NO_LOCK enables weak locking for the entire address space
|
1999-06-15 13:14:56 +00:00
|
|
|
|
# of Cyrix 6x86 and 6x86MX CPUs by setting the NO_LOCK bit of CCR1.
|
|
|
|
|
# Otherwise, the NO_LOCK bit of CCR1 is cleared. (NOTE 3)
|
1997-10-06 08:08:41 +00:00
|
|
|
|
#
|
2004-01-19 01:07:18 +00:00
|
|
|
|
# CPU_DIRECT_MAPPED_CACHE sets L1 cache of Cyrix 486DLC CPU in direct
|
|
|
|
|
# mapped mode. Default is 2-way set associative mode.
|
|
|
|
|
#
|
2004-03-13 00:56:11 +00:00
|
|
|
|
# CPU_DISABLE_5X86_LSSER disables load store serialize (i.e., enables
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# reorder). This option should not be used if you use memory mapped
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# I/O device(s).
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
2002-09-04 19:43:22 +00:00
|
|
|
|
# CPU_ELAN enables support for AMDs ElanSC520 CPU.
|
2003-12-04 19:57:56 +00:00
|
|
|
|
# CPU_ELAN_PPS enables precision timestamp code.
|
2004-03-13 00:56:11 +00:00
|
|
|
|
# CPU_ELAN_XTAL sets the clock crystal frequency in Hz.
|
2003-11-03 10:34:40 +00:00
|
|
|
|
#
|
2004-02-24 04:18:07 +00:00
|
|
|
|
# CPU_ENABLE_LONGRUN enables support for Transmeta Crusoe LongRun
|
|
|
|
|
# technology which allows to restrict power consumption of the CPU by
|
|
|
|
|
# using group of hw.crusoe.* sysctls.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CPU_FASTER_5X86_FPU enables faster FPU exception handler.
|
|
|
|
|
#
|
2004-01-03 18:43:37 +00:00
|
|
|
|
# CPU_GEODE is for the SC1100 Geode embedded processor. This option
|
|
|
|
|
# is necessary because the i8254 timecounter is toast.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CPU_I486_ON_386 enables CPU cache on i486 based CPU upgrade products
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# for i386 machines.
|
1997-06-27 13:46:19 +00:00
|
|
|
|
#
|
1999-06-19 20:20:52 +00:00
|
|
|
|
# CPU_IORT defines I/O clock delay time (NOTE 1). Default values of
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# I/O clock delay time on Cyrix 5x86 and 6x86 are 0 and 7,respectively
|
|
|
|
|
# (no clock delay).
|
|
|
|
|
#
|
2004-01-29 21:07:54 +00:00
|
|
|
|
# CPU_L2_LATENCY specifies the L2 cache latency value. This option is used
|
2000-06-13 09:10:37 +00:00
|
|
|
|
# only when CPU_PPRO2CELERON is defined and Mendocino Celeron is detected.
|
|
|
|
|
# The default value is 5.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CPU_LOOP_EN prevents flushing the prefetch buffer if the destination
|
|
|
|
|
# of a jump is already present in the prefetch buffer on Cyrix 5x86(NOTE
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# 1).
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
2000-06-13 09:10:37 +00:00
|
|
|
|
# CPU_PPRO2CELERON enables L2 cache of Mendocino Celeron CPUs. This option
|
|
|
|
|
# is useful when you use Socket 8 to Socket 370 converter, because most Pentium
|
|
|
|
|
# Pro BIOSs do not enable L2 cache of Mendocino Celeron CPUs.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CPU_RSTK_EN enables return stack on Cyrix 5x86 (NOTE 1).
|
|
|
|
|
#
|
2004-01-19 01:07:18 +00:00
|
|
|
|
# CPU_SOEKRIS enables support www.soekris.com hardware.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CPU_SUSP_HLT enables suspend on HALT. If this option is set, CPU
|
|
|
|
|
# enters suspend mode following execution of HALT instruction.
|
|
|
|
|
#
|
2001-09-14 12:32:04 +00:00
|
|
|
|
# CPU_UPGRADE_HW_CACHE eliminates unneeded cache flush instruction(s).
|
|
|
|
|
#
|
1998-10-06 13:16:29 +00:00
|
|
|
|
# CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD
|
2004-01-29 21:07:54 +00:00
|
|
|
|
# K5/K6/K6-2 CPUs.
|
1997-10-06 08:08:41 +00:00
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# CYRIX_CACHE_WORKS enables CPU cache on Cyrix 486 CPUs with cache
|
|
|
|
|
# flush at hold state.
|
|
|
|
|
#
|
|
|
|
|
# CYRIX_CACHE_REALLY_WORKS enables (1) CPU cache on Cyrix 486 CPUs
|
|
|
|
|
# without cache flush at hold state, and (2) write-back CPU cache on
|
|
|
|
|
# Cyrix 6x86 whose revision < 2.7 (NOTE 2).
|
|
|
|
|
#
|
1997-12-04 21:20:58 +00:00
|
|
|
|
# NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY
|
|
|
|
|
# Pentiums) from locking up when a LOCK CMPXCHG8B instruction is
|
2000-10-27 10:57:33 +00:00
|
|
|
|
# executed. This option is only needed if I586_CPU is also defined,
|
|
|
|
|
# and should be included for any non-Pentium CPU that defines it.
|
1997-12-04 21:20:58 +00:00
|
|
|
|
#
|
1998-12-27 23:23:26 +00:00
|
|
|
|
# NO_MEMORY_HOLE is an optimisation for systems with AMD K6 processors
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# which indicates that the 15-16MB range is *definitely* not being
|
1998-12-27 23:23:26 +00:00
|
|
|
|
# occupied by an ISA memory hole.
|
|
|
|
|
#
|
1997-03-23 11:08:28 +00:00
|
|
|
|
# NOTE 1: The options, CPU_BTB_EN, CPU_LOOP_EN, CPU_IORT,
|
1999-06-19 20:20:52 +00:00
|
|
|
|
# CPU_LOOP_EN and CPU_RSTK_EN should not be used because of CPU bugs.
|
1999-11-05 20:40:01 +00:00
|
|
|
|
# These options may crash your system.
|
1997-03-23 11:08:28 +00:00
|
|
|
|
#
|
|
|
|
|
# NOTE 2: If CYRIX_CACHE_REALLY_WORKS is not set, CPU cache is enabled
|
|
|
|
|
# in write-through mode when revision < 2.7. If revision of Cyrix
|
|
|
|
|
# 6x86 >= 2.7, CPU cache is always enabled in write-back mode.
|
|
|
|
|
#
|
1997-10-06 08:08:41 +00:00
|
|
|
|
# NOTE 3: This option may cause failures for software that requires
|
|
|
|
|
# locked cycles in order to operate correctly.
|
|
|
|
|
#
|
2002-02-12 21:13:02 +00:00
|
|
|
|
options CPU_ATHLON_SSE_HACK
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_BLUELIGHTNING_3X
|
2004-01-19 01:07:18 +00:00
|
|
|
|
options CPU_BLUELIGHTNING_FPU_OP_CACHE
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_BTB_EN
|
|
|
|
|
options CPU_DIRECT_MAPPED_CACHE
|
|
|
|
|
options CPU_DISABLE_5X86_LSSER
|
2002-09-08 15:16:49 +00:00
|
|
|
|
options CPU_ELAN
|
2003-12-04 19:57:56 +00:00
|
|
|
|
options CPU_ELAN_PPS
|
2004-01-19 01:07:18 +00:00
|
|
|
|
options CPU_ELAN_XTAL=32768000
|
2004-02-24 04:18:07 +00:00
|
|
|
|
options CPU_ENABLE_LONGRUN
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_FASTER_5X86_FPU
|
2004-01-03 18:43:37 +00:00
|
|
|
|
options CPU_GEODE
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_I486_ON_386
|
|
|
|
|
options CPU_IORT
|
2000-06-13 09:10:37 +00:00
|
|
|
|
options CPU_L2_LATENCY=5
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_LOOP_EN
|
2000-06-13 09:10:37 +00:00
|
|
|
|
options CPU_PPRO2CELERON
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_RSTK_EN
|
2004-01-19 01:07:18 +00:00
|
|
|
|
options CPU_SOEKRIS
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_SUSP_HLT
|
2001-09-14 12:32:04 +00:00
|
|
|
|
options CPU_UPGRADE_HW_CACHE
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options CPU_WT_ALLOC
|
|
|
|
|
options CYRIX_CACHE_WORKS
|
|
|
|
|
options CYRIX_CACHE_REALLY_WORKS
|
|
|
|
|
#options NO_F00F_HACK
|
1997-03-23 11:08:28 +00:00
|
|
|
|
|
2003-02-13 21:55:13 +00:00
|
|
|
|
# Debug options
|
2004-01-19 01:44:06 +00:00
|
|
|
|
options NPX_DEBUG # enable npx debugging
|
1997-03-23 11:08:28 +00:00
|
|
|
|
|
1995-01-14 02:39:22 +00:00
|
|
|
|
#
|
1996-04-02 18:13:36 +00:00
|
|
|
|
# PERFMON causes the driver for Pentium/Pentium Pro performance counters
|
|
|
|
|
# to be compiled. See perfmon(4) for more information.
|
|
|
|
|
#
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options PERFMON
|
1996-04-02 18:13:36 +00:00
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# NETWORKING OPTIONS
|
|
|
|
|
|
2001-12-14 23:35:33 +00:00
|
|
|
|
#
|
|
|
|
|
# DEVICE_POLLING adds support for mixed interrupt-polling handling
|
|
|
|
|
# of network device drivers, which has significant benefits in terms
|
|
|
|
|
# of robustness to overloads and responsivity, as well as permitting
|
|
|
|
|
# accurate scheduling of the CPU time between kernel network processing
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# and other activities. The drawback is a moderate (up to 1/HZ seconds)
|
2001-12-14 23:35:33 +00:00
|
|
|
|
# potential increase in response times.
|
|
|
|
|
# It is strongly recommended to use HZ=1000 or 2000 with DEVICE_POLLING
|
|
|
|
|
# to achieve smoother behaviour.
|
2005-10-07 08:55:58 +00:00
|
|
|
|
# Additionally, you can enable/disable polling at runtime with help of
|
|
|
|
|
# the ifconfig(8) utility, and select the CPU fraction reserved to
|
|
|
|
|
# userland with the sysctl variable kern.polling.user_frac
|
|
|
|
|
# (default 50, range 0..100).
|
2001-12-14 23:35:33 +00:00
|
|
|
|
#
|
2004-01-11 22:07:19 +00:00
|
|
|
|
# Not all device drivers support this mode of operation at the time of
|
|
|
|
|
# this writing. See polling(4) for more details.
|
2001-12-14 23:35:33 +00:00
|
|
|
|
|
2002-09-09 02:40:59 +00:00
|
|
|
|
options DEVICE_POLLING
|
2001-12-14 23:35:33 +00:00
|
|
|
|
|
2008-03-24 22:23:22 +00:00
|
|
|
|
# BPF_JITTER adds support for BPF just-in-time compiler.
|
|
|
|
|
|
2009-05-10 00:00:25 +00:00
|
|
|
|
options BPF_JITTER
|
2008-03-24 22:23:22 +00:00
|
|
|
|
|
2012-04-12 14:01:06 +00:00
|
|
|
|
# OpenFabrics Enterprise Distribution (Infiniband).
|
|
|
|
|
options OFED
|
|
|
|
|
options OFED_DEBUG_INIT
|
|
|
|
|
|
|
|
|
|
# Sockets Direct Protocol
|
|
|
|
|
options SDP
|
|
|
|
|
options SDP_DEBUG
|
|
|
|
|
|
2012-08-28 11:34:09 +00:00
|
|
|
|
# IP over Infiniband
|
2012-04-12 14:01:06 +00:00
|
|
|
|
options IPOIB
|
|
|
|
|
options IPOIB_DEBUG
|
|
|
|
|
options IPOIB_CM
|
|
|
|
|
|
2000-03-23 16:22:50 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# CLOCK OPTIONS
|
|
|
|
|
|
2007-10-29 22:19:08 +00:00
|
|
|
|
# Provide read/write access to the memory in the clock chip.
|
|
|
|
|
device nvram # Access to rtc cmos via /dev/nvram
|
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# MISCELLANEOUS DEVICES AND OPTIONS
|
1994-10-01 05:43:09 +00:00
|
|
|
|
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
device speaker #Play IBM BASIC-style noises out your speaker
|
2002-11-02 04:18:10 +00:00
|
|
|
|
hint.speaker.0.at="isa"
|
|
|
|
|
hint.speaker.0.port="0x61"
|
2004-01-19 01:26:59 +00:00
|
|
|
|
device gzip #Exec gzipped a.out's. REQUIRES COMPAT_AOUT!
|
2002-09-11 05:33:15 +00:00
|
|
|
|
device apm_saver # Requires APM
|
1998-05-19 08:58:53 +00:00
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
# HARDWARE BUS CONFIGURATION
|
1994-04-07 12:10:31 +00:00
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
2002-04-03 18:09:17 +00:00
|
|
|
|
# ISA bus
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
2017-02-03 12:51:40 +00:00
|
|
|
|
device isa
|
1994-10-21 01:10:54 +00:00
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Options for `isa':
|
|
|
|
|
#
|
1996-03-31 04:18:02 +00:00
|
|
|
|
# AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A
|
|
|
|
|
# interrupt controller. This saves about 0.7-1.25 usec for each interrupt.
|
|
|
|
|
# This option breaks suspend/resume on some portables.
|
|
|
|
|
#
|
1994-12-11 23:52:18 +00:00
|
|
|
|
# AUTO_EOI_2 enables the `automatic EOI' feature for the slave 8259A
|
1996-03-31 04:18:02 +00:00
|
|
|
|
# interrupt controller. This saves about 0.7-1.25 usec for each interrupt.
|
1994-12-11 23:52:18 +00:00
|
|
|
|
# Automatic EOI is documented not to work for for the slave with the
|
|
|
|
|
# original i8259A, but it works for some clones and some integrated
|
|
|
|
|
# versions.
|
|
|
|
|
#
|
1996-06-18 23:21:28 +00:00
|
|
|
|
# MAXMEM specifies the amount of RAM on the machine; if this is not
|
1997-12-31 21:46:17 +00:00
|
|
|
|
# specified, FreeBSD will first read the amount of memory from the CMOS
|
|
|
|
|
# RAM, so the amount of memory will initially be limited to 64MB or 16MB
|
|
|
|
|
# depending on the BIOS. If the BIOS reports 64MB, a memory probe will
|
|
|
|
|
# then attempt to detect the installed amount of RAM. If this probe
|
|
|
|
|
# fails to detect >64MB RAM you will have to use the MAXMEM option.
|
|
|
|
|
# The amount is in kilobytes, so for a machine with 128MB of RAM, it would
|
|
|
|
|
# be 131072 (128 * 1024).
|
1996-06-18 23:21:28 +00:00
|
|
|
|
#
|
1995-05-18 09:17:07 +00:00
|
|
|
|
# BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to
|
|
|
|
|
# reset the CPU for reboot. This is needed on some systems with broken
|
|
|
|
|
# keyboard controllers.
|
1996-04-11 06:19:44 +00:00
|
|
|
|
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options AUTO_EOI_1
|
2000-06-26 10:04:00 +00:00
|
|
|
|
#options AUTO_EOI_2
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
|
2002-10-17 13:47:31 +00:00
|
|
|
|
options MAXMEM=(128*1024)
|
2000-06-26 10:04:00 +00:00
|
|
|
|
#options BROKEN_KEYBOARD_RESET
|
1994-10-21 01:10:54 +00:00
|
|
|
|
|
2001-02-04 12:36:50 +00:00
|
|
|
|
#
|
|
|
|
|
# AGP GART support
|
|
|
|
|
device agp
|
|
|
|
|
|
2009-02-06 20:57:10 +00:00
|
|
|
|
# AGP debugging.
|
2009-05-10 00:00:25 +00:00
|
|
|
|
options AGP_DEBUG
|
2009-02-06 20:57:10 +00:00
|
|
|
|
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# HARDWARE DEVICE CONFIGURATION
|
|
|
|
|
|
2009-09-21 07:08:20 +00:00
|
|
|
|
# To include support for VGA VESA video modes
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options VESA
|
1999-03-10 14:47:41 +00:00
|
|
|
|
|
2002-04-09 18:26:58 +00:00
|
|
|
|
# Turn on extra debugging checks and output for VESA support.
|
|
|
|
|
options VESA_DEBUG
|
2001-08-09 00:05:30 +00:00
|
|
|
|
|
2008-08-23 21:00:40 +00:00
|
|
|
|
device dpms # DPMS suspend & resume via VESA BIOS
|
|
|
|
|
|
2009-09-21 23:58:29 +00:00
|
|
|
|
# x86 real mode BIOS emulator, required by atkbdc/dpms/vesa
|
2014-03-18 14:41:18 +00:00
|
|
|
|
options X86BIOS
|
2009-09-21 23:58:29 +00:00
|
|
|
|
|
1995-11-29 20:02:29 +00:00
|
|
|
|
#
|
2017-02-03 12:51:40 +00:00
|
|
|
|
# Hints for the non-optional Numeric Processing eXtension driver.
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
hint.npx.0.flags="0x0"
|
|
|
|
|
hint.npx.0.irq="13"
|
1996-11-11 20:39:03 +00:00
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# `flags' for npx0:
|
1999-07-25 13:16:09 +00:00
|
|
|
|
# 0x01 don't use the npx registers to optimize bcopy.
|
|
|
|
|
# 0x02 don't use the npx registers to optimize bzero.
|
1996-11-11 20:39:03 +00:00
|
|
|
|
# 0x04 don't use the npx registers to optimize copyin or copyout.
|
|
|
|
|
# The npx registers are normally used to optimize copying and zeroing when
|
|
|
|
|
# all of the following conditions are satisfied:
|
1999-04-24 21:45:44 +00:00
|
|
|
|
# I586_CPU is an option
|
1996-11-11 20:39:03 +00:00
|
|
|
|
# the cpu is an i586 (perhaps not a Pentium)
|
|
|
|
|
# the probe for npx0 succeeds
|
|
|
|
|
# INT 16 exception handling works.
|
|
|
|
|
# Then copying and zeroing using the npx registers is normally 30-100% faster.
|
|
|
|
|
# The flags can be used to control cases where it doesn't work or is slower.
|
2005-01-17 08:35:50 +00:00
|
|
|
|
# Setting them at boot time using hints works right (the optimizations
|
1996-11-11 20:39:03 +00:00
|
|
|
|
# are not used until later in the bootstrap when npx0 is attached).
|
1999-07-26 05:47:31 +00:00
|
|
|
|
# Flag 0x08 automatically disables the i586 optimized routines.
|
1996-11-11 20:39:03 +00:00
|
|
|
|
#
|
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
# Optional devices:
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
|
|
|
|
|
2006-10-20 09:52:27 +00:00
|
|
|
|
# PS/2 mouse
|
|
|
|
|
device psm
|
|
|
|
|
hint.psm.0.at="atkbdc"
|
|
|
|
|
hint.psm.0.irq="12"
|
|
|
|
|
|
|
|
|
|
# Options for psm:
|
|
|
|
|
options PSM_HOOKRESUME #hook the system resume event, useful
|
|
|
|
|
#for some laptops
|
|
|
|
|
options PSM_RESETAFTERSUSPEND #reset the device at the resume event
|
|
|
|
|
|
|
|
|
|
# The keyboard controller; it controls the keyboard and the PS/2 mouse.
|
|
|
|
|
device atkbdc
|
|
|
|
|
hint.atkbdc.0.at="isa"
|
|
|
|
|
hint.atkbdc.0.port="0x060"
|
|
|
|
|
|
|
|
|
|
# The AT keyboard
|
|
|
|
|
device atkbd
|
|
|
|
|
hint.atkbd.0.at="atkbdc"
|
|
|
|
|
hint.atkbd.0.irq="1"
|
|
|
|
|
|
|
|
|
|
# Options for atkbd:
|
|
|
|
|
options ATKBD_DFLT_KEYMAP # specify the built-in keymap
|
2015-03-25 15:51:41 +00:00
|
|
|
|
makeoptions ATKBD_DFLT_KEYMAP=fr.dvorak
|
2006-10-20 09:52:27 +00:00
|
|
|
|
|
|
|
|
|
# `flags' for atkbd:
|
|
|
|
|
# 0x01 Force detection of keyboard, else we always assume a keyboard
|
|
|
|
|
# 0x02 Don't reset keyboard, useful for some newer ThinkPads
|
|
|
|
|
# 0x03 Force detection and avoid reset, might help with certain
|
|
|
|
|
# dockingstations
|
|
|
|
|
# 0x04 Old-style (XT) keyboard support, useful for older ThinkPads
|
|
|
|
|
|
|
|
|
|
# Video card driver for VGA adapters.
|
|
|
|
|
device vga
|
|
|
|
|
hint.vga.0.at="isa"
|
|
|
|
|
|
|
|
|
|
# Options for vga:
|
|
|
|
|
# Try the following option if the mouse pointer is not drawn correctly
|
|
|
|
|
# or font does not seem to be loaded properly. May cause flicker on
|
|
|
|
|
# some systems.
|
|
|
|
|
options VGA_ALT_SEQACCESS
|
|
|
|
|
|
|
|
|
|
# If you can dispense with some vga driver features, you may want to
|
|
|
|
|
# use the following options to save some memory.
|
|
|
|
|
#options VGA_NO_FONT_LOADING # don't save/load font
|
|
|
|
|
#options VGA_NO_MODE_CHANGE # don't change video modes
|
|
|
|
|
|
|
|
|
|
# Older video cards may require this option for proper operation.
|
|
|
|
|
options VGA_SLOW_IOACCESS # do byte-wide i/o's to TS and GDC regs
|
|
|
|
|
|
|
|
|
|
# The following option probably won't work with the LCD displays.
|
|
|
|
|
options VGA_WIDTH90 # support 90 column modes
|
|
|
|
|
|
|
|
|
|
# Debugging.
|
|
|
|
|
options VGA_DEBUG
|
|
|
|
|
|
2014-07-01 00:22:54 +00:00
|
|
|
|
# vt(4) drivers.
|
|
|
|
|
device vt_vga
|
|
|
|
|
|
2009-09-21 07:05:48 +00:00
|
|
|
|
# Linear framebuffer driver for S3 VESA 1.2 cards. Works on top of VESA.
|
|
|
|
|
device s3pci
|
|
|
|
|
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# 3Dfx Voodoo Graphics, Voodoo II /dev/3dfx CDEV support. This will create
|
|
|
|
|
# the /dev/3dfx0 device to work with glide implementations. This should get
|
|
|
|
|
# linked to /dev/3dfx and /dev/voodoo. Note that this is not the same as
|
2002-11-08 20:04:38 +00:00
|
|
|
|
# the tdfx DRI module from XFree86 and is completely unrelated.
|
|
|
|
|
#
|
|
|
|
|
# To enable Linuxulator support, one must also include COMPAT_LINUX in the
|
2006-03-03 21:37:38 +00:00
|
|
|
|
# config as well. The other option is to load both as modules.
|
2002-11-08 20:04:38 +00:00
|
|
|
|
|
2004-03-02 19:15:13 +00:00
|
|
|
|
device tdfx # Enable 3Dfx Voodoo support
|
2006-03-03 21:37:38 +00:00
|
|
|
|
device tdfx_linux # Enable Linuxulator support
|
2002-11-08 20:04:38 +00:00
|
|
|
|
|
2002-07-15 14:28:20 +00:00
|
|
|
|
#
|
|
|
|
|
# ACPI support using the Intel ACPI Component Architecture reference
|
|
|
|
|
# implementation.
|
|
|
|
|
#
|
|
|
|
|
# ACPI_DEBUG enables the use of the debug.acpi.level and debug.acpi.layer
|
|
|
|
|
# kernel environment variables to select initial debugging levels for the
|
|
|
|
|
# Intel ACPICA code. (Note that the Intel code must also have USE_DEBUGGER
|
|
|
|
|
# defined when it is built).
|
2004-03-03 05:51:48 +00:00
|
|
|
|
|
2004-03-02 19:15:13 +00:00
|
|
|
|
device acpi
|
2002-07-15 14:28:20 +00:00
|
|
|
|
options ACPI_DEBUG
|
Import the driver for VT-d DMAR hardware, as specified in the revision
1.3 of Intelб╝ Virtualization Technology for Directed I/O Architecture
Specification. The Extended Context and PASIDs from the rev. 2.2 are
not supported, but I am not aware of any released hardware which
implements them. Code does not use queued invalidation, see comments
for the reason, and does not provide interrupt remapping services.
Code implements the management of the guest address space per domain
and allows to establish and tear down arbitrary mappings, but not
partial unmapping. The superpages are created as needed, but not
promoted. Faults are recorded, fault records could be obtained
programmatically, and printed on the console.
Implement the busdma(9) using DMARs. This busdma backend avoids
bouncing and provides security against misbehaving hardware and driver
bad programming, preventing leaks and corruption of the memory by wild
DMA accesses.
By default, the implementation is compiled into amd64 GENERIC kernel
but disabled; to enable, set hw.dmar.enable=1 loader tunable. Code is
written to work on i386, but testing there was low priority, and
driver is not enabled in GENERIC. Even with the DMAR turned on,
individual devices could be directed to use the bounce busdma with the
hw.busdma.pci<domain>:<bus>:<device>:<function>.bounce=1 tunable. If
DMARs are capable of the pass-through translations, it is used,
otherwise, an identity-mapping page table is constructed.
The driver was tested on Xeon 5400/5500 chipset legacy machine,
Haswell desktop and E5 SandyBridge dual-socket boxes, with ahci(4),
ata(4), bce(4), ehci(4), mfi(4), uhci(4), xhci(4) devices. It also
works with em(4) and igb(4), but there some fixes are needed for
drivers, which are not committed yet. Intel GPUs do not work with
DMAR (yet).
Many thanks to John Baldwin, who explained me the newbus integration;
Peter Holm, who did all testing and helped me to discover and
understand several incredible bugs; and to Jim Harris for the access
to the EDS and BWG and for listening when I have to explain my
findings to somebody.
Sponsored by: The FreeBSD Foundation
MFC after: 1 month
2013-10-28 13:33:29 +00:00
|
|
|
|
options ACPI_DMAR
|
2002-07-15 14:28:20 +00:00
|
|
|
|
|
2009-06-23 13:17:25 +00:00
|
|
|
|
# ACPI WMI Mapping driver
|
|
|
|
|
device acpi_wmi
|
|
|
|
|
|
2004-04-22 21:29:02 +00:00
|
|
|
|
# ACPI Asus Extras (LCD backlight/brightness, video output, etc.)
|
|
|
|
|
device acpi_asus
|
|
|
|
|
|
2005-03-18 09:34:52 +00:00
|
|
|
|
# ACPI Fujitsu Extras (Buttons)
|
|
|
|
|
device acpi_fujitsu
|
|
|
|
|
|
2009-06-23 13:17:25 +00:00
|
|
|
|
# ACPI extras driver for HP laptops
|
|
|
|
|
device acpi_hp
|
|
|
|
|
|
2006-05-07 20:13:18 +00:00
|
|
|
|
# ACPI extras driver for IBM laptops
|
2009-05-10 00:00:25 +00:00
|
|
|
|
device acpi_ibm
|
2006-05-07 20:13:18 +00:00
|
|
|
|
|
2004-07-21 14:47:54 +00:00
|
|
|
|
# ACPI Panasonic Extras (LCD backlight/brightness, video output, etc.)
|
|
|
|
|
device acpi_panasonic
|
|
|
|
|
|
2004-11-15 19:46:22 +00:00
|
|
|
|
# ACPI Sony extra (LCD brightness)
|
|
|
|
|
device acpi_sony
|
|
|
|
|
|
2004-01-11 19:18:38 +00:00
|
|
|
|
# ACPI Toshiba Extras (LCD backlight/brightness, video output, etc.)
|
2004-03-02 19:15:13 +00:00
|
|
|
|
device acpi_toshiba
|
2004-03-01 08:12:56 +00:00
|
|
|
|
|
|
|
|
|
# ACPI Video Extensions (LCD backlight/brightness, video output, etc.)
|
2004-03-02 19:15:13 +00:00
|
|
|
|
device acpi_video
|
2004-01-11 19:18:38 +00:00
|
|
|
|
|
2006-04-15 12:31:34 +00:00
|
|
|
|
# ACPI Docking Station
|
|
|
|
|
device acpi_dock
|
|
|
|
|
|
2010-06-25 15:32:46 +00:00
|
|
|
|
# ACPI ASOC ATK0110 ASUSTeK AI Booster (voltage, temperature and fan sensors)
|
|
|
|
|
device aibs
|
|
|
|
|
|
2007-07-01 22:19:20 +00:00
|
|
|
|
# The cpufreq(4) driver provides support for non-ACPI CPU frequency control
|
|
|
|
|
device cpufreq
|
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
# Network interfaces:
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
|
2013-09-20 20:18:49 +00:00
|
|
|
|
# bxe: Broadcom NetXtreme II (BCM5771X/BCM578XX) PCIe 10Gb Ethernet
|
|
|
|
|
# adapters.
|
2006-01-31 23:11:35 +00:00
|
|
|
|
# ce: Cronyx Tau-PCI/32 sync single/dual port G.703/E1 serial adaptor
|
|
|
|
|
# with 32 HDLC subchannels (requires sppp (default), or NETGRAPH if
|
|
|
|
|
# NETGRAPH_CRONYX is configured)
|
2004-05-17 14:42:59 +00:00
|
|
|
|
# cp: Cronyx Tau-PCI sync single/dual/four port
|
|
|
|
|
# V.35/RS-232/RS-530/RS-449/X.21/G.703/E1/E3/T3/STS-1
|
|
|
|
|
# serial adaptor (requires sppp (default), or NETGRAPH if
|
|
|
|
|
# NETGRAPH_CRONYX is configured)
|
2004-05-17 14:35:32 +00:00
|
|
|
|
# ctau: Cronyx Tau sync dual port V.35/RS-232/RS-530/RS-449/X.21/G.703/E1
|
2004-03-13 00:46:33 +00:00
|
|
|
|
# serial adaptor (requires sppp (default), or NETGRAPH if
|
|
|
|
|
# NETGRAPH_CRONYX is configured)
|
2006-06-12 20:38:17 +00:00
|
|
|
|
# ipw: Intel PRO/Wireless 2100 IEEE 802.11 adapter
|
|
|
|
|
# iwi: Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11 adapters
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# Requires the iwi firmware module
|
2014-08-14 18:29:55 +00:00
|
|
|
|
# iwn: Intel Wireless WiFi Link 1000/105/135/2000/4965/5000/6000/6050 abgn
|
|
|
|
|
# 802.11 network adapters
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# Requires the iwn firmware module
|
2018-02-13 17:04:34 +00:00
|
|
|
|
# mthca: Mellanox HCA InfiniBand
|
2012-04-12 14:01:06 +00:00
|
|
|
|
# mlx4ib: Mellanox ConnectX HCA InfiniBand
|
2016-09-30 08:23:06 +00:00
|
|
|
|
# mlx4en: Mellanox ConnectX HCA Ethernet
|
2006-06-26 23:41:07 +00:00
|
|
|
|
# nfe: nVidia nForce MCP on-board Ethernet Networking (BSD open source)
|
2008-09-10 18:36:58 +00:00
|
|
|
|
# sbni: Granch SBNI12-xx ISA and PCI adapters
|
2013-09-06 20:24:21 +00:00
|
|
|
|
# vmx: VMware VMXNET3 Ethernet (BSD open source)
|
2007-11-08 22:09:37 +00:00
|
|
|
|
# wpi: Intel 3945ABG Wireless LAN controller
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# Requires the wpi firmware module
|
Since this file is doc now, reorganize its structure.
Currently, many drivers support more than one bus of ISA, EISA, MCA,
PCI.
Before this commit, we had, for example, some SCSI devices listed more
than once, iirc, some up to three times (ISA/EISA, MCA, PCI).
Since now the "device" line is common for all of them and they only
differ for the hints stuff, I did the following:
First, list Busses: (E)ISA, MCA, PCI and explain, that only ISA
needs the hints stuff.
Move NIC/SCSI stuff, which were the only split sections, behind these
stuff. Describe all drivers only one time and list all supported
chips.
List all device (+ hints for ISA, if possible).
I've also added few additional supported chips to some drivers, xl for
example and some SCSI drivers.
Also, softupdates is no longer disabled by default, so the comment should
not say, it's not enabled by default due to license issues.
Approved by: asmodai
To come: include PAO devices (imp volunteered for help)
2000-07-09 12:34:53 +00:00
|
|
|
|
|
|
|
|
|
# Order for ISA/EISA devices is important here
|
|
|
|
|
|
2013-09-20 20:18:49 +00:00
|
|
|
|
device bxe # Broadcom NetXtreme II BCM5771X/BCM578XX 10GbE
|
2006-01-31 23:11:35 +00:00
|
|
|
|
device ce
|
2004-05-17 14:42:59 +00:00
|
|
|
|
device cp
|
2005-12-20 23:00:11 +00:00
|
|
|
|
hint.cs.0.at="isa"
|
|
|
|
|
hint.cs.0.port="0x300"
|
2004-03-03 12:43:59 +00:00
|
|
|
|
device ctau
|
|
|
|
|
hint.ctau.0.at="isa"
|
|
|
|
|
hint.ctau.0.port="0x240"
|
|
|
|
|
hint.ctau.0.irq="15"
|
|
|
|
|
hint.ctau.0.drq="7"
|
2005-02-28 00:58:06 +00:00
|
|
|
|
#options NETGRAPH_CRONYX # Enable NETGRAPH support for Cronyx adapter(s)
|
|
|
|
|
options ED_3C503
|
|
|
|
|
options ED_HPP
|
|
|
|
|
options ED_SIC
|
2002-11-06 22:03:53 +00:00
|
|
|
|
hint.ed.0.at="isa"
|
|
|
|
|
hint.ed.0.port="0x280"
|
|
|
|
|
hint.ed.0.irq="5"
|
|
|
|
|
hint.ed.0.maddr="0xd8000"
|
2012-04-04 13:49:22 +00:00
|
|
|
|
device ipw # Intel 2100 wireless NICs.
|
|
|
|
|
device iwi # Intel 2200BG/2225BG/2915ABG wireless NICs.
|
|
|
|
|
device iwn # Intel 4965/1000/5000/6000 wireless NICs.
|
2006-05-17 21:25:23 +00:00
|
|
|
|
# Hint for the i386-only ISA front-end of le(4).
|
|
|
|
|
hint.le.0.at="isa"
|
|
|
|
|
hint.le.0.port="0x280"
|
|
|
|
|
hint.le.0.irq="10"
|
|
|
|
|
hint.le.0.drq="0"
|
2018-02-13 17:04:34 +00:00
|
|
|
|
device mthca # Mellanox HCA InfiniBand
|
2016-09-30 08:23:06 +00:00
|
|
|
|
device mlx4 # Shared code module between IB and Ethernet
|
2012-04-12 14:01:06 +00:00
|
|
|
|
device mlx4ib # Mellanox ConnectX HCA InfiniBand
|
2016-09-30 08:23:06 +00:00
|
|
|
|
device mlx4en # Mellanox ConnectX HCA Ethernet
|
2012-04-04 13:49:22 +00:00
|
|
|
|
device nfe # nVidia nForce MCP on-board Ethernet
|
2008-09-10 18:36:58 +00:00
|
|
|
|
device sbni
|
|
|
|
|
hint.sbni.0.at="isa"
|
|
|
|
|
hint.sbni.0.port="0x210"
|
|
|
|
|
hint.sbni.0.irq="0xefdead"
|
|
|
|
|
hint.sbni.0.flags="0"
|
2013-09-06 20:24:21 +00:00
|
|
|
|
device vmx # VMware VMXNET3 Ethernet
|
2012-04-04 13:49:22 +00:00
|
|
|
|
device wpi # Intel 3945ABG wireless NICs.
|
1999-02-20 11:18:00 +00:00
|
|
|
|
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# IEEE 802.11 adapter firmware modules
|
|
|
|
|
|
|
|
|
|
# Intel PRO/Wireless 2100 firmware:
|
|
|
|
|
# ipwfw: BSS/IBSS/monitor mode firmware
|
|
|
|
|
# ipwbssfw: BSS mode firmware
|
|
|
|
|
# ipwibssfw: IBSS mode firmware
|
|
|
|
|
# ipwmonitorfw: Monitor mode firmware
|
|
|
|
|
# Intel PRO/Wireless 2200BG/2225BG/2915ABG firmware:
|
|
|
|
|
# iwifw: BSS/IBSS/monitor mode firmware
|
|
|
|
|
# iwibssfw: BSS mode firmware
|
|
|
|
|
# iwiibssfw: IBSS mode firmware
|
|
|
|
|
# iwimonitorfw: Monitor mode firmware
|
|
|
|
|
# Intel Wireless WiFi Link 4965/1000/5000/6000 series firmware:
|
2014-08-14 18:29:55 +00:00
|
|
|
|
# iwnfw: Single module to support all devices
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# iwn1000fw: Specific module for the 1000 only
|
2014-08-14 18:29:55 +00:00
|
|
|
|
# iwn105fw: Specific module for the 105 only
|
|
|
|
|
# iwn135fw: Specific module for the 135 only
|
|
|
|
|
# iwn2000fw: Specific module for the 2000 only
|
|
|
|
|
# iwn2030fw: Specific module for the 2030 only
|
|
|
|
|
# iwn4965fw: Specific module for the 4965 only
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# iwn5000fw: Specific module for the 5000 only
|
|
|
|
|
# iwn5150fw: Specific module for the 5150 only
|
|
|
|
|
# iwn6000fw: Specific module for the 6000 only
|
2014-08-14 18:29:55 +00:00
|
|
|
|
# iwn6000g2afw: Specific module for the 6000g2a only
|
|
|
|
|
# iwn6000g2bfw: Specific module for the 6000g2b only
|
2010-07-15 11:26:07 +00:00
|
|
|
|
# iwn6050fw: Specific module for the 6050 only
|
2010-02-08 21:38:42 +00:00
|
|
|
|
# wpifw: Intel 3945ABG Wireless LAN Controller firmware
|
|
|
|
|
|
|
|
|
|
device iwifw
|
|
|
|
|
device iwibssfw
|
|
|
|
|
device iwiibssfw
|
|
|
|
|
device iwimonitorfw
|
|
|
|
|
device ipwfw
|
|
|
|
|
device ipwbssfw
|
|
|
|
|
device ipwibssfw
|
|
|
|
|
device ipwmonitorfw
|
|
|
|
|
device iwnfw
|
|
|
|
|
device iwn1000fw
|
2014-08-14 18:29:55 +00:00
|
|
|
|
device iwn105fw
|
|
|
|
|
device iwn135fw
|
|
|
|
|
device iwn2000fw
|
|
|
|
|
device iwn2030fw
|
|
|
|
|
device iwn4965fw
|
2010-02-08 21:38:42 +00:00
|
|
|
|
device iwn5000fw
|
|
|
|
|
device iwn5150fw
|
|
|
|
|
device iwn6000fw
|
2014-08-14 18:29:55 +00:00
|
|
|
|
device iwn6000g2afw
|
|
|
|
|
device iwn6000g2bfw
|
2010-07-15 11:26:07 +00:00
|
|
|
|
device iwn6050fw
|
2010-02-08 21:38:42 +00:00
|
|
|
|
device wpifw
|
|
|
|
|
|
2017-08-30 21:16:32 +00:00
|
|
|
|
#
|
|
|
|
|
# Non-Transparent Bridge (NTB) drivers
|
|
|
|
|
#
|
|
|
|
|
device if_ntb # Virtual NTB network interface
|
|
|
|
|
device ntb_transport # NTB packet transport driver
|
|
|
|
|
device ntb # NTB hardware interface
|
|
|
|
|
device ntb_hw_intel # Intel NTB hardware driver
|
|
|
|
|
device ntb_hw_plx # PLX NTB hardware driver
|
|
|
|
|
|
2003-02-26 23:36:59 +00:00
|
|
|
|
#
|
|
|
|
|
# ATA raid adapters
|
|
|
|
|
#
|
|
|
|
|
device pst
|
|
|
|
|
|
2005-03-31 20:21:43 +00:00
|
|
|
|
#
|
|
|
|
|
# Areca 11xx and 12xx series of SATA II RAID controllers.
|
|
|
|
|
# CAM is required.
|
|
|
|
|
#
|
|
|
|
|
device arcmsr # Areca SATA II RAID
|
|
|
|
|
|
2004-04-02 18:50:56 +00:00
|
|
|
|
#
|
|
|
|
|
# 3ware 9000 series PATA/SATA RAID controller driver and options.
|
|
|
|
|
# The driver is implemented as a SIM, and so, needs the CAM infrastructure.
|
|
|
|
|
#
|
2005-02-28 00:58:06 +00:00
|
|
|
|
options TWA_DEBUG # 0-10; 10 prints the most messages.
|
2004-04-02 18:50:56 +00:00
|
|
|
|
device twa # 3ware 9000 series PATA/SATA RAID
|
|
|
|
|
|
2002-09-26 18:16:28 +00:00
|
|
|
|
#
|
|
|
|
|
# Adaptec FSA RAID controllers, including integrated DELL controllers,
|
|
|
|
|
# the Dell PERC 2/QC and the HP NetRAID-4M
|
|
|
|
|
device aac
|
|
|
|
|
device aacp # SCSI Passthrough interface (optional, CAM required)
|
|
|
|
|
|
2013-05-24 09:22:43 +00:00
|
|
|
|
#
|
|
|
|
|
# Adaptec by PMC RAID controllers, Series 6/7/8 and upcoming families
|
|
|
|
|
device aacraid # Container interface, CAM required
|
|
|
|
|
|
2011-12-28 23:26:58 +00:00
|
|
|
|
#
|
|
|
|
|
# Highpoint RocketRAID 27xx.
|
|
|
|
|
device hpt27xx
|
|
|
|
|
|
2004-10-24 08:53:40 +00:00
|
|
|
|
#
|
2007-12-15 00:56:17 +00:00
|
|
|
|
# Highpoint RocketRAID 182x.
|
2004-10-24 08:53:40 +00:00
|
|
|
|
device hptmv
|
|
|
|
|
|
2013-07-06 07:49:41 +00:00
|
|
|
|
#
|
|
|
|
|
# Highpoint DC7280 and R750.
|
|
|
|
|
device hptnr
|
|
|
|
|
|
2007-12-15 00:56:17 +00:00
|
|
|
|
#
|
|
|
|
|
# Highpoint RocketRAID. Supports RR172x, RR222x, RR2240, RR232x, RR2340,
|
|
|
|
|
# RR2210, RR174x, RR2522, RR231x, RR230x.
|
|
|
|
|
device hptrr
|
|
|
|
|
|
2007-05-09 15:55:45 +00:00
|
|
|
|
#
|
|
|
|
|
# Highpoint RocketRaid 3xxx series SATA RAID
|
|
|
|
|
device hptiop
|
|
|
|
|
|
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
|
|
|
|
#
|
|
|
|
|
# Intel integrated Memory Controller (iMC) SMBus controller
|
|
|
|
|
# Sandybridge-Xeon, Ivybridge-Xeon, Haswell-Xeon, Broadwell-Xeon
|
|
|
|
|
device imcsmb
|
|
|
|
|
|
2003-05-11 06:39:05 +00:00
|
|
|
|
#
|
|
|
|
|
# IBM (now Adaptec) ServeRAID controllers
|
|
|
|
|
device ips
|
|
|
|
|
|
2012-01-31 19:38:18 +00:00
|
|
|
|
#
|
|
|
|
|
# Intel C600 (Patsburg) integrated SAS controller
|
|
|
|
|
device isci
|
2014-03-18 14:41:18 +00:00
|
|
|
|
options ISCI_LOGGING # enable debugging in isci HAL
|
2012-01-31 19:38:18 +00:00
|
|
|
|
|
2012-09-17 19:26:33 +00:00
|
|
|
|
#
|
|
|
|
|
# NVM Express (NVMe) support
|
|
|
|
|
device nvme # base NVMe driver
|
|
|
|
|
device nvd # expose NVMe namespaces as disks, depends on nvme
|
|
|
|
|
|
2015-07-07 13:17:02 +00:00
|
|
|
|
#
|
|
|
|
|
# PMC-Sierra SAS/SATA controller
|
|
|
|
|
device pmspcv
|
2003-07-21 21:51:24 +00:00
|
|
|
|
#
|
|
|
|
|
# SafeNet crypto driver: can be moved to the MI NOTES as soon as
|
|
|
|
|
# it's tested on a big-endian machine
|
|
|
|
|
#
|
|
|
|
|
device safe # SafeNet 1141
|
2005-02-28 00:58:06 +00:00
|
|
|
|
options SAFE_DEBUG # enable debugging support: hw.safe.debug
|
|
|
|
|
options SAFE_RNDTEST # enable rndtest support
|
2003-07-21 21:51:24 +00:00
|
|
|
|
|
2011-05-15 14:01:23 +00:00
|
|
|
|
#
|
|
|
|
|
# glxiic is an I2C driver for the AMD Geode LX CS5536 System Management Bus
|
|
|
|
|
# controller. Requires 'device iicbus'.
|
|
|
|
|
#
|
|
|
|
|
device glxiic # AMD Geode LX CS5536 System Management Bus
|
|
|
|
|
|
2008-08-09 14:52:31 +00:00
|
|
|
|
#
|
|
|
|
|
# glxsb is a driver for the Security Block in AMD Geode LX processors.
|
|
|
|
|
# Requires 'device crypto'.
|
|
|
|
|
#
|
|
|
|
|
device glxsb # AMD Geode LX Security Block
|
|
|
|
|
|
2013-01-13 07:14:16 +00:00
|
|
|
|
#
|
|
|
|
|
# VirtIO support
|
2013-03-06 07:17:53 +00:00
|
|
|
|
#
|
|
|
|
|
# The virtio entry provides a generic bus for use by the device drivers.
|
|
|
|
|
# It must be combined with an interface that communicates with the host.
|
|
|
|
|
# Multiple such interfaces defined by the VirtIO specification. FreeBSD
|
|
|
|
|
# only has support for PCI. Therefore, virtio_pci must be statically
|
|
|
|
|
# compiled in or loaded as a module for the device drivers to function.
|
|
|
|
|
#
|
2013-01-13 07:14:16 +00:00
|
|
|
|
device virtio # Generic VirtIO bus (required)
|
|
|
|
|
device virtio_pci # VirtIO PCI Interface
|
|
|
|
|
device vtnet # VirtIO Ethernet device
|
|
|
|
|
device virtio_blk # VirtIO Block device
|
|
|
|
|
device virtio_scsi # VirtIO SCSI device
|
|
|
|
|
device virtio_balloon # VirtIO Memory Balloon device
|
2014-01-18 06:14:38 +00:00
|
|
|
|
device virtio_random # VirtIO Entropy device
|
2014-11-03 22:37:10 +00:00
|
|
|
|
device virtio_console # VirtIO Console device
|
2013-01-13 07:14:16 +00:00
|
|
|
|
|
2013-12-05 00:54:38 +00:00
|
|
|
|
device hyperv # HyperV drivers
|
|
|
|
|
|
2003-07-21 21:51:24 +00:00
|
|
|
|
#####################################################################
|
|
|
|
|
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
1995-07-16 08:55:04 +00:00
|
|
|
|
# Miscellaneous hardware:
|
1994-10-21 01:10:54 +00:00
|
|
|
|
#
|
|
|
|
|
# apm: Laptop Advanced Power Management (experimental)
|
2006-09-22 22:11:29 +00:00
|
|
|
|
# ipmi: Intelligent Platform Management Interface
|
2005-07-20 16:57:53 +00:00
|
|
|
|
# smapi: System Management Application Program Interface driver
|
|
|
|
|
# smbios: DMI/SMBIOS entry point
|
|
|
|
|
# vpd: Vital Product Data kernel interface
|
2009-02-07 00:06:13 +00:00
|
|
|
|
# pbio: Parallel (8255 PPI) basic I/O (mode 0) port (e.g. Advantech PCL-724)
|
2007-12-28 22:50:04 +00:00
|
|
|
|
# asmc: Apple System Management Controller
|
2009-02-08 12:40:33 +00:00
|
|
|
|
# si: Specialix International SI/XIO or SX intelligent serial card driver
|
2010-09-19 14:40:37 +00:00
|
|
|
|
# tpm: Trusted Platform Module
|
1995-04-28 00:51:40 +00:00
|
|
|
|
|
1996-04-22 19:40:28 +00:00
|
|
|
|
# Notes on APM
|
1997-03-29 11:07:12 +00:00
|
|
|
|
# The flags takes the following meaning for apm0:
|
|
|
|
|
# 0x0020 Statclock is broken.
|
1999-02-04 22:34:23 +00:00
|
|
|
|
|
1995-09-23 08:52:30 +00:00
|
|
|
|
# Notes on the Specialix SI/XIO driver:
|
1995-08-09 12:58:50 +00:00
|
|
|
|
# The host card is memory, not IO mapped.
|
|
|
|
|
# The Rev 1 host cards use a 64K chunk, on a 32K boundary.
|
|
|
|
|
# The Rev 2 host cards use a 32K chunk, on a 32K boundary.
|
|
|
|
|
# The cards can use an IRQ of 11, 12 or 15.
|
|
|
|
|
|
2000-12-11 19:41:48 +00:00
|
|
|
|
# Notes on the Sony Programmable I/O controller
|
|
|
|
|
# This is a temporary driver that should someday be replaced by something
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# that hooks into the ACPI layer. The device is hooked to the PIIX4's
|
2000-12-11 19:41:48 +00:00
|
|
|
|
# General Device 10 decoder, which means you have to fiddle with PCI
|
|
|
|
|
# registers to map it in, even though it is otherwise treated here as
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# an ISA device. At the moment, the driver polls, although the device
|
|
|
|
|
# is capable of generating interrupts. It largely undocumented.
|
2000-12-11 19:41:48 +00:00
|
|
|
|
# The port location in the hint is where you WANT the device to be
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# mapped. 0x10a0 seems to be traditional. At the moment the jogdial
|
2004-01-29 21:07:54 +00:00
|
|
|
|
# is the only thing truly supported, but apparently a fair percentage
|
2000-12-11 19:41:48 +00:00
|
|
|
|
# of the Vaio extra features are controlled by this device.
|
|
|
|
|
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
device apm
|
|
|
|
|
hint.apm.0.flags="0x20"
|
2006-09-22 22:11:29 +00:00
|
|
|
|
device ipmi
|
2005-07-20 16:57:53 +00:00
|
|
|
|
device smapi
|
|
|
|
|
device smbios
|
|
|
|
|
device vpd
|
2004-10-07 16:21:03 +00:00
|
|
|
|
device pbio
|
|
|
|
|
hint.pbio.0.at="isa"
|
|
|
|
|
hint.pbio.0.port="0x360"
|
2007-12-28 22:50:04 +00:00
|
|
|
|
device asmc
|
2010-09-19 14:40:37 +00:00
|
|
|
|
device tpm
|
2013-08-21 22:43:29 +00:00
|
|
|
|
device padlock_rng # VIA Padlock RNG
|
|
|
|
|
device rdrand_rng # Intel Bull Mountain RNG
|
2013-10-04 17:21:01 +00:00
|
|
|
|
device aesni # AES-NI OpenCrypto module
|
2009-02-08 12:40:33 +00:00
|
|
|
|
|
1995-07-16 10:31:26 +00:00
|
|
|
|
#
|
|
|
|
|
# Laptop/Notebook options:
|
|
|
|
|
#
|
|
|
|
|
# See also:
|
1996-01-30 23:02:38 +00:00
|
|
|
|
# apm under `Miscellaneous hardware'
|
1995-07-16 10:31:26 +00:00
|
|
|
|
# above.
|
|
|
|
|
|
|
|
|
|
# For older notebooks that signal a powerfail condition (external
|
|
|
|
|
# power supply dropped, or battery state low) by issuing an NMI:
|
|
|
|
|
|
1999-06-29 18:58:27 +00:00
|
|
|
|
options POWERFAIL_NMI # make it beep instead of panicing
|
1995-10-10 04:03:12 +00:00
|
|
|
|
|
1998-09-03 20:58:34 +00:00
|
|
|
|
#
|
|
|
|
|
# I2C Bus
|
|
|
|
|
#
|
|
|
|
|
# Philips i2c bus support is provided by the `iicbus' device.
|
|
|
|
|
#
|
|
|
|
|
# Supported interfaces:
|
|
|
|
|
# pcf Philips PCF8584 ISA-bus controller
|
|
|
|
|
#
|
Borrow phk's axe and apply the next stage of config(8)'s evolution.
Use Warner Losh's "hint" driver to decode ascii strings to fill the
resource table at boot time.
config(8) no longer generates an ioconf.c table - ie: the configuration
no longer has to be compiled into the kernel. You can reconfigure your
isa devices with the likes of this at loader(8) time:
set hint.ed.0.port=0x320
userconfig will be rewritten to use this style interface one day and will
move to /boot/userconfig.4th or something like that.
It is still possible to statically compile in a set of hints into a kernel
if you do not wish to use loader(8). See the "hints" directive in GENERIC
as an example.
All device wiring has been moved out of config(8). There is a set of
helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98)
that extract the 'at isa? port foo irq bar' from the old files and produces
a hints file. If you install this file as /boot/device.hints (and update
/boot/defaults/loader.conf - You can do a build/install in sys/boot) then
loader will load it automatically for you. You can also compile in the
hints directly with: hints "device.hints" as well.
There are a few things that I'm not too happy with yet. Under this scheme,
things like LINT would no longer be useful as "documentation" of settings.
I have renamed this file to 'NOTES' and stored the example hints strings
in it. However... this is not something that config(8) understands, so
there is a script that extracts the build-specific data from the
documentation file (NOTES) to produce a LINT that can be config'ed and
built. A stack of man4 pages will need updating. :-/
Also, since there is no longer a difference between 'device' and
'pseudo-device' I collapsed the two together, and the resulting 'device'
takes a 'number of units' for devices that still have it statically
allocated. eg: 'device fe 4' will compile the fe driver with NFE set
to 4. You can then set hints for 4 units (0 - 3). Also note that
'device fe0' will be interpreted as "zero units of 'fe'" which would be
bad, so there is a config warning for this. This is only needed for
old drivers that still have static limits on numbers of units.
All the statically limited drivers that I could find were marked.
Please exercise EXTREME CAUTION when transitioning!
Moral support by: phk, msmith, dfr, asmodai, imp, and others
2000-06-13 22:28:50 +00:00
|
|
|
|
device pcf
|
|
|
|
|
hint.pcf.0.at="isa"
|
|
|
|
|
hint.pcf.0.port="0x320"
|
|
|
|
|
hint.pcf.0.irq="5"
|
1998-09-03 20:58:34 +00:00
|
|
|
|
|
2004-08-29 11:11:31 +00:00
|
|
|
|
#
|
|
|
|
|
# Hardware watchdog timers:
|
|
|
|
|
#
|
|
|
|
|
# ichwd: Intel ICH watchdog timer
|
2009-11-30 11:44:03 +00:00
|
|
|
|
# amdsbwd: AMD SB7xx watchdog timer
|
2011-12-20 00:16:52 +00:00
|
|
|
|
# viawd: VIA south bridge watchdog timer
|
2012-03-06 18:44:52 +00:00
|
|
|
|
# wbwd: Winbond watchdog timer
|
2004-08-29 11:11:31 +00:00
|
|
|
|
#
|
|
|
|
|
device ichwd
|
2009-11-30 11:44:03 +00:00
|
|
|
|
device amdsbwd
|
2011-12-12 09:50:33 +00:00
|
|
|
|
device viawd
|
2012-03-06 18:44:52 +00:00
|
|
|
|
device wbwd
|
2004-08-29 11:11:31 +00:00
|
|
|
|
|
2007-08-15 19:26:03 +00:00
|
|
|
|
#
|
|
|
|
|
# Temperature sensors:
|
|
|
|
|
#
|
|
|
|
|
# coretemp: on-die sensor on Intel Core and newer CPUs
|
2009-10-20 09:31:57 +00:00
|
|
|
|
# amdtemp: on-die sensor on AMD K8/K10/K11 CPUs
|
2007-08-15 19:26:03 +00:00
|
|
|
|
#
|
|
|
|
|
device coretemp
|
2009-10-20 09:31:57 +00:00
|
|
|
|
device amdtemp
|
2007-08-15 19:26:03 +00:00
|
|
|
|
|
2008-08-08 16:26:53 +00:00
|
|
|
|
#
|
|
|
|
|
# CPU control pseudo-device. Provides access to MSRs, CPUID info and
|
|
|
|
|
# microcode update feature.
|
|
|
|
|
#
|
|
|
|
|
device cpuctl
|
|
|
|
|
|
add superio driver
The goal of this driver is consolidate information about SuperIO chips
and to provide for peaceful coexistence of drivers that need to access
SuperIO configuration registers.
While SuperIO chips can host various functions most of them are
discoverable and accessible without any knowledge of the SuperIO.
Examples are: keyboard and mouse controllers, UARTs, floppy disk
controllers. SuperIO-s also provide non-standard functions such as
GPIO, watchdog timers and hardware monitoring. Such functions do
require drivers with a knowledge of a specific SuperIO.
At this time the driver supports a number of ITE and Nuvoton (fka
Winbond) SuperIO chips.
There is a single driver for all devices. So, I have not done the usual
split between the hardware driver and the bus functionality. Although,
superio does act as a bus for devices that represent known non-standard
functions of a SuperIO chip. The bus provides enumeration of child
devices based on the hardcoded knowledge of such functions. The
knowledge as extracted from datasheets and other drivers.
As there is a single driver, I have not defined a kobj interface for it.
So, its interface is currently made of simple functions.
I think that we can the flexibility (and complications) when we actually
need it.
I am planning to convert nctgpio and wbwd to superio bus very soon.
Also, I am working on itwd driver (watchdog in ITE SuperIO-s).
Additionally, there is ithwm driver based on the reverted sensors
import, but I am not sure how to integrate it given that we still lack
any sensors interface.
Discussed with: imp, jhb
MFC after: 7 weeks
Differential Revision: https://reviews.freebsd.org/D8175
2019-07-01 17:05:41 +00:00
|
|
|
|
#
|
|
|
|
|
# SuperIO driver.
|
|
|
|
|
#
|
|
|
|
|
device superio
|
|
|
|
|
|
2004-04-16 05:59:08 +00:00
|
|
|
|
#
|
2004-04-16 09:29:45 +00:00
|
|
|
|
# System Management Bus (SMB)
|
2004-04-16 05:59:08 +00:00
|
|
|
|
#
|
|
|
|
|
options ENABLE_ALART # Control alarm on Intel intpm driver
|
|
|
|
|
|
1998-03-09 22:09:13 +00:00
|
|
|
|
#
|
|
|
|
|
# Set the number of PV entries per process. Increasing this can
|
2004-01-19 01:26:59 +00:00
|
|
|
|
# stop panics related to heavy use of shared memory. However, that can
|
1998-03-09 22:09:13 +00:00
|
|
|
|
# (combined with large amounts of physical memory) cause panics at
|
|
|
|
|
# boot time due the kernel running out of VM space.
|
|
|
|
|
#
|
|
|
|
|
# If you're tweaking this, you might also want to increase the sysctls
|
|
|
|
|
# "vm.v_free_min", "vm.v_free_reserved", and "vm.v_free_target".
|
|
|
|
|
#
|
1998-03-10 15:42:13 +00:00
|
|
|
|
# The value below is the one more than the default.
|
1998-03-09 22:09:13 +00:00
|
|
|
|
#
|
1999-11-05 20:40:01 +00:00
|
|
|
|
options PMAP_SHPGPERPROC=201
|
1998-03-09 22:09:13 +00:00
|
|
|
|
|
2010-03-10 19:50:52 +00:00
|
|
|
|
#
|
|
|
|
|
# Number of initial kernel page table pages used for early bootstrap.
|
|
|
|
|
# This number should include enough pages to map the kernel, any
|
|
|
|
|
# modules or other data loaded with the kernel by the loader, and data
|
|
|
|
|
# structures allocated before the VM system is initialized such as the
|
|
|
|
|
# vm_page_t array. Each page table page maps 4MB (2MB with PAE).
|
|
|
|
|
#
|
|
|
|
|
options NKPT=31
|
|
|
|
|
|
2001-02-27 07:39:12 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# ABI Emulation
|
|
|
|
|
|
2018-06-02 06:40:15 +00:00
|
|
|
|
# Enable (32-bit) a.out binary support
|
|
|
|
|
options COMPAT_AOUT
|
|
|
|
|
|
2016-08-22 17:37:31 +00:00
|
|
|
|
# Enable 32-bit runtime support for CloudABI binaries.
|
|
|
|
|
options COMPAT_CLOUDABI32
|
|
|
|
|
|
2001-02-27 07:39:12 +00:00
|
|
|
|
# Enable Linux ABI emulation
|
|
|
|
|
options COMPAT_LINUX
|
|
|
|
|
|
2001-06-11 11:04:36 +00:00
|
|
|
|
# Enable the linux-like proc filesystem support (requires COMPAT_LINUX
|
|
|
|
|
# and PSEUDOFS)
|
2001-03-02 05:57:39 +00:00
|
|
|
|
options LINPROCFS
|
|
|
|
|
|
2006-05-09 22:27:01 +00:00
|
|
|
|
#Enable the linux-like sys filesystem support (requires COMPAT_LINUX
|
|
|
|
|
# and PSEUDOFS)
|
2009-05-10 00:00:25 +00:00
|
|
|
|
options LINSYSFS
|
2006-05-09 22:27:01 +00:00
|
|
|
|
|
2006-06-12 20:38:17 +00:00
|
|
|
|
# Enable NDIS binary driver support
|
2009-03-07 19:54:30 +00:00
|
|
|
|
options NDISAPI
|
|
|
|
|
device ndis
|
2006-06-12 20:38:17 +00:00
|
|
|
|
|
2002-07-15 19:25:40 +00:00
|
|
|
|
|
|
|
|
|
#####################################################################
|
|
|
|
|
# VM OPTIONS
|
|
|
|
|
|
|
|
|
|
# KSTACK_PAGES is the number of memory pages to assign to the kernel
|
|
|
|
|
# stack of each thread.
|
|
|
|
|
|
i386: Bump KSTACK_PAGES default to match amd64
Logically, extend r286288 to cover all threads, by default.
The world has largely moved on from i386. Most FreeBSD users and developers
test on amd64 hardware. For better or worse, we have written a non-trivial
amount of kernel code that relies on stacks larger than 8 kB, and it "just
works" on amd64, so there has been little incentive to shrink it.
amd64 had its KSTACK_PAGES bumped to 4 back in Peter's initial AMD64 commit,
r114349, in 2003. Since that time, i386 has limped along on a stack half
the size. We've even observed the stack overflows years ago, but neglected
to fix the issue; see the 20121223 and 20150728 entries in UPDATING.
If anyone is concerned with this change, I suggest they configure their
AMD64 kernels with KSTACK_PAGES 2 and fix the fallout there first. Eugene
has identified a list of high stack usage functions in the first PR below.
PR: 219476, 224218
Reported by: eugen@, Shreesh Holla <hshreesh AT yahoo.com>
Relnotes: maybe
Sponsored by: Dell EMC Isilon
2017-12-11 04:32:37 +00:00
|
|
|
|
options KSTACK_PAGES=5
|
2002-07-15 19:25:40 +00:00
|
|
|
|
|
2012-03-24 19:43:49 +00:00
|
|
|
|
# Enable detailed accounting by the PV entry allocator.
|
|
|
|
|
|
|
|
|
|
options PV_STATS
|
|
|
|
|
|
2000-07-26 19:39:46 +00:00
|
|
|
|
#####################################################################
|
|
|
|
|
|
2000-03-18 18:39:02 +00:00
|
|
|
|
# More undocumented options for linting.
|
|
|
|
|
# Note that documenting these are not considered an affront.
|
|
|
|
|
|
2003-02-13 22:33:26 +00:00
|
|
|
|
options FB_INSTALL_CDEV # install a CDEV entry in /dev
|
|
|
|
|
|
2000-03-18 18:39:02 +00:00
|
|
|
|
options I586_PMC_GUPROF=0x70000
|
|
|
|
|
options KBDIO_DEBUG=2
|
|
|
|
|
options KBD_MAXRETRY=4
|
|
|
|
|
options KBD_MAXWAIT=6
|
|
|
|
|
options KBD_RESETDELAY=201
|
2000-11-08 11:34:09 +00:00
|
|
|
|
|
2000-03-18 18:39:02 +00:00
|
|
|
|
options PSM_DEBUG=1
|
2001-01-20 12:34:53 +00:00
|
|
|
|
|
2002-10-17 13:47:31 +00:00
|
|
|
|
options TIMER_FREQ=((14318182+6)/12)
|
2001-01-20 12:34:53 +00:00
|
|
|
|
|
2000-03-18 18:39:02 +00:00
|
|
|
|
options VM_KMEM_SIZE
|
|
|
|
|
options VM_KMEM_SIZE_MAX
|
|
|
|
|
options VM_KMEM_SIZE_SCALE
|
2004-08-01 11:40:54 +00:00
|
|
|
|
|
|
|
|
|
|