d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
005e768447
freebsd-skq/sys/i386/conf/GENERIC

341 lines
13 KiB
Plaintext
Raw Normal View History

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
#
updated comments
2000-01-21 20:19:18 +00:00
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
Back out revision 205307. For the record: CPU_ENABLE_SSE enables some code that dynamically enables SSE support but not necessarily enforce execution of SSE instructions.
2010-03-19 16:09:57 +00:00
cpu I486_CPU
cpu I586_CPU
De-quote where possible and minor tweaks. depends on a current config(8).
1999-04-24 21:45:44 +00:00
cpu I686_CPU
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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
options INET # InterNETworking
options INET6 # IPv6 communications protocols
Use the correct expanded name for SCTP. PR: 116496 Submitted by: koitsu Reviewed by: rrs Approved by: re (kensmith)
2007-09-26 20:05:07 +00:00
options SCTP # Stream Control Transmission Protocol
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # 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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
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.
Turn on USB support for most USB devices. udbp is not turned on since NETGRAPH is not present in GENERIC at the moment. Also, change some settings to support USB installs: - Add KBD_INSTALL_CDEV as an option to make /dev/kbd[01] actually work. - Turn on keyboard probing in sc0. The syscons driver will now use a flag documented in ukbd(4) but not in sc(4) that tells syscons to actively search for a keyboard device if none is found. This allows USB keyboards to just be plugged in and instantly start working. - Require the atkbd0 driver to actually probe to see if a keyboard is there. This allows USB keyboards to be seen by sc0 if an AT keyboard isn't plugged into the computer. This also means that you will no longer be able to plug an AT keyboard into a machine after it has booted a GENERIC kernel and use it. AT keyboards aren't designed for this anyway. USB keyboards are designed for this, and they work.
2000-05-12 03:05:35 +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
Fix whitespace nits. PR: conf/148989 Submitted by: pluknet <pluknet at gmail.com> MFC after: 3 days
2010-08-06 18:46:27 +00:00
options FLOWTABLE # per-cpu routing cache
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_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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
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
- Indent the comments beside the SMP options to the same level as all the other comments. Clarify that the next two things needed for SMP are two lines. - Expand mii abbreviation to miibus for clarity in the USB ethernet comment.
2004-12-30 15:30:23 +00:00
# To make an SMP kernel, the next two lines are needed
options SMP # Symmetric MultiProcessor Kernel
device apic # I/O APIC
Add commented out SMP stuff in GENERIC, remove stale configs.
1998-12-27 13:12:59 +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
Create a default kernel config for i386 and move 'device isa' and 'device npx' (both of which aren't really optional right now) and 'device io' and 'device mem' (to preserve POLA for 4.x users upgrading to 6.0) from GENERIC into DEFAULTS. Requested by: scottl Reviewed by: scottl
2005-10-27 17:34:35 +00:00
# Bus support.
Add 'device acpi' to GENERIC on i386. Most newer i386 machines require it, so the benefit of having acpi.ko as a standalone module is outweighed by the complications of drivers compiled into the kernel not including ACPI attachments by default. Discussed on: current
2008-09-16 20:22:22 +00:00
device acpi
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 eisa
de-count pci
2002-07-23 06:38:47 +00:00
device pci
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
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
# Floppy drives
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 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
Finally use the new ata driver.
1999-12-08 09:19:37 +00:00
# ATA and ATAPI devices
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 ata
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID # Static device numbering
Add a commented out 'ATA' driver config block to help assist -CURRENT people to migrate to this driver since it will be the default IDE/ATA/ATAPI driver in 4.0-R.
1999-11-27 23:25:17 +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
# SCSI Controllers
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 ahb # EISA AHA1742 family
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.
Enable ahd/ahc register pretty printing by default. This expedites handling of bug reports.
2002-08-31 06:56:43 +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.
Spelling and capitalization fixes. Reviewed by: gshapiro, jake, jhb, rwatson (all within 30 seconds)
2001-03-07 04:58:38 +00:00
device amd # AMD 53C974 (Tekram DC-390(T))
o Fix typo: comments start by "#" not "*".
2007-05-09 11:43:04 +00:00
device hptiop # Highpoint RocketRaid 3xxx series
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 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
Add support for the LSI-Logic Fusion/MP architecture. This is an architecture that present a thing message passing interface to the OS. You can query as to how many ports and what kind are attached and enable them and so on. A less grand view is that this is just another way to package SCSI (SPI or FC) and FC-IP into a one-driver interface set. This driver support the following hardware: LSI FC909: Single channel, 1Gbps, Fibre Channel (FC-SCSI only) LSI FC929: Dual Channel, 1-2Gbps, Fibre Channel (FC-SCSI only) LSI 53c1020: Single Channel, Ultra4 (320M) (Untested) LSI 53c1030: Dual Channel, Ultra4 (320M) Currently it's in fair shape, but expect a lot of changes over the next few weeks as it stabilizes. Credits: The driver is mostly from some folks from Jeff Roberson's company- I've been slowly migrating it to broader support that I it came to me as. The hardware used in developing support came from: FC909: LSI-Logic, Advansys (now Connetix) FC929: LSI-Logic 53c1030: Antares Microsystems (they make a very fine board!) MFC after: 3 weeks
2002-08-11 23:34:20 +00:00
device mpt # LSI-Logic MPT-Fusion
Comment out `ncr' as `sym' handles all that `ncr' does. (only commented out to make it easy for people to find it that really wants it.) Asked for by: Peter
2000-07-29 01:31:09 +00:00
#device ncr # NCR/Symbios Logic
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
Add the trm(4) driver. MFC after: 1 day
2002-12-16 18:47:37 +00:00
device trm # Tekram DC395U/UW/F DC315U adapters
s/controller/device/ as per config(8) changes
2000-01-08 15:59:12 +00:00
Spelling and capitalization fixes. Reviewed by: gshapiro, jake, jhb, rwatson (all within 30 seconds)
2001-03-07 04:58:38 +00:00
device adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aha # Adaptec 154x SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adapters
Put UCONSOLE back - I was wrong, it's still used in one last place. Submitted by: ollivier
1995-01-14 02:39:22 +00:00
Add PC-Card/ISA SCSI host adpater drivers from NetBSD/pc98 (a NetBSD port for NEC PC-98x1 machines). They are ncv for NCR 53C500, nsp for Workbit Ninja SCSI-3, and stg for TMC 18C30 and 18C50. I thank NetBSD/pc98 and bsd-nomads people. Obtained from: NetBSD/pc98
2000-10-23 12:55:51 +00:00
device ncv # NCR 53C500
device nsp # Workbit Ninja SCSI-3
device stg # TMC 18C30/18C50
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
# SCSI peripherals
Note that scbus is required for SCSI, not just "required" in general. Submitted by: Edward Kaplan (tmbg37 on IRC) Reviewed by: rwatson (in principle)
2003-06-08 02:03:02 +00:00
device scbus # SCSI bus (required for SCSI)
Make SCSI changer and SES devices standard in generic kernels. Reviewed by: ken@kdm.org
2001-10-16 22:22:58 +00:00
device ch # SCSI media changers
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 da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
Make SCSI changer and SES devices standard in generic kernels. Reviewed by: ken@kdm.org
2001-10-16 22:22:58 +00:00
device ses # SCSI Environmental Services (and SAF-TE)
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
Re-arrange the raid section a small bit and put drivers into their proper category.
2003-09-09 06:36:32 +00:00
# RAID controllers interfaced to the SCSI subsystem
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
Re-arrange the raid section a small bit and put drivers into their proper category.
2003-09-09 06:36:32 +00:00
device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID
device ciss # Compaq Smart RAID 5*
device dpt # DPT Smartcache III, IV - See NOTES for options
Hook the hptmv driver up to the build.
2004-10-24 08:53:40 +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
Re-arrange the raid section a small bit and put drivers into their proper category.
2003-09-09 06:36:32 +00:00
device iir # Intel Integrated RAID
device ips # IBM (Adaptec) ServeRAID
device mly # Mylex AcceleRAID/eXtremeRAID
Initial check-in of the device driver for 3ware's 9000 series PATA/SATA RAID controllers. This driver is a SIM under CAM, and so, behaves like a driver for a SCSI controller.
2004-03-30 03:46:00 +00:00
device twa # 3ware 9000 series PATA/SATA RAID
Re-arrange the raid section a small bit and put drivers into their proper category.
2003-09-09 06:36:32 +00:00
Revert previous commit. Not all RAID controllers are SCSI.
2000-07-29 02:12:44 +00:00
# RAID controllers
A new driver for PCI:SCSI RAID controllers based on the Adaptec FSA design. This includes integrated Dell RAID controllers, the Dell PERC 2/QC and the HP NetRAID-4M.
2000-09-13 03:20:35 +00:00
device aac # Adaptec FSA RAID
Add a CAM interface to the aac driver. This is useful in case you should ever connect a SCSI Cdrom/Tape/Jukebox/Scanner/Printer/kitty-litter-scooper to your high-end RAID controller. The interface to the arrays is still via the block interface; this merely provides a way to circumvent the RAID functionality and access the SCSI buses directly. Note that for somewhat obvious reasons, hard drives are not exposed to the da driver through this interface, though you can still talk to them via the pass driver. Be the first on your block to low-level format unsuspecting drives that are part of an array! To enable this, add the 'aacp' device to your kernel config. MFC after: 3 days
2002-04-27 01:31:17 +00:00
device aacp # SCSI passthrough for aac (requires CAM)
Minor ordering changes to make more sections strictly alphabetical.
2000-11-07 21:06:57 +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
Revert previous commit. Not all RAID controllers are SCSI.
2000-07-29 02:12:44 +00:00
device mlx # Mylex DAC960 family
Add the pst (Promise SX6000) driver to GENERIC.
2002-09-27 19:09:21 +00:00
device pst # Promise Supertrak SX6000
Bring the 'twe' driver back now that we think it should work.
2000-10-12 01:46:43 +00:00
device twe # 3ware ATA RAID
Revert previous commit. Not all RAID controllers are SCSI.
2000-07-29 02:12:44 +00:00
Spelling police
1999-04-19 10:18:34 +00:00
# atkbdc0 controls both the keyboard and the PS/2 mouse
remove unit counts from atkbdc, pckbd, sc
2002-08-20 00:10:22 +00:00
device atkbdc # AT keyboard controller
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +00:00
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 Requested by: scottl
2006-03-31 19:03:37 +00:00
device kbdmux # keyboard multiplexer
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +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
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +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
remove unit counts from atkbdc, pckbd, sc
2002-08-20 00:10:22 +00:00
device sc
De-quote where possible and minor tweaks. depends on a current config(8).
1999-04-24 21:45:44 +00:00
Add device agp to GENERIC, filter it out of floppy builds Approved by: des (mentor)
2002-08-04 18:35:02 +00:00
device agp # support several AGP chipsets
s%LINT%NOTES%g
2000-07-25 08:25:48 +00:00
# Power management support (see NOTES for more options)
Comment out apm; ACPI is the modern replacement, and folks who really need it can uncomment it. This may buy us some kernel space. Discussed with: imp & msmith (quite a while ago)
2002-07-08 11:56:44 +00:00
#device apm
Add pmtimer device, necessary for proper time keeping when apm or other power management devices are enabled.
2000-11-15 18:36:24 +00:00
# Add suspend/resume support for the i8254.
device pmtimer
Sanitize APM a bit. Convert various #ifdef to id_flags instead. You may want to add "flags 0x31" to apm0 if you have a lousy implementation. Read LINT.
1997-03-29 11:07:12 +00:00
Added commented out PCCARD entries to GENERIC, also document and add entries in LINT.
1996-05-13 04:29:14 +00:00
# PCCARD (PCMCIA) support
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +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
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 ppc
Some formatting cleanups and remove comments about numbers of units that were intended to head off confusion about the trailing '0'.
2000-01-23 18:30:35 +00:00
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
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
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
This commit adds device driver support for the Sundance Technologies ST201 PCI fast ethernet controller. Currently, the only card I know that uses this chip is the D-Link DFE-550TX. (Don't ask me where to buy these: the only cards I have are samples sent to me by D-Link.) This driver is the first to make use of the miibus code once I'm sure it all works together nicely, I'll start converting the other drivers. The Sundance chip is a clone of the 3Com 3c90x Etherlink XL design only with its own register layout. Support is provided for ifmedia, hardware multicast filtering, bridging and promiscuous mode.
1999-08-21 18:34:58 +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
# PCI Ethernet 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 de # DEC/Intel DC21x4x (``Tulip'')
Add igb driver to the default kernel
2008-07-30 22:30:49 +00:00
device em # Intel PRO/1000 Gigabit Ethernet Family
device igb # Intel PRO/1000 PCIE Server Gigabit Family
First release of ixgb driver for the Intel(R) PRO/10GbE Family of Adapters. This driver has been developed for use with FreeBSD, version 4.8 and later. Submitted by: Hema Joyce Reviewed by: Prafulla Deuskar Approved by: Prafulla Deuskar MFC after: 1 week
2004-05-28 00:23:00 +00:00
device ixgb # Intel PRO/10GbE Ethernet Card
- As only the PCI front-end of le(4) is common to all platforms move its entry to the PCI NICs section so it's in the same spot in all GENERIC config files. - Add a note to the description of pcn(4) informing that is has precedence over le(4).
2006-05-17 20:44:01 +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
You were knocked senseless by the Boomerang, spun around by the Cyclone, blown over by the Hurricane and had a house dropped on you by the Tornado. Now it's time to have your parade rained on by... the Typhoon! This commit adds driver support for 3Com 3cR990 10/100 ethernet adapters based on the Typhoon I and Typhoon II chipsets. This is actually a port of the OpenBSD driver with many hacks by me. No Virginia, there isn't any support for the hardware crypto yet. However there is support for TCP/IP checksum offload and VLANs. Special thanks go to Jason Wright, Aaron Campbell and Theo de Raadt for squeezing enough info out of 3Com to get this written, and for doing most of the hard work. Manual page is included. Compiled as a module and included in GENERIC.
2001-07-23 20:44:54 +00:00
device txp # 3Com 3cR990 (``Typhoon'')
+ Fix misplacement of `txp' + Document our -CURRENT debugging bits
2001-09-24 03:23:48 +00:00
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
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 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
- As only the PCI front-end of le(4) is common to all platforms move its entry to the PCI NICs section so it's in the same spot in all GENERIC config files. - Add a note to the description of pcn(4) informing that is has precedence over le(4).
2006-05-17 20:44:01 +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
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 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
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 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
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 ste # Sundance ST201 (D-Link DFE-550TX)
Add stge(4) to the list of drivers supported by GENERIC kernel.
2006-07-25 01:06:32 +00:00
device stge # Sundance/Tamarack TC9021 gigabit Ethernet
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 tl # Texas Instruments ThunderLAN
Synced tx(4) driver descriptions + ``device tx'' line moved to the list of drivers using miibus. PR: kern/22556
2000-11-07 20:22:19 +00:00
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
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 vr # VIA Rhine, Rhine II
Add driver for DM&P Vortex86 RDC R6040 Fast Ethernet. The controller is commonly found on DM&P Vortex86 x86 SoC. The driver supports all hardware features except flow control. The flow control was intentionally disabled due to silicon bug. DM&P Electronics, Inc. provided all necessary information including sample board to write driver and answered many questions I had. Many thanks for their support of FreeBSD. H/W donated by: DM&P Electronics, Inc.
2010-12-31 00:21:41 +00:00
device vte # DM&P Vortex86 RDC R6040 Fast Ethernet
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 wb # Winbond W89C840F
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
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
# ISA Ethernet NICs. pccard NICs included.
Make the ISA nic section look like the other device sections with comments on the same line like so: device foo # FooInc Brand NetEther cards Also, move the wireless NIC cards to their own section. Add commented out wl driver in wireless section. Remove obsolete or redundant comments about some of the wireless cards that used to apply but don't since we've removed 'at foobus'. There should be no functional changes in this change.
2000-11-07 21:20:52 +00:00
device cs # Crystal Semiconductor CS89x0 NIC
Add support for Dlink DL10022 to the ed driver. This is a mii part bolted to a ne-2000 chip. This is necessary for the NetGear FA-410TX and other cards. This also requires you add mii to your kernel if you have an ed driver configured. This code will result in a couple of timeout messages for ed on the impacted cards. Additional work will be needed, but this does work right now, and many people need these cards. Submitted by: Ian Dowse <iedowse@maths.tcd.ie>
2001-03-03 08:31:37 +00:00
# 'device ed' requires 'device miibus'
Make the ISA nic section look like the other device sections with comments on the same line like so: device foo # FooInc Brand NetEther cards Also, move the wireless NIC cards to their own section. Add commented out wl driver in wireless section. Remove obsolete or redundant comments about some of the wireless cards that used to apply but don't since we've removed 'at foobus'. There should be no functional changes in this change.
2000-11-07 21:20:52 +00:00
device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
device ex # Intel EtherExpress Pro/10 and Pro/10+
device ep # Etherlink III based cards
device fe # Fujitsu MB8696x based cards
- Move driver to newbus. - Provide identify methods for EtherExpress and 3c507 cards; this means these cards no longer need wired configs. - Provide a detach method.
2003-03-29 13:36:41 +00:00
device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc.
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
Minor ordering changes to make more sections strictly alphabetical.
2000-11-07 21:06:57 +00:00
Make the ISA nic section look like the other device sections with comments on the same line like so: device foo # FooInc Brand NetEther cards Also, move the wireless NIC cards to their own section. Add commented out wl driver in wireless section. Remove obsolete or redundant comments about some of the wireless cards that used to apply but don't since we've removed 'at foobus'. There should be no functional changes in this change.
2000-11-07 21:20:52 +00:00
# Wireless NIC cards
wi now needs wlan Reviewed by: imp
2003-01-16 00:21:52 +00:00
device wlan # 802.11 support
Use the "options " spelling (vs. "options<TAB>") so that commented lines line up nicely.
2008-05-21 03:36:53 +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 Requested by: many MFC after: 1 month
2006-05-03 18:13:11 +00:00
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
Add support for Ralink Technology RT2501USB/RT2601USB devices. Reviewed by: sam, sephe Obtained from: OpenBSD
2007-05-06 10:07:21 +00:00
device wlan_amrr # AMRR transmit rate control algorithm
Consistently capitalize acronyms like POSIX and NIC. Style.
2004-01-29 21:24:53 +00:00
device an # Aironet 4500/4800 802.11 wireless NICs.
add ath and wlan crypto support Requested by: many MFC after: 1 month
2006-05-03 18:13:11 +00:00
device ath # Atheros pci/cardbus NIC's
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 Requested by: many MFC after: 1 month
2006-05-03 18:13:11 +00:00
device ath_rate_sample # SampleRate tx rate control for ath
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.
re-enable wi: was accidentally disabled in r1.502
2009-01-19 17:20:09 +00:00
device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
Make the ISA nic section look like the other device sections with comments on the same line like so: device foo # FooInc Brand NetEther cards Also, move the wireless NIC cards to their own section. Add commented out wl driver in wireless section. Remove obsolete or redundant comments about some of the wireless cards that used to apply but don't since we've removed 'at foobus'. There should be no functional changes in this change.
2000-11-07 21:20:52 +00:00
#device wl # Older non 802.11 Wavelan wireless NIC.
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
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 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
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 md # Memory "disks"
gif(4) and stf(4) modernization: - Remove gif dependencies from stf. - Make gif and stf into modules - Make gif cloneable. PR: kern/27983 Reviewed by: ru, ume Obtained from: NetBSD MFC after: 1 week
2001-07-02 21:02:09 +00:00
device gif # IPv6 and IPv4 tunneling
The faith(4) device is no longer a count device so don't specify a count.
2001-09-25 18:56:40 +00:00
device faith # IPv6-to-IPv4 relaying (translation)
Make the firmware assist driver resident in preparation for isp using it. Reviewed by: sam, max
2006-07-09 16:41:22 +00:00
device firmware # firmware assist module
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
# The `bpf' device enables the Berkeley Packet Filter.
Enable bpf by default. There was no significant dissention to my proposal of 2 weeks ago that this be done, and anyone who wishes to make bpf more selective according to securelevel or compile-time options is more than free to do so.
1999-08-07 01:42:08 +00:00
# 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.
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 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
Change USB_DEBUG to #ifdef and allow it to be turned off. Previously this had the illusion of a tunable setting but was always turned on regardless. MFC after: 1 week
2010-04-22 21:31:34 +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)
The USB double bulk pipe driver (Host to host cables). Currently there are two supported chips, the NetChip 1080 (only prototypes available) and the EzLink cable. Any other cable should be supported however as they are all very much alike (there is a difference between them wrt performance). It uses Netgraph. This driver was mostly written by Doug Ambrisko and Julian Elischer and I would like to thank Whistle for yet another contribution. And my aplogies to them for me sitting on the driver for so long (2 months). Also, many thanks to Reid Augustin from NetChip for providing me with a prototype of their 1080 chip. Be aware of the fact that this driver is very immature and has only been tested very lightly. If someone feels like learning about Netgraph however this is an excellent driver to start playing with.
2000-05-01 22:48:23 +00:00
#device udbp # USB Double Bulk Pipe devices
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
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 u3g # USB-based 3G modems (Option, Huawei, Sierra)
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
- Indent the comments beside the SMP options to the same level as all the other comments. Clarify that the next two things needed for SMP are two lines. - Expand mii abbreviation to miibus for clarity in the USB ethernet comment.
2004-12-30 15:30:23 +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
device uath # Atheros AR5523 wireless NICs
device ural # Ralink Technology RT2500USB wireless NICs
device zyd # ZyDAS zb1211/zb1211b wireless NICs
Add FireWire drivers to GENERIC.
2003-04-21 16:44:05 +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