patch-2.1.124 linux/Documentation/Configure.help

• Lines: 365
• Date: Sun Oct 4 10:21:45 1998
• Orig file: v2.1.123/linux/Documentation/Configure.help
• Orig date: Mon Sep 28 10:51:32 1998

diff -u --recursive --new-file v2.1.123/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -431,6 +431,20 @@
 
   It is safe to say Y to this question.
 
+Boot off-board chipsets first support
+CONFIG_BLK_DEV_OFFBOARD
+  Normally, IDE controllers built into the motherboard (on-board
+  controllers) are assigned to ide0 and ide1 while those on add-in
+  PCI cards (off-board controllers) are relegated to ide2 and ide3.
+  Saying Y to here will reverse the situation, with off-board
+  controllers on ide0/1 and on-board controllers on ide2/3. This
+  can improve the usability of some boot managers such as LILO
+  when booting from a drive on an off-board controller.
+  Note that this will rearrange the order of the hd* devices and
+  may require modification of fstab and other files.
+
+  If in doubt, say N.
+
 Use DMA by default when available
 CONFIG_IDEDMA_AUTO
   Prior to kernel version 2.1.112, Linux used to automatically use
@@ -650,9 +664,11 @@
   The module will be called pg.o.  You must also have at least one 
   parallel port protocol driver in your system.  This driver 
   implements an API loosely related to the generic SCSI driver.  
-  See /usr/include/linux/pg.h for details, or visit 
-  http://www.torque.net/parport/cdr.html for more information and
-  the required patches to cdrecord.
+  See /usr/include/linux/pg.h for details. 
+
+  You can obtain the most recent version of cdrecord from
+  ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ .  Versions 1.6.1a3 and
+  later fully support the pg driver.
 
 ATEN EH-100 protocol
 CONFIG_PARIDE_ATEN
@@ -1173,7 +1189,8 @@
   that implements the TGA interface (much like the VGA standard, but
   older TGA adapters are *not* VGA compatible).  On such systems, you
   should say Y here so that the TGA driver rather than the standard
-  VGA driver is used. 
+  VGA driver is used.  Note that, at this time, there is no X server
+  for these systems. If unsure, try N.
 
 PCI support
 CONFIG_PCI
@@ -1462,6 +1479,13 @@
   display that complies with the generic VGA standard. Virtually
   everyone wants that. Say Y.
 
+Use 64KB of VGA video RAM (aka: Maximum VGA Scrollback)
+CONFIG_VGA_GET_64KB
+  Use 64K rather than 32K of video RAM. This doesn't actually work
+  on all "VGA" controllers. If your vga card can do it, then you 
+  can say Y here to get more scrollback buffer (shift-pgup) on VGA
+  consoles.
+
 Video mode selection support
 CONFIG_VIDEO_SELECT
   This enables support for text mode selection on kernel startup. If
@@ -1483,26 +1507,20 @@
   hardware. It represents the frame buffer of some video hardware and
   allows application software to access the graphics hardware through
   a well-defined interface, so the software doesn't need to know
-  anything about the low-level (hardware register) stuff. 
+  anything about the low-level (hardware register) stuff. This works
+  across the different architectures supported by Linux and makes the
+  implementation of application programs easier and more portable; at
+  this point, an X server exists which uses the frame buffer device
+  exclusively.
 
-  Frame buffer devices work identically across the different
-  architectures supported by Linux and make the implementation of
-  application programs easier and more portable; at this point, an X
-  server exists which uses the frame buffer device exclusively.
-  On several non-X86 architectures, the frame buffer device is the
-  only way to use the graphics hardware.
- 
   The device is accessed through special device nodes, usually located
   in the /dev directory, i.e. /dev/fb*.
 
-  You need an utility program called fbset to make full use of frame
-  buffer devices. Please read the file
-  Documentation/fb/framebuffer.txt for more information.
-
-  If you want to play with it, say Y here and also to the driver for
-  your graphics board, below. If unsure, say N, unless you are
-  compiling a kernel for a non-X86 architecture, in which case you
-  should say Y.
+  Please read the file Documentation/fb/framebuffer.txt for more
+  information.
+
+  If you want to play with it, say Y here and to the driver for your
+  graphics board, below. If unsure, say N.
 
 Acorn VIDC support
 CONFIG_FB_ACORN
