patch-2.1.67 linux/Documentation/Configure.help

Next file: linux/Documentation/VGA-softcursor.txt
Previous file: linux/CREDITS
Back to the patch index
Back to the overall index

diff -u --recursive --new-file v2.1.66/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -148,6 +148,15 @@
   nothing to do with the loopback device used for network connections
   from the machine to itself.  Most users will answer N here.
 
+Network Block Device support
+CONFIG_BLK_DEV_NBD
+  Saying Y here will allow computer to serve as client for network
+  block device - it will be able to use block devices exported by
+  servers (mount filesystems on them etc.). It also allows you to run
+  a block-device in userland (making server and client physicaly the same
+  computer, communicating using loopback). Normal users say N
+  here. Read Documentation/nbd.txt.
+
 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
 CONFIG_BLK_DEV_IDE
   This will use the full-featured IDE driver to control up to four IDE
@@ -522,7 +531,30 @@
   kernel, you should consider updating your networking tools too
   because changes in the kernel and the tools often go hand in hand;
   see http://www.inka.de/sites/lina/linux/NetTools/index_en.html for
-  details. 
+  details.
+
+Packet socket
+CONFIG_PACKET
+  Packet protocol is used by applications directly communicating
+  to network devices f.e. tcpdump. You want that they worked,
+  so that choose Y. If you run kerneld, option M is the best solution.
+
+Kernel/User netlink socket
+CONFIG_NETLINK
+  This protocol family is used for bi-directional communication
+  between kernel and user level daemons. This option is unlikely to
+  be useful for common workstation, but if you configure router or
+  firewall, do not hesitate: press Y.
+
+Routing messages
+CONFIG_RTNETLINK
+  One of netlink protocols used by kernel routing engine.
+  You will need it to use advanced routing features.
+
+Netlink device emulation
+CONFIG_NETLINK_DEV
+  It is backward compatibility option, choose Y for now.
+  This option will be removed soon.
 
 Network aliasing
 CONFIG_NET_ALIAS
@@ -741,9 +773,10 @@
 
 PCI bridge optimization (experimental)
 CONFIG_PCI_OPTIMIZE
-  This can improve access times for some hardware devices under
-  certain BIOSes if your computer uses a PCI bus system. This is
-  recommended; say Y.
+  This can improve access times for some hardware devices if you have
+  a really broken BIOS and your computer uses a PCI bus system. Set to Y
+  if you think it might help, but try turning it off if you experience
+  any problems with the PCI bus.
 
 MCA support
 CONFIG_MCA
@@ -882,11 +915,11 @@
   you have use for it.  
   If you don't know what to answer at this point, say Y.
 
-Processor type
+Processor family
 CONFIG_M386
   This is the processor type of your CPU. This information is used for
   optimizing purposes. In order to compile a kernel that can run on
-  all Intel CPU types (albeit not optimally fast), you can specify
+  all x86 CPU types (albeit not optimally fast), you can specify
   "386" here.  If you specify one of "486" or "Pentium" or "PPro",
   then the kernel will run on all of these CPUs: 486 and Pentium
   (=586) and Pentium Pro (=686). In rare cases, it can make sense to
@@ -963,6 +996,72 @@
   when requested.  If this option is enabled the kernel will probe to see
   what devices are connected at boot time.
 
