patch-2.4.0-test5 linux/Documentation/Configure.help

Next file: linux/Documentation/DocBook/Makefile
Previous file: linux/Documentation/Changes
Back to the patch index
Back to the overall index
Lines: 431
Date: Thu Jul 27 16:40:57 2000
Orig file: v2.4.0-test4/linux/Documentation/Configure.help
Orig date: Fri Jul 14 12:12:04 2000

diff -u --recursive --new-file v2.4.0-test4/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -898,7 +898,7 @@
 CONFIG_BLK_DEV_PDC202XX
   Promise Ultra33 or PDC20246
   Promise Ultra66 or PDC20262
-  Promise Ultra100 or PDC20267
+  Promise Ultra100 or PDC20265/PDC20267
 
   This driver adds up to 4 more EIDE devices sharing a single
   interrupt. This add-on card is a bootable PCI UDMA controller. Since
@@ -918,11 +918,11 @@
 
 Special UDMA Feature (EXPERIMENTAL)
 CONFIG_PDC202XX_BURST
-  For PDC20246, PDC20262 and PDC20267 Ultra DMA chipsets. Designed
-  originally for PDC20246/Ultra33 that has BIOS setup failures when
-  using 3 or more cards.
+  For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
+  Designed originally for PDC20246/Ultra33 that has BIOS setup
+  failures when using 3 or more cards.
 
-  Unknown for PDC20267 Ultra DMA 100.
+  Unknown for PDC20265/PDC20267 Ultra DMA 100.
 
   Please read the comments at the top of drivers/ide/pdc202xx.c
 
@@ -2531,12 +2531,20 @@
 
 Support for hot-pluggable devices
 CONFIG_HOTPLUG
-  Say Y here if you want to attach devices to your computer that can
-  be attached and detached while the system is running. The most
-  prominent example of this are PCMCIA- or PC-cards, credit-card size
-  devices such as network cards, modems or hard drives which are
+  Say Y here if you want to plug devices into your computer while
+  the system is running, and be able to use them quickly.  In many
+  cases, the devices can likewise be unplugged at any time too.
+
+  One well known example of this is PCMCIA- or PC-cards, credit-card
+  size devices such as network cards, modems or hard drives which are
   plugged into slots found on all modern laptop computers.
 
