patch-2.4.17 linux/Documentation/Configure.help
Next file: linux/Documentation/DMA-mapping.txt
Previous file: linux/Documentation/Changes
Back to the patch index
Back to the overall index
- Lines: 3776
- Date:
Fri Dec 21 16:40:31 2001
- Orig file:
linux-2.4.16/Documentation/Configure.help
- Orig date:
Thu Nov 22 18:52:44 2001
diff -Naur -X /home/marcelo/lib/dontdiff linux-2.4.16/Documentation/Configure.help linux/Documentation/Configure.help
@@ -2,10 +2,10 @@
# Eric S. Raymond <mailto:esr@thyrsus.com>
# Steven Cole <mailto:elenstev@mesatop.com>
#
-# Merged version 2.49: Current with 2.4.15-pre1 and 2.4.13-ac8.
+# Merged version 2.69: current with 2.4.17-pre8/2.5.1-pre10.
#
# This version of the Linux kernel configuration help texts
-# corresponds to the kernel versions 2.4.x.
+# corresponds to kernel versions 2.4.x and 2.5.x.
#
# Translations of this file available on the WWW:
#
@@ -14,11 +14,13 @@
# - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
# <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
# - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
-# <http://www.traduc.org/kernelfr>
+# <http://www.traduc.org/kernelfr/>
# - Polish, by Dominik Mierzejewski <mailto:dmierzej@elka.pw.edu.pl>, at
# <http://home.elka.pw.edu.pl/~dmierzej/linux/kernel/>
-# - German, by SuSE, at <http://www.suse.de/~ke/kernel>. This patch
+# - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
# also includes infrastructure to support different languages.
+# - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
+# <http://www.terra.es/personal7/bella5/traduccions.htm>
#
# To access a document on the WWW, you need to have a direct Internet
# connection and a browser program such as netscape or lynx. If you
@@ -67,7 +69,7 @@
# Explain why someone configuring a kernel might want to select your
# option.
#
-# All this was shamelessly stolen from several different sources. Many
+# All this was shamelessly stolen from numerous different sources. Many
# thanks to all the contributors. Feel free to use these help texts in
# your own kernel configuration tools. The texts are copyrighted (c)
# 1995-2000 by Axel Boldt and many others and are governed by the GNU
@@ -133,8 +135,8 @@
See also the <file:Documentation/smp.tex>,
<file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
- <file:Documentation/nmi_watchdog.txt> and the SMP-FAQ on the WWW at
- <http://www.irisa.fr/prive/mentre/smp-faq/>.
+ <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
+ <http://www.linuxdoc.org/docs.html#howto>.
If you don't know what to do here, say N.
@@ -239,7 +241,7 @@
You will need a new lynxer.elf file to flash your firmware with - send
email to Martin.Bligh@us.ibm.com
-IO-APIC Support on Uniprocessors
+IO-APIC support on uniprocessors
CONFIG_X86_UP_IOAPIC
An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
SMP-capable replacement for PC-style interrupt controllers. Most
@@ -339,7 +341,7 @@
"high memory".
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
+ more than 960 megabytes of total physical RAM, answer "off" here (default
choice and suitable for most users). This will result in a "3GB/1GB"
split: 3GB are mapped so that each process sees a 3GB virtual memory
space and the remaining part of the 4GB virtual memory space is used
@@ -356,10 +358,10 @@
processors (Pentium Pro and better). NOTE: If you say "64GB" here,
then the kernel will not boot on CPUs that don't support PAE!
- The actual amount of total physical memory will either be
- auto detected 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
+ The actual amount of total physical memory will either be auto
+ detected 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 (grub, lilo or loadlin) about how to pass options to the
kernel at boot time.)
If unsure, say "off".
@@ -374,7 +376,7 @@
Select this if you have a 32-bit processor and more than 4
gigabytes of physical RAM.
-Normal PC floppy disk support
+Normal floppy disk support
CONFIG_BLK_DEV_FD
If you want to use the floppy disk drive(s) of your PC under Linux,
say Y. Information about this driver, especially important for IBM
@@ -577,7 +579,7 @@
To fine-tune ATA/IDE drive/interface parameters for improved
performance, look for the hdparm package at
- <http://www.ibiblio.org/pub/Linux/system/hardware>.
+ <ftp://ibiblio.org/pub/Linux/system/hardware/>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -666,12 +668,9 @@
CD-ROM drive, you can say N to all other CD-ROM options, but be sure
to say Y or M to "ISO 9660 CD-ROM file system support".
- Read the CD-ROM-HOWTO, available from
- <http://www.linuxdoc.org/docs.html#howto> and
- <file:Documentation/cdrom/ide-cd>. Note that older versions of lilo
- (the Linux boot loader) cannot properly deal with IDE/ATAPI CD-ROMs,
- so install lilo-16 or higher, available from
- <ftp://metalab.unc.edu/pub/Linux/system/boot/lilo>.
+ Note that older versions of LILO (LInux LOader) cannot properly deal
+ with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
+ <ftp://brun.dyndns.org/pub/linux/lilo/>.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -820,7 +819,7 @@
for these drives, but you can change that by saying Y to the
following question "Use DMA by default when available". You can get
the latest version of the hdparm utility from
- <ftp://metalab.unc.edu/pub/Linux/system/hardware/>.
+ <ftp://ibiblio.org/pub/Linux/system/hardware/>.
Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
and the file <file:Documentation/ide.txt> for more information.
@@ -887,7 +886,7 @@
IGNORE word93 Validation BITS
CONFIG_IDEDMA_IVB
- There are unclear terms is ATA-4 and ATA-5 standards how certain
+ There are unclear terms in ATA-4 and ATA-5 standards how certain
hardware (an 80c ribbon) should be detected. Different interpretations
of the standards have been released in hardware. This causes problems:
for example, a host with Ultra Mode 4 (or higher) will not run
@@ -899,7 +898,7 @@
It is normally safe to answer Y; however, the default is N.
-ATA Work(s) In Progress (EXPERIMENTAL)‹
+ATA Work(s) In Progress (EXPERIMENTAL)
CONFIG_IDEDMA_PCI_WIP
If you enable this you will be able to use and test highly
developmental projects. If you say N, the configurator will
@@ -914,7 +913,7 @@
Pacific Digital A-DMA support (EXPERIMENTAL)
CONFIG_BLK_DEV_PDC_ADMA
- Please read the comments at the top of <file:drivers/ide/pdcadma.c>.
+ Please read the comments at the top of <file:drivers/ide/ide-pci.c>.
3ware Hardware ATA-RAID support
CONFIG_BLK_DEV_3W_XXXX_RAID
@@ -973,7 +972,7 @@
SAY N!
-AMD Viper support
+AMD Viper (7401/7409/7411) chipset support
CONFIG_BLK_DEV_AMD74XX
This driver ensures (U)DMA support for the AMD756/760 Viper
chipsets.
@@ -984,7 +983,7 @@
If unsure, say N.
-AMD Viper ATA-66 Override (WIP)
+AMD Viper ATA-66 Override support (WIP)
CONFIG_AMD74XX_OVERRIDE
This option auto-forces the ata66 flag.
This effect can be also invoked by calling "idex=ata66"
@@ -1118,11 +1117,13 @@
Special UDMA Feature
CONFIG_PDC202XX_BURST
- 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.
+ This option causes the pdc202xx driver to enable UDMA modes on the
+ PDC202xx even when the PDC202xx BIOS has not done so.
- Unknown for PDC20265/PDC20267 Ultra DMA 100.
+ It was originally designed for the PDC20246/Ultra33, whose BIOS will
+ only setup UDMA on the first two PDC20246 cards. It has also been
+ used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes
+ when the PDC20265 BIOS has been disabled (for faster boot up).
Please read the comments at the top of
<file:drivers/ide/pdc202xx.c>.
@@ -1251,15 +1252,6 @@
<file:Documentation/ide.txt> and <file:drivers/ide/pdc4030.c> files
for more info.
-# This is for Linus's tree.
-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
- <file:Documentation/ide.txt> and <file:drivers/ide/qd6580.c> for
- more info.
-
-# This is for Alan's tree. Note the name difference.
QDI QD65XX support
CONFIG_BLK_DEV_QD65XX
This driver is enabled at runtime using the "ide0=qd65xx" kernel
@@ -1488,7 +1480,7 @@
CONFIG_PARIDE_PG
This option enables a special high-level driver for generic ATAPI
devices connected through a parallel port. The driver allows user
- programs, such as cdrecord, to send ATAPI commands directly to a
+ programs, such as cdrtools, to send ATAPI commands directly to a
device.
If you chose to build PARIDE support into your kernel, you may
@@ -1502,7 +1494,7 @@
This driver implements an API loosely related to the generic SCSI
driver. See <file:include/linux/pg.h>. for details.
- You can obtain the most recent version of cdrecord from
+ You can obtain the most recent version of cdrtools from
<ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
later fully support this driver.
@@ -1603,7 +1595,7 @@
(low speed) adapter that is used in some portable hard drives. If
you chose to build PARIDE support into your kernel, you may answer Y
here to build in the protocol driver, otherwise you should answer M
- to build it as a loadable module. The module will be called ktti.o.
+ to build it as a loadable module. The module will be called fit2.o.
You must also have a high-level driver for the type of device that
you want to support.
@@ -1716,9 +1708,9 @@
controller, you do not need to say Y here.
More information about Software RAID on Linux is contained in the
- Software-RAID mini-HOWTO, available from
- <http://www.linuxdoc.org/docs.html#howto>. There you will also
- learn where to get the supporting user space utilities raidtools.
+ Software RAID mini-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>. There you will also learn
+ where to get the supporting user space utilities raidtools.
If unsure, say N.
@@ -1811,7 +1803,6 @@
If unsure, say N.
-# AC tree only
Support for IDE Raid controllers
CONFIG_BLK_DEV_ATARAID
Say Y or M if you have an IDE Raid controller and want linux
@@ -1824,7 +1815,6 @@
has its own Raid drivers, which you should use if you need better
performance.
-# AC tree only
Support Promise software RAID (Fasttrak(tm))
CONFIG_BLK_DEV_ATARAID_PDC
Say Y or M if you have a Promise Fasttrak (tm) Raid controller
@@ -1835,7 +1825,6 @@
If you choose to compile this as a module, the module will be called
pdcraid.o.
-# AC tree only
Highpoint 370 software RAID
CONFIG_BLK_DEV_ATARAID_HPT
Say Y or M if you have a Highpoint HPT 370 Raid controller
@@ -1851,19 +1840,19 @@
This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- <http://oss.sgi.com/mips>.
+ <http://oss.sgi.com/mips/>.
Support for Algorithmics P4032 (EXPERIMENTAL)
CONFIG_ALGOR_P4032
This is an evaluation board of the British company Algorithmics.
The board uses the R4300 and a R5230 CPUs. For more information
- about this board see <http://www.algor.co.uk>.
+ about this board see <http://www.algor.co.uk/>.
Support for BAGET MIPS series
CONFIG_BAGET_MIPS
This enables support for the Baget, a Russian embedded system. For
more details about the Baget see the Linux/MIPS FAQ on
- <http://oss.sgi.com/mips>.
+ <http://oss.sgi.com/mips/>.
Baget AMD LANCE support
CONFIG_BAGETLANCE
@@ -1874,8 +1863,8 @@
Support for DECstations
CONFIG_DECSTATION
This enables support for DEC's MIPS based workstations. For details
- see the Linux/MIPS FAQ on <http://oss.sgi.com/mips> and the
- DECstation porting pages on <http://decstation.unix-ag.org>.
+ see the Linux/MIPS FAQ on <http://oss.sgi.com/mips/> and the
+ DECstation porting pages on <http://decstation.unix-ag.org/>.
If you have one of the following DECstation Models you definitely
want to choose R4xx0 for the CPU Type:
@@ -1904,7 +1893,7 @@
Support for the Momentum Computer Ocelot SBC
CONFIG_MOMENCO_OCELOT
The Ocelot is a MIPS-based Single Board Computer (SBC) made by
- Momentum Computer <http://www.momenco.com>.
+ Momentum Computer <http://www.momenco.com/>.
Support for NEC DDB Vrc-5074
CONFIG_DDB5074
@@ -1917,7 +1906,7 @@
evaluation board.
Features : kernel debugging, serial terminal, NFS root fs, on-board
- ether port (Need an additional patch at <http://linux.junsun.net>),
+ ether port (Need an additional patch at <http://linux.junsun.net/>),
USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
PS2 keyboard, PS2 mouse, etc.
@@ -1927,7 +1916,7 @@
evaluation board.
Features : kernel debugging, serial terminal, NFS root fs, on-board
- ether port (Need an additional patch at <http://linux.junsun.net>),
+ ether port (Need an additional patch at <http://linux.junsun.net/>),
USB, AC97, PCI, etc.
Support for MIPS Atlas board
@@ -1953,7 +1942,7 @@
This is a machine with a R4000 100 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- <http://oss.sgi.com/mips>.
+ <http://oss.sgi.com/mips/>.
Enable Qtronix 990P Keyboard Support
CONFIG_QTRONIX_KEYBOARD
@@ -1965,7 +1954,7 @@
This is a machine with a R4000 100 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- <http://oss.sgi.com/mips>.
+ <http://oss.sgi.com/mips/>.
Support for SNI RM200 PCI
CONFIG_SNI_RM200_PCI
@@ -1974,13 +1963,13 @@
Technology and now in turn merged with Fujitsu. Say Y here to
support this machine type.
-Support for SGI IP22
+Support for SGI-IP22 (Indy/Indigo2)
CONFIG_SGI_IP22
This are the SGI Indy, Challenge S and Indigo2, as well as certain
OEM variants like the Tandem CMN B006S. To compile a Linux kernel
that runs on these, say Y here.
-Support for SGI IP27
+Support for SGI IP27 (Origin200/2000)
CONFIG_SGI_IP27
This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
workstations. To compile a Linux kernel that runs on these, say Y
@@ -2036,13 +2025,26 @@
DZ11-family serial controllers for VAXstations, including the
DC7085, M7814, and M7819.
-
TURBOchannel support
CONFIG_TC
TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
Documentation on writing device drivers for TurboChannel is available at:
<http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
+# Choice: galileo_clock
+75
+CONFIG_SYSCLK_75
+ Configure the kernel for clock speed of your Galileo board.
+ The choices are 75MHz, 83.3MHz, and 100MHz.
+
+83.3
+CONFIG_SYSCLK_83
+ Configure the Galileo kernel for a clock speed of 83.3 MHz.
+
+100
+CONFIG_SYSCLK_100
+ Configure the Galileo kernel for a clock speed of 100 MHz.
+
Z85C30 Serial Support
CONFIG_ZS
Documentation on the Zilog 85C350 serial communications controller
@@ -2072,7 +2074,7 @@
CONFIG_PCMCIA_NINJA_SCSI
If you intend to attach this type of PCMCIA SCSI host adapter to
your computer, say Y here and read
- <file:Documentation/README.nsp_cs>.
+ <file:Documentation/README.nsp_cs.eng>.
This driver is also available as a module called nsp_cs.o ( =
code which can be inserted in and removed from the running kernel
@@ -2197,7 +2199,7 @@
Access). This option is for configuring high-end multiprocessor
server machines. If in doubt, say N.
-CPU type
+R41xx
CONFIG_CPU_VR41XX
The options selects support for the NEC VR41xx series of processors.
Only choose this option if you have one of these processors as a
@@ -2209,7 +2211,7 @@
Saying yes here allows you to select support for various features
your CPU may or may not have. Most people should say N here.
-ll/sc Instructions available
+ll and sc instructions available
CONFIG_CPU_HAS_LLSC
MIPS R4000 series and later provide the Load Linked (ll)
and Store Conditional (sc) instructions. More information is
@@ -2219,7 +2221,7 @@
for better performance, N if you don't know. You must say Y here
for multiprocessor machines.
-lld and scd instructions
+lld and scd instructions available
CONFIG_CPU_HAS_LLDSCD
Say Y here if your CPU has the lld and scd instructions, the 64-bit
equivalents of ll and sc. Say Y here for better performance, N if
@@ -2263,7 +2265,7 @@
of which are given in <file:Documentation/Changes>.
For a general introduction to Linux networking, it is highly
- recommended to read the NET-3-HOWTO, available from
+ recommended to read the NET-HOWTO, available from
<http://www.linuxdoc.org/docs.html#howto>.
Socket filtering
@@ -2352,7 +2354,7 @@
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. If unsure, say `N'.
-IRC Send/Chat support
+IRC Send/Chat protocol support
CONFIG_IP_NF_IRC
There is a commonly-used extension to IRC called
Direct Client-to-Client Protocol (DCC). This enables users to send
@@ -2436,7 +2438,7 @@
If you want to compile it as a module, say M here and read
Documentation/modules.txt. If unsure, say `N'.
-length match support
+LENGTH match support
CONFIG_IP_NF_MATCH_LENGTH
This option allows you to match the length of a packet against a
specific value or range of values.
@@ -2658,6 +2660,23 @@
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. If unsure, say `N'.
+Multiple port match support
+CONFIG_IP6_NF_MATCH_MULTIPORT
+ Multiport matching allows you to match TCP or UDP packets based on
+ a series of source or destination ports: normally a rule can only
+ match a single range of ports.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say `N'.
+
+Owner match support
+CONFIG_IP6_NF_MATCH_OWNER
+ Packet owner matching allows you to match locally-generated packets
+ based on who created them: the user, group, process or session.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say `N'.
+
Packet filtering
CONFIG_IP6_NF_FILTER
Packet filtering defines a table `filter', which has a series of
@@ -2724,6 +2743,14 @@
If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>. If unsure, say `N'.
+LOG target support
+CONFIG_IP6_NF_TARGET_LOG
+ This option adds a `LOG' target, which allows you to create rules in
+ any iptables table which records the packet header to the syslog.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say `N'.
+
SYN flood protection
CONFIG_SYN_COOKIES
Normal TCP/IP networking is open to an attack known as "SYN
@@ -2776,7 +2803,7 @@
To find out what type of Alpha system you have, you may want to
check out the Linux/Alpha FAQ, accessible on the WWW from
- <http://www.alphalinux.org>. In summary:
+ <http://www.alphalinux.org/>. In summary:
Alcor/Alpha-XLT AS 600
Alpha-XL XL-233, XL-266
@@ -2955,13 +2982,18 @@
CONFIG_ALPHA_GAMMA
Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
+EV67 (or later) CPU (speed > 600MHz)?
+CONFIG_ALPHA_EV67
+ Is this a machine based on the EV67 core? If in doubt, select N here
+ and the machine will be treated as an EV6.
+
Use SRM as bootloader
CONFIG_ALPHA_SRM
There are two different types of booting firmware on Alphas: SRM,
which is command line driven, and ARC, which uses menus and arrow
keys. Details about the Linux/Alpha booting process are contained in
the Linux/Alpha FAQ, accessible on the WWW from
- <http://www.alphalinux.org>.
+ <http://www.alphalinux.org/>.
The usual way to load Linux on an Alpha machine is to use MILO
(a bootloader that lets you pass command line parameters to the
@@ -3130,7 +3162,7 @@
The user level application needed to use this driver can be found at
the IBM Linux Technology Center (LTC) web site:
- http://www.ibm.com/linux/ltc/
+ <http://www.ibm.com/linux/ltc/>.
If you own one of the above IBM Thinkpads which has the Mwave chipset
in it, say Y.
@@ -3300,7 +3332,7 @@
When in doubt, say Y.
-PCI Hotplug support
+Generic PCI hotplug support
CONFIG_HOTPLUG_PCI
Say Y here if you have a motherboard with a PCI Hotplug controller.
This allows you to add and remove PCI cards while the machine is
@@ -3314,7 +3346,7 @@
When in doubt, say N.
-PCI Compaq Hotplug controller
+Compaq PCI Hotplug driver
CONFIG_HOTPLUG_PCI_COMPAQ
Say Y here if you have a motherboard with a Compaq PCI Hotplug
controller.
@@ -3505,7 +3537,7 @@
example, used on modern desktops as well as laptops, is USB.
Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
- software (at <http://linux-hotplug.sourceforge.net>) and install it.
+ software (at <http://linux-hotplug.sourceforge.net/>) and install it.
Then your kernel will automatically call out to a user mode "policy
agent" (/sbin/hotplug) to load modules and set up software needed
to use devices as you hotplug them.
@@ -3547,6 +3579,12 @@
If unsure, say Y.
+i82092 compatible bridge support
+CONFIG_I82092
+ This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
+ found in some older laptops and more commonly in evaluation boards for the
+ chip.
+
i82365 compatible host bridge support
CONFIG_I82365
Say Y here to include support for ISA-bus PCMCIA host bridges that
@@ -3625,7 +3663,6 @@
don't understand what this means or are not a kernel hacker, just
leave it at its default value ELF.
-# Choice: kcore
Select a.out format for /proc/kcore
CONFIG_KCORE_AOUT
Not necessary unless you're using a very out-of-date binutils
@@ -3748,7 +3785,7 @@
The module will be called envctrl.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-# Choice: x86
+# Choice: x86type
Processor family
CONFIG_M386
This is the processor type of your CPU. This information is used for
@@ -3821,7 +3858,7 @@
The program SVGATextMode can be used to utilize SVGA video cards to
their full potential in text mode. Download it from
- <ftp://metalab.unc.edu/pub/Linux/utils/console>.
+ <ftp://ibiblio.org/pub/Linux/utils/console/>.
Say Y.
@@ -4053,21 +4090,18 @@
module will be called aty128fb.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-# AC tree only
Maxine (Personal DECstation) onboard framebuffer support
CONFIG_FB_MAXINE
Say Y here to directly support the on-board framebuffer in the
Maxine (5000/20, /25, /33) version of the DECstation. There is a
page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
-# AC tree only
PMAG-BA TURBOchannel framebuffer support
CONFIG_FB_PMAG_BA
Say Y here to directly support the on-board PMAG-BA framebuffer in
the 5000/1xx versions of the DECstation. There is a page dedicated
to Linux on DECstations at <http://decstation.unix-ag.org/>.
-# AC tree only
PMAGB-B TURBOchannel framebuffer support
CONFIG_FB_PMAGB_B
Say Y here to directly support the on-board PMAGB-B framebuffer in
@@ -4079,10 +4113,32 @@
Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
Electronics) StrongARM PCI card.
-P720T
-CONFIG_ARCH_P720T
- Say Y here if you intend to run this kernel on the ARM Prospector
- 720T.
+ANAKIN Vehicle Telematics Platform
+CONFIG_ARCH_ANAKIN
+ The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
+ 64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
+
+ On board peripherals:
+ * Front display: 400x234 16 bit TFT touchscreen
+ * External independent second screen interface
+ * CAN controller SJA1000
+ * USB host controller
+ * 6 channel video codec with hardware overlay
+ * Smartcard reader
+ * IrDa
+
+ Modules interfaced over the Multi Media Extension slots:
+ * A communication card
+ Wavecom GPRS modem
+ uBlock GPS
+ Bosch DAB module
+ * An audio card ( 4 * 40W, AC97 Codec, I2S)
+
+Altera Excalibur XA10 Dev Board
+ARCH_CAMELOT
+ This enables support for Altera's Excalibur XA10 development board.
+ If you would like to build your kernel to run on one of these boards
+ then you must say 'Y' here. Otherwise say 'N'
Link-Up Systems LCD support
CONFIG_FB_L7200
@@ -4306,10 +4362,8 @@
a module, say M here and read <file:Documentation/modules.txt>.
You can pass several parameters to the driver at boot time or at
- module load time. The parameters look like "video=matrox:XXX", where
- the meaning of XXX can be found at the end of the main source file
- (<file:drivers/video/matroxfb.c>). Please see
- <file:Documentation/fb/matroxfb.txt>.
+ module load time. The parameters look like "video=matrox:XXX", and
+ are described in <file:Documentation/fb/matroxfb.txt>.
Matrox Millennium I/II support
CONFIG_FB_MATROX_MILLENIUM
@@ -4372,7 +4426,7 @@
The driver starts in monitor mode and you must use the matroxset
tool (available at
- <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to switch it to
+ <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
PAL or NTSC or to swap primary and secondary head outputs.
Secondary head driver also always start in 640x480 resolution, you
must use fbset to change it.
@@ -4394,7 +4448,7 @@
The driver starts in monitor mode and currently does not support
output in TV modes. You must use the matroxset tool (available
- at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to swap
+ at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to swap
primary and secondary head outputs. Secondary head driver always
start in 640x480 resolution and you must use fbset to change it.
@@ -4504,19 +4558,17 @@
This is the frame buffer device driver for the Hitachi HD64461 LCD
frame buffer card.
-SIS 630/540 display support
+SIS acceleration
CONFIG_FB_SIS
This is the frame buffer device driver for the SiS 630 and 640 Super
Socket 7 UMA cards. Specs available at <http://www.sis.com.tw/>.
-# AC tree only
SIS 630/540/730 support
CONFIG_FB_SIS_300
This is the frame buffer device driver for the SiS 630 and related
Super Socket 7 UMA cards. Specs available at
<http://www.sis.com.tw/>.
-# AC tree only
SIS 315H/315 support
CONFIG_FB_SIS_315
This is the frame buffer device driver for the SiS 315 graphics
@@ -4570,7 +4622,6 @@
is at
<http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
-# AC tree only
ATI Radeon display support
CONFIG_FB_RADEON
Choose this option if you want to use an ATI Radeon graphics card as
@@ -4697,7 +4748,8 @@
drive, PLIP link (Parallel Line Internet Protocol is mainly used to
create a mini network by connecting the parallel ports of two local
machines) etc., then you need to say Y here; please read
- <file:Documentation/parport.txt> and drivers/parport/BUGS-parport.
+ <file:Documentation/parport.txt> and
+ <file:drivers/parport/BUGS-parport>.
For extensive information about drivers for many devices attaching
to the parallel port see <http://www.torque.net/linux-pp.html> on
@@ -4729,7 +4781,7 @@
If unsure, say Y.
-Parallel+serial PCI card support
+Parallel+serial PCI multi-IO card support
CONFIG_PARPORT_SERIAL
This adds support for multi-IO PCI cards that have parallel and
serial ports. You should say Y or M here. If you say M, the module
@@ -5154,6 +5206,7 @@
It is safe to say N here for now.
+# 2.5 tree only
IPv6: routing messages via old netlink
CONFIG_IPV6_NETLINK
You can say Y here to receive routing messages from the IPv6 code
@@ -5186,7 +5239,7 @@
used for local networks of Windows machines. You need it if you
want to access Novell NetWare file or print servers using the Linux
Novell client ncpfs (available from
- <ftp://metalab.unc.edu/pub/Linux/system/filesystems/>) or from
+ <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
available from <http://www.linuxdoc.org/docs.html#howto>). In order
to do the former, you'll also have to say Y to "NCP file system
@@ -5198,8 +5251,8 @@
To turn your Linux box into a fully featured NetWare file server and
IPX router, say Y here and fetch either lwared from
- <ftp://metalab.unc.edu/pub/Linux/system/network/daemons/> or
- mars_nwe from <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>. For more
+ <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
+ mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
information, read the IPX-HOWTO available from
<http://www.linuxdoc.org/docs.html#howto>.
@@ -5235,7 +5288,7 @@
'special' sockets to sockets listening on the primary network is
disabled. This might break existing applications, especially RIP/SAP
daemons. A RIP/SAP daemon that works well with the full internal net
- can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>.
+ can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
If you don't know what you are doing, say N.
@@ -5303,7 +5356,7 @@
network link driver", "Routing messages" and "Network packet
filtering". The first two are required to allow configuration via
rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
- from <ftp://ftp.inr.ac.ru>). The "Network packet filtering" option
+ from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
will be required for the forthcoming routing daemon to work.
See <file:Documentation/networking/decnet.txt> for more information.
@@ -5424,9 +5477,8 @@
Amateur Radio support
CONFIG_HAMRADIO
If you want to connect your Linux box to an amateur radio, answer Y
- here. You want to read <http://www.tapr.org/tapr/html/pkthome.html>
- and the HAM-HOWTO and the AX25-HOWTO, both available from
- <http://www.linuxdoc.org/docs.html#howto>.
+ here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
+ the AX25-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question won't directly affect the
kernel: saying N will just cause the configurator to skip all
@@ -5633,7 +5685,7 @@
connect to a parallel interface. The driver supports the picpar and
par96 designs. To configure the driver, use the sethdlc utility
available in the standard ax25 utilities package. For information on
- the modems, see <http://www.baycom.de> and the file
+ the modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
@@ -5647,7 +5699,7 @@
connect to a parallel interface. The driver supports the EPP
designs. To configure the driver, use the sethdlc utility available
in the standard ax25 utilities package. For information on the
- modems, see <http://www.baycom.de> and the file
+ modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
@@ -5666,7 +5718,7 @@
driver and still provided in case this driver does not work with
your serial interface chip. To configure the driver, use the sethdlc
utility available in the standard ax25 utilities package. For
- information on the modems, see <http://www.baycom.de> and
+ information on the modems, see <http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
@@ -5683,7 +5735,7 @@
the full-duplex driver. This driver is depreciated. To configure
the driver, use the sethdlc utility available in the standard ax25
utilities package. For information on the modems, see
- <http://www.baycom.de> and
+ <http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
@@ -5860,7 +5912,7 @@
- etc...
For more informations, please refer to:
- <http://www.freshmeat.net/projects/etherdivert>
+ <http://diverter.sourceforge.net/>
<http://perso.wanadoo.fr/magpie/EtherDivert.html>
If unsure, say N.
@@ -5915,14 +5967,14 @@
If unsure, say N.
+# 2.5 tree only
Kernel/User network link driver
CONFIG_NETLINK
This driver allows for two-way communication between the kernel and
user processes. It does so by creating a new socket family,
PF_NETLINK. Over this socket, the kernel can send and receive
datagrams carrying information. It is documented on many systems in
- netlink(7), a HOWTO is provided as well, for example on
- <http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html>.
+ netlink(7).
So far, the kernel uses this feature to publish some network related
information if you say Y to "Routing messages", below. You also need
@@ -5934,11 +5986,12 @@
If unsure, say Y.
+# 2.5 tree only
Routing messages
CONFIG_RTNETLINK
If you say Y here, user space programs can receive some network
related routing information over the netlink. 'rtmon', supplied
- with the iproute2 package (<ftp://ftp.inr.ac.ru>), can read and
+ with the iproute2 package (<ftp://ftp.inr.ac.ru/>), can read and
interpret this data. Information sent to the kernel over this link
is ignored.
@@ -6225,7 +6278,7 @@
control memory (128K-1KVC, 512K-4KVC), the size of the packet
memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
UTP155, UTP25, DS3 and E3). Go to:
- www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
+ <http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
for more info about the cards. Say Y (or M to compile as a module
named iphase.o) here if you have one of these cards.
@@ -6238,7 +6291,7 @@
messages is controlled by a bitmap. This may be specified as a
module argument (kernel command line argument as well?), changed
dynamically using an ioctl (Get the debug utility, iadbg, from
- <ftp://ftp.iphase.com/pub/atm/pci>).
+ <ftp://ftp.iphase.com/pub/atm/pci/>).
See the file <file:drivers/atm/iphase.h> for the meanings of the
bits in the mask.
@@ -6247,6 +6300,13 @@
speed of the driver, and the size of your syslog files! When
inactive, they will have only a modest impact on performance.
+Efficient Networks Speedstream 3010
+CONFIG_ATM_LANAI
+ Supports ATM cards based on the Efficient Networks "Lanai"
+ chipset such as the Speedstream 3010 and the ENI-25p. The
+ Speedstream 3060 is currently not supported since we don't
+ have the code to drive the on-board Alcatel DSL chipset (yet).
+
Linux telephony support
CONFIG_PHONE
Say Y here if you have a telephony card, which for example allows
@@ -6365,6 +6425,13 @@
the performances of the driver, and the size of your syslog files!
Keep the debugging level to 0 during normal operations.
+PPP over ATM
+CONFIG_PPPOATM
+ Support PPP (Point to Point Protocol) encapsulated in ATM frames.
+ This implementation does not yet comply with section 8 of RFC2364,
+ which can lead to bad results idf the ATM peer loses state and
+ changes its encapsulation unilaterally.
+
Fusion MPT device support
CONFIG_FUSION
LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
@@ -6490,12 +6557,6 @@
You also need to say Y here if you want support for the parallel
port version of the 100 MB IOMEGA ZIP drive.
- Please read the SCSI-HOWTO, available from
- <http://www.linuxdoc.org/docs.html#howto>. The
- SCSI-Programming-HOWTO contains information about how to add or
- remove an SCSI device from a running Linux machine without
- rebooting.
-
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 scsi_mod.o. If you want to compile it as
@@ -6573,7 +6634,7 @@
tape drives (ADR-x0) that supports the standard SCSI-2 commands for
tapes (QIC-157) and can be driven by the standard driver st.
For more information, you may have a look at the SCSI-HOWTO
- <ftp://metalab.unc.edu/pub/Linux/docs/HOWTO> and
+ <http://www.linuxdoc.org/docs.html#howto> and
<file:drivers/scsi/README.osst> in the kernel source.
More info on the OnStream driver may be found on
<http://linux1.onstream.nl/test/>
@@ -6628,12 +6689,12 @@
directly, so you need some additional software which knows how to
talk to these devices using the SCSI protocol:
- For scanners, look at SANE (<http://www.mostang.com/sane>). For CD
- writer software look at cdrecord
+ For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
+ writer software look at Cdrtools
(<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
- and for burning a "disk at once": cdrdao
- (<http://www.ping.de/sites/daneb/cdrdao.html>). Cdparanoia is a high
- quality digital reader of audio CDs (<http://www.xiph.org/paranoia>).
+ and for burning a "disk at once": CDRDAO
+ (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
+ quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
For other devices, it's possible that you'll have to write the
driver software yourself. Please read the file
<file:Documentation/scsi-generic.txt> for more information.
@@ -6644,17 +6705,6 @@
<file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
say N.
-Enable extra checks in SCSI queueing code
-CONFIG_SCSI_DEBUG_QUEUES
- This option turns on a lot of additional consistency checking for
- the new queueing code. This will adversely affect performance, but
- it is likely that bugs will be caught sooner if this is turned on.
- This will typically cause the kernel to panic if an error is
- detected, but it would have probably crashed if the panic weren't
- there. Comments/questions/problems to linux-scsi mailing list
- please. See <http://www.andante.org/scsi_queue.html> for more
- up-to-date information.
-
Probe all LUNs on each SCSI device
CONFIG_SCSI_MULTI_LUN
If you have a SCSI device that supports more than one LUN (Logical
@@ -6768,7 +6818,7 @@
intended to replace the previous aic7xxx driver maintained by Doug
Ledford since Doug is no longer maintaining that driver.
-Adaptec I2O RAID controllers
+Adaptec I2O RAID support
CONFIG_SCSI_DPT_I2O
This driver supports all of Adaptec's I2O based RAID controllers as
well as the DPT SmartRaid V cards. This is an Adaptec maintained
@@ -6941,10 +6991,10 @@
This is support for BusLogic MultiMaster and FlashPoint SCSI Host
Adapters. Consult the SCSI-HOWTO, available from
<http://www.linuxdoc.org/docs.html#howto>, and the files
- README.BusLogic and README.FlashPoint in drivers/scsi for more
- information. If this driver does not work correctly without
- modification, please contact the author, Leonard N. Zubkoff, by
- email to lnz@dandelion.com.
+ <file:drivers/scsi/README.BusLogic> and
+ <file:drivers/scsi/README.FlashPoint> for more information. If this
+ driver does not work correctly without modification, please contact
+ the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
You can also build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -7121,7 +7171,7 @@
Unless you have an NCR manufactured machine, the chances are that
you do not have this SCSI card, so say N.
-HP LASI SCSI support for 53c700
+HP LASI SCSI support for 53c700/710
CONFIG_SCSI_LASI700
This is a driver for the lasi baseboard in some parisc machines
which is based on the 53c700 chip. Will also support LASI subsystems
@@ -7186,7 +7236,7 @@
If your system has problems using this new major version of the
SYM53C8XX driver, you may switch back to driver version 1.
- Please read drivers/scsi/sym53c8xx_2/Documentation.txt for more
+ Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
information.
PCI DMA addressing mode
@@ -7727,7 +7777,7 @@
NCR53c406a SCSI support
CONFIG_SCSI_NCR53C406A
This is support for the NCR53c406a SCSI host adapter. For user
- configurable parameters, check out <file:drivers/scsi/NCR53c406.c>
+ configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
in the kernel source. Also read the SCSI-HOWTO, available from
<http://www.linuxdoc.org/docs.html#howto>.
@@ -7833,13 +7883,14 @@
say M here and read <file:Documentation/modules.txt>. The module
will be called megaraid.o.
-Intel/ICP (former GDT SCSI Disk Array) RAID Controller Support
+Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
CONFIG_SCSI_GDTH
Formerly called GDT SCSI Disk Array Controller Support.
This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
manufactured by Intel/ICP vortex (an Intel Company). It is documented
- in the kernel source in drivers/scsi/gdth.c and drivers/scsi/gdth.h.
+ in the kernel source in <file:drivers/scsi/gdth.c> and
+ <file:drivers/scsi/gdth.h.>
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -8122,7 +8173,7 @@
# say M here and read <file:Documentation/modules.txt>. The module
# will be called aic5800.o.
#
-OHCI-1394 support
+OHCI-1394 (Open Host Controller Interface) support
CONFIG_IEEE1394_OHCI1394
Enable this driver if you have an IEEE 1394 controller based on the
OHCI-1394 specification. The current driver is only tested with OHCI
@@ -8252,8 +8303,8 @@
Normally, your access provider has to support SLIP in order for you
to be able to use it, but there is now a SLIP emulator called SLiRP
- around (available via FTP (user: anonymous) from
- <ftp://metalab.unc.edu/pub/Linux/system/network/serial/>) which
+ around (available from
+ <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection. If
you plan to use SLiRP, make sure to say Y to CSLIP, below. The
NET-3-HOWTO, available from
@@ -8278,7 +8329,7 @@
on both ends. Ask your access provider if you are not sure and
answer Y, just in case. You will still be able to use plain SLIP. If
you plan to use SLiRP, the SLIP emulator (available from
- <ftp://metalab.unc.edu/pub/Linux/system/network/serial/>) which
+ <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection, you
definitely want to say Y here. The NET-3-HOWTO, available from
<http://www.linuxdoc.org/docs.html#howto>, explains how to configure
@@ -8415,7 +8466,7 @@
This driver requires a specially patched pppd daemon. The patch to
pppd, along with binaries of a patched pppd package can be found at:
- <http://www.shoshin.uwaterloo.ca/~mostrows>.
+ <http://www.shoshin.uwaterloo.ca/~mostrows/>.
Wireless LAN (non-hamradio)
CONFIG_NET_RADIO
@@ -8437,7 +8488,7 @@
Some user-level drivers for scarab devices which don't require
special kernel support are available from
- <ftp://shadow.cabi.net/pub/Linux>.
+ <ftp://shadow.cabi.net/pub/Linux/>.
STRIP (Metricom Starmode radio IP)
CONFIG_STRIP
@@ -8684,6 +8735,19 @@
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
+Asix AX88190 PCMCIA support
+CONFIG_PCMCIA_AXNET
+ Say Y here if you intend to attach an Asix AX88190-based PCMCIA
+ (PC-card) Fast Ethernet card to your computer. These cards are
+ nearly NE2000 compatible but need a separate driver due to a few
+ misfeatures.
+
+ 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 axnet_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
+
New Media PCMCIA support
CONFIG_PCMCIA_NMCLAN
Say Y here if you intend to attach a New Media Ethernet or LiveWire
@@ -8739,7 +8803,7 @@
The module will be called ibmtr_cs.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
-Xircom Tulip-like CardBus support
+Xircom Tulip-like CardBus support (old driver)
CONFIG_PCMCIA_XIRTULIP
This driver is for the Digital "Tulip" Ethernet CardBus adapters.
It should work with most DEC 21*4*-based chips/ethercards, as well
@@ -8783,12 +8847,6 @@
configure your card and that /etc/pcmcia/wireless.opts works :
<http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>
-Apple Airport support (built-in)
-CONFIG_APPLE_AIRPORT
- Enable support for the Apple Airport card (which is essentially a
- Lucent Orinoco card with a non-standard interface) built into some
- newer Apple Macintosh machines.
-
Hermes 802.11b in PLX9052 based PCI adaptor support
CONFIG_PLX_HERMES
Enable support for PCMCIA cards supported by the "Hermes" (aka
@@ -8870,7 +8928,8 @@
CONFIG_APPLE_AIRPORT
Say Y here to support the Airport 802.11b wireless Ethernet hardware
built into the Macintosh iBook and other recent PowerPC-based
- Macintosh machines.
+ Macintosh machines. This is essentially a Lucent Orinoco card with
+ a non-standard interface
Xircom Netwave AirSurfer wireless support
CONFIG_PCMCIA_NETWAVE
@@ -9015,7 +9074,7 @@
of the Cisco HDLC/PPP driver (syncppp.c).
The SyncLink WAN driver (in character devices) must also be enabled.
-FarSync T-Series support
+FarSync T-Series X.21 (and V.35/V.24) cards
CONFIG_FARSYNC
This driver supports the FarSync T-Series X.21 (and V.35/V.24) cards
from FarSite Communications Ltd.
@@ -9118,7 +9177,7 @@
the price of an external router. If you have one of those cards and
wish to use your Linux box as a WAN router, say Y here and also to
the WAN driver for your card, below. You will then need the
- wan-tools package which is available from <ftp://ftp.sangoma.com>.
+ wan-tools package which is available from <ftp://ftp.sangoma.com/>.
Read <file:Documentation/networking/wan-router.txt> for more
information.
@@ -9500,7 +9559,7 @@
up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more
information about the cards (including the pointer to the user-space
utilities). You can also read the comment at the top of the
- <file:drivers/net/cosa.c> for details about the cards and the driver
+ <file:drivers/net/wan/cosa.c> for details about the cards and the driver
itself.
The driver will be compiled as a module ( = code which can be
@@ -9512,7 +9571,7 @@
CONFIG_DSCC4
This is a driver for Etinc PCISYNC boards based on the Infineon
(ex. Siemens) DSCC4 chipset. It is supposed to work with the four
- ports card. Take a look at <http://www.cogenit.fr/dscc4>
+ ports card. Take a look at <http://www.cogenit.fr/dscc4/>
for further informations about the driver and his configuration.
The driver will be compiled as a module ( = code which can be
@@ -9539,7 +9598,7 @@
additional external hardware.
To change setting such as syncPPP vs cisco HDLC or clock source you
- will need lmcctl. It is available at <ftp://ftp.lanmedia.com>.
+ will need lmcctl. It is available at <ftp://ftp.lanmedia.com/>.
This code is also available as a module called lmc.o ( = code
which can be inserted in and removed from the running kernel
@@ -9584,12 +9643,12 @@
module will be called sbni.o).
You can find more information and last versions of drivers and
- utilities at <http://www.granch.ru>. If you have any question you
+ utilities at <http://www.granch.ru/>. If you have any question you
can send email to sbni@granch.ru.
Say N if unsure.
-SBNI Adapters Multiline feature
+SBNI multiple-line feature support
CONFIG_SBNI_MULTILINE
Schedule traffic for some parallel lines, via SBNI12 adapters.
If you have two computers connected with two parallel lines it's
@@ -9607,7 +9666,7 @@
Router".
You will need the wan-tools package which is available from
- <ftp://ftp.sangoma.com>. Read
+ <ftp://ftp.sangoma.com/>. Read
<file:Documentation/networking/wan-router.txt> for more information.
Note that the answer to this question won't directly affect the
@@ -9616,7 +9675,7 @@
Sangoma WANPIPE(tm) multiprotocol cards
CONFIG_VENDOR_SANGOMA
- WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com>)
+ WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com/>)
is a family of intelligent multiprotocol WAN adapters with data
transfer rates up to 4Mbps. They are also known as Synchronous
Data Link Adapters (SDLA) and are designated as S514-PCI or
@@ -9704,7 +9763,7 @@
Read <file:Documentation/networking/comx.txt> for help on
configuring and using COMX interfaces. Further info on these cards
- can be found at <http://www.itc.hu> or <info@itc.hu>.
+ can be found at <http://www.itc.hu/> or <info@itc.hu>.
You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
use this driver.
@@ -9798,8 +9857,8 @@
Cyclom 2X(tm) multiprotocol cards
CONFIG_CYCLADES_SYNC
- Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com> and
- <http://www.cyclades.com.br)> is an intelligent multiprotocol WAN
+ Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com/> and
+ <http://www.cyclades.com.br/>) is an intelligent multiprotocol WAN
adapter with data transfer rates up to 512 Kbps. These cards support
the X.25 and SNA related protocols. If you have one or more of these
cards, say Y to this option. The next questions will ask you about
@@ -9808,10 +9867,10 @@
While no documentation is available at this time please grab the
wanconfig tarball in
- <http://www.conectiva.com.br/~acme/cycsyn-devel> (with minor changes
+ <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
to make it compile with the current wanrouter include files; efforts
are being made to use the original package available at
- <ftp://ftp.sangoma.com>).
+ <ftp://ftp.sangoma.com/>).
Feel free to contact me or the cycsyn-devel mailing list at
acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
@@ -10288,15 +10347,7 @@
is a 10Mbit/sec Ethernet controller. Product overview and specs at
<http://www.national.com/pf/DP/DP83902A.html>.
-CompactFlash Connection Area
-CONFIG_CF_AREA5
- If your board has "Directly Connected" CompactFlash, You should
- select the area where your CF is connected to.
-
- - "Area5" if CompactFlash is connected to Area 5 (0x14000000)
- - "Area6" if it is connected to Area 6 (0x18000000)
-
- "Area6" will work for most boards. For ADX, select "Area5".
+ If unsure, say N.
3COM cards
CONFIG_NET_VENDOR_3COM
@@ -10643,7 +10694,7 @@
module, say M here and read <file:Documentation/modules.txt> as well
as <file:Documentation/networking/net-modules.txt>.
-EtherExpressPro support/EtherExpress 10 (i82595) support
+EtherExpressPro and EtherExpress 10 (i82595) support
CONFIG_EEXPRESS_PRO
If you have a network (Ethernet) card of this type, say Y. This
driver supports intel i82595{FX,TX} based boards. Note however
@@ -10787,10 +10838,7 @@
driver and as a module ( = code which can be inserted in and removed
from the running kernel whenever you want). If you want to compile
it as a module, say M here and read <file:Documentation/modules.txt>
- as well as <file:Documentation/networking/net-modules.txt>.
- If you plan to use more than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
- <ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini>. The only
+ as well as <file:Documentation/networking/net-modules.txt>. The only
currently supported card is the IBM LAN Adapter/A for Ethernet. It
will both support 16K and 32K memory windows, however a 32K window
gives a better security against packet losses. Usage of multiple
@@ -10914,6 +10962,13 @@
If unsure, say N.
+Use PCI shared memory for NIC registers
+CONFIG_TULIP_MMIO
+ Use PCI shared memory for the NIC registers, rather than going through
+ the Tulip's PIO (programmed I/O ports). Faster, but could produce
+ obscure bugs if your mainboard has memory controller timing issues.
+ If in doubt, say N.
+
Digi Intl. RightSwitch SE-X support
CONFIG_DGRS
This is support for the Digi International RightSwitch series of
@@ -10957,7 +11012,7 @@
CONFIG_FEALNX
Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
cards. Specifications and data at
- <http:www.myson.com.hk/mtd/datasheet>.
+ <http://www.myson.com.hk/mtd/datasheet/>.
ICL EtherTeam 16i/32 support
CONFIG_ETH16I
@@ -11001,10 +11056,21 @@
a module, say M here and read <file:Documentation/modules.txt> as
well as <file:Documentation/networking/net-modules.txt>.
+VIA Rhine MMIO support (EXPERIMENTAL)
+CONFIG_VIA_RHINE_MMIO
+ This instructs the driver to use PCI shared memory (MMIO) instead of
+ programmed I/O ports (PIO). Enabling this gives an improvement in
+ processing time in parts of the driver.
+
+ It is not known if this works reliably on all "rhine" based cards,
+ but it has been tested successfully on some DFE-530TX adapters.
+
+ If unsure, say N.
+
Davicom DM910x/DM980x support
CONFIG_DM9102
This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
- Davicom (<http://www.davicom.com.tw>). If you have such a network
+ Davicom (<http://www.davicom.com.tw/>). If you have such a network
(Ethernet) card, say Y. Some information is contained in the file
<file:Documentation/networking/dmfe.txt>.
@@ -11189,8 +11255,7 @@
Wake On Lan, and PCI 100/16/4 adapters.
If you have such an adapter, say Y and read the Token-Ring
- mini-HOWTO, available from
- <http://www.linuxdoc.org/docs.html#howto>.
+ mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -11199,15 +11264,14 @@
Also read <file:Documentation/networking/olympic.txt> or check the
Linux Token Ring Project site for the latest information at
- <http://www.linuxtr.net>.
+ <http://www.linuxtr.net/>.
IBM Lanstreamer chipset PCI adapter support
CONFIG_IBMLS
This is support for IBM Lanstreamer PCI Token Ring Cards.
If you have such an adapter, say Y and read the Token-Ring
- mini-HOWTO available via FTP (user:anonymous) from
- <ftp://metalab.unc/edu/pub/Linux/docs/HOWTO>.
+ mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a modules ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -11358,7 +11422,7 @@
say Y to "QoS and/or fair queueing" above.
To set up and configure shaper devices, you need the shapecfg
- program, available from <ftp://shadow.cabi.net/pub/Linux> in the
+ program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
shaper package.
This driver is also available as a module ( = code which can be
@@ -11619,7 +11683,7 @@
Say Y here only if you have two CD-ROM controller cards of this type
(usually only if you have more than four drives). You should enter
the parameters for the second, third and fourth interface card into
- <file:include/linux/sbpcd.h> before compiling the new kernel. Read
+ <file:drivers/cdrom/sbpcd.h> before compiling the new kernel. Read
the file <file:Documentation/cdrom/sbpcd>.
Matsushita/Panasonic, ... third CD-ROM controller support
@@ -11904,7 +11968,7 @@
<linux-mtd@lists.infradead.org> if you want to help to make it more
reliable.
-Common Flash Interface (CFI) support
+Detect flash chips by Common Flash Interface (CFI) probe
CONFIG_MTD_CFI
The Common Flash Interface specification was developed by Intel,
AMD and other flash manufactures that provides a universal method
@@ -11961,7 +12025,7 @@
If your flash chips are interleaved in fours - i.e. you have four
flash chips addressed by each bus cycle, then say 'Y'.
-# Choice: mtd_swap_data
+# Choice: mtd_data_swap
Flash cmd/query data swapping
CONFIG_MTD_CFI_NOSWAP
This option defines the way in which the CPU attempts to arrange
@@ -12101,7 +12165,7 @@
PNC-2000 is the name of Network Camera product from PHOTRON
Ltd. in Japan. It uses CFI-compliant flash.
-Flash chip mapping on RPXlite PPC board
+Flash chip mapping on RPXlite or CLLF PPC board
CONFIG_MTD_RPXLITE
The RPXLite PowerPC board has CFI-compliant chips mapped in
a strange sparse mapping. This 'mapping' driver supports that
@@ -12177,26 +12241,26 @@
allow a window into the flash. Both CFI and JEDEC probes are
called.
-Physical start location of flash mapping
+Physical start location of flash chip mapping
CONFIG_MTD_CSTM_MIPS_IXX_START
This is the physical memory location that the MTD driver will
use for the flash chips on your particular target board.
Refer to the memory map which should hopefully be in the
documentation for your board.
-Physical length of flash mapping
+Physical length of flash chip mapping
CONFIG_MTD_CSTM_MIPS_IXX_LEN
This is the total length that the MTD driver will use for the
flash chips on your particular board. Refer to the memory
map which should hopefully be in the documentation for your
board.
-Physical bus width of flash mapping
+Physical bus width of flash mapping in bytes
CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH
This is the total bus width of the mapping of the flash chips
on your particular board.
-Flash chip mapping on Mixcom piggyback card
+JEDEC Flash device mapped on Mixcom piggyback card
CONFIG_MTD_MIXMEM
This supports the paging arrangement for access to flash chips
on the MixCOM piggyback card, allowing the flash chip drivers
@@ -12205,14 +12269,14 @@
you probably want to enable this mapping driver. More info is at
<http://www.itc.hu/>.
-Flash chip mapping on Octagon 5066 SBC
+JEDEC Flash device mapped on Octagon 5066 SBC
CONFIG_MTD_OCTAGON
This provides a 'mapping' driver which supports the way in which
the flash chips are connected in the Octagon-5066 Single Board
Computer. More information on the board is available at
<http://www.octagonsystems.com/Products/5066/5066.html>.
-Flash chip mapping on Tempustech VMAX SBC301
+JEDEC Flash device mapped on Tempustech VMAX SBC301
CONFIG_MTD_VMAX
This provides a 'mapping' driver which supports the way in which
the flash chips are connected in the Tempustech VMAX SBC301 Single
@@ -12383,7 +12447,7 @@
allocating space from Linux's available memory. Otherwise, leave
this set to zero. Most people will want to leave this as zero.
-Flash chip mapping on the Flaga Digital Module
+CFI Flash device mapping on the Flaga Digital Module
CONFIG_MTD_CFI_FLAGADM
Mapping for the Flaga digital module. If you don´t have one, ignore
this setting.
@@ -12394,6 +12458,102 @@
NVRAM on the Momenco Ocelot board. If you have one of these boards
and would like access to either of these, say 'Y'.
+Support for absent chips in bus mapping
+CONFIG_MTD_ABSENT
+ This option enables support for a dummy probing driver used to
+ allocated placeholder MTD devices on systems that have socketed
+ or removable media. Use of this driver as a fallback chip probe
+ preserves the expected registration order of MTD device nodes on
+ the system regardless of media presence. Device nodes created
+ with this driver will return -ENODEV upon access.
+
+MTD emulation using block device
+CONFIG_MTD_BLKMTD
+ This driver allows a block device to appear as an MTD. It would
+ generally be used in the following cases:
+
+ Using Compact Flash as an MTD, these usually present themselves to
+ the system as an ATA drive.
+ Testing MTD users (eg JFFS2) on large media and media that might
+ be removed during a write (using the floppy drive).
+
+Cirrus CDB89712 evaluation board mappings
+CONFIG_MTD_CDB89712
+ This enables access to the flash or ROM chips on the CDB89712 board.
+ (This board has 8 MB of Intel Strataflash, a 128 byte boot ROM, and 48 KB of
+ internal SRAM. This driver provides MTD devices for all three components.)
+ If you have such a board, say 'Y'.
+
+Detect non-CFI AMD/JEDEC-compatible flash chips
+CONFIG_MTD_JEDECPROBE
+ This option enables JEDEC-style probing of flash chips which are not
+ compatible with the Common Flash Interface, but will use the common
+ CFI-targetted flash drivers for any chips which are identified which
+ are in fact compatible in all but the probe method. This actually
+ covers most AMD/Fujitsu-compatible chips, and will shortly cover also
+ non-CFI Intel chips (that code is in MTD CVS and should shortly be sent
+ for inclusion in Linus' tree)
+
+BIOS flash chip on Intel L440GX boards
+CONFIG_MTD_L440GX
+ Support for treating the BIOS flash chip on Intel L440GX motherboards
+ as an MTD device - with this you can reprogram your BIOS.
+
+ BE VERY CAREFUL.
+
+28F160xx flash driver for LART
+CONFIG_MTD_LART
+ This enables the flash driver for LART. Please note that you do
+ not need any mapping/chip driver for LART. This one does it all
+ for you, so go disable all of those if you enabled some of them (:
+
+Older (theoretically obsoleted now) drivers for non-CFI chips
+CONFIG_MTD_OBSOLETE_CHIPS
+ This option does not enable any code directly, but will allow you to
+ select some other chip drivers which are now considered obsolete,
+ because the generic CONFIG_JEDEC_PROBE code above should now detect
+ the chips which are supported by these drivers, and allow the generic
+ CFI-compatible drivers to drive the chips. Say 'N' here unless you have
+ already tried the CONFIG_JEDEC_PROBE method and reported its failure
+ to the MTD mailing list at <linux-mtd@lists.infradead.org>
+
+CFI Flash device mapped on Hitachi SolutionEngine
+CONFIG_MTD_SOLUTIONENGINE
+ This enables access to the flash chips on the Hitachi SolutionEngine and
+ similar boards. Say 'Y' if you are building a kernel for such a board.
+
+CFI Flash device mapped on TQM8XXL PPC board
+CONFIG_MTD_TQM8XXL
+ The TQM8xxL PowerPC board has up to two banks of CFI-compliant
+ chips, currently uses AMD one. This 'mapping' driver supports
+ that arrangement, allowing the CFI probe and command set driver
+ code to communicate with the chips on the TQM8xxL board. More at
+ <http://www.denx.de/embedded-ppc-en.html>.
+
+Darkness
+CONFIG_MEMORY_SET
+ This is an option about which you will never be asked a question.
+ Therefore, I conclude that you do not exist - go away.
+
+ There is a grue here.
+
+Physical memory size
+CONFIG_MEMORY_SIZE
+ This sets the default memory size assumed by your SH kernel. It can
+ be overridden as normal by the 'mem=' argument on the kernel command
+ line. If unsure, consult your board specifications or just leave it
+ as 0x00400000 which was the default value before this became
+ configurable.
+
+Cache and PCI noncoherent
+CONFIG_SH_PCIDMA_NONCOHERENT
+ Enable this option if your platform does not have a CPU cache which
+ remains coherent with PCI DMA. It is safest to say 'Y', although you
+ will see better performance if you can say 'N', because the PCI DMA
+ code will not have to flush the CPU's caches. If you have a PCI host
+ bridge integrated with your SH CPU, refer carefully to the chip specs
+ to see if you can say 'N' here. Otherwise, leave it as 'Y'.
+
USB (Universal Serial Bus) support
CONFIG_USB
Universal Serial Bus (USB) is a specification for a serial bus
@@ -12438,7 +12598,7 @@
If you have an APC UPS, say Y; otherwise say N.
-USB long timeout
+USB long timeout for slow-responding devices (some MGE Ellipse UPSes)
CONFIG_USB_LONG_TIMEOUT
This option makes the standard time out a bit longer. Basically,
some devices are just slow to respond, so this makes usb more
@@ -12579,7 +12739,7 @@
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 aiptek.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Use input layer for ADB devices
CONFIG_INPUT_ADBHID
@@ -12740,7 +12900,7 @@
CONFIG_USB_SERIAL_VISOR
Say Y here if you want to connect to your HandSpring Visor, Palm
m500 or m505 through its USB docking station. See
- <http://usbvisor.sourceforge.net> for more information on using this
+ <http://usbvisor.sourceforge.net/> for more information on using this
driver.
This code is also available as a module ( = code which can be
@@ -12776,7 +12936,7 @@
converter device. The implementation I have is called the USC-1000.
This driver has also be tested with the 245 and 232 devices.
- See http://ftdi-usb-sio.sourceforge.net for more
+ See <http://ftdi-usb-sio.sourceforge.net/> for more
information on this driver and the device.
This code is also available as a module ( = code which can be
@@ -13008,12 +13168,12 @@
The module will be called ov511.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-USB Communication Class Ethernet driver
+USB Communication Class Ethernet device support
CONFIG_USB_CDCETHER
This driver supports devices conforming to the Communication Device
Class Ethernet Control Model. This is used in some cable modems.
For more details on the specification, get the Communication Device
- Class specification from <http://www.usb.org>.
+ Class specification from <http://www.usb.org/>.
This driver should work with the following devices:
* Ericsson PipeRider (all variants)
@@ -13077,7 +13237,7 @@
The module will be called pegasus.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-USB KLSI KL5USB101-based Ethernet device support '
+USB KLSI KL5USB101-based Ethernet device support
CONFIG_USB_KAWETH
Say Y here if you want to use one of the following 10Mbps only
USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
@@ -13140,7 +13300,7 @@
Say Y here if you want to connect this type of still camera to your
computer's USB port. See <file:Documentation/usb/dc2xx.txt> for
more information; some non-Kodak cameras may also work with this
- driver, given application support (such as <http://www.gPhoto.org>).
+ driver, given application support (such as <http://www.gphoto.org/>).
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -13151,7 +13311,7 @@
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 <http://www.gphoto.org>).
+ and higher (look at <http://www.gphoto.org/>).
To use it create a device node with "mknod /dev/mustek c 180 32" and
configure it in your software.
@@ -13175,7 +13335,7 @@
Say Y here in order to have the USB Mass Storage code generate
verbose debugging messages.
-ISD-200 USB/ATA driver
+ISD-200 USB/ATA Bridge support
CONFIG_USB_STORAGE_ISD200
Say Y here if you want to use USB Mass Store devices based
on the In-Systems Design ISD-200 USB/ATA bridge.
@@ -13255,7 +13415,7 @@
DABUSB driver
CONFIG_USB_DABUSB
A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
- brought to you by the DAB-Team (<http://dab.in.tum.de>). This
+ brought to you by the DAB-Team (<http://dab.in.tum.de/>). This
driver can be taken as an example for URB-based bulk, control, and
isochronous transactions. URB's are explained in
<file:Documentation/usb/URB.txt>.
@@ -13295,7 +13455,7 @@
reader, details at <http://www.microtechint.com/zio/index.html>.
This driver treats the flash card as a removable storage device.
-Sandisk SDDR-09 SmartMedia reader support
+SanDisk SDDR-09 (and other SmartMedia) support
CONFIG_USB_STORAGE_SDDR09
Say Y here to include additional code to support the Sandisk SDDR-09
SmartMedia reader in the USB Mass Storage driver.
@@ -13493,7 +13653,7 @@
running UML to exchange packets with its host over one of the
host's Ethertap devices, such as /dev/tap0. Additional running
UMLs can use additional Ethertap devices, one per running UML.
- While the UML believes its on a (multi-device, broadcast) virtual
+ While the UML believes it's on a (multi-device, broadcast) virtual
Ethernet network, it's in fact communicating over a point-to-point
link with the host.
@@ -13578,7 +13738,7 @@
and work. SANE 1.0.4 or newer is needed to make use of your scanner.
This driver can be compiled as a module.
-HP 53xx and Minolta Dual Scanner support
+HP53xx and Minolta Dual Scanner support
CONFIG_USB_HPUSBSCSI
Say Y here if you want support for the HP 53xx series of scanners
and the Minolta Scan Dual. This driver is experimental.
@@ -13588,7 +13748,7 @@
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
+ 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
@@ -13617,14 +13777,14 @@
Reiserfs support
CONFIG_REISERFS_FS
Stores not just filenames but the files themselves in a balanced
- tree. Uses journaling.
+ tree. Uses journalling.
Balanced trees are more efficient than traditional file system
architectural foundations.
In general, ReiserFS is as fast as ext2, but is very efficient with
large directories and small files. Additional patches are needed
- for NFS and quotas, please see <http://www.reiserfs.org> for links.
+ for NFS and quotas, please see <http://www.reiserfs.org/> for links.
It is more easily extended to have features currently found in
database and keyword search systems than block allocation based file
@@ -13632,7 +13792,7 @@
plugins consistent with our motto ``It takes more than a license to
make source code open.''
- Read <http://www.reiserfs.org> to learn more about reiserfs.
+ Read <http://www.reiserfs.org/> to learn more about reiserfs.
Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
@@ -13660,15 +13820,6 @@
everyone but ReiserFS developers and people fine-tuning reiserfs or
tracing problems should say N.
-Publish some reiserfs-specific info under /proc/fs/reiserfs
-CONFIG_REISERFS_PROC_INFO
- Create under /proc/fs/reiserfs hierarchy of files, displaying
- various ReiserFS statistics and internal data on the expense of
- making your kernel or module slightly larger (+8K). This also increases
- amount of kernel memory required for each mount. Almost everyone
- but ReiserFS developers and people fine-tuning reiserfs or tracing
- problems should say NO.
-
Second extended fs support
CONFIG_EXT2_FS
This is the de facto standard Linux file system (method to organize
@@ -13698,10 +13849,10 @@
directories on ext2 file systems, use chattr ("man chattr").
Ext2fs partitions can be read from within DOS using the ext2tool
- command line tool package (available via FTP (user: anonymous) from
- <ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2>) and from
+ command line tool package (available from
+ <ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
within Windows NT using the ext2nt command line tool package from
- <ftp://metalab.unc.edu/pub/Linux/utils/dos>. Explore2fs is a
+ <ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
graphical explorer for ext2fs partitions which runs on Windows 95
and Windows NT and includes experimental write support; it is
available from
@@ -13715,13 +13866,13 @@
be compiled as a module, and so this could be dangerous. Most
everyone wants to say Y here.
-Ext3 journaling file system support (EXPERIMENTAL)
+Ext3 journalling file system support (EXPERIMENTAL)
CONFIG_EXT3_FS
- This is the journaling version of the Second extended file system
+ This is the journalling version of the Second extended file system
(often called ext3), the de facto standard Linux file system
(method to organize files on a storage device) for hard disks.
- The journaling code included in this driver means you do not have
+ The journalling code included in this driver means you do not have
to run e2fsck (file system checker) on your file systems after a
crash. The journal keeps track of any changes that were being made
at the time the system crashed, and can ensure that your file system
@@ -13749,7 +13900,7 @@
Journal Block Device support (JBD for ext3) (EXPERIMENTAL)
CONFIG_JBD
- This is a generic journaling layer for block devices. It is
+ This is a generic journalling layer for block devices. It is
currently used by the ext3 file system, but it could also be used to
add journal support to other file systems or block devices such as
RAID or LVM.
@@ -13835,9 +13986,14 @@
mainframe systems. Only the basic format is supported so far. If
you don't know what CMS is you probably don't want to know any more.
+# When the 2.5 version of configure.help goes away, the part of this that
+# duplicates Documentation/filesystems/tmpfs.txt can drop out.
Virtual memory file system support
CONFIG_TMPFS
Tmpfs is a file system which keeps all files in virtual memory.
+ Everything in tmpfs is temporary in the sense that no files will be
+ created on your hard drive. If you reboot, everything in tmpfs will
+ be lost.
In contrast to RAM disks, which get allocated a fixed amount of
physical RAM, tmpfs grows and shrinks to accommodate the files it
@@ -13864,6 +14020,8 @@
The initial permissions of the root directory can be set with the
mount option "mode".
+ See <file:Documentation/filesystems/tmpfs.txt> for details.
+
Simple RAM-based file system support
CONFIG_RAMFS
Ramfs is a file system which keeps all files in RAM. It allows
@@ -13901,7 +14059,7 @@
which allows for long filenames in unicode format (unicode is the
new 16 bit character code, successor to ASCII, which encodes the
characters of almost all languages of the world; see
- <http://www.unicode.org> for more information). Say Y here if you
+ <http://www.unicode.org/> for more information). Say Y here if you
want to be able to read Joliet CD-ROMs under Linux.
Transparent decompression extension
@@ -13986,7 +14144,7 @@
Linux, you can either use the DOS emulator DOSEMU, described in the
DOSEMU-HOWTO, available from
<http://www.linuxdoc.org/docs.html#howto>, or try dmsdosfs in
- <ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs>. If you
+ <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
intend to use dosemu with a non-compressed MSDOS partition, say Y
here) and MSDOS floppies. This means that file access becomes
transparent, i.e. the MSDOS files look and behave just like all
@@ -14161,8 +14319,9 @@
level IP autoconfiguration" above and to "Root file system on NFS"
below. You cannot compile this driver as a module in this case.
There are two packages designed for booting diskless machines over
- the net: netboot and etherboot, both available via FTP from
- <ftp://metalab.unc.edu/pub/Linux/system/boot/Ethernet/>.
+ the net: netboot, available from
+ <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
+ available from <http://ftp1.sourceforge.net/etherboot/>.
If you don't know what all this is about, say N.
@@ -14285,7 +14444,7 @@
a set of kernel modules that lets you run SCO, Xenix, Wyse,
UnixWare, Dell Unix and System V programs under Linux. It is
available via FTP (user: ftp) from
- <ftp://ftp.openlinux.org/pub/people/hch/linux-abi>).
+ <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
NOTE: that will work only for binaries from Intel-based systems;
PDP ones will have to wait until somebody ports Linux to -11 ;-)
@@ -14414,7 +14573,7 @@
automounter (amd), which is a pure user space daemon.
To use the automounter you need the user-space tools from
- <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4>; you also
+ <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
want to answer Y to "NFS file system support", below.
If you want to compile this as a module ( = code which can be
@@ -14445,7 +14604,7 @@
Journalling Flash File System (JFFS) support
CONFIG_JFFS_FS
- JFFS is the Journaling Flash File System developed by Axis
+ JFFS is the Journalling Flash File System developed by Axis
Communications in Sweden, aimed at providing a crash/powerdown-safe
file system for disk-less embedded devices. Further information is
available at (<http://developer.axis.com/software/jffs/>).
@@ -14478,6 +14637,11 @@
If reporting bugs, please try to have available a full dump of the
messages at debug level 1 while the misbehaviour was occurring.
+JFFS stats available in /proc filesystem
+CONFIG_JFFS_PROC_FS
+ Enabling this option will cause statistics from mounted JFFS file systems
+ to be made available to the user in the /proc/fs/jffs/ directory.
+
UFS file system support (read-only)
CONFIG_UFS_FS
BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
@@ -14562,7 +14726,7 @@
Say Y here if you would like to use hard disks under Linux which
were partitioned on a Macintosh.
-Windows' Logical Disk Manager (Dynamic Disk) support (EXPERIMENTAL)
+Windows Logical Disk Manager (Dynamic Disk) support (EXPERIMENTAL)
CONFIG_LDM_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned using Windows 2000's or XP's Logical Disk Manager.
@@ -14578,11 +14742,11 @@
XP.
Technical documentation to accompany this driver is available from:
- <http://linux-ntfs.sf.net/ldm>.
+ <http://linux-ntfs.sf.net/ldm/>.
If unsure, say N.
-Windows' LDM extra logging
+Windows LDM extra logging
CONFIG_LDM_DEBUG
Say Y here if you would like LDM to log verbosely. This could be
helpful if the driver doesn't work as expected and you'd like to
@@ -14706,7 +14870,6 @@
Note that the experimental "/dev file system support"
(CONFIG_DEVFS_FS) is a more general facility.
-# This is for Linus's tree
FreeVxFS file system support (VERITAS VxFS(TM) compatible)
CONFIG_VXFS_FS
FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
@@ -14725,25 +14888,6 @@
module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
-# This is for Alan's tree. Note the name difference.
-FreeVxFS file system support (VERITAS VxFS(TM) compatible)
-CONFIG_FREEVXFS_FS
- FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
- file system format. VERITAS VxFS(TM) is the standard file system
- of SCO UnixWare (and possibly others) and optionally available
- for Sunsoft Solaris, HP-UX and many other operating systems.
- Currently only readonly access is supported.
-
- NOTE: the file system type as used by mount(1), mount(2) and
- fstab(5) is 'vxfs' as it describes the filesystem format, not
- the actual driver.
-
- This file system is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module is called freevxfs.o. If you want to compile it as a
- module, say M here and read <file:Documentation/modules.txt>. If
- unsure, say N.
-
UnixWare slices support
CONFIG_UNIXWARE_DISKLABEL
Like some systems, UnixWare uses its own slice table inside a
@@ -14777,8 +14921,8 @@
Note: if you just want your box to act as an SMB *server* and make
files and printing services available to Windows clients (which need
to have a TCP/IP stack), you don't need to say Y here; you can use
- the program samba (available via FTP (user: anonymous) in
- <ftp://metalab.unc.edu/pub/Linux/system/network/samba>) for that.
+ the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
+ for that.
General information about how to connect Linux, Windows machines and
Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
@@ -14827,14 +14971,14 @@
client and server. Servers are currently user level, i.e. they need
no kernel support. Please read
<file:Documentation/filesystems/coda.txt> and check out the Coda
- home page <http://www.coda.cs.cmu.edu>.
+ home page <http://www.coda.cs.cmu.edu/>.
If you want to compile the coda client support as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called coda.o.
-InterMezzo file system support (experimental, replicating fs)
+InterMezzo file system support (replicating fs)
CONFIG_INTERMEZZO_FS
InterMezzo is a networked file system with disconnected operation
and kernel level write back caching. It is most often used for
@@ -14843,7 +14987,7 @@
If you say Y or M your kernel or module will provide InterMezzo
support. You will also need a file server daemon, which you can get
- from <http://www.inter-mezzo.org>.
+ from <http://www.inter-mezzo.org/>.
NCP file system support (to mount NetWare volumes)
CONFIG_NCP_FS
@@ -15414,6 +15558,7 @@
Enable Ethernet support via the Motorola MPC8xx serial
commmunications controller.
+# Choice: scc_ethernet
Ethernet on SCC1
CONFIG_SCC1_ENET
Use MPC8xx serial communications controller 1 to drive Ethernet
@@ -15495,7 +15640,7 @@
CONFIG_ADB_IOP
The I/O Processor (IOP) is an Apple custom IC designed to provide
intelligent support for I/O controllers. It is described at
- <http://www.angelfire.com/ca2/dev68k/iopdesc.html;> to enable direct
+ <http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
support for it, say 'Y' here.
Mac II style Apple Desktop Bus support
@@ -16190,7 +16335,7 @@
<file:Documentation/modules.txt>.
The module will be called i2c-dev.o.
-I2C /proc support
+I2C /proc interface (required for hardware sensors)
CONFIG_I2C_PROC
This provides support for i2c device entries in the /proc filesystem.
The entries will be found in /proc/sys/dev/sensors.
@@ -16204,9 +16349,7 @@
Say Y here if your machine has a bus mouse as opposed to a serial
mouse. Most people have a regular serial MouseSystem or
Microsoft mouse (made by Logitech) that plugs into a COM port
- (rectangular with 9 or 25 pins). These people say N here. If you
- have something else, read the Busmouse-HOWTO, available from
- <http://www.linuxdoc.org/docs.html#howto>, and say Y here.
+ (rectangular with 9 or 25 pins). These people say N here.
If you have a laptop, you either have to check the documentation or
experiment a bit to find out whether the trackball is a serial mouse
@@ -16271,8 +16414,8 @@
When using a PS/2 mouse, you can get problems if you want to use the
mouse both on the Linux console and under X. Using the "-R" option
of the Linux mouse managing program gpm (available from
- <ftp://metalab.unc.edu/pub/Linux/system/mouse>) solves this
- problem, or you can get the "mconv2" utility from the same location.
+ <ftp://gnu.systemy.it/pub/gpm/>) solves this problem, or you can get
+ the "mconv2" utility from <ftp://ibiblio.org/pub/Linux/system/mouse/>.
C&T 82C710 mouse port support (as on TI Travelmate)
CONFIG_82C710_MOUSE
@@ -16391,7 +16534,7 @@
Note that the Ftape-HOWTO is out of date (sorry) and documents the
older version 2.08 of this software but still contains useful
information. There is a web page with more recent documentation at
- <http://www.math1.rwth-aachen.de/~heine/ftape/>. This page
+ <http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page
always contains the latest release of the ftape driver and useful
information (backup software, ftape related patches and
documentation, FAQ). Note that the file system interface has
@@ -16427,7 +16570,7 @@
file <file:Documentation/ftape.txt> contains a short description of
the most important changes in the file system interface compared to
previous versions of ftape. The ftape home page
- <http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/> contains
+ <http://www.instmath.rwth-aachen.de/~heine/ftape/> contains
further information.
IMPORTANT NOTE: zftape can read archives created by previous
@@ -16670,7 +16813,7 @@
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 see <http://dri.sourceforge.net> for more
+ DMA transfers. Please see <http://dri.sourceforge.net/> for more
details. You should also select and configure AGP
(/dev/agpgart) support.
@@ -16925,8 +17068,8 @@
can be downloaded from:
<http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
- The ACPI mailing list may also be of interest:
- <http://phobos.fs.tum.de/acpi/index.html>.
+ The ACPI Sourceforge project may also be of interest:
+ <http://sf.net/projects/acpi/>
Enable ACPI 2.0 with errata 1.3
CONFIG_ACPI20
@@ -17136,9 +17279,9 @@
in the kernel source.
The watchdog is usually used together with the watchdog daemon
- which is available via FTP (user: anonymous) from
- <ftp://tsx-11.mit.edu/pub/linux/sources/sbin/>. This daemon can also
- monitor NFS connections and can reboot the machine when the process
+ which is available from
+ <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
+ also monitor NFS connections and can reboot the machine when the process
table is full.
If unsure, say N.
@@ -17212,7 +17355,7 @@
and if it does, it reboots your computer after a certain amount of
time. This driver is like the WDT501 driver but for different
hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC
- watchdog cards can be ordered from <http://www.berkprod.com>.
+ watchdog cards can be ordered from <http://www.berkprod.com/>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17321,23 +17464,24 @@
Say Y if you intend to run this kernel on a Toshiba portable.
Say N otherwise.
-Dell Inspiron 8000 support
+Dell laptop support
CONFIG_I8K
This adds a driver to safely access the System Management Mode
- of the CPU on the Dell Inspiron 8000. The System Management Mode
- is used to read cpu temperature and cooling fan status and to
- control the fans on the I8K portables.
-
- This driver has been tested only on the Inspiron 8000 but it may
- also work with other Dell laptops. You can force loading on other
- models by passing the parameter `force=1' to the module. Use at
- your own risk.
+ of the CPU on the Dell Inspiron and Latitude laptops. The System
+ Management Mode is used to read cpu temperature, cooling fan
+ status and Fn-keys status on Dell laptops. It can also be used
+ to switch the fans on and off.
+
+ The driver has been developed and tested on an Inspiron 8000
+ but it should work on any Dell Inspiron or Latitude laptop.
+ You can force loading on unsupported models by passing the
+ parameter `force=1' to the module. Use at your own risk.
+
+ For more information on this driver and for utilities that make
+ use of the module see the I8K Linux Utilities web site at:
+ <http://www.debian.org/~dz/i8k/>.
- For information on utilities to make use of this driver see the
- I8K Linux utilities web site at:
- <http://www.debian.org/~dz/i8k/>
-
- Say Y if you intend to run this kernel on a Dell Inspiron 8000.
+ Say Y if you intend to run this kernel on a Dell laptop.
Say N otherwise.
/dev/cpu/microcode - Intel IA32 CPU microcode support
@@ -17387,6 +17531,12 @@
You can compile this driver directly into the kernel, or use
it as a module. The module will be called sbc60xxwdt.o.
+Eurotech CPU-1220/1410 Watchdog Timer
+CONFIG_EUROTECH_WDT
+ Enable support for the watchdog timer on the Eurotech CPU-1220 and
+ CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
+ information are at <http://www.eurotech.it/>.
+
Enhanced Real Time Clock Support
CONFIG_RTC
If you say Y here and create a character special file /dev/rtc with
@@ -17446,7 +17596,6 @@
The module will be called nvram.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-# Linus tree only
Joystick support
CONFIG_JOYSTICK
If you have a joystick, 6dof controller, gamepad, steering wheel,
@@ -17454,18 +17603,17 @@
enable generic support for these controllers. You will also need to
say Y or M to at least one of the hardware specific drivers. This
will make the controllers available as /dev/input/jsX devices.
- Please read the file <file:Documentation/joystick.txt> which
+ Please read the file <file:Documentation/input/joystick.txt> which
contains more information and the location of the joystick package
that you'll need.
-# AC tree only
Game port support
CONFIG_INPUT_GAMEPORT
Gameport support is for the standard 15-pin PC gameport. If you
have a joystick, gamepad, gameport card, a soundcard with a gameport
or anything else that uses the gameport, say Y or M here and also to
at least one of the hardware specific drivers.
- Please read the file <file:Documentation/joystick.txt> which
+ Please read the file <file:Documentation/input/joystick.txt> which
contains more information and the location of the joystick package
that you'll need if you use the gameport with a joystick.
@@ -17478,7 +17626,7 @@
CONFIG_INPUT_NS558
Say Y here if you have an ISA or PnP gameport.
For more information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17489,7 +17637,7 @@
CONFIG_INPUT_LIGHTNING
Say Y here if you have a PDPI Lightning 4 gamecard. For more
information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17511,7 +17659,7 @@
CONFIG_INPUT_PCIGAME
Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
card. For more information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17522,7 +17670,7 @@
CONFIG_INPUT_EMU10K1
Say Y here if you have a SoundBlaster Live! card and want to use
its gameport. For more information on how to use the driver
- please read <file:Documentation/joystick.txt>.
+ please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17537,7 +17685,7 @@
additional hats and buttons compatible with CH Flightstick Pro,
ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
joysticks. For more information on how to use the driver please
- read <file:Documentation/joystick.txt>.
+ read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17548,7 +17696,7 @@
CONFIG_INPUT_A3D
Say Y here if you have an FPGaming or MadCatz controller using the
A3D protocol over the PC gameport. For more information on how to
- use the driver please read <file:Documentation/joystick.txt>.
+ use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17559,7 +17707,7 @@
CONFIG_INPUT_ADI
Say Y here if you have a Logitech controller using the ADI
protocol over the PC gameport. For more information on how to use
- the driver please read <file:Documentation/joystick.txt>.
+ the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17570,7 +17718,7 @@
CONFIG_INPUT_COBRA
Say Y here if you have a Creative Labs Blaster Cobra gamepad.
For more information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17581,7 +17729,7 @@
CONFIG_INPUT_GF2K
Say Y here if you have a Genius Flight2000 or MaxFighter digitally
communicating joystick or gamepad. For more information on how to
- use the driver please read <file:Documentation/joystick.txt>.
+ use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17592,7 +17740,7 @@
CONFIG_INPUT_GRIP
Say Y here if you have a Gravis controller using the GrIP protocol
over the PC gameport. For more information on how to use the driver
- please read <file:Documentation/joystick.txt>.
+ please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17603,7 +17751,7 @@
CONFIG_INPUT_INTERACT
Say Y hereif you have an InterAct gameport or joystick
communicating digitally over the gameport. For more information on
- how to use the driver please read <file:Documentation/joystick.txt>.
+ how to use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17615,7 +17763,7 @@
Say Y here if you have a ThrustMaster controller using the
DirectConnect (BSP) protocol over the PC gameport. For more
information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17626,7 +17774,7 @@
CONFIG_INPUT_SIDEWINDER
Say Y here if you have a Microsoft controller using the Digital
Overdrive protocol over PC gameport. For more information on how to
- use the driver please read <file:Documentation/joystick.txt>.
+ use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17638,7 +17786,7 @@
Say Y here and to the Serial port input line discipline option if
you plan to use a joystick that communicates over the serial (COM)
port. For more information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17649,7 +17797,7 @@
CONFIG_INPUT_SERPORT
Say Y here if you plan to use a joystick that communicates over the
serial (COM) port. For more information on how to use the driver
- please read <file:Documentation/joystick.txt>.
+ please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17660,7 +17808,7 @@
CONFIG_INPUT_WARRIOR
Say Y here if you have a Logitech WingMan Warrior joystick connected
to your computer's serial port. For more information on how to use
- the driver please read <file:Documentation/joystick.txt>.
+ the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17671,7 +17819,7 @@
CONFIG_INPUT_MAGELLAN
Say Y here if you have a Magellan or Space Mouse 6DOF controller
connected to your computer's serial port. For more information on
- how to use the driver please read <file:Documentation/joystick.txt>.
+ how to use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17683,7 +17831,7 @@
Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
controller connected to your computer's serial port. For more
information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17694,7 +17842,7 @@
CONFIG_INPUT_SPACEBALL
Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
connected to your computer's serial port. For more information on
- how to use the driver please read <file:Documentation/joystick.txt>.
+ how to use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17705,7 +17853,7 @@
CONFIG_INPUT_STINGER
Say Y here if you have a Gravis Stinger connected to one of your
serial ports. For more information on how to use the driver please
- read <file:Documentation/joystick.txt>.
+ read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17716,7 +17864,7 @@
CONFIG_INPUT_IFORCE_232
Say Y here if you have an I-Force joystick or steering wheel
connected to your serial (COM) port. For more information on how
- to use the driver please read <file:Documentation/joystick.txt>.
+ to use the driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17727,7 +17875,7 @@
CONFIG_INPUT_IFORCE_USB
Say Y here if you have an I-Force joystick or steering wheel
connected to your USB port. For more information on how to use the
- driver please read <file:Documentation/joystick.txt>.
+ driver please read <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17740,8 +17888,8 @@
gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
Commodore, Amstrad CPC joystick connected to your parallel port.
For more information on how to use the driver please read
- <file:Documentation/joystick.txt> and
- <file:Documentation/joystick-parport.txt>.
+ <file:Documentation/input/joystick.txt> and
+ <file:Documentation/input/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17755,8 +17903,8 @@
Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
Commodore, Amstrad CPC joystick connected to your parallel port.
For more information on how to use the driver please read
- <file:Documentation/joystick.txt> and
- <file:Documentation/joystick-parport.txt>.
+ <file:Documentation/input/joystick.txt> and
+ <file:Documentation/input/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17768,8 +17916,8 @@
Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
and want to use it with Multisystem -- Atari, Amiga, Commodore,
Amstrad CPC joystick. For more information on how to use the driver
- please read <file:Documentation/joystick.txt> and
- <file:Documentation/joystick-parport.txt>.
+ please read <file:Documentation/input/joystick.txt> and
+ <file:Documentation/input/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17780,7 +17928,7 @@
CONFIG_INPUT_AMIJOY
Say Y here if you have an Amiga with a digital joystick connected
to it. For more information on how to use the driver please read
- <file:Documentation/joystick.txt>.
+ <file:Documentation/input/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -18353,7 +18501,7 @@
questions.
Read the <file:Documentation/sound/README.OSS> file and the head of
- <file:drivers/sound/lowlevel/aedsp16.c> as well as
+ <file:drivers/sound/aedsp16.c> as well as
<file:Documentation/sound/AudioExcelDSP16> to get more information
about this driver and its configuration.
@@ -18412,12 +18560,20 @@
or the CMI8378 chipset. Data on these chips are available at
<http://www.cmedia.com.tw/>.
+ A userspace utility to control some internal registers of these
+ chips is available at
+ <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
+
Support CMI8738 based audio cards
CONFIG_SOUND_CMPCI_CM8738
Say Y or M if you have a PCI sound card using the CMI8338
or the CMI8378 chipset. Data on this chip is available at
<http://www.cmedia.com.tw/doc8738.htm>.
+ A userspace utility to control some internal registers of these
+ chips is available at
+ <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
+
Enable joystick
CONFIG_SOUND_CMPCI_JOYSTICK
Say here in order to enable the joystick port on a sound crd using
@@ -18435,13 +18591,19 @@
"The 8738 Audio SPDIF In/Out Technical Data" on the technical
support page at <http://www.cmedia.com.tw/>.
+ A userspace utility to control even more internal registers of these
+ chips is available at
+ <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
+ This package will among other things help you enable SPDIF
+ out/in/loop/monitor.
+
Creative SBLive! (EMU10K1) based PCI sound cards
CONFIG_SOUND_EMU10K1
Say Y or M if you have a PCI sound card using the EMU10K1 chipset,
such as the Creative SBLive!, SB PCI512 or Emu-APS.
For more information on this driver and the degree of support for the
- different card models please check <http://opensource.creative.com>.
+ different card models please check <http://opensource.creative.com/>.
It is now possible to load dsp microcode patches into the EMU10K1
chip. These patches are used to implement real time sound
@@ -18450,7 +18612,7 @@
Userspace tools to create new patches and load/unload them can be
found at <http://opensource.creative.com/dist.html>.
-Creative EMU10K1 MIDI
+Creative SBLive! (EMU10K1) MIDI
CONFIG_MIDI_EMU10K1
Say Y if you want to be able to use the OSS /dev/sequencer
interface. This code is still experimental.
@@ -18674,7 +18836,7 @@
Support for ITE 8172G board
CONFIG_MIPS_ITE8172
- Ths is an evaluation board made by ITE (http://www.ite.com.tw/)
+ Ths is an evaluation board made by ITE <http://www.ite.com.tw/>
with ATX form factor that utilizes a MIPS R5000 to work with its
ITE8172G companion internet appliance chip. The MIPS core can be
either a NEC Vr5432 or QED RM5231. Say Y here if you wish to build
@@ -18703,20 +18865,21 @@
website at <http://www.realitydiluted.com/projects/nino/index.html>
will have more information.
-Model-500/510
-CONFIG_NINO_16MB
- Say Y here to build a kernel specifically for Nino 500/501 color
- Palm PCs from Philips (INCOMPLETE).
+# Choice: nino_model
+CONFIG_NINO_4MB
+ Say Y here to build a kernel specifically for Nino Palm PCs with
+ 4MB of memory. These include models 300/301/302/319.
Model-200/210/312/320/325/350/390
CONFIG_NINO_8MB
Say Y here to build a kernel specifically for Nino Palm PCs with
8MB of memory. These include models 200/210/312/320/325/350/390.
+Model-500/510
+CONFIG_NINO_16MB
+ Say Y here to build a kernel specifically for Nino 500/501 color
+ Palm PCs from Philips (INCOMPLETE).
Model-300/301/302/319
-CONFIG_NINO_4MB
- Say Y here to build a kernel specifically for Nino Palm PCs with
- 4MB of memory. These include models 300/301/302/319.
Low-level debugging
CONFIG_LL_DEBUG
@@ -18740,6 +18903,26 @@
hardware debugging with a logic analyzer and need to see all traffic
on the bus.
+AU1000 serial console
+CONFIG_AU1000_SERIAL_CONSOLE
+ If you have an Alchemy AU1000 processor (MIPS based) and you want
+ to use a console on a serial port, say Y. Otherwise, say N.
+
+AU1000 serial support
+CONFIG_AU1000_UART
+ If you have an Alchemy AU1000 processor (MIPS based) and you want
+ to use serial ports, say Y. Otherwise, say N.
+
+AU1000 ethernet controller on SGI MIPS system
+CONFIG_MIPS_AU1000_ENET
+ If you have an Alchemy Semi AU1000 ethernet controller
+ on an SGI MIPS system, say Y. Otherwise, say N.
+
+WD93 SCSI Controller on SGI MIPS system
+CONFIG_SGIWD93_SCSI
+ If you have a Western Digital WD93 SCSI controller on
+ an SGI MIPS system, say Y. Otherwise, say N.
+
Magic System Request Key support
CONFIG_MAGIC_SYSRQ
If you say Y here, you will have some control over the system even
@@ -18933,6 +19116,12 @@
Enable this if you like to use ISDN in US on a NI1 basic rate
interface.
+# 2.4 tree only
+Maximum number of cards supported by HiSax
+CONFIG_HISAX_MAX_CARDS
+ This is used to allocate a driver-internal structure array with one
+ entry for each HiSax card on your system.
+
Teles 16.0/8.0
CONFIG_HISAX_16_0
This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
@@ -19162,7 +19351,7 @@
This enables the PCMCIA client driver for the Sedlbauer Speed Star
and Speed Star II cards.
-ST5481 USB ISDN adapter
+ST5481 USB ISDN modem
CONFIG_HISAX_ST5481
This enables the driver for ST5481 based USB ISDN adapters,
e.g. the BeWan Gazel 128 USB
@@ -19188,7 +19377,7 @@
can be inserted in and removed from the running kernel whenever you
want, details in <file:Documentation/modules.txt>); the module will
be called sc.o. See <file:Documentation/isdn/README.sc> and
- <http://www.spellcast.com> for more information.
+ <http://www.spellcast.com/> for more information.
Eicon active card support
CONFIG_ISDN_DRV_EICON
@@ -19330,7 +19519,7 @@
This enables support for the Auvertech TurboPAM ISDN-card.
For running this card, additional firmware is necessary, which has
to be downloaded into the card using a utility which is distributed
- separately from the Auvertech's web site: <http://www.auvertech.fr>.
+ separately from the Auvertech's web site: <http://www.auvertech.fr/>.
Please redirect all support questions to support@auvertech.fr.
@@ -19525,7 +19714,7 @@
It was designed as a replacement for cables and other short-range
technologies like IrDA. Bluetooth operates in personal area range
that typically extends up to 10 meters. More information about
- Bluetooth can be found at <http://www.bluetooth.com>.
+ Bluetooth can be found at <http://www.bluetooth.com/>.
Linux Bluetooth subsystem consist of several layers:
HCI Core (device and connection manager, scheduler)
@@ -19538,7 +19727,7 @@
To use Linux Bluetooth subsystem, you will need several user-space
utilities like hciconfig and hcid. These utilities and updates to
Bluetooth kernel modules are provided in the BlueZ package.
- For more information, see <http://bluez.sf.net>.
+ For more information, see <http://bluez.sourceforge.net/>.
If you want to compile HCI Core as module (hci.o) say M here.
@@ -19580,62 +19769,6 @@
# The following options are for Linux when running on the Hitachi
# SuperH family of RISC microprocessors.
-CPU Selection
-CONFIG_CPU_SUBTYPE_SH7707
- This is the type of your Hitachi SuperH processor. This information is
- used for optimizing and configuration purposes.
-
- - "SH7707" for SH7707
- - "SH7708" for SH7708, SH7708S, SH7708R
- - "SH7709" for SH7707, SH7709, SH7709A, and SH7729.
- - "SH7750" for SH7750, SH7750S
- - "SH7751" for SH7751
- - "ST40STB1" for ST40STB1
-
-Target machine selection
-CONFIG_SH_GENERIC
- This is machine type of your target.
-
- - "Generic" for Generic kernel which might support all of them
- - "SolutionEngine" for Hitachi SolutionEngine (7709A, 7750, 7750S)
- - "SolutionEngine7751" for Hitachi SolutionEngine (7751)
- - "STB1_Harp" for STMicroelectronics HARP
- - "STB1_Overdrive" for STMicroelectronics Overdrive
- - "HP620" for HP 'Jornada' 620
- - "HP680" for HP 'Jornada' 680
- - "HP690" for HP 'Jornada' 690
- - "CqREEK" for CQ Publishing CqREEK SH-4
- - "DMIDA" for DMIDA, industrial data assistant
- - "EC3104" for Compaq Aero 8000
- - "Dreamcast" for SEGA Dreamcast
- - "CAT68701" for CAT 68701 Evaluation Board (SH7708)
- - "BigSur" for Big Sur Evaluation Board
- - "SH2000" for SH2000 Evaluation Board (SH7709A)
- - "ADX" for A&D ADX
- - "BareCPU" for Bare CPU board such as CqREEK SH-3
-
- If unsure, select "BareCPU".
-
-Physical memory start address
-CONFIG_MEMORY_START
- Computers built with Hitachi SuperH processors always
- map the ROM starting at address zero. But the processor
- does not specify the range that RAM takes. RAM is usually
- mapped starting at 0c000000, but it may be elsewhere.
-
- You should set this value to the address of the lowest
- RAM location.
-
- A value of 0c000000 will work for most boards.
-
-Directly Connected Compact Flash support
-CONFIG_CF_ENABLER
- If your board has "Directly Connected" CompactFlash at area 5 or 6,
- you may want to enable this option. Then, you can use CF as
- primary IDE drive (only tested for SanDisk).
-
- If in doubt, press "n".
-
SuperH RTC support
CONFIG_SH_RTC
Selecting this option will allow the Linux kernel to emulate
@@ -19650,38 +19783,7 @@
If unsure, say N.
-SuperH SCI (serial) support
-CONFIG_SH_SCI
- Selecting this option will allow the Linux kernel to transfer
- data over SCI (Serial Communication Interface) and/or SCIF
- which are built into the Hitachi SuperH processor.
-
- If unsure, say N.
-
-Use LinuxSH standard BIOS
-CONFIG_SH_STANDARD_BIOS
- Say Y here if your target has the gdb-sh-stub package from
- www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH
- or EPROM. The kernel will use standard BIOS calls during boot
- for various housekeeping tasks. Note this does not work with
- WindowsCE machines. If unsure, say N.
-
-Early printk support
-CONFIG_SH_EARLY_PRINTK
- If you say Y here, the kernel printk routine will begin output to
- the console much earlier in the boot process, before the serial
- console is initialised, instead of buffering output. Standard
- LinuxSH BIOS calls are used for the output. This helps when
- debugging fatal problems early in the boot sequence. This is only
- useful for kernel hackers. If unsure, say N.
-
-National Semiconductor DP83902AV 'ST-NIC' support
-CONFIG_STNIC
- If you have a network adaptor with National Semiconductor DP83902AV,
- say Y or M (for module).
-
- If unsure, say N.
-
+# Choice: cf_area
CompactFlash Connection Area
CONFIG_CF_AREA5
If your board has "Directly Connected" CompactFlash, You should
@@ -19763,6 +19865,12 @@
Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
emulation.
+Q40/Q60 IDE interface support
+CONFIG_BLK_DEV_Q40IDE
+ Enable the on-board IDE controller in the Q40/Q60. This should
+ normally be on; disable it only if you are running a custom hard
+ drive subsystem through an expansion card.
+
Sun 3 support
CONFIG_SUN3
This option enables support for the Sun 3 series of workstations.
@@ -20371,7 +20479,7 @@
If in doubt, say N.
-# Choice: Machine type
+# Choice: ppc4xxtype
Oak
CONFIG_OAK
Select Oak if you have an IBM 403GCX "Oak" Evaluation Board.
@@ -20416,13 +20524,14 @@
If in doubt, say N here.
-MPC8xx IDE support
+MPC8xx direct IDE support on PCMCIA port
CONFIG_BLK_DEV_MPC8xx_IDE
This option provides support for IDE on Motorola MPC8xx Systems.
Please see 'Type of MPC8xx IDE interface' for details.
If unsure, say N.
+# Choice: mpc8xxtype
Type of MPC8xx IDE interface
CONFIG_IDE_8xx_PCCARD
Select how the IDE devices are connected to the MPC8xx system:
@@ -20483,7 +20592,7 @@
<http://www.synergymicro.com/PressRel/97_10_15.html>.
Select APUS if configuring for a PowerUP Amiga. More information is
- available at: <http://linux-apus.sourceforge.net>.
+ available at: <http://linux-apus.sourceforge.net/>.
Synergy-Gemini
CONFIG_GEMINI
@@ -20495,124 +20604,9 @@
CONFIG_APUS
Select APUS if configuring for a PowerUP Amiga.
More information is available at:
- <http://linux-apus.sourceforge.net>.
-
-Embedded 8xx Board Type
-CONFIG_RPXLITE
- RPX-Lite:
- Embedded Planet RPX Lite
-
- RPX-Classic:
- Embedded Planet RPX Classic Low-fat.
-
- BSE-IP:
- Bright Star Engineering ip-Engine.
-
- TQM823L:
- TQM850L:
- TQM855L:
- TQM860L:
- MPC8xx based family of mini modules, half credit card size,
- up to 64 MB of RAM, 8 MB Flash, (Fast) Ethernet, 2 x serial ports,
- 2 x CAN bus interface, ...
- Manufacturer: TQ Components, www.tq-group.de
- Date of Release: October (?) 1999
- End of Life: not yet :-)
- URL:
- - module: http://www.denx.de/PDF/TQM8xxLHWM201.pdf
- - starter kit: http://www.denx.de/PDF/STK8xxLHWM201.pdf
- - images: http://www.denx.de/embedded-ppc-en.html
-
- FPS850L:
- FingerPrint Sensor System (based on TQM850L)
- Manufacturer: IKENDI AG, http://www.ikendi.com/
- Date of Release: November 1999
- End of life: end 2000 ?
- URL: see TQM850L
-
- SPD823TS:
- MPC823 based board used in the "Tele Server" product
- Manufacturer: Speech Design, http://www.speech-design.de/
- Date of Release: Mid 2000 (?)
- End of life: -
- URL: http://www.speech-design.de/
- select "English", then "Teleteam Solutions", then "TeleServer"
+ <http://linux-apus.sourceforge.net/>.
- IVMS8:
- MPC860 based board used in the "Integrated Voice Mail System",
- Small Version (8 voice channels)
- Manufacturer: Speech Design, http://www.speech-design.de/
- Date of Release: December 2000 (?)
- End of life: -
- URL: http://www.speech-design.de/
-
- IVML24:
- MPC860 based board used in the "Integrated Voice Mail System",
- Large Version (24 voice channels)
- Manufacturer: Speech Design, http://www.speech-design.de/
- Date of Release: March 2001 (?)
- End of life: -
- URL: http://www.speech-design.de/
-
- SM850:
- Service Module (based on TQM850L)
- Manufacturer: Dependable Computer Systems, http://www.decomsys.com/
- Date of Release: end 2000 (?)
- End of life: mid 2001 (?)
- URL: http://www.tz-mikroelektronik.de/ServiceModule/index.html
-
- HERMES:
- Hermes-Pro ISDN/LAN router with integrated 8 x hub
- Manufacturer: Multidata Gesellschaft für Datentechnik und Informatik
- http://www.multidata.de/
- Date of Release: 2000 (?)
- End of life: -
- URL: http://www.multidata.de/english/products/hpro.htm
-
- IP860:
- VMEBus IP (Industry Pack) carrier board with MPC860
- Manufacturer: MicroSys GmbH, http://www.microsys.de/
- Date of Release: ?
- End of life: -
- URL: http://www.microsys.de/html/ip860.html
-
- PCU_E:
- PCU = Peripheral Controller Unit, Extended
- Manufacturer: Siemens AG, ICN (Information and Communication Networks)
- http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html
- Date of Release: April 2001
- End of life: August 2001
- URL: n. a.
-
-Embedded 82xx Board Type
-CONFIG_EST8260
- EST8260: Wind River System, Inc. EST SBC8260
-
- TQM8260:
- MPC8260 based module, little larger than credit card,
- up to 128 MB global + 64 MB local RAM, 32 MB Flash,
- 32 kB EEPROM, 256 kB L@ Cache, 10baseT + 100baseT Ethernet,
- 2 x serial ports, ...
- Manufacturer: TQ Components, www.tq-group.de
- Date of Release: June 2001
- End of Life: not yet :-)
- URL: http://www.denx.de/PDF/TQM82xx_SPEC_Rev005.pdf
-
- PM826:
- Modular system with MPC8260 CPU
- Manufacturer: MicroSys GmbH, http://www.microsys.de/
- Date of Release: mid 2001
- End of life: -
- URL: http://www.microsys.de/html/pm826.html
-
- CU824:
- VMEBus Board with PCI extension with MPC8240 CPU
- Manufacturer: MicroSys GmbH, http://www.microsys.de/
- Date of Release: early 2001 (?)
- End of life: -
- URL: http://www.microsys.de/html/cu824.html
-
-AltiVec Kernel Support
+AltiVec kernel support
CONFIG_ALTIVEC
This option enables kernel support for the Altivec extensions to the
PowerPC processor. The kernel currently supports saving and restoring
@@ -20684,26 +20678,97 @@
change the screen brightness.
# Choice: ppc8xxtype
-RPX-Lite
+Embedded 8xx Board Type
CONFIG_RPXLITE
Single-board computers based around the PowerPC MPC8xx chips and
intended for embedded applications. The following types are
supported:
- RPX-Lite -- PC104 form-factor SBC based on the MPC823
- RPX-Classic -- Credit-card-size SBC based on the MPC 860
- BSE-IP -- Bright Star Engineering BSE-IP SBC
- TQM823L -- TQM823L SBC from TQ Components
- TQM850L -- TQM850L SBC from TQ Components
- TQM855L -- TQM855L SBC from TQ Components
- TQM860L -- TQM860L SBC from TQ Components
- FPS850L -- FingerPrint Sensor from TQ Components
- TQM860 -- TQM860 SBC from IKENDI AG
- SPD823TS -- Speech Design TeleServer from Speech Design
- IVMS8 -- Integrated VoiceMail SBC from Speech Design
- SM850 -- Service Module 850 from Dependable Computer Systems
- MBX -- MBX821 and MBX860 SBCs
- Wincept -- Wincept SBCs for thin-client machines
+ RPX-Lite:
+ Embedded Planet RPX Lite. PC104 form-factor SBC based on the MPC823.
+
+ RPX-Classic:
+ Embedded Planet RPX Classic Low-fat. Credit-card-size SBC based on
+ the MPC 860
+
+ BSE-IP:
+ Bright Star Engineering ip-Engine.
+
+ TQM823L:
+ TQM850L:
+ TQM855L:
+ TQM860L:
+ MPC8xx based family of mini modules, half credit card size,
+ up to 64 MB of RAM, 8 MB Flash, (Fast) Ethernet, 2 x serial ports,
+ 2 x CAN bus interface, ...
+ Manufacturer: TQ Components, www.tq-group.de
+ Date of Release: October (?) 1999
+ End of Life: not yet :-)
+ URL:
+ - module: <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>
+ - starter kit: <http://www.denx.de/PDF/STK8xxLHWM201.pdf>
+ - images: <http://www.denx.de/embedded-ppc-en.html>
+
+ FPS850L:
+ FingerPrint Sensor System (based on TQM850L)
+ Manufacturer: IKENDI AG, <http://www.ikendi.com/>
+ Date of Release: November 1999
+ End of life: end 2000 ?
+ URL: see TQM850L
+
+ SPD823TS:
+ MPC823 based board used in the "Tele Server" product
+ Manufacturer: Speech Design, <http://www.speech-design.de/>
+ Date of Release: Mid 2000 (?)
+ End of life: -
+ URL: <http://www.speech-design.de/>
+ select "English", then "Teleteam Solutions", then "TeleServer"
+
+ IVMS8:
+ MPC860 based board used in the "Integrated Voice Mail System",
+ Small Version (8 voice channels)
+ Manufacturer: Speech Design, <http://www.speech-design.de/>
+ Date of Release: December 2000 (?)
+ End of life: -
+ URL: <http://www.speech-design.de/>
+
+ IVML24:
+ MPC860 based board used in the "Integrated Voice Mail System",
+ Large Version (24 voice channels)
+ Manufacturer: Speech Design, <http://www.speech-design.de/>
+ Date of Release: March 2001 (?)
+ End of life: -
+ URL: <http://www.speech-design.de/>
+
+ SM850:
+ Service Module (based on TQM850L)
+ Manufacturer: Dependable Computer Systems, <http://www.decomsys.com/>
+ Date of Release: end 2000 (?)
+ End of life: mid 2001 (?)
+ URL: <http://www.tz-mikroelektronik.de/ServiceModule/index.html>
+
+ HERMES:
+ Hermes-Pro ISDN/LAN router with integrated 8 x hub
+ Manufacturer: Multidata Gesellschaft für Datentechnik und Informatik
+ <http://www.multidata.de/>
+ Date of Release: 2000 (?)
+ End of life: -
+ URL: <http://www.multidata.de/english/products/hpro.htm>
+
+ IP860:
+ VMEBus IP (Industry Pack) carrier board with MPC860
+ Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
+ Date of Release: ?
+ End of life: -
+ URL: <http://www.microsys.de/html/ip860.html>
+
+ PCU_E:
+ PCU = Peripheral Controller Unit, Extended
+ Manufacturer: Siemens AG, ICN (Information and Communication Networks)
+ <http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
+ Date of Release: April 2001
+ End of life: August 2001
+ URL: n. a.
RPX-Classic
CONFIG_RPXCLASSIC
@@ -20831,7 +20896,7 @@
# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
# Date of Release: early 2001 (?)
# End of life: -
-# URL: <http://www.microsys.de/html/cu824.html
+# URL: <http://www.microsys.de/html/cu824.html>
#
# PM826:
# Modular system with MPC8260 CPU
@@ -20850,13 +20915,39 @@
# End of life: -
# URL: n. a.o
-Support for EST8260
+# Choice: ppc82xxtype
+Embedded 82xx Board Type
CONFIG_EST8260
- The EST8260 is a single-board computer manufactured by Wind River
- Systems, Inc. (formerly Embedded Support Tools Corp.) and based on
- the MPC8260. Wind River Systems has a website at
- <http://www.windriver.com/>, but the EST8260 cannot be found on it
- and has probably been discontinued or rebadged.
+ EST8260:
+ The EST8260 is a single-board computer manufactured by Wind River
+ Systems, Inc. (formerly Embedded Support Tools Corp.) and based on
+ the MPC8260. Wind River Systems has a website at
+ <http://www.windriver.com/>, but the EST8260 cannot be found on it
+ and has probably been discontinued or rebadged.
+
+ TQM8260:
+ MPC8260 based module, little larger than credit card,
+ up to 128 MB global + 64 MB local RAM, 32 MB Flash,
+ 32 kB EEPROM, 256 kB L@ Cache, 10baseT + 100baseT Ethernet,
+ 2 x serial ports, ...
+ Manufacturer: TQ Components, www.tq-group.de
+ Date of Release: June 2001
+ End of Life: not yet :-)
+ URL: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev005.pdf>
+
+ PM826:
+ Modular system with MPC8260 CPU
+ Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
+ Date of Release: mid 2001
+ End of life: -
+ URL: <http://www.microsys.de/html/pm826.html>
+
+ CU824:
+ VMEBus Board with PCI extension with MPC8240 CPU
+ Manufacturer: MicroSys GmbH, http://www.microsys.de/
+ Date of Release: early 2001 (?)
+ End of life: -
+ URL: <http://www.microsys.de/html/cu824.html>
ADB raw keycode support
CONFIG_MAC_ADBKEYCODES
@@ -20870,6 +20961,13 @@
If unsure, say Y here.
+I2C/SPI Microcode Patch
+CONFIG_UCODE_PATCH
+ Motorola releases microcode updates for their 8xx CPM modules. The
+ microcode update file has updates for IIC, SMC and USB. Currently only
+ the USB update is available by default, if the MPC8xx USB option is
+ enabled. If in doubt, say 'N' here.
+
Mouse button 2+3 emulation support
CONFIG_MAC_EMUMOUSEBTN
This provides generic support for emulating the 2nd and 3rd mouse
@@ -21013,7 +21111,7 @@
Support for audio/video capture and overlay devices and FM radio
cards. The exact capabilities of each device vary. User tools for
this are available from
- <ftp://ftp.uk.linux.org/pub/linux/video4linux>.
+ <ftp://ftp.uk.linux.org/pub/linux/video4linux/>.
If you are interested in writing a driver for such an audio/video
device or user software interacting with such a driver, please read
@@ -21253,7 +21351,7 @@
Guillemot MAXI Radio FM 2000 Radio Card
CONFIG_RADIO_MAXIRADIO
Choose Y here if you have this radio card. This card may also be
- found as Gemtek PCI FM.
+ found as GemTek PCI FM.
In order to control your radio card, you will need to use programs
that are compatible with the Video For Linux API. Information on
@@ -21284,10 +21382,10 @@
CONFIG_RADIO_GEMTEK_PORT
Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
0x34c, if you haven't changed the jumper setting on the card. On
- Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the I/O
+ Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM GemTek), the I/O
port is 0x28c.
-Gemtek PCI Radio
+GemTek PCI Radio Card support
CONFIG_RADIO_GEMTEK_PCI
Choose Y here if you have this PCI FM radio card.
@@ -21365,7 +21463,7 @@
whenever you want). If you want to compile it as a module, say M
here and read <file:Documentation/modules.txt>.
-BT878 Audio DMA
+BT878 audio DMA
CONFIG_SOUND_BT878
Audio DMA support for bt878 based grabber boards. As you might have
already noticed, bt878 is listed with two functions in /proc/pci.
@@ -21399,7 +21497,7 @@
Miro DC10 and DC30 video capture cards).
Include support for Iomega Buz
-CONFIG_VIDEO_BUZ
+CONFIG_VIDEO_ZORAN_BUZ
Say Y here to include support for the Iomega Buz video card. There
is a Buz/Linux homepage at <http://www.lysator.liu.se/~gz/buz/>.
@@ -21444,7 +21542,7 @@
as a module (c-qcam.o).
Read <file:Documentation/video4linux/CQcam.txt> for more information.
-Winbond W9966CF Webcam Video For Linux
+W9966 Webcam (FlyCam Supra and others) Video For Linux
CONFIG_VIDEO_W9966
Video4linux driver for Winbond's w9966 based Webcams.
Currently tested with the LifeView FlyCam Supra.
@@ -21452,8 +21550,8 @@
otherwise say N.
This driver is also available as a module (w9966.o).
- Check out <file:Documentation/video4linux/w9966.txt> and
- <file:Documentation/video4linux/w9966.c> for more information.
+ Check out <file:drivers/media/video4linux/w9966.txt> and
+ <file:drivers/media/video/w9966.c> for more information.
CPiA Video For Linux
CONFIG_VIDEO_CPIA
@@ -21492,7 +21590,7 @@
it as a module, say M here and read
<file:Documentation/modules.txt>.
-Sony Vaio Picturebook Motion Eye Video for Linux
+Sony Vaio Picturebook Motion Eye Video For Linux
CONFIG_VIDEO_MEYE
This is the video4linux driver for the Motion Eye camera found
in the Vaio Picturebook laptops. Please read the material in
@@ -21555,16 +21653,16 @@
attached to another IBM mainframe operation system (OS/390,
VM/ESA, VSE/ESA).
-ECKD devices
+Support for ECKD hard disks
CONFIG_DASD_ECKD
- ECKD devices are the most commonly used devices. you should enable
- this option unless you are very sure to have no ECKD device.
+ ECKD devices are the most commonly used devices. You should enable
+ this option unless you are very sure you have no ECKD device.
CKD devices
CONFIG_DASD_CKD
CKD devices are currently unsupported.
-FBA devices
+Support for FBA hard disks
CONFIG_DASD_FBA
FBA devices are currently unsupported.
@@ -21577,25 +21675,23 @@
CONFIG_IPLABE.
Support for 3215 line mode terminal
-CONFIG_3215
- Include support for IBM 3215 line-mode terminals. Can't be used
- if 3270 console support is chosen.
+CONFIG_TN3215
+ Include support for IBM 3215 line-mode terminals.
Support for console on 3215 line mode terminal
-CONFIG_3215_CONSOLE
- Include support for using an IBM 3215 line-mode terminal as the
- Linux system console. Can't be used if 3270 console support is
- chosen.
+CONFIG_TN3215_CONSOLE
+ Include support for using an IBM 3215 line-mode terminal as a
+ Linux system console.
Support for 3270 line mode terminal
-CONFIG_3270
+CONFIG_TN3270
Include support for IBM 3270 line-mode terminals.
Support for console on 3270 line mode terminal
-CONFIG_3270_CONSOLE
- Include support for using an IBM 3270 line-mode terminal as the
- Linux system console. Excludes using 3215s. Available only if 3270
- support is compiled in statically.
+CONFIG_TN3270_CONSOLE
+ Include support for using an IBM 3270 line-mode terminal as a Linux
+ system console. Available only if 3270 support is compiled in
+ statically.
Support for HWC line mode terminal
CONFIG_HWC
@@ -21846,11 +21942,25 @@
There are no product plans beyond the current research
prototypes at this time. Information is available at:
- <http://crl.research.compaq.com/projects/personalserver>
+ <http://crl.research.compaq.com/projects/personalserver/>
If you have any questions or comments about the Compaq Personal
Server, send e-mail to skiff@crl.dec.com.
+Cirrus Logic EDB-7211 evaluation board
+CONFIG_ARCH_EDB7211
+ Say Y here if you intend to run this kernel on a Cirrus Logic EDB-7211
+ evaluation board.
+
+EP7211 infrared support
+CONFIG_EP7211_IR
+ Say Y here if you wish to use the infrared port on the EP7211. Note
+ that you can't use the first UART and the infrared port at the same
+ time, and that the EP7211 only supports SIR mode, at speeds up to
+ 115.2 kbps. To use the I/R port, you will need to get the source to
+ irda-utils and apply the patch at
+ <http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-June/003510.html>.
+
Assabet
CONFIG_SA1100_ASSABET
Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
@@ -21886,7 +21996,35 @@
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.
+ <http://www.applieddata.net/> for information on this system.
+
+GraphicsMaster
+CONFIG_SA1100_GRAPHICSMASTER
+ Say Y here if you are using an Applied Data Systems Intel(R)
+ StrongARM(R) SA-1100 based Graphics Master SBC with SA-1111
+ StrongARM companion chip. See
+ <http://www.applieddata.net/products_masterSpec.asp> for information
+ on this system.
+
+ADSBitsy
+CONFIG_SA1100_ADSBITSY
+ Say Y here if you are using Applied Data Systems Intel(R)
+ StrongARM(R) 1110 based Bitsy, 3 x 5 inches in size, Compaq - IPAQ -
+ like platform. See
+ <http://www.applieddata.net/products_bitsySpec.asp> for more
+ information.
+
+ITSY
+CONFIG_SA1100_ITSY
+ Say Y here if you are using the Compaq Itsy experimental pocket
+ computer. See <http://research.compaq.com/wrl/projects/itsy/> for
+ more information.
+
+PLEB
+CONFIG_SA1100_PLEB
+ Say Y here if you are using a Portable Linux Embedded Board
+ (also known as PLEB). See <http://www.cse.unsw.edu.au/~pleb/>
+ for more information.
CerfBoard
CONFIG_SA1100_CERF
@@ -21897,6 +22035,12 @@
Say Y if configuring for an Intrinsyc CerfBoard.
Say N otherwise.
+FlexaNet
+CONFIG_SA1100_FLEXANET
+ Say Y here if you intend to run this kernel on the FlexaNet
+ handheld instruments. Information about this machine can be
+ found at: <http://www.flexanet.com/>.
+
nanoEngine
CONFIG_SA1100_NANOENGINE
The nanoEngine is a StrongARM 1110-based single board computer
@@ -21923,6 +22067,38 @@
<http://www.visuaide.com/pagevictor.en.html> for information on
this system.
+# Choice: cerf_ram
+Cerf on-board RAM size
+CONFIG_SA1100_CERF_8MB
+ Declare the size of the CerfBoard's on-board RAM.
+ Alternatives are 8, 16, 32, and 64MB.
+
+16MB
+CONFIG_SA1100_CERF_16MB
+ Declare that the CerfBoard has 16MB RAM.
+
+32MB
+CONFIG_SA1100_CERF_32MB
+ Declare that the CerfBoard has 32MB RAM.
+
+64MB
+CONFIG_SA1100_CERF_64MB
+ Declare that the CerfBoard has 64MB RAM.
+
+# Choice: cerf_flash
+Cerf flash memory size
+CONFIG_SA1100_CERF_FLASH_8MB
+ Tell the Cerf kernel the size of on-board memory. The choices
+ are 8MB, 16MB, or 32MB.
+
+16MB
+CONFIG_SA1100_CERF_FLASH_16MB
+ Configure the Cerf kernel to expect 16MB of flash memory.
+
+32MB
+CONFIG_SA1100_CERF_FLASH_32MB
+ Configure the Cerf kernel to expect 32MB of flash memory.
+
Support ARM610 processor
CONFIG_CPU_ARM610
The ARM610 is the successor to the ARM3 processor
@@ -21976,6 +22152,50 @@
Say Y if you want support for the SA-110 processor.
Otherwise, say N.
+Tulsa
+CONFIG_SA1100_PFS168
+ The Radisys Corp. PFS-168 (aka Tulsa) is an Intel® StrongArm® SA-1110 based
+ computer which includes the SA-1111 Microprocessor Companion Chip and other
+ custom I/O designed to add connectivity and multimedia features for vending
+ and business machine applications. Say Y here if you require support for
+ this target.
+
+HP Jornada 720
+CONFIG_SA1100_JORNADA720
+ Say Y here if you want to build a kernel for the HP Jornada 720
+ handheld computer. See <http://www.hp.com/jornada/products/720>
+ for details.
+
+InHand Electronics OmniMeter
+CONFIG_SA1100_OMNIMETER
+ Say Y here if you are using the inhand electronics OmniMeter. See
+ <http://www.inhandelectronics.com/html/omni1.html> for details.
+
+Load kernel using Angel Debug Monitor
+CONFIG_ANGELBOOT
+ Say Y if you plan to load the kernel using Angel, ARM Ltd's target
+ debug stub. If you are not using Angel, you must say N. It is
+ important to get this setting correct.
+
+CDB89712
+CONFIG_ARCH_CDB89712
+ This is an evaluation board from Cirrus for the CS89712 processor. The
+ board includes 2 serial ports, Ethernet, IRDA, and expansion headers.
+ It comes with 16 MB SDRAM and 8 MB flash ROM.
+
+CLPS-711X internal ROM bootstrap
+CONFIG_EP72XX_ROM_BOOT
+ If you say Y here, your CLPS711x-based kernel will use the bootstrap
+ mode memory map instead of the normal memory map.
+
+ Processors derived from the Cirrus CLPS-711X core support two boot modes.
+ Normal mode boots from the external memory device at CS0. Bootstrap mode
+ rearranges parts of the memory map, placing an internal 128 byte bootstrap
+ ROM at CS0. This option performs the address map changes required to
+ support booting in this mode.
+
+ You almost surely want to say N here.
+
Math emulation
CONFIG_FPE_NWFPE
Say Y to include the NWFPE floating point emulator in the kernel.
@@ -22284,11 +22504,6 @@
no management frames, simple fixed header).
Ultra is available as a special socket : socket(AF_IRDA, SOCK_DGRAM, 1);
-IrDA protocol options
-CONFIG_IRDA_OPTIONS
- Say Y here if you want to configure any of the following IrDA
- options.
-
IrDA cache last LSAP
CONFIG_IRDA_CACHE_LAST_LSAP
Say Y here if you want IrLMP to cache the last LSAP used. This
@@ -22300,47 +22515,35 @@
IrDA Fast RRs
CONFIG_IRDA_FAST_RR
Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
- when acting as a primary station. This will make IrLAP send out a RR
- frame immediately when receiving a frame if its own transmit queue
- is currently empty. This will give a lot of speed improvement when
- receiving much data since the secondary station will not have to
- wait the max. turn around time before it is allowed to transmit the
- next time. If the transmit queue of the secondary is also empty the
- primary will back off waiting longer for sending out the RR frame
- until the timeout reaches the normal value. Enabling this option
- will make the IR-diode burn more power and thus reduce your battery
- life.
+ when acting as a primary station.
+ Disabling this option will make latency over IrDA very bad. Enabling
+ this option will make the IrDA stack send more packet than strictly
+ necessary, thus reduce your battery life (but not that much).
+
+ Fast RR will make IrLAP send out a RR frame immediately when
+ receiving a frame if its own transmit queue is currently empty. This
+ will give a lot of speed improvement when receiving much data since
+ the secondary station will not have to wait the max. turn around
+ time (usually 500ms) before it is allowed to transmit the next time.
+ If the transmit queue of the secondary is also empty, the primary will
+ start backing-off before sending another RR frame, waiting longer
+ each time until the back-off reaches the max. turn around time.
+ This back-off increase in controlled via
+ /proc/sys/net/irda/fast_poll_increase
- If unsure, say N.
+ If unsure, say Y.
IrDA debugging information
CONFIG_IRDA_DEBUG
Say Y here if you want the IrDA subsystem to write debug information
to your syslog. You can change the debug level in
/proc/sys/net/irda/debug .
+ When this option is enabled, the IrDA also perform many extra internal
+ verifications which will usually prevent the kernel to crash in case of
+ bugs.
If unsure, say Y (since it makes it easier to find the bugs).
-IrLAP compression support
-CONFIG_IRDA_COMPRESSION
- Compression is _not_ part of the IrDA(tm) protocol specification,
- but it's working great! Linux is the first to try out compression
- support at the IrLAP layer. This means that you will only benefit
- from compression if you are running a Linux <-> Linux configuration.
-
- If you say Y here, you also need to say Y or M to a compression
- protocol below.
-
-IrLAP Deflate compression
-CONFIG_IRDA_DEFLATE
- Say Y here if you want to build support for the Deflate compression
- protocol. The deflate compression (GZIP) is exactly
- the same as the one used by the PPP protocol.
-
- If you want to compile this compression support as a module, say M
- here and read <file:Documentation/modules.txt>. The module will be
- called irda_deflate.o.
-
IrLAN protocol
CONFIG_IRLAN
Say Y here if you want to build support for the IrLAN protocol. If
@@ -22417,6 +22620,27 @@
Please note that the driver is still experimental. And of course,
you will need both USB and IrDA support in your kernel...
+Datafab MDCFE-B Compact Flash Reader support
+CONFIG_USB_STORAGE_DATAFAB
+ This option enables a sub-driver of the USB Mass Storage driver. These
+ sub-drivers are considered experimental, and should only be used by very
+ brave people. System crashes and other bad things are likely to occur if
+ you use this driver. If in doubt, select N.
+
+HP CD-Writer 82xx support
+CONFIG_USB_STORAGE_HP8200e
+ This option enables a sub-driver of the USB Mass Storage driver. These
+ sub-drivers are considered experimental, and should only be used by very
+ brave people. System crashes and other bad things are likely to occur if
+ you use this driver. If in doubt, select N.
+
+Lexar Jumpshot Compact Flash Reader
+CONFIG_USB_STORAGE_JUMPSHOT
+ This option enables a sub-driver of the USB Mass Storage driver. These
+ sub-drivers are considered experimental, and should only be used by very
+ brave people. System crashes and other bad things are likely to occur if
+ you use this driver. If in doubt, select N.
+
Winbond W83977AF IrDA Device Driver
CONFIG_WINBOND_FIR
Say Y here if you want to build IrDA support for the Winbond
@@ -22438,13 +22662,18 @@
<file:Documentation/modules.txt>. The module will be called
nsc-ircc.o.
-National Semiconductor DP83820 series driver
+National Semiconductor DP83820 support
CONFIG_NS83820
This is a driver for the National Semiconductor DP83820 series
- of gigabit ethernet MACs. Cards using this chipset include
- the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
- SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
- zero copy.
+ of gigabit ethernet MACs. Cards using this chipset include:
+
+ SMC 9452TX SMC SMC9462TX
+ D-Link DGE-500T PureData PDP8023Z-TG
+ SOHO-GA2000T SOHO-GA2500T.
+ NetGear GA621
+
+ This driver supports the use of zero copy on tx, checksum
+ validation on rx, and 64 bit addressing.
Toshiba Type-O IR Port device driver
CONFIG_TOSHIBA_FIR
@@ -22462,7 +22691,7 @@
here and read <file:Documentation/modules.txt>. The module will be
called smc-ircc.o.
-ALi M5123 FIR Controller Driver
+ALi M5123 FIR controller driver
CONFIG_ALI_FIR
Say Y here if you want to build support for the ALi M5123 FIR
Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
@@ -22473,7 +22702,7 @@
<file:Documentation/modules.txt>. The module will be called
ali-ircc.o.
-VLSI 82C147 PCI-IrDA Controller Driver
+VLSI 82C147 PCI-IrDA SIR/MIR/FIR Controller driver
CONFIG_VLSI_FIR
Say Y here if you want to build support for the VLSI 82C147
PCI-IrDA Controller. This controller is used by the HP OmniBook 800
@@ -22684,6 +22913,7 @@
CONFIG_ETRAX_FLASH_BUSWIDTH
Width in bytes of the Flash bus (1, 2 or 4). Is usually 2.
+# Choice: crisleds
LED configuration on PA
CONFIG_ETRAX_PA_LEDS
The Etrax network driver is responsible for flashing LED's when
@@ -23168,6 +23398,7 @@
CONFIG_ETRAX_I2C_EEPROM_8KB
Use a 8kB EEPROM.
+# Choice: etrax_eeprom
Etrax100 I2C EEPROM (NVRAM) size/probe
CONFIG_ETRAX_I2C_EEPROM_PROBE
Specifies size or auto probe of the EEPROM size.
@@ -23215,7 +23446,7 @@
CONFIG_ETRAX_IDE_CSPE1_16_RESET
Configures the pin used to reset the IDE bus.
-Etrax 100 ATA/IDE support
+Delay for drives to regain consciousness
CONFIG_ETRAX_IDE_DELAY
Sets the time to wait for disks to regain consciousness after reset.
@@ -23223,6 +23454,7 @@
CONFIG_ETRAX_IDE_G27_RESET
Configures the pin used to reset the IDE bus.
+# Choice: ide_reset
IDE reset on PB Bit 7
CONFIG_ETRAX_IDE_PB7_RESET
Configures the pin used to reset the IDE bus.
@@ -23541,7 +23773,7 @@
this. If in doubt, say Y.
/proc/efi/vars support
-CONFIG_IA64_EFIVARS
+CONFIG_EFI_VARS
If you say Y here, you are able to get EFI (Extensible Firmware
Interface) variable information in /proc/efi/vars. You may read,
write, create, and destroy EFI variables through this interface.
@@ -23549,6 +23781,42 @@
To use this option, you have to check that the "/proc file system
support" (CONFIG_PROC_FS) is enabled, too.
+Physical memory granularity (16 MB)
+CONFIG_IA64_GRANULE_16MB
+ IA64 identity-mapped regions use a large page size. We'll call such
+ large pages "granules". If you can think of a better name that's
+ unambiguous, let us know... Unless your identity-mapped regions are
+ very large, select a granule size of 16MB.
+
+Physical memory granularity (64 MB)
+CONFIG_IA64_GRANULE_64MB
+ IA64 identity-mapped regions use a large page size. We'll call such
+ large pages "granules". If you can think of a better name that's
+ unambiguous, let us know... Unless your identity-mapped regions are
+ very large, select a granule size of 16MB. (This is the "large" choice.)
+
+Enable SGI SN extra debugging code
+CONFIG_IA64_SGI_SN_DEBUG
+ Turns on extra debugging code in the SGI SN (Scalable NUMA) platform
+ for IA64. Unless you are debugging problems on an SGI SN IA64 box,
+ say N.
+
+Enable SGI Medusa Simulator Support
+CONFIG_IA64_SGI_SN_SIM
+ If you are compiling a kernel that will run under SGI's IA64
+ simulator (Medusa) then say Y, otherwise say N.
+
+PCIBA Support
+CONFIG_PCIBA
+ IRIX PCIBA-inspired user mode PCI interface for the SGI SN (Scalable
+ NUMA) platform for IA64. Unless you are compiling a kernel for an SGI SN IA64 box, say N.
+
+Enable protocol mode for the L1 console
+SERIAL_SGI_L1_PROTOCOL
+ Uses protocol mode instead of raw mode for the level 1 console on the
+ SGI SN (Scalable NUMA) platform for IA64. If you are compiling for
+ an SGI SN box then Y is the recommended value, otherwise say N.
+
Directly Connected Compact Flash support
CONFIG_CF_ENABLER
Compact Flash is a small, removable mass storage device introduced
@@ -23574,7 +23842,7 @@
allocation as well as poisoning memory on free to catch use of freed
memory.
-Memory mapped I/O debug support
+Memory mapped I/O debugging
CONFIG_DEBUG_IOVIRT
Say Y here to get warned whenever an attempt is made to do I/O on
obviously invalid addresses such as those generated when ioremap()
@@ -23590,6 +23858,19 @@
best used in conjunction with the NMI watchdog so that spinlock
deadlocks are also debuggable.
+Read-write spinlock debugging
+CONFIG_DEBUG_RWLOCK
+ If you say Y here then read-write lock processing will count how many
+ times it has tried to get the lock and issue an error message after
+ too many attempts. If you suspect a rwlock problem or a kernel
+ hacker asks for this option then say Y. Otherwise say N.
+
+Semaphore debugging
+CONFIG_DEBUG_SEMAPHORE
+ If you say Y here then semaphore processing will issue lots of
+ verbose debugging messages. If you suspect a semaphore problem or a
+ kernel hacker asks for this option then say Y. Otherwise say N.
+
Verbose BUG() reporting (adds 70K)
CONFIG_DEBUG_BUGVERBOSE
Say Y here to make BUG() panics output the file name and line number
@@ -23698,7 +23979,7 @@
each of the machines below is described by a machine vector.
Select SolutionEngine if configuring for a Hitachi SH7709
- or SH7750 evalutation board.
+ or SH7750/7750S evalutation board.
Select Overdrive if configuring for a ST407750 Overdrive board.
More information at
@@ -23706,34 +23987,43 @@
Select HP620 if configuring for a HP Jornada HP620.
More information (hardware only) at
- <http://www.hp.com/jornada>.
+ <http://www.hp.com/jornada/>.
Select HP680 if configuring for a HP Jornada HP680.
More information (hardware only) at
- <http://www.hp.com/jornada/products/680>.
+ <http://www.hp.com/jornada/products/680/>.
Select HP690 if configuring for a HP Jornada HP690.
More information (hardware only) at
- <http://www.hp.com/jornada/products/680>.
+ <http://www.hp.com/jornada/products/680/>.
Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
More information at
<http://sources.redhat.com/ecos/hardware.html#SuperH>.
Select DMIDA if configuring for a DataMyte 4000 Industrial
- Digital Assistant. More information at <http://www.dmida.com>.
+ Digital Assistant. More information at <http://www.dmida.com/>.
Select EC3104 if configuring for a system with an Eclipse
- International EC3104 chip, e.g. the Harris AD2000.
+ International EC3104 chip, e.g. the Harris AD2000 or Compaq Aero 8000.
Select Dreamcast if configuring for a SEGA Dreamcast.
More information at
- <http://www.m17n.org/linux-sh/dreamcast>. There is a
+ <http://www.m17n.org/linux-sh/dreamcast/>. There is a
Dreamcast project is at <http://linuxdc.sourceforge.net/>.
Select BareCPU if you know what this means, and it applies
to your system.
+# These may have to be merged in when we go to CML2:
+# - "SolutionEngine7751" for Hitachi SolutionEngine (7751)
+# - "STB1_Harp" for STMicroelectronics HARP
+# - "CqREEK" for CQ Publishing CqREEK SH-4
+# - "CAT68701" for CAT 68701 Evaluation Board (SH7708)
+# - "BigSur" for Big Sur Evaluation Board
+# - "SH2000" for SH2000 Evaluation Board (SH7709A)
+# - "ADX" for A&D ADX
+
SolutionEngine
CONFIG_SH_SOLUTION_ENGINE
Select SolutionEngine if configuring for a Hitachi SH7709
@@ -23754,19 +24044,19 @@
CONFIG_SH_HP620
Select HP620 if configuring for a HP jornada HP620.
More information (hardware only) at
- <http://www.hp.com/jornada>.
+ <http://www.hp.com/jornada/>.
HP680
CONFIG_SH_HP680
Select HP680 if configuring for a HP Jornada HP680.
More information (hardware only) at
- <http://www.hp.com/jornada/products/680>.
+ <http://www.hp.com/jornada/products/680/>.
HP690
CONFIG_SH_HP690
Select HP690 if configuring for a HP Jornada HP690.
More information (hardware only)
- at <http://www.hp.com/jornada/products/680>.
+ at <http://www.hp.com/jornada/products/680/>.
CqREEK
CONFIG_SH_CQREEK
@@ -23777,7 +24067,7 @@
DMIDA
CONFIG_SH_DMIDA
Select DMIDA if configuring for a DataMyte 4000 Industrial
- Digital Assistant. More information at <http://www.dmida.com>.
+ Digital Assistant. More information at <http://www.dmida.com/>.
EC3104
CONFIG_SH_EC3104
@@ -23788,7 +24078,7 @@
CONFIG_SH_DREAMCAST
Select Dreamcast if configuring for a SEGA Dreamcast.
More information at
- <http://www.m17n.org/linux-sh/dreamcast>. There is a
+ <http://www.m17n.org/linux-sh/dreamcast/>. There is a
Dreamcast project is at <http://linuxdc.sourceforge.net/>.
BareCPU
@@ -23805,7 +24095,8 @@
# Choice: superhtype
SH7707
CONFIG_CPU_SUBTYPE_SH7707
- Select the type of SuperH processor you have.
+ Select the type of SuperH processor you have. This information is
+ used for optimizing and configuration purposes.
Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU.
@@ -23816,6 +24107,10 @@
Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
+ Select SH7751 if you have a SH7751
+
+ Select ST40STB1 if you have a ST40STB1
+
SH7708
CONFIG_CPU_SUBTYPE_SH7708
Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
@@ -23831,7 +24126,11 @@
Physical memory start address
CONFIG_MEMORY_START
- The physical memory start address will be automatically
+ Computers built with Hitachi SuperH processors always
+ map the ROM starting at address zero. But the processor
+ does not specify the range that RAM takes.
+
+ The physical memory (RAM) start address will be automatically
set to 08000000, unless you selected one of the following
processor types: SolutionEngine, Overdrive, HP620, HP680, HP690,
in which case the start address will be set to 0c000000.
@@ -23889,15 +24188,15 @@
The default setting of the HD64465 IO base address is 0xb0000000.
Do not change this unless you know what you are doing.
-
+
Early printk support
CONFIG_SH_EARLY_PRINTK
- Say Y here to redirect kernel messages to the serial port
+ Say Y here to redirect kernel printk messages to the serial port
used by the SH-IPL bootloader, starting very early in the boot
process and ending when the kernel's serial console is initialised.
This option is only useful porting the kernel to a new machine,
when the kernel may crash or hang before the serial console is
- initialised.
+ initialised. If unsure, say N.
SuperH SCI (serial) support
CONFIG_SH_SCI
@@ -23951,7 +24250,7 @@
#
# This is used by Emacs' spell checker ispell.el:
#
-# LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
+# LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp ibiblio
# LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
# LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
# LocalWords: HD CD-ROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
@@ -23997,7 +24296,7 @@
# LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
# LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
# LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
-# LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
+# LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrtools pg
# LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
# LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
# LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen (who was at: slshen@lbl.gov)