Use a fast interrupt handler for the PCI version of the cy driver

[FreeBSD/FreeBSD.git] / sys / i386 / conf / LINT

#
# LINT -- config file for checking all the sources, tries to pull in
#       as much of the source tree as it can.
#
#       $Id: LINT,v 1.534 1999/01/13 09:55:19 yokota Exp $
#
# NB: You probably don't want to try running a kernel built from this
# file.  Instead, you should start from GENERIC, and add options from
# this file as required.
#

#
# This directive is mandatory; it defines the architecture to be
# configured for; in this case, the 386 family based IBM-PC and
# compatibles.
#
machine         "i386"

# 
# This is the ``identification'' of the kernel.  Usually this should
# be the same as the name of your kernel.
#
ident           LINT

#
# The `maxusers' parameter controls the static sizing of a number of
# internal system tables by a complicated formula defined in param.c.
#
maxusers        10

#
# Certain applications can grow to be larger than the 128M limit
# that FreeBSD initially imposes.  Below are some options to
# allow that limit to grow to 256MB, and can be increased further
# with changing the parameters.  MAXDSIZ is the maximum that the
# limit can be set to, and the DFLDSIZ is the default value for
# the limit.  You might want to set the default lower than the
# max, and explicitly set the maximum with a shell command for processes
# that regularly exceed the limit like INND.
#
options         "MAXDSIZ=(256*1024*1024)"
options         "DFLDSIZ=(256*1024*1024)"

# When this is set, be extra conservative in various parts of the kernel
# and choose functionality over speed (on the widest variety of systems).
options         FAILSAFE

# Options for the VM subsystem
#options        PQ_NOOPT                # No coloring
options         PQ_LARGECACHE           # color for 512k/16k cache
#options        PQ_HUGECACHE            # color for 1024k/16k cache

# This allows you to actually store this configuration file into
# the kernel binary itself, where it may be later read by saying:
#    strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL
#
options         INCLUDE_CONFIG_FILE     # Include this file in kernel

#
# This directive defines a number of things:
#  - The compiled kernel is to be called `kernel'
#  - The root filesystem might be on partition wd0a
#  - Crash dumps will be written to wd0b, if possible.  Specifying the
#    dump device here is not recommended.  Use dumpon(8).
#
config          kernel  root on wd0 dumps on wd0

\f
#####################################################################
# SMP OPTIONS:
#
# SMP enables building of a Symmetric MultiProcessor Kernel.
# APIC_IO enables the use of the IO APIC for Symmetric I/O.
# NCPU sets the number of CPUs, defaults to 2.
# NBUS sets the number of busses, defaults to 4.
# NAPIC sets the number of IO APICs on the motherboard, defaults to 1.
# NINTR sets the total number of INTs provided by the motherboard.
#
# Notes:
#
#  An SMP kernel will ONLY run on an Intel MP spec. qualified motherboard.
#
#  Be sure to disable 'cpu "I386_CPU"' && 'cpu "I486_CPU"' for SMP kernels.
#
#  Check the 'Rogue SMP hardware' section to see if additional options
#   are required by your hardware.
#

# Mandatory:
options         SMP                     # Symmetric MultiProcessor Kernel
options         APIC_IO                 # Symmetric (APIC) I/O

# Optional, these are the defaults plus 1:
options         NCPU=5                  # number of CPUs
options         NBUS=5                  # number of busses
options         NAPIC=2                 # number of IO APICs
options         NINTR=25                # number of INTs

#
# Rogue SMP hardware:
#

# Bridged PCI cards:
#
# The MP tables of most of the current generation MP motherboards
#  do NOT properly support bridged PCI cards.  To use one of these
#  cards you should refer to ???

\f
#####################################################################
# CPU OPTIONS

#
# You must specify at least one CPU (the one you intend to run on);
# deleting the specification for CPUs you don't need to use may make
# parts of the system run faster.  This is especially true removing
# I386_CPU.
#
cpu             "I386_CPU"
cpu             "I486_CPU"
cpu             "I586_CPU"              # aka Pentium(tm)
cpu             "I686_CPU"              # aka Pentium Pro(tm)

#
# Options for CPU features.
#
# CPU_BLUELIGHTNING_FPU_OP_CACHE enables FPU operand cache on IBM
# BlueLightning CPU.  It works only with Cyrix FPU, and this option
# should not be used with Intel FPU.
#
# CPU_BLUELIGHTNING_3X enables triple-clock mode on IBM Blue Lightning 
# CPU if CPU supports it. The default is double-clock mode on
# BlueLightning CPU box.  
#
# CPU_BTB_EN enables branch target buffer on Cyrix 5x86 (NOTE 1).
#
# CPU_DIRECT_MAPPED_CACHE sets L1 cache of Cyrix 486DLC CPU in direct
# mapped mode.  Default is 2-way set associative mode.
#
# CPU_CYRIX_NO_LOCK enables weak locking for the entire address space
# of Cyrix 6x86 and 6x86MX CPUs.  If this option is not set and
# FAILESAFE is defined, NO_LOCK bit of CCR1 is cleared.  (NOTE 3)
#
# CPU_DISABLE_5X86_LSSER disables load store serialize (i.e. enables
# reorder).  This option should not be used if you use memory mapped
# I/O device(s). 
#
# CPU_FASTER_5X86_FPU enables faster FPU exception handler.
#
# CPU_I486_ON_386 enables CPU cache on i486 based CPU upgrade products
# for i386 machines. 
#
# CPU_IORT defines I/O clock delay time (NOTE 1).  Default vaules of
# I/O clock delay time on Cyrix 5x86 and 6x86 are 0 and 7,respectively
# (no clock delay).
#
# CPU_LOOP_EN prevents flushing the prefetch buffer if the destination
# of a jump is already present in the prefetch buffer on Cyrix 5x86(NOTE
# 1). 
#
# CPU_RSTK_EN enables return stack on Cyrix 5x86 (NOTE 1).
#
# CPU_SUSP_HLT enables suspend on HALT.  If this option is set, CPU
# enters suspend mode following execution of HALT instruction.
#
# CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD
# K5/K6/K6-2 cpus.
#
# CYRIX_CACHE_WORKS enables CPU cache on Cyrix 486 CPUs with cache
# flush at hold state.
#
# CYRIX_CACHE_REALLY_WORKS enables (1) CPU cache on Cyrix 486 CPUs
# without cache flush at hold state, and (2) write-back CPU cache on
# Cyrix 6x86 whose revision < 2.7 (NOTE 2).
#
# NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY
# Pentiums) from locking up when a LOCK CMPXCHG8B instruction is
# executed.  This should be included for ALL kernels that won't run
# on a Pentium.
#
# NO_MEMORY_HOLE is an optimisation for systems with AMD K6 processors
# which indicates that the 15-16MB range is *definitely* not being 
# occupied by an ISA memory hole.
#
# NOTE 1: The options, CPU_BTB_EN, CPU_LOOP_EN, CPU_IORT,
# CPU_LOOP_ENand CPU_RSTK_EN should not be used becasue of CPU bugs.
# These options may crash your system. 
#
# NOTE 2: If CYRIX_CACHE_REALLY_WORKS is not set, CPU cache is enabled
# in write-through mode when revision < 2.7.  If revision of Cyrix
# 6x86 >= 2.7, CPU cache is always enabled in write-back mode.
#
# NOTE 3: This option may cause failures for software that requires
# locked cycles in order to operate correctly.
#
options         "CPU_BLUELIGHTNING_FPU_OP_CACHE"
options         "CPU_BLUELIGHTNING_3X"
options         "CPU_BTB_EN"
options         "CPU_DIRECT_MAPPED_CACHE"
options         "CPU_DISABLE_5X86_LSSER"
options         "CPU_FASTER_5X86_FPU"
options         "CPU_I486_ON_386"
options         "CPU_IORT"
options         "CPU_LOOP_EN"
options         "CPU_RSTK_EN"
options         "CPU_SUSP_HLT"
options         "CPU_WT_ALLOC"
options         "CYRIX_CACHE_WORKS"
options         "CYRIX_CACHE_REALLY_WORKS"
#options        "NO_F00F_HACK"

#
# A math emulator is mandatory if you wish to run on hardware which
# does not have a floating-point processor.  Pick either the original,
# bogus (but freely-distributable) math emulator, or a much more
# fully-featured but GPL-licensed emulator taken from Linux.
#
options         MATH_EMULATE            #Support for x87 emulation
# Don't enable both of these in a real config.
options         GPL_MATH_EMULATE        #Support for x87 emulation via
                                        #new math emulator 

\f
#####################################################################
# COMPATIBILITY OPTIONS                                             

#
# Implement system calls compatible with 4.3BSD and older versions of
# FreeBSD.  You probably do NOT want to remove this as much current code
# still relies on the 4.3 emulation.
#
options         "COMPAT_43"

#
# Allow user-mode programs to manipulate their local descriptor tables.
# This option is required for the WINE Windows(tm) emulator, and is
# not used by anything else (that we know of).
#
options         USER_LDT                #allow user-level control of i386 ldt

#
# These three options provide support for System V Interface
# Definition-style interprocess communication, in the form of shared
# memory, semaphores, and message queues, respectively.
#
options         SYSVSHM
options         SYSVSEM
options         SYSVMSG

#
# This option includes a MD5 routine in the kernel, this is used for
# various authentication and privacy uses.
#
options         "MD5"

#
# Allow processes to switch to vm86 mode, as well as enabling direct
# user-mode access to the I/O port space.  This option is necessary for 
# the doscmd emulator to run.
#
options         "VM86"

\f
#####################################################################
# DEBUGGING OPTIONS

#
# Enable the kernel debugger.
#
options         DDB

