1994-10-17 21:10:20 +00:00
|
|
|
#
|
2000-01-21 20:19:18 +00:00
|
|
|
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
|
1994-10-17 21:10:20 +00:00
|
|
|
#
|
1999-06-20 03:36:46 +00:00
|
|
|
# For more information on this file, please read the handbook section on
|
|
|
|
# Kernel Configuration Files:
|
1994-10-17 21:10:20 +00:00
|
|
|
#
|
2002-08-01 17:21:18 +00:00
|
|
|
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
|
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
|
2000-05-13 11:21:19 +00:00
|
|
|
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
|
1999-06-20 03:36:46 +00:00
|
|
|
# latest information.
|
|
|
|
#
|
|
|
|
# An exhaustive list of options and more detailed explanations of the
|
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
|
2002-07-16 18:20:17 +00:00
|
|
|
# in NOTES.
|
1996-08-27 16:25:53 +00:00
|
|
|
#
|
1999-08-28 01:08:13 +00:00
|
|
|
# $FreeBSD$
|
1994-10-17 21:10:20 +00:00
|
|
|
|
1999-04-24 21:45:44 +00:00
|
|
|
cpu I486_CPU
|
|
|
|
cpu I586_CPU
|
|
|
|
cpu I686_CPU
|
1994-10-17 21:10:20 +00:00
|
|
|
ident GENERIC
|
|
|
|
|
2004-01-29 21:24:53 +00:00
|
|
|
# To statically compile in device wiring instead of /boot/device.hints
|
|
|
|
#hints "GENERIC.hints" # Default places to look for devices.
|
|
|
|
|
|
|
|
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
|
|
|
|
|
2007-10-19 12:30:33 +00:00
|
|
|
options SCHED_ULE # ULE scheduler
|
2004-09-07 22:37:43 +00:00
|
|
|
options PREEMPTION # Enable kernel thread preemption
|
2004-01-29 21:24:53 +00:00
|
|
|
options INET # InterNETworking
|
|
|
|
options INET6 # IPv6 communications protocols
|
2007-09-26 20:05:07 +00:00
|
|
|
options SCTP # Stream Control Transmission Protocol
|
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
|
2007-04-10 21:40:13 +00:00
|
|
|
options UFS_GJOURNAL # Enable gjournal-based UFS journaling
|
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
|
2008-03-27 11:54:20 +00:00
|
|
|
options NFSLOCKD # Network Lock Manager
|
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
|
2007-02-07 18:55:31 +00:00
|
|
|
options GEOM_PART_GPT # GUID Partition Tables.
|
2007-02-09 19:03:18 +00:00
|
|
|
options GEOM_LABEL # Provides labelization
|
2008-12-02 19:09:08 +00:00
|
|
|
options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty)
|
2004-01-29 21:24:53 +00:00
|
|
|
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
|
2005-07-14 15:39:06 +00:00
|
|
|
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
|
2006-09-26 12:36:34 +00:00
|
|
|
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
|
2008-01-07 21:40:11 +00:00
|
|
|
options COMPAT_FREEBSD7 # Compatible with FreeBSD7
|
2004-11-02 20:57:20 +00:00
|
|
|
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
|
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
|
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
|
2000-05-12 03:05:35 +00:00
|
|
|
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
|
2005-11-01 22:59:03 +00:00
|
|
|
options STOP_NMI # Stop CPUS using NMI instead of IPI
|
2008-07-07 22:55:11 +00:00
|
|
|
options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4)
|
2007-06-08 20:29:07 +00:00
|
|
|
options AUDIT # Security event auditing
|
2009-01-05 14:21:49 +00:00
|
|
|
#options KDTRACE_HOOKS # Kernel DTrace hooks
|
1994-10-17 21:10:20 +00:00
|
|
|
|
2001-04-15 19:37:28 +00:00
|
|
|
# Debugging for use in -current
|
2004-07-11 03:20:09 +00:00
|
|
|
options KDB # Enable kernel debugger support.
|
|
|
|
options DDB # Support DDB.
|
|
|
|
options GDB # Support remote GDB.
|
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
|
2001-04-15 19:37:28 +00:00
|
|
|
|
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
|
1998-12-27 13:12:59 +00:00
|
|
|
|
2007-07-01 21:47:45 +00:00
|
|
|
# CPU frequency control
|
|
|
|
device cpufreq
|
|
|
|
|
2005-10-27 17:34:35 +00:00
|
|
|
# Bus support.
|
2008-09-16 20:22:22 +00:00
|
|
|
device acpi
|
2000-01-23 12:18:53 +00:00
|
|
|
device eisa
|
2002-07-23 06:38:47 +00:00
|
|
|
device pci
|
1994-10-17 21:10:20 +00:00
|
|
|
|
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
|
1994-10-17 21:10:20 +00:00
|
|
|
|
1999-12-08 09:19:37 +00:00
|
|
|
# ATA and ATAPI devices
|
2000-01-23 12:18:53 +00:00
|
|
|
device ata
|
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
|
1999-11-27 23:25:17 +00:00
|
|
|
|
1999-06-29 18:55:53 +00:00
|
|
|
# SCSI Controllers
|
2000-01-23 12:18:53 +00:00
|
|
|
device ahb # EISA AHA1742 family
|
|
|
|
device ahc # AHA2940 and onboard AIC7xxx devices
|
2006-04-24 08:44:34 +00:00
|
|
|
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
|
|
|
|
# output. Adds ~128k to driver.
|
2002-08-31 06:56:43 +00:00
|
|
|
device ahd # AHA39320/29320 and onboard AIC79xx devices
|
2006-04-24 08:44:34 +00:00
|
|
|
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
|
|
|
|
# output. Adds ~215k to driver.
|
2001-03-07 04:58:38 +00:00
|
|
|
device amd # AMD 53C974 (Tekram DC-390(T))
|
2007-05-09 11:43:04 +00:00
|
|
|
device hptiop # Highpoint RocketRaid 3xxx series
|
2000-01-23 12:18:53 +00:00
|
|
|
device isp # Qlogic family
|
2004-09-19 00:52:22 +00:00
|
|
|
#device ispfw # Firmware for QLogic HBAs- normally a module
|
2002-08-11 23:34:20 +00:00
|
|
|
device mpt # LSI-Logic MPT-Fusion
|
2000-07-29 01:31:09 +00:00
|
|
|
#device ncr # NCR/Symbios Logic
|
|
|
|
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
|
2002-12-16 18:47:37 +00:00
|
|
|
device trm # Tekram DC395U/UW/F DC315U adapters
|
2000-01-08 15:59:12 +00:00
|
|
|
|
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
|
1995-01-14 02:39:22 +00:00
|
|
|
|
2000-10-23 12:55:51 +00:00
|
|
|
device ncv # NCR 53C500
|
|
|
|
device nsp # Workbit Ninja SCSI-3
|
|
|
|
device stg # TMC 18C30/18C50
|
|
|
|
|
1999-06-29 18:55:53 +00:00
|
|
|
# SCSI peripherals
|
2003-06-08 02:03:02 +00:00
|
|
|
device scbus # SCSI bus (required for SCSI)
|
2001-10-16 22:22:58 +00:00
|
|
|
device ch # SCSI media changers
|
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)
|
2001-10-16 22:22:58 +00:00
|
|
|
device ses # SCSI Environmental Services (and SAF-TE)
|
1994-10-17 21:10:20 +00:00
|
|
|
|
2003-09-09 06:36:32 +00:00
|
|
|
# RAID controllers interfaced to the SCSI subsystem
|
|
|
|
device amr # AMI MegaRAID
|
2005-03-31 20:21:43 +00:00
|
|
|
device arcmsr # Areca SATA II RAID
|
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
|
2004-10-24 08:53:40 +00:00
|
|
|
device hptmv # Highpoint RocketRAID 182x
|
2007-12-15 00:56:17 +00:00
|
|
|
device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
|
2003-09-09 06:36:32 +00:00
|
|
|
device iir # Intel Integrated RAID
|
|
|
|
device ips # IBM (Adaptec) ServeRAID
|
|
|
|
device mly # Mylex AcceleRAID/eXtremeRAID
|
2004-03-30 03:46:00 +00:00
|
|
|
device twa # 3ware 9000 series PATA/SATA RAID
|
2003-09-09 06:36:32 +00:00
|
|
|
|
2000-07-29 02:12:44 +00:00
|
|
|
# RAID controllers
|
2000-09-13 03:20:35 +00:00
|
|
|
device aac # Adaptec FSA RAID
|
2002-04-27 01:31:17 +00:00
|
|
|
device aacp # SCSI passthrough for aac (requires CAM)
|
2000-11-07 21:06:57 +00:00
|
|
|
device ida # Compaq Smart RAID
|
2006-03-29 09:57:22 +00:00
|
|
|
device mfi # LSI MegaRAID SAS
|
2000-07-29 02:12:44 +00:00
|
|
|
device mlx # Mylex DAC960 family
|
2002-09-27 19:09:21 +00:00
|
|
|
device pst # Promise Supertrak SX6000
|
2000-10-12 01:46:43 +00:00
|
|
|
device twe # 3ware ATA RAID
|
2000-07-29 02:12:44 +00:00
|
|
|
|
1999-04-19 10:18:34 +00:00
|
|
|
# atkbdc0 controls both the keyboard and the PS/2 mouse
|
2002-08-20 00:10:22 +00:00
|
|
|
device atkbdc # AT keyboard controller
|
2002-07-16 18:20:17 +00:00
|
|
|
device atkbd # AT keyboard
|
|
|
|
device psm # PS/2 mouse
|
1999-01-11 03:18:56 +00:00
|
|
|
|
2006-03-31 19:03:37 +00:00
|
|
|
device kbdmux # keyboard multiplexer
|
|
|
|
|
2002-07-16 18:20:17 +00:00
|
|
|
device vga # VGA video card driver
|
1999-01-11 03:18:56 +00:00
|
|
|
|
2002-07-16 18:20:17 +00:00
|
|
|
device splash # Splash screen and screen saver support
|
1999-01-11 03:18:56 +00:00
|
|
|
|
1999-01-01 08:09:58 +00:00
|
|
|
# syscons is the default console driver, resembling an SCO console
|
2002-08-20 00:10:22 +00:00
|
|
|
device sc
|
1999-04-24 21:45:44 +00:00
|
|
|
|
2002-08-04 18:35:02 +00:00
|
|
|
device agp # support several AGP chipsets
|
|
|
|
|
2000-07-25 08:25:48 +00:00
|
|
|
# Power management support (see NOTES for more options)
|
2002-07-08 11:56:44 +00:00
|
|
|
#device apm
|
2000-11-15 18:36:24 +00:00
|
|
|
# Add suspend/resume support for the i8254.
|
|
|
|
device pmtimer
|
1997-03-29 11:07:12 +00:00
|
|
|
|
1996-05-13 04:29:14 +00:00
|
|
|
# PCCARD (PCMCIA) support
|
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
|
1996-04-22 19:40:28 +00:00
|
|
|
|
1999-06-29 18:55:53 +00:00
|
|
|
# Serial (COM) ports
|
2005-11-05 19:48:53 +00:00
|
|
|
device uart # Generic UART driver
|
1994-10-17 21:10:20 +00:00
|
|
|
|
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
|
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
|
1999-06-29 18:55:53 +00:00
|
|
|
|
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
|
2005-11-05 19:48:53 +00:00
|
|
|
# line to enable it (connects to sio, uart and/or ppc drivers):
|
2005-01-05 05:25:21 +00:00
|
|
|
#device puc
|
1999-08-21 18:34:58 +00:00
|
|
|
|
1999-06-29 18:55:53 +00:00
|
|
|
# PCI Ethernet NICs.
|
2000-01-23 12:18:53 +00:00
|
|
|
device de # DEC/Intel DC21x4x (``Tulip'')
|
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
|
2004-05-28 00:23:00 +00:00
|
|
|
device ixgb # Intel PRO/10GbE Ethernet Card
|
2006-05-17 20:44:01 +00:00
|
|
|
device le # AMD Am7900 LANCE and Am79C9xx PCnet
|
2008-05-17 23:50:00 +00:00
|
|
|
device ti # Alteon Networks Tigon I/II gigabit Ethernet
|
2001-07-23 20:44:54 +00:00
|
|
|
device txp # 3Com 3cR990 (``Typhoon'')
|
2001-09-24 03:23:48 +00:00
|
|
|
device vx # 3Com 3c590, 3c595 (``Vortex'')
|
1999-09-09 18:30:58 +00:00
|
|
|
|
|
|
|
# PCI Ethernet NICs that use the common MII bus controller code.
|
2000-10-28 22:32:17 +00:00
|
|
|
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
|
2000-01-23 12:18:53 +00:00
|
|
|
device miibus # MII bus support
|
2008-10-03 10:31:31 +00:00
|
|
|
device ae # Attansic/Atheros L2 FastEthernet
|
2008-05-19 02:30:27 +00:00
|
|
|
device age # Attansic/Atheros L1 Gigabit Ethernet
|
2008-11-12 09:52:06 +00:00
|
|
|
device ale # Atheros AR8121/AR8113/AR8114 Ethernet
|
2006-04-10 20:04:22 +00:00
|
|
|
device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
|
2004-05-02 18:57:29 +00:00
|
|
|
device bfe # Broadcom BCM440x 10/100 Ethernet
|
2003-09-10 18:54:59 +00:00
|
|
|
device bge # Broadcom BCM570xx Gigabit Ethernet
|
2000-01-23 12:18:53 +00:00
|
|
|
device dc # DEC/Intel 21143 and various workalikes
|
2008-06-20 19:28:33 +00:00
|
|
|
device et # Agere ET1310 10/100/Gigabit Ethernet
|
2001-03-12 21:51:07 +00:00
|
|
|
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
|
2008-05-27 02:22:32 +00:00
|
|
|
device jme # JMicron JMC250 Gigabit/JMC260 Fast Ethernet
|
2005-01-05 05:25:21 +00:00
|
|
|
device lge # Level 1 LXT1001 gigabit Ethernet
|
2006-12-13 03:41:47 +00:00
|
|
|
device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet
|
2007-06-12 02:24:30 +00:00
|
|
|
device nfe # nVidia nForce MCP on-board Ethernet
|
2005-01-05 05:25:21 +00:00
|
|
|
device nge # NatSemi DP83820 gigabit Ethernet
|
2007-06-12 02:24:30 +00:00
|
|
|
#device nve # nVidia nForce MCP on-board Ethernet Networking
|
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
|
2000-01-23 12:18:53 +00:00
|
|
|
device rl # RealTek 8129/8139
|
|
|
|
device sf # Adaptec AIC-6915 (``Starfire'')
|
|
|
|
device sis # Silicon Integrated Systems SiS 900/SiS 7016
|
2004-05-02 18:57:29 +00:00
|
|
|
device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
|
2000-01-23 12:18:53 +00:00
|
|
|
device ste # Sundance ST201 (D-Link DFE-550TX)
|
2006-07-25 01:06:32 +00:00
|
|
|
device stge # Sundance/Tamarack TC9021 gigabit Ethernet
|
2000-01-23 12:18:53 +00:00
|
|
|
device tl # Texas Instruments ThunderLAN
|
2000-11-07 20:22:19 +00:00
|
|
|
device tx # SMC EtherPower II (83c170 ``EPIC'')
|
2005-01-05 05:25:21 +00:00
|
|
|
device vge # VIA VT612x gigabit Ethernet
|
2000-01-23 12:18:53 +00:00
|
|
|
device vr # VIA Rhine, Rhine II
|
|
|
|
device wb # Winbond W89C840F
|
|
|
|
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
|
1999-06-29 18:55:53 +00:00
|
|
|
|
2004-01-29 21:24:53 +00:00
|
|
|
# ISA Ethernet NICs. pccard NICs included.
|
2000-11-07 21:20:52 +00:00
|
|
|
device cs # Crystal Semiconductor CS89x0 NIC
|
2001-03-03 08:31:37 +00:00
|
|
|
# 'device ed' requires 'device miibus'
|
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
|
2003-03-29 13:36:41 +00:00
|
|
|
device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc.
|
2004-05-02 18:57:29 +00:00
|
|
|
device sn # SMC's 9000 series of Ethernet chips
|
|
|
|
device xe # Xircom pccard Ethernet
|
2000-11-07 21:06:57 +00:00
|
|
|
|
2000-11-07 21:20:52 +00:00
|
|
|
# Wireless NIC cards
|
2003-01-16 00:21:52 +00:00
|
|
|
device wlan # 802.11 support
|
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
|
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
|
2007-05-06 10:07:21 +00:00
|
|
|
device wlan_amrr # AMRR transmit rate control algorithm
|
2004-01-29 21:24:53 +00:00
|
|
|
device an # Aironet 4500/4800 802.11 wireless NICs.
|
2006-05-03 18:13:11 +00:00
|
|
|
device ath # Atheros pci/cardbus NIC's
|
2008-12-01 16:53:01 +00:00
|
|
|
device ath_hal # pci/cardbus chip support
|
|
|
|
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
|
2006-05-03 18:13:11 +00:00
|
|
|
device ath_rate_sample # SampleRate tx rate control for ath
|
2005-05-24 16:48:07 +00:00
|
|
|
device ral # Ralink Technology RT2500 wireless NICs.
|
2008-12-01 16:53:01 +00:00
|
|
|
#device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
|
2000-11-07 21:20:52 +00:00
|
|
|
#device wl # Older non 802.11 Wavelan wireless NIC.
|
|
|
|
|
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
|
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
|
|
|
|
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"
|
2001-07-02 21:02:09 +00:00
|
|
|
device gif # IPv6 and IPv4 tunneling
|
2001-09-25 18:56:40 +00:00
|
|
|
device faith # IPv6-to-IPv4 relaying (translation)
|
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.
|
1999-08-07 01:42:08 +00:00
|
|
|
# Be aware of the administrative consequences of enabling this!
|
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
|
1998-11-26 23:13:13 +00:00
|
|
|
|
|
|
|
# USB support
|
2000-05-12 03:05:35 +00:00
|
|
|
device uhci # UHCI PCI->USB interface
|
|
|
|
device ohci # OHCI PCI->USB interface
|
2005-03-16 02:34:50 +00:00
|
|
|
device ehci # EHCI PCI->USB interface (USB 2.0)
|
2000-05-12 03:05:35 +00:00
|
|
|
device usb # USB Bus (required)
|
2000-05-01 22:48:23 +00:00
|
|
|
#device udbp # USB Double Bulk Pipe devices
|
2000-05-12 03:05:35 +00:00
|
|
|
device ugen # Generic
|
|
|
|
device uhid # "Human Interface Devices"
|
|
|
|
device ukbd # Keyboard
|
|
|
|
device ulpt # Printer
|
|
|
|
device umass # Disks/Mass storage - Requires scbus and da
|
|
|
|
device ums # Mouse
|
2005-05-24 16:48:07 +00:00
|
|
|
device ural # Ralink Technology RT2500USB wireless NICs
|
2007-05-06 10:07:21 +00:00
|
|
|
device rum # Ralink Technology RT2501USB wireless NICs
|
2007-10-26 02:20:29 +00:00
|
|
|
device zyd # ZyDAS zb1211/zb1211b wireless NICs
|
2000-05-12 03:05:35 +00:00
|
|
|
device urio # Diamond Rio 500 MP3 player
|
2000-10-25 10:34:38 +00:00
|
|
|
device uscanner # Scanners
|
2007-10-26 02:20:29 +00:00
|
|
|
# USB Serial devices
|
|
|
|
device ucom # Generic com ttys
|
2008-10-09 21:25:01 +00:00
|
|
|
device u3g # USB-based 3G modems (Option, Huawei, Sierra)
|
2007-10-26 02:20:29 +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
|
2008-03-05 14:13:30 +00:00
|
|
|
device uslcom # SI Labs CP2101/CP2102 serial adapters
|
2007-10-26 02:20:29 +00:00
|
|
|
device uvisor # Visor and Palm devices
|
|
|
|
device uvscom # USB serial support for DDI pocket's PHS
|
2004-12-30 15:30:23 +00:00
|
|
|
# USB Ethernet, requires miibus
|
2004-05-02 18:57:29 +00:00
|
|
|
device aue # ADMtek USB Ethernet
|
|
|
|
device axe # ASIX Electronics USB Ethernet
|
2005-03-22 14:52:40 +00:00
|
|
|
device cdce # Generic USB over Ethernet
|
2004-05-02 18:57:29 +00:00
|
|
|
device cue # CATC USB Ethernet
|
|
|
|
device kue # Kawasaki LSI USB Ethernet
|
|
|
|
device rue # RealTek RTL8150 USB Ethernet
|
2007-10-26 02:20:29 +00:00
|
|
|
device udav # Davicom DM9601E USB
|
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!)
|
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
|