+Plug and Play subsystem (EXPERIMENTAL)
+CONFIG_PNP_DRV
+  This enables support for the new Plug-and-Play (or PnP) Linux
+  subsystems. This support is required for PnP ISA support, and for PnP
+  Legacy support. User-mode utilities for this support may be found at
+  http://www.lpsg.demon.co.uk/pnp-linux.html.
+
+PnP resource management
+CONFIG_KERNEL_PNP_RESOURCE
+  This option will cause the new PnP generic resource management
+  routines to be used instead of the old routines request_xxx and
+  free_xxx. Emulation routines are put in place to support the old
+  calling style. This code support masks for IO decoding (required for
+  Plug and Play devices). There is no need to enable this option unless
+  you want to - these features will still be used where they are needed.
+  However, enabling it will reduce your kernel size slightly, and also
+  allow you to test this code more extensively.
+
+Support for boot-loaded PnP configuration (RECOMMENDED)
+CONFIG_PNP_BLDCONFIG
+  This will enable support for preloading data about the configuration
+  of any Plug-and-Play devices in the system into the kernel at boot
+  time, which means that any devices required at boot can be configured
+  at this time manually. Say Y unless you have a reason not to.
+
+PnP ISA support
+CONFIG_PNP_ISA
+  This option is required to allow the Linux PnP subsystem to handle
+  Plug and Play ISA devices. This includes full support for PnP ISA,
+  including the I/O range check feature.
+
+PnP ISA backwards-compatiblity support
+CONFIG_PNP_ISA_COMPAT
+  This option will enable partial backwards compatibility with drivers
+  written using older versions (up to the last 0.2.x) of the PnP driver
+  written by Tom Lees <tom@lpsg.demon.co.uk>.
+
+PnP Legacy device support
+CONFIG_PNP_LEGACY
+  Before PnP ISA was standardized, several "jumperless", or
+  "soft-configurable" boards were finding there way onto the market.
+  These cards used somewhat proprietary mechanisms for configuring
+  IRQs, DMAs, IO addresses, and memory ranges. These devices (mainly
+  network cards, but also some sound card) can be configured as any
+  other PnP device can by enabling this option, if appropriate drivers
+  for these devices are available.
+
+PnP sysctl support (RECOMMENDED)
+CONFIG_PNP_SYSCTL
+  This option enables support for the user-mode interface to the
+  kernel-mode PnP systems. It requires that you enable CONFIG_SYSCTL.
+  The only reason you might want to switch this off is if you aren't
+  going to use user-mode utilities to configure PnP, and you want to
+  save a couple of kilobytes of kernel space. Answer Y unless you know
+  what you are doing. User-mode utilities and a library for accessing
+  this interface may be found at
+  http://www.lpsg.demon.co.uk/pnp-linux.html.
+
+PnP auto-configures all devices on startup
+CONFIG_PNP_BOOTINIT
+  This option will allow the PnP subsystem to automatically configure
+  all the   PnP devices it finds upon system startup (or at least
+  attempt to). This is useful if you have older driver which do not use
+  the Linux-PnP system to configure PnP devices, and which you need
+  configured by PnP in order to use.
+
 Enable loadable module support
 CONFIG_MODULES
   Kernel modules are small pieces of compiled code which can be 
@@ -1039,9 +1138,7 @@
 IP: multicasting
 CONFIG_IP_MULTICAST
   This is code for addressing several networked computers at once,
-  enlarging your kernel by about 2 kB. If you are using gated, the
-  daemon that updates your computer's routing tables, you will need to
-  have this option compiled in. You also need multicasting if you
+  enlarging your kernel by about 2 kB. You need multicasting if you
   intend to participate in the MBONE, a high bandwidth network on top
   of the internet which carries audio and video broadcasts. More
   information about the MBONE is on the WWW at
@@ -1112,6 +1209,39 @@
   recorded, you need the tool ipfwadm (available via ftp (user:
   anonymous) from ftp.xos.nl/pub/linux/ipfwadm/).
 
+IP: kernel level autoconfiguration
+CONFIG_IP_PNP
+  This enables automatic configuration of IP addresses of devices and
+  of the routing table during kernel boot, based on either information
+  supplied at the kernel command line or by BOOTP or RARP protocols.
+  You need to say Y only for diskless machines requiring network access
+  to boot (see CONFIG_ROOT_NFS for more information about root volume
+  mounted via NFS), because all other machines configure the network in
+  their startup scripts.
+
+BOOTP support
+CONFIG_IP_PNP_BOOTP
+  If you want your Linux box to mount its whole root filesystem from
+  some other computer over the net via NFS and you want the IP address
+  of your computer to be discovered automatically at boot time using
+  the BOOTP protocol (a special protocol designed for doing this job),
+  say Y here. In case the boot ROM of your network card was designed
+  for booting Linux and does BOOTP itself, providing all necessary
+  information on the kernel command line, you can say N here.  If
+  unsure, say Y. Note that in case you want to use BOOTP, a BOOTP
+  server must be operating on your network. Read
+  Documentation/nfsroot.txt for details.
+
+RARP support
+CONFIG_IP_PNP_RARP
+  If you want your Linux box to mount its whole root filesystem from
+  some other computer over the net via NFS and you want the IP address
+  of your computer to be discovered automatically at boot time using
+  the RARP protocol (an older protocol which is being obsoleted by
+  BOOTP and DHCP), say Y here. Note that in case you want to use RARP,
+  a RARP server must be operating on your network. Read
+  Documentation/nfsroot.txt for details.
+
 IP: tunneling
 CONFIG_NET_IPIP
   Tunneling means encapsulating data of one protocol type within