#
# Don't drop into DDB for a panic. Intended for unattended operation
# where you may want to drop to DDB from the console, but still want
# the machine to recover from a panic
#
options         DDB_UNATTENDED

#
# If using GDB remote mode to debug the kernel, there's a non-standard
# extension to the remote protocol that can be used to use the serial
# port as both the debugging port and the system console.  It's non-
# standard and you're on your own if you enable it.  See also the
# "remotechat" variables in the FreeBSD specific version of gdb.
#
options         GDB_REMOTE_CHAT

# 
# KTRACE enables the system-call tracing facility ktrace(2).
#
options         KTRACE                  #kernel tracing

#
# The INVARIANTS option is used in a number of source files to enable
# extra sanity checking of internal structures.  This support is not
# enabled by default because of the extra time it would take to check
# for these conditions, which can only occur as a result of
# programming errors.
#
options         INVARIANTS

#
# The INVARIANT_SUPPORT option makes us compile in support for
# verifying some of the internal structures.  It is a prerequisite for
# 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be
# called.  The intent is that you can set 'INVARIANTS' for single
# source files (by changing the source file or specifying it on the
# command line) if you have 'INVARIANT_SUPPORT' enabled.
#
options         INVARIANT_SUPPORT

#
# The DIAGNOSTIC option is used to enable extra debugging information
# from some parts of the kernel.  As this makes everything more noisy,
# it is disabled by default.
#
options         DIAGNOSTIC

#
# PERFMON causes the driver for Pentium/Pentium Pro performance counters
# to be compiled.  See perfmon(4) for more information.
#
options         PERFMON


#
# This option let some drivers co-exist that can't co-exist in a running
# system.  This is used to be able to compile all kernel code in one go for
# quality assurance purposes (like this file, which the option takes it name
# from.)
#
options COMPILING_LINT


# XXX - this doesn't belong here.
# Allow ordinary users to take the console - this is useful for X.
options         UCONSOLE

# XXX - this doesn't belong here either
options         USERCONFIG              #boot -c editor
options         INTRO_USERCONFIG        #imply -c and show intro screen
options         VISUAL_USERCONFIG       #visual boot -c editor
\f
#####################################################################
# NETWORKING OPTIONS

#
# Protocol families:
#  Only the INET (Internet) family is officially supported in FreeBSD.
#  Source code for the NS (Xerox Network Service) is provided for amusement
#  value.
#
options         INET                    #Internet communications protocols

options         IPX                     #IPX/SPX communications protocols
options         IPXIP                   #IPX in IP encapsulation (not available)
options         IPTUNNEL                #IP in IPX encapsulation (not available)

options         NETATALK                #Appletalk communications protocols

# These are currently broken but are shipped due to interest.
#options                NS                      #Xerox NS protocols

# These are currently broken and are no longer shipped due to lack
# of interest.
#options                CCITT                   #X.25 network layer
#options                ISO
#options                TPIP                    #ISO TP class 4 over IP
#options                TPCONS                  #ISO TP class 0 over X.25
#options                LLC                     #X.25 link layer for Ethernets
#options                HDLC                    #X.25 link layer for serial lines
#options                EON                     #ISO CLNP over IP
#options                NSIP                    #XNS over IP

#
# Network interfaces:
#  The `loop' pseudo-device is MANDATORY when networking is enabled.
#  The `ether' pseudo-device provides generic code to handle
#  Ethernets; it is MANDATORY when a Ethernet device driver is
#  configured.
#  The 'fddi' pseudo-device provides generic code to support FDDI.
#  The `sppp' pseudo-device serves a similar role for certain types
#  of synchronous PPP links (like `cx', `ar').
#  The `sl' pseudo-device implements the Serial Line IP (SLIP) service.
#  The `ppp' pseudo-device implements the Point-to-Point Protocol.
#  The `bpfilter' pseudo-device enables the Berkeley Packet Filter.  Be
#  aware of the legal and administrative consequences of enabling this
#  option.  The number of devices determines the maximum number of
#  simultaneous BPF clients programs runnable.
#  The `disc' pseudo-device implements a minimal network interface,
#  which throws away all packets sent and never receives any.  It is
#  included for testing purposes.
#  The `tun' pseudo-device implements the User Process PPP (iijppp)
#
# The PPP_BSDCOMP option enables support for compress(1) style entire
# packet compression, the PPP_DEFLATE is for zlib/gzip style compression.
# PPP_FILTER enables code for filtering the ppp data stream and selecting
# events for resetting the demand dial activity timer - requires bpfilter.
# See pppd(8) for more details.
#
pseudo-device   ether                   #Generic Ethernet
pseudo-device   fddi                    #Generic FDDI
pseudo-device   sppp                    #Generic Synchronous PPP
pseudo-device   loop                    #Network loopback device
pseudo-device   bpfilter 4              #Berkeley packet filter
pseudo-device   disc                    #Discard device
pseudo-device   tun     1               #Tunnel driver (user process ppp(8))
pseudo-device   sl      2               #Serial Line IP
pseudo-device   ppp     2               #Point-to-point protocol
options PPP_BSDCOMP                     #PPP BSD-compress support
options PPP_DEFLATE                     #PPP zlib/deflate/gzip support
options PPP_FILTER                      #enable bpf filtering (needs bpfilter)

#
# Internet family options:
#
# TCP_COMPAT_42 causes the TCP code to emulate certain bugs present in
# 4.2BSD.  This option should not be used unless you have a 4.2BSD
# machine and TCP connections fail.
#
# MROUTING enables the kernel multicast packet forwarder, which works
# with mrouted(8).
#
# IPFIREWALL enables support for IP firewall construction, in
# conjunction with the `ipfw' program.  IPFIREWALL_VERBOSE sends
# logged packets to the system logger.  IPFIREWALL_VERBOSE_LIMIT
# limits the number of times a matching entry can be logged.
#
# WARNING:  IPFIREWALL defaults to a policy of "deny ip from any to any"
# and if you do not add other rules during startup to allow access,
# YOU WILL LOCK YOURSELF OUT.  It is suggested that you set firewall=open
# in /etc/rc.conf when first enabling this feature, then refining the
# firewall rules in /etc/rc.firewall after you've tested that the new kernel
# feature works properly.
#
# IPFIREWALL_DEFAULT_TO_ACCEPT causes the default rule (at boot) to
# allow everything.  Use with care, if a cracker can crash your
# firewall machine, they can get to your protected machines.  However,
# if you are using it as an as-needed filter for specific problems as
# they arise, then this may be for you.  Changing the default to 'allow'
# means that you won't get stuck if the kernel and /sbin/ipfw binary get
# out of sync.
#
# IPDIVERT enables the divert IP sockets, used by ``ipfw divert''
#
# IPFILTER enables Darren Reed's ipfilter package.
# IPFILTER_LOG enables ipfilter's logging.
# IPFILTER_LKM enables LKM support for an ipfilter module (untested).
#
# TCPDEBUG is undocumented.
#
options         "TCP_COMPAT_42"         #emulate 4.2BSD TCP bugs
options         MROUTING                # Multicast routing
options         IPFIREWALL              #firewall
options         IPFIREWALL_VERBOSE      #print information about
                                        # dropped packets
options         IPFIREWALL_FORWARD      #enable xparent proxy support
options         "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity
options         IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
options         IPDIVERT                #divert sockets
options         IPFILTER                #kernel ipfilter support
options         IPFILTER_LOG            #ipfilter logging
#options        IPFILTER_LKM            #kernel support for ip_fil.o LKM
options         TCPDEBUG

# ICMP_BANDLIM enables icmp error response bandwidth limiting.   You
# typically want this option as it will help protect the machine from
# D.O.S. packet attacks.
#
options         "ICMP_BANDLIM"

# DUMMYNET enables the "dummynet" bandwidth limiter. You need
# IPFIREWALL as well. See the dummynet(4) manpage for more info.
# BRIDGE enables bridging between ethernet cards -- see bridge(4).
# You can use IPFIREWALL and dummynet together with bridging.
options DUMMYNET
options BRIDGE

#
# ATM (HARP version) options
#
# ATM_CORE includes the base ATM functionality code.  This must be included
#       for ATM support.
#
# ATM_IP includes support for running IP over ATM.
#
# At least one (and usually only one) of the following signalling managers 
# must be included (note that all signalling managers include PVC support):
# ATM_SIGPVC includes support for the PVC-only signalling manager `sigpvc'.
# ATM_SPANS includes support for the `spans' signalling manager, which runs
#       the FORE Systems's proprietary SPANS signalling protocol. 
# ATM_UNI includes support for the `uni30' and `uni31' signalling managers, 
#       which run the ATM Forum UNI 3.x signalling protocols.
#
# The `hea' driver provides support for the Efficient Networks, Inc.
# ENI-155p ATM PCI Adapter.
#
# The `hfa' driver provides support for the FORE Systems, Inc.
# PCA-200E ATM PCI Adapter.
#
options         ATM_CORE                #core ATM protocol family
options         ATM_IP                  #IP over ATM support
options         ATM_SIGPVC              #SIGPVC signalling manager
options         ATM_SPANS               #SPANS signalling manager
options         ATM_UNI                 #UNI signalling manager
device          hea0                    #Efficient ENI-155p ATM PCI
device          hfa0                    #FORE PCA-200E ATM PCI

\f
#####################################################################
# FILESYSTEM OPTIONS

#
# Only the root, /usr, and /tmp filesystems need be statically
# compiled; everything else will be automatically loaded at mount
# time.  (Exception: the UFS family---FFS, and MFS --- cannot
# currently be demand-loaded.)  Some people still prefer to statically
# compile other filesystems as well.
#
# NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be
# buggy, and WILL panic your system if you attempt to do anything with
# them.  They are included here as an incentive for some enterprising
# soul to sit down and fix them.
#

