d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
00c885e181
freebsd-nq/sys/amd64/conf/GENERIC

340 lines
13 KiB
Plaintext
Raw Normal View History

Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
#
Commit MD parts of a loosely functional AMD64 port. This is based on a heavily stripped down FreeBSD/i386 (brutally stripped down actually) to attempt to get a stable base to start from. There is a lot missing still. Worth noting: - The kernel runs at 1GB in order to cheat with the pmap code. pmap uses a variation of the PAE code in order to avoid having to worry about 4 levels of page tables yet. - It boots in 64 bit "long mode" with a tiny trampoline embedded in the i386 loader. This simplifies locore.s greatly. - There are still quite a few fragments of i386-specific code that have not been translated yet, and some that I cheated and wrote dumb C versions of (bcopy etc). - It has both int 0x80 for syscalls (but using registers for argument passing, as is native on the amd64 ABI), and the 'syscall' instruction for syscalls. int 0x80 preserves all registers, 'syscall' does not. - I have tried to minimize looking at the NetBSD code, except in a couple of places (eg: to find which register they use to replace the trashed %rcx register in the syscall instruction). As a result, there is not a lot of similarity. I did look at NetBSD a few times while debugging to get some ideas about what I might have done wrong in my first attempt.
2003-05-01 01:05:25 +00:00
# GENERIC -- Generic kernel configuration file for FreeBSD/amd64
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
#
Documentation-only change: - add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive. I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because: 1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook) 2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective. I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan. MFC after: 3 days
2009-01-13 12:35:33 +00:00
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
#
Fix the link to the Handbook
2002-08-01 17:21:18 +00:00
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
Clean up some of the documentation at the top.
1999-06-20 03:36:46 +00:00
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
Change to comments only: spell FreeBSD.org correctly
2000-05-13 11:21:19 +00:00
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
Clean up some of the documentation at the top.
1999-06-20 03:36:46 +00:00
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +00:00
# in NOTES.
Add hints to the file ./LINT and the handbook.
1996-08-27 16:25:53 +00:00
#
$Id$ -> $FreeBSD$
1999-08-28 01:08:13 +00:00
# $FreeBSD$
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
Commit MD parts of a loosely functional AMD64 port. This is based on a heavily stripped down FreeBSD/i386 (brutally stripped down actually) to attempt to get a stable base to start from. There is a lot missing still. Worth noting: - The kernel runs at 1GB in order to cheat with the pmap code. pmap uses a variation of the PAE code in order to avoid having to worry about 4 levels of page tables yet. - It boots in 64 bit "long mode" with a tiny trampoline embedded in the i386 loader. This simplifies locore.s greatly. - There are still quite a few fragments of i386-specific code that have not been translated yet, and some that I cheated and wrote dumb C versions of (bcopy etc). - It has both int 0x80 for syscalls (but using registers for argument passing, as is native on the amd64 ABI), and the 'syscall' instruction for syscalls. int 0x80 preserves all registers, 'syscall' does not. - I have tried to minimize looking at the NetBSD code, except in a couple of places (eg: to find which register they use to replace the trashed %rcx register in the syscall instruction). As a result, there is not a lot of similarity. I did look at NetBSD a few times while debugging to get some ideas about what I might have done wrong in my first attempt.
2003-05-01 01:05:25 +00:00
cpu HAMMER
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
ident GENERIC
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
Sync with i386/GENERIC ordering.
2003-06-01 20:26:38 +00:00
Switch over to ULE as the default scheduler for amd64 and i386 architectures.
2007-10-19 12:30:33 +00:00
options SCHED_ULE # ULE scheduler
Switch the default scheduler to 4BSD to match what will go into RELENG_5 soon. It can be switched back once 5.3 is tested and released. Also turn on PREEMPTION as many of the stability problems with it have been fixed. MT5: 3 days.
2004-09-07 22:37:43 +00:00
options PREEMPTION # Enable kernel thread preemption
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options INET # InterNETworking
options INET6 # IPv6 communications protocols
Eliminate whitespace diffs to the i386 version.
2008-02-19 06:30:49 +00:00
options SCTP # Stream Control Transmission Protocol
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
Remove trailing '.' for consistency!
2007-04-10 21:40:13 +00:00
options UFS_GJOURNAL # Enable gjournal-based UFS journaling
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options MD_ROOT # MD is a potential root device
This patch changes head so that the default NFS client is now the new NFS client (which I guess is no longer experimental). The fstype "newnfs" is now "nfs" and the regular/old NFS client is now fstype "oldnfs". Although mounts via fstype "nfs" will usually work without userland changes, an updated mount_nfs(8) binary is needed for kernels built with "options NFSCL" but not "options NFSCLIENT". Updated mount_nfs(8) and mount(8) binaries are needed to do mounts for fstype "oldnfs". The GENERIC kernel configs have been changed to use options NFSCL and NFSD (the new client and server) instead of NFSCLIENT and NFSSERVER. For kernels being used on diskless NFS root systems, "options NFSCL" must be in the kernel config. Discussed on freebsd-fs@.
2011-04-27 17:51:51 +00:00
options NFSCL # New Network Filesystem Client
options NFSD # New Network Filesystem Server
Add kernel module support for nfslockd and krpc. Use the module system to detect (or load) kernel NLM support in rpc.lockd. Remove the '-k' option to rpc.lockd and make kernel NLM the default. A user can still force the use of the old user NLM by building a kernel without NFSLOCKD and/or removing the nfslockd.ko module.
2008-03-27 11:54:20 +00:00
options NFSLOCKD # Network Lock Manager
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
Evolve the ctlreq interface added to geom_gpt into a generic partitioning class that supports multiple schemes. Current schemes supported are APM (Apple Partition Map) and GPT. Change all GEOM_APPLE anf GEOM_GPT options into GEOM_PART_APM and GEOM_PART_GPT (resp). The ctlreq interface supports verbs to create and destroy partitioning schemes on a disk; to add, delete and modify partitions; and to commit or undo changes made.
2007-02-07 18:55:31 +00:00
options GEOM_PART_GPT # GUID Partition Tables.
Include GEOM_LABEL in GENERIC. It's very useful and not well publicized enough. Approved by: pjd
2007-02-09 19:03:18 +00:00
options GEOM_LABEL # Provides labelization
Provide groundwork for 32-bit binary compatibility on non-x86 platforms, for upcoming 64-bit PowerPC and MIPS support. This renames the COMPAT_IA32 option to COMPAT_FREEBSD32, removes some IA32-specific code from MI parts of the kernel and enhances the freebsd32 compatibility code to support big-endian platforms. Reviewed by: kib, jhb
2010-03-11 14:49:06 +00:00
options COMPAT_FREEBSD32 # Compatible with i386 binaries
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
Add recently invented COMPAT_FREEBSD5 option. MFC after: 3 days
2005-07-14 15:39:06 +00:00
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
Added COMPAT_FREEBSD6 option.
2006-09-26 12:36:34 +00:00
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
Add COMPAT_FREEBSD7 and enable it in configs that have COMPAT_FREEBSD6.
2008-01-07 21:40:11 +00:00
options COMPAT_FREEBSD7 # Compatible with FreeBSD7
Reduce annoying SCSI probing delay from 15 to 5 seconds in all GENRIC kernels. Discussed on: -current
2004-11-02 20:57:20 +00:00
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options KTRACE # ktrace(1) support
Break out stack(9) from ddb(4): - Introduce per-architecture stack_machdep.c to hold stack_save(9). - Introduce per-architecture machine/stack.h to capture any common definitions required between db_trace.c and stack_machdep.c. - Add new kernel option "options STACK"; we will build in stack(9) if it is defined, or also if "options DDB" is defined to provide compatibility with existing users of stack(9). Add new stack_save_td(9) function, which allows the capture of a stacktrace of another thread rather than the current thread, which the existing stack_save(9) was limited to. It requires that the thread be neither swapped out nor running, which is the responsibility of the consumer to enforce. Update stack(9) man page. Build tested: amd64, arm, i386, ia64, powerpc, sparc64, sun4v Runtime tested: amd64 (rwatson), arm (cognet), i386 (rwatson)
2007-12-02 20:40:35 +00:00
options STACK # stack(9) support
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
Minor sync to i386 GENERIC in the form of comments and whitespace.
2004-12-30 18:51:23 +00:00
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
Enable PRINTF_BUFR_SIZE on i386 and amd64 by default. In the past there have been some reports of PRINTF_BUFR_SIZE not functioning correctly. Instead of having garbled console messages, we should just see whether the issues are still there and analyze them. Approved by: re
2009-06-14 18:01:35 +00:00
options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
- Use "device\t" and "options \t" for consistency.
2009-05-10 00:00:25 +00:00
options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4)
Enable AUDIT by default in the GENERIC kernel, allowing security event auditing to be turned on without a kernel recompile, just an rc.conf option. Approved by: re (kensmith) Obtained from: TrustedBSD Project
2007-06-08 20:29:07 +00:00
options AUDIT # Security event auditing
Remove MAC kernel config files and add "options MAC" to GENERIC, with the goal of shipping 8.0 with MAC support in the default kernel. No policies will be compiled in or enabled by default, but it will now be possible to load them at boot or runtime without a kernel recompile. While the framework is not believed to impose measurable overhead when no policies are loaded (a result of optimization over the past few months in HEAD), we'll continue to benchmark and optimize as the release approaches. Please keep an eye out for performance or functionality regressions that could be a result of this change. Approved by: re (kensmith) Obtained from: TrustedBSD Project
2009-06-02 18:31:08 +00:00
options MAC # TrustedBSD MAC Framework
Add commented out options KDTRACE_HOOKS and, for amd64, KDRACE_FRAME, to GENERIC configuration files. This brings what's in 8.x in sync with what is in 7.x, but does not change any current defaults. Possibly they should now be enabled in head by default?
2009-01-05 14:21:49 +00:00
#options KDTRACE_FRAME # Ensure frames are compiled in
#options KDTRACE_HOOKS # Kernel DTrace hooks
Add INCLUDE_CONFIG_FILE in GENERIC on all non-embedded platforms. # This is the resolution of removing it from DEFAULTS... MFC after: 5 days
2010-01-10 17:44:22 +00:00
options INCLUDE_CONFIG_FILE # Include this file in kernel
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
Turn on kernel debugging support (DDB, INVARIANTS, INVARIANT_SUPPORT, WITNESS) by default while SMPng is still being developed. Submitted by: jhb
2001-04-15 19:37:28 +00:00
# Debugging for use in -current
Add options KDB and GDB. KDB takes on the function of what DDB used to be. Both DDB and GDB specify which KDB backends to include.
2004-07-11 03:20:09 +00:00
options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.
Adjust style (following the already existing rules) for the newly introduced option DEADLKRES. Reported by: danfe, julian, avg
2010-02-15 23:44:48 +00:00
options DEADLKRES # Enable the deadlock resolver
Ooops. Put back Invariants and witness Submitted by: csjp
2007-10-26 02:35:42 +00:00
options INVARIANTS # Enable calls of extra sanity checking
options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS
options WITNESS # Enable checks to detect deadlocks and cycles
options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed
Add MALLOC_DEBUG_MAXZONES debug malloc(9) option to use multiple uma zones for each malloc bucket size. The purpose is to isolate different malloc types into hash classes, so that any buffer overruns or use-after-free will usually only affect memory from malloc types in that hash class. This is purely a debugging tool; by varying the hash function and tracking which hash class was corrupted, the intersection of the hash classes from each instance will point to a single malloc type that is being misused. At this point inspection or memguard(9) can be used to catch the offending code. Add MALLOC_DEBUG_MAXZONES=8 to -current GENERIC configuration files. The suggestion to have this on by default came from Kostik Belousov on -arch. This code is based on work by Ron Steinke at Isilon Systems. Reviewed by: -arch (mostly silence) Reviewed by: zml Approved by: zml (mentor)
2010-07-28 15:36:12 +00:00
options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones
Add commented out SMP stuff in GENERIC, remove stale configs.
1998-12-27 13:12:59 +00:00
Sync with i386. - turn on SMP in generic - add 'device atpic' - this is unconditional on i386, but certain nvidia based systems need to disable acpi because the reference bios seems to be hosed. If acpi is disabled, we won't find the apic. amd64 has the mptable code in a seperate compile option as well. - turn sym back on, it doesn't fail to compile anymore. Approved by: re
2003-11-19 18:11:27 +00:00
# Make an SMP-capable kernel by default
MFi386: Sync whitespace and an abbreviation
2005-02-28 23:39:58 +00:00
options SMP # Symmetric MultiProcessor Kernel
Minor sync to i386 GENERIC in the form of comments and whitespace.
2004-12-30 18:51:23 +00:00
Add cpufreq(4) to GENERIC. It does not change the frequency by default, so systems should be relatively unaffected. Users can then simply enable powerd(8) in rc.conf to take advantage of it. Approved by: re
2007-07-01 21:47:45 +00:00
# CPU frequency control
device cpufreq
MFi386: bring over DEFAULTS (repocopy) and adapt. While there isn't a 4.x->6.x amd64 upgrade path, the config files are kept in approximate sync.
2005-10-27 18:54:43 +00:00
# Bus support.
Converge with i386/GENERIC
2003-11-08 03:17:36 +00:00
device acpi
de-count pci
2002-07-23 06:38:47 +00:00
device pci
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# Floppy drives
device fdc
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
Switch the GENERIC kernels for all architectures to the new CAM-based ATA stack. It means that all legacy ATA drivers are disabled and replaced by respective CAM drivers. If you are using ATA device names in /etc/fstab or other places, make sure to update them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, where 'Y's are the sequential numbers for each type in order of detection, unless configured otherwise with tunables, see cam(4)). ataraid(4) functionality is now supported by the RAID GEOM class. To use it you can load geom_raid kernel module and use graid(8) tool for management. Instead of /dev/arX device names, use /dev/raid/rX.
2011-04-24 08:58:58 +00:00
# ATA controllers
device ahci # AHCI-compatible SATA controllers
device ata # Legacy ATA/SATA controllers
options ATA_CAM # Handle legacy controllers with CAM
- Add shim to simplify migration to the CAM-based ATA. For each new adaX device in /dev/ create symbolic link with adY name, trying to mimic old ATA numbering. Imitation is not complete, but should be enough in most cases to mount file systems without touching /etc/fstab. - To know what behavior to mimic, restore ATA_STATIC_ID option in cases where it was present before. - Add some more details to UPDATING.
2011-04-26 17:01:49 +00:00
options ATA_STATIC_ID # Static device numbering
Switch the GENERIC kernels for all architectures to the new CAM-based ATA stack. It means that all legacy ATA drivers are disabled and replaced by respective CAM drivers. If you are using ATA device names in /etc/fstab or other places, make sure to update them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, where 'Y's are the sequential numbers for each type in order of detection, unless configured otherwise with tunables, see cam(4)). ataraid(4) functionality is now supported by the RAID GEOM class. To use it you can load geom_raid kernel module and use graid(8) tool for management. Instead of /dev/arX device names, use /dev/raid/rX.
2011-04-24 08:58:58 +00:00
device mvs # Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA
device siis # SiliconImage SiI3124/SiI3132/SiI3531 SATA
Revert previous commit. Not all RAID controllers are SCSI.
2000-07-29 02:12:44 +00:00
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# SCSI Controllers
device ahc # AHA2940 and onboard AIC7xxx devices
Move AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT below their corresponding devices.
2006-04-24 08:44:34 +00:00
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ahd # AHA39320/29320 and onboard AIC79xx devices
Move AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT below their corresponding devices.
2006-04-24 08:44:34 +00:00
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device amd # AMD 53C974 (Tekram DC-390(T))
Introduce a driver for the Highpoint RocketRAID 3xxx series of controllers. The driver relies on CAM. Many thanks to Highpoint for providing this driver.
2007-05-09 07:07:26 +00:00
device hptiop # Highpoint RocketRaid 3xxx series
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device isp # Qlogic family
- Use "device\t" and "options \t" for consistency.
2009-05-10 00:00:25 +00:00
#device ispfw # Firmware for QLogic HBAs- normally a module
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device mpt # LSI-Logic MPT-Fusion
MFp4 (//depot/projects/mps/...) Bring in a driver for the LSI Logic MPT2 6Gb SAS controllers. This driver supports basic I/O, and works with SAS and SATA drives and expanders. Basic error recovery works (i.e. timeouts and aborts) as well. Integrated RAID isn't supported yet, and there are some known bugs. So this isn't ready for production use, but is certainly ready for testing and additional development. For the moment, new commits to this driver should go into the FreeBSD Perforce repository first (//depot/projects/mps/...) and then get merged into -current once they've been vetted. This has only been added to the amd64 GENERIC, since that is the only architecture I have tested this driver with. Submitted by: scottl Discussed with: imp, gibbs, will Sponsored by: Yahoo, Spectra Logic Corporation
2010-09-10 15:03:56 +00:00
device mps # LSI-Logic MPT-Fusion 2
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
#device ncr # NCR/Symbios Logic
Sync with i386. - turn on SMP in generic - add 'device atpic' - this is unconditional on i386, but certain nvidia based systems need to disable acpi because the reference bios seems to be hosed. If acpi is disabled, we won't find the apic. amd64 has the mptable code in a seperate compile option as well. - turn sym back on, it doesn't fail to compile anymore. Approved by: re
2003-11-19 18:11:27 +00:00
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device trm # Tekram DC395U/UW/F DC315U adapters
device adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adapters
Switch the GENERIC kernels for all architectures to the new CAM-based ATA stack. It means that all legacy ATA drivers are disabled and replaced by respective CAM drivers. If you are using ATA device names in /etc/fstab or other places, make sure to update them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, where 'Y's are the sequential numbers for each type in order of detection, unless configured otherwise with tunables, see cam(4)). ataraid(4) functionality is now supported by the RAID GEOM class. To use it you can load geom_raid kernel module and use graid(8) tool for management. Instead of /dev/arX device names, use /dev/raid/rX.
2011-04-24 08:58:58 +00:00
# ATA/SCSI peripherals
device scbus # SCSI bus (required for ATA/SCSI)
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
Switch the GENERIC kernels for all architectures to the new CAM-based ATA stack. It means that all legacy ATA drivers are disabled and replaced by respective CAM drivers. If you are using ATA device names in /etc/fstab or other places, make sure to update them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, where 'Y's are the sequential numbers for each type in order of detection, unless configured otherwise with tunables, see cam(4)). ataraid(4) functionality is now supported by the RAID GEOM class. To use it you can load geom_raid kernel module and use graid(8) tool for management. Instead of /dev/arX device names, use /dev/raid/rX.
2011-04-24 08:58:58 +00:00
device pass # Passthrough device (direct ATA/SCSI access)
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ses # SCSI Environmental Services (and SAF-TE)
Converge with i386/GENERIC
2003-11-08 03:17:36 +00:00
# RAID controllers interfaced to the SCSI subsystem
asr(4) is not amd64-clean, not amr(4). Pointy hat to: myself Submitted by: scottl
2009-01-19 08:51:20 +00:00
device amr # AMI MegaRAID
Glue the arcmsr driver into the tree.
2005-03-31 20:21:43 +00:00
device arcmsr # Areca SATA II RAID
asr(4) is not amd64-clean, not amr(4). Pointy hat to: myself Submitted by: scottl
2009-01-19 08:51:20 +00:00
#XXX it is not 64-bit clean, -scottl
#device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID
Converge with i386/GENERIC
2003-11-08 03:17:36 +00:00
device ciss # Compaq Smart RAID 5*
device dpt # DPT Smartcache III, IV - See NOTES for options
Hook up the hptmv driver for amd64. MFC After: 3 days
2005-09-08 03:29:18 +00:00
device hptmv # Highpoint RocketRAID 182x
Add the 'hptrr' driver for supporting the following Highpoint RocketRAID cards: o RocketRAID 172x series o RocketRAID 174x series o RocketRAID 2210 o RocketRAID 222x series o RocketRAID 2240 o RocketRAID 230x series o RocketRAID 231x series o RocketRAID 232x series o RocketRAID 2340 o RocketRAID 2522 Many thanks to Highpoint for their continued support of FreeBSD. Submitted by: Highpoint
2007-12-15 00:56:17 +00:00
device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
Converge with i386/GENERIC
2003-11-08 03:17:36 +00:00
device iir # Intel Integrated RAID
device ips # IBM (Adaptec) ServeRAID
device mly # Mylex AcceleRAID/eXtremeRAID
MFi386: add rue and twa
2004-05-16 20:57:01 +00:00
device twa # 3ware 9000 series PATA/SATA RAID
Converge with i386/GENERIC
2003-11-08 03:17:36 +00:00
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# RAID controllers
Turn aac back on now that its been cleaned up for 64 bit compilation
2003-09-08 20:00:55 +00:00
device aac # Adaptec FSA RAID
device aacp # SCSI passthrough for aac (requires CAM)
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ida # Compaq Smart RAID
Hook the MFI driver up to the build.
2006-03-29 09:57:22 +00:00
device mfi # LSI MegaRAID SAS
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device mlx # Mylex DAC960 family
#XXX pointer/int warnings
#device pst # Promise Supertrak SX6000
device twe # 3ware ATA RAID
Spelling police
1999-04-19 10:18:34 +00:00
# atkbdc0 controls both the keyboard and the PS/2 mouse
Turn syscons on now that it works, so that anybody trying to run this can see something. Probing for keyboard still works for auto serial console mode.
2003-05-09 18:26:06 +00:00
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
The first stage of console driver reorganization: activate new keyboard and video card drivers. Because of the changes, you are required to update your kernel configuration file now! The files in sys/dev/syscons are still i386-specific (but less so than before), and won't compile for alpha and PC98 yet. syscons still directly accesses the video card registers here and there; this will be rectified in the later stages.
1999-01-11 03:18:56 +00:00
Add kbdmux(4) to GENERIC on amd64 Requested by: scottl Tested by: scottl
2006-03-31 23:04:48 +00:00
device kbdmux # keyboard multiplexer
Turn syscons on now that it works, so that anybody trying to run this can see something. Probing for keyboard still works for auto serial console mode.
2003-05-09 18:26:06 +00:00
device vga # VGA video card driver
The first stage of console driver reorganization: activate new keyboard and video card drivers. Because of the changes, you are required to update your kernel configuration file now! The files in sys/dev/syscons are still i386-specific (but less so than before), and won't compile for alpha and PC98 yet. syscons still directly accesses the video card registers here and there; this will be rectified in the later stages.
1999-01-11 03:18:56 +00:00
Turn syscons on now that it works, so that anybody trying to run this can see something. Probing for keyboard still works for auto serial console mode.
2003-05-09 18:26:06 +00:00
device splash # Splash screen and screen saver support
The first stage of console driver reorganization: activate new keyboard and video card drivers. Because of the changes, you are required to update your kernel configuration file now! The files in sys/dev/syscons are still i386-specific (but less so than before), and won't compile for alpha and PC98 yet. syscons still directly accesses the video card registers here and there; this will be rectified in the later stages.
1999-01-11 03:18:56 +00:00
Part 1 of pcvt/voxware revival. I hope I have not clobbered any other deltas, but it is possible since I had a few merge conflicts over the last few days while this has been sitting ready to go. Approved by: core
1999-01-01 08:09:58 +00:00
# syscons is the default console driver, resembling an SCO console
Turn syscons on now that it works, so that anybody trying to run this can see something. Probing for keyboard still works for auto serial console mode.
2003-05-09 18:26:06 +00:00
device sc
Add SC_PIXEL_MODE to GENERIC for amd64 and i386. Requested by: many
2011-05-10 16:44:16 +00:00
options SC_PIXEL_MODE # add support for the raster text mode
Include three lines about the pcvt console driver, so we don't ever need a different config file for it.
1995-02-15 20:38:36 +00:00
Follow i386's suit and include AGP support in the generic kernel.
2005-04-13 06:00:07 +00:00
device agp # support several AGP chipsets
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# PCCARD (PCMCIA) support
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
# PCMCIA and cardbus bridge support
device cbb # cardbus (yenta) bridge
device pccard # PC Card (16-bit) bus
device cardbus # CardBus (32-bit) bus
- add apm to the GENERIC kernel (disabled by default), and add some comments regarding apm to LINT - Disabled the statistics clock on machines which have an APM BIOS and have the options "APM_BROKEN_STATCLOCK" enabled (which is default in GENERIC now) - move around some of the code in clock.c dealing with the rtc to make it more obvios the effects of disabling the statistics clock Reviewed by: bde
1996-04-22 19:40:28 +00:00
Put on my asbestos suit and attempt to tidy up and add some simple docs or notes to make it much more obvious what things are for people who have not committed LINT to memory yet.
1999-06-29 18:55:53 +00:00
# Serial (COM) ports
Add uart(4). When both sio(4) and uart(4) can handle a serial port, sio(4) will claim it. This change therefore only affects how ports are handled when they are not claimed by sio(4), and in principle will improve hardware support. MFC after: 2 months
2005-11-05 19:48:53 +00:00
device uart # Generic UART driver
GENERIC is our new all singing and dancing kernel. Please report ASAP if there is anything GENERICAH or GENERICBT can, which this one cannot. MINI changed to reflect the SCSI-pecking-order.
1994-10-17 21:10:20 +00:00
Fix typos
1999-02-11 06:07:27 +00:00
# Parallel port
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
#device vpo # Requires scbus and da
Mention the puc(4) glue driver in a commented-out example so the user of "dumb" PCI-based serial/parallel boards get a hint how to enable them. I wasn't sure about the ia64, pc98, powerpc, and sparc64 archs whether they'd support puc(4) or not.
2003-09-19 20:04:55 +00:00
# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
Add uart(4). When both sio(4) and uart(4) can handle a serial port, sio(4) will claim it. This change therefore only affects how ports are handled when they are not claimed by sio(4), and in principle will improve hardware support. MFC after: 2 months
2005-11-05 19:48:53 +00:00
# line to enable it (connects to sio, uart and/or ppc drivers):
o Use tab instead of spaces for puc(4) line. o Use capitalized "Ethernet" for consistency.
2005-01-05 05:25:21 +00:00
#device puc
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# PCI Ethernet NICs.
- Initial release of bxe(4) to support Broadcom NetXtreme II 10GbE. (BCM57710, BCM57711, BCM57711E) MFC after: One month
2011-03-14 22:42:41 +00:00
device bxe # Broadcom BCM57710/BCM57711/BCM57711E 10Gb Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device de # DEC/Intel DC21x4x (``Tulip'')
Add igb to the default kernel MFC after:ASAP
2008-07-30 22:27:38 +00:00
device em # Intel PRO/1000 Gigabit Ethernet Family
device igb # Intel PRO/1000 PCIE Server Gigabit Family
Add ixgbe to the GENERIC amd64 kernel in place of the older ixgb driver. I will add to other architectures after this one proves trouble free. MFC after: 2 weeks
2009-04-10 00:40:48 +00:00
device ixgbe # Intel PRO/10GbE PCIE Ethernet Family
Add le(4). I could actually only test it on alpha, i386 and sparc64 but given that this includes the more problematic platforms I see no reason why it shouldn't also work on amd64 and ia64.
2006-05-17 20:45:45 +00:00
device le # AMD Am7900 LANCE and Am79C9xx PCnet
Resort the if_ti driver to match the PCI Network cards instead of placing it under the mii devices list. PR: kern/123147 Submitted by: gavin Approved by: imp (mentor, implicit) MFC after: 3 days
2008-05-17 23:50:00 +00:00
device ti # Alteon Networks Tigon I/II gigabit Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device txp # 3Com 3cR990 (``Typhoon'')
device vx # 3Com 3c590, 3c595 (``Vortex'')
Seperate the miibus pci ethernet drivers from the non-miibus drivers so it's a little clearer which is which from just looking at GENERIC.
1999-09-09 18:30:58 +00:00
# PCI Ethernet NICs that use the common MII bus controller code.
Add a brief comment telling people to retain 'device miibus' as necessary. PR: docs/21981 Submitted by: Matthew Emmerton <matt@gsicomp.on.ca>
2000-10-28 22:32:17 +00:00
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
Update GENERIC/LINT to leave out the useless digit at the end of pci or other unwired devices.
2000-01-23 12:18:53 +00:00
device miibus # MII bus support
- Add driver for Attansic L2 FastEthernet controller found on Asus EeePC and some Asus mainboards. Reviewed by: yongari, rpaulo, jhb Tested by: many Approved by: kib (mentor) MFC after: 1 week
2008-10-03 10:31:31 +00:00
device ae # Attansic/Atheros L2 FastEthernet
Add age(4) to the list of drivers supported by GENERIC kernel.
2008-05-19 02:30:27 +00:00
device age # Attansic/Atheros L1 Gigabit Ethernet
Add alc(4), a driver for Atheros AR8131/AR8132 PCIe ethernet controller. These controllers are also known as L1C(AR8131) and L2C(AR8132) respectively. These controllers resembles the first generation controller L1 but usage of different descriptor format and new register mappings over L1 register space requires a new driver. There are a couple of registers I still don't understand but the driver seems to have no critical issues for performance and stability. Currently alc(4) supports the following hardware features. o MSI o TCP Segmentation offload o Hardware VLAN tag insertion/stripping o Tx/Rx interrupt moderation o Hardware statistics counters(dev.alc.%d.stats) o Jumbo frame o WOL AR8131/AR8132 also supports Tx checksum offloading but I disabled it due to stability issues. I'm not sure this comes from broken sample boards or hardware bugs. If you know your controller works without problems you can still enable it. The controller has a silicon bug for Rx checksum offloading, so the feature was not implemented. I'd like to say big thanks to Atheros. Atheros kindly sent sample boards to me and answered several questions I had. HW donated by: Atheros Communications, Inc.
2009-06-10 02:07:58 +00:00
device alc # Atheros AR8131/AR8132 Ethernet
Add ale(4), a driver for Atheros AR8121/AR8113/AR8114 PCIe ethernet controller. The controller is also known as L1E(AR8121) and L2E(AR8113/AR8114). Unlike its predecessor Attansic L1, AR8121/AR8113/AR8114 uses completely different Rx logic such that it requires separate driver. Datasheet for AR81xx is not available to open source driver writers but it shares large part of Tx and PHY logic of L1. I still don't understand some part of register meaning and some MAC statistics counters but the driver seems to have no critical issues for performance and stability. The AR81xx requires copy operation to pass received frames to upper stack such that ale(4) consumes a lot of CPU cycles than that of other controller. A couple of silicon bugs also adds more CPU cycles to address the known hardware bug. However, if you have fast CPU you can still saturate the link. Currently ale(4) supports the following hardware features. - MSI. - TCP Segmentation offload. - Hardware VLAN tag insertion/stripping with checksum offload. - Tx TCP/UDP checksum offload and Rx IP/TCP/UDP checksum offload. - Tx/Rx interrupt moderation. - Hardware statistics counters. - Jumbo frame. - WOL. AR81xx PCIe ethernet controllers are mainly found on ASUS EeePC or P5Q series of ASUS motherboards. Special thanks to Jeremy Chadwick who sent the hardware to me. Without his donation writing a driver for AR81xx would never have been possible. Big thanks to all people who reported feedback or tested patches. HW donated by: koitsu Tested by: bsam, Joao Barros <joao.barros <> gmail DOT com > Jan Henrik Sylvester <me <> janh DOT de > Ivan Brawley < ivan <> brawley DOT id DOT au >, CURRENT ML
2008-11-12 09:52:06 +00:00
device ale # Atheros AR8121/AR8113/AR8114 Ethernet
Hook bce up to the build
2006-04-10 20:04:22 +00:00
device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
Spell Ethernet correctly.
2004-05-02 18:57:29 +00:00
device bfe # Broadcom BCM440x 10/100 Ethernet
Sort 'bge' correctly.
2003-09-10 18:54:59 +00:00
device bge # Broadcom BCM570xx Gigabit Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device dc # DEC/Intel 21143 and various workalikes
Add et(4), a port of DragonFly's Agere ET1310 10/100/Gigabit Ethernet device driver, written by sephe@ Obtained from: DragonFly Sponsored by: iXsystems MFC after: 2 weeks
2008-06-20 19:28:33 +00:00
device et # Agere ET1310 10/100/Gigabit Ethernet
Move the fxp driver so it is under the miibus section.
2001-03-12 21:51:07 +00:00
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
Add jme(4) to the list of drivers supported by GENERIC kernel.
2008-05-27 02:22:32 +00:00
device jme # JMicron JMC250 Gigabit/JMC260 Fast Ethernet
o Use tab instead of spaces for puc(4) line. o Use capitalized "Ethernet" for consistency.
2005-01-05 05:25:21 +00:00
device lge # Level 1 LXT1001 gigabit Ethernet
Add msk(4) to the list of drivers supported by GENERIC kernel.
2006-12-13 03:41:47 +00:00
device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet
Add nfe(4) to the list of drivers supported by GENERIC kernel. While I'm here comment out nve(4) as nfe(4) will take over. Approved by: re
2007-06-12 02:24:30 +00:00
device nfe # nVidia nForce MCP on-board Ethernet
o Use tab instead of spaces for puc(4) line. o Use capitalized "Ethernet" for consistency.
2005-01-05 05:25:21 +00:00
device nge # NatSemi DP83820 gigabit Ethernet
Add nfe(4) to the list of drivers supported by GENERIC kernel. While I'm here comment out nve(4) as nfe(4) will take over. Approved by: re
2007-06-12 02:24:30 +00:00
#device nve # nVidia nForce MCP on-board Ethernet Networking
Add le(4). I could actually only test it on alpha, i386 and sparc64 but given that this includes the more problematic platforms I see no reason why it shouldn't also work on amd64 and ia64.
2006-05-17 20:45:45 +00:00
device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le')
Take the support for the 8139C+/8169/8169S/8110S chips out of the rl(4) driver and put it in a new re(4) driver. The re(4) driver shares the if_rlreg.h file with rl(4) but is a separate module. (Ultimately I may change this. For now, it's convenient.) rl(4) has been modified so that it will never attach to an 8139C+ chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to match the 8169/8169S/8110S gigE chips. if_re.c contains the same basic code that was originally bolted onto if_rl.c, with the following updates: - Added support for jumbo frames. Currently, there seems to be a limit of approximately 6200 bytes for jumbo frames on transmit. (This was determined via experimentation.) The 8169S/8110S chips apparently are limited to 7.5K frames on transmit. This may require some more work, though the framework to handle jumbo frames on RX is in place: the re_rxeof() routine will gather up frames than span multiple 2K clusters into a single mbuf list. - Fixed bug in re_txeof(): if we reap some of the TX buffers, but there are still some pending, re-arm the timer before exiting re_txeof() so that another timeout interrupt will be generated, just in case re_start() doesn't do it for us. - Handle the 'link state changed' interrupt - Fix a detach bug. If re(4) is loaded as a module, and you do tcpdump -i re0, then you do 'kldunload if_re,' the system will panic after a few seconds. This happens because ether_ifdetach() ends up calling the BPF detach code, which notices the interface is in promiscuous mode and tries to switch promisc mode off while detaching the BPF listner. This ultimately results in a call to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init() to handle the IFF_PROMISC flag change. Unfortunately, calling re_init() here turns the chip back on and restarts the 1-second timeout loop that drives re_tick(). By the time the timeout fires, if_re.ko has been unloaded, which results in a call to invalid code and blows up the system. To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(), which stops the ioctl routine from trying to reset the chip. - Modified comments in re_rxeof() relating to the difference in RX descriptor status bit layout between the 8139C+ and the gigE chips. The layout is different because the frame length field was expanded from 12 bits to 13, and they got rid of one of the status bits to make room. - Add diagnostic code (re_diag()) to test for the case where a user has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some NICs have the REQ64# and ACK64# lines connected even though the board is 32-bit only (in this case, they should be pulled high). This fools the chip into doing 64-bit DMA transfers even though there is no 64-bit data path. To detect this, re_diag() puts the chip into digital loopback mode and sets the receiver to promiscuous mode, then initiates a single 64-byte packet transmission. The frame is echoed back to the host, and if the frame contents are intact, we know DMA is working correctly, otherwise we complain loudly on the console and abort the device attach. (At the moment, I don't know of any way to work around the problem other than physically modifying the board, so until/unless I can think of a software workaround, this will have do to.) - Created re(4) man page - Modified rlphy.c to allow re(4) to attach as well as rl(4). Note that this code works for the sample 8169/Marvell 88E1000 NIC that I have, but probably won't work for the 8169S/8110S chips. RealTek has sent me some sample NICs, but they haven't arrived yet. I will probably need to add an rlgphy driver to handle the on-board PHY in the 8169S/8110S (it needs special DSP initialization).
2003-09-08 02:11:25 +00:00
device re # RealTek 8139C+/8169/8169S/8110S
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device rl # RealTek 8129/8139
device sf # Adaptec AIC-6915 (``Starfire'')
Add driver for Silicon Integrated Systems SiS190/191 Fast/Gigabit Ethernet. This driver was written by Alexander Pohoyda and greatly enhanced by Nikolay Denev. I don't have these hardwares but this driver was tested by Nikolay Denev and xclin. Because SiS didn't release data sheet for this controller, programming information came from Linux driver and OpenSolaris. Unlike other open source driver for SiS190/191, sge(4) takes full advantage of TX/RX checksum offloading and does not require additional copy operation in RX handler. The controller seems to have advanced offloading features like VLAN hardware tag insertion/stripping, TCP segmentation offload(TSO) as well as jumbo frame support but these features are not available yet. Special thanks to xclin <xclin<> cs dot nctu dot edu dot tw> who sent fix for receiving VLAN oversized frames.
2010-04-14 20:45:33 +00:00
device sge # Silicon Integrated Systems SiS190/191
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device sis # Silicon Integrated Systems SiS 900/SiS 7016
Spell Ethernet correctly.
2004-05-02 18:57:29 +00:00
device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ste # Sundance ST201 (D-Link DFE-550TX)
Add asr(4) and stge(4) from i386 GENERIC. Both drivers compile on amd64 and there is no particular reason for them to be i386-only. MFC after: 2 weeks
2009-01-19 07:10:11 +00:00
device stge # Sundance/Tamarack TC9021 gigabit Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device tl # Texas Instruments ThunderLAN
device tx # SMC EtherPower II (83c170 ``EPIC'')
o Use tab instead of spaces for puc(4) line. o Use capitalized "Ethernet" for consistency.
2005-01-05 05:25:21 +00:00
device vge # VIA VT612x gigabit Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device vr # VIA Rhine, Rhine II
device wb # Winbond W89C840F
Update GENERIC/LINT to leave out the useless digit at the end of pci or other unwired devices.
2000-01-23 12:18:53 +00:00
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
Put on my asbestos suit and attempt to tidy up and add some simple docs or notes to make it much more obvious what things are for people who have not committed LINT to memory yet.
1999-06-29 18:55:53 +00:00
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
# ISA Ethernet NICs. pccard NICs included.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device cs # Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
Add back ed(4) in amd64 GENERIC. It now works nicely and since those chips are commonly found, it makes sense to have it in GENERIC. This is a candidate for a RELENG_6 MFC. Approved by; peter Requested by: pav Tested by: pav
2005-07-24 17:55:57 +00:00
device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device ex # Intel EtherExpress Pro/10 and Pro/10+
device ep # Etherlink III based cards
device fe # Fujitsu MB8696x based cards
Spell Ethernet correctly.
2004-05-02 18:57:29 +00:00
device sn # SMC's 9000 series of Ethernet chips
device xe # Xircom pccard Ethernet
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# Wireless NIC cards
device wlan # 802.11 support
Whitespace-only: reduce diff to the i386 GENERIC.
2009-01-19 07:18:32 +00:00
options IEEE80211_DEBUG # enable debug msgs
options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
Improve 802.11s comment. Spotted by: dougb MFC after: 1 day
2009-10-01 02:08:42 +00:00
options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
add ath and wlan crypto support MFC after: 1 month
2006-05-03 18:15:36 +00:00
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
Add wlan_amrr. ural(4) uses amrr as transmit rate control.
2007-05-10 01:39:50 +00:00
device wlan_amrr # AMRR transmit rate control algorithm
GRR. MFi386: white space spam
2004-01-30 03:02:45 +00:00
device an # Aironet 4500/4800 802.11 wireless NICs.
Break out the ath PCI logic into a separate device/module. Introduce the AHB glue for Atheros embedded systems. Right now it's hard-coded for the AR9130 chip whose support isn't yet in this HAL; it'll be added in a subsequent commit. Kernel configuration files now need both 'ath' and 'ath_pci' devices; both modules need to be loaded for the ath device to work.
2011-03-31 08:07:13 +00:00
device ath # Atheros NIC's
device ath_pci # Atheros pci/cardbus glue
Switch to ath hal source code. Note this removes the ath_hal module; the ath module now brings in the hal support. Kernel config files are almost backwards compatible; supplying device ath_hal gives you the same chip support that the binary hal did but you must also include options AH_SUPPORT_AR5416 to enable the extended format descriptors used by 11n parts. It is now possible to control the chip support included in a build by specifying exactly which chips are to be supported in the config file; consult ath_hal(4) for information.
2008-12-01 16:53:01 +00:00
device ath_hal # pci/cardbus chip support
- Use "device\t" and "options \t" for consistency.
2009-05-10 00:00:25 +00:00
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
add ath and wlan crypto support MFC after: 1 month
2006-05-03 18:15:36 +00:00
device ath_rate_sample # SampleRate tx rate control for ath
Add the remaining wireless drivers. Discussed with: joel
2011-05-01 13:26:34 +00:00
#device bwi # Broadcom BCM430x/BCM431x wireless NICs.
#device bwn # Broadcom BCM43xx wireless NICs.
device ipw # Intel 2100 wireless NICs.
device iwi # Intel 2200BG/2225BG/2915ABG wireless NICs.
device iwn # Intel 4965/1000/5000/6000 wireless NICs.
device malo # Marvell Libertas wireless NICs.
device mwl # Marvell 88W8363 802.11n wireless NICs.
Add new ral(4) and ural(4) drivers. Approved by: silby (mentor)
2005-05-24 16:48:07 +00:00
device ral # Ralink Technology RT2500 wireless NICs.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
Add the remaining wireless drivers. Discussed with: joel
2011-05-01 13:26:34 +00:00
device wpi # Intel 3945ABG wireless NICs.
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
In -CURRENT pseudo devices are not statically assigned at compile time, remove a stale comment. PR: kern/62285
2004-07-18 09:03:12 +00:00
# Pseudo devices.
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 loop # Network loopback
Break out the MI part of the /dev/[k]mem and /dev/io drivers into their own directory and module, leaving the MD parts in the MD area (the MD parts _are_ part of the modules). /dev/mem and /dev/io are now loadable modules, thus taking us one step further towards a kernel created entirely out of modules. Of course, there is nothing preventing the kernel from having these statically compiled.
2004-08-01 11:40:54 +00:00
device random # Entropy 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 ether # Ethernet support
Add vlan(4) to all GENERIC kernels. MFC after: 1 week
2010-01-03 20:40:54 +00:00
device vlan # 802.1Q VLAN support
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device tun # Packet tunnel.
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
device pty # BSD-style compatibility pseudo ttys
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
device md # Memory "disks"
device gif # IPv6 and IPv4 tunneling
device faith # IPv6-to-IPv4 relaying (translation)
Make the firmware assist driver resident in preparation for isp using it.
2006-07-09 16:40:31 +00:00
device firmware # firmware assist module
Sync with i386/GENERIC ordering.
2003-06-01 20:26:38 +00:00
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
Add a comment to note that pseudo-device bpf is required for DHCP. This is mentioned in the Handbook but it is not as obvious to new users why bpf is needed compared to the other largely self-explanatory items in GENERIC. PR: conf/40855 MFC after: 1 week
2005-03-18 15:24:00 +00:00
# Note that 'bpf' is required for DHCP.
Sync with i386/GENERIC ordering.
2003-06-01 20:26:38 +00:00
device bpf # Berkeley packet filter
Initial commit of ported NetBSD USB stack
1998-11-26 23:13:13 +00:00
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
# USB support
Set USB_DEBUG like the other platforms, I had turned it off to test the build before committing r207077. Spotted by: marius
2010-04-25 22:01:32 +00:00
options USB_DEBUG # enable debug msgs
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
Add a small change to the comment in the GENRIC config files that include udbp Submitted by: Chris Forgron, cforgeron at acsi dot ca MFC after: 1 week
2011-03-09 17:15:11 +00:00
#device udbp # USB Double Bulk Pipe devices (needs netgraph)
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus and da
device ums # Mouse
device urio # Diamond Rio 500 MP3 player
Add usb serial devices by default. I'm tired of telling people how to do this that should know better :-).
2007-10-26 02:20:29 +00:00
# USB Serial devices
Add the u3g(4) driver. I can't find any reason why it's not here.
2010-07-07 09:23:46 +00:00
device u3g # USB-based 3G modems (Option, Huawei, Sierra)
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device uark # Technologies ARK3116 based serial adapters
device ubsa # Belkin F5U103 and compatible serial adapters
device uftdi # For FTDI usb serial adapters
device uipaq # Some WinCE based devices
device uplcom # Prolific PL-2303 serial adapters
device uslcom # SI Labs CP2101/CP2102 serial adapters
device uvisor # Visor and Palm devices
device uvscom # USB serial support for DDI pocket's PHS
MFi386: Sync whitespace and an abbreviation
2005-02-28 23:39:58 +00:00
# USB Ethernet, requires miibus
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device aue # ADMtek USB Ethernet
device axe # ASIX Electronics USB Ethernet
device cdce # Generic USB over Ethernet
device cue # CATC USB Ethernet
device kue # Kawasaki LSI USB Ethernet
device rue # RealTek RTL8150 USB Ethernet
device udav # Davicom DM9601E USB
Move the USB wireless drivers down into their own section next to the USB ethernet drivers. Submitted by: Glen Barber glen.j.barber @ gmail MFC after: 1 month
2009-10-13 19:02:03 +00:00
# USB Wireless
device rum # Ralink Technology RT2501USB wireless NICs
Add the remaining wireless drivers. Discussed with: joel
2011-05-01 13:26:34 +00:00
device run # Ralink Technology RT2700/RT2800/RT3000 NICs.
Move the USB wireless drivers down into their own section next to the USB ethernet drivers. Submitted by: Glen Barber glen.j.barber @ gmail MFC after: 1 month
2009-10-13 19:02:03 +00:00
device uath # Atheros AR5523 wireless NICs
Add the remaining wireless drivers. Discussed with: joel
2011-05-01 13:26:34 +00:00
device upgt # Conexant/Intersil PrismGT wireless NICs.
Move the USB wireless drivers down into their own section next to the USB ethernet drivers. Submitted by: Glen Barber glen.j.barber @ gmail MFC after: 1 month
2009-10-13 19:02:03 +00:00
device ural # Ralink Technology RT2500USB wireless NICs
Add urtw(4)
2011-04-29 06:36:39 +00:00
device urtw # Realtek RTL8187B/L wireless NICs
Move the USB wireless drivers down into their own section next to the USB ethernet drivers. Submitted by: Glen Barber glen.j.barber @ gmail MFC after: 1 month
2009-10-13 19:02:03 +00:00
device zyd # ZyDAS zb1211/zb1211b wireless NICs
Sync with i386 - add everything that compiles. There are a few drivers that are trivially easy to fix (eg: ips) that I've not committed fixes for.
2003-06-26 03:49:54 +00:00
# FireWire support
device firewire # FireWire bus code
device sbp # SCSI over FireWire (Requires scbus and da)
device fwe # Ethernet over FireWire (non-standard!)
Enable fwip and dcons in GENERIC. They seem fairly stable. Note on dcons: To enable dcons in kernel, put the following lines in /boot/loader.conf. You may also want to enable dcons in /etc/ttys. boot_multicons="YES" #Force dcons to be the high-level console if a firewire bus presents. #hw.firewire.dcons_crom.force_console=1 FireWire/dcons support in loader will come shortly. (i386/amd64 only)
2007-05-28 14:38:43 +00:00
device fwip # IP over FireWire (RFC 2734,3146)
device dcons # Dumb console driver
device dcons_crom # Configuration ROM for dcons
Reference in New Issue Copy Permalink