@@ -1128,7 +1258,22 @@
   one encapsulator called tunnel.o and one decapsulator called
   ipip.o. You can read details in drivers/net/README.tunnel. Most
   people won't need this and can say N.
-  
+
+IP: GRE tunnels over IP
+CONFIG_NET_IPGRE
+  Another kind of tunneling protocol - "Generic Routing Encapsulation".
+  It allows to tunnel any networking protocol over existing IPv4
+  infrastructure. At the moment only IPv4 and IPv6 are supported.
+  It is useful, if another endpoint is Cisco router: it likes
+  GRE much more than IPIP and, particularly, allows multicasts
+  redistribution over GRE tunnels.
+
+IP: broadcast GRE over IP
+CONFIG_NET_IPGRE_BROADCAST
+  One application of GRE/IP, allowing to construct broadcast LAN,
+  looking like ethernet network, distributed over the Internet.
+  It requires, that your domain supported multicast routing.
+
 IP: firewall packet logging
 CONFIG_IP_FIREWALL_VERBOSE
   This gives you information about what your firewall did with
@@ -1220,6 +1365,21 @@
   drivers/net/README.multicast. If you haven't heard about it, you
   don't need it.
 
+IP: PIM-SM version 1 support
+CONFIG_IP_PIMSM_V1
+  Kernel side support for Sparse Mode PIM version 1. This multicast
+  routing protocol is used widely due to Cisco supports it.
+  You need special software to use it (pimd-v1). Press N, if
+  you do not want to use PIM-SM v1. Note, that Dense Mode PIM
+  need not this option.
+
+IP: PIM-SM version 2 support
+CONFIG_IP_PIMSM_V2
+  Kernel side support for Sparse Mode PIM version 2. You need
+  experimental routing daemon supporting it (pimd or gated-5).
+  This protocol is not used widely, so that press Y, if you
+  do not want play with it.
+
 PC/TCP compatibility mode
 CONFIG_INET_PCTCP
   If you have been having difficulties telneting to your Linux machine
@@ -1320,6 +1480,13 @@
   a second or   satellite links this option will make no difference to
   performance.
 
+BSD Unix domain sockets
+CONFIG_UNIX
+  Y if you want BSD Unix domain sockets.  Unless you are working on an
+  embedded system or somthing, you probably want to say Y.  If you try
+  building this as a module and you are running kerneld, you need to make
+  sure and add 'alias net-pf-1 unix' to your /etc/conf.module file.
+
 The IPv6 protocol
 CONFIG_IPV6
   This is experimental support for the next version of the Internet
@@ -1338,6 +1505,20 @@
   be called ipv6.o. If you want to compile it as a module, say M here
   and read Documentation/modules.txt.  It's safe to say N for now.
 
+IPv6: enable EUI-64 token format
+CONFIG_IPV6_EUI64
+  6bone is moving to new aggregatable address format and new link local
+  address assignment (EUI-64). Say Y, if your site already upgraded, or
+  started upgrade.
+
+IPv6: disable provider based addresses
+CONFIG_IPV6_NO_PB
+  Linux tries to operate correctly, when site is moved to EUI-64
+  only partially. Unfortunately, these two formats ("provider based"
+  and "aggregatable") are incompatible. Say Y, if your site finished
+  upgrade, and/or you encountered some problems caused by presense of
+  two link-local addresses on an interface.
+
 The IPX protocol
 CONFIG_IPX
   This is support for the Novell networking protocol, IPX, commonly
@@ -2675,6 +2856,18 @@
   with many transceiver designs and the fact that the TCM3105 (if
   used) is operated widely outside its specifications.
 