# One of these is mandatory:
options         FFS                     #Fast filesystem
options         MFS                     #Memory File System
options         NFS                     #Network File System

# The rest are optional:
# options       NFS_NOSERVER            #Disable the NFS-server code.
options         "CD9660"                #ISO 9660 filesystem
options         FDESC                   #File descriptor filesystem
options         KERNFS                  #Kernel filesystem
options         MSDOSFS                 #MS DOS File System
options         NULLFS                  #NULL filesystem
options         PORTAL                  #Portal filesystem
options         PROCFS                  #Process filesystem
options         UMAPFS                  #UID map filesystem
options         UNION                   #Union filesystem
# The xFS_ROOT options REQUIRE the associated ``options xFS''
options         "CD9660_ROOT"           #CD-ROM usable as root device
options         FFS_ROOT                #FFS usable as root device
options         MFS_ROOT                #MFS usable as root device
options         NFS_ROOT                #NFS usable as root device
# This code is still experimental (e.g. doesn't handle disk slices well).
# Also, 'options MFS' is currently incompatible with DEVFS.
options         DEVFS                   #devices filesystem

# Soft updates is technique for improving file system speed and
# making abrupt shutdown less risky.  It is not enabled by default due
# to copyright restraints on the code that implement it.
#
# Read .../../ufs/ffs/README.softupdates to learn what you need to
# do to enable this.  ../../../contrib/sys/softupdates/README gives
# more details on how they actually work.
#
#options                SOFTUPDATES

# Make space in the kernel for a MFS root filesystem.  Define to the number
# of kilobytes to reserve for the filesystem.
options         MFS_ROOT_SIZE=10
# Allows MFS filesystems to be exported via nfs
options         EXPORTMFS

# Allow this many swap-devices.
options         NSWAPDEV=20

# Disk quotas are supported when this option is enabled.  If you
# change the value of this option, you must do a `make clean' in your
# kernel compile directory in order to get a working kernel.
#
options         QUOTA                   #enable disk quotas

# Add more checking code to various filesystems
#options                NULLFS_DIAGNOSTIC
#options                KERNFS_DIAGNOSTIC
#options                UMAPFS_DIAGNOSTIC
#options                UNION_DIAGNOSTIC

# In particular multi-session CD-Rs might require a huge amount of
# time in order to "settle".  If we are about mounting them as the
# root f/s, we gotta wait a little.
#
# The number is supposed to be in seconds.
options         "CD9660_ROOTDELAY=20"

# If you are running a machine just as a fileserver for PC and MAC
# users, using SAMBA or Netatalk, you may consider setting this option
# and keeping all those users' directories on a filesystem that is
# mounted with the suiddir option. This gives new files the same
# ownership as the directory (similiar to group). It's a security hole
# if you let these users run programs, so confine it to file-servers
# (but it'll save you lots of headaches in those cases). Root owned
# directories are exempt and X bits are cleared. The suid bit must be
# set on the directory as well; see chmod(1) PC owners can't see/set
# ownerships so they keep getting their toes trodden on. This saves
# you all the support calls as the filesystem it's used on will act as
# they expect: "It's my dir so it must be my file".
#
options         SUIDDIR


# Add some error checking code to the null_bypass routine
# in the NULL filesystem
#options                SAFETY


# NFS options:
options         "NFS_MINATTRTIMO=3"     # VREG attrib cache timeout in sec
options         "NFS_MAXATTRTIMO=60"
options         "NFS_MINDIRATTRTIMO=30" # VDIR attrib cache timeout in sec
options         "NFS_MAXDIRATTRTIMO=60"
options         "NFS_GATHERDELAY=10"    # Default write gather delay (msec)
options         "NFS_UIDHASHSIZ=29"     # Tune the size of nfssvc_sock with this
options         "NFS_WDELAYHASHSIZ=16"  # and with this
options         "NFS_MUIDHASHSIZ=63"    # Tune the size of nfsmount with this
options         NFS_DEBUG               # Enable NFS Debugging

# Coda stuff:
options         CODA                    #CODA filesystem.
pseudo-device   vcoda   4               #coda minicache <-> venus comm.

\f
#####################################################################
# POSIX P1003.1B

# Real time extensions added int the 1993 Posix
# P1003_1B: Infrastructure
# _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING
# _KPOSIX_VERSION:             Version kernel is built for

options         "P1003_1B"
options         "_KPOSIX_PRIORITY_SCHEDULING"
options         "_KPOSIX_VERSION=199309L"

\f
#####################################################################
# SCSI DEVICES

# SCSI DEVICE CONFIGURATION

# The SCSI subsystem consists of the `base' SCSI code, a number of
# high-level SCSI device `type' drivers, and the low-level host-adapter
# device drivers.  The host adapters are listed in the ISA and PCI
# device configuration sections below.
#
# Beginning with FreeBSD 2.0.5 you can wire down your SCSI devices so
# that a given bus, target, and LUN always come on line as the same
# device unit.  In earlier versions the unit numbers were assigned
# in the order that the devices were probed on the SCSI bus.  This
# means that if you removed a disk drive, you may have had to rewrite
# your /etc/fstab file, and also that you had to be careful when adding
# a new disk as it may have been probed earlier and moved your device
# configuration around.

# This old behavior is maintained as the default behavior.  The unit
# assignment begins with the first non-wired down unit for a device
# type.  For example, if you wire a disk as "da3" then the first
# non-wired disk will be assigned da4.

# The syntax for wiring down devices is:

# controller    scbus0 at ahc0          # Single bus device
# controller    scbus1 at ahc1 bus 0    # Single bus device
# controller    scbus3 at ahc2 bus 0    # Twin bus device
# controller    scbus2 at ahc2 bus 1    # Twin bus device
# disk          da0 at scbus0 target 0 unit 0
# disk          da1 at scbus3 target 1
# disk          da2 at scbus2 target 3
# tape          st1 at scbus1 target 6
# device        cd0 at scbus?

# "units" (SCSI logical unit number) that are not specified are
# treated as if specified as LUN 0.

# All SCSI devices allocate as many units as are required.

# The "unknown" device (uk? in pre-2.0.5) is now part of the base SCSI
# configuration and doesn't have to be explicitly configured.

controller      scbus0  #base SCSI code
device          ch0     #SCSI media changers
device          da0     #SCSI direct access devices (aka disks)
device          sa0     #SCSI tapes
device          cd0     #SCSI CD-ROMs
#device         od0     #SCSI optical disk
device          pass0   #CAM passthrough driver

# The previous devices (ch, da, st, cd) are recognized by config.
# config doesn't (and shouldn't) know about these newer ones,
# so we have to specify that they are on a SCSI bus with the "at scbus?"
# clause.

device pt0 at scbus?    # SCSI processor type
device sctarg0 at scbus? # SCSI target

# CAM OPTIONS:
# debugging options:
# -- NOTE --  If you specify one of the bus/target/lun options, you must
#             specify them all!
# CAMDEBUG: When defined enables debugging macros
# CAM_DEBUG_BUS:  Debug the given bus.  Use -1 to debug all busses.
# CAM_DEBUG_TARGET:  Debug the given target.  Use -1 to debug all targets.
# CAM_DEBUG_LUN:  Debug the given lun.  Use -1 to debug all luns.
# CAM_DEBUG_FLAGS:  OR together CAM_DEBUG_INFO, CAM_DEBUG_TRACE,
#                   CAM_DEBUG_SUBTRACE, and CAM_DEBUG_CDB
# 
# CAM_MAX_HIGHPOWER: Maximum number of concurrent high power (start unit) cmds
# SCSI_NO_SENSE_STRINGS: When defined disables sense descriptions
# SCSI_NO_OP_STRINGS: When defined disables opcode descriptions
# SCSI_REPORT_GEOMETRY: Always report disk geometry at boot up instead
#                       of only when booting verbosely.
# SCSI_DELAY: The number of MILLISECONDS to freeze the SIM (scsi adapter)
#             queue after a bus reset, and the number of milliseconds to
#             freeze the device queue after a bus device reset.
options         CAMDEBUG
options         "CAM_DEBUG_BUS=-1"
options         "CAM_DEBUG_TARGET=-1"
options         "CAM_DEBUG_LUN=-1"
options         "CAM_DEBUG_FLAGS=CAM_DEBUG_INFO|CAM_DEBUG_TRACE|CAM_DEBUG_CDB"
options         "CAM_MAX_HIGHPOWER=4"
options         SCSI_NO_SENSE_STRINGS
options         SCSI_NO_OP_STRINGS
options         SCSI_REPORT_GEOMETRY
options         SCSI_DELAY=8000 # Be pessimistic about Joe SCSI device

# Options for the CAM CDROM driver:
# CHANGER_MIN_BUSY_SECONDS: Guaranteed minimum time quantum for a changer LUN
# CHANGER_MAX_BUSY_SECONDS: Maximum time quantum per changer LUN, only
#                           enforced if there is I/O waiting for another LUN
# The compiled in defaults for these variables are 2 and 10 seconds,
# respectively.
#
# These can also be changed on the fly with the following sysctl variables:
# kern.cam.cd.changer.min_busy_seconds
# kern.cam.cd.changer.max_busy_seconds
#
options         "CHANGER_MIN_BUSY_SECONDS=2"
options         "CHANGER_MAX_BUSY_SECONDS=10"

# Options for the CAM sequential access driver:
# SA_SPACE_TIMEOUT: Timeout for space operations, in minutes
# SA_REWIND_TIMEOUT: Timeout for rewind operations, in minutes
# SA_ERASE_TIMEOUT: Timeout for erase operations, in minutes
options         "SA_SPACE_TIMEOUT=(60)"
options         "SA_REWIND_TIMEOUT=(2*60)"
options         "SA_ERASE_TIMEOUT=(4*60)"