@@ -1541,34 +1559,33 @@
 
 Amiga CyberVision support
 CONFIG_FB_CYBER
-  This enables support for the Cybervision 64 graphics card from
-  Phase5. Please note that its use is not all that intuitive (i.e. if
-  you have any questions, be sure to ask!). Say N unless you have a
-  Cybervision 64 or plan to get one before you next recompile the
-  kernel. Please note that this driver DOES NOT support the
-  Cybervision 64 3D card, as they use incompatible video chips.
+  This enables support for the Cybervision 64 graphics card from Phase5.
+  Please note that its use is not all that intuitive (i.e. if you have
+  any questions, be sure to ask!).  Say N unless you have a Cybervision
+  64 or plan to get one before you next recompile the kernel.         
+  Please note that this driver DOES NOT support the Cybervision 64 3D
+  card, as they use incompatible video chips.           
 
 Amiga CyberVision3D support (EXPERIMENTAL)
 CONFIG_FB_VIRGE
-  This enables support for the Cybervision 64/3D graphics card from
-  Phase5. Please note that its use is not all that intuitive (i.e. if
-  you have any questions, be sure to ask!). Say N unless you have a
-  Cybervision 64/3D or plan to get one before you next recompile the
-  kernel. Please note that this driver DOES NOT support the older
-  Cybervision 64 card, as they use incompatible video chips.
+  This enables support for the Cybervision 64/3D graphics card from Phase5.
+  Please note that its use is not all that intuitive (i.e. if you have
+  any questions, be sure to ask!).  Say N unless you have a Cybervision
+  64/3D or plan to get one before you next recompile the kernel.         
+  Please note that this driver DOES NOT support the older Cybervision 64
+  card, as they use incompatible video chips.           
 
 Amiga RetinaZ3 support (EXPERIMENTAL)
 CONFIG_FB_RETINAZ3
-  This enables support for the Retina Z3 graphics card. Say N unless
-  you have a Retina Z3 or plan to get one before you next recompile
-  the kernel.
+  This enables support for the Retina Z3 graphics card. Say N unless you
+  have a Retina Z3 or plan to get one before you next recompile the kernel.
 
 Amiga CLgen driver (EXPERIMENTAL)
 CONFIG_FB_CLGEN
-  This enables support for Cirrus Logic GD542x/543x based boards on
-  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
-  Say N unless you have such a graphics board or plan to get one
-  before you next recompile the kernel.
+  This enables support for Cirrus Logic GD542x/543x based boards on Amiga:
+  SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.  Say N
+  unless you have such a graphics board or plan to get one before you next
+  recompile the kernel.
 
 Atari native chipset support
 CONFIG_FB_ATARI
@@ -1597,6 +1614,11 @@
   This driver supports a frame buffer for the "platinum" graphics adapter
   in some Power Macintoshes.
 
+PowerMac "valkyrie" frame buffer device support
+CONFIG_FB_VALKYRIE
+  This driver supports a frame buffer for the "valkyrie" graphics adapter
+  in some Power Macintoshes.
+
 Chips 65550 display support
 CONFIG_FB_CT65550
   This is the frame buffer device driver for the Chips & Technologies
@@ -1612,36 +1634,26 @@
   This is the frame buffer device driver for the Topcat graphics
   hardware found in HP300 workstations.
 
-VGA chipset support (text only)
-CONFIG_FB_VGA
-  This is the frame buffer device driver for generic VGA chips. This
-  driver works only in text mode and is deprecated; it is preferable
-  to say Y to "VGA text console" instead. For a graphical frame buffer
-  device driver that works for VGA cards, say Y to "VESA VGA graphics
-  console" below.
-
-TGA frame buffer support' 
+TGA frame buffer support
 CONFIG_FB_TGA
   This is the frame buffer device driver for generic TGA graphic cards.
   Say Y if you have one of those.
 
 VESA VGA graphics console
 CONFIG_FB_VESA