+Soundcard modem support for 2666 baud AFSK modulation
+CONFIG_SOUNDMODEM_AFSK2666
+  This option enables the soundmodem driver 2666 baud AFSK modem.
+  This modem is experimental, and not compatible to anything
+  else I know of.
+
+Soundcard modem support for 4800 baud 8PSK modulation
+CONFIG_SOUNDMODEM_PSK4800
+  This option enables the soundmodem driver 4800 baud 8PSK modem.
+  This modem is experimental, and not compatible to anything
+  else I know of.
+
 Soundcard modem support for 4800 baud HAPN-1 modulation
 CONFIG_SOUNDMODEM_HAPN4800
   This option enables the soundmodem driver 4800 baud HAPN-1
@@ -4465,29 +4658,6 @@
   module, say M here and read Documentation/modules.txt. If unsure,
   say N.
 
-BOOTP support
-CONFIG_RNFS_BOOTP
-  If you want your Linux box to mount its whole root filesystem from
-  some other computer over the net via NFS and you want the IP address
-  of your computer to be discovered automatically at boot time using
-  the BOOTP protocol (a special protocol designed for doing this job),
-  say Y here. In case the boot ROM of your network card was designed
-  for booting Linux and does BOOTP itself, providing all necessary
-  information on the kernel command line, you can say N here.  If
-  unsure, say Y. Note that in case you want to use BOOTP, a BOOTP
-  server must be operating on your network. Read
-  Documentation/nfsroot.txt for details.
-
-RARP support
-CONFIG_RNFS_RARP
-  If you want your Linux box to mount its whole root filesystem from
-  some other computer over the net via NFS and you want the IP address
-  of your computer to be discovered automatically at boot time using
-  the RARP protocol (an older protocol which is being obsoleted by
-  BOOTP and DHCP), say Y here. Note that in case you want to use RARP,
-  a RARP server must be operating on your network. Read
-  Documentation/nfsroot.txt for details.
-
 ISO9660 cdrom filesystem support
 CONFIG_ISO9660_FS
   This is the standard filesystem used on CDROMs. It was previously
@@ -5492,38 +5662,18 @@
 
 PC joystick support
 CONFIG_JOYSTICK
-  If you have a joystick, you can say Y here. If you then create a
-  character special file under /dev with major number 15 and minor
-  number 0 or 1 (for the two joystick ports) using mknod ("man
-  mknod"), you can read the status of the buttons and the x and y
-  coordinates from that file. More information, an example program and
-  a calibration program are contained in the joystick package which is
-  available via ftp (user: anonymous) in
-  sunsite.unc.edu/pub/Linux/kernel/patches/console/. This driver is
-  also available as a module ( = code which can be inserted in and
-  removed from the running kernel whenever you want). The module will
-  be called joystick.o. If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
-
-Radio support
-CONFIG_MISC_RADIO
-  If you have a radio card (you will probably know if you do!), then
-  you will want to say "y" here and make a character device file 
-  (usually /dev/radio) with major number 10 and minor 152 using mknod
-  ("man mknod").  And then, don't forget to pick up some useful tools
-  to use said device (you _might_ find something at ftp.lmh.ox.ac.uk:
-  /users/weejock/linux/radio/, but I haven't written anything too
-  useful yet...)
-
-AIMSlab RadioTrack card
-CONFIG_RADIO_RTRACK
-  Choose "y" here if you have one of these, and then fill in the port
-  address below.
-
-RadioTrack i/o port
-CONFIG_RADIO_RTRACK_PORT
-  Enter either 0x30f or 0x20f here.  The card default is 0x30f, if you
-  haven't changed the jumper setting on the card.
+  If you have a PC compatible analog or digital joystick, you can
+  say Y here. If you then create a character special file under /dev
+  with major number 15 and minor number 0 or 1 (for the two joystick
+  ports) using mknod ("man mknod"), you can read the status of the
+  buttons and the x and y coordinates from that file. More
+  information, an example program and a calibration program are
+  contained in the joystick package which is available at:
+  ftp://sunsite.unc.edu/pub/Linux/kernel/patches/console
+  This driver is also available as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called joystick.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 ARC console time
 CONFIG_RTC_ARC
@@ -5767,9 +5917,9 @@
   flush the disks, reboot the system immediately or dump some status
   information). This is accomplished by pressing various keys while
   holding SysRq (Alt+PrintScreen). As you are expected to be a kernel
-  hacker to use this, the simple rule about learning what the keys
+  hacker to use this, the simple rule about learning what do the keys
   mean is "Use the source, Luke!" -- read drivers/char/sysrq.c.  