\f
#####################################################################
# MISCELLANEOUS DEVICES AND OPTIONS

# The `pty' device usually turns out to be ``effectively mandatory'',
# as it is required for `telnetd', `rlogind', `screen', `emacs', and
# `xterm', among others.

pseudo-device   pty     16      #Pseudo ttys - can go as high as 256
pseudo-device   speaker         #Play IBM BASIC-style noises out your speaker
pseudo-device   gzip            #Exec gzipped a.out's
pseudo-device   vn              #Vnode driver (turns a file into a device)
pseudo-device   snp     3       #Snoop device - to look at pty/vty/etc..
pseudo-device   ccd     4       #Concatenated disk driver
pseudo-device   vinum           #Vinum concat/mirror/raid driver
options         VINUMDEBUG      #enable Vinum debugging hooks

# These are only for watching for bitrot in old tty code.
# broken
#pseudo-device  tb

# Size of the kernel message buffer.  Should be N * pagesize.
options         "MSGBUF_SIZE=40960"

\f
#####################################################################
# HARDWARE DEVICE CONFIGURATION

# ISA and EISA devices:
# EISA support is available for some device, so they can be auto-probed.
# Micro Channel is not supported at all.

#
# Mandatory ISA devices: isa, npx
#
controller      isa0

#
# Options for `isa':
#
# AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A
# interrupt controller.  This saves about 0.7-1.25 usec for each interrupt.
# This option breaks suspend/resume on some portables.
#
# AUTO_EOI_2 enables the `automatic EOI' feature for the slave 8259A
# interrupt controller.  This saves about 0.7-1.25 usec for each interrupt.
# Automatic EOI is documented not to work for for the slave with the
# original i8259A, but it works for some clones and some integrated
# versions.
#
# MAXMEM specifies the amount of RAM on the machine; if this is not
# specified, FreeBSD will first read the amount of memory from the CMOS
# RAM, so the amount of memory will initially be limited to 64MB or 16MB
# depending on the BIOS.  If the BIOS reports 64MB, a memory probe will
# then attempt to detect the installed amount of RAM.  If this probe
# fails to detect >64MB RAM you will have to use the MAXMEM option.
# The amount is in kilobytes, so for a machine with 128MB of RAM, it would
# be 131072 (128 * 1024).
#
# TUNE_1542 enables the automatic ISA bus speed selection for the
# Adaptec 1542 boards. Does not work for all boards, use it with caution.
#
# BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to
# reset the CPU for reboot.  This is needed on some systems with broken
# keyboard controllers.
#
# PAS_JOYSTICK_ENABLE enables the gameport on the ProAudio Spectrum

options         "AUTO_EOI_1"
#options        "AUTO_EOI_2"
options         "MAXMEM=(128*1024)"
options         "TUNE_1542"
#options        BROKEN_KEYBOARD_RESET
#options        PAS_JOYSTICK_ENABLE

# Enable support for the kernel PLL to use an external PPS signal,
# under supervision of [x]ntpd(8)
# More info in ftp://ftp.udel.edu/pub/ntp/kernel.tar.Z

options         PPS_SYNC

# If you see the "calcru: negative time of %ld usec for pid %d (%s)\n"
# message you probably have some broken sw/hw which disables interrupts
# for too long.  You can make the system more resistant to this by
# choosing a high value for NTIMECOUNTER.  The default is 5, there
# is no upper limit but more than a couple of hundred are not productive.

options         "NTIMECOUNTER=20"

# Enable PnP support in the kernel.  This allows you to automaticly
# attach to PnP cards for drivers that support it and allows you to
# configure cards from USERCONFIG.  See pnp(4) for more info.
controller      pnp0

# The keyboard controller; it controlls the keyboard and the PS/2 mouse.
controller      atkbdc0 at isa? port IO_KBD tty

# The AT keyboard
device          atkbd0  at isa? tty irq 1

# `flags' for atkbd:
#       0x01    Force detection of keyboard, else we always assume a keyboard
#       0x02    Don't reset keyboard, useful for some newer ThinkPads
#       0x04    Old-style (XT) keyboard support, useful for older ThinkPads

# PS/2 mouse
device          psm0    at isa? tty irq 12

# Options for psm:
options         PSM_HOOKAPM             #hook the APM resume event, useful
                                        #for some laptops
options         PSM_RESETAFTERSUSPEND   #reset the device at the resume event

# The video card driver.
device          vga0    at isa? port ? conflicts

# Splash screen at start up!  Screen savers require this too.
pseudo-device   splash

# The pcvt console driver (vt220 compatible).
device          vt0     at isa? tty
options         XSERVER                 # support for running an X server.
options         FAT_CURSOR              # start with block cursor
# This PCVT option is for keyboards such as those used on IBM ThinkPad laptops
options         PCVT_SCANSET=2          # IBM keyboards are non-std

# The syscons console driver (sco color console compatible).
device          sc0     at isa? tty
options         MAXCONS=16              # number of virtual consoles
options         VGA_SLOW_IOACCESS       # do byte-wide i/o's to TS and GDC regs
options         "STD8X16FONT"           # Compile font in
makeoptions     "STD8X16FONT"="cp850"
options         SC_HISTORY_SIZE=200     # number of history buffer lines
options         SC_DISABLE_REBOOT       # disable reboot key sequence
# Try the following option if the mouse pointer is not drawn correctly 
# or font does not seem to be loaded properly.  May cause flicker on 
# some systems.
#options        SC_ALT_SEQACCESS

# To include support for VESA video modes
# Dont use together with SMP!!
options         VESA                    # needs VM86 defined too!!

#
# `flags' for sc0:
#       0x01    Use a 'visual' bell
#       0x02    Use a 'blink' cursor
#       0x04    Use a 'underline' cursor
#       0x06    Use a 'blinking underline' (destructive) cursor
#       0x40    Make the bell quiet if it is rung in the backgroud vty.

#
# The Numeric Processing eXtension driver.  This should be configured if
# your machine has a math co-processor, unless the coprocessor is very
# buggy. If it is not configured then you *must* configure math emulation
# (see above).  If both npx0 and emulation are configured, then only npx0
# is used (provided it works).
device          npx0    at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13

#
# `flags' for npx0:
#       0x01    don't use the npx registers to optimize bcopy
#       0x02    don't use the npx registers to optimize bzero
#       0x04    don't use the npx registers to optimize copyin or copyout.
# The npx registers are normally used to optimize copying and zeroing when
# all of the following conditions are satisfied:
#       "I586_CPU" is an option
#       the cpu is an i586 (perhaps not a Pentium)
#       the probe for npx0 succeeds
#       INT 16 exception handling works.
# Then copying and zeroing using the npx registers is normally 30-100% faster.
# The flags can be used to control cases where it doesn't work or is slower.
# Setting them at boot time using userconfig works right (the optimizations
# are not used until later in the bootstrap when npx0 is attached).
#

#
# `iosiz' for npx0:
# This can be used instead of the MAXMEM option to set the memory size.  If
# it is nonzero, then it overrides both the MAXMEM option and the memory
# size reported by the BIOS.  Setting it at boot time using userconfig takes
# effect on the next reboot after the change has been recorded in the kernel
# binary (the size is used early in the boot before userconfig has a chance
# to change it).
#

#
# Optional ISA and EISA devices:
#

#
# SCSI host adapters: `aha', `aic', `bt'
#
# adv: All Narrow SCSI bus AdvanSys controllers.
# adw: Second Generation AdvanSys controllers including the ADV940UW.
# aha: Adaptec 154x
# ahc: Adaptec 274x/284x/294x
# aic: Adaptec 152x and sound cards using the Adaptec AIC-6360 (slow!)
# bt: Most Buslogic controllers
#
# Note that the order is important in order for Buslogic cards to be
# probed correctly.
#

controller      bt0     at isa? port "IO_BT0" cam irq ?
controller      adv0    at isa? port ? cam irq ?
controller      adw0
controller      aha0    at isa? port ? cam irq ?

#!CAM# controller      aic0    at isa? port 0x340 bio irq 11


#
# ST-506, ESDI, and IDE hard disks: `wdc' and `wd'
#
# The flags fields are used to enable the multi-sector I/O and
# the 32BIT I/O modes.  The flags may be used in either the controller
# definition or in the individual disk definitions.  The controller
# definition is supported for the boot configuration stuff.
#
# Each drive has a 16 bit flags value defined:
#       The low 8 bits are the maximum value for the multi-sector I/O,
#       where 0xff defaults to the maximum that the drive can handle.
#       The high bit of the 16 bit flags (0x8000) allows probing for
#       32 bit transfers.  Bit 14 (0x4000) enables a hack to wake
#       up powered-down laptop drives.  Bit 13 (0x2000) allows
#       probing for PCI IDE DMA controllers, such as Intel's PIIX
#       south bridges. Bit 12 (0x1000) sets LBA mode instead of the
#       default CHS mode for accessing the drive. See the wd.4 man page.
#
# The flags field for the drives can be specified in the controller
# specification with the low 16 bits for drive 0, and the high 16 bits
# for drive 1.
# e.g.:
#controller     wdc0    at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004
#
# specifies that drive 0 will be allowed to probe for 32 bit transfers and
# a maximum multi-sector transfer of 4 sectors, and drive 1 will not be
# allowed to probe for 32 bit transfers, but will allow multi-sector
# transfers up to the maximum that the drive supports.
#
# If you are using a PCI controller that is not running in compatibility
# mode (for example, it is a 2nd IDE PCI interface), then use config line(s)
# such as:
#
#controller     wdc2    at isa? port "0" bio irq ? flags 0xa0ffa0ff
#disk           wd4     at wdc2 drive 0
#disk           wd5     at wdc2 drive 1
#
#controller     wdc3    at isa? port "0" bio irq ? flags 0xa0ffa0ff
#disk           wd6     at wdc3 drive 0
#disk           wd7     at wdc3 drive 1
#
# Note that the above config would be useful for a Promise card, when used
# on a MB that already has a PIIX controller.  Note the bogus irq and port
# entries.  These are automatically filled in by the IDE/PCI support.
#