-  This is the frame buffer device driver for generic VESA graphic
-  cards. You will get a boot time penguin logo at no additional cost.
-  Please read Documentation/fb/vesafb.txt. If unsure, say Y.
+  This is the frame buffer device driver for generic VESA graphic cards.
+  Please read Documentation/fb/vesafb.txt.
 
-MDA dual-headed support
-CONFIG_FB_MDA
+MDA text console (dual-headed)
+CONFIG_MDA_CONSOLE
   Say Y here if you have an old MDA or monochrome Hercules graphics
-  adapter in your system acting as a second head ( = video card). You
-  will then be able to use two monitors with your Linux system. Do not
-  say Y here if your MDA card is the primary card in your system; the
-  normal VGA driver will handle it.
+  adapter in your system acting as a second head ( = video card).  Do 
+  not enable this driver if your MDA card is the primary card in your
+  system; the normal VGA driver will handle it.
   
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
-  The module will be called mdafb.o.  If you want to compile it as
+  The module will be called mdacon.o.  If you want to compile it as
   a module, say M here and read Documentation/modules.txt.
   
   If unsure, say N.
@@ -1674,14 +1686,13 @@
 
 Virtual Frame Buffer support (ONLY FOR TESTING!)
 CONFIG_FB_VIRTUAL
-  This is a `virtual' frame buffer device. It operates on a chunk of
-  unswapable kernel memory instead of on the memory of a graphics
-  board. This means you cannot see any output sent to this frame
-  buffer device, while it does consume precious memory. The main use
-  of this frame buffer device is testing and debugging the frame
-  buffer subsystem. Do NOT enable it for normal systems! To protect
-  the innocent, it has to be enabled explicitly at boot time using the
-  kernel option `video=vfb:'.
+  This is a `virtual' frame buffer device.  It operates on a chunk of
+  unswapable kernel memory instead of on the memory of a graphics board.
+  This means you cannot see any output sent to this frame buffer device,
+  while it does consume precious memory.  The main use of this frame
+  buffer device is testing and debugging the frame buffer subsystem. Do
+  NOT enable it for normal systems! To protect the innocent, it has to
+  be enabled explicitly on boot time using the kernel option `video=vfb:'.
 
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
@@ -1698,12 +1709,12 @@
   drivers. Note that they are used for text console output only; they are
   NOT needed for graphical applications.
 
-  If you say N here, the needed low level drivers are automatically
-  enabled, depending on what frame buffer devices you selected above.
-  This is recommended for most users.
+  If you do not enable this option, the needed low level drivers are
+  automatically enabled, depending on what frame buffer devices you
+  selected. This is recommended for most users.
 