-  Don't say Y unless you really know what this hack does.
+  Don't say Y unless you really know what does this hack do.
 
 ISDN subsystem
 CONFIG_ISDN
@@ -5979,6 +6129,124 @@
   removed from the running kernel whenever you want), say M and read
   Documentation/modules.txt. If unsure, say Y.
 
+Support for Cyrix processors
+CONFIG_CYRIX
+  This enables recognition of Cyrix processors. Without it
+  /proc/cpuinfo will list your processor as an unknown model
+  of Cyrix. With it it will list the correct details. It should
+  be safe to say Y here regardless of what processor you are
+  actually using. If this option is not enabled none of the
+  Cyrix feature options are available.
+
+Enable suspend on halt power saving feature
+CONFIG_CYRIX_SUSP_HLT
+  Suspend on halt causes the processor to enter a low power state
+  when the "hlt" instruction is executed. This is disabled at
+  power up and many BIOSs leave it that way. You probably want it
+  enabled since it dramatically reduces the operating temperature
+  of the processor. In a few rare cases there may be problems
+  with some bus master DMA cards if this is enabled.
+
+No I/O recovery delays
+CONFIG_CYRIX_FAST_IO
+  Historically programmers used "jmp $+2" instructions to create
+  delays between I/O instructions. The branch prediction of 5x86
+  and higher processors renders this ineffective and so a selectable
+  delay is implemented for I/O instructions in the processor. Linux
+  uses dummy I/O instructions where necessary rather than jumps
+  and so the extra processor imposed delay should not be necessary.
+  Enabling this option removes this delay.
+
+5x86 performance features
+CONFIG_CYRIX_5X86
+  The Cyrix 5x86 has several performance feature which are enabled
+  using on-chip registers. This code attempts to ensure that the
+  useful features are set to suit Linux. Read Documentation/CPU/Cyrix
+  before enabling this.
+    WARNING: If this is enabled you may find that the only way to
+  reboot is to power cycle the machine. Even a hard reboot seems
+  to fail on some systems.
+
+6x86 performance features
+CONFIG_CYRIX_6X86
+  The Cyrix 6x86 has several performance feature which are enabled
+  using on-chip registers. Most are normally enabled by the BIOS
+  however this code ensures that all the useful ones are set to
+  suit Linux. Read Documentation/CPU/Cyrix before enabling this.
+
+Avoid unnecessary locked cycles
+CONFIG_CYRIX_6X86_NOLOCK
+  Enabling this option causes the 6x86 not to use locked bus cycles
+  except for page table access and interrupt acknowledge cycles.
+  This allows the data used by descriptor tables, xchg instructions
+  and instructions preceeded by the LOCK prefix to be cached leading
+  to improved performance. Enabling this option has no effect if
+  an SMP kernel is being built - SMP requires locked cycles to
+  guarantee processor synchronization.
+
+Allocate L1 cache lines on write misses
+CONFIG_CYRIX_6X86_WTALLOC
+  If this is enabled L1 cache write misses will cause a cache line
+  to be allocated. This may result in increased performance. On the
+  other hand it may cause excessive trashing of the L1 cache when
+  copying or zeroing pages. In general you _probably_ win...
+
+Branch Target Buffer features
+CONFIG_CYRIX_6X86_BTB
+  The Cyrix 6x86 has branch prediction logic which is normally
+  only set to handle short branches (as in small loops and ifs).
+  This code attempts on configure the branch prediction logic
+  appropriately. Read Documentation/CPU/Cyrix before enabling this.
+
+Variable sized paging mechanism (VSPM)
+CONFIG_CYRIX_6X86_VSPM
+  Variable sized paging mechanism (VSPM) is a feature of the Cyrix
+  6x86 family of processors that allows large regions of memory
+  to be mapped in one go, significantly reducing the amount of work
+  the MMU has to do compared with traditional paging. However VSPM
+  is known to be buggy in many 6x86 chip revisions. Please read
+  Documentation/CPU/Cyrix before enabling this.
+    WARNING: If this is enabled you may find that the only way to
+  reboot is to power cycle the machine. Even a hard reboot seems
+  to fail on some systems.
+
+Allocate L1 cache lines on write misses
+CONFIG_AMD_K5_WTALLOC
+  If this is enabled L1 cache write misses will cause a cache line
+  to be allocated. This may result in increased performance. On the
+  other hand it may cause excessive trashing of the L1 cache when
+  copying or zeroing pages. In general you _probably_ win...
+
+Allocate L1 cache lines on write misses
+CONFIG_AMD_K6_WTALLOC
+  If this is enabled L1 cache write misses will cause a cache line
+  to be allocated. This may result in increased performance. On the
+  other hand it may cause excessive trashing of the L1 cache when
+  copying or zeroing pages. In general you _probably_ win...
+
+Use write cacheability detection
+CONFIG_AMD_K6_WTALLOC_WCDE
+  Write cacheability detection requires the system logic to assert
+  the cache enable bus signal during a write cycle. Some chipsets
+  do this and some do not. Some, such as Triton, do but not at
+  the appropriate point during the write cycle. Cacheability
+  detection is not normally useful unless you have memory mapped
+  devices which exist outside the 640k-1M range but within your
+  actual memory. (There is another option that disables write
+  allocate for the 15M-16M range commonly used by older VLB
+  video cards). You probably do not want to enable this.
+
+No write allocate between 15MB-16MB
+CONFIG_AMD_K6_WTALLOC_WAE15M
+  There were a small number of cards, mainly VESA Local Bus
+  video cards, that were memory mapped to the 15M-16M address
+  range. If you have such a card you do not want write allocate
+  to delay or reorder writes to this space so you must enable
+  this option. Other memory mapped cards are either outside the
+  systems memory space or are in the 640k-1M range which is
+  not subject to write allocate so this option is not normally
+  required.
+
 # m68k-specific kernel options
 # Documented by Chris Lawrence <quango@themall.net> et al.
 
