patch-2.3.99-pre3 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: 661
- Date:
Thu Mar 23 08:38:57 2000
- Orig file:
v2.3.99-pre2/linux/Documentation/Configure.help
- Orig date:
Sun Mar 19 18:35:30 2000
diff -u --recursive --new-file v2.3.99-pre2/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -186,10 +186,22 @@
CONFIG_NOHIGHMEM
If you are compiling a kernel which will never run on a machine
with more than 1 Gigabyte total physical RAM, answer "off"
- here (default choice).
+ here (default choice). This will result in the old "3GB/1GB"
+ virtual/physical memory split. 3BG are mapped so as each processus
+ sees a 3GB virtual memory space.
+ The remaining part of the 4G virtual memory space is used by the
+ kernel to 'permanently map' as much physical memory as possible.
+ Certain types of applications perform better if there is more
+ 'permanently mapped' kernel memory.
+ Certain types of applications (eg. database servers) perform
+ better if they have as much virtual memory per process as possible.
Linux can use up to 64 Gigabytes of physical memory on x86 systems.
- High memory is all the physical RAM that could not be directly
+ However 32-bit x86 processors have only 4 Gigabytes of virtual memory
+ space.
+
+ Any potentially remaining part of physical memory is called
+ 'high memory' that is all the physical RAM that could not be directly
mapped by the kernel - ie. 3GB if there is 4GB RAM in the system,
7GB if there is 8GB RAM in the system.
@@ -202,6 +214,13 @@
processors (PPro and better). NOTE: The "64GB" kernel will not
boot CPUs that not support PAE!
+ The actual amount of total physical memory will either be
+ autodetected or can be forced by using a kernel command line option
+ such as "mem=256M". (Try "man bootparam" or see the documentation of
+ your boot loader (lilo or loadlin) about how to pass options to the
+ kernel at boot time. The lilo procedure is also explained in the
+ SCSI-HOWTO, available from http://www.linuxdoc.org/docs.html#howto .)
+
Normal PC floppy disk support
CONFIG_BLK_DEV_FD
If you want to use the floppy disk drive(s) of your PC under Linux,
@@ -372,7 +391,7 @@
Useful information about large (>540 MB) IDE disks, multiple
interfaces, what to do if ATA/IDE devices are not automatically
detected, sound card ATA/IDE ports, module support, and other topics, is
- contained in Documentation/ata-ide.txt. For detailed information about
+ contained in Documentation/ide.txt. For detailed information about
hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
available from http://www.linuxdoc.org/docs.html#howto .
@@ -494,7 +513,7 @@
along with other IDE devices, as "hdb" or "hdc", or something
similar, and will be mapped to a character device such as "ht0"
(check the boot messages with dmesg). Be sure to consult the
- drivers/block/ide-tape.c and Documentation/ide.txt files for usage
+ drivers/ide/ide-tape.c and Documentation/ide.txt files for usage
information.
If you want to compile the driver as a module ( = code which can be
@@ -627,7 +646,7 @@
the latest version of the hdparm utility from
ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
- Read the comments at the beginning of drivers/block/ide-dma.c and the
+ Read the comments at the beginning of drivers/ide/ide-dma.c and the
file Documentation/ide.txt for more information.
It is safe to say Y to this question.
@@ -707,12 +726,12 @@
should say Y here, and preferably also to "Use DMA by default when
available".
- Please read the comments at the top of drivers/block/aec6210.c
+ Please read the comments at the top of drivers/ide/aec6210.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
AEC6210 Tuning support (WIP)
CONFIG_AEC6210_TUNING
- Please read the comments at the top of drivers/block/aec6210.c
+ Please read the comments at the top of drivers/ide/aec6210.c
If unsure, say N.
ALI M15x3 chipset support
@@ -721,16 +740,28 @@
1535, 1535D onboard chipsets. It also tests for Simplex mode and
enables normal dual channel support.
- Please read the comments at the top of drivers/block/alim15x3.c
+ Please read the comments at the top of drivers/ide/alim15x3.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
If unsure, say N.
+ALI M15x3 WDC support (DANGEROUS)
+CONFIG_WDC_ALI15X3
+ This allows for UltraDMA support for WDC drives that ignore CRC checking.
+ You are a fool for enabling this option, but there have been requests.
+ DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORUPTION, IF YOU ENABLE THIS!
+ No one will listen, just laugh for ignoring this SERIOUS WARNING.
+
+ Using this option can allow WDC drives to run at ATA-4/5 transfer rates with
+ only an ATA-2 support structure.
+
+ SAY NO!
+
AMD7409 chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_AMD7409
This driver ensures (U)DMA support for AMD756 Viper chipset.
- Please read the comments at the top of drivers/block/amd7409.c
+ Please read the comments at the top of drivers/ide/amd7409.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
If unsure, say N.
@@ -776,7 +807,7 @@
HPT34X AUTODMA support (WIP)
CONFIG_HPT34X_AUTODMA
This is a dangerous thing to attempt currently!
- Please read the comments at the top of drivers/block/hpt34x.c
+ Please read the comments at the top of drivers/ide/hpt34x.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
If unsure, say N.
@@ -795,7 +826,7 @@
the ide-probe at boot. It is reported to support DVD II drives, by the
manufacturer.
- Please read the comments at the top of drivers/block/hpt366.c
+ Please read the comments at the top of drivers/ide/hpt366.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
HPT366 Fast Interrupts (WIP)
@@ -813,12 +844,12 @@
This driver adds detection and support for the NS87415 chip
(used in SPARC64, among others).
- Please read the comments at the top of drivers/block/ns87415.c.
+ Please read the comments at the top of drivers/ide/ns87415.c.
OPTi 82C621 enhanced support (EXPERIMENTAL)
CONFIG_BLK_DEV_OPTI621
This is a driver for the OPTi 82C621 EIDE controller.
- Please read the comments at the top of drivers/block/opti621.c.
+ Please read the comments at the top of drivers/ide/opti621.c.
Intel PIIXn chipsets support
CONFIG_BLK_DEV_PIIX
@@ -827,7 +858,7 @@
PIO 0-4 mode settings, this allows dynamic tuning of the chipset
via the standard end-user tool 'hdparm'.
- Please read the comments at the top of drivers/block/piix.c
+ Please read the comments at the top of drivers/ide/piix.c
Should also include "PIIXn Tuning support" CONFIG_PIIX_TUNING
If unsure, say Y.
@@ -866,7 +897,7 @@
1.11 or newer required.
If you say Y here, then say Y to "Use DMA by default when available" as well.
- Please read the comments at the top of drivers/block/pdc202xx.c
+ Please read the comments at the top of drivers/ide/pdc202xx.c
If unsure, say N.
@@ -876,7 +907,7 @@
for PDC20246/Ultra33 that has BIOS setup failures when using 3 or
more cards.
- Please read the comments at the top of drivers/block/pdc202xx.c
+ Please read the comments at the top of drivers/ide/pdc202xx.c
If unsure, say N.
@@ -898,7 +929,7 @@
This driver adds support for bus master DMA transfers
using the Tekram TRM290 PCI IDE chip. Volunteers are
needed for further tweaking and development.
- Please read the comments at the top of drivers/block/trm290.c.
+ Please read the comments at the top of drivers/ide/trm290.c.
VIA82CXXX chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_VIA82CXXX
@@ -909,7 +940,7 @@
If no command line is provided, it will try to set fifo configuration
at its best. It will allow you to get a proc/ide/via display
(while running a "cat") provided you enabled "proc" support.
- Please read the comments at the top of drivers/block/via82cxxx.c
+ Please read the comments at the top of drivers/ide/via82cxxx.c
If you say Y here, then say Y to "Use DMA by default when available" as well.
@@ -943,14 +974,14 @@
boot parameter. It enables support for the secondary IDE interface
of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
I/O speeds to be set as well. See the files Documentation/ide.txt
- and drivers/block/ali14xx.c for more info.
+ and drivers/ide/ali14xx.c for more info.
DTC-2278 support
CONFIG_BLK_DEV_DTC2278
This driver is enabled at runtime using the "ide0=dtc2278" kernel
boot parameter. It enables support for the secondary IDE interface
of the DTC-2278 card, and permits faster I/O speeds to be set as
- well. See the Documentation/ide.txt and drivers/block/dtc2278.c
+ well. See the Documentation/ide.txt and drivers/ide/dtc2278.c
files for more info.
Holtek HT6560B support
@@ -958,7 +989,7 @@
This driver is enabled at runtime using the "ide0=ht6560b" kernel
boot parameter. It enables support for the secondary IDE interface
of the Holtek card, and permits faster I/O speeds to be set as well.
- See the Documentation/ide.txt and drivers/block/ht6560b.c files for
+ See the Documentation/ide.txt and drivers/ide/ht6560b.c files for
more info.
PROMISE DC4030 support (EXPERIMENTAL)
@@ -969,13 +1000,13 @@
attached to the secondary interface. CDROM and TAPE devices are not
supported yet. This driver is enabled at runtime using the
"ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
- and drivers/block/pdc4030.c files for more info.
+ and drivers/ide/pdc4030.c files for more info.
QDI QD6580 support
CONFIG_BLK_DEV_QD6580
This driver is enabled at runtime using the "ide0=qd6580" kernel
boot parameter. It permits faster I/O speeds to be set. See the
- files Documentation/ide.txt and drivers/block/qd6580.c for more
+ files Documentation/ide.txt and drivers/ide/qd6580.c for more
info.
UMC 8672 support
@@ -983,7 +1014,7 @@
This driver is enabled at runtime using the "ide0=umc8672" kernel
boot parameter. It enables support for the secondary IDE interface
of the UMC-8672, and permits faster I/O speeds to be set as well.
- See the files Documentation/ide.txt and drivers/block/umc8672.c for
+ See the files Documentation/ide.txt and drivers/ide/umc8672.c for
more info.
Amiga builtin Gayle IDE interface support
@@ -2135,6 +2166,14 @@
Say Y here to enable support in the dumb serial driver to support
the HUB6 card.
+Support for hot-pluggable devices
+CONFIG_HOTPLUG
+ Say Y here to enable support for hot plugin of certain hardware such as
+ PCMCIA cards and the like.
+
+ At this moment, few drivers support it, but as they get converted to use the
+ new ressource allocator/manager, their number will increase.
+
PCMCIA serial device support
CONFIG_PCMCIA_SERIAL_CS
Say Y here to enable support for 16-bit PCMCIA serial devices,
@@ -2728,6 +2767,27 @@
CONFIG_FB_S3TRIO
If you have a S3 Trio say Y. Say N for S3 Virge.
+3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
+CONFIG_FB_3DFX
+ This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 chips.
+ Say Y if you have such a graphics board.
+
+ The 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 tdfxfb.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
+
+nVidia Riva support (EXPERIMENTAL)
+CONFIG_FB_RIVA
+ This driver supports graphics boards with the nVidia Riva (aka TNTx)
+ chips.
+ Say Y if you have such a graphics board.
+
+ The 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 rivafb.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
+
ATI Mach64 display support (EXPERIMENTAL)
CONFIG_FB_ATY
This driver supports graphics boards with the ATI Mach64 chips.
@@ -2808,19 +2868,36 @@
running kernel whenever you want), say M here and read
Documentation/modules.txt. The module will be called vga16fb.o.
+Select other compiled-in fonts
+CONFIG_FBCON_FONTS
+ Say Y here if you would like to use fonts other than the default your frame
+ buffer console usually use.
+
+ Note that the answer to this question won't directly affect the kernel:
+ saying N will just cause this configure script to skip all the questions
+ about foreign fonts.
+
+ If unsure, say N (the default choices are safe).
+
VGA 8x16 font
CONFIG_FONT_8x16
This is the "high resolution" font for the VGA frame buffer (the one
- provided by the text console 80x25 mode.
+ provided by the VGA text console 80x25 mode.
+
+ If unsure, say Y.
Support only 8 pixels wide fonts
CONFIG_FBCON_FONTWIDTH8_ONLY
Answer Y here will make the kernel provide only the 8x8 fonts (these
are the less readable).
+ If unsure, say N.
+
Sparc console 8x16 font
CONFIG_FONT_SUN8x16
- This is the high resolution console font for Sun machines. Say Y.
+ This is the high resolution console font for Sun machines.
+
+ Say Y.
Sparc console 12x22 font (not supported by all drivers)
CONFIG_FONT_SUN12x22
@@ -2834,6 +2911,7 @@
provided by the text console 80x50 (and higher) modes.
Note this is a poor quality font. The VGA 8x16 font is quite a lot
more readable.
+
Given the resolution provided by the frame buffer device, answer N
here is safe.
@@ -2844,13 +2922,25 @@
includes a server that supports the frame buffer device directly
(XF68_FBDev).
+HGA monochrome support (EXPERIMENTAL)
+Hercules mono graphics console (EXPERIMENTAL)
+CONFIG_FBCON_HGA
+ Say Y here if you have a Hercules mono graphics card.
+
+ 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 hgafb.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt.
+
+ As this card technology is 15 years old, most people will answer N here.
+
Matrox unified accelerated driver (EXPERIMENTAL)
CONFIG_FB_MATROX
Say Y here if you have Matrox Millennium, Matrox Millennium II,
Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
- Mystique G200, Matrox Millennium G200 or Matrox Marvel G200 video
- card in your box. At this time, support for the G100, Mystique G200
- and Marvel G200 is untested.
+ Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video or
+ Matrox G400 card in your box. At this time, support for the G100,
+ Mystique G200 and Marvel G200 is untested.
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
@@ -3784,6 +3874,12 @@
See Documentation/networking/decnet.txt for more information.
+Appletalk interfaces support
+CONFIG_APPLETALK
+ AppleTalk is the way Apple computers speak to each other on a
+ network. If your Linux box is connected to such a network and you
+ want to join the conversation, say Y.
+
AppleTalk DDP
CONFIG_ATALK
AppleTalk is the way Apple computers speak to each other on a
@@ -6069,7 +6165,7 @@
with a similar Bonding Linux driver, a Cisco 5500 switch or a
SunTrunking SunSoft driver.
- This is similar to the EQL driver, but it merge etherner segments instead
+ This is similar to the EQL driver, but it merge ethernet segments instead
of serial lines.
If you want to compile this as a module ( = code which can be
@@ -6718,6 +6814,17 @@
Say Y here if you have a native Econet network card installed in
your computer.
+Wan interfaces support
+CONFIG_WAN
+ Wide Area Networks (WANs), such as X.25, frame relay and leased
+ lines, are used to interconnect Local Area Networks (LANs) over vast
+ distances with data transfer rates significantly higher than those
+ achievable with commonly used asynchronous modem connections.
+
+ Say Y here if you want to use such interconnections.
+
+ It is safe to say N. Most people won't need it.
+
WAN Router
CONFIG_WAN_ROUTER
Wide Area Networks (WANs), such as X.25, frame relay and leased
@@ -6743,6 +6850,18 @@
If unsure, say N.
+WAN router drivers
+CONFIG_WAN_ROUTER_DRIVERS
+ Wide Area Networks (WANs), such as X.25, frame relay and leased
+ lines, are used to interconnect Local Area Networks (LANs) over vast
+ distances with data transfer rates significantly higher than those
+ achievable with commonly used asynchronous modem connections.
+ Usually, a quite expensive external device called a `WAN router' is
+ needed to connect to a WAN.
+
+ Say Y here will enable the kernel to a??? as a WAN router betwenn LAN by
+ means of WAN adapters.
+
Fast switching (read help!)
CONFIG_NET_FASTROUTE
Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
@@ -7037,8 +7156,14 @@
The module will be called cosa.o. For general information about
modules read Documentation/modules.txt.
-# Fibre Channel driver support
-# CONFIG_NET_FC
+Fibre Channel driver support
+CONFIG_NET_FC
+ Say Y here provide support for storage arrays connected to
+ the system using Fibre Optic and the "X3.269-199X Fibre Channel
+ Protocol for SCSI" specification. You'll also need the generic SCSI
+ support, as well as the drivers for the storage array itself and
+ for the interface adapter such as SOC or SOC+. This subsystem could even
+ serve for IP networking, with some code extensions. If unsure, say N.
# Interphase 5526 Tachyon chipset based adaptor support
# CONFIG_IPHASE5526
@@ -9154,6 +9279,21 @@
The module will be called dc2xx.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt.
+
+USB Mustek MDC800 Digital Camera Support
+CONFIG_USB_MDC800
+ Say Y here if you want to connect this type of still camera to
+ your computer's USB port. This driver can be used with gphoto 0.4.3
+ and higher (look at www.gphoto.org).
+ To use it create a devicenode with mknod /dev/mustek c 10 171 and
+ configure it in your software.
+
+ 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 mdc800.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
+
+
USB Mass Storage support
CONFIG_USB_STORAGE
Say Y here if you want to connect USB mass storage devices to your
@@ -9473,6 +9613,23 @@
say M here and read Documentation/modules.txt. The module will be
called vfat.o.
+Compressed ROM file system support
+CONFIG_CRAMFS
+ This option provides support for CramFs (Compressed ROM File System).
+ Cramfs is designed to be a simple, small, and compressed file system for ROM
+ based embedded systems.
+ CramFs is read-only, limited to 256MB file systems (with 16MB files), don't
+ support neither 16/32 bits uid/gid nor hard links. Neither are timestamps.
+ It isn't endian aware.
+
+ See Documentation/filesystems/cramfs.txt and fs/cramfs/README
+ for further information.
+
+ If you want to compile this as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read Documentation/modules.txt. The module will be
+ called cramfs.o.
+
UMSDOS: Unix-like file system on top of standard MSDOS fs
CONFIG_UMSDOS_FS
Say Y here if you want to run Linux from within an existing DOS
@@ -9871,7 +10028,9 @@
Note that the answer to this question won't directly affect the
kernel: saying N will just cause this configure script to skip all
- the questions about foreign partitioning schemes. If unsure, say N.
+ the questions about foreign partitioning schemes.
+
+ If unsure, say N.
Alpha OSF partition support
CONFIG_OSF_PARTITION
@@ -11375,11 +11534,17 @@
This enable the kernel to lower the requested computer power by making some
devices enter in lower power levels (standy, sleep, ... modes).
Basically, this let you save power.
+
Two majors interfaces exist between the hardware and the OS, the older
Advanced Power Management (APM) and the newer Advanced Configuration and
Power Interface (ACPI).
+
Both are supported by the Linux Kernel.
+ Note that on some architectures (such as ia32), the idle task perform hlt
+ instructions which makes the CPU enter a low power mode. This can be seen as
+ the first kernel PM level.
+
Enter S1 for sleep (EXPERIMENTAL)
CONFIG_ACPI_S1_SLEEP
This enable ACPI compliant devices to enter level 1 of ACPI saving
@@ -12882,22 +13047,12 @@
an ISDN-fax-machine. This must be supported by the lowlevel driver
also. See Documentation/isdn/README.fax for more information.
-AVM CAPI2.0 support
-CONFIG_ISDN_DRV_AVMB1
- This enables support for the AVM B1/T1 ISDN networking cards.In
- addition, a CAPI (Common ISDN Application Programming Interface, a
+CAPI2.0 support
+CONFIG_ISDN_CAPI
+ This provides the CAPI (Common ISDN Application Programming Interface, a
standard making it easy for programs to access ISDN hardware, see
- http://www.capi.org/; to browse the WWW, you need to have access to
- a machine on the Internet that has a program like lynx or netscape)
- interface for this card is provided. In order to use this card,
- additional firmware is necessary, which has to be downloaded into
- the card using a utility which is distributed separately. Please
- read the file Documentation/isdn/README.avmb1.
-
- 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 avmb1.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ http://www.capi.org/. This is needed for AVM's set of active ISDN
+ controllers like B1, T1, M1.
AVM B1 ISA support
CONFIG_ISDN_DRV_AVMB1_B1ISA
@@ -12907,6 +13062,10 @@
CONFIG_ISDN_DRV_AVMB1_B1PCI
Enable support for the PCI version of the AVM B1 card.
+AVM B1 PCI V4 support
+CONFIG_ISDN_DRV_AVMB1_B1PCIV4
+ Enable support for the V4 version of AVM B1 PCI card.
+
AVM T1/T1-B ISA support
CONFIG_ISDN_DRV_AVMB1_T1ISA
Enable support for the AVM T1 T1B card.
@@ -12921,6 +13080,11 @@
Enable support for the AVM T1 T1B card.
Note: This is a PRI card and handle 30 B-channels.
+AVM C4 support
+CONFIG_ISDN_DRV_AVMB1_C4
+ Enable support for the AVM C4 PCI card.
+ This card handle 4 BRI ISDN lines (8 channels).
+
Verbose reason code reporting (kernel size +=7K)
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
If you say Y here, the AVM B1 driver will give verbose reasons for
@@ -13144,7 +13308,7 @@
say M here and read Documentation/modules.txt. The module will be
called ohci1394.o.
-RAW IEEE 1394 I/O support
+Raw IEEE 1394 I/O support
CONFIG_IEEE1394_RAWIO
Say Y here if you want support for the raw device. This is generally
a good idea, so you should say Y here. The raw device enables
@@ -13155,6 +13319,17 @@
say M here and read Documentation/modules.txt. The module will be
called raw1394.o.
+Excessive debugging output
+CONFIG_IEEE1394_VERBOSEDEBUG
+ If you say Y here, you will get very verbose debugging logs from the
+ subsystem which includes a dump of the header of every sent and
+ received packet. This can amount to a high amount of data collected
+ in a very short time which is usually also saved to disk by the
+ system logging daemons.
+
+ Say Y if you really want or need the debugging output, everyone else
+ says N.
+
#
# m68k-specific kernel options
# Documented by Chris Lawrence <quango@themall.net> et al.
@@ -13193,6 +13368,14 @@
If you plan to try to use the kernel on such a machine say Y here.
Everybody else says N.
+Sun 3X support
+CONFIG_SUN3X
+ This option enables support for the Sun 3x series of workstations. Be
+ warned that this support is very experimental. You will also want to
+ say Y to 68020 support and N to the other processors below.
+
+ If you don't want to compile a kernel for a Sun 3x, say N.
+
Sun 3 support
CONFIG_SUN3
This option enables support for the Sun 3 series of workstations. Be
@@ -13256,8 +13439,8 @@
mantissa and round slightly incorrect, what is more then enough
for normal usage.
-Advanced processor options
-CONFIG_ADVANCED_CPU
+Advanced configuration options
+CONFIG_ADVANCED
This gives you access to some advanced options for the CPU. The
defaults should be fine for most users, but these options may make
it possible for you to improve performance somewhat if you know what
@@ -14223,45 +14406,6 @@
If you have any questions or comments about the Compaq Personal
Server, send e-mail to skiff@crl.dec.com
-
-Virtual/Physical Memory Split
-CONFIG_1GB
- If you are compiling a kernel which will never run on a machine
- with more than 1 Gigabyte total physical RAM, answer "3GB/1GB"
- here (default choice).
-
- On 32-bit x86 systems Linux can use up to 64 Gigabytes of physical
- memory. However 32-bit x86 processors have only 4 Gigabytes of
- virtual memory space. This option specifies the maximum amount of
- virtual memory space one process can potentially use. Certain types
- of applications (eg. database servers) perform better if they have
- as much virtual memory per process as possible.
-
- The remaining part of the 4G virtual memory space is used by the
- kernel to 'permanently map' as much physical memory as possible.
- Certain types of applications perform better if there is more
- 'permanently mapped' kernel memory.
-
- [WARNING! Certain boards do not support PCI DMA to physical addresses
- bigger than 2 Gigabytes. Non-DMA-able memory must not be permanently
- mapped by the kernel, thus a 1G/3G split will not work on such boxes.]
-
- As you can see there is no 'perfect split' - the fundamental
- problem is that 4G of 32-bit virtual memory space is short. So
- you'll have to pick your own choice - depending on the application
- load of your box. A 2G/2G split is typically a good choice for a
- generic Linux server with lots of RAM.
-
- Any potentially remaining (not permanently mapped) part of physical
- memory is called 'high memory'. How much total high memory the kernel
- can handle is influenced by the (next) High Memory configuration option.
-
- The actual amount of total physical memory will either be
- autodetected or can be forced by using a kernel command line option
- such as "mem=256M". (Try "man bootparam" or see the documentation of
- your boot loader (lilo or loadlin) about how to pass options to the
- kernel at boot time. The lilo procedure is also explained in the
- SCSI-HOWTO, available from http://www.linuxdoc.org/docs.html#howto .)
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)