controller      wdc0    at isa? port "IO_WD1" bio irq 14
disk            wd0     at wdc0 drive 0
disk            wd1     at wdc0 drive 1
controller      wdc1    at isa? port "IO_WD2" bio irq 15
disk            wd2     at wdc1 drive 0
disk            wd3     at wdc1 drive 1

#
# Options for `wdc':
#
# CMD640 enables serializing access to primary and secondary channel
# of the CMD640B IDE Chip. The serializing will only take place
# if this option is set *and* the chip is probed by the pci-system.
#
options         "CMD640"        #Enable work around for CMD640 h/w bug
#
# ATAPI enables the support for ATAPI-compatible IDE devices
#
options         ATAPI   #Enable ATAPI support for IDE bus
options         ATAPI_STATIC    #Don't do it as an LKM

#
# This option allow you to override the default probe time for IDE
# devices, to get a faster probe.  Setting this below 10000 violate
# the IDE specs, but may still work for you (it will work for most
# people).
#
options         IDE_DELAY=8000  # Be optimistic about Joe IDE device

# IDE CD-ROM & CD-R/RW  driver - requires wdc controller and ATAPI option
device          acd0

# IDE floppy driver - requires wdc controller and ATAPI option
device          wfd0

# IDE tape driver - requires wdc controller and ATAPI option
device          wst0


#
# Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft'
#
controller      fdc0    at isa? port "IO_FD1" bio irq 6 drq 2
#
# FDC_DEBUG enables floppy debugging.  Since the debug output is huge, you
# gotta turn it actually on by setting the variable fd_debug with DDB,
# however.
options         FDC_DEBUG
# FDC_YE enables support for the floppies used on the Libretto.  This is a
# pcmcia floppy.  You will also need to add
#card "Y-E DATA" "External FDD"
#        config 0x4 "fdc0" 10
# to your pccard.conf file.
options         FDC_YE
# This option is undocumented on purpose.
options         FDC_PRINT_BOGUS_CHIPTYPE
#
# Activate this line instead of the fdc0 line above if you happen to
# have an Insight floppy tape.  Probing them proved to be dangerous
# for people with floppy disks only, so it's "hidden" behind a flag:
#controller fdc0 at isa? port "IO_FD1" bio flags 1 irq 6 drq 2

disk            fd0     at fdc0 drive 0
disk            fd1     at fdc0 drive 1

#
# Other standard PC hardware: `lpt', `mse', `sio', etc.
#
# lpt: printer port
#       lpt specials:
#               The port may be specified as ?.  This will cause the
#               driver to scan the BIOS port list.
#               The irq clause may be omitted.  This will force the port
#               into polling mode.
# mse: Logitech and ATI InPort bus mouse ports
# sio: serial ports (see sio(4))

device          lpt0    at isa? port? tty irq 7
device          lpt1    at isa? port "IO_LPT3" tty irq 5
device          mse0    at isa? port 0x23c tty irq 5

device          sio0    at isa? port "IO_COM1" tty flags 0x10 irq 4

#
# `flags' for serial drivers that support consoles (only for sio now):
#       0x10    enable console support for this unit.  The other console flags
#               are ignored unless this is set.  Enabling console support does
#               not make the unit the preferred console - boot with -h or set
#               the 0x20 flag for that.  Currently, at most one unit can have
#               console support; the first one (in config file order) with
#               this flag set is preferred.  Setting this flag for sio0 gives
#               the old behaviour.
#       0x20    force this unit to be the console (unless there is another
#               higher priority console).  This replaces the COMCONSOLE option.
#       0x40    reserve this unit for low level console operations.  Do not
#               access the device in any normal way.
#
# PnP `flags' (set via userconfig using pnp x flags y)
#       0x1     disable probing of this device.  Used to prevent your modem
#               from being attached as a PnP modem.
#

# Options for serial drivers that support consoles (only for sio now):
options         BREAK_TO_DEBUGGER       #a BREAK on a comconsole goes to 
                                        #DDB, if available.
options         CONSPEED=9600           #default speed for serial console (default 9600)

# Options for sio:
options         COM_ESP                 #code for Hayes ESP
options         COM_MULTIPORT           #code for some cards with shared IRQs
options         "EXTRA_SIO=2"           #number of extra sio ports to allocate

# Other flags for sio that aren't documented in the man page.
#       0x20000 enable hardware RTS/CTS and larger FIFOs.  Only works for
#               ST16650A-compatible UARTs.

#
# Network interfaces: `cx', `ed', `el', `ep', `ie', `is', `le', `lnc'
#
# ar: Arnet SYNC/570i hdlc sync 2/4 port V.35/X.21 serial driver (requires sppp)
# cs: IBM Etherjet and other Crystal Semi CS89x0-based adapters
# cx: Cronyx/Sigma multiport sync/async (with Cisco or PPP framing)
# ed: Western Digital and SMC 80xx; Novell NE1000 and NE2000; 3Com 3C503
# el: 3Com 3C501 (slow!)
# ep: 3Com 3C509 (buggy)
# ex: Intel EtherExpress Pro/10 and other i82595-based adapters
# fe: Fujitsu MB86960A/MB86965A Ethernet
# ie: AT&T StarLAN 10 and EN100; 3Com 3C507; unknown NI5210; Intel EtherExpress
# le: Digital Equipment EtherWorks 2 and EtherWorks 3 (DEPCA, DE100,
#     DE101, DE200, DE201, DE202, DE203, DE204, DE205, DE422)
# lnc: Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL, AMD Am7990 & Am79C960)
# rdp: RealTek RTL 8002-based pocket ethernet adapters
# sr: RISCom/N2 hdlc sync 1/2 port V.35/X.21 serial driver (requires sppp)
# wl: Lucent Wavelan (ISA card only).
# ze: IBM/National Semiconductor PCMCIA ethernet controller.
# zp: 3Com PCMCIA Etherlink III (It does not require shared memory for
#     send/receive operation, but it needs 'iomem' to read/write the
#     attribute memory)
#

device ar0 at isa? port 0x300 net irq 10 iomem 0xd0000
device cs0 at isa? port 0x300 net irq ?
device cx0 at isa? port 0x240 net irq 15 drq 7
device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000
device el0 at isa? port 0x300 net irq 9
device ep0 at isa? port 0x300 net irq 10
device ex0 at isa? port? net irq?
device fe0 at isa? port 0x300 net irq ?
device ie0 at isa? port 0x300 net irq 5 iomem 0xd0000
device ie1 at isa? port 0x360 net irq 7 iomem 0xd0000
device le0 at isa? port 0x300 net irq 5 iomem 0xd0000
device lnc0 at isa? port 0x280 net irq 10 drq 0
device rdp0 at isa? port 0x378 net irq 7 flags 2
device sr0 at isa? port 0x300 net irq 5 iomem 0xd0000
options         WLCACHE         # enables the signal-strength cache
options         WLDEBUG         # enables verbose debugging output
device wl0 at isa? port 0x300 net irq ?
# We can (bogusly) include both the dedicated PCCARD drivers and the generic
# support when COMPILING_LINT.
device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000
device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000

#
# ATM related options
#
# The `en' device provides support for Efficient Networks (ENI)
# ENI-155 PCI midway cards, and the Adaptec 155Mbps PCI ATM cards (ANA-59x0).
#
# atm pseudo-device provides generic atm functions and is required for
# atm devices.
# NATM enables the netnatm protocol family that can be used to
# bypass TCP/IP.
#
# the current driver supports only PVC operations (no atm-arp, no multicast).
# for more details, please read the original documents at 
# http://www.ccrc.wustl.edu/pub/chuck/bsdatm/wucs.html
#
pseudo-device   atm
device en0
device en1
options         NATM                    #native ATM

#
# Audio drivers: `snd', `sb', `pas', `gus', `pca'
#
# snd: Voxware sound support code
# sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum
# sbxvi: SoundBlaster 16
# sbmidi: SoundBlaster 16 MIDI interface
# pas: ProAudioSpectrum PCM and MIDI
# gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX
# gusxvi: Gravis Ultrasound 16-bit PCM  (do not use)
# mss: Microsoft Sound System
# css: Crystal Sound System (CSS 423x PnP)
# sscape: Ensoniq Soundscape MIDI interface
# sscape_mss: Ensoniq Soundscape PCM (requires sscape)
# opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum
# uart: stand-alone 6850 UART for MIDI
# mpu: Roland MPU-401 stand-alone card
# 
# Beware!  The addresses specified below are also hard-coded in
# i386/isa/sound/sound_config.h.  If you change the values here, you
# must also change the values in the include file.
#
# pcm: PCM audio through various sound cards.
#
# This has support for a large number of new audio cards, based on
# CS423x, OPTi931, Yamaha OPL-SAx, and also for SB16, GusPnP.
# For more information about this driver and supported cards,
# see the  pcm.4 man page  and /sys/i386/isa/snd/CARDS.
#
# The flags of the device tells the device a bit more info about the
# device that normally is obtained through the PnP interface.
#       bit  2..0   secondary DMA channel;
#       bit  4      set if the board uses two dma channels;
#       bit 15..8   board type, overrides autodetection; leave it
#                   zero if don't know what to put in (and you don't,
#                   since this is unsupported at the moment...).
#
# This driver will use the new PnP code if it's available.
#
# pca: PCM audio through your PC speaker
#
# If you have a GUS-MAX card and want to use the CS4231 codec on the
# card the drqs for the gus max must be 8 bit (1, 2, or 3).
# 
# If you would like to use the full duplex option on the gus, then define
# flags to be the ``read dma channel''.
#
# options BROKEN_BUS_CLOCK      #PAS-16 isn't working and OPTI chipset
# options SYMPHONY_PAS          #PAS-16 isn't working and SYMPHONY chipset
# options EXCLUDE_SBPRO         #PAS-16
# options SBC_IRQ=5             #PAS-16. Must match irq on sb0 line.
# PAS16: The order of the pas0/sb0/opl0 is important since the
#       sb emulation is enabled in the pas-16 attach.
#
# To overide the GUS defaults use:
# options GUS_DMA2
# options GUS_DMA
# options GUS_IRQ
#
# The i386/isa/sound/sound.doc has more information.