-  If you say Y here, you have more fine-grained control over which low
-  level drivers are enabled. You can e.g. leave out low level drivers
+  If you enable this option, you have more fine-grained control over which
+  low level drivers are enabled. You can e.g. leave out low level drivers
   for color depths you do not intend to use for text consoles.
 
   Low level frame buffer console drivers can be modules ( = code which
@@ -1777,13 +1788,13 @@
 Mac variable bpp packed pixels support
 CONFIG_FBCON_MAC
   This is the low level frame buffer console driver for 1/2/4/8/16/32
-  bits per pixel packed pixels on Mac. It supports variable font widths
+  bits per pixel packed pixels on Mac. It supports variable fontwidths
   for low resolution screens.
   
 VGA characters/attributes support
 CONFIG_FBCON_VGA
-  This is the low level frame buffer console driver for VGA text mode;
-  it is used if you said Y to "VGA chipset support (text only)" above.
+  This is the low level frame buffer console driver for VGA text mode, as
+  used by vgafb.
 
 Parallel-port support
 CONFIG_PARPORT
@@ -2236,6 +2247,9 @@
   via FTP (user: anonymous) from
   ftp://ftp.netis.com/pub/members/rlynch/
 
+  For 2.1 kernels, you will need "ipmasqadm" tool from
+  http://juanjox.home.ml.org
+
   The ipautofw code is still under development and so is currently
   marked EXPERIMENTAL. If you want to try it, say Y.
 
@@ -2244,6 +2258,22 @@
   The module will be called ip_masq_autofw.o. If you want to compile
   it as a module, say M here and read Documentation/modules.txt.
 
+IP: masquerading special modules support
+CONFIG_IP_MASQUERADE_MOD
+  This provides support for special modules that can modify rewriting
+  rules to achieve, for example, input port forwarding.
+  Beware that this feature adds a little overhead in the input packet
+  processing chain.
+
+  You will need user space program "ipmasqadm" to use these
+  additional modules, you can download it from 
+  http://juanjox.home.ml.org/
+
+  All this additional code is still under development and so is currently
+  marked EXPERIMENTAL. 
+  
+  If you want to try, for example, PORT FORWARDING, say Y.
+
 IP: ipportfw masquerade support
 CONFIG_IP_MASQUERADE_IPPORTFW
   Port Forwarding is an addition to IP Masquerading written by Steven
@@ -2261,7 +2291,10 @@
   http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to
   browse the WWW, you need to have access to a machine on the Internet
   that has a program like lynx or netscape). You will need the user
-  space program ipportfw which can be downloaded from
+  space program "ipmasqadm" which can be downloaded from
+  http://juanjox.home.ml.org/
+
+  For general info, please see
   ftp://ftp.compsoc.net/users/steve/ipportfw/linux21/
 
   The portfw code is still under development and so is currently
@@ -2272,6 +2305,20 @@
   The module will be called ip_masq_portfw.o. If you want to compile
   it as a module, say M here and read Documentation/modules.txt.
 
+IP: ipmarkfw masquerade support
+CONFIG_IP_MASQUERADE_IPMARKFW
+  This provides functionally equivalent to port forwarding, the difference
+  is that Mark Forwarding uses "firewalling mark" to select which packets
+  must forward (see ipchains(8), "-m" argument).
+
+  The markfw code is still under development and so is currently
+  marked EXPERIMENTAL. If you want to try it, say Y.
+
+  This code 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 ip_masq_markfw.o. If you want to compile
+  it as a module, say M here and read Documentation/modules.txt.
+
 IP: always defragment 
 CONFIG_IP_ALWAYS_DEFRAG
   This option means that all incoming fragments (= parts of IP packets
@@ -8941,6 +8988,15 @@
   and CD32.  If you intend to run Linux on any of these systems, say Y;
   otherwise say N.
 
+Amiga Cybervision support
+CONFIG_FB_CYBER
+  This enables support for the Cybervision 64 graphics card from Phase5.
+  Please note that its use is not all that intuitive (i.e. if you have
+  any questions, be sure to ask!).  Say N unless you have a Cybervision
+  64 or plan to get one before you next recompile the kernel.
+  Please note that this driver DOES NOT support the Cybervision 64 3D
+  card at present, as they use incompatible video chips.
+
 Amiga GSP (TMS340x0) support
 CONFIG_AMIGA_GSP
   Include support for Amiga graphics cards that use the Texas
@@ -9306,17 +9362,6 @@
   This option adds a device-tree directory under /proc which contains
   an image of the device tree that the kernel copies from Open
   Firmware.  If unsure, say Y here.
-
-Support for ATI Mach64 display cards
-CONFIG_ATY_VIDEO
-  Several of the newer Power Macintoshes and clones have a video
-  display interface based on the ATI Mach64 chipset.  Say N here if
-  you are sure you don't need this functionality, otherwise Y.
-
-Support for IMS Twin Turbo display card
-CONFIG_IMSTT_VIDEO
-  Some Power Macintosh clones have an IMS Twin Turbo video display
-  interface.  Say Y to include support for this.
 
 MESH (Power Mac internal SCSI) support
 CONFIG_SCSI_MESH