@@ -6214,6 +6482,11 @@
   1260 accelerator, and the optional SCSI module, say Y.  Otherwise,
   say N.
 
+Fastlane SCSI support
+CONFIG_FASTLANE_SCSI
+  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one
+  in the near future, say Y to this question.  Otherwise, say N.
+
 Atari native SCSI support
 CONFIG_ATARI_SCSI
   If you have an Atari with built-in NCR5380 SCSI controller (TT,
@@ -6333,6 +6606,33 @@
   whenever you want). If you want to compile it as a module, say M
   here and read Documentation/modules.txt.
 
+Radio support
+CONFIG_MISC_RADIO
+  If you have a radio card (you will probably know if you do!), then
+  you will want to say "y" here and make a character device file 
+  (usually /dev/radio) with major number 10 and minor 152 using mknod
+  ("man mknod").  And then, don't forget to pick up some useful tools
+  to use said device (you _might_ find something at ftp.lmh.ox.ac.uk:
+  /users/weejock/linux/radio/, but I haven't written anything too
+  useful yet...)
+
+AIMSlab RadioTrack card
+CONFIG_RADIO_RTRACK
+  Choose "y" here if you have one of these, and then fill in the port
+  address below.
+
+RadioTrack i/o port
+CONFIG_RADIO_RTRACK_PORT
+  Enter either 0x30f or 0x20f here.  The card default is 0x30f, if you
+  haven't changed the jumper setting on the card.
+
+Atari SCC serial DMA support
+CONFIG_ATARI_SCC_DMA
+  This enables DMA support for receiving data on channel A of the SCC. If
+  you have a TT you may say Y here and read drivers/char/atari_SCC.README.
+  All other users should say N here, because only the TT has SCC-DMA, even
+  if your machine keeps claiming so at boot time.
+
 Atari MIDI serial support
 CONFIG_ATARI_MIDI
   If you want to use your Atari's MIDI port in Linux, say Y.
@@ -6462,6 +6762,17 @@
   Power Macintoshes and clones with ethernet built-in on the
   motherboard will usually use a MACE (Medium Access Control for
   Ethernet) interface.  Say Y to include support for the MACE chip.
+
+Video For Linux
+CONFIG_VIDEO_DEV
+  Support for audio/video capture and overlay devices. The exact capabilities
+  of each device vary. User tools for this are available from
+  ftp://ftp.uk.linux.org/pub/linux/video4linux
+
+BT848 Video For Linux
+CONFIG_VIDEO_BT848
+  Support for BT848 based frame grabber/overlay boards. This includes the 
+  Miro, Hauppauge and STB boards.
 
 # need an empty line after last entry, for sed script in Configure.
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen, slshen@lbl.gov