# Controls all "VOXWARE" driver sound devices.  See Luigi's driver
# below for an alternate which may work better for some cards.
#
controller      snd0
device pas0     at isa? port 0x388 irq 10 drq 6
device sb0      at isa? port 0x220 irq 5 drq 1
device sbxvi0   at isa? drq 5
device sbmidi0  at isa? port 0x330
device awe0     at isa? port 0x620
device gus0 at isa? port 0x220 irq 12 drq 1
#device gus0 at isa? port 0x220 irq 12 drq 1 flags 0x3
device mss0 at isa? port 0x530 irq 10 drq 1
device css0     at isa? port 0x534 irq 5 drq 1 flags 0x08
device sscape0  at isa? port 0x330 irq 9 drq 0
device trix0    at isa? port 0x330 irq 6 drq 0
device sscape_mss0  at isa? port 0x534 irq 5 drq 1
device opl0     at isa? port 0x388
device mpu0     at isa? port 0x330 irq 6 drq 0
device uart0 at isa? port 0x330 irq 5

# Luigi's snd code (use INSTEAD of snd0 and all VOXWARE drivers!).
# You may also wish to enable the pnp controller with this, for pnp
# sound cards.
#
#device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0

# Not controlled by `snd'
device pca0 at isa? port "IO_TIMER1" tty

#
# Miscellaneous hardware:
#
# mcd: Mitsumi CD-ROM
# scd: Sony CD-ROM
# matcd: Matsushita/Panasonic CD-ROM
# wt: Wangtek and Archive QIC-02/QIC-36 tape drives
# ctx: Cortex-I frame grabber
# apm: Laptop Advanced Power Management (experimental)
# spigot: The Creative Labs Video Spigot video-acquisition board
# meteor: Matrox Meteor video capture board
# bktr: Brooktree bt848/848a/849/878/879 family video capture and TV Tuner board
# alog: Industrial Computer Source AIO8-P driver
# cy: Cyclades serial driver
# dgb: Digiboard PC/Xi and PC/Xe series driver (ALPHA QUALITY!)
# dgm: Digiboard PC/Xem driver
# gp:  National Instruments AT-GPIB and AT-GPIB/TNT board
# asc: GI1904-based hand scanners, e.g. the Trust Amiscan Grey
# gsc: Genius GS-4500 hand scanner.
# joy: joystick
# labpc: National Instrument's Lab-PC and Lab-PC+
# rc: RISCom/8 multiport card
# rp: Comtrol Rocketport(ISA) - single card
# tw: TW-523 power line interface for use with X-10 home control products
# si: Specialix SI/XIO 4-32 port terminal multiplexor
# stl: Stallion EasyIO and EasyConnection 8/32 (cd1400 based)
# stli: Stallion EasyConnection 8/64, ONboard, Brumby (intelligent)

#
# Notes on APM
#  The flags takes the following meaning for apm0:
#    0x0020  Statclock is broken.
#    0x0011  Limit APM protocol to 1.1 or 1.0
#    0x0010  Limit APM protocol to 1.0
#
#
# Notes on the spigot:
#  The video spigot is at 0xad6.  This port address can not be changed.
#  The irq values may only be 10, 11, or 15
#  I/O memory is an 8kb region.  Possible values are:
#    0a0000, 0a2000, ..., 0fffff, f00000, f02000, ..., ffffff
#    The start address must be on an even boundary.
#  Add the following option if you want to allow non-root users to be able
#  to access the spigot.  This option is not secure because it allows users
#  direct access to the I/O page. 
#       options SPIGOT_UNSECURE
#

# Notes on the Comtrol Rocketport driver:
#
# The exact values used for rp0 depend on how many boards you have
# in the system.  The manufacturer's sample configs are listed as:
#
#   Comtrol Rocketport ISA single card
#               device  rp0     at isa? port 0x280 tty
#
#   If instead you have two ISA cards, one installed at 0x100 and the
#   second installed at 0x180, then you should add the following to
#   your kernel configuration file:
#
#               device  rp0     at isa? port 0x100 tty
#               device  rp1     at isa? port 0x180 tty
#
#   For 4 ISA cards, it might be something like this:
#
#               device  rp0     at isa? port 0x180 tty
#               device  rp1     at isa? port 0x100 tty
#               device  rp2     at isa? port 0x340 tty
#               device  rp3     at isa? port 0x240 tty
#
#   And for PCI cards, you only need say:
#
#               device rp0
#               device rp1
#               ...
#   Note: Make sure that any Rocketport PCI devices are specified BEFORE the
#   ISA Rocketport devices.

# Notes on the Digiboard driver:
#
# The following flag values have special meanings:
#       0x01 - alternate layout of pins (dgb & dgm)
#       0x02 - use the windowed PC/Xe in 64K mode (dgb only)

# Notes on the Specialix SI/XIO driver:
#  **This is NOT a Specialix supported Driver!**
#  The host card is memory, not IO mapped.
#  The Rev 1 host cards use a 64K chunk, on a 32K boundary.
#  The Rev 2 host cards use a 32K chunk, on a 32K boundary.
#  The cards can use an IRQ of 11, 12 or 15.

# Notes on the Stallion stl and stli drivers:
#  See src/i386/isa/README.stl for complete instructions.
#  This is version 0.0.5alpha, unsupported by Stallion.
#  The stl driver has a secondary IO port hard coded at 0x280.  You need
#     to change src/i386/isa/stallion.c if you reconfigure this on the boards.
#  The "flags" and "iosiz" settings on the stli driver depend on the board:
#       EasyConnection 8/64 ISA:     flags 23         iosiz 0x1000
#       EasyConnection 8/64 EISA:    flags 24         iosiz 0x10000
#       EasyConnection 8/64 MCA:     flags 25         iosiz 0x1000
#       ONboard ISA:                 flags 4          iosiz 0x10000
#       ONboard EISA:                flags 7          iosiz 0x10000
#       ONboard MCA:                 flags 3          iosiz 0x10000
#       Brumby:                      flags 2          iosiz 0x4000
#       Stallion:                    flags 1          iosiz 0x10000

device          mcd0    at isa? port 0x300 bio irq 10
# for the Sony CDU31/33A CDROM
device          scd0    at isa? port 0x230 bio
# for the SoundBlaster 16 multicd - up to 4 devices
controller      matcd0  at isa? port 0x230 bio
device          wt0     at isa? port 0x300 bio irq 5 drq 1
device          ctx0    at isa? port 0x230 iomem 0xd0000
device          spigot0 at isa? port 0xad6 irq 15 iomem 0xee000
device          apm0    at isa? 
device          gp0     at isa? port 0x2c0 tty
device          gsc0    at isa? port "IO_GSC1" tty drq 3
device          joy0    at isa? port IO_GAME
device          alog0   at isa? port 0x260 tty irq 5
device          cy0     at isa? tty irq 10 iomem 0xd4000 iosiz 0x2000
options         CY_PCI_FASTINTR         # Use with cy_pci unless irq is shared
device          dgb0    at isa? port 0x220 iomem 0xfc0000 iosiz ? tty
device          dgm0    at isa? port 0x104 iomem 0xd00000 iosiz ? tty
device          labpc0  at isa? port 0x260 tty irq 5
device          rc0     at isa? port 0x220 tty irq 12
device          rp0     at isa? port 0x280 tty
# the port and irq for tw0 are fictitious
device          tw0     at isa? port 0x380 tty irq 11
device          si0     at isa? iomem 0xd0000 tty irq 12
device          asc0    at isa? port "IO_ASC1" tty drq 3 irq 10
device          stl0    at isa? port 0x2a0 tty irq 10
device          stli0   at isa? port 0x2a0 tty iomem 0xcc000 flags 23 iosiz 0x1000
# You are unlikely to have the hardware for loran0 <phk@FreeBSD.org>
device          loran0  at isa? port ? tty irq 5
# HOT1 Xilinx 6200 card (www.vcc.com)
device          xrpu0

#
# EISA devices:
#
# The EISA bus device is eisa0.  It provides auto-detection and
# configuration support for all devices on the EISA bus.
#
# The `ahb' device provides support for the Adaptec 174X adapter.
#
# The `ahc' device provides support for the Adaptec 274X and 284X
# adapters.  The 284X, although a VLB card responds to EISA probes.
#
# fea: DEC DEFEA EISA FDDI adapter
#
controller      eisa0
controller      ahb0
controller      ahc0
device          fea0

# The aic7xxx driver will attempt to use memory mapped I/O for all PCI
# controllers that have it configured only if this option is set. Unfortunately,
# this doesn't work on some motherboards, which prevents it from being the
# default.
options AHC_ALLOW_MEMIO