+  Another example, used on modern desktops as well as laptops, is USB.
+  Enable HOTPLUG with USB and KMOD, and your kernel will automatically
+  call out to a user mode "policy agent" to load modules and set up
+  software needed to use USB devices you plug in.  Get agent software
+  (at http://www.linux-usb.org/policy.html) and install it.
+
 PCMCIA/Cardbus support
 CONFIG_PCMCIA
   Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
@@ -6294,6 +6302,66 @@
 
   Generally, saying N is fine.
 
+Parallel port SCSI device support
+CONFIG_PPSCSI
+  There are many external CD-ROM and disk devices that connect through
+  your computer's parallel port. Lots of them are actually SCSI
+  devices using a parallel port SCSI adapter. This option enables the
+  ppSCSI subsystem which contains drivers for many of these external
+  drives. You may also want to look at CONFIG_PARIDE (Parallel port
+  IDE device support).
+
+  If you built ppSCSI support into your kernel, you may still build
+  the individual protocol modules and high-level drivers as loadable
+  modules. If you build this support as a module, it will be called
+  ppscsi.o.
+
+  To use the ppSCSI support, you must say Y or M here and also to at
+  least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
+  adapter", "Shining ScarSCI adapter" etc.).
+
+Adaptec APA-348 adapter
+CONFIG_PPSCSI_T348
+  This option enables support for the APA-348 adapter from Adaptec
+  (also known as Trantor T348).  If you build this as a module it will
+  be called t348.o.
+
+Adaptec APA-358 adapter
+CONFIG_PPSCSI_T358
+  This option enables support for the APA-358 adapter from Adaptec
+  (also known as Trantor T358).  If you build this as a module it will
+  be called t358.o.
+
+Iomega VPI0 adapter
+CONFIG_PPSCSI_VPI0
+  This option enables support for the Iomega VPI0 adapter found in the
+  original ZIP-100 drives and the Jaz Traveller.  If you build this as
+  a module it will be called vpi0.o.
+
+OnSpec 90c26 adapter
+CONFIG_PPSCSI_ONSCSI
+  This option enables support for the OnSpec 90c26 in its SCSI adapter
+  mode.  If you build this as a module it will be called onscsi.o.
+
+Shining SparSCI adapter
+CONFIG_PPSCSI_SPARCSI
+  This option enables support for the WBS-11A parallel port SCSI
+  adapter.  This adapter has been marketed by LinkSys as the
+  "ParaSCSI+" and by Shining Technologies as the "SparCSI".  If you
+  build this as a module it will be called sparcsi.o.
+
+Shuttle EPSA-2 adapter
+CONFIG_PPSCSI_EPSA2
+  This option enables support for the Shuttle Technologies EPSA2
+  parallel port SCSI adapter.  EPAS2 is a predecessor to the EPST.  If
+  you build this as a module it will be called epsa2.o.
+
+Shuttle EPST adapter
+CONFIG_PPSCSI_EPST
+  This option enables support for the Shuttle Technologies EPST
+  parallel port SCSI adapter.  If you build this as a module is will
+  be called epst.o.
+
 SCSI Debug host simulator. (EXPERIMENTAL)
 CONFIG_SCSI_DEBUG
   This is a host adapter simulator that can be programmed to simulate
@@ -9991,7 +10059,7 @@
   
   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 usb-serial.o. If you want to compile it 
+  The module will be called usbserial.o. If you want to compile it 
   as a module, say M here and read Documentation/modules.txt.
 
 USB Generic Serial Driver
@@ -10007,12 +10075,22 @@
   Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
   USB to serial converter device.
 
+  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 whiteheat.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
 USB Handspring Visor Driver
 CONFIG_USB_SERIAL_VISOR
   Say Y here if you want to connect to your HandSpring Visor through
   its USB docking station. See http://usbvisor.sourceforge.net for
   more information on using this driver.
 
+  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 visor.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
 USB FTDI Single Port Serial Driver
 CONFIG_USB_SERIAL_FTDI_SIO
   Say Y here if you want to use a FTDI SIO single port USB to serial
@@ -10021,12 +10099,22 @@
   See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
   information on this driver and the device.
 
+  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 ftdi_sio.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
 USB Keyspan PDA Single Port Serial Driver
 CONFIG_USB_SERIAL_KEYSPAN_PDA
   Say Y here if you want to use a Keyspan PDA single port USB to
   serial converter device.  This driver makes use of firmware
   developed from scratch by Brian Warner.
 
+  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 keyspan_pda.o. If you want to compile it 
+  as a module, say M here and read Documentation/modules.txt.
+
 USB Keyspan USA-xxx Serial Driver
 CONFIG_USB_SERIAL_KEYSPAN
   Say Y here if you want to use Keyspan USB to serial converter
@@ -10037,6 +10125,11 @@
   See http://www.linuxcare.com.au/hugh/keyspan.html for 
   more information.
  
+  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 keyspan.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
 USB Keyspan USA-28 Firmware
 CONFIG_USB_SERIAL_KEYSPAN_USA28
   Say Y here to include firmware for the USA-28 converter.
@@ -10061,12 +10154,27 @@
 CONFIG_USB_SERIAL_OMNINET
   Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
 
+  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 omninet.o. If you want to compile it as a 
+  module, say M here and read Documentation/modules.txt.
+
 USB Digi International AccelePort USB Serial Driver
 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
   Say Y here if you want to use a Digi AccelePort USB 4 device,
   a 4 port USB serial converter.  The Digi Acceleport USB 2 and
   8 are not yet supported by this driver.
 
+  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 digi_acceleport.o. If you want to compile 
+  it as a module, say M here and read Documentation/modules.txt.
+
+USB Serial Converter verbose debug
+CONFIG_USB_SERIAL_DEBUG
+  Say Y here if you want verbose debug messages from the USB Serial
+  Converter. 
+
 USB Printer support
 CONFIG_USB_PRINTER
   Say Y here if you want to connect a USB printer to your computer's
@@ -10077,11 +10185,6 @@
   The module will be called printer.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
-USB Serial Converter verbose debug
-CONFIG_USB_SERIAL_DEBUG
-  Say Y here if you want verbose debug messages from the USB Serial
-  Converter. 
-
 USB IBM (Xirlink) C-It Camera support
 CONFIG_USB_IBMCAM
   Say Y here if you want to connect a IBM "C-It" camera, also known as
@@ -10301,6 +10404,18 @@
   http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
   This driver can be compiled as a module.
 
+USB Bluetooth support
+CONFIG_USB_BLUETOOTH
+  Say Y here if you want to connect a USB Bluetooth device to your
+  computer's USB port. You will need the Bluetooth stack (available
+  at http://developer.axis.com/software/index.shtml) to fully use
+  the device.
+
+  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 bluetooth.o. If you want to compile it as 
+  a module, say M here and read Documentation/modules.txt.
+  
 Minix fs support
 CONFIG_MINIX_FS
   Minix is a simple operating system used in many classes about OS's.
@@ -11297,6 +11412,20 @@
   To use the new attributes, it is recommended to use the flags
   '-f 600 -d 755' on the ncpmount command line.
 
+nls default codepage
+CONFIG_NLS_DEFAULT
+  The default NLS used when mounting filesystem. Currently, the valid
+  values are:
+  big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
+  cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
+  cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
+  iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
+  iso8859-14, iso8859-15, koi8-r, sjis
+  If you specify a wrong value, it will use the built-in NLS; compatible
+  with iso8859-1.
+
+  If unsure, specify it as "iso8859-1".
+
 nls codepage 437
 CONFIG_NLS_CODEPAGE_437
   The Microsoft FAT file system family can deal with filenames in
@@ -11472,6 +11601,50 @@
   only, not to the file contents. You can include several codepages;
   say Y here if you want to include the DOS codepage for Thai.
 
+nls codepage 932
+CONFIG_NLS_CODEPAGE_932
+  The Microsoft fat filesystem family can deal with filenames in
+  native language character sets. These character sets are stored in
+  so-called DOS codepages. You need to include the appropriate
+  codepage if you want to be able to read/write these filenames on
+  DOS/Windows partitions correctly. This does apply to the filenames
+  only, not to the file contents. You can include several codepages;
+  say Y here if you want to include the DOS codepage for Shift-JIS
+  or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
+  NLS Default value during kernel configuration , instead of 'cp932'
+
+nls codepage 936
+CONFIG_NLS_CODEPAGE_936
+  The Microsoft fat filesystem family can deal with filenames in
+  native language character sets. These character sets are stored in
+  so-called DOS codepages. You need to include the appropriate
+  codepage if you want to be able to read/write these filenames on
+  DOS/Windows partitions correctly. This does apply to the filenames
+  only, not to the file contents. You can include several codepages;
+  say Y here if you want to include the DOS codepage for Simplified
+  Chinese(GBK).
+
+nls codepage 949
+CONFIG_NLS_CODEPAGE_949
+  The Microsoft fat filesystem family can deal with filenames in
+  native language character sets. These character sets are stored in
+  so-called DOS codepages. You need to include the appropriate
+  codepage if you want to be able to read/write these filenames on
+  DOS/Windows partitions correctly. This does apply to the filenames
+  only, not to the file contents. You can include several codepages;
+  say Y here if you want to include the DOS codepage for UHC.
+
+nls codepage 950
+CONFIG_NLS_CODEPAGE_950
+  The Microsoft fat filesystem family can deal with filenames in
+  native language character sets. These character sets are stored in
+  so-called DOS codepages. You need to include the appropriate
+  codepage if you want to be able to read/write these filenames on
+  DOS/Windows partitions correctly. This does apply to the filenames
+  only, not to the file contents. You can include several codepages;
+  say Y here if you want to include the DOS codepage for Traditional
+  Chinese(Big5).
+
 nls iso8859-1
 CONFIG_NLS_ISO8859_1
   If you want to display filenames with native language characters
@@ -12054,6 +12227,9 @@
   it as a module, say M here and read Documentation/modules.txt. The
   module will be called i2c-philips-par.o.
 
+  Note that if you want support for different parallel port devices,
+  life will be much easier if you compile them all as modules.
+
 ELV adapter
 CONFIG_I2C_ELV
   This supports parallel-port I2C adapters called ELV. Say Y if you
@@ -12550,21 +12726,40 @@
 Direct Rendering Manager (XFree86 DRI support)
 CONFIG_DRM
   Kernel-level support for the Direct Rendering Infrastructure (DRI)
-  introduced in XFree86 4.x. If you say Y here, you need to select 
+  introduced in XFree86 4.0. If you say Y here, you need to select
   the module that's right for your graphics card from the list below.
-  These modules provide support for synchronization, security, and 
-  DMA transfers. Please read drivers/char/drm/README.drm for more 
-  details. 
+  These modules provide support for synchronization, security, and
+  DMA transfers. Please see http://dri.sourceforge.net for more
+  details.  You should also select and configure AGP
+  (/dev/agpgart) support.
 
-3dfx Banshee/Voodoo3
+3dfx Banshee/Voodoo3+
 CONFIG_DRM_TDFX
-  Choose M here if you have a 3dfx Banshee/Voodoo3 graphics card.
-  The module will be called tdfx.o.
+  Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
+  graphics card.  If M is selected, the module will be called tdfx.o.
 
-3dlabs GMX 2000 Direct Rendering Driver (XFree86 DRI support)
+3dlabs GMX 2000
 CONFIG_DRM_GAMMA
-  Choose M here if you have a 3dlabs GMX 2000 graphics card.
-  The module will be called gamma.o.
+  Choose this option if you have a 3dlabs GMX 2000 graphics card.
+  If M is selected, the module will be called gamma.o.
+
+ATI Rage 128
+CONFIG_DRM_R128
+  Choose this option if you have an ATI Rage 128 graphics card.  If M
+  is selected, the module will be called r128.o.  AGP support for
+  this card is strongly suggested (unless you have a PCI version).
+
+Intel I810
+CONFIG_DRM_I810
+  Choose this option if you have an Intel I810 graphics card.  If M is
+  selected, the module will be called i810.o.  AGP support is required
+  for this driver to work.
+
+Matrox g200/g400
+CONFIG_DRM_MGA
+  Choose this option if you have a Matrox g200 or g400 graphics card.  If M
+  is selected, the module will be called mga.o.  AGP support is required
+  for this driver to work.
 
 MTRR control and configuration
 CONFIG_MTRR
@@ -15707,14 +15902,50 @@
   Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
   Microprocessor Development Board (also known as the Assabet).
 
-Include support for the Compaq iPAQ 3600
+Include support for Neponset
+CONFIG_ASSABET_NEPONSET
+  Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
+  Microprocessor Development Board (Assabet)  with the SA-1111
+  Development Board (Nepon).
+
+Include support for the Compaq iPAQ H3600 (Bitsy)
 CONFIG_SA1100_BITSY
-  Say Y here if you intend to run this kernel on the Compaq iPAQ 3600
-  handheld computer.  Information about this machine and the Linux
-  port to this machine can be found at:
+  Say Y here if you intend to run this kernel on the Compaq iPAQ 
+  H3600 handheld computer.  Information about this machine and the
+  Linux port to this machine can be found at:
 
   http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
   http://www.compaq.com/products/handhelds/pocketpc/
+
+Include support for Brutus
+CONFIG_SA1100_BRUTUS
+  Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
+  Microprocessor Development Board (also known as the Brutus).
+
+Include support for LART
+CONFIG_SA1100_LART
+  Say Y here if you are using the Linux Advanced Radio Terminal
+  (also known as the LART).  See http://www.lart.tudelft.nl/ for
+  information on the LART.
+
+Include support for ThinClient
+CONFIG_SA1100_THINCLIENT
+  Say Y here if you are using an Applied Data Systems Intel(R)
+  StrongARM(R) SA-1100 based Thin Client SBC.  See
+  http://www.flatpanels.com/ for information on this system.
+
+Include support for GraphicsClient
+CONFIG_SA1100_GRAPHICSCLIENT
+  Say Y here if you are using an Applied Data Systems Intel(R)
+  StrongARM(R) SA-1100 based Graphics Client SBC.  See
+  http://www.flatpanels.com/ for information on this system.
+
+Include support for Victor
+CONFIG_SA1100_VICTOR
+  Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
+  SA-1100 based Victor Digital Talking Book Reader.  See
+  http://www.visuaide.com/pagevictor.en.html for information on
+  this system.
 
 Math emulation
 CONFIG_NWFPE
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen (who was at: slshen@lbl.gov)