# By default, only 10 EISA slots are probed, since the slot numbers
# above clash with the configuration address space of the PCI subsystem,
# and the EISA probe is not very smart about this.  This is sufficient
# for most machines, but in particular the HP NetServer LC series comes
# with an onboard AIC7770 dual-channel SCSI controller on EISA slot #11,
# thus you need to bump this figure to 12 for them.
options "EISA_SLOTS=12"

#
# PCI devices & PCI options:
#
# The main PCI bus device is `pci'.  It provides auto-detection and
# configuration support for all devices on the PCI bus, using either
# configuration mode defined in the PCI specification.
#
# The `ahc' device provides support for the Adaptec 29/3940(U)(W)
# and motherboard based AIC7870/AIC7880 adapters.
#
# The `ncr' device provides support for the NCR 53C810 and 53C825
# self-contained SCSI host adapters.
#
# The `isp' device provides support for the Qlogic ISP 1020, 1040
# nd 1040B PCI SCSI host adapters, as well as the Qlogic ISP 2100
# FC/AL Host Adapter.
#
# The `ax' device provides support for PCI fast ethernet adapters
# based on the ASIX Electronics AX88140A chip, including the Alfa
# Inc. GFC2204.
#
# The `de' device provides support for the Digital Equipment DC21040
# self-contained Ethernet adapter.
#
# The `fxp' device provides support for the Intel EtherExpress Pro/100B
# PCI Fast Ethernet adapters.
#
# The `mx' device provides support for various fast ethernet adapters
# based on the Macronix 98713, 987615 ans 98725 series chips.
#
# The `pn' device provides support for various fast ethernet adapters
# based on the Lite-On 82c168 and 82c169 PNIC chips, including the
# LinkSys LNE100TX, the NetGear FA310TX rev. D1 and the Matrox
# FastNIC 10/100.
#
# The 'rl' device provides support for PCI fast ethernet adapters based
# on the RealTek 8129/8139 chipset. Note that the RealTek driver defaults
# to useing programmed I/O to do register accesses because memory mapped
# mode seems to cause severe lockups on SMP hardware. This driver also
# supports the Accton EN1207D `Cheetah' adapter, which uses a chip called
# the MPX 5030/5038, which is either a RealTek in disguise or a RealTek
# workalike.
#
# The 'tl' device provides support for the Texas Instruments TNETE100
# series 'ThunderLAN' cards and integrated ethernet controllers. This
# includes several Compaq Netelligent 10/100 cards and the built-in
# ethernet controllers in several Compaq Prosignia, Proliant and
# Deskpro systems. It also supports several Olicom 10Mbps and 10/100
# boards.
#
# The `tx' device provides support for the SMC 9432TX cards.
#
# The `vr' device provides support for various fast ethernet adapters
# based on the VIA Technologies VT3043 `Rhine I' and VT86C100A `Rhine II'
# chips, including the D-Link DFE530TX.
#
# The `vx' device provides support for the 3Com 3C590 and 3C595
# early support
#
# The `wb' device provides support for various fast ethernet adapters
# based on the Winbond W89C840F chip. Note: this is not the same as
# the Winbond W89C940F, which is an NE2000 clone.
#
# The `xl' device provides support for the 3Com 3c900, 3c905 and
# 3c905B (Fast) Etherlink XL cards and integrated controllers. This
# includes the integrated 3c905B-TX chips in certain Dell Optiplex and
# Dell Precision desktop machines and the integrated 3c905-TX chips
# in Dell Latitude laptop docking stations.
#
# The `fpa' device provides support for the Digital DEFPA PCI FDDI
# adapter. pseudo-device fddi is also needed.
#
# The `meteor' device is a PCI video capture board. It can also have the
# following options:
#   options METEOR_ALLOC_PAGES=xxx      preallocate kernel pages for data entry
#       figure (ROWS*COLUMN*BYTES_PER_PIXEL*FRAME+PAGE_SIZE-1)/PAGE_SIZE
#   options METEOR_DEALLOC_PAGES        remove all allocated pages on close(2)
#   options METEOR_DEALLOC_ABOVE=xxx    remove all allocated pages above the
#       specified amount. If this value is below the allocated amount no action
#       taken
#   option METEOR_SYSTEM_DEFAULT={METEOR_PAL|METEOR_NTSC|METEOR_SECAM}, used
#       for initialization of fps routine when a signal is not present.
#
# The 'bktr' device is a PCI video capture device using the Brooktree 
# bt848/bt848a/bt849/bt878/bt879 chipset. When used with a TV Tuner it forms a
# TV card, eg Miro PC/TV,Hauppauge WinCast/TV WinTV, VideoLogic Captivator,
# Intel Smart Video III, AverMedia, IMS Turbo. 
# The following options can be used to override the auto detection
#   options OVERRIDE_CARD=xxx
#   options OVERRIDE_TUNER=xxx
#   options OVERRIDE_MSP=1
#   options OVERRIDE_DBX=1
# The current values are found in /usr/src/sys/pci/brooktree848.c
#
#   option BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL
# This is required for Dual Crystal (28&35Mhz) boards where PAL is used
# to prevent hangs during initialisation.  eg VideoLogic Captivator PCI.
#
# PAL or SECAM users who have a 28Mhz crystal (and no 35Mhz crystal)
# must enable PLL mode with this option. eg some new Hauppauge cards.
#   option BKTR_USE_PLL
#
# Using sysctl(8) run-time overrides on a per-card basis can be made
#
controller      pci0
controller      ahc1
controller      ncr0
controller      isp0
device          ax0
device          de0
device          fxp0
device          mx0
device          pn0
device          rl0
device          tl0
device          tx0
device          vr0
device          vx0
device          wb0
device          xl0
device          fpa0
device          meteor0

# Brooktree driver has been ported to the new I2C framework. Thus,
# you'll need at least iicbus, iicbb and smbus. iic/smb are only needed if you
# want to control other I2C slaves connected to the external connector of
# some cards.
#
device          bktr0

#
# PCI options
#
#options        PCI_QUIET       #quiets PCI code on chipset settings

#
# PCCARD/PCMCIA
#
# card: slot controller
# pcic: slots
controller      card0
device          pcic0 at card?
device          pcic1 at card?

# You may need to reset all pccards after resuming
options         PCIC_RESUME_RESET       # reset after resume

#
# Laptop/Notebook options:
#
# See also:
#  apm under `Miscellaneous hardware'
# above.

# For older notebooks that signal a powerfail condition (external
# power supply dropped, or battery state low) by issuing an NMI:

options         POWERFAIL_NMI   # make it beep instead of panicing

#
# SMB bus
#
# System Management Bus support provided by the 'smbus' device.
#
# Supported devices:
# smb   standard io
#
# Supported interfaces:
# iicsmb I2C to SMB bridge with any iicbus interface
# bktr  brooktree848 I2C hardware interface
#
controller smbus0

device smb0     at smbus?

#
# I2C Bus
#
# Philips i2c bus support is provided by the `iicbus' device.
#
# Supported devices:
# ic    i2c network interface
# iic   i2c standard io
# iicsmb i2c to smb bridge. Allow i2c i/o with smb commands.
#
# Supported interfaces:
# pcf   Philips PCF8584 ISA-bus controller
# bktr  brooktree848 I2C software interface
#
# Other:
# iicbb generic I2C bit-banging code (needed by lpbb, bktr)
#
controller iicbus0
controller iicbb0

device ic0      at iicbus?
device iic0     at iicbus?
device iicsmb0  at iicbus?

controller pcf0 at isa? port 0x320 net irq 5

# ISDN4BSD section

# i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver)
# note that the ``options'' and ``device'' lines must BOTH be defined !
#
# Non-PnP Cards:
# --------------
#
# Teles S0/8 or Niccy 1008
options "TEL_S0_8"
#device isic0 at isa? iomem 0xd0000 net irq 5 flags 1
#
# Teles S0/16 or Creatix ISDN-S0 or Niccy 1016
options "TEL_S0_16"
#device isic0 at isa? port 0xd80 iomem 0xd0000 net irq 5 flags 2
#
# Teles S0/16.3 
options "TEL_S0_16_3"
#device isic0 at isa? port 0xd80 net irq 5 flags 3
#
# AVM A1 or AVM Fritz!Card
options "AVM_A1"
#device isic0 at isa? port 0x340 net irq 5 flags 4
#
# USRobotics Sportster ISDN TA intern
options "USR_STI"
#device isic0 at isa? port 0x268 net irq 5 flags 7
#
# ITK ix1 Micro
options "ITKIX1"
#device isic0 at isa? port 0x398 net irq 10 flags 18
#
# PnP-Cards:
# ----------
#
# Teles S0/16.3 PnP
options "TEL_S0_16_3_P"
#device isic0 at isa? port ? net irq ?
#
# Creatix ISDN-S0 P&P
options "CRTX_S0_P"
#device isic0 at isa? port ? net irq ?
#
# Dr. Neuhaus Niccy Go@
options "DRN_NGO"
#device isic0 at isa? port ? net irq ?
#
# Sedlbauer Win Speed
options "SEDLBAUER"
#device isic0 at isa? port ? net irq ?
#
# Dynalink IS64PH
options "DYNALINK"
#device isic0 at isa? port ? net irq ?
#
# ELSA QuickStep 1000pro ISA
options "ELSA_QS1ISA"
#device isic0 at isa? port ? net irq ?
#
# PCI-Cards:
# ----------
#
# ELSA QuickStep 1000pro PCI
options "ELSA_QS1PCI"
#device  isic0
#
# PCMCIA-Cards:
# -------------
#
# AVM PCMCIA Fritz!Card
options "AVM_A1_PCMCIA"
device  isic0 at isa? port 0x340 net irq 5 flags 10
#
# Active Cards:
# -------------
#
# Stollmann Tina-dd control device
device tina0 at isa? port 0x260 net irq 10
#
# ISDN Protocol Stack
# -------------------
# 
# Q.921 / layer 2 - i4b passive cards D channel handling
pseudo-device   "i4bq921"
#
# Q.931 / layer 3 - i4b passive cards D channel handling
pseudo-device   "i4bq931"
#
# layer 4 - i4b common passive and active card handling
pseudo-device   "i4b"
#
# ISDN devices
# ------------
#
# userland driver to do ISDN tracing (for passive cards only)
pseudo-device   "i4btrc"        4
#
# userland driver to control the whole thing
pseudo-device   "i4bctl"
#
# userland driver for access to raw B channel
pseudo-device   "i4brbch"       4
#
# userland driver for telephony
pseudo-device   "i4btel"        2
#
# network driver for IP over raw HDLC ISDN
pseudo-device   "i4bipr"        4
# enable VJ header compression detection for ipr i/f
options         IPR_VJ
#
# network driver for sync PPP over ISDN
pseudo-device   "i4bisppp"      4


# Parallel-Port Bus
#
# Parallel port bus support is provided by the `ppbus' device.
# Multiple devices may be attached to the parallel port, devices
# are automatically probed and attached when found.
#
# Supported devices:
# vpo   Iomega Zip Drive
#       Requires SCSI disk support ('scbus' and 'da'), best
#       performance is achieved with ports in EPP 1.9 mode.
# nlpt  Parallel Printer, use _instead_ of lpt0
# plip  Parallel network interface
# ppi   General-purpose I/O ("Geek Port")
# pps   Pulse per second Timing Interface
# lpbb  Philips official parallel port I2C bit-banging interface
#
# Supported interfaces:
# ppc   ISA-bus parallel port interfaces.  
#
controller      ppbus0
controller      vpo0    at ppbus?
device          nlpt0   at ppbus?
device          plip0   at ppbus?
device          ppi0    at ppbus?
device          pps0    at ppbus?
device          lpbb0   at ppbus?

controller      ppc0    at isa? disable port ? tty irq 7

# Kernel BOOTP support 

options         BOOTP           # Use BOOTP to obtain IP address/hostname
options         BOOTP_NFSROOT   # NFS mount root filesystem using BOOTP info
options         "BOOTP_NFSV3"   # Use NFS v3 to NFS mount root
options         BOOTP_COMPAT    # Workaround for broken bootp daemons.
options         "BOOTP_WIRED_TO=fxp0" # Use interface fxp0 for BOOTP

# If you want to disable loadable kernel modules (LKM), you
# might want to use this option.
#options                NO_LKM

#
# Add tie-ins for a hardware watchdog.  This only enable the hooks;
# the user must still supply the actual driver.
#
options         HW_WDOG

#
# Set the number of PV entries per process.  Increasing this can
# stop panics related to heavy use of shared memory. However, that can
# (combined with large amounts of physical memory) cause panics at
# boot time due the kernel running out of VM space.
#
# If you're tweaking this, you might also want to increase the sysctls
# "vm.v_free_min", "vm.v_free_reserved", and "vm.v_free_target".
#
# The value below is the one more than the default.
#
options         "PMAP_SHPGPERPROC=201"

#
# Disable swapping. This option removes all code which actually performs
# swapping, so it's not possible to turn it back on at run-time.
#
# This is sometimes usable for systems which don't have any swap space
# (see also sysctls "vm.defer_swapspace_pageouts" and
# "vm.disable_swapspace_pageouts")
#
#options        NO_SWAPPING

# Set the number of sf_bufs to allocate. sf_bufs are virtual buffers
# for sendfile(2) that are used to map file VM pages, and normally
# default to a quantity that is roughly 16*MAXUSERS+512. You would
# typically want about 4 of these for each simultaneous file send.
#
options         "NSFBUFS=1024"

# More undocumented options for linting.

options         CLK_CALIBRATION_LOOP
options         "CLK_USE_I8254_CALIBRATION"
options         CLK_USE_TSC_CALIBRATION
options         CLUSTERDEBUG
options         COMPAT_LINUX
options         CPU_UPGRADE_HW_CACHE
options         DEBUG
options         "DEBUG_1284"
#options        DISABLE_PSE
options         "EXT2FS"
options         "I586_PMC_GUPROF=0x70000"
options         "IBCS2"
options         KEY
options         KEY_DEBUG
options         LOCKF_DEBUG
options         LOUTB
options         KBD_MAXRETRY=4
options         KBD_MAXWAIT=6
options         KBD_RESETDELAY=201
options         KBDIO_DEBUG=2
options         MSGMNB=2049
options         MSGMNI=41
options         MSGSEG=2049
options         MSGSSZ=16
options         MSGTQL=41
options         NBUF=512
options         NETATALKDEBUG
options         NMBCLUSTERS=1024
options         NPX_DEBUG
options         PANIC_REBOOT_WAIT_TIME=16
options         "PCVT_24LINESDEF"
options         PCVT_CTRL_ALT_DEL
options         PCVT_EMU_MOUSE
options         PCVT_FREEBSD=211
options         PCVT_META_ESC
options         PCVT_NSCREENS=9
options         PCVT_PRETTYSCRNS
options         PCVT_SCREENSAVER
options         PCVT_USEKBDSEC
options         "PCVT_VT220KEYB"
options         PSM_DEBUG=1
options         SCSI_NCR_DEBUG
options         SCSI_NCR_DFLT_TAGS=4
options         SCSI_NCR_MAX_SYNC=10000
options         SCSI_NCR_MAX_WIDE=1
options         SCSI_NCR_MYADDR=7
options         SEMMAP=31
options         SEMMNI=11
options         SEMMNS=61
options         SEMMNU=31
options         SEMMSL=61
options         SEMOPM=101
options         SEMUME=11
options         SHOW_BUSYBUFS   # List buffers that prevent root unmount
options         SHMALL=1025
options         "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)"
options         SHMMAXPGS=1025
options         SHMMIN=2
options         SHMMNI=33
options         SHMSEG=9
options         SI_DEBUG
options         SIMPLELOCK_DEBUG
options         SPX_HACK
options         VFS_BIO_DEBUG

# The 'dpt' driver provides support for DPT controllers (http://www.dpt.com/).
# These have hardware RAID-{0,1,5} support, and do multi-initiator I/O.
# The DPT controllers are commonly re-licensed under other brand-names -
# some controllers by Olivetti, Dec, HP, AT&T, SNI, AST, Alphatronic, NEC and
# Compaq are actually DPT controllers.
#
# See sys/dev/dpt for debugging and other subtle options.
#   DPT_VERIFY_HINTR        Performs some strict hardware interrupts testing.
#                           Only use if you suspect PCI bus corruption problems
#   DPT_RESTRICTED_FREELIST Normally, the freelisat used by the DPT for queue
#                           will grow to accomodate increased use.  This growth
#                           will NOT shrink.  To restrict the number of queue
#                           slots to exactly what the DPT can hold at one time,
#                           enable this option.
#   DPT_MEASURE_PERFORMANCE Enables a set of (semi)invasive metrics. Various
#                           instruments are enabled.  The tools in 
#                           /usr/sbin/dpt_* assume these to be enabled.
#   DPT_FREELIST_IS_STACK   For optimal L{1,2} CPU cache utilization, enable
#                           this option.  Otherwise, the transaction queue is
#                           a LIFO.  I cannot measure the performance gain.
#   DPT_HANDLE_TIMEOUTS     Normally device timeouts are handled by the DPT.
#                           If you ant the driver to handle timeouts, enable
#                           this option.  If your system is very busy, this
#                           option will create more trouble than solve.
#   DPT_TIMEOUT_FACTOR      Used to compute the excessive amount of time to
#                           wait when timing out with the above option.
#  DPT_DEBUG_xxxx           These are controllable from sys/dev/dpt/dpt.h
#  DPT_LOST_IRQ             When enabled, will try, once per second, to catch
#                           any interrupt that got lost.  Seems to help in some
#                           DPT-firmware/Motherboard combinations.  Minimal
#                           cost, great benefit.
#  DPT_RESET_HBA            Make "reset" actually reset the controller
#                           instead of fudging it.  Only enable this if you
#                           are 100% certain you need it.
#  DPT_SHUTDOWN_SLEEP       Reset controller if a request take more than
#                           this number of seconds.  Do NOT enable this
#                           unless you are really, really, really certain
#                           you need it.  You are advised to call Simon (the
#                           driver author) before setting it, and NEVER,
#                           EVER set it to less than 300s (5 minutes).

controller      dpt0

# DPT options
options DPT_VERIFY_HINTR
options DPT_RESTRICTED_FREELIST
#!CAM# options DPT_MEASURE_PERFORMANCE
options DPT_FREELIST_IS_STACK
#!CAM# options DPT_HANDLE_TIMEOUTS
options DPT_TIMEOUT_FACTOR=4
options DPT_INTR_DELAY=200      # Some motherboards need that
options DPT_LOST_IRQ
options DPT_RESET_HBA

# Don't EVER set this without having talked to Simon Shapiro on the phone
# first.
options DPT_SHUTDOWN_SLEEP=500

# USB support
# UHCI controller 
controller    uhci0
# OHCI controller
controller    ohci0
# General USB code (mandatory for USB)
controller    usb0
#
# for the moment we have to specify the priorities of the device
# drivers explicitly by the ordering in the list below. This will
# be changed in the future.
#
# USB mouse
device        ums0
# USB keyboard
device        ukbd0
# USB printer
device        ulpt0
# USB hub (kind of mandatory, no other driver is available for the root hub)
device        uhub0
# USB communications driver
device        ucom0
# USB modem driver
device        umodem0
# Human Interface Device (anything with buttons and dials)
device        hid0
# Generic USB device driver
device        ugen0
#
options       USB_DEBUG
options       USBVERBOSE