Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Linux Kernel Patch v2.4, patch-2.4.15 (008/115)

15 views

Skip to first unread message

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:44 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part008

#!/bin/sh -x
# this is part 008 of a 115 - part archive
# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck
if test "$Scheck" != 008; then
echo "Please unpack part $Scheck next!"
exit 1
else
exit 0
fi
) < _shar_seq_.tmp || exit 1
if test ! -f _shar_wnt_.tmp; then
echo 'x - still skipping patch-2.4.15'
else
echo 'x - continuing with patch-2.4.15'
sed 's/^X//' << 'SHAR_EOF' >> 'patch-2.4.15' &&
- the WAN driver for your card, below. You will then need the
- wan-tools package which is available from ftp://ftp.sangoma.com .
- Read Documentation/networking/wan-router.txt for more information.
+ the WAN driver for your card, below. You will then need the
+ wan-tools package which is available from <ftp://ftp.sangoma.com>.
+ Read <file:Documentation/networking/wan-router.txt> for more
+ information.
X
X The WAN routing support is also available as a module called
X wanrouter.o ( = 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 Documentation/modules.txt.
+ running kernel whenever you want). If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X If unsure, say N.
X
@@ -8103,13 +9137,13 @@
X IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
X filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
X
- However, it will work with all options in the "IP: advanced router"
- section (except for "IP: use TOS value as routing key" and
- "IP: use FWMARK value as routing key").
+ However, it will work with all options in the "Advanced router"
+ section (except for "Use TOS value as routing key" and
+ "Use FWMARK value as routing key").
X
X At the moment, few devices support fast switching (tulip is one of
X them, a modified 8390 driver can be found at
- ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
+ <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
X
X If unsure, say N.
X
@@ -8119,7 +9153,7 @@
X during periods of extremal congestion. At the moment only a couple
X of device drivers support it (really only one -- tulip, a modified
X 8390 driver can be found at
- ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
+ <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
X
X Really, this option is applicable to any machine attached to a fast
X enough network, and even a 10 Mb NIC is able to kill a not very slow
@@ -8146,68 +9180,75 @@
X This code is considered to be experimental.
X
X To administer these schedulers, you'll need the user-level utilities
- from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
+ from the package iproute2+tc at <ftp://ftp.inr.ac.ru/ip-routing/>.
X That package also contains some documentation; for more, check out
- http://snafu.freedom.org/linux2.2/iproute-notes.html .
+ <http://snafu.freedom.org/linux2.2/iproute-notes.html>.
X
X This Quality of Service (QoS) support will enable you to use
X Differentiated Services (diffserv) and Resource Reservation Protocol
X (RSVP) on your Linux router if you also say Y to "QoS support",
X "Packet classifier API" and to some classifiers below. Documentation
- and software is at http://icawww1.epfl.ch/linux-diffserv/ .
+ and software is at <http://icawww1.epfl.ch/linux-diffserv/>.
X
X If you say Y here and to "/proc file system" below, you will be able
X to read status information about packet schedulers from the file
X /proc/net/psched.
-
+
X The available schedulers are listed in the following questions; you
X can say Y to as many as you like. If unsure, say N now.
X
X CBQ packet scheduler
X CONFIG_NET_SCH_CBQ
X Say Y here if you want to use the Class-Based Queueing (CBQ) packet
- scheduling algorithm for some of your network devices. This
+ scheduling algorithm for some of your network devices. This
X algorithm classifies the waiting packets into a tree-like hierarchy
X of classes; the leaves of this tree are in turn scheduled by
X separate algorithms (called "disciplines" in this context).
X
- See the top of net/sched/sch_cbq.c for references about the CBQ
- algorithm.
-
+ See the top of <file:net/sched/sch_cbq.c> for references about the
+ CBQ algorithm.
+
X CBQ is a commonly used scheduler, so if you're unsure, you should
X say Y here. Then say Y to all the queueing algorithms below that you
- want to use as CBQ disciplines. Then say Y to "Packet classifier
+ want to use as CBQ disciplines. Then say Y to "Packet classifier
X API" and say Y to all the classifiers you want to use; a classifier
X is a routine that allows you to sort your outgoing traffic into
X classes based on a certain criterion.
X
X This code is also available as a module called sch_cbq.o ( = code
X 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 Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X CSZ packet scheduler
X CONFIG_NET_SCH_CSZ
X Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
- scheduling algorithm for some of your network devices. At the
+ scheduling algorithm for some of your network devices. At the
X moment, this is the only algorithm that can guarantee service for
- real-time applications (see the top of net/sched/sch_csz.c for
- details and references about the algorithm).
-
+ real-time applications (see the top of <file:net/sched/sch_csz.c>
+ for details and references about the algorithm).
+
X Note: this scheduler is currently broken.
X
X This code is also available as a module called sch_csz.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
-#ATM pseudo-scheduler
-#CONFIG_NET_SCH_ATM
-#
-# ???
-#
-
-The simplest PRIO pseudo scheduler
+ATM pseudo-scheduler
+CONFIG_NET_SCH_ATM
+ Say Y here if you want to use the ATM pseudo-scheduler. This
+ provides a framework for invoking classifiers (aka "filters"), which
+ in turn select classes of this queuing discipline. Each class maps
+ the flow(s) it is handling to a given virtual circuit (see the top of
+ <file:net/sched/sch_atm.c>).
+
+ This code is also available as a module called sch_atm.o ( = 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>.
+
+The simplest PRIO pseudo-scheduler
X CONFIG_NET_SCH_PRIO
X Say Y here if you want to use an n-band priority queue packet
X "scheduler" for some of your network devices or as a leaf discipline
@@ -8216,32 +9257,56 @@
X This code is also available as a module called sch_prio.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+Diffserv field marker
+CONFIG_NET_SCH_DSMARK
+ Say Y if you want to schedule packets avccording to the
+ Differentiated Services architecture proposed in RFC 2475.
+ Technical information on this method, with pointers to associated
+ RFCs, is available at <http://www.gta.ufrj.br/diffserv/>.
+
+ This code is also available as a module called sch_dsmark.o ( = 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>.
+
+GRED queue
+CONFIG_NET_SCH_GRED
+ Say Y here if you want to use the Generic Random Early Detection
+ (RED) packet scheduling algorithm for some of your network devices
+ (see the top of <file:net/sched/sch_red.c> for details and
+ references about the algorithm).
+
+ This code is also available as a module called sch_gred.o ( = 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>.
X
X RED queue
X CONFIG_NET_SCH_RED
X Say Y here if you want to use the Random Early Detection (RED)
X packet scheduling algorithm for some of your network devices (see
- the top of net/sched/sch_red.c for details and references about the
- algorithm).
+ the top of <file:net/sched/sch_red.c> for details and references
+ about the algorithm).
X
X This code is also available as a module called sch_red.o ( = code
X 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 Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X SFQ queue
X CONFIG_NET_SCH_SFQ
X Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
X packet scheduling algorithm for some of your network devices or as a
X leaf discipline for the CBQ scheduling algorithm (see the top of
- net/sched/sch_sfq.c for details and references about the SFQ
- algorithm).
+ <file:net/sched/sch_sfq.c> for details and references about the SFQ
+ algorithm).
X
X This code is also available as a module called sch_sfq.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
X TEQL queue
X CONFIG_NET_SCH_TEQL
@@ -8249,30 +9314,36 @@
X scheduling algorithm for some of your network devices or as a leaf
X discipline for the CBQ scheduling algorithm. This queueing
X discipline allows the combination of several physical devices into
- one virtual device. (see the top of net/sched/sch_teql.c for
+ one virtual device. (see the top of <file:net/sched/sch_teql.c> for
X details).
X
X This code is also available as a module called sch_teql.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
X TBF queue
X CONFIG_NET_SCH_TBF
X Say Y here if you want to use the Simple Token Bucket Filter (TBF)
X packet scheduling algorithm for some of your network devices or as a
X leaf discipline for the CBQ scheduling algorithm (see the top of
- net/sched/sch_tbf.c for a description of the TBF algorithm).
+ <file:net/sched/sch_tbf.c> for a description of the TBF algorithm).
X
X This code is also available as a module called sch_tbf.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+Ingress Qdisc
+CONFIG_NET_SCH_INGRESS
+ If you say Y here, you will be able to police incoming bandwidth
+ and drop packets when this bandwidth exceeds your desired rate.
+ If unsure, say Y.
X
-### Add these
-#+tristate ' GRED queue' CONFIG_NET_SCH_GRED
-#+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
-#+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
+ This code is also available as a module called cls_ingress.o
+ ( = 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>.
X
X QoS support
X CONFIG_NET_QOS
@@ -8284,10 +9355,10 @@
X Differentiated Services (diffserv) and Resource Reservation Protocol
X (RSVP) on your Linux router if you also say Y to "Packet classifier
X API" and to some classifiers below. Documentation and software is at
- http://icawww1.epfl.ch/linux-diffserv/ .
+ <http://icawww1.epfl.ch/linux-diffserv/>.
X
X Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
X the questions about QoS support.
X
X Rate estimator
@@ -8307,10 +9378,24 @@
X This will enable you to use Differentiated Services (diffserv) and
X Resource Reservation Protocol (RSVP) on your Linux router.
X Documentation and software is at
- http://icawww1.epfl.ch/linux-diffserv/ .
+ <http://icawww1.epfl.ch/linux-diffserv/>.
X
-### Add
-#tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
+Traffic policing (needed for in/egress)
+CONFIG_NET_CLS_POLICE
+ Say Y to support traffic policing (bandwidth limits). Needed for
+ ingress and egress rate limiting.
+
+TC index classifier
+CONFIG_NET_CLS_TCINDEX
+ If you say Y here, you will be able to classify outgoing packets
+ according to the tc_index field of the skb. You will want this
+ feature if you want to implement Differentiated Services using
+ sch_dsmark. If unsure, say Y.
+
+ This code is also available as a module called cls_tcindex.o
+ ( = 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>.
X
X Routing tables based classifier
X CONFIG_NET_CLS_ROUTE4
@@ -8319,8 +9404,8 @@
X
X This code is also available as a module called cls_route.o ( = code
X 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 Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X Firewall based classifier
X CONFIG_NET_CLS_FW
@@ -8329,8 +9414,8 @@
X
X This code is also available as a module called cls_fw.o ( = code
X 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 Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X U32 classifier
X CONFIG_NET_CLS_U32
@@ -8339,8 +9424,8 @@
X
X This code is also available as a module called cls_u32.o ( = code
X 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 Documentation/modules.txt
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X Special RSVP classifier
X CONFIG_NET_CLS_RSVP
@@ -8353,8 +9438,8 @@
X
X This code is also available as a module called cls_rsvp.o ( = code
X 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 Documentation/modules.txt
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X Special RSVP classifier for IPv6
X CONFIG_NET_CLS_RSVP6
@@ -8368,15 +9453,8 @@
X
X This code is also available as a module called cls_rsvp6.o ( = code
X 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 Documentation/modules.txt
-
-#
-# Traffic policing (needed for in/egress)
-# CONFIG_NET_CLS_POLICE
-###
-### Some expert please fill these in
-###
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
X
X Network code profiler
X CONFIG_NET_PROFILE
@@ -8405,10 +9483,10 @@
X CONFIG_HOSTESS_SV11
X This is a network card for low speed synchronous serial links, at
X up to 256Kbps. It supports both PPP and Cisco HDLC.
-
+
X At this point, the driver can only be compiled as a module.
X
-COSA/SRP sync serial boards support
+COSA/SRP sync serial board support
X CONFIG_COSA
X This is a driver for COSA and SRP synchronous serial boards. These
X boards allow to connect synchronous serial devices (for example
@@ -8419,59 +9497,60 @@
X
X To actually use the COSA or SRP board, you will need user-space
X utilities for downloading the firmware to the cards and to set them
- up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
+ up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more
X information about the cards (including the pointer to the user-space
X utilities). You can also read the comment at the top of the
- drivers/net/cosa.c for details about the cards and the driver
+ <file:drivers/net/cosa.c> for details about the cards and the driver
X itself.
X
X The driver will be compiled as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
X The module will be called cosa.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
X
-Etinc PCISYNC serial boards support
+Etinc PCISYNC serial board support
X CONFIG_DSCC4
X This is a driver for Etinc PCISYNC boards based on the Infineon
X (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>
X for further informations about the driver and his configuration.
X
X The driver will be compiled as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
X The module will be called dscc4.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
X
-Lan Media sync serial boards support
+LanMedia Corp. serial boards (SSI/V.35, T1/E1, HSSI, T3)
X CONFIG_LANMEDIA
- This is a driver for the following Lan Media family of serial boards.
-
+ This is a driver for the following Lan Media family of serial
+ boards.
+
X LMC 1000 board allows you to connect synchronous serial devices (for
X example base-band modems, or any other device with the X.21, V.24,
X V.35 or V.36 interface) to your Linux box.
-
+
X LMC 1200 with on board DSU board allows you to connect your Linux
X box dirrectly to a T1 or E1 circuit.
-
- LMC 5200 board provides a HSSI interface capable of runnig up to
+
+ LMC 5200 board provides a HSSI interface capable of running up to
X 52 mbits per second.
-
+
X LMC 5245 board connects directly to a T3 circuit saving the
X additional external hardware.
-
+
X To change setting such as syncPPP vs cisco HDLC or clock source you
- will need lmcctl. It it available at ftp.lanmedia.com.
-
+ will need lmcctl. It is available at <ftp://ftp.lanmedia.com>.
+
X This code is also available as a module called lmc.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
X Fibre Channel driver support
X CONFIG_NET_FC
X Fibre Channel is a high speed serial protocol mainly used to connect
X large storage devices to the computer; it is compatible with and
- intended to replace SCSI.
+ intended to replace SCSI.
X
X If you intend to use Fibre Channel, you need to have a Fibre channel
X adaptor card in your computer; say Y here and to the driver for your
@@ -8485,9 +9564,9 @@
X The driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
X The module will be called iph5526.o. For general information about
- modules read Documentation/modules.txt.
-
-Red Creek Hardware VPN (EXPERIMENTAL)
+ modules read <file:Documentation/modules.txt>.
+
+Red Creek Hardware VPN
X CONFIG_RCPCI
X This is a driver for hardware which provides a Virtual Private
X Network (VPN). Say Y if you have it.
@@ -8495,19 +9574,28 @@
X This code is also available as a module called rcpci.o ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
-
-SBNI12-xx support
+ here and read <file:Documentation/modules.txt>.
+
+Granch SBNI12 Leased Line adapter driver
X CONFIG_SBNI
X This is a driver for ISA SBNI12-xx cards which are low cost
X alternatives to leased line modems. Say Y if you want to insert
X the driver into the kernel or say M to compile it as a module (the
- 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
+ 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
X can send email to sb...@granch.ru.
-
+
+ Say N if unsure.
+
+SBNI Adapters Multiline feature
+CONFIG_SBNI_MULTILINE
+ Schedule traffic for some parallel lines, via SBNI12 adapters.
+ If you have two computers connected with two parallel lines it's
+ possible to increase transfer rate nearly twice. You should have
+ a program named 'sbniconfig' to configure adapters.
+
X Say N if unsure.
X
X WAN router drivers
@@ -8519,27 +9607,26 @@
X Router".
X
X You will need the wan-tools package which is available from
- ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
- for more information.
+ <ftp://ftp.sangoma.com>. Read
+ <file:Documentation/networking/wan-router.txt> for more information.
X
X Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
X the questions about WAN router drivers. If unsure, say N.
X
X Sangoma WANPIPE(tm) multiprotocol cards
X CONFIG_VENDOR_SANGOMA
+ 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
+ S508-ISA. These cards support
+
+ - X.25, Frame Relay, PPP, Cisco HDLC protocols.
+
+ - API support for protocols like HDLC (LAPB),
+ HDLC Streaming, X.25, Frame Relay and BiSync.
X
- 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 S508-ISA.
- These cards support
-
- - X.25, Frame Relay, PPP, Cisco HDLC protocols.
-
- - API support for protocols like HDLC (LAPB),
- HDLC Streaming, X.25, Frame Relay and BiSync.
-
X - Ethernet Bridging over Frame Relay protocol.
X
X - MULTILINK PPP
@@ -8547,32 +9634,32 @@
X - Async PPP (Modem Dialup)
X
X If you have one or more of these cards, say M to this option; you
- may then also want to read the file
- Documentation/networking/wanpipe.txt. The next questions will ask
- you about the protocols you want the driver to support.
+ may then also want to read the file
+ <file:Documentation/networking/wanpipe.txt>. The next questions
+ will ask you about the protocols you want the driver to support.
X
X The driver will be compiled as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called wanpipe.o. For general information about
- modules read Documentation/modules.txt.
+ The module will be called wanpipe.o. For general information about
+ modules read <file:Documentation/modules.txt>.
X
X WANPIPE X.25 support
X CONFIG_WANPIPE_X25
X Say Y to this option if you are planning to connect a WANPIPE card
X to an X.25 network. Note, this feature also includes the X.25 API
X support used to develope custom applications over the X.25 protocol.
- If you say N, the X.25 support will not be included in the driver.
+ If you say N, the X.25 support will not be included in the driver.
X The X.25 option is supported on S514-PCI and S508-ISA cards.
X
X WANPIPE Frame Relay support
X CONFIG_WANPIPE_FR
X Say Y to this option if you are planning to connect a WANPIPE card
- to a frame relay network, or use frame relay API to develope
- custom applications over the Frame Relay protocol.
+ to a frame relay network, or use frame relay API to develope
+ custom applications over the Frame Relay protocol.
X This feature also contains the Ethernet Bridging over Frame Relay,
- where a WANPIPE frame relay link can be directly connected to the Linux
- kernel bridge. If you say N, the frame relay support will
- not be included in the driver. The Frame Relay option is
+ where a WANPIPE frame relay link can be directly connected to the
+ Linux kernel bridge. If you say N, the frame relay support will
+ not be included in the driver. The Frame Relay option is
X supported on S514-PCI and S508-ISA cards.
X
X WANPIPE PPP support
@@ -8582,70 +9669,71 @@
X the PPP support will not be included in the driver. The PPP option
X is supported on S514-PCI/S508-ISA cards.
X
-WANPIPE MultiPort PPP support
+WANPIPE Multi-Port PPP support
X CONFIG_WANPIPE_MULTPPP
X Say Y to this option if you are planning to connect a WANPIPE card
- to a leased line using Point-to-Point protocol (PPP). Note, the
- MultiPort PPP uses the Linux Kernel SyncPPP protocol over the Sangoma
- HDLC Streaming adapter. In this case each Sangoma adapter port
- can support an independent PPP connection. For example, a single
- Quad-Port PCI adapter can support up to four independent
- PPP links. If you say N,the PPP support will not be included
- in the driver. The PPP option is supported on S514-PCI/S508-ISA cards.
-
+ to a leased line using Point-to-Point protocol (PPP). Note, the
+ MultiPort PPP uses the Linux Kernel SyncPPP protocol over the
+ Sangoma HDLC Streaming adapter. In this case each Sangoma adapter
+ port can support an independent PPP connection. For example, a
+ single Quad-Port PCI adapter can support up to four independent
+ PPP links. If you say N,the PPP support will not be included in the
+ driver. The PPP option is supported on S514-PCI/S508-ISA cards.
+
X WANPIPE Cisco HDLC support
X CONFIG_WANPIPE_CHDLC
X Say Y to this option if you are planning to connect a WANPIPE card
X to a leased line using the Cisco HDLC protocol. This now supports
- Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
- This support also allows user to build applications using the
- HDLC streaming API.
-
+ Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
+ This support also allows user to build applications using the
+ HDLC streaming API.
+
X CHDLC Streaming driver also supports MULTILINK PPP
X support that can bind multiple WANPIPE T1 cards into
X a single logical channel.
-
- If you say N, the Cisco HDLC support and
- HDLC streaming API and MULTILINK PPP will not be
+
+ If you say N, the Cisco HDLC support and
+ HDLC streaming API and MULTILINK PPP will not be
X included in the driver.
X
-MultiGate/COMX support
+MultiGate (COMX) synchronous serial board support
X CONFIG_COMX
X Say Y if you want to use any board from the MultiGate (COMX) family.
X These boards are synchronous serial adapters for the PC,
X manufactured by ITConsult-Pro Co, Hungary.
X
- Read linux/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 <in...@itc.hu>.
+ 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 <in...@itc.hu>.
X
X You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
X use this driver.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called comx.o.
+ <file:Documentation/modules.txt>. The module will be called comx.o.
X
-COMX/CMX/HiCOMX board support
+Support for COMX/CMX/HiCOMX boards
X CONFIG_COMX_HW_COMX
X Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
- MultiGate family. Say Y if you have one of these.
+ MultiGate family. Say Y if you have one of these.
X
X You will need additional firmware to use these cards, which are
- downloadable from ftp://ftp.itc.hu/.
+ downloadable from <ftp://ftp.itc.hu/>.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called comx-hw-comx.o.
+ <file:Documentation/modules.txt>. The module will be called
+ comx-hw-comx.o.
X
-LoCOMX board support
+Support for LoCOMX board
X CONFIG_COMX_HW_LOCOMX
X Hardware driver for the 'LoCOMX' board from the MultiGate family.
X Say Y if you have a board like this.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X comx-hw-locomx.o.
X
-MixCOM board support
+Support for MixCOM board
X CONFIG_COMX_HW_MIXCOM
X Hardware driver for the 'MixCOM' board from the MultiGate family.
X Say Y if you have a board like this.
@@ -8655,63 +9743,63 @@
X configuration. The ISDN interface of this card is Teles 16.3
X compatible, you should enable it in the ISDN configuration menu. The
X driver for the flash ROM of this card is available separately on
- ftp://ftp.itc.hu/.
+ <ftp://ftp.itc.hu/>.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X comx-hw-mixcom.o.
X
-i810 TCO support
+i810 TCO timer/watchdog support
X CONFIG_I810_TCO
X Hardware driver for the TCO timer built into the Intel i810 and i815
- chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
- timer that will reboot the machine after it's second expiration. The
- expiration time can be configured by commandline argument
- "i810_margin=<n>" where <n> is the counter initial value. It is
- decremented every 0.6 secs, the default is 50 which gives a timeout
- of 30 seconds and one minute until reset.
+ chipset family. The TCO (Total Cost of Ownership) timer is a
+ watchdog timer that will reboot the machine after its second
+ expiration. The expiration time can be configured by commandline
+ argument "i810_margin=<n>" where <n> is the counter initial value.
+ It is decremented every 0.6 secs, the default is 50 which gives a
+ timeout of 30 seconds and one minute until reset.
X
X On some motherboards the driver may fail to reset the chipset's
- NO_REBOOT flag which prevents the watchdog from rebooting the machine.
- If this is the case you will get a kernel message like
+ NO_REBOOT flag which prevents the watchdog from rebooting the
+ machine. If this is the case you will get a kernel message like
X "i810tco init: failed to reset NO_REBOOT flag".
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X i810-tco.o.
X
-MultiGate Cisco-HDLC and synchronous PPP protocol support
+Support for HDLC and syncPPP protocols on MultiGate boards
X CONFIG_COMX_PROTO_PPP
X Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
X boards. Say Y if you want to use either protocol on your MultiGate
X boards.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X comx-proto-ppp.o.
X
-MultiGate LAPB protocol support
+Support for LAPB protocol on MultiGate boards
X CONFIG_COMX_PROTO_LAPB
- LAPB protocol driver for all MultiGate boards. Say Y if you
+ LAPB protocol driver for all MultiGate boards. Say Y if you
X want to use this protocol on your MultiGate boards.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X comx-proto-lapb.o.
X
-MultiGate Frame Relay protocol support
+Support for Frame Relay on MultiGate boards
X CONFIG_COMX_PROTO_FR
- Frame Relay protocol driver for all MultiGate boards. Say Y if you
+ Frame Relay protocol driver for all MultiGate boards. Say Y if you
X want to use this protocol on your MultiGate boards.
X
X If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
X comx-proto-fr.o.
X
-Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
+Cyclom 2X(tm) multiprotocol cards
X 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
X adapter with data transfer rates up to 512 Kbps. These cards support
X the X.25 and SNA related protocols. If you have one or more of these
X cards, say Y to this option. The next questions will ask you about
@@ -8719,10 +9807,11 @@
X supported).
X
X 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 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 ).
+ wanconfig tarball in
+ <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>).
X
X Feel free to contact me or the cycsyn-devel mailing list at
X ac...@conectiva.com.br and cycsyn...@bazar.conectiva.com.br for
@@ -8732,12 +9821,12 @@
X The driver will be compiled as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
X The module will be called cyclomx.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
X
X Cyclom 2X X.25 support
X CONFIG_CYCLOMX_X25
X Say Y to this option if you are planning to connect a Cyclom 2X card
- to an X.25 network.
+ to an X.25 network.
X
X If you say N, the X.25 support will not be included in the driver
X (saves about 11 KB of kernel memory).
@@ -8747,41 +9836,69 @@
X Say Y to this option if your Linux box contains a WAN card supported
X by this driver and you are planning to connect the box to a WAN
X ( = Wide Area Network). You will need supporting software from
- http://hq.pm.waw.pl/hdlc/.
+ <http://hq.pm.waw.pl/hdlc/>.
X Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
X Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
X
X If unsure, say N here.
X
-Synchronous Point-to-Point Protocol (PPP)
+Raw HDLC support
+CONFIG_HDLC_RAW
+ Say Y to this option if you want generic HDLC driver to support
+ raw HDLC over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Cisco HDLC support
+CONFIG_HDLC_CISCO
+ Say Y to this option if you want generic HDLC driver to support
+ Cisco HDLC over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Frame-Relay HDLC support
+CONFIG_HDLC_FR
+ Say Y to this option if you want generic HDLC driver to support
+ Frame-Relay protocol over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Frame-Relay bridging support
+CONFIG_HDLC_FR_BRIDGE
+ Say Y to this option if you want generic HDLC driver to support
+ bridging LAN frames over Frame-Relay links.
+
+ If unsure, say N here.
+
+Synchronous Point-to-Point Protocol (PPP) support
X CONFIG_HDLC_PPP
X Say Y to this option if you want generic HDLC driver to support
X PPP over WAN (Wide Area Network) connections.
X
X If unsure, say N here.
X
-CCITT X.25 protocol
+CCITT X.25 over HDLC support
X CONFIG_HDLC_X25
X Say Y to this option if you want generic HDLC driver to support
X X.25 protocol over WAN (Wide Area Network) connections.
X
X If unsure, say N here.
X
-SDL RISCom/N2 driver
+SDL RISCom/N2 support
X CONFIG_N2
X This driver is for RISCom/N2 single or dual channel ISA cards
- made by SDL Communications Inc. If you have such a card,
- say Y here and see http://hq.pm.waw.pl/pub/hdlc/
+ made by SDL Communications Inc. If you have such a card,
+ say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>.
X
X Note that N2csu and N2dds cards are not supported by this driver.
X
X If unsure, say N here.
X
-Moxa C101 driver
+Moxa C101 support
X CONFIG_C101
X This driver is for C101 SuperSync ISA cards made by Moxa
X Technologies Co., Ltd. If you have such a card,
- say Y here and see http://hq.pm.waw.pl/pub/hdlc/
+ say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>
X
X If unsure, say N here.
X
@@ -8803,21 +9920,21 @@
X If your Linux machine will be connected to an Ethernet and you have
X an Ethernet network interface card (NIC) installed in your computer,
X say Y here and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You will then also have
+ <http://www.linuxdoc.org/docs.html#howto>. You will then also have
X to say Y to the driver for your particular NIC.
X
X Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
X the questions about Ethernet network cards. If unsure, say N.
X
X Western Digital/SMC cards
X CONFIG_NET_VENDOR_SMC
X If you have a network (Ethernet) card belonging to this class, say Y
X and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
X the questions about Western Digital cards. If you say Y, you will be
X asked for your specific card in the following questions.
X
@@ -8825,32 +9942,32 @@
X CONFIG_WD80x3
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called wd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called wd.o. 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>.
X
X SMC Ultra MCA support
X CONFIG_ULTRAMCA
X If you have a network (Ethernet) card of this type and are running
X an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called smc-mca.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called smc-mca.o. 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>.
X
X SMC Ultra support
X CONFIG_ULTRA
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
-
+ <http://www.linuxdoc.org/docs.html#howto>.
+
X Important: There have been many reports that, with some motherboards
X mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
X such as some BusLogic models) causes corruption problems with many
@@ -8860,44 +9977,44 @@
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called smc-ultra.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called smc-ultra.o. 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>.
X
X SMC Ultra32 EISA support
X CONFIG_ULTRA32
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called smc-ultra32.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt as well
- as Documentation/networking/net-modules.txt.
+ The module will be called smc-ultra32.o. 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>.
X
-SMC 9194 Support
+SMC 9194 support
X CONFIG_SMC9194
X This is support for the SMC9xxx based Ethernet cards. Choose this
X option if you have a DELL laptop with the docking station, or
- another SMC9192/9194 based chipset. Say Y if you want it compiled
+ another SMC9192/9194 based chipset. Say Y if you want it compiled
X into the kernel, and read the file
- Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X
X 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 smc9194.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt as
- well as Documentation/networking/net-modules.txt.
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called smc9194.o. 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>.
X
-PCI NE2000 support
+PCI NE2000 and clones support
X CONFIG_NE2K_PCI
X This driver is for NE2000 compatible PCI cards. It will not work
X with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
X support" below). If you have a PCI NE2000 network (Ethernet) card,
X say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver also works for the following NE2000 clone cards:
X RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
@@ -8906,64 +10023,64 @@
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called ne2k-pci.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ne2k-pci.o. 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>.
X
X Racal-Interlan (Micom) NI cards
X CONFIG_NET_VENDOR_RACAL
X If you have a network (Ethernet) card belonging to this class, such
X as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X
X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
X the questions about NI cards. If you say Y, you will be asked for
X your specific card in the following questions.
X
-NI5010 support (EXPERIMENTAL)
+NI5010 support
X CONFIG_NI5010
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that this is still
+ <http://www.linuxdoc.org/docs.html#howto>. Note that this is still
X experimental code.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called ni5010.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni5010.o. 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>.
X
X NI5210 support
X CONFIG_NI52
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called ni52.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni52.o. 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>.
X
X NI6510 support
X CONFIG_NI65
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).
- The module will be called ni65.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni65.o. 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>.
X
X RealTek RTL-8139C+ 10/100 PCI Fast Ethernet Adapter support
X CONFIG_8139CP
X This is a driver for the Fast Ethernet PCI network cards based on
X the RTL8139C+ chips. If you have one of those, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
@@ -8974,21 +10091,23 @@
X CONFIG_8139TOO
X This is a driver for the Fast Ethernet PCI network cards based on
X the RTL8139 chips. If you have one of those, say Y and read
- Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/8139too.txt> as well as the
+ Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called 8139too.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called 8139too.o.
X
X Use PIO instead of MMIO
X CONFIG_8139TOO_PIO
X This instructs the driver to use programmed I/O ports (PIO) instead
- of PCI shared memory (MMIO). This can possibly solve some problems in
- case your mainboard has memory consistency issues. If unsure, say N.
+ of PCI shared memory (MMIO). This can possibly solve some problems
+ in case your mainboard has memory consistency issues. If unsure,
+ say N.
X
-Support for automatic channel equalization (EXPERIMENTAL)
+Support for automatic channel equalization
X CONFIG_8139TOO_TUNE_TWISTER
X This implements a function which might come in handy in case you are
X using low quality on long cabling. It tries to match the transceiver
@@ -8998,40 +10117,40 @@
X Support for older RTL-8129/8130 boards
X CONFIG_8139TOO_8129
X This enables support for the older and uncommon RTL-8129 and
- RTL-8130 chips, which support MII via an external transceiver, instead
- of an internal one. Disabling this option will save some memory
- by making the code size smaller. If unsure, say Y.
+ RTL-8130 chips, which support MII via an external transceiver,
+ instead of an internal one. Disabling this option will save some
+ memory by making the code size smaller. If unsure, say Y.
X
-SiS 900 PCI Fast Ethernet Adapter support
+SiS 900/7016 PCI Fast Ethernet Adapter support
X CONFIG_SIS900
X This is a driver for the Fast Ethernet PCI network cards based on
X the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
- SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
+ SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
X read the Ethernet-HOWTO, available at
- http://www.linuxdoc.org/docs.html#howto . Please read
- Documentation/networking/sis900.txt and comments at the beginning of
- drivers/net/sis900.c for more information.
+ <http://www.linuxdoc.org/docs.html#howto>. Please read
+ <file:Documentation/networking/sis900.txt> and comments at the
+ beginning of <file:drivers/net/sis900.c> for more information.
X
X This driver also supports AMD 79C901 HomePNA so that you can use
X your phone line as a network cable.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called sis900.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called sis900.o.
X
X Packet Engines Yellowfin Gigabit-NIC / Symbios 53c885 support
X CONFIG_YELLOWFIN
X Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
X adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
X used by the Beowulf Linux cluster project. See
- http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for more
+ <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
X information about this driver in particular and Beowulf in general.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called yellowfin.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called yellowfin.o.
X
X General Instruments Surfboard 1000
X CONFIG_NET_SB1000
@@ -9044,29 +10163,29 @@
X
X At present this driver only compiles as a module, so say M here if
X you have this card. The module will be called sb1000.o. Then read
- Documentation/networking/README.sb1000 for information on how to use
- this module, as it needs special ppp scripts for establishing a
- connection. Further documentation and the necessary scripts can be
+ <file:Documentation/networking/README.sb1000> for information on how
+ to use this module, as it needs special ppp scripts for establishing
+ a connection. Further documentation and the necessary scripts can be
X found at:
X
- http://www.jacksonville.net/~fventuri/
- http://home.adelphia.net/~siglercm/sb1000.html
- http://linuxpower.cx/~cable/
+ <http://www.jacksonville.net/~fventuri/>
+ <http://home.adelphia.net/~siglercm/sb1000.html>
+ <http://linuxpower.cx/~cable/>
X
X If you don't have this card, of course say N.
X
-Adaptec Starfire support (EXPERIMENTAL)
+Adaptec Starfire support
X CONFIG_ADAPTEC_STARFIRE
X Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
X adapter. The DuraLAN chip is used on the 64 bit PCI boards from
X Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
X driver.
-
+
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called starfire.o.
-
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called starfire.o.
+
X Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
X CONFIG_ACENIC
X Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
@@ -9078,16 +10197,16 @@
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called acenic.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called acenic.o.
X
-Omit support for older Tigon I based AceNICs
+Omit support for old Tigon I based AceNICs
X CONFIG_ACENIC_OMIT_TIGON_I
X Say Y here if you only have Tigon II based AceNICs and want to leave
X out support for the older Tigon I based cards which are no longer
X being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
- version)). This will reduce the size of the driver object by
- app. 100KB. If you are not sure whether your card is a Tigon I or a
+ version)). This will reduce the size of the driver object by
+ app. 100KB. If you are not sure whether your card is a Tigon I or a
X Tigon II, say N here.
X
X The safe and default value for this is N.
@@ -9107,148 +10226,170 @@
X The driver also supports the following adapters from Allied Telesyn:
X - AT2970...
X
- The dual link adapters support a link-failover feature.
- Read Documentation/networking/sk98lin.txt for information about
+ The dual link adapters support a link-failover feature. Read
+ <file:Documentation/networking/sk98lin.txt> for information about
X optional driver parameters.
X Questions concerning this driver may be addressed to:
X li...@syskonnect.de
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called sk98lin.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called sk98lin.o.
+
+Sun GEM support
+CONFIG_SUNGEM
+ Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
+ <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
X
X MyriCOM Gigabit Ethernet support
X CONFIG_MYRI_SBUS
- This driver supports MyriCOM Sbus gigabit ethernet cards.
+ This driver supports MyriCOM Sbus gigabit Ethernet cards.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called myri_sbus.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called myri_sbus.o.
X
X D-Link 2000-based Gigabit Ethernet support
X CONFIG_DL2K
X This driver supports D-Link 2000-based gigabit ethernet cards, which
X includes
- D-Link DGE-550T Gigabit Ethernet Adapter.
- D-Link DL2000-based Gigabit Ethernet Adapter.
+ D-Link DGE-550T Gigabit Ethernet Adapter.
+ D-Link DL2000-based Gigabit Ethernet Adapter.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called dl2k.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called dl2k.o.
X
X AMD LANCE and PCnet (AT1500 and NE2100) support
X CONFIG_LANCE
X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
+ <http://www.linuxdoc.org/docs.html#howto>. Some LinkSys cards are
X of this type.
X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called lance.o.
SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi
echo 'End of part 008'
echo 'File patch-2.4.15 is continued in part 009'
echo "009" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:45 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part009

#!/bin/sh -x
# this is part 009 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 009; then

echo "Please unpack part $Scheck next!"
exit 1
else
exit 0
fi
) < _shar_seq_.tmp || exit 1
if test ! -f _shar_wnt_.tmp; then
echo 'x - still skipping patch-2.4.15'
else
echo 'x - continuing with patch-2.4.15'
sed 's/^X//' << 'SHAR_EOF' >> 'patch-2.4.15' &&

+ say M here and read <file:Documentation/modules.txt>. This is

+ recommended. The module will be called lance.o.
X
X SGI IOC3 Ethernet
X CONFIG_SGI_IOC3_ETH

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.

+
+National Semiconductor DP83902AV support
+CONFIG_STNIC
+ Support for cards based on the National Semiconductor DP83902AV
+ ST-NIC Serial Network Interface Controller for Twisted Pair. This
+ 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".
X
X 3COM cards
X CONFIG_NET_VENDOR_3COM

X If you have a network (Ethernet) card belonging to this class, say Y
X and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all

X the questions about 3COM cards. If you say Y, you will be asked for

X your specific card in the following questions.
X

-3c501 support
+3c501 "EtherLink" support
X CONFIG_EL1

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
+ <http://www.linuxdoc.org/docs.html#howto>. Also, consider buying a
X new card, since the 3c501 is slow, broken, and obsolete: you will
- have problems. Some people suggest to ping ("man ping") a nearby
+ have problems. Some people suggest to ping ("man ping") a nearby
X machine every minute ("man cron") when using this card.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called 3c501.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called 3c501.o. 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>.
X

-3c503 support
+3c503 "EtherLink II" support
X CONFIG_EL2

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called 3c503.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called 3c503.o. 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>.
X

-3c505 support
+3c505 "EtherLink Plus" support
X CONFIG_ELPLUS
X Information about this network (Ethernet) card can be found in
- Documentation/networking/3c505.txt. If you have a card of this type,
- say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/3c505.txt>. If you have a card of
+ this type, say Y and read the Ethernet-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c505.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c505.o.
X
-3c507 support (EXPERIMENTAL)
+3c507 (EtherLink 16) support
X CONFIG_EL16

- The module will be called 3c507.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called 3c507.o. 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>.
X

-3c523 support
+3c523 "EtherlinkMC" support
X CONFIG_ELMC

- The module will be called 3c523.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called 3c523.o. 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>.
X

-3c527 support
+3c527 "EtherLink/MC 32" support
X CONFIG_ELMC_II

- The module will be called 3c527.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called 3c527.o. 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>.
X

-3c509/3c579 support
+3c509/3c529 (MCA)/3c579 "EtherLink III" support
X CONFIG_EL3
X If you have a network (Ethernet) card belonging to the 3Com
X EtherLinkIII series, say Y and read the Ethernet-HOWTO, available

- from http://www.linuxdoc.org/docs.html#howto .

+ from <http://www.linuxdoc.org/docs.html#howto>.
X
X If your card is not working you may need to use the DOS
X setup disk to disable Plug & Play mode, and to select the default
@@ -9256,23 +10397,23 @@
X
X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c509.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c509.o.
X
X 3c515 ISA Fast EtherLink
X CONFIG_3C515
X If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
X network card, say Y and read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c515.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c515.o.
X
-3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
+3c590/3c900 series (592/595/597) "Vortex/Boomerang/Cyclone" support
X CONFIG_VORTEX
X This option enables driver support for a large number of 10mbps and
X 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
@@ -9283,15 +10424,16 @@
X "Tornado" (3c905) PCI
X "Hurricane" (3c555/3cSOHO) PCI
X
- If you have such a card, say Y and read the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto . More specific
- information is in Documentation/networking/vortex.txt and in the
- comments at the beginning of drivers/net/3c59x.c.
+ If you have such a card, say Y and read the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>. More
+ specific information is in
+ <file:Documentation/networking/vortex.txt> and in the comments at
+ the beginning of <file:drivers/net/3c59x.c>.
X
X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>.
X
X Other ISA cards
X CONFIG_NET_ISA
@@ -9299,19 +10441,20 @@
X bus system (that's the way the cards talks to the other components
X of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
X Make sure you know the name of your card. Read the Ethernet-HOWTO,

- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X

X If unsure, say Y.
X

X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all

X the remaining ISA network card questions. If you say Y, you will be

X asked for your specific card in the following questions.
X

X Generic ARCnet support
X CONFIG_ARCNET
X If you have a network card of this type, say Y and check out the
- (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
+ (arguably) beautiful poetry in
+ <file:Documentation/networking/arcnet.txt>.
X
X You need both this driver, and the driver for the particular ARCnet
X chipset of your card. If you don't know, then it's probably a
@@ -9319,26 +10462,14 @@
X support" below.
X
X You might also want to have a look at the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
+ from <http://www.linuxdoc.org/docs.html#howto>(even though ARCnet
X is not really Ethernet).

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called arcnet.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

-
-Enable arc0e (ARCnet "ether-encap" packet format)
-CONFIG_ARCNET_ETH
- This allows you to use "Ethernet encapsulation" with your ARCnet
- card via the virtual arc0e device. You only need arc0e if you want
- to talk to nonstandard ARCnet software, specifically,
- DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
- communicate with industry-standard RFC1201 implementations, like the
- arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
- is included automatically as the arc0 device. Please read the
- ARCnet documentation in Documentation/networking/arcnet.txt for more
- information about using arc0e and arc0s.
+ The module will be called arcnet.o. 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>.
X

X Enable old ARCNet packet format (RFC 1051)
X CONFIG_ARCNET_1051
@@ -9350,33 +10481,48 @@
X industry-standard RFC1201 implementations, like the arcether.com
X packet driver or most DOS/Windows ODI drivers. RFC1201 is included
X automatically as the arc0 device. Please read the ARCnet
- documentation in Documentation/networking/arcnet.txt for more
+ documentation in <file:Documentation/networking/arcnet.txt> for more
X information about using arc0e and arc0s.
X
+Enable standard ARCNet packet format (RFC 1201)
+CONFIG_ARCNET_1201
+ This allows you to use RFC1201 with your ARCnet card via the virtual
+ arc0 device. You need to say Y here to communicate with
+ industry-standard RFC1201 implementations, like the arcether.com
+ packet driver or most DOS/Windows ODI drivers. Please read the
+ ARCnet documentation in <file:Documentation/networking/arcnet.txt>
+ for more information about using arc0.
+
+Enable raw mode packet interface
+CONFIG_ARCNET_RAW
+ ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely
+ to work unless talking to a copy of the same Linux arcnet driver,
+ but perhaps marginally faster in that case.
+
X ARCnet COM90xx (normal) chipset driver
X CONFIG_ARCNET_COM90xx
X This is the chipset driver for the standard COM90xx cards. If you
X have always used the old ARCnet driver without knowing what type of
- card you had, this is probably the one for you.
+ card you had, this is probably the one for you.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called com90xx.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called com90xx.o. 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>.
X

X ARCnet COM90xx (IO mapped) chipset driver
X CONFIG_ARCNET_COM90xxIO
X This is the chipset driver for the COM90xx cards, using them in
X IO-mapped mode instead of memory-mapped mode. This is slower than
X the normal driver. Only use it if your card doesn't support shared
- memory.
+ memory.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called com90io.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called com90io.o. 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>.
X

X ARCnet COM90xx (RIM I) chipset driver
X CONFIG_ARCNET_RIM_I
@@ -9387,197 +10533,198 @@

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you

- want). The module will be called arc-rimi.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt as
- well as Documentation/networking/net-modules.txt.

+ want). The module will be called arc-rimi.o. 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>.
X
X ARCnet COM20020 chipset driver
X CONFIG_ARCNET_COM20020
X This is the driver for the new COM20020 chipset. It supports such
X things as promiscuous mode, so packet sniffing is possible, and
- extra diagnostic information.
+ extra diagnostic information.
X

X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called com20020.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called com20020.o. 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>.
X

X Cabletron E21xx support
X CONFIG_E2100

- The module will be called e2100.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called e2100.o. 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>.
X

-CS89x0 support
+CS89x0 support (Daynaport CS and LC cards)
X CONFIG_CS89x0
X Support for CS89x0 chipset based Ethernet cards. If you have a
X network (Ethernet) card of this type, say Y and read the
X Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto as well as
- Documentation/networking/cs89x0.txt.
+ <http://www.linuxdoc.org/docs.html#howto> as well as
+ <file:Documentation/networking/cs89x0.txt>.
X
X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- cs89x.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called cs89x.o.
X
-DEPCA support
+DEPCA, DE10x, DE200, DE201, DE202, DE422 support
X CONFIG_DEPCA

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto as well as
- drivers/net/depca.c.
+ <http://www.linuxdoc.org/docs.html#howto> as well as
+ <file:drivers/net/depca.c>.
X
X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called
X depca.o.
X
-EtherWorks 3 support
+EtherWORKS 3 (DE203, DE204, DE205) support
X CONFIG_EWRK3
X This driver supports the DE203, DE204 and DE205 network (Ethernet)
X cards. If this is for you, say Y and read
- Documentation/networking/ewrk3.txt in the kernel source as well as
- the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/ewrk3.txt> in the kernel source as
+ well as the Ethernet-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- ewrk3.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called ewrk3.o.
X
X SEEQ8005 support
X CONFIG_SEEQ8005
- This is a driver for the SEEQ 8005 network (Ethernet) card. If this
+ This is a driver for the SEEQ 8005 network (Ethernet) card. If this
X is for you, read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

X If you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- at1700.o.
+ <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called at1700.o.
X
X FMV-181/182/183/184 support
X CONFIG_FMV18X
X If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,

X say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you use an FMV-183 or FMV-184 and it is not working, you may need
X to disable Plug & Play mode of the card.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called fmv18x.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called fmv18x.o. 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>.
X

-EtherExpress PRO support
+EtherExpressPro support/EtherExpress 10 (i82595) support
X CONFIG_EEXPRESS_PRO
X If you have a network (Ethernet) card of this type, say Y. This
- driver supports intel i82595{FX,TX} based boards. Note however
+ driver supports intel i82595{FX,TX} based boards. Note however
X that the EtherExpress PRO/100 Ethernet card has its own separate
- driver. Please read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ driver. Please read the Ethernet-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called eepro.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called eepro.o. 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>.
X

-EtherExpress support
+EtherExpress 16 support
X CONFIG_EEXPRESS
X If you have an EtherExpress16 network (Ethernet) card, say Y and
X read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that the Intel
+ <http://www.linuxdoc.org/docs.html#howto>. Note that the Intel
X EtherExpress16 card used to be regarded as a very poor choice
X because the driver was very unreliable. We now have a new driver
X that should do better.

X
X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- eexpress.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called eexpress.o.
X
X Packet Engines Hamachi GNIC-II support
X CONFIG_HAMACHI
X If you have a Gigabit Ethernet card of this type, say Y and read

X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- hamachi.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called hamachi.o.
X
X HP PCLAN+ (27247B and 27252A) support
X CONFIG_HPLAN_PLUS

- The module will be called hp-plus.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called hp-plus.o. 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>.
X

X HP PCLAN (27245 and other 27xxx series) support
X CONFIG_HPLAN

- The module will be called hp.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called hp.o. 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>.
X

X HP 10/100VG PCLAN (ISA, EISA, PCI) support
X CONFIG_HP100

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- hp100.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called hp100.o.
X
X NE2000/NE1000 support
X CONFIG_NE2000

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
+ <http://www.linuxdoc.org/docs.html#howto>. Many Ethernet cards
X without a specific driver are compatible with NE2000.
X
X If you have a PCI NE2000 card however, say N here and Y to "PCI
@@ -9588,74 +10735,76 @@

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called ne.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called ne.o. 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>.
X

-National Semiconductor DP83810 series PCI Ethernet support
+National Semiconductor DP8381x series PCI Ethernet support
X CONFIG_NATSEMI
X This driver is for the National Semiconductor DP83810 series,
- including the 83815 chip.
- More specific information and updates are available from
- http://www.scyld.com/network/natsemi.html
+ which is used in cards from PureData, NetGear, Linksys
+ and others, including the 83815 chip.
+ More specific information and updates are available from
+ <http://www.scyld.com/network/natsemi.html>.
X
X SK_G16 support
X CONFIG_SK_G16

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X NE/2 (ne2000 MCA version) support
X CONFIG_NE2_MCA

- The module will be called ne2.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called ne2.o. 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>.
X

X SKnet MCA support
X CONFIG_SKMC
- These are Micro Channel ethernet adapters. You need to say Y to "MCA
- support" in order to use this driver. Supported cards are the SKnet
- Junior MC2 and the SKnet MC2(+). The driver automatically
+ These are Micro Channel Ethernet adapters. You need to say Y to "MCA
+ support" in order to use this driver. Supported cards are the SKnet
+ Junior MC2 and the SKnet MC2(+). The driver automatically
X distinguishes between the two cards. Note that using multiple boards
- of different type hasn't been tested with this driver. Say Y if you
- have one of these ethernet adapters.
+ of different type hasn't been tested with this driver. Say Y if you
+ have one of these Ethernet adapters.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module is called sk_mca.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module is called sk_mca.o. 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>.
X

X IBM LAN Adapter/A support
X CONFIG_IBMLANA
- This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
- to use this driver. It is both available as an in-kernel 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 Documentation/modules.txt as well as
- 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 sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. 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 boards with
- this driver should be possible, but has not been tested up to now due
- to lack of hardware.
+ This is a Micro Channel Ethernet adapter. You need to set
+ CONFIG_MCA to use this driver. It is both available as an in-kernel
+ 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
+ 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
+ boards with this driver should be possible, but has not been tested
+ up to now due to lack of hardware.
X
X EISA, VLB, PCI and on board controllers
X CONFIG_NET_PCI
X This is another class of network cards which attach directly to the
X bus. If you have one of those, say Y and read the Ethernet-HOWTO,

- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X
X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all

X the questions about this class of network cards. If you say Y, you
X will be asked for your specific card in the following questions. If
X you are unsure, say Y.
@@ -9664,98 +10813,100 @@
X CONFIG_PCNET32
X If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
X answer Y here and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called pcnet32.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called pcnet32.o. 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>.
X

X Ansel Communications EISA 3200 support
X CONFIG_AC3200

- The module will be called ac3200.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called ac3200.o. 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>.
X

-Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
+Mylex EISA LNE390A/LNE390B support
X CONFIG_LNE390

- The module will be called lne390.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called lne390.o. 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>.
X

X Novell/Eagle/Microdyne NE3210 EISA support
X CONFIG_NE3210

X If you have a network (Ethernet) card of this type, say Y and read
X the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto . Note that this driver
+ <http://www.linuxdoc.org/docs.html#howto>. Note that this driver
X will NOT WORK for NE3200 cards as they are completely different.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called ne3210.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called ne3210.o. 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>.
X

X Apricot Xen-II on board Ethernet
X CONFIG_APRICOT
X If you have a network (Ethernet) controller of this type, say Y and
X read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- apricot.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called apricot.o.
X
X Generic DECchip & DIGITAL EtherWORKS PCI/EISA
X CONFIG_DE4X5
X This is support for the DIGITAL series of PCI/EISA Ethernet cards.
- These include the DE425, DE434, DE435, DE450 and DE500 models. If
+ These include the DE425, DE434, DE435, DE450 and DE500 models. If
X you have a network card of this type, say Y and read the
X Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/de4x5.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in
+ <file:Documentation/networking/de4x5.txt>.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called de4x5.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called de4x5.o. 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>.
X

X DECchip Tulip (dc21x4x) PCI support
X CONFIG_TULIP
X This driver is developed for the SMC EtherPower series Ethernet
- cards and also works with cards based on the DECchip
- 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
- of this type. (If your card is NOT SMC EtherPower 10/100 PCI
+ cards and also works with cards based on the DECchip
+ 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
+ of this type. (If your card is NOT SMC EtherPower 10/100 PCI
X (smc9332dst), you can also try the driver for "Generic DECchip"
- cards, above. However, most people with a network card of this type
+ cards, above. However, most people with a network card of this type
X will say Y here.) Do read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/tulip.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in
+ <file:Documentation/networking/tulip.txt>.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called tulip.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called tulip.o. 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>.
X

-New Tulip bus configuration (EXPERIMENTAL)
-CONFIG_TULIP_MWI
+New Tulip bus configuration
+CONFIG_TULIP_MWI
X This configures your Tulip card specifically for the card and
X system cache line size type you are using.
X
@@ -9763,34 +10914,34 @@

X
X If unsure, say N.
X

-Digi Intl. RightSwitch support
+Digi Intl. RightSwitch SE-X support
X CONFIG_DGRS
X This is support for the Digi International RightSwitch series of
X PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
- models. If you have a network card of this type, say Y and read the
+ models. If you have a network card of this type, say Y and read the
X Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/dgrs.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in <file:Documentation/networking/dgrs.txt>.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called dgrs.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called dgrs.o. 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>.
X

-EtherExpress PRO/100 support
+EtherExpress Pro/100 support
X CONFIG_EEPRO100
X If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
X card, say Y and read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called eepro100.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called eepro100.o. 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>.
X

-Enable Power Management (EXPERIMENTAL)
+Enable Power Management
X CONFIG_EEPRO100_PM
X Many Intel EtherExpress PRO/100 PCI network cards are capable
X of providing power management capabilities. To make use of these
@@ -9802,34 +10953,40 @@
X
X It is recommended to say N here.
X
-ICL EtherTeam 16i/32 support (EXPERIMENTAL)
+Myson MTD-8xx PCI Ethernet support
+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>.
+
+ICL EtherTeam 16i/32 support
X CONFIG_ETH16I

- The module will be called eth16i.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called eth16i.o. 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>.
X

-TI ThunderLAN support (EXPERIMENTAL)
+TI ThunderLAN support
X CONFIG_TLAN
X If you have a PCI Ethernet network card based on the ThunderLAN chip
X which is supported by this driver, say Y and read the
X Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X Devices currently supported by this driver are Compaq Netelligent,
- Compaq NetFlex and Olicom cards. Please read the file
- Documentation/networking/tlan.txt for more details.
+ Compaq NetFlex and Olicom cards. Please read the file
+ <file:Documentation/networking/tlan.txt> for more details.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called tlan.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called tlan.o. 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>.
X

X Please email feedback to torben.m...@compaq.com.
X
@@ -9840,131 +10997,164 @@

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called via-rhine.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called via-rhine.o. 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>.
X

-PCI DM9102(A)/DM9132/DM9801 support
+Davicom DM910x/DM980x support
X CONFIG_DM9102
X This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
- Davicom ( http://www.davicom.com.tw ). If you have such a network
- (Ethernet) card, say Y. Some information is contained in the file
- Documentation/networking/dmfe.txt.
-
+ 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>.
+

X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called dmfe.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called dmfe.o. 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>.
X

-Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
+Racal-Interlan EISA ES3210 support
X CONFIG_ES3210

- The module will be called es3210.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.

+ The module will be called es3210.o. 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>.
X

X SMC EtherPower II
X CONFIG_EPIC100
X This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
X which is based on the SMC83c17x (EPIC/100).
X More specific information and updates are available from
- http://www.scyld.com/network/epic100.html
+ <http://www.scyld.com/network/epic100.html>.
X
-SGI Seeq ethernet controller support
+DEC LANCE Ethernet controller support
+CONFIG_DECLANCE
+ This driver is for the series of Ethernet controllers produced by
+ DEC (now Compaq) based on the AMD Lance chipset, including the
+ DEPCA series. (This chipset is better known via the NE2100 cards.)
+
+SGI Seeq Ethernet controller support
X CONFIG_SGISEEQ
X Say Y here if you have an Seeq based Ethernet network card. This is
X used in many Silicon Graphics machines.
X
-Sundance "Alta" PCI Ethernet support
+Sundance Alta PCI Ethernet support
X CONFIG_SUNDANCE
X This driver is for the Sundance "Alta" chip.
X More specific information and updates are available from
- http://www.scyld.com/network/sundance.html
+ <http://www.scyld.com/network/sundance.html>.
+
+Sun3/Sun3x on-board LANCE support
+CONFIG_SUN3LANCE
+ Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
+ featured an AMD Lance 10Mbit Ethernet controller on board; say Y
+ here to compile in the Linux driver for this and enable Ethernet.
+ General Linux information on the Sun 3 and 3x series (now
+ discontinued) is at
+ <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+ If you're not building a kernel for a Sun 3, say N.
+
+Sun3 on-board Intel 82586 support
+CONFIG_SUN3_82586
+ This driver enables support for the on-board Intel 82586 based
+ Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
+ that this driver does not support 82586-based adapters on additional
+ VME boards.
X
X Winbond W89c840 PCI Ethernet support
X CONFIG_WINBOND_840
X This driver is for the Winbond W89c840 chip. It also works with
X the TX9882 chip on the Compex RL100-ATX board.
X More specific information and updates are available from
- http://www.scyld.com/network/drivers.html
+ <http://www.scyld.com/network/drivers.html>.
X
-Zenith Z-Note support (EXPERIMENTAL)
+Zenith Z-Note support
X CONFIG_ZNET
X The Zenith Z-Note notebook computer has a built-in network
X (Ethernet) card, and this is the Linux driver for it. Note that the
X IBM Thinkpad 300 is compatible with the Z-Note and is also supported
X by this driver. Read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.

+
+Philips SAA9730 Ethernet support
+CONFIG_LAN_SAA9730
+ The SAA9730 is a combined multimedia and peripheral controller used
+ in thin clients, Internet access terminals, and diskless
+ workstations.
+ See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
X
X Pocket and portable adapters
X CONFIG_NET_POCKET
X Cute little network (Ethernet) devices which attach to the parallel
X port ("pocket adapters"), commonly used with laptops. If you have
X one of those, say Y and read the Ethernet-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you want to plug a network (or some other) card into the PCMCIA
X (or PC-card) slot of your laptop instead (PCMCIA is the standard for
X credit card size extension cards used by all modern laptops), you
X need the pcmcia-cs package (location contained in the file
- Documentation/Changes) and you can say N here.
+ <file:Documentation/Changes>) and you can say N here.
X
X Laptop users should read the Linux Laptop home page at
- http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
+ <http://www.cs.utexas.edu/users/kharker/linux-laptop/>.

X
X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all

X the questions about this class of network devices. If you say Y, you
X will be asked for your specific device in the following questions.
X
X AT-LAN-TEC/RealTek pocket adapter support
X CONFIG_ATP
X This is a network (Ethernet) device which attaches to your parallel
- port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto , if you
- want to use this. If you intend to use this driver, you should have
+ port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>, if you
+ want to use this. If you intend to use this driver, you should have
X said N to the "Parallel printer support", because the two drivers
X don't like each other.
X
X If you want to compile this driver as a module however ( = code

X which can be inserted in and removed from the running kernel

- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called atp.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called atp.o.
X
X D-Link DE600 pocket adapter support
X CONFIG_DE600
X This is a network (Ethernet) device which attaches to your parallel
- port. Read Documentation/networking/DLINK.txt as well as the
+ port. Read <file:Documentation/networking/DLINK.txt> as well as the
X Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , if you want to use
+ <http://www.linuxdoc.org/docs.html#howto>, if you want to use
X this. It is possible to have several devices share a single parallel
X port and it is safe to compile the corresponding drivers into the
X kernel.
X
X If you want to compile this driver as a module however ( = code

X which can be inserted in and removed from the running kernel

- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
X The module will be called de600.o.
X
X D-Link DE620 pocket adapter support
X CONFIG_DE620
X This is a network (Ethernet) device which attaches to your parallel
- port. Read Documentation/networking/DLINK.txt as well as the
+ port. Read <file:Documentation/networking/DLINK.txt> as well as the
X Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , if you want to use
+ <http://www.linuxdoc.org/docs.html#howto>, if you want to use
X this. It is possible to have several devices share a single parallel
X port and it is safe to compile the corresponding drivers into the
X kernel.
X
X If you want to compile this driver as a module however ( = code

X which can be inserted in and removed from the running kernel

- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
X The module will be called de620.o.
X
X Token Ring driver support
@@ -9975,41 +11165,41 @@
X connected to such a Token Ring network and want to use your Token
X Ring card under Linux, say Y here and to the driver for your
X particular card below and read the Token-Ring mini-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto . Most people can
+ from <http://www.linuxdoc.org/docs.html#howto>. Most people can
X say N here.
X
X IBM Tropic chipset based adapter support
X CONFIG_IBMTR
X This is support for all IBM Token Ring cards that don't use DMA. If
X you have such a beast, say Y and read the Token-Ring mini-HOWTO,

- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X

X Warning: this driver will almost definitely fail if more than one
- active Token Ring card is present.
+ active Token Ring card is present.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called ibmtr.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>.
X

X IBM Olympic chipset PCI adapter support
X CONFIG_IBMOL
- This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
+ This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
X Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
X Wake On Lan, and PCI 100/16/4 adapters.
X
X If you have such an adapter, say Y and read the Token-Ring
X mini-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called olympic.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X
- Also read the file Documentation/networking/olympic.txt or check the
+ Also read <file:Documentation/networking/olympic.txt> or check the
X Linux Token Ring Project site for the latest information at
- http://www.linuxtr.net .
+ <http://www.linuxtr.net>.
X
X IBM Lanstreamer chipset PCI adapter support
X CONFIG_IBMLS
@@ -10017,12 +11207,12 @@
X
X If you have such an adapter, say Y and read the Token-Ring
X mini-HOWTO available via FTP (user:anonymous) from
- ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
+ <ftp://metalab.unc/edu/pub/Linux/docs/HOWTO>.
X
X This driver is also available as a modules ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The modules will be called lanstreamer.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X
X Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
X CONFIG_TMS380TR
@@ -10037,15 +11227,15 @@
X
X If you have such an adapter and would like to use it, say Y and
X read the Token-Ring mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 009'
echo 'File patch-2.4.15 is continued in part 010'
echo "010" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:46 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part010

#!/bin/sh -x
# this is part 010 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 010; then

+ <http://www.linuxdoc.org/docs.html#howto>.
X
- Also read the file Documentation/networking/tms380tr.txt or
- check http://www.auk.cx/tms380tr/ .
+ Also read the file <file:Documentation/networking/tms380tr.txt> or
+ check <http://www.auk.cx/tms380tr/>.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called tms380tr.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X Generic TMS380 PCI support
X CONFIG_TMSPCI
@@ -10060,19 +11250,31 @@
X This driver is available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called tmspci.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.

+
+Generic TMS380 ISA support
+CONFIG_TMSISA
+ This tms380 module supports generic TMS380-based ISA cards.
+
+ These cards are known to work:
+ - SysKonnect TR4/16 ISA (SK-4190)
+
+ This driver is available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called tmsisa.o. If you want to compile it

+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X Madge Smart 16/4 PCI Mk2 support
X CONFIG_ABYSS
- This tms380 module supports the Madge Smart 16/4 PCI Mk2
+ This tms380 module supports the Madge Smart 16/4 PCI Mk2
X cards (51-02).
X
X This driver is available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called abyss.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

-Madge Smart 16/4 Ringode MicroChannel
+Madge Smart 16/4 Ringnode MicroChannel
X CONFIG_MADGEMC
X This tms380 module supports the Madge Smart 16/4 MC16 and MC32
X MicroChannel adapters.
@@ -10080,9 +11282,9 @@
X This driver is available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called madgemc.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

-SMC ISA TokenRing adapter support
+SMC ISA/MCA Token Ring adapter support
X CONFIG_SMCTR
X This is support for the ISA and MCA SMC Token Ring cards,
X specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
@@ -10090,13 +11292,13 @@
X
X If you have such an adapter and would like to use it, say Y or M and

X read the Token-Ring mini-HOWTO, available from

- http://www.linuxdoc.org/docs.html#howto and the file
- Documentation/networking/smctr.txt.
+ <http://www.linuxdoc.org/docs.html#howto> and the file
+ <file:Documentation/networking/smctr.txt>.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called smctr.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X Sun Happy Meal 10/100baseT support
X CONFIG_HAPPYMEAL
@@ -10108,60 +11310,62 @@
X This support is also available as a module called sunhme.o ( = code

X which can be inserted in and removed from the running kernel

X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
X Sun Lance support
X CONFIG_SUNLANCE
X This driver supports the "le" interface present on all 32-bit Sparc
- systems, on some older Ultra systems and as an Sbus option.
+ systems, on some older Ultra systems and as an Sbus option. These
+ cards are based on the AMD Lance chipset, which is better known
+ via the NE2100 cards.
X
X This support is also available as a module called sunlance.o ( =
X code which can be inserted in and removed from the running kernel
X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
-Sun BigMAC 10/100baseT support (EXPERIMENTAL)
+Sun BigMAC 10/100baseT support
X CONFIG_SUNBMAC
X This driver supports the "be" interface available as an Sbus option.
- This is Sun's older 100baseT ethernet device.
+ This is Sun's older 100baseT Ethernet device.
X
X This support is also available as a module called sunbmac.o ( = code

X which can be inserted in and removed from the running kernel

X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
X Sun QuadEthernet support
X CONFIG_SUNQE
- This driver supports the "qe" 10baseT ethernet device, available as
+ This driver supports the "qe" 10baseT Ethernet device, available as
X an Sbus option. Note that this is not the same as Quad FastEthernet
X "qfe" which is supported by the Happy Meal driver instead.
X
X This support is also available as a module called sunqe.o ( = code

X which can be inserted in and removed from the running kernel

X whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
X
-Traffic Shaper (EXPERIMENTAL)
+Traffic Shaper
X CONFIG_SHAPER
X The traffic shaper is a virtual network device that allows you to
X limit the rate of outgoing data flow over some other network device.
X The traffic that you want to slow down can then be routed through
- these virtual devices. See Documentation/networking/shaper.txt for
- more information.
+ these virtual devices. See
+ <file:Documentation/networking/shaper.txt> for more information.
X
X An alternative to this traffic shaper is the experimental
X Class-Based Queueing (CBQ) scheduling support which you get if you
X say Y to "QoS and/or fair queueing" above.
X
X 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
X shaper package.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called shaper.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called shaper.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
X
X FDDI driver support
X CONFIG_FDDI
@@ -10196,8 +11400,8 @@
X - Netelligent 100 FDDI DAS UTP
X - Netelligent 100 FDDI SAS UTP
X - Netelligent 100 FDDI SAS Fibre MIC
-
- Read Documentation/networking/skfp.txt for information about
+
+ Read <file:Documentation/networking/skfp.txt> for information about
X the driver.
X
X Questions concerning this driver can be addressed to:
@@ -10205,10 +11409,10 @@
X

X If you want to compile this driver as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called skfp.o.

+ say M here and read <file:Documentation/modules.txt>. This is

+ recommended. The module will be called skfp.o.
X
-HIgh Performance Parallel Interface support (EXPERIMENTAL)
+HIgh Performance Parallel Interface (HIPPI) support
X CONFIG_HIPPI
X HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
X 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
@@ -10218,16 +11422,16 @@
X and have a HIPPI network card in your computer that you want to use
X under Linux, say Y here (you must also remember to enable the driver
X for your HIPPI card below). Most people will say N here.
-
+
X Essential RoadRunner HIPPI PCI adapter support
X CONFIG_ROADRUNNER
X Say Y here if this is your PCI HIPPI network card.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called rrunner.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called rrunner.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
X
X Use large TX/RX rings
X CONFIG_ROADRUNNER_LARGE_RINGS
@@ -10237,80 +11441,92 @@
X kernel code or by user space programs. Say Y here only if you have
X the memory.
X
-Acorn Ether1 card
+Acorn Ether1 support
X CONFIG_ARM_ETHER1
X If you have an Acorn system with one of these (AKA25) network cards,
X you should say Y to this option if you wish to use it with Linux.
X
-Acorn/ANT Ether3 card
+Acorn/ANT Ether3 support
X CONFIG_ARM_ETHER3
X If you have an Acorn system with one of these network cards, you
X should say Y to this option if you wish to use it with Linux.
X
-I Cubed EtherH card
+I-Cubed EtherH support
X CONFIG_ARM_ETHERH
X If you have an Acorn system with one of these network cards, you
X should say Y to this option if you wish to use it with Linux.
X
-EBSA-110 Ethernet interface
+EBSA-110 Ethernet interface (AM79C961A)
X CONFIG_ARM_AM79C961A
X If you wish to compile a kernel for the EBSA-110, then you should
X always answer Y to this.
X
-Support CDROM drives that are not SCSI or IDE/ATAPI
+Support Thumb instructions
+CONFIG_ARM_THUMB
+ Say Y if you want to have kernel support for ARM Thumb instructions,
+ fault handlers, and system calls.
+
+ The Thumb instruction set is a compressed form of the standard ARM
+ instruction set resulting in smaller binaries at the expense of
+ slightly less efficient code.
+
+ If you don't know what this all is, saying Y is a safe choice.
+
+Support CD-ROM drives that are not SCSI or IDE/ATAPI
X CONFIG_CD_NO_IDESCSI
- If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
- here, otherwise N. Read the CDROM-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
+ here, otherwise N. Read the CD-ROM-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all

- the questions about these CDROM drives. If you are unsure what you

+ kernel: saying N will just cause the configurator to skip all

+ the questions about these CD-ROM drives. If you are unsure what you
X have, say Y and find out whether you have one of the following
- drives.
+ drives.
X
- For each of these drivers, a file Documentation/cdrom/<driver_name>
+ For each of these drivers, a file Documentation/cdrom/{driver_name}
X exists. Especially in cases where you do not know exactly which kind
X of drive you have you should read there. Most of these drivers use a
- file drivers/cdrom/<driver_name>.h where you can define your
- interface parameters and switch some internal goodies.
+ file drivers/cdrom/{driver_name}.h where you can define your
+ interface parameters and switch some internal goodies.
X
- All these CDROM drivers are also usable as a module ( = code which
+ All these CD-ROM drivers are also usable as a module ( = code which
X can be inserted in and removed from the running kernel whenever you
X want). If you want to compile them as module, say M instead of Y and
- read Documentation/modules.txt.
+ read <file:Documentation/modules.txt>.
X
- If you want to use any of these CDROM drivers, you also have to
- answer Y or M to "ISO 9660 CDROM file system support" below (this
+ If you want to use any of these CD-ROM drivers, you also have to
+ answer Y or M to "ISO 9660 CD-ROM file system support" below (this
X answer will get "defaulted" for you if you enable any of the Linux
- CDROM drivers).
+ CD-ROM drivers).
X
-Sony CDU31A/CDU33A CDROM support
+Sony CDU31A/CDU33A CD-ROM support
X CONFIG_CDU31A
- These CDROM drives have a spring-pop-out caddyless drawer, and a
- rectangular green LED centered beneath it. NOTE: these CDROM drives
- will not be auto detected by the kernel at boot time; you have to
- provide the interface address as an option to the kernel at boot
- time as described in Documentation/cdrom/cdu31a or fill in your
- parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
- see the documentation of your boot loader (lilo or loadlin) about
- how to pass options to the kernel.
+ These CD-ROM drives have a spring-pop-out caddyless drawer, and a
+ rectangular green LED centered beneath it. NOTE: these CD-ROM
+ drives will not be auto detected by the kernel at boot time; you
+ have to provide the interface address as an option to the kernel at
+ boot time as described in <file:Documentation/cdrom/cdu31a> or fill
+ in your parameters into <file:drivers/cdrom/cdu31a.c>. Try "man
+ bootparam" or see the documentation of your boot loader (lilo or
+ loadlin) about how to pass options to the kernel.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called cdu31a.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called cdu31a.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
-Standard Mitsumi [no XA/Multisession] CDROM support
+Standard Mitsumi [no XA/Multisession] CD-ROM support
X CONFIG_MCD
X This is the older of the two drivers for the older Mitsumi models
X LU-005, FX-001 and FX-001D. This is not the right driver for the
X FX-001DE and the triple or quad speed models (all these are
- IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
+ IDE/ATAPI models). Please also the file
+ <file:Documentation/cdrom/mcd>.
X
X With the old LU-005 model, the whole drive chassis slides out for cd
X insertion. The FX-xxx models use a motorized tray type mechanism.
@@ -10318,184 +11534,201 @@
X (PhotoCDs). There is a new driver (next question) which can do
X this. If you want that one, say N here.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called mcd.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>.
X

X IRQ channel for Mitsumi CD-ROM
X CONFIG_MCD_IRQ
X This allows you to specify the default value of the IRQ used by the
X driver. This setting can be overridden by passing the "mcd="
X parameter to the kernel at boot time (or at module load time if you
- said M to "Standard Mitsumi CDROM support").
+ said M to "Standard Mitsumi CD-ROM support").
X
X I/O base address for Mitsumi CD-ROM
X CONFIG_MCD_BASE
X This allows you to specify the default value of the I/O base address
X used by the driver. This setting can be overridden by passing the
X "mcd=" parameter to the kernel at boot time (or at module load time
- if you said M to "Standard Mitsumi CDROM support").
+ if you said M to "Standard Mitsumi CD-ROM support").
X
-Mitsumi [XA/MultiSession] support
+Mitsumi [XA/MultiSession] CD-ROM support
X CONFIG_MCDX
X Use this driver if you want to be able to read XA or MultiSession
X CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
- FX-001 or FX-001D CDROM drive. In addition, this driver uses much
+ FX-001 or FX-001D CD-ROM drive. In addition, this driver uses much
X less kernel memory than the old one, if that is a concern. This
X driver is able to support more than one drive, but each drive needs
X a separate interface card. Please read the file
- Documentation/cdrom/mcdx.
+ <file:Documentation/cdrom/mcdx>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called mcdx.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>.
X

-Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
+Matsushita/Panasonic/Creative, Longshine, TEAC CD-ROM support
X CONFIG_SBPCD
X This driver supports most of the drives which use the Panasonic or
- Sound Blaster interface. Please read the file
- Documentation/cdrom/sbpcd.
+ Sound Blaster interface. Please read the file
+ <file:Documentation/cdrom/sbpcd>.
X
X The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
X (sometimes labeled "Creative"), the Creative Labs CD200, the
- Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
- model), the TEAC CD-55A fall under this category. Some other
+ Longshine LCS-7260, the "IBM External ISA CD-ROM" (in fact a CR-56x
+ model), the TEAC CD-55A fall under this category. Some other
X "electrically compatible" drives (Vertos, Genoa, some Funai models)
X are currently not supported; for the Sanyo H94A drive currently a
- separate driver (asked later) is responsible. Most drives have a
+ separate driver (asked later) is responsible. Most drives have a
X uniquely shaped faceplate, with a caddyless motorized drawer, but
- without external brand markings. The older CR-52x drives have a
- caddy and manual loading/eject, but still no external markings. The
+ without external brand markings. The older CR-52x drives have a
+ caddy and manual loading/eject, but still no external markings. The
X driver is able to do an extended auto-probing for interface
X addresses and drive types; this can help to find facts in cases you
X are not sure, but can consume some time during the boot process if
- none of the supported drives gets found. Once your drive got found,
- you should enter the reported parameters into drivers/cdrom/sbpcd.h
- and set "DISTRIBUTION 0" there.
-
- This driver can support up to four CDROM controller cards, and each
- card can support up to four CDROM drives; if you say Y here, you
- will be asked how many controller cards you have. If compiled as a
+ none of the supported drives gets found. Once your drive got found,
+ you should enter the reported parameters into
+ <file:drivers/cdrom/sbpcd.h> and set "DISTRIBUTION 0" there.
+
+ This driver can support up to four CD-ROM controller cards, and each
+ card can support up to four CD-ROM drives; if you say Y here, you
+ will be asked how many controller cards you have. If compiled as a
X module, only one controller card (but with up to four drives) is
X usable.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called sbpcd.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called sbpcd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
-Matsushita/Panasonic, ... second CDROM controller support
+Matsushita/Panasonic, ... second CD-ROM controller support
X CONFIG_SBPCD2
- Say Y here only if you have two CDROM controller cards of this type
- (usually only if you have more than four drives). You should enter
+ 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
X the parameters for the second, third and fourth interface card into
- include/linux/sbpcd.h before compiling the new kernel. Read
- the file Documentation/cdrom/sbpcd.
+ <file:include/linux/sbpcd.h> before compiling the new kernel. Read
+ the file <file:Documentation/cdrom/sbpcd>.
+
+Matsushita/Panasonic, ... third CD-ROM controller support
+CONFIG_SBPCD3
+ Say Y here only if you have three CD-ROM controller cards of this
+ type (usually only if you have more than six 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 the file <file:Documentation/cdrom/sbpcd>.
+
+Matsushita/Panasonic, ... fourth CD-ROM controller support
+CONFIG_SBPCD4
+ Say Y here only if you have four CD-ROM controller cards of this
+ type (usually only if you have more than eight 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 the file <file:Documentation/cdrom/sbpcd>.
X
-Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
+Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CD-ROM support
X CONFIG_AZTCD
X This is your driver if you have an Aztech CDA268-01A, Orchid
- CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
- CR540 CDROM drive. This driver -- just like all these CDROM drivers
- -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
- CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
+ CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCD-ROM CR520 or
+ CR540 CD-ROM drive. This driver -- just like all these CD-ROM
+ drivers -- is NOT for CD-ROM drives with IDE/ATAPI interfaces, such
+ as Aztech CDA269-031SE. Please read the file
+ <file:Documentation/cdrom/aztcd>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called aztcd.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called aztcd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
-Sony CDU535 CDROM support
+Sony CDU535 CD-ROM support
X CONFIG_CDU535
- This is the driver for the older Sony CDU-535 and CDU-531 CDROM
- drives. Please read the file Documentation/cdrom/sonycd535.
+ This is the driver for the older Sony CDU-535 and CDU-531 CD-ROM
+ drives. Please read the file <file:Documentation/cdrom/sonycd535>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called sonycd535.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X
-Goldstar R420 CDROM support
+Goldstar R420 CD-ROM support
X CONFIG_GSCD
- If this is your CDROM drive, say Y here. As described in the file
- Documentation/cdrom/gscd, you might have to change a setting
- in the file drivers/cdrom/gscd.h before compiling the
- kernel. Please read the file Documentation/cdrom/gscd.
+ If this is your CD-ROM drive, say Y here. As described in the file
+ <file:Documentation/cdrom/gscd>, you might have to change a setting
+ in the file <file:drivers/cdrom/gscd.h> before compiling the
+ kernel. Please read the file <file:Documentation/cdrom/gscd>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called gscd.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called gscd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
-Philips/LMS CM206 CDROM support
+Philips/LMS CM206 CD-ROM support
X CONFIG_CM206
- If you have a Philips/LMS CDROM drive cm206 in combination with a
+ If you have a Philips/LMS CD-ROM drive cm206 in combination with a
X cm260 host adapter card, say Y here. Please also read the file
- Documentation/cdrom/cm206.
+ <file:Documentation/cdrom/cm206>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called cm206.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>.
X

-Optics Storage DOLPHIN 8000AT CDROM support
+Optics Storage DOLPHIN 8000AT CD-ROM support
X CONFIG_OPTCD
X This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
X compatible interface. It also works with the Lasermate CR328A. If
X you have one of those, say Y. This driver does not work for the
- Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
- one. Please read the file Documentation/cdrom/optcd.
+ Optics Storage 8001 drive; use the IDE-ATAPI CD-ROM driver for that
+ one. Please read the file <file:Documentation/cdrom/optcd>.
X
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
X file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called optcd.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>.
X

-Sanyo CDR-H94A CDROM support
+Sanyo CDR-H94A CD-ROM support
X CONFIG_SJCD
- If this is your CDROM drive, say Y here and read the file
- Documentation/cdrom/sjcd. You should then also say Y or M to
- "ISO 9660 CDROM file system support" below, because that's the
- file system used on CDROMs.
+ If this is your CD-ROM drive, say Y here and read the file
+ <file:Documentation/cdrom/sjcd>. You should then also say Y or M to
+ "ISO 9660 CD-ROM file system support" below, because that's the
+ file system used on CD-ROMs.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called sjcd.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>.
X

X ISP16/MAD16/Mozart soft configurable cdrom interface support
X CONFIG_ISP16_CDI
@@ -10503,12 +11736,17 @@
X 82C928 or 82C929 chips. Say Y here to have them detected and
X possibly configured at boot time. In addition, You'll have to say Y
X to a driver for the particular cdrom drive you have attached to the
- card. Read Documentation/cdrom/isp16 for details.
+ card. Read <file:Documentation/cdrom/isp16> for details.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called isp16.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>.

+
+iSeries Virtual I/O CD Support
+CONFIG_VIOCD
+ If you are running Linux on an IBM iSeries system and you want to
+ read a CD drive owned by OS/400, say Y here.
X
X Quota support
X CONFIG_QUOTA
@@ -10516,13 +11754,13 @@
X usage (also called disk quotas). Currently, it works only for the
X ext2 file system. You need additional software in order to use quota
X support; for details, read the Quota mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Probably the quota
+ <http://www.linuxdoc.org/docs.html#howto>. Probably the quota
X support is only useful for multi user systems. If unsure, say N.
X
X Memory Technology Device (MTD) support
X CONFIG_MTD
X Memory Technology Devices are flash, RAM and similar chips, often
- used for solid state filesystems on embedded devices. This option
+ used for solid state file systems on embedded devices. This option
X will provide the generic support for MTD drivers to register
X themselves with the kernel and for potential users of MTD devices
X to enumerate the devices which are present and obtain a handle on
@@ -10548,18 +11786,17 @@
X RedBoot partition table parsing
X CONFIG_MTD_REDBOOT_PARTS
X RedBoot is a ROM monitor and bootloader which deals with multiple
- 'images' in flash devices by putting a table in the last erase
- block of the device, similar to a partition table, which gives
- the offsets, lengths and names of all the images stored in the
- flash.
+ 'images' in flash devices by putting a table in the last erase block
+ of the device, similar to a partition table, which gives the
+ offsets, lengths and names of all the images stored in the flash.
X
X If you need code which can detect and parse this table, and register
X MTD 'partitions' corresponding to each image in the table, enable
- this option.
+ this option.
X
X You will still need the parsing functions to be called by the driver
- for your particular device. It won't happen automatically. The
- SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
+ for your particular device. It won't happen automatically. The
+ SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
X example.
X
X Compaq bootldr partition table parsing
@@ -10567,11 +11804,11 @@
X The Compaq bootldr deals with multiple 'images' in flash devices
X by putting a table in one of the first erase blocks of the device,
X similar to a partition table, which gives the offsets, lengths and
- names of all the images stored in the flash.
+ names of all the images stored in the flash.
X
X If you need code which can detect and parse this table, and register
X MTD 'partitions' corresponding to each image in the table, enable
- this option.
+ this option.
X
X You will still need the parsing functions to be called by the driver
X for your particular device. It won't happen automatically. The
@@ -10582,21 +11819,20 @@
X CONFIG_MTD_AFS_PARTS
X The ARM Firmware Suite allows the user to divide flash devices into
X multiple 'images'. Each such image has a header containing its name
- and offset/size etc.
+ and offset/size etc.
X
- If you need code which can detect and parse these tables, and register
- MTD 'partitions' corresponding to each image detected, enable
- this option.
+ If you need code which can detect and parse these tables, and
+ register MTD 'partitions' corresponding to each image detected,
+ enable this option.
X
X You will still need the parsing functions to be called by the driver
- for your particular device. It won't happen automatically. The
+ for your particular device. It won't happen automatically. The
X 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
X
-MTD debugging verbosity
+MTD debugging verbosity (0 = quiet, 3 = noisy)
X CONFIG_MTD_DEBUG_VERBOSE
X Determines the verbosity level of the MTD debugging messages.
X
-
X Direct chardevice access to MTD devices
X CONFIG_MTD_CHAR
X This provides a character device for each MTD device present in
@@ -10608,8 +11844,8 @@
X CONFIG_MTD_BLOCK
X Although most flash chips have an erase size too large to be useful
X as block devices, it is possible to use MTD devices which are based
- on RAM chips in this manner. This block device is a user of MTD devices
- performing that function.
+ on RAM chips in this manner. This block device is a user of MTD
+ devices performing that function.
X
X At the moment, it is also required for the Journalling Flash File
X System(s) to obtain a handle on the MTD device when it's mounted
@@ -10618,7 +11854,7 @@
X
X Later, it may be extended to perform read/erase/modify/write cycles
X on flash chips to emulate a smaller block size. Needless to say,
- this is very unsafe, but could be useful for filesystems which are
+ this is very unsafe, but could be useful for file systems which are
X almost never written to.
X
X You do not need this option for use with the DiskOnChip devices. For
@@ -10626,9 +11862,9 @@
X
X Readonly block device access to MTD devices
X CONFIG_MTD_BLOCK_RO
- This allows you to mount read-only filesystems (such as cramfs) from
- an MTD device, without the overhead (and danger) of the caching
- driver.
+ This allows you to mount read-only file systems (such as cramfs)
+ from an MTD device, without the overhead (and danger) of the caching
+ driver.
X
X You do not need this option for use with the DiskOnChip devices. For
X those, enable NFTL support (CONFIG_NFTL) instead.
@@ -10637,8 +11873,8 @@
X CONFIG_FTL
X This provides support for the original Flash Translation Layer which
X is part of the PCMCIA specification. It uses a kind of pseudo-
- filesystem on a flash device to emulate a block device with 512-byte
- sectors, on top of which you put a 'normal' filesystem.
+ file system on a flash device to emulate a block device with
+ 512-byte sectors, on top of which you put a 'normal' file system.
X
X You may find that the algorithms used in this code are patented
X unless you live in the Free World where software patents aren't
@@ -10651,8 +11887,8 @@
X CONFIG_NFTL
X This provides support for the NAND Flash Translation Layer which is
X used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
- filesystem on a flash device to emulate a block device with 512-byte
- sectors, on top of which you put a 'normal' filesystem.
+ file system on a flash device to emulate a block device with
+ 512-byte sectors, on top of which you put a 'normal' file system.
X
X You may find that the algorithms used in this code are patented
X unless you live in the Free World where software patents aren't
@@ -10663,9 +11899,10 @@
X
X Write support for NFTL (EXPERIMENTAL)
X CONFIG_NFTL_RW
- If you're lucky, this will actually work. Don't whinge if it doesn't.
- Send mail to the MTD mailing list <linu...@lists.infradead.org> if
- you want to help to make it more reliable.
+ If you're lucky, this will actually work. Don't whinge if it
+ doesn't. Send mail to the MTD mailing list
+ <linu...@lists.infradead.org> if you want to help to make it more
+ reliable.
X
X Common Flash Interface (CFI) support
X CONFIG_MTD_CFI
@@ -10673,7 +11910,7 @@
X AMD and other flash manufactures that provides a universal method
X for probing the capabilities of flash devices. If you wish to
X support any device that is CFI-compliant, you need to enable this
- option. Visit (http://www.amd.com/products/nvd/overview/cfi.html)
+ option. Visit <http://www.amd.com/products/nvd/overview/cfi.html>
X for more information on CFI.
X
X CFI Advanced configuration options
@@ -10724,6 +11961,7 @@
X If your flash chips are interleaved in fours - i.e. you have four
X flash chips addressed by each bus cycle, then say 'Y'.
X
+# Choice: mtd_swap_data
X Flash cmd/query data swapping
X CONFIG_MTD_CFI_NOSWAP
X This option defines the way in which the CPU attempts to arrange
@@ -10732,7 +11970,7 @@
X enabled, means that the CPU will not do any swapping; the chips
X are expected to be wired to the CPU in 'host-endian' form.
X Specific arrangements are possible with the BIG_ENDIAN_BYTE and
- LITTLE_ENDIAN_BYTE, if the bytes are reversed.
+ LITTLE_ENDIAN_BYTE, if the bytes are reversed.
X
X If you have a LART, on which the data (and address) lines were
X connected in a fashion which ensured that the nets were as short
@@ -10741,14 +11979,14 @@
X
X Yes, there really exists something sicker than PDP-endian :)
X
-CFI support for Intel/Sharp Extended Commands
+CFI support for Intel/Sharp Extended Command Set chips
X CONFIG_MTD_CFI_INTELEXT
X The Common Flash Interface defines a number of different command
X sets which a CFI-compliant chip may claim to implement. This code
X provides support for one of those command sets, used on Intel
X StrataFlash and other parts.
X
-CFI support for AMD/Fujitsu Standard Commands
+CFI support for AMD/Fujitsu Standard Command Set chips
X CONFIG_MTD_CFI_AMDSTD
X The Common Flash Interface defines a number of different command
X sets which a CFI-compliant chip may claim to implement. This code
@@ -10785,26 +12023,36 @@
X This option enables basic support for ROM chips accessed through
X a bus mapping driver.
X
+JEDEC device support
X CONFIG_MTD_JEDEC
- Enable older older JEDEC flash interface devices for self programming
- flash. It is commonly used in older AMD chips. It is only called
- JEDEC because the JEDEC association (http://www.jedec.org/)
- distributes the identification codes for the chips. WARNING!!!! This
- code does not compile and is incomplete as are the specific JEDEC
- devices drivers.
+ Enable older older JEDEC flash interface devices for self
+ programming flash. It is commonly used in older AMD chips. It is
+ only called JEDEC because the JEDEC association
+ <http://www.jedec.org/> distributes the identification codes for the
+ chips. WARNING!!!! This code does not compile and is incomplete as
+ are the specific JEDEC devices drivers.
X
X CFI Flash device mapped on StrongARM SA11x0
X CONFIG_MTD_SA1100
- This enables access to the flash chips on most platforms based on the
- SA1100 and SA1110, including the Assabet and the Compaq iPAQ. If you
- have such a board, say 'Y'.
+ This enables access to the flash chips on most platforms based on
+ the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
+ If you have such a board, say 'Y'.
X
+Support for Compaq bootldr partition tables on SA11x0
X CONFIG_MTD_SA1100_REDBOOT_PARTITIONS
X Enabling this option will cause the kernel to look for a RedBoot
X FIS (Flash Image System) table in the last erase block of the flash
X chips detected. If you are using RedBoot on your SA11x0-based board
X and want Linux to present 'partitions' matching the images which
- RedBoot has listed, say 'Y'.
+ RedBoot has listed, say 'Y'.
+
+Support for Compaq bootldr partition tables on SA11x0
+CONFIG_MTD_SA1100_BOOTLDR_PARTITIONS
+ Enabling this option will cause the kernel to look for a Compaq
+ bootldr partition table on the flash chips detected. If you are
+ using the Compaq bootldr on your SA11x0-based board and want Linux
+ to present 'partitions' matching the images which the bootldr has
+ listed, say 'Y'.
X
X Flash chip mapping in physical memory
X CONFIG_MTD_PHYSMAP
@@ -10830,6 +12078,7 @@
X map which should hopefully be in the documentation for your
X board.
X
+Buswidth of flash in bytes
X CONFIG_MTD_PHYSMAP_BUSWIDTH
X This is the total width of the data bus of the flash devices
X in octets. For example, if you have a data bus width of 32
@@ -10847,7 +12096,7 @@
X CONFIG_MTD_NORA
X If you had to ask, you don't have one. Say 'N'.
X
-Flash chip mapping on PNC2000
+Flash chip mapping on Photron PNC-2000
X CONFIG_MTD_PNC2000
X PNC-2000 is the name of Network Camera product from PHOTRON
X Ltd. in Japan. It uses CFI-compliant flash.
@@ -10858,7 +12107,7 @@
X a strange sparse mapping. This 'mapping' driver supports that
X arrangement, allowing the CFI probe and command set driver code
X to communicate with the chips on the RPXLite board. More at
- (http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm).
+ <http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm>.
X
X Flash chip mapping on AMD SC520 CDP board
X CONFIG_MTD_SC520CDP
@@ -10866,47 +12115,67 @@
X Dual-in-line JEDEC chip. This 'mapping' driver supports that
X arrangement, implementing three MTD devices.
X
-Flash chip mapping on Arcom Control Systems' SBC-MediaGX
-CONFIG_MTD_SBC_MEDIAGX
+Flash chip mapping on Arcom Control Systems SBC-MediaGX
+CONFIG_MTD_SBC_GXX
X This provides a driver for the on-board flash of Arcom Control
- Systems' SBC-MediaGX development board. By default the flash
- is split into 3 partitions which are accessed as separate MTD
- devices. This board utilizes Intel StrataFlash. More info at
- (http://www.arcomcontrols.com/products/icp/pc104/processors/).
+ Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
+ By default the flash is split into 3 partitions which are accessed
+ as separate MTD devices. This board utilizes Intel StrataFlash.
+ More info at
+ <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
+
+CFI Flash device mapped on D-Box2
+CONFIG_MTD_DBOX2
+ This enables access routines for the flash chips on the Nokia/Sagem
+ D-Box 2 board. If you have one of these boards and would like to use
+ the flash chips on it, say 'Y'.
+
+CFI Flash device mapped on the XScale IQ80310 board
+CONFIG_MTD_IQ80310
+ This enables access routines for the flash chips on the Intel XScale
+ IQ80310 evaluation board. If you have one of these boards and would
+ like to use the flash chips on it, say 'Y'.
+
+CFI Flash device mapped on AMD NetSc520
+CONFIG_MTD_NETSC520
+ This enables access routines for the flash chips on the AMD NetSc520
+ demonstration board. If you have one of these boards and would like
+ to use the flash chips on it, say 'Y'.
X
-Flash chip mapping on Arcom Control Systems' ELAN-104NC
+Flash chip mapping on Arcom Control Systems ELAN-104NC
X CONFIG_MTD_ELAN_104NC
X This provides a driver for the on-board flash of the Arcom Control
X System's ELAN-104NC development board. By default the flash
X is split into 3 partitions which are accessed as separate MTD
X devices. This board utilizes Intel StrataFlash. More info at
- (http://www.arcomcontrols.com/products/icp/pc104/processors/).
+ <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
X
X Flash chip mapping on Compaq iPAQ/Bitsy
X CONFIG_MTD_BITSY
X This provides a driver for the on-board flash found in Compaq's
X iPAQ Palm PC and their research prototype the Itsy. iPAQ info at
- (http://www5.compaq.com/products/handhelds/pocketpc/) and the
- Itsy (http://www.research.digital.com/wrl/projects/Itsy/index.html).
+ <http://www5.compaq.com/products/handhelds/pocketpc/> and the
+ Itsy <http://www.research.digital.com/wrl/projects/Itsy/index.html>.
X
X Flash chip mapping on Compaq iPAQ/Bitsy
X CONFIG_MTD_DC21285
X This provides a driver for the flash accessed using Intel's
X 21285 bridge used with Intel's StrongARM processors. More info at
- (http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm).
+ <http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm>.
X
X Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board
X CONFIG_MTD_CSTM_MIPS_IXX
- This provides a mapping driver for the Integrated Tecnology
- Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference
- Board. It provides the necessary addressing, length, buswidth, vpp code
- and addition setup of the flash device for these boards. In addition,
- this mapping driver can be used for other boards via setting of the
- CONFIG_MTD_CSTM_MIPS_IXX_START/LEN/BUSWIDTH parameters. This mapping
- will provide one mtd device using one partition. The start address can
- be offset from the beginning of flash and the len can be less than the
- total flash device size to allow a window into the flash. Both CFI and
- JEDEC probes are called.
+ This provides a mapping driver for the Integrated Tecnology Express,
+ Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference
+ Board. It provides the necessary addressing, length, buswidth, vpp
+ code and addition setup of the flash device for these boards. In
+ addition, this mapping driver can be used for other boards via
+ setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/LEN/BUSWIDTH
+ parameters. This mapping will provide one mtd device using one
+ partition. The start address can be offset from the beginning of
+ flash and the len can be less than the total flash device size to
+ allow a window into the flash. Both CFI and JEDEC probes are
+ called.
X
X Physical start location of flash mapping
X CONFIG_MTD_CSTM_MIPS_IXX_START
@@ -10920,7 +12189,7 @@
X This is the total length that the MTD driver will use for the
X flash chips on your particular board. Refer to the memory
X map which should hopefully be in the documentation for your
- board.
+ board.
X
X Physical bus width of flash mapping
X CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH
@@ -10934,26 +12203,26 @@
X to get on with their job of driving the flash chips without
X having to know about the paging. If you have one of these boards,
X you probably want to enable this mapping driver. More info is at
- (http://www.itc.hu/).
+ <http://www.itc.hu/>.
X
X Flash chip mapping on Octagon 5066 SBC
X CONFIG_MTD_OCTAGON
X This provides a 'mapping' driver which supports the way in which
X the flash chips are connected in the Octagon-5066 Single Board
X Computer. More information on the board is available at
- (http://www.octagonsystems.com/Products/5066/5066.html).
+ <http://www.octagonsystems.com/Products/5066/5066.html>.
X
X Flash chip mapping on Tempustech VMAX SBC301
X CONFIG_MTD_VMAX
X This provides a 'mapping' driver which supports the way in which
X the flash chips are connected in the Tempustech VMAX SBC301 Single
X Board Computer. More information on the board is available at
- (http://www.tempustech.com/tt301.htm).
+ <http://www.tempustech.com/tt301.htm>.
X
X Support for NAND flash devices
X CONFIG_MTD_NAND
X This enables support for accessing all type of NAND flash
- devices.
+ devices.
X
X Support for software ECC algorithm
X CONFIG_MTD_NAND_ECC
@@ -10983,96 +12252,102 @@
X M-Systems Disk-On-Chip 2000 and Millennium support
X CONFIG_MTD_DOC2000
X This provides an MTD device driver for the M-Systems DiskOnChip
- 2000 and Millennium devices. Originally designed for the DiskOnChip
- 2000, it also now includes support for the DiskOnChip Millennium.
+ 2000 and Millennium devices. Originally designed for the DiskOnChip
+ 2000, it also now includes support for the DiskOnChip Millennium.
X If you have problems with this driver and the DiskOnChip Millennium,
X you may wish to try the alternative Millennium driver below. To use
X the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
- in the drivers/mtd/devices/docprobe.c source code.
+ in the <file:drivers/mtd/devices/docprobe.c> source code.
X
X If you use this device, you probably also want to enable the NFTL
- 'NAND Flash Translation Layer' option below, which is used to emulate
- a block device by using a kind of filesystem on the flash chips.
+ 'NAND Flash Translation Layer' option below, which is used to
+ emulate a block device by using a kind of file system on the flash
+ chips.
X
X Alternative Disk-On-Chip Millennium support
X CONFIG_MTD_DOC2001
X This provides an alternative MTD device driver for the M-Systems
- DiskOnChip Millennium devices. Use this if you have problems with
- the combined DiskOnChip 2000 and Millennium driver above. To get
+ DiskOnChip Millennium devices. Use this if you have problems with
+ the combined DiskOnChip 2000 and Millennium driver above. To get
X the DiskOnChip probe code to load and use this driver instead of
X the other one, you will need to undefine DOC_SINGLE_DRIVER near
- the beginning of drivers/mtd/devices/docprobe.c
+ the beginning of <file:drivers/mtd/devices/docprobe.c>.
X
X If you use this device, you probably also want to enable the NFTL
- 'NAND Flash Translation Layer' option below, which is used to emulate
- a block device by using a kind of filesystem on the flash chips.
+ 'NAND Flash Translation Layer' option below, which is used to
+ emulate a block device by using a kind of file system on the flash
+ chips.
X
X Probe for DiskOnChip devices
X CONFIG_MTD_DOCPROBE
- This isn't a real config option, it's derived.
+ This isn't a real config option, it's derived.
X
X Advanced detection options for DiskOnChip
X CONFIG_MTD_DOCPROBE_ADVANCED
X This option allows you to specify nonstandard address at which to
- probe for a DiskOnChip, or to change the detection options. You're
- unlikely to need any of this unless you're using LinuxBIOS. Say 'N'.
+ probe for a DiskOnChip, or to change the detection options. You
+ are unlikely to need any of this unless you are using LinuxBIOS.
+ Say 'N'.
X
-Probe for 0x55 0xAA BIOS Extension Signature.
+Probe for 0x55 0xAA BIOS Extension Signature
X CONFIG_MTD_DOCPROBE_55AA
- Check for the 0x55 0xAA signature of a DiskOnChip, and do not continue
- with probing if it is absent. The signature will always be present for
- a DiskOnChip 2000 or a normal DiskOnChip Millennium. Only if you have
- overwritten the first block of a DiskOnChip Millennium will it be
- absent. Enable this option if you are using LinuxBIOS or if you need
- to recover a DiskOnChip Millennium on which you have managed to wipe
- the first block.
+ Check for the 0x55 0xAA signature of a DiskOnChip, and do not
+ continue with probing if it is absent. The signature will always be
+ present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
+ Only if you have overwritten the first block of a DiskOnChip
+ Millennium will it be absent. Enable this option if you are using
+ LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
+ you have managed to wipe the first block.
X
X Physical address of DiskOnChip
X CONFIG_MTD_DOCPROBE_ADDRESS
- By default, the probe for DiskOnChip devices will look for a DiskOnChip
- at every multiple of 0x2000 between 0xC8000 and 0xEE000. This option
- allows you to specify a single address at which to probe for the device,
- which is useful if you have other devices in that range which get upset
- when they're probed.
+ By default, the probe for DiskOnChip devices will look for a
+ DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
+ This option allows you to specify a single address at which to probe
+ for the device, which is useful if you have other devices in that
+ range which get upset when they are probed.
X
- (Note that on PowerPC, the normal probe will only check at 0xE4000000.)
+ (Note that on PowerPC, the normal probe will only check at
+ 0xE4000000.)
X
- Normally, you should leave this set to zero, to allow the probe at the
- normal addresses.
+ Normally, you should leave this set to zero, to allow the probe at
+ the normal addresses.
X
X Probe high addresses
X CONFIG_MTD_DOCPROBE_HIGH
- By default, the probe for DiskOnChip devices will look for a DiskOnChip
- at every multiple of 0x2000 between 0xC8000 and 0xEE000. This option
- changes to make it probe between 0xFFFC8000 and 0xFFFEE000. Unless
- you're using LinuxBIOS, this is unlikely to be useful to you. Say 'N'.
+ By default, the probe for DiskOnChip devices will look for a
+ DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
+ This option changes to make it probe between 0xFFFC8000 and
+ 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
+ useful to you. Say 'N'.
X
X Ramix PMC551 PCI Mezzanine ram card support
X CONFIG_MTD_PMC551
X This provides a MTD device driver for the Ramix PMC551 RAM PCI card
- from Ramix Inc. (http://www.ramix.com/products/memory/pmc551.html).
+ from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
X These devices come in memory configurations from 32M - 1G. If you
X have one, you probably want to enable this.
X
- If this driver is compiled as a module you get the ability to select the
- size of the aperture window pointing into the devices memory. What this
- means is that if you have a 1G card, normally the kernel will use a 1G
- memory map as it's view of the device. As a module, you can select a
- 1M window into the memory and the driver will "slide" the window around
- the PMC551's memory. This was particularly useful on the 2.2 kernels
- on PPC architectures as there was limited kernel space to deal with.
+ If this driver is compiled as a module you get the ability to select
+ the size of the aperture window pointing into the devices memory.
+ What this means is that if you have a 1G card, normally the kernel
+ will use a 1G memory map as its view of the device. As a module,
+ you can select a 1M window into the memory and the driver will
+ "slide" the window around the PMC551's memory. This was
+ particularly useful on the 2.2 kernels on PPC architectures as there
+ was limited kernel space to deal with.
X
X PMC551 256M DRAM Bugfix
X CONFIG_MTD_PMC551_BUGFIX
- Some of Ramix's PMC551 boards with 256M configurations have invalid column
- and row mux values. This option will fix them, but will break other memory
- configurations. If unsure say N.
+ Some of Ramix's PMC551 boards with 256M configurations have invalid
+ column and row mux values. This option will fix them, but will
+ break other memory configurations. If unsure say N.
X
X PMC551 Debugging
X CONFIG_MTD_PMC551_DEBUG
- This option makes the PMC551 more verbose during it's operation and is only
- really usefull if you are developing on this driver or suspect a possible
- hardware or driver bug. If unsure say N.
+ This option makes the PMC551 more verbose during its operation and
+ is only really useful if you are developing on this driver or
+ suspect a possible hardware or driver bug. If unsure say N.
X
X Use extra onboard system memory as MTD device
X CONFIG_MTD_SLRAM
@@ -11083,24 +12358,24 @@
X Debugging RAM test driver
X CONFIG_MTD_MTDRAM
X This enables a test MTD device driver which uses vmalloc() to
- provide storage. You probably want to say 'N' unless you're
+ provide storage. You probably want to say 'N' unless you're
X testing stuff.
X
-MTDRAM erase block size in KiB
+MTDRAM erase block size in KB
X CONFIG_MTDRAM_ERASE_SIZE
X This allows you to configure the size of the erase blocks in the
- device emulated by the MTDRAM driver. If the MTDRAM driver is built
+ device emulated by the MTDRAM driver. If the MTDRAM driver is built
X as a module, it is also possible to specify this as a parameter when
X loading the module.
X
-MTDRAM device size in KiB
+MTDRAM device size in KB
X CONFIG_MTDRAM_TOTAL_SIZE
X This allows you to configure the total size of the MTD device
- emulated by the MTDRAM driver. If the MTDRAM driver is built
+ emulated by the MTDRAM driver. If the MTDRAM driver is built
X as a module, it is also possible to specify this as a parameter when
X loading the module.
X
-SRAM absolute position
+SRAM Hexadecimal Absolute position or 0
X CONFIG_MTDRAM_ABS_POS
X If you have system RAM accessible by the CPU but not used by Linux
X in normal operation, you can give the physical address at which the
@@ -11110,34 +12385,40 @@
X
X Flash chip mapping on the Flaga Digital Module
X CONFIG_MTD_CFI_FLAGADM
- Mapping for the Flaga digital module. If you don´t have one, ignore this
- setting.
+ Mapping for the Flaga digital module. If you don´t have one, ignore
+ this setting.
+
+Momenco Ocelot boot flash device
+CONFIG_MTD_OCELOT
+ This enables access routines for the boot flash device and for the
+ NVRAM on the Momenco Ocelot board. If you have one of these boards
+ and would like access to either of these, say 'Y'.
X
-Support for USB
+USB (Universal Serial Bus) support
X CONFIG_USB
X Universal Serial Bus (USB) is a specification for a serial bus
X subsystem which offers higher speeds and more features than the
- traditional PC serial port. The bus supplies power to peripherals
- and allows for hot swapping. Up to 127 USB peripherals can be

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 010'
echo 'File patch-2.4.15 is continued in part 011'
echo "011" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:47 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part011

#!/bin/sh -x
# this is part 011 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 011; then

- connected to a single USB port in a tree structure. The USB port is
+ traditional PC serial port. The bus supplies power to peripherals
+ and allows for hot swapping. Up to 127 USB peripherals can be
+ connected to a single USB port in a tree structure. The USB port is
X the root of the tree, the peripherals are the leaves and the inner
- nodes are special USB devices called hubs. Many newer PC's have USB
+ nodes are special USB devices called hubs. Many newer PC's have USB
X ports and newer peripherals such as scanners, keyboards, mice,
X modems, and printers support the USB protocol and can be connected
X to the PC via those ports.
X
X Say Y here if your computer has a USB port and you want to use USB
- devices. You then need to say Y to at least one of "UHCI support" or
- "OHCI support" below (the type of interface that the USB hardware in
- your computer provides to the operating system) and then choose from
- among the drivers for USB peripherals. You may want to check out the
- information provided in Documentation/usb/ and especially the links
- given in Documentation/usb/usb-help.txt.
+ devices. You then need to say Y to at least one of "UHCI support"
+ or "OHCI support" below (the type of interface that the USB hardware
+ in your computer provides to the operating system) and then choose
+ from among the drivers for USB peripherals. You may want to check
+ out the information provided in <file:Documentation/usb/> and
+ especially the links given in <file:Documentation/usb/usb-help.txt>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called usbcore.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called usbcore.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X USB verbose debug messages
X CONFIG_USB_DEBUG
@@ -11160,14 +12441,14 @@
X USB long timeout
X CONFIG_USB_LONG_TIMEOUT
X This option makes the standard time out a bit longer. Basically,
- some devices are just slow to respond, so this makes usb more
+ some devices are just slow to respond, so this makes usb more
X patient. There should be no harm in selecting this, but it is
X needed for some MGE Ellipse UPSes.
X
X If you have an MGE Ellipse UPS, or you see timeouts in HID
X transactions, say Y; otherwise say N.
X
-UHCI (intel PIIX4, VIA, ...) support
+UHCI (Intel PIIX4, VIA, ...) support
X CONFIG_USB_UHCI
X The Universal Host Controller Interface is a standard by Intel for
X accessing the USB hardware in the PC (which is also called the USB
@@ -11179,15 +12460,15 @@
X 133).
X
X Currently there exist two drivers for UHCI host controllers: this
- one and the so-called JE driver, which you can get from
+ one and the so-called JE driver, which you can get from
X "UHCI alternate (JE) support", below. You need only one.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called usb-uhci.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>.
X

-UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
+UHCI (Intel PIIX4, VIA, ...) alternate (JE) support
X CONFIG_USB_UHCI_ALT
X The Universal Host Controller Interface is a standard by Intel for
X accessing the USB hardware in the PC (which is also called the USB
@@ -11205,11 +12486,7 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called uhci.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

-
-UHCI unlink optimizations (EXPERIMENTAL)
-CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
- This option currently does nothing. You may say Y or N.

+ module, say M here and read <file:Documentation/modules.txt>.
X

X OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
X CONFIG_USB_OHCI
@@ -11221,12 +12498,12 @@
X -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
X Aladdin Pro..) -- conform to this standard.
X
- You may want to read the file Documentation/usb/ohci.txt.
+ You may want to read <file:Documentation/usb/ohci.txt>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called usb-ohci.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Human Interface Device (full HID) support
X CONFIG_USB_HID
@@ -11234,22 +12511,20 @@
X mice, joysticks, graphic tablets, or any other HID based devices
X to your computer via USB. You can't use this driver and the
X HIDBP (Boot Protocol) keyboard and mouse drivers at the same time.
- More information is available: Documentation/input/input.txt.
+ More information is available: <file:Documentation/input/input.txt>.

X
X If unsure, say Y.
X

X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called hid.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>.
X

X /dev/usb/hiddev raw HID device support
X CONFIG_USB_HIDDEV
X Say Y here if you want to support HID devices (from the USB
X specification standpoint) that aren't strictly user interface
X devices, like monitor controls and Uninterruptable Power Supplies.
- It is also used for "consumer keys" on multimedia keyboards and
- USB speakers.
X
X This module supports these devices separately using a separate
X event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
@@ -11266,7 +12541,7 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called usbkbd.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>.
X

X If unsure, say N.
X
@@ -11279,41 +12554,41 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called usbmouse.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X If unsure, say N.
X
X Wacom Intuos/Graphire tablet support
X CONFIG_USB_WACOM
X Say Y here if you want to use the USB version of the Wacom Intuos
- or Graphire tablet. Make sure to say Y to "Mouse support"
+ or Graphire tablet. Make sure to say Y to "Mouse support"
X (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
X (CONFIG_INPUT_EVDEV) as well.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called wacom.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called wacom.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

-Logitech WingMan Force joystick support
-CONFIG_USB_WMFORCE
- Say Y here if you want to use the Logitech WingMan Force with Linux
- on the USB port. No force-feedback support yet, but other than that
- it should work like a normal joystick.
+Aiptek 8000U tablet support
+CONFIG_USB_AIPTEK
+ Say Y here if you want to use the USB version of the Aiptek 8000U
+ tablet. Make sure to say Y to "Event interface support"
+ (CONFIG_INPUT_EVDEV) as well.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called wmforce.o. If you want to compile it as a
+ The module will be called aiptek.o. If you want to compile it as a
X module, say M here and read Documentation/modules.txt.
X
X Use input layer for ADB devices
X CONFIG_INPUT_ADBHID
X Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
- such as keyboards, mice, joysticks, or graphic tablets handled by the
- input layer. If you say Y here, make sure to say Y to the
+ such as keyboards, mice, joysticks, or graphic tablets handled by
+ the input layer. If you say Y here, make sure to say Y to the
X corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
- "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface support"
- (CONFIG_INPUT_EVDEV) as well.
+ "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
+ support" (CONFIG_INPUT_EVDEV) as well.
X
X If you say N here, you still have the option of using the old ADB
X keyboard and mouse drivers.
@@ -11333,12 +12608,13 @@
X Keyboard support
X CONFIG_INPUT_KEYBDEV
X Say Y here if you want your USB HID keyboard (or an ADB keyboard
- handled by the input layer) to be able to serve as a system keyboard.
+ handled by the input layer) to be able to serve as a system
+ keyboard.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

- The module will be called keybdev.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called keybdev.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X Mouse support
X CONFIG_INPUT_MOUSEDEV
@@ -11347,13 +12623,13 @@
X /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
X mouse. That way, all user space programs will be able to use your
X mouse.
-
+

X If unsure, say Y.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called mousedev.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X Horizontal screen resolution
X CONFIG_INPUT_MOUSEDEV_SCREEN_X
@@ -11372,71 +12648,81 @@
X Joystick support
X CONFIG_INPUT_JOYDEV
X Say Y here if you want your USB HID joystick or gamepad to be
- accessible as char device 13:0+ - /dev/input/jsX device.
+ accessible as char device 13:0+ - /dev/input/jsX device.

X
X This driver is also available as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want).

X The module will be called joydev.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>.
X

X Event interface support
X CONFIG_INPUT_EVDEV
- Say Y here if you want your USB or ADB HID device events be accessible
- under char device 13:64+ - /dev/input/eventX in a generic way.
- This is the future ...
+ Say Y here if you want your USB or ADB HID device events be
+ accessible under char device 13:64+ - /dev/input/eventX in a generic
+ way. This is the future ...
X
X USB Scanner support
X CONFIG_USB_SCANNER
X Say Y here if you want to connect a USB scanner to your computer's
- USB port. Please read Documentation/usb/scanner.txt and
- Documentation/usb/scanner-hp-sane.txt for more information.
+ USB port. Please read <file:Documentation/usb/scanner.txt> and
+ <file:Documentation/usb/scanner-hp-sane.txt> for more information.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called scanner.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.

+
+HP 5300C scanner support
+CONFIG_USB_HP5300
+ Say Y here if you want to connect a HP5300C scanner to your
+ computer's USB port.
+
+ This code is also available as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want).

+ The module will be called hp5300.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Audio support
X CONFIG_USB_AUDIO
- Say Y here if you want to connect UAB audio equipment such as
+ Say Y here if you want to connect USB audio equipment such as
X speakers to your computer's USB port.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called audio.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>.
X

X USB Modem (CDC ACM) support
X CONFIG_USB_ACM
X This driver supports USB modems and ISDN adapters which support the
X Communication Device Class Abstract Control Model interface.
- Please read Documentation/usb/acm.txt for details.
+ Please read <file:Documentation/usb/acm.txt> for details.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called acm.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>.
X

-USB Serial converter support
+USB serial converter support
X CONFIG_USB_SERIAL
X Say Y here if you have a USB device that provides normal serial
X ports, or acts like a serial device, and you want to connect it to
X your USB bus.
X
- Please read Documentation/usb/usb-serial.txt for more information
- on the specifics of the different devices that are supported, and
- on how to use them.
-
+ Please read <file:Documentation/usb/usb-serial.txt> for more
+ information on the specifics of the different devices that are
+ supported, and on how to use them.
+
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called usbserial.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.

+ The module will be called usbserial.o. If you want to compile it

+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Generic Serial Driver
X CONFIG_USB_SERIAL_GENERIC
- Say Y here if you want to use the generic USB serial driver. Please
- read Documentation/usb/usb-serial.txt for more information on using
- this driver. It is recommended that the "USB Serial converter
+ Say Y here if you want to use the generic USB serial driver. Please
+ read <file:Documentation/usb/usb-serial.txt> for more information on
+ using this driver. It is recommended that the "USB Serial converter
X support" be compiled as a module for this driver to be used
X properly.
X
@@ -11447,20 +12733,31 @@
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called whiteheat.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called whiteheat.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Handspring Visor Driver
X 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
+ 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
X driver.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called visor.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>.
+

+USB IR Dongle Serial Driver
+CONFIG_USB_SERIAL_IR
+ Say Y here if you want to enable simple serial support for USB IrDA
+ devices. This is useful if you do not want to use the full IrDA
+ stack.
+
+ This code is also available as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want).

+ The module will be called ir-usb.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X USB Belkin and Paracom Single Port Serial Driver
X CONFIG_USB_SERIAL_BELKIN
@@ -11471,20 +12768,21 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called belkin_sa.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB FTDI Single Port Serial Driver
X CONFIG_USB_SERIAL_FTDI_SIO
X Say Y here if you want to use a FTDI SIO single port USB to serial
X converter device. The implementation I have is called the USC-1000.
+ This driver has also be tested with the 245 and 232 devices.
X
- See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
+ See http://ftdi-usb-sio.sourceforge.net for more
X information on this driver and the device.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called ftdi_sio.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called ftdi_sio.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Keyspan PDA Single Port Serial Driver
X CONFIG_USB_SERIAL_KEYSPAN_PDA
@@ -11494,8 +12792,8 @@
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called keyspan_pda.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.

+ The module will be called keyspan_pda.o. If you want to compile it

+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Xircom / Entregra Single Port Serial Driver
X CONFIG_USB_SERIAL_XIRCOM
@@ -11513,14 +12811,14 @@
X Say Y here if you want to use Keyspan USB to serial converter
X devices. This driver makes use of Keyspan's official firmware
X and was developed with their support. You must also include
- firmware to support your particular device(s).
+ firmware to support your particular device(s).
+
+ See <http://misc.nu/hugh/keyspan.html> for more information.
X
- See http://misc.nu/hugh/keyspan.html for more information.
-
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called keyspan.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>.
X

X USB Keyspan USA-28 Firmware
X CONFIG_USB_SERIAL_KEYSPAN_USA28
@@ -11566,8 +12864,8 @@
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called omninet.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called omninet.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X USB Digi International AccelePort USB Serial Driver
X CONFIG_USB_SERIAL_DIGI_ACCELEPORT
@@ -11581,33 +12879,34 @@
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called digi_acceleport.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called digi_acceleport.o. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
X
X USB Empeg empeg-car Mark I/II Driver
X CONFIG_USB_SERIAL_EMPEG
X Say Y here if you want to connect to your Empeg empeg-car Mark I/II
X mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
- device node. See Documentation/usb/usb-serial.txt for more
+ device node. See <file:Documentation/usb/usb-serial.txt> for more
X tidbits of information.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called empeg.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>.
X

X USB MCT Single Port Serial Driver
X CONFIG_USB_SERIAL_MCT_U232
X Say Y here if you want to use a USB Serial single port adapter from
X Magic Control Technology Corp. (U232 is one of the model numbers).
-
+
X This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB
X BAY devices.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called mct_u232.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Prolific 2303 Single Port Serial Driver
X CONFIG_USB_SERIAL_PL2303
@@ -11617,19 +12916,19 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called pl2303.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X USB REINER SCT cyberJack pinpad/e-com chipcard reader
X CONFIG_USB_SERIAL_CYBERJACK
X Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard
X reader. This is an interface to ISO 7816 compatible contactbased
X chipcards, e.g. GSM SIMs.
-
+
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called cyberjack.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.

+ a module, say M here and read <file:Documentation/modules.txt>.

+
X If unsure, say N.
X
X USB Edgeport Serial Driver
@@ -11655,8 +12954,8 @@
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called io_edgeport.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.

+ The module will be called io_edgeport.o. If you want to compile it

+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Serial Converter verbose debug
X CONFIG_USB_SERIAL_DEBUG
@@ -11671,57 +12970,85 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called printer.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>.
X

X USB IBM (Xirlink) C-It Camera support
X CONFIG_USB_IBMCAM
X Say Y here if you want to connect a IBM "C-It" camera, also known as
- "Xirlink PC Camera" to your computer's USB port. For more
- information, read Documentation/usb/ibmcam.txt.
+ "Xirlink PC Camera" to your computer's USB port. For more
+ information, read <file:Documentation/usb/ibmcam.txt>.
X
X This driver uses the Video For Linux API. You must enable
X (Y or M in config) Video For Linux (under Character Devices)
X to use this driver. Information on this API and pointers to
X "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called ibmcam.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. This camera
- has several configuration options which can be specified when you
- load the module. Read Documentation/usb/ibmcam.txt to learn more.
+ The module will be called ibmcam.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. This
+ camera has several configuration options which can be specified when
+ you load the module. Read <file:Documentation/usb/ibmcam.txt> to
+ learn more.
X
X USB OV511 Camera support
X CONFIG_USB_OV511
X Say Y here if you want to connect this type of camera to your
- computer's USB port. See Documentation/usb/ov511.txt for more
+ computer's USB port. See <file:Documentation/usb/ov511.txt> for more
X information and for a list of supported cameras.
-
+
X This driver uses the Video For Linux API. You must say Y or M to
X "Video For Linux" (under Character Devices) to use this driver.
X Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called ov511.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>.
+

+USB Communication Class Ethernet driver
+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>.
+
+ This driver should work with the following devices:
+ * Ericsson PipeRider (all variants)
+ * Motorola (DM100 and SB4100)
+ * Broadcom Cable Modem (reference design)
+ * Toshiba PCX1100U and possibly other cable modems
+
+ The device creates a network device (ethX, where X depends on what
+ other networking devices you have in use), as for a normal PCI
+ or ISA based ethernet network card.
+
+ This code is also available as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want).

+ The module will be called CDCEther.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.

+
+NetChip 1080-based USB Host-to-Host Link
+CONFIG_USB_NET1080
+ The NetChip 1080 is a USB 1.1 host controller. NetChip has a web
+ site with technical information at <http://www.netchip.com/>.
X
X Philips webcam support
X CONFIG_USB_PWC
X Say Y or M here if you want to use one of these Philips USB webcams:
- PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
- the Askey VC010. The PCA635, PCVC665 and PCVC720 are not
- supported by this driver and never will be.
-
- This driver has an optional plugin, which is distributed as a
- binary module only. It contains code that allow you to use
- higher resolutions and framerates but may not be distributed
- as source. But even without this plugin you can these cams
- for most applications.
+ PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
+ the Askey VC010. The PCA635, PCVC665 and PCVC720 are not supported
+ by this driver and never will be.
+
+ This driver has an optional plugin, which is distributed as a binary
+ module only. It contains code that allow you to use higher
+ resolutions and framerates but may not be distributed as source.
+ But even without this plugin you can these cams for most
+ applications.
X
- See Documentation/usb/philips.txt for more information and
+ See <file:Documentation/usb/philips.txt> for more information and
X installation instructions.
X
X The built-in microphone is enabled by selecting USB Audio support.
@@ -11729,29 +13056,12 @@
X This driver uses the Video For Linux API. You must say Y or M to
X "Video For Linux" (under Character Devices) to use this driver.
X Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called pwc.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

-
-
-USB SE401 Camera support
-CONFIG_USB_SE401
- Say Y here if you want to connect this type of camera to your
- computer's USB port. See Documentation/usb/se401.txt for more
- information and for a list of supported cameras.
-
- This driver uses the Video For Linux API. You must say Y or M to
- "Video For Linux" (under Multimedia Devices) to use this driver.
- Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
-
- This code is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module will be called se401.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called pwc.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X Pegasus/Pegasus II based USB-Ethernet device support
X CONFIG_USB_PEGASUS
@@ -11765,8 +13075,9 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called pegasus.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>.
X

+USB KLSI KL5USB101-based Ethernet device support '
X CONFIG_USB_KAWETH
X Say Y here if you want to use one of the following 10Mbps only
X USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
@@ -11783,7 +13094,7 @@
X Kingston Technology USB Ethernet Adapter
X Linksys USB10T
X Mobility USB-Ethernet Adapter
- NetGear EA-101
+ NetGear EA-101
X Peracom Enet and Enet2
X Portsmith Express Ethernet Adapter
X Shark Pocket Adapter
@@ -11815,62 +13126,39 @@
X CATC NetMate II
X smartBridges smartNIC
X
+ This driver makes the adapter appear as a normal Ethernet interface,
+ typically on eth0, if it is the only ethernet device, or perhaps on
+ eth1, if you have a PCI or ISA ethernet card installed.
+
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called catc.o. If you want to compile it as a
X module, say M here and read <file:Documentation/modules.txt>.
X
-USB Communication Class Ethernet driver
-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>.
-
- This driver should work with the following devices:
- * Ericsson PipeRider (all variants)
- * Motorola (DM100 and SB4100)
- * Broadcom Cable Modem (reference design)
- * Toshiba PCX1100U and possibly other cable modems
-
- The device creates a network device (ethX, where X depends on what
- other networking devices you have in use), as for a normal PCI
- or ISA based ethernet network card.
-
- This code is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module will be called CDCEther.o. If you want to compile it as
- a module, say M here and read <file:Documentation/modules.txt>.
-
-NetChip 1080-based USB Host-to-Host Link
-CONFIG_USB_NET1080
- The NetChip 1080 is a USB 1.1 host controller. NetChip has a web
- site with technical information at http://www.netchip.com/ .
-
X USB Kodak DC-2xx Camera support
X CONFIG_USB_DC2XX
- Say Y here if you want to connect this type of still camera to
- your computer's USB port. See Documentation/usb/dc2xx.txt for more
- information; some non-Kodak cameras may also work with this
- driver, given application support (such as www.gPhoto.org).
+ 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>).
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called dc2xx.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>.
X

-USB Mustek MDC800 Digital Camera Support
+USB Mustek MDC800 Digital Camera support
X CONFIG_USB_MDC800
X Say Y here if you want to connect this type of still camera to
X 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>).
X To use it create a device node with "mknod /dev/mustek c 180 32" and
X configure it in your software.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called mdc800.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>.
X

X USB Mass Storage support
X CONFIG_USB_STORAGE
@@ -11880,7 +13168,7 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called usb-storage.o. If you want to compile it

- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
X

X USB Mass Storage verbose debug
X CONFIG_USB_STORAGE_DEBUG
@@ -11907,7 +13195,7 @@
X Technologies USS-720 chip. These cables are plugged into your USB
X port and provide USB compatibility to peripherals designed with
X parallel port interfaces.
-
+
X The chip has two modes: automatic mode and manual mode. In automatic
X mode, it looks to the computer like a standard USB printer. Only
X printers may be connected to the USS-720 in this mode. The generic
@@ -11927,29 +13215,33 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called uss720.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>.
+

X USB device file system
X CONFIG_USB_DEVICEFS
- If you say Y here (and to "/proc file system support" below), you
- will get a file /proc/bus/usb/devices which lists the devices
- currently connected to your USB busses, a file /proc/bus/usb/drivers
- which lists the USB kernel client drivers currently loaded, and for
- every connected device a file named "/proc/bus/usb/xxx/yyy", where
- xxx is the bus number and yyy the device number; the latter files
- can be used by user space programs to talk directly to the device.
- These files are "virtual", meaning they are generated on the fly
- and not stored on the hard drive.
-
- For the format of the /proc/bus/usb/ files, please read
- Documentation/usb/proc_usb_info.txt.
+ If you say Y here (and to "/proc file system support" in the "File
+ systems section, above), you will get a file /proc/bus/usb/devices
+ which lists the devices currently connected to your USB bus or
+ busses, a file /proc/bus/usb/drivers which lists the USB kernel
+ client drivers currently loaded, and for every connected device a
+ file named "/proc/bus/usb/xxx/yyy", where xxx is the bus number and
+ yyy the device number; the latter files can be used by user space
+ programs to talk directly to the device. These files are "virtual",
+ meaning they are generated on the fly and not stored on the hard
+ drive.
+
+ You may need to mount the usbdevfs file system to see the files, use
+ mount -t usbdevfs none /proc/bus/usb
+
+ For the format of the various /proc/bus/usb/ files, please read
+ <file:Documentation/usb/proc_usb_info.txt>.
X
X Please note that this code is completely unrelated to devfs, the
X "/dev file system support".
X
X Most users want to say Y here.
X
-USB Bandwidth allocation
+Enforce USB bandwidth allocation
X CONFIG_USB_BANDWIDTH
X If you say Y here, the USB subsystem enforces USB bandwidth
X allocation and will prevent some device opens from succeeding
@@ -11963,23 +13255,25 @@
X DABUSB driver
X CONFIG_USB_DABUSB
X A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
- 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
+ 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
X isochronous transactions. URB's are explained in
- Documentation/usb/URB.txt.
+ <file:Documentation/usb/URB.txt>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called dabusb.o. If you want to compile it as a

- module, say M here and read Documentation/modules.txt.

+ The module will be called dabusb.o. If you want to compile it as a

+ module, say M here and read <file:Documentation/modules.txt>.
X

X Host-to-Host USB networking
X CONFIG_USB_USBNET
X This driver supports network links over USB with USB "Network"
X or "data transfer" cables, often used to network laptops to PCs.
- Such cables have chips from suppliers such as NetChip and Prolific.
- Intelligent USB devices could also use this approach to provide
- Internet access, using standard USB cabling.
+ Such cables have chips from suppliers such as Belkin/eTEK, GeneSys
+ (GeneLink), NetChip and Prolific. Intelligent USB devices could also
+ use this approach to provide Internet access, using standard USB
+ cabling. You can find these chips also on some motherboards with
+ USB PC2PC support.
X
X These links will have names like "usb0", "usb1", etc. They act
X like two-node Ethernets, so you can use 802.1d Ethernet Bridging
@@ -11990,16 +13284,32 @@
X The module will be called usbnet.o. If you want to compile it as a
X module, say M here and read <file:Documentation/modules.txt>.
X
+Freecom USB/ATAPI Bridge support
+CONFIG_USB_STORAGE_FREECOM
+ Support for the Freecom USB to IDE/ATAPI adaptor.
+ Freecom has a web page at <http://www.freecom.de/>.
+
+Microtech CompactFlash/SmartMedia reader
+CONFIG_USB_STORAGE_DPCM
+ Say Y here to support the Microtech ZiO! CompactFlash/SmartMedia
+ 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
+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.
+
X USB Diamond Rio500 support
X CONFIG_USB_RIO500
X Say Y here if you want to connect a USB Rio500 mp3 player to your
- computer's USB port. Please read Documentation/usb/rio.txt
+ computer's USB port. Please read <file:Documentation/usb/rio.txt>
X for more information.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called rio500.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
X

X D-Link DSB-R100 FM radio support
X CONFIG_USB_DSBR
@@ -12012,18 +13322,256 @@
X (Y or M in config) Video For Linux (under Character Devices)
X to use this driver. Information on this API and pointers to
X "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called dsbr100.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>.
+

+Always do synchronous disk IO for UBD
+CONFIG_BLK_DEV_UBD_SYNC
+ The User-Mode Linux port includes a driver called UBD which will let
+ you access arbitrary files on the host computer as block devices.
+ Writes to such a block device are not immediately written to the
+ host's disk; this may cause problems if, for example, the User-Mode
+ Linux 'Virtual Machine' uses a journalling file system and the host
+ computer crashes.
+
+ Synchronous operation (i.e. always writing data to the host's disk
+ immediately) is configurable on a per-UBD basis by using a special
+ kernel command line option. Alternatively, you can say Y here to
+ turn on synchronous operation by default for all block.
+
+ If you're running a journalling file system (like reiserfs, for
+ example) in your virtual machine, you will want to say Y here. If
+ you care for the safety of the data in your virtual machine, Y is a
+ wise choice too. In all other cases (for example, if you're just
+ playing around with User-Mode Linux) you can choose N.
+
+Enable ptrace proxy
+CONFIG_PT_PROXY
+ This option enables a debugging interface which allows gdb to debug
+ the kernel without needing to actually attach to kernel threads.
+ If you want to do kernel debugging, say Y here; otherwise say N.
+
+Management console
+CONFIG_MCONSOLE
+ The user mode linux management console is a low-level interface to
+ the kernel, somewhat like the i386 SysRq interface. Since there is
+ a full-blown operating system running under every user mode linux
+ instance, there is much greater flexibility possible than with the
+ SysRq mechanism.
+
+ If you answer 'Y' to this option, to use this feature, you need the
+ mconsole client (called uml_mconsole) which is present in CVS in
+ 2.4.5-9um and later (path /tools/mconsole), and is also in the
+ distribution RPM package in 2.4.6 and later.
+
+ It is safe to say 'Y' here.
+
+Enable kernel debugging symbols
+CONFIG_DEBUGSYM
+ When this is enabled, the User-Mode Linux binary will include
+ debugging symbols. This enlarges the binary by a few megabytes,
+ but aids in tracking down kernel problems in UML. It is required
+ if you intend to do any kernel development.
+
+ If you're truly short on disk space or don't expect to report any
+ bugs back to the UML developers, say N, otherwise say Y.
+
+Enable gcov support
+CONFIG_GCOV
+ This option allows developers to retrieve coverage data from a UML
+ session.
+
+ See <http://user-mode-linux.sourceforge.net/gcov.html> for more
+ details.
+
+ If you're involved in UML kernel development and want to use gcov,
+ say Y. If you're unsure, say N.
+
+Enable gprof support
+CONFIG_GPROF
+ This allows profiling of a User-Mode Linux kernel with the gprof
+ utility.
+
+ See <http://user-mode-linux.sourceforge.net/gprof.html> for more
+ details.
+
+ If you're involved in UML kernel development and want to use gprof,
+ say Y. If you're unsure, say N.
+
+Host filesystem
+CONFIG_HOSTFS
+ While the User-Mode Linux port uses its own root file system for
+ booting and normal file access, this module lets the UML user
+ access files stored on the host. It does not require any
+ network connection between the Host and UML. An example use of
+ this might be:
+
+ mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
+
+ where /tmp/fromhost is an empty directory inside UML and
+ /tmp/umlshare is a directory on the host with files the UML user
+ wishes to access.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/hostfs.html>.
+
+ If you'd like to be able to work with files stored on the host,
+ say Y or M here; otherwise say N.
+
+Example IO Memory driver
+CONFIG_MMAPPER
+ The User-Mode Linux port can provide support for IO Memory
+ emulation with this option. This allows a host file to be
+ specified as an I/O region on the kernel command line. That file
+ will be mapped into UML's kernel address space where a driver can
+ locate it and do whatever it wants with the memory, including
+ providing an interface to it for UML processes to use.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/iomem.html>.
+
+ If you'd like to be able to provide a simulated IO port space for
+ User-Mode Linux processes, say Y. If unsure, say N.
+
+Virtual Serial Line
+CONFIG_SSL
+ The User-Mode Linux environment allows you to create virtual serial
+ lines on the UML that are usually made to show up on the host as
+ ttys or ptys.
+
+ See <http://user-mode-linux.sourceforge.net/input.html> for more
+ information and command line examples of how to use this facility.
+
+ Unless you have a specific reason for disabling this, say Y.
+
+Virtual network device
+CONFIG_UML_NET
+ While the User-Mode port cannot directly talk to any physical
+ hardware devices, this choice and the following transport options
+ provide one or more virtual network devices through which the UML
+ kernels can talk to each other, the host, and with the host's help,
+ machines on the outside world.
+
+ For more information, including explations of the networking and
+ sample configurations, see
+ <http://user-mode-linux.sourceforge.net/networking.html>.
+
+ If you'd like to be able to enable networking in the User-Mode
+ linux environment, say Y; otherwise say N. Note that you must
+ enable at least one of the following transport options to actually
+ make use of UML networking.
+
+Daemon transport
+CONFIG_UML_NET_DAEMON
+ This User-Mode Linux network transport allows one or more running
+ UMLs on a single host to communicate with each other, but not to
+ the host.
+
+ To use this form of networking, you'll need to run the UML
+ networking daemon on the host.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Daemon
+ networking.
+
+ If you'd like to set up a network with other UMLs on a single host,
+ say Y. If you need a network between UMLs on multiple physical
+ hosts, choose the Multicast Transport. To set up a network with
+ the host and/or other IP machines, say Y to the Ethertap or Slip
+ transports. You'll need at least one of them, but may choose
+ more than one without conflict. If you don't need UML networking,
+ say N.
+
+Ethertap transport
+CONFIG_UML_NET_ETHERTAP
+ The Ethertap User-Mode Linux network transport allows a single
+ 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
+ Ethernet network, it's in fact communicating over a point-to-point
+ link with the host.
+
+ To use this, your host kernel must have support for Ethertap
+ devices. Also, if your host kernel is 2.4.x, it must have
+ CONFIG_NETLINK_DEV configured as Y or M.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Ethertap
+ networking.
+
+ If you'd like to set up an IP network with the host and/or the
+ outside world, say Y to this, the Daemon Transport and/or the
+ Slip Transport. You'll need at least one of them, but may choose
+ more than one without conflict. If you don't need UML networking,
+ say N.
+
+TUN/TAP transport
+CONFIG_UML_NET_TUNTAP
+ The UML TUN/TAP network transport allows a UML instance to exchange
+ packets with the host over a TUN/TAP device. This option will only
+ work with a 2.4 host, unless you've applied the TUN/TAP patch to
+ your 2.2 host kernel.
+
+ To use this transport, your host kernel must have support for TUN/TAP
+ devices, either built-in or as a module.
+
+Multicast transport
+CONFIG_UML_NET_MCAST
+ This Multicast User-Mode Linux network transport allows multiple
+ UMLs (even ones running on different host machines!) to talk to
+ each other over a virtual ethernet network. However, it requires
+ at least one UML with one of the other transports to act as a
+ bridge if any of them need to be able to talk to their hosts or any
+ other IP machines.
+
+ To use this, your host kernel(s) must support IP Multicasting.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Multicast
+ networking, and notes about the security of this approach.
+
+ If you need UMLs on multiple physical hosts to communicate as if
+ they shared an Ethernet network, say Y. If you need to communicate
+ with other IP machines, make sure you select one of the other
+ transports (possibly in addition to Multicast; they're not
+ exclusive). If you don't need to network UMLs say N to each of
+ the transports.
+
+SLIP transport
+CONFIG_UML_NET_SLIP
+ The Slip User-Mode Linux network transport allows a running UML to
+ network with its host over a point-to-point link. Unlike Ethertap,
+ which can carry any Ethernet frame (and hence even non-IP packets),
+ the Slip transport can only carry IP packets.
+
+ To use this, your host must support Slip devices.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html>. That site
+ has examples of the UML command line to use to enable Slip
+ networking, and details of a few quirks with it.
+
+ The Ethertap Transport is preferred over Slip because of its
+ limitation. If you prefer Slip, however, say Y here. Otherwise
+ choose the Multicast transport (to network multiple UMLs on
+ multiple hosts), Ethertap (to network with the host and the
+ outside world), and/or the Daemon transport (to network multiple
+ UMLs on a single host). You may choose more than one without
+ conflict. If you don't need UML networking, say N.
X
X Microtek USB scanner support
X CONFIG_USB_MICROTEK
X Say Y here if you want support for the Microtek X6USB and
X possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L.
- Support for anything but the X6 is experimetal.
+ Support for anything but the X6 is experimental.
X Please report failures and successes.
X The scanner will appear as a scsi generic device to the rest
X of the system. Scsi support is required for this driver to compile
@@ -12040,14 +13588,14 @@
X CONFIG_USB_BLUETOOTH
X Say Y here if you want to connect a USB Bluetooth device to your
X 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
X the device.
X
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called bluetooth.o. If you want to compile it as

- a module, say M here and read Documentation/modules.txt.

-
+ The module will be called bluetooth.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.

+
X Minix fs support
X CONFIG_MINIX_FS
X Minix is a simple operating system used in many classes about OS's.
@@ -12056,58 +13604,75 @@
X but has been superseded by the second extended file system ext2fs.
X You don't want to use the minix file system on your hard disk
X because of certain built-in restrictions, but it is sometimes found
- on older Linux floppy disks. This option will enlarge your kernel by
- about 28 KB. If unsure, say N.
+ on older Linux floppy disks. This option will enlarge your kernel
+ by about 28 KB. If unsure, say N.
X
X If you want to compile this as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt. The module will be
- called minix.o. Note that the file system of your root partition
- (the one containing the directory /) cannot be compiled as a module.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called minix.o. Note that the file system of your root
+ partition (the one containing the directory /) cannot be compiled as
+ a module.
X
X Reiserfs support
X CONFIG_REISERFS_FS
-
X Stores not just filenames but the files themselves in a balanced
X tree. Uses journaling.
X
- Balanced trees are more efficient than traditional
- filesystem architectural foundations.
+ Balanced trees are more efficient than traditional file system
+ architectural foundations.
X
- 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 www.reiserfs.org for
- links.
+ 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.
X
X It is more easily extended to have features currently found in
- database and keyword search systems than block allocation based
- filesystems are. The next version will be so extended, and will
- support plugins consistent with our motto ``It takes more than a
- license to make source code open.''
+ database and keyword search systems than block allocation based file
+ systems are. The next version will be so extended, and will support
+ plugins consistent with our motto ``It takes more than a license to
+ make source code open.''
X
- Read www.reiserfs.org to learn more about reiserfs.
+ Read <http://www.reiserfs.org> to learn more about reiserfs.
X
X Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
X
X If you like it, you can pay us to add new features to it that you
X need, buy a support contract, or pay us to port it to another OS.
X
-Enable Reiserfs consistency checks
+Enable extra Reiserfs consistency checks
X CONFIG_REISERFS_CHECK
- If you set this to yes, then ReiserFS will perform every check it
- can possibly imagine of its internal consistency throughout its
+ If you set this to Y, then ReiserFS will perform every check it can
+ possibly imagine of its internal consistency throughout its
X operation. It will also go substantially slower. More than once we
X have forgotten that this was on, and then gone despondent over the
X latest benchmarks.:-) Use of this option allows our team to go all
X out in checking for consistency when debugging without fear of its
X effect on end users. If you are on the verge of sending in a bug
- report, say yes and you might get a useful error message. Almost
- everyone should say no.
+ report, say Y and you might get a useful error message. Almost
+ everyone 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 (+8 KB). 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 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.
X
X Second extended fs support
X CONFIG_EXT2_FS
X This is the de facto standard Linux file system (method to organize

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 011'
echo 'File patch-2.4.15 is continued in part 012'
echo "012" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:48 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part012

#!/bin/sh -x
# this is part 012 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 012; then

- files on a storage device) for hard disks.
+ files on a storage device) for hard disks.
X
X You want to say Y here, unless you intend to use Linux exclusively
X from inside a DOS partition using the UMSDOS file system. The
@@ -12125,70 +13690,151 @@
X by about 44 KB.
X
X The Ext2fs-Undeletion mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , gives information about
+ <http://www.linuxdoc.org/docs.html#howto>, gives information about
X how to retrieve deleted files on ext2fs file systems.
X
X To change the behavior of ext2 file systems, you can use the tune2fs
X utility ("man tune2fs"). To modify attributes of files and
X directories on ext2 file systems, use chattr ("man chattr").
-
+
X Ext2fs partitions can be read from within DOS using the ext2tool
X command line tool package (available via FTP (user: anonymous) from
- ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
+ <ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2>) and from
X within Windows NT using the ext2nt command line tool package from
- ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
+ <ftp://metalab.unc.edu/pub/Linux/utils/dos>. Explore2fs is a
X graphical explorer for ext2fs partitions which runs on Windows 95
X and Windows NT and includes experimental write support; it is
X available from
- http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
+ <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
+
+ If you want to compile this file system 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 ext2.o. Be aware however that the file system
+ of your root partition (the one containing the directory /) cannot
+ be compiled as a module, and so this could be dangerous. Most
+ everyone wants to say Y here.
+
+Ext3 journaling file system support (EXPERIMENTAL)
+CONFIG_EXT3_FS
+ This is the journaling 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
+ 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
+ is consistent without the need for a lengthy check.
+
+ Other than adding the journal to the file system, the on-disk format
+ of ext3 is identical to ext2. It is possible to freely switch
+ between using the ext3 driver and the ext2 driver, as long as the
+ file system has been cleanly unmounted, or e2fsck is run on the file
+ system.
+
+ To add a journal on an existing ext2 file system or change the
+ behavior of ext3 file systems, you can use the tune2fs utility ("man
+ tune2fs"). To modify attributes of files and directories on ext3
+ file systems, use chattr ("man chattr"). You need to be using
+ e2fsprogs version 1.20 or later in order to create ext3 journals
+ (available at <http://sourceforge.net/projects/e2fsprogs/>).
X
X If you want to compile this file system as a module ( = code which
X can be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called ext2.o. Be aware however that the file system of your
- root partition (the one containing the directory /) cannot be
- compiled as a module, and so this could be dangerous. Most everyone
- wants to say Y here.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called ext3.o. Be aware however that the file system
+ of your root partition (the one containing the directory /) cannot
+ be compiled as a module, and so this may be dangerous.
X
-BFS file system support (EXPERIMENTAL)
+Journal Block Device support (JBD for ext3) (EXPERIMENTAL)
+CONFIG_JBD
+ This is a generic journaling 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.
+
+ If you are using the ext3 file system, you need to say Y here. If
+ you are not using ext3 then you will probably want to say N.
+
+ If you want to compile this device 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 jbd.o. If you are compiling ext3 into the kernel,
+ you cannot compile this code as a module.
+
+JBD (ext3) debugging support
+CONFIG_JBD_DEBUG
+ If you are using the ext3 journaled file system (or potentially any
+ other file system/device using JBD), this option allows you to
+ enable debugging output while the system is running, in order to
+ help track down any problems you are having. By default the
+ debugging output will be turned off.
+
+ If you select Y here, then you will be able to turn on debugging
+ with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
+ 1 and 5, the higher the number, the more debugging output is
+ generated. To turn debugging off again, do
+ "echo 0 > /proc/sys/fs/jbd-debug".
+
+Buffer Head tracing (DEBUG)
+CONFIG_BUFFER_DEBUG
+ If you are a kernel developer working with file systems or in the
+ block device layer, this buffer head tracing may help you to track
+ down bugs in your code. This enables some debugging macros
+ (BUFFER_TRACE, etc.) which allow you to track the state of a buffer
+ through various layers of code. The debugging code is used
+ primarily by ext3 and JBD code.
+
+ Because this option adds considerably to the size of each buffer,
+ most people will want to say N here.
+
+BFS file system support
X CONFIG_BFS_FS
X Boot File System (BFS) is a file system used under SCO UnixWare to
X allow the bootloader access to the kernel image and other important
- files during the boot process. It is usually mounted under /stand
+ files during the boot process. It is usually mounted under /stand
X and corresponds to the slice marked as "STAND" in the UnixWare
- partition. You should say Y if you want to read or write
- the files on your /stand slice from within Linux. You then also
- need to say Y to "UnixWare slices support", below. More information
- about the BFS file system is contained in the file
- Documentation/filesystems/bfs.txt.
+ partition. You should say Y if you want to read or write the files
+ on your /stand slice from within Linux. You then also need to say Y
+ to "UnixWare slices support", below. More information about the BFS
+ file system is contained in the file
+ <file:Documentation/filesystems/bfs.txt>.
X
X If you don't know what this is about, say N.

X
X If you want to compile this as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be

- called bfs.o. Note that the file system of your root partition (the
- one containing the directory /) cannot be compiled as a module.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called bfs.o. Note that the file system of your root

+ partition (the one containing the directory /) cannot be compiled as
+ a module.
X

X Compressed ROM file system support
X CONFIG_CRAMFS
X Saying Y here includes support for CramFs (Compressed ROM File
- System). Cramfs is designed to be a simple, small, and compressed
- file system for ROM based embedded systems. CramFs is read-only,
+ System). CramFs is designed to be a simple, small, and compressed
+ file system for ROM based embedded systems. CramFs is read-only,
X limited to 256MB file systems (with 16MB files), and doesn't support
X 16/32 bits uid/gid, hard links and timestamps.
-
- See Documentation/filesystems/cramfs.txt and fs/cramfs/README
- for further information.
+
+ See <file:Documentation/filesystems/cramfs.txt> and
+ <file:fs/cramfs/README> for further information.

- called cramfs.o. Note that the root file system (the one containing
- the directory /) cannot be compiled as a module.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called cramfs.o. Note that the root file system (the one
+ containing the directory /) cannot be compiled as a module.

X
X If unsure, say N.

-
+
+CMS file system support
+CONFIG_CMS_FS
+ Read only support for CMS minidisk file systems found on IBM
+ 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.
+
X Virtual memory file system support
X CONFIG_TMPFS
X Tmpfs is a file system which keeps all files in virtual memory.
@@ -12200,8 +13846,8 @@
X Everything is "virtual" in the sense that no files will be created
X on your hard drive; if you reboot, everything in tmpfs will be
X lost.
-
- You should mount the filesystem somewhere to be able to use
+
+ You should mount the file system somewhere to be able to use
X POSIX shared memory. Adding the following line to /etc/fstab should
X take care of things:
X
@@ -12211,10 +13857,10 @@
X if necessary (/dev/shm is automagically created if you use devfs).
X
X You can set limits for the number of blocks and inodes used by the
- filesystem with the mount options "size", "nr_blocks" and
+ file system with the mount options "size", "nr_blocks" and
X "nr_inodes". These parameters accept a suffix k, m or g for kilo,
X mega and giga and can be changed on remount.
-
+
X The initial permissions of the root directory can be set with the
X mount option "mode".
X
@@ -12223,40 +13869,40 @@
X Ramfs is a file system which keeps all files in RAM. It allows
X read and write access.
X
- It is more of an programming example than a useable filesystem. If
+ It is more of an programming example than a useable file system. If
X you need a file system which lives in RAM with limit checking use
X tmpfs.

- called ramfs.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called ramfs.o.
X
-ISO 9660 CDROM file system support
+ISO 9660 CD-ROM file system support
X CONFIG_ISO9660_FS
- This is the standard file system used on CDROMs. It was previously
+ This is the standard file system used on CD-ROMs. It was previously
X known as "High Sierra File System" and is called "hsfs" on other
- Unix systems. The so-called Rock-Ridge extensions which allow for
+ Unix systems. The so-called Rock-Ridge extensions which allow for
X long Unix filenames and symbolic links are also supported by this
- driver. If you have a CDROM drive and want to do more with it than
+ driver. If you have a CD-ROM drive and want to do more with it than
X just listen to audio CDs and watch its LEDs, say Y (and read
- Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
- your kernel by about 27 KB; otherwise say N.
+ <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>), thereby
+ enlarging your kernel by about 27 KB; otherwise say N.

- called isofs.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called isofs.o.
X
-Microsoft Joliet CDROM extensions
+Microsoft Joliet CD-ROM extensions
X CONFIG_JOLIET
- Joliet is a Microsoft extension for the ISO 9660 CDROM file system
+ Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
X which allows for long filenames in unicode format (unicode is the
X new 16 bit character code, successor to ASCII, which encodes the
X characters of almost all languages of the world; see
- http://www.unicode.org for more information). Say Y here if you want
- to be able to read Joliet CDROMs under Linux.
+ <http://www.unicode.org> for more information). Say Y here if you
+ want to be able to read Joliet CD-ROMs under Linux.
X
X Transparent decompression extension
X CONFIG_ZISOFS
@@ -12267,21 +13913,21 @@
X necessary to create such a filesystem. Say Y here if you want to be
X able to read such compressed CD-ROMs.
X
-UDF File System support (read only)
+UDF file system support (read-only)
X CONFIG_UDF_FS
- This is the new file system used on some CDROMs and DVDs. Say Y if
+ This is the new file system used on some CD-ROMs and DVDs. Say Y if
X you intend to mount DVD discs or CDRW's written in packet mode, or
X if written to by other UDF utilities, such as DirectCD. This UDF
X file system support is read-only. If you want to write to UDF
X file systems on some media, you need to say Y to "UDF read-write
X support" below in addition. Please read
- Documentation/filesystems/udf.txt.
+ <file:Documentation/filesystems/udf.txt>.
X
X This file system support is also available as a module ( = code
X which can be inserted in and removed from the running kernel
X whenever you want). The module is called udf.o. If you want to
X compile it as a module, say M here and read
- Documentation/modules.txt.

+ <file:Documentation/modules.txt>.
X

X If unsure, say N.
X

@@ -12315,23 +13961,23 @@
X Linux box, say Y here, mount the floppy under Linux with an MSDOS
X file system and use GNU tar's M option. GNU tar is a program
X available for Unix and DOS ("man tar" or "info tar").
-
+
X It is now also becoming possible to read and write compressed FAT
- file systems; read Documentation/filesystems/fat_cvf.txt for
+ file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
X details.
-
+
X The FAT support will enlarge your kernel by about 37 KB. If unsure,
X say Y.
X
X If you want to compile this as a module however ( = code which can
X be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called fat.o. Note that if you compile the FAT support as a
- module, you cannot compile any of the FAT-based file systems into
- the kernel -- they will have to be modules as well. The file system
- of your root partition (the one containing the directory /) cannot
- be a module, so don't say M here if you intend to use UMSDOS as your
- root file system.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called fat.o. Note that if you compile the FAT
+ support as a module, you cannot compile any of the FAT-based file
+ systems into the kernel -- they will have to be modules as well.
+ The file system of your root partition (the one containing the
+ directory /) cannot be a module, so don't say M here if you intend
+ to use UMSDOS as your root file system.
X
X MSDOS fs support
X CONFIG_MSDOS_FS
@@ -12339,8 +13985,8 @@
X they are compressed; to access compressed MSDOS partitions under
X Linux, you can either use the DOS emulator DOSEMU, described in the
X 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
+ <http://www.linuxdoc.org/docs.html#howto>, or try dmsdosfs in
+ <ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs>. If you
X intend to use dosemu with a non-compressed MSDOS partition, say Y
X here) and MSDOS floppies. This means that file access becomes
X transparent, i.e. the MSDOS files look and behave just like all
@@ -12359,32 +14005,33 @@
X answer Y. This will only work if you said Y to "DOS FAT fs support"
X as well. If you want to compile this as a module however ( = code
X which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
X The module will be called msdos.o.
X
X VFAT (Windows-95) fs support
X CONFIG_VFAT_FS
X This option provides support for normal Windows file systems with
- long filenames. That includes non-compressed FAT-based file systems
+ long filenames. That includes non-compressed FAT-based file systems
X used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
X programs from the mtools package.
X
X You cannot use the VFAT file system for your Linux root partition
X (the one containing the directory /); use UMSDOS instead if you
X want to run Linux from within a DOS partition (i.e. say Y to
- "UMSDOS: Unix like fs on top of std MSDOS fs", below).
+ "Unix like fs on top of std MSDOS fs", below).
X
X The VFAT support enlarges your kernel by about 10 KB and it only
- works if you said Y to the "DOS FAT fs support" above. Please read
- the file Documentation/filesystems/vfat.txt for details. If unsure,
- say Y.
+ works if you said Y to the "DOS FAT fs support" above. Please read
+ the file <file:Documentation/filesystems/vfat.txt> for details. If
+ unsure, say Y.
X

X If you want to compile this as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be

- called vfat.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called vfat.o.
X
-UMSDOS: Unix-like file system on top of standard MSDOS fs
+Unix-like file system on top of standard MSDOS fs
X CONFIG_UMSDOS_FS
X Say Y here if you want to run Linux from within an existing DOS
X partition of your hard drive. The advantage of this is that you can
@@ -12392,34 +14039,25 @@
X backing everything up and restoring afterwards) and hence you're
X able to quickly try out Linux or show it to your friends; the
X disadvantage is that Linux becomes susceptible to DOS viruses and
- that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
+ that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
X is to write files with long unix filenames to MSDOS floppies; it
X also allows Unix-style soft-links and owner/permissions of files on
- MSDOS floppies. You will need a program called umssync in order to
- make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
+ MSDOS floppies. You will need a program called umssync in order to
+ make use of UMSDOS; read
+ <file:Documentation/filesystems/umsdos.txt>.
X
X To get utilities for initializing/checking UMSDOS file system, or
X latest patches and/or information, visit the UMSDOS home page at
- http://www.voyager.hr/~mnalis/umsdos/ .
+ <http://www.voyager.hr/~mnalis/umsdos/>.
X
X This option enlarges your kernel by about 28 KB and it only works if
X you said Y to both "DOS FAT fs support" and "MSDOS fs support"
- above. If you want to compile this as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt. The module will be

- called umsdos.o. Note that the file system of your root partition
- (the one containing the directory /) cannot be a module, so saying M
- could be dangerous. If unsure, say N.
-
-PReP residual data support
-CONFIG_PREP_RESIDUAL
- Some PReP systems have residual data passed to the kernel by the
- firmware. This allows detection of memory size, devices present and
- other useful pieces of information. Sometimes this information is not
- present or incorrect.
-
- Unless you expect to boot on a PReP system, there is not need to select
- yes.
+ above. If you want to compile this as a module ( = code which can
+ be inserted in and removed from the running kernel whenever you
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called umsdos.o. Note that the file system of your
+ root partition (the one containing the directory /) cannot be a
+ module, so saying M could be dangerous. If unsure, say N.
X
X /proc file system support
X CONFIG_PROC_FS
@@ -12427,7 +14065,7 @@
X of the system. "Virtual" means that it doesn't take up any space on
X your hard disk: the files are created on the fly by the kernel when
X you try to access them. Also, you cannot read the files with older
- version of the program less: you need to use more or cat.
+ version of the program less: you need to use more or cat.
X
X It's totally cool; for example, "cat /proc/interrupts" gives
X information about what the different IRQs are used for at the moment
@@ -12443,13 +14081,23 @@
X /proc" or the equivalent line in /etc/fstab does the job.
X
X The /proc file system is explained in the file
- Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
- 5 proc").
+ <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
+ ("man 5 proc").
X
X This option will enlarge your kernel by about 67 KB. Several
X programs depend on this, so everyone should say Y here.
X
-/dev file system support (EXPERIMENTAL)
+Support for PReP Residual Data
+CONFIG_PREP_RESIDUAL
+ Some PReP systems have residual data passed to the kernel by the
+ firmware. This allows detection of memory size, devices present and
+ other useful pieces of information. Sometimes this information is
+ not present or incorrect.
+
+ Unless you expect to boot on a PReP system, there is not need to
+ select Y.
+
+/dev file system support
X CONFIG_DEVFS_FS
X This is support for devfs, a virtual file system (like /proc) which
X provides the file system interface to device drivers, normally found
@@ -12460,12 +14108,12 @@
X /dev directory using the mknod command (or MAKEDEV script) anymore.
X
X This is work in progress. If you want to use this, you *must* read
- the material in Documentation/filesystems/devfs/, especially the
- file README there.
+ the material in <file:Documentation/filesystems/devfs/>, especially
+ the file README there.

X
X If unsure, say N.
X

-Enable automatic mounting at boot
+Automatically mount devfs at boot time
X CONFIG_DEVFS_MOUNT
X This option appears if you have CONFIG_DEVFS_FS enabled. Setting
X this to 'Y' will make the kernel automatically mount devfs onto /dev
@@ -12478,8 +14126,9 @@
X CONFIG_DEVFS_DEBUG
X If you say Y here, then the /dev file system code will generate
X debugging messages. See the file
- Documentation/filesystems/devfs/boot-options for more details.
-
+ <file:Documentation/filesystems/devfs/boot-options> for more
+ details.
+

X If unsure, say N.
X

X NFS file system support
@@ -12493,35 +14142,35 @@
X programs nfsd and mountd (but does not need to have NFS file system
X support enabled in its kernel). NFS is explained in the Network
X Administrator's Guide, available from
- http://www.linuxdoc.org/docs.html#guide , on its man page: "man
+ <http://www.linuxdoc.org/docs.html#guide>, on its man page: "man
X nfs", and in the NFS-HOWTO.
-
+
X A superior but less widely used alternative to NFS is provided by
X the Coda file system; see "Coda file system support" below.
X
X If you say Y here, you should have said Y to TCP/IP networking also.
- This option would enlarge your kernel by about 27 KB.
+ This option would enlarge your kernel by about 27 KB.
X
X This file system is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module is called nfs.o. If you want to compile it as a module,

- say M here and read Documentation/modules.txt.

+ say M here and read <file:Documentation/modules.txt>.

X
X If you are configuring a diskless machine which will mount its root
- file system over NFS at boot time, say Y here and to "IP: kernel
- level autoconfiguration" above and to "Root file system on NFS"
+ file system over NFS at boot time, say Y here and to "Kernel
+ level IP autoconfiguration" above and to "Root file system on NFS"
X below. You cannot compile this driver as a module in this case.
X There are two packages designed for booting diskless machines over
X the net: netboot and etherboot, both available via FTP from
- ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
+ <ftp://metalab.unc.edu/pub/Linux/system/boot/Ethernet/>.
X
X If you don't know what all this is about, say N.
X
-Provide NFSv3 client support (EXPERIMENTAL)
+Provide NFSv3 client support
X CONFIG_NFS_V3
X Say Y here if you want your NFS client to be able to speak the newer
- version 3 of the NFS protocol.
-
+ version 3 of the NFS protocol.

+
X If unsure, say N.
X

X Root file system on NFS
@@ -12529,12 +14178,12 @@
X If you want your Linux box to mount its whole root file system (the
X one containing the directory /) from some other computer over the
X net via NFS (presumably because your box doesn't have a hard disk),
- say Y. Read Documentation/nfsroot.txt for details. It is likely that
- in this case, you also want to say Y to "IP: kernel level
+ say Y. Read <file:Documentation/nfsroot.txt> for details. It is
+ likely that in this case, you also want to say Y to "Kernel level IP
X autoconfiguration" so that your box can discover its network address
X at boot time.
-
- Most people say N here.
+
+ Most people say N here.
X
X NFS server support
X CONFIG_NFSD
@@ -12547,20 +14196,21 @@
X faster.
X
X In either case, you will need support software; the respective
- locations are given in the file Documentation/Changes in the NFS
- section.
+ locations are given in the file <file:Documentation/Changes> in the
+ NFS section.
X
X If you say Y here, you will get support for version 2 of the NFS
X protocol (NFSv2). If you also want NFSv3, say Y to the next question
X as well.
X
X Please read the NFS-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X The NFS server is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called nfsd.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
+ The module is called nfsd.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
X
X Provide NFSv3 server support
X CONFIG_NFSD_V3
@@ -12572,7 +14222,8 @@
X If you are a developer and want to work on fixing problems with
X NFS server over TCP support, say Y here. If unsure, say N.
X
- Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
+ Some problems can be found by looking for FIXME in
+ <file:net/sunrpc/svcsock.c>.
X
X OS/2 HPFS file system support
X CONFIG_HPFS_FS
@@ -12582,29 +14233,13 @@
X write files to an OS/2 HPFS partition on your hard drive. OS/2
X floppies however are in regular MSDOS format, so you don't need this
X option in order to be able to read them. Read
- Documentation/filesystems/hpfs.txt.
+ <file:Documentation/filesystems/hpfs.txt>.
X
X This file system is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called hpfs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
-
-FreeVxFS file system support (VERITAS VxFS(TM) compatible)
-CONFIG_VXFS_FS
- FreeVxFS is a filesystem driver that support the VERITAS VxFS(TM)
- filesystem format. VERITAS VxFS(TM) is the standard filesystem
- 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 filesystem 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 Documentation/modules.txt. If unsure, say N.
+ The module is called hpfs.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
X
X NTFS file system support (read-only)
X CONFIG_NTFS_FS
@@ -12637,94 +14272,98 @@

X
X If unsure, say N.
X

-System V, Version 7, Xenix and Coherent filesystem support
+System V/Xenix/V7/Coherent file system support
X CONFIG_SYSV_FS
X SCO, Xenix and Coherent are commercial Unix systems for Intel
X machines, and Version 7 was used on the DEC PDP-11. Saying Y
X here would allow you to read from their floppies and hard disk
- partitions. If you also want to write to these media, say Y to
- "SYSV file system write support" below.
+ partitions.
X
X If you have floppies or hard disk partitions like that, it is likely
X that they contain binaries from those other Unix systems; in order
X to run these binaries, you will want to install linux-abi which is a
- a set of kernel modules that lets you run SCO, Xenix, Wyse, UnixWare,
- Dell Unix and System V programs under Linux. It's available via FTP
- (user: ftp) from ftp://ftp.openlinux.org/pub/people/hch/linux-abi).
+ 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>).
X NOTE: that will work only for binaries from Intel-based systems;
X PDP ones will have to wait until somebody ports Linux to -11 ;-)
X
X If you only intend to mount files from some other Unix over the
X network using NFS, you don't need the System V file system support
- (but you need NFS file system support obviously).
+ (but you need NFS file system support obviously).
X
X Note that this option is generally not needed for floppies, since a
X good portable way to transport files and directories between unixes
X (and even other operating systems) is given by the tar program ("man
- tar" or preferably "info tar"). Note also that this option has
+ tar" or preferably "info tar"). Note also that this option has
X nothing whatsoever to do with the option "System V IPC". Read about
- the System V file system in Documentation/filesystems/sysv-fs.txt.
+ the System V file system in
+ <file:Documentation/filesystems/sysv-fs.txt>.
X Saying Y here will enlarge your kernel by about 27 KB.

- called sysv.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called sysv.o.
X
X If you haven't heard about all of this before, it's safe to say N.
X
X Amiga FFS file system support
X CONFIG_AFFS_FS
X The Fast File System (FFS) is the common file system used on hard
- disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
+ disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
X if you want to be able to read and write files from and to an Amiga
- FFS partition on your hard drive. Amiga floppies however cannot be
+ FFS partition on your hard drive. Amiga floppies however cannot be
X read with this driver due to an incompatibility of the floppy
X controller used in an Amiga and the standard floppy controller in
- PCs and workstations. Read Documentation/filesystems/affs.txt and
- fs/affs/Changes.
+ PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
+ and <file:fs/affs/Changes>.
X
X With this driver you can also mount disk files used by Bernd
- Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
+ Schmidt's Un*X Amiga Emulator
+ (<http://www.freiburg.linux.de/~uae/>).
X If you want to do this, you will also need to say Y or M to "Loop
X device support", above.
X
X This file system is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called affs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
+ The module is called affs.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
X
-Apple Macintosh file system support (EXPERIMENTAL)
+Apple Macintosh file system support
X CONFIG_HFS_FS
X If you say Y here, you will be able to mount Macintosh-formatted
X floppy disks and hard drive partitions with full read-write access.
- Please read fs/hfs/HFS.txt to learn about the available mount
- options.
+ Please read <file:fs/hfs/HFS.txt> to learn about the available mount
+ options.
X
X This file system support is also available as a module ( = code
X which can be inserted in and removed from the running kernel
- whenever you want). The module is called hfs.o. If you want to
+ whenever you want). The module is called hfs.o. If you want to
X compile it as a module, say M here and read
- Documentation/modules.txt.

+ <file:Documentation/modules.txt>.
X

X ROM file system support
X CONFIG_ROMFS_FS
X This is a very small read-only file system mainly intended for
X initial ram disks of installation disks, but it could be used for
- other read-only media as well. Read
- Documentation/filesystems/romfs.txt for details.
+ other read-only media as well. Read
+ <file:Documentation/filesystems/romfs.txt> for details.
X
X This file system support is also available as a module ( = code
X which can be inserted in and removed from the running kernel
- whenever you want). The module is called romfs.o. If you want to
+ whenever you want). The module is called romfs.o. If you want to
X compile it as a module, say M here and read
- Documentation/modules.txt. Note that the file system of your root
- partition (the one containing the directory /) cannot be a module.
+ <file:Documentation/modules.txt>. Note that the file system of your
+ root partition (the one containing the directory /) cannot be a
+ module.
X
X If you don't know whether you need it, then you don't need it:
X answer N.
X
-QNX4 file system support (read only) (EXPERIMENTAL)
+QNX4 file system support (read only)
X CONFIG_QNX4FS_FS
X This is the file system used by the operating system QNX 4. Say Y if
X you intend to mount QNX hard disks or floppies. Unless you say Y to
@@ -12735,7 +14374,7 @@
X which can be inserted in and removed from the running kernel
X whenever you want). The module is called qnx4.o. If you want to
X compile it as a module, say M here and read
- Documentation/modules.txt.

+ <file:Documentation/modules.txt>.
X

X If you don't know whether you need it, then you don't need it:
X answer N.
@@ -12752,8 +14391,8 @@
X automounter (amd), which is a pure user space daemon.
X
X To use the automounter you need the user-space tools from the autofs
- package; you can find the location in Documentation/Changes. You
- also want to answer Y to "NFS file system support", below.
+ package; you can find the location in <file:Documentation/Changes>.
+ You also want to answer Y to "NFS file system support", below.
X
X If you want to use the newer version of the automounter with more
X features, say N here and say Y to "Kernel automounter v4 support",
@@ -12761,13 +14400,13 @@

- called autofs.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called autofs.o.
X
X If you are not a part of a fairly large, distributed network, you
X probably do not need an automounter, and can say N here.
X
-Kernel automounter v4 support
+Kernel automounter version 4 support (also supports v3)
X CONFIG_AUTOFS4_FS
X The automounter is a tool to automatically mount remote file systems
X on demand. This implementation is partially kernel-based to reduce
@@ -12775,46 +14414,70 @@
X automounter (amd), which is a pure user space daemon.
X
X 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
X want to answer Y to "NFS file system support", below.

- called autofs4.o. You will need to add "alias autofs autofs4" to
- your modules configuration file.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called autofs4.o. You will need to add "alias autofs
+ autofs4" to your modules configuration file.
X
X If you are not a part of a fairly large, distributed network or
X don't have a laptop which needs to dynamically reconfigure to the
X local network, you probably do not need an automounter, and can say
X N here.
X
-EFS file system support (read-only) (EXPERIMENTAL)
+EFS file system support (read-only)
X CONFIG_EFS_FS
- EFS is an older file system used for non-ISO9660 CDROMs and hard
+ EFS is an older file system used for non-ISO9660 CD-ROMs and hard
X disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
X uses the XFS file system for hard disk partitions however).
X
X This implementation only offers read-only access. If you don't know
X what all this is about, it's safe to say N. For more information
- about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
+ about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
X
X If you want to compile the EFS file system support as a module ( =
X code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called efs.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called efs.o.
X
-Support for the Journalling Flash Filesystem
+Journalling Flash File System (JFFS) support
X CONFIG_JFFS_FS
X JFFS is the Journaling Flash File System developed by Axis
X Communications in Sweden, aimed at providing a crash/powerdown-safe
- filesystem for disk-less embedded devices. Further information is
- available at (http://developer.axis.com/software/jffs/).
+ file system for disk-less embedded devices. Further information is
+ available at (<http://developer.axis.com/software/jffs/>).
X
-JFFS debugging verbosity
+JFFS debugging verbosity (0 = quiet, 3 = noisy)
X CONFIG_JFFS_FS_VERBOSE
X Determines the verbosity level of the JFFS debugging messages.
X
+Journalling Flash File System v2 (JFFS2) support
+CONFIG_JFFS2_FS
+ JFFS2 is the second generation of the Journalling Flash File System
+ for use on diskless embedded devices. It provides improved wear
+ levelling, compression and support for hard links. You cannot use
+ this on normal block devices, only on 'MTD' devices.
+
+ Further information should be made available soon at
+ <http://sources.redhat.com/jffs2/>.
+
+JFFS2 debugging verbosity (0 = quiet, 2 = noisy)
+CONFIG_JFFS2_FS_DEBUG
+ This controls the amount of debugging messages produced by the JFFS2
+ code. Set it to zero for use in production systems. For evaluation,
+ testing and debugging, it's advisable to set it to one. This will
+ enable a few assertions and will print debugging messages at the
+ KERN_DEBUG loglevel, where they won't normally be visible. Level 2
+ is unlikely to be useful - it enables extra debugging in certain
+ areas which at one point needed debugging, but when the bugs were
+ located and fixed, the detailed messages were relegated to level 2.
+
+ If reporting bugs, please try to have available a full dump of the
+ messages at debug level 1 while the misbehaviour was occurring.
+
X UFS file system support (read-only)
X CONFIG_UFS_FS
X BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
@@ -12823,11 +14486,11 @@
X this file system as well. Saying Y here will allow you to read from
X these partitions; if you also want to write to them, say Y to the
X experimental "UFS file system write support", below. Please read the
- file Documentation/filesystems/ufs.txt for more information.
+ file <file:Documentation/filesystems/ufs.txt> for more information.
X
X If you only intend to mount files from some other Unix over the
X network using NFS, you don't need the UFS file system support (but
- you need NFS file system support obviously).
+ you need NFS file system support obviously).
X
X Note that this option is generally not needed for floppies, since a
X good portable way to transport files and directories between unixes
@@ -12836,12 +14499,12 @@
X
X When accessing NeXTstep files, you may need to convert them from the
X NeXT character set to the Latin1 character set; use the program
- recode ("info recode") for this purpose.
+ recode ("info recode") for this purpose.
X
X If you want to compile the UFS file system support as a module ( =
X code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called ufs.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called ufs.o.
X
X If you haven't heard about all of this before, it's safe to say N.
X
@@ -12857,11 +14520,38 @@
X architecture than your Linux system.
X
X Note that the answer to this question won't directly affect the

- kernel: saying N will just cause this configure script to skip all

- the questions about foreign partitioning schemes.

+ kernel: saying N will just cause the configurator to skip all

+ the questions about foreign partitioning schemes.

X
X If unsure, say N.
X

+Acorn partition support
+CONFIG_ACORN_PARTITION
+ Support hard disks partitioned under Acorn operating systems.
+
+Native filecore partition support
+CONFIG_ACORN_PARTITION_ADFS
+ The Acorn Disc Filing System is the standard file system of the
+ RiscOS operating system which runs on Acorn's ARM-based Risc PC
+ systems and the Acorn Archimedes range of machines. If you say
+ `Y' here, Linux will support disk partitions created under ADFS.
+
+PowerTec partition support
+CONFIG_ACORN_PARTITION_POWERTEC
+ Support reading partition tables created on Acorn machines using
+ the PowerTec SCSI drive.
+
+RISCiX partition support
+CONFIG_ACORN_PARTITION_RISCIX
+ Once upon a time, there was a native Unix port for the Acorn series
+ of machines called RISCiX. If you say 'Y' here, Linux will be able
+ to read disks partitioned under RISCiX.
+
+ICS partition support
+CONFIG_ACORN_PARTITION_ICS
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned using the ICS interface on Acorn machines.
+
X Alpha OSF partition support
X CONFIG_OSF_PARTITION
X Say Y here if you would like to use hard disks under Linux which
@@ -12884,10 +14574,11 @@
X mirrored, striped or RAID volumes, all without the need for
X rebooting.
X
- Normal partitions are now called Basic Disks under Windows 2000 and XP.
+ Normal partitions are now called Basic Disks under Windows 2000 and
+ XP.
X
X Technical documentation to accompany this driver is available from:
- <http://linux-ntfs.sf.net/ldm>
+ <http://linux-ntfs.sf.net/ldm>.

X
X If unsure, say N.
X

@@ -12904,6 +14595,16 @@
X Say Y here if you would like to use hard disks under Linux which
X were partitioned on an x86 PC (not necessarily by DOS).
X
+Amiga partition table support
+CONFIG_AMIGA_PARTITION
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned under AmigaOS.
+
+Atari partition table support
+CONFIG_ATARI_PARTITION
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned under the Atari OS.
+
X BSD disklabel (FreeBSD partition tables) support
X CONFIG_BSD_DISKLABEL
X FreeBSD uses its own hard disk partition scheme on your PC. It
@@ -12921,7 +14622,7 @@
X Say Y here if you want to mount and use Minix 2.0.0/2.0.2
X subpartitions.
X
-Sun partition tables support
+Sun partition table support
X CONFIG_SUN_PARTITION
X Like most systems, SunOS uses its own hard disk partition table
X format, incompatible with all others. Saying Y here allows you to
@@ -12947,13 +14648,19 @@
X Say Y here if you would like to be able to read the hard disk
X partition table format used by SGI machines.
X
-Ultrix partition support
+Ultrix partition table support
X CONFIG_ULTRIX_PARTITION
X Say Y here if you would like to be able to read the hard disk
X partition table format used by DEC (now Compaq) Ultrix machines.
X Otherwise, say N.
X
-ADFS file system support (EXPERIMENTAL)
+IBM disk label and partition support
+CONFIG_IBM_PARTITION
+ Say Y here if you would like to be able to read the hard disk
+ partition table format used by IBM DASD disks operating under CMS.
+ Otherwise, say N.
+
+ADFS file system support
X CONFIG_ADFS_FS
X The Acorn Disc Filing System is the standard file system of the
X RiscOS operating system which runs on Acorn's ARM-based Risc PC
@@ -12964,12 +14671,12 @@
X
X The ADFS partition should be the first partition (i.e.,
X /dev/[hs]d?1) on each of your drives. Please read the file
- Documentation/filesystems/adfs.txt for further details.
+ <file:Documentation/filesystems/adfs.txt> for further details.
X
X This code is also available as a module called adfs.o ( = code which
X can be inserted in and removed from the running kernel whenever you
X want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.

+ <file:Documentation/modules.txt>.
X

X If unsure, say N.
X

@@ -12989,17 +14696,55 @@
X to acquire a pseudo terminal, a process opens /dev/ptmx; the number
X of the pseudo terminal is then made available to the process and the
X pseudo terminal slave can be accessed as /dev/pts/<number>. What was
- traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
+ traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
X
X The GNU C library glibc 2.1 contains the requisite support for this
X mode of operation; you also need client programs that use the Unix98
- API. Please read Documentation/Changes for more information about
- the Unix98 pty devices.
+ API. Please read <file:Documentation/Changes> for more information
+ about the Unix98 pty devices.
X
X Note that the experimental "/dev file system support"
X (CONFIG_DEVFS_FS) is a more general facility.
X
-UnixWare slices support (EXPERIMENTAL)
+# 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)
+ 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 file system 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.

+
+# 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
X CONFIG_UNIXWARE_DISKLABEL
X Like some systems, UnixWare uses its own slice table inside a
X partition (VTOC - Virtual Table of Contents). Its format is
@@ -13013,7 +14758,7 @@
X removable IDE drives. Note, however, that a good portable way to
X transport files and directories between unixes (and even other
X operating systems) is given by the tar program ("man tar" or
- preferably "info tar").
+ preferably "info tar").
X
X If you don't know what all this is about, say N.
X
@@ -13021,29 +14766,29 @@
X CONFIG_SMB_FS
X SMB (Server Message Block) is the protocol Windows for Workgroups
X (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
- files and printers over local networks. Saying Y here allows you to
+ files and printers over local networks. Saying Y here allows you to
X mount their file systems (often called "shares" in this context) and
- access them just like any other Unix directory. Currently, this
+ access them just like any other Unix directory. Currently, this
X works only if the Windows machines use TCP/IP as the underlying
- transport protocol, and not NetBEUI. For details, read
- Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available

- from http://www.linuxdoc.org/docs.html#howto .

+ transport protocol, and not NetBEUI. For details, read
+ <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X
X Note: if you just want your box to act as an SMB *server* and make
X files and printing services available to Windows clients (which need
X to have a TCP/IP stack), you don't need to say Y here; you can use
X the program samba (available via FTP (user: anonymous) in
- ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
+ <ftp://metalab.unc.edu/pub/Linux/system/network/samba>) for that.
X
X General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
X
X If you want to compile the SMB support as a module ( = code which
X can be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called smbfs.o. Most people say N, however.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called smbfs.o. Most people say N, however.
X
-use nls by default
+Use a default NLS
X CONFIG_SMB_NLS_DEFAULT
X Enabling this will make smbfs use nls translations by default. You
X need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
@@ -13055,7 +14800,7 @@
X
X smbmount from samba 2.2.0 or later supports this.
X
-nls support setting
+Default Remote NLS Option
X CONFIG_SMB_NLS_REMOTE
X This setting allows you to specify a default value for which
X codepage the server uses. If this field is left blank no
@@ -13072,72 +14817,85 @@
X Coda is an advanced network file system, similar to NFS in that it
X enables you to mount file systems of a remote server and access them
X with regular Unix commands as if they were sitting on your hard
- disk. Coda has several advantages over NFS: support for disconnected
- operation (e.g. for laptops), read/write server replication,
- security model for authentication and encryption, persistent client
- caches and write back caching.
+ disk. Coda has several advantages over NFS: support for
+ disconnected operation (e.g. for laptops), read/write server
+ replication, security model for authentication and encryption,
+ persistent client caches and write back caching.
X
X If you say Y here, your Linux box will be able to act as a Coda
- *client*. You will need user level code as well, both for the client
- and server. Servers are currently user level, i.e. they need no
- kernel support. Please read Documentation/filesystems/coda.txt and
- check out the Coda home page http://www.coda.cs.cmu.edu .
+ *client*. You will need user level code as well, both for the
+ 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>.
X
X If you want to compile the coda client support as a module ( = code
X which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called coda.o.
+ 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)
+CONFIG_INTERMEZZO_FS
+ InterMezzo is a networked file system with disconnected operation
+ and kernel level write back caching. It is most often used for
+ replicating potentially large trees or keeping laptop/desktop copies
+ in sync.
+
+ 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>.
X
X NCP file system support (to mount NetWare volumes)
X CONFIG_NCP_FS
X NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
- used by Novell NetWare clients to talk to file servers. It is to IPX
- what NFS is to TCP/IP, if that helps. Saying Y here allows you to
- mount NetWare file server volumes and to access them just like any
- other Unix directory. For details, please read the file
- Documentation/filesystems/ncpfs.txt in the kernel source and the
- IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
+ used by Novell NetWare clients to talk to file servers. It is to
+ IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
+ to mount NetWare file server volumes and to access them just like
+ any other Unix directory. For details, please read the file
+ <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
+ the IPX-HOWTO from <http://www.linuxdoc.org/docs.html#howto>.
X
X You do not have to say Y here if you want your Linux box to act as a
X file *server* for Novell NetWare clients.
X
X General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.

- called ncpfs.o. Say N unless you are connected to a Novell network.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called ncpfs.o. Say N unless you are connected to a Novell
+ network.
X
X Packet signatures
X CONFIG_NCPFS_PACKET_SIGNING
X NCP allows packets to be signed for stronger security. If you want
- security, say Y. Normal users can leave it off. To be able to use
+ security, say Y. Normal users can leave it off. To be able to use
X packet signing you must use ncpfs > 2.0.12.
X
X Proprietary file locking
X CONFIG_NCPFS_IOCTL_LOCKING
- Allows locking of records on remote volumes. Say N unless you have
+ Allows locking of records on remote volumes. Say N unless you have
X special applications which are able to utilize this locking scheme.
X
X Clear remove/delete inhibit when needed
X CONFIG_NCPFS_STRONG
- Allows manipulation of files flagged as Delete or Rename Inhibit. To
- use this feature you must mount volumes with the ncpmount parameter
- "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
- volumes with -f 444.
+ Allows manipulation of files flagged as Delete or Rename Inhibit.
+ To use this feature you must mount volumes with the ncpmount
+ parameter "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not
+ mounting volumes with -f 444.
X
-Use NFS namespace when available
+Use NFS namespace if available
X CONFIG_NCPFS_NFS_NS
- Allows you to utilize NFS namespace on NetWare servers. It brings
- you case sensitive filenames. Say Y. You can disable it at
+ Allows you to utilize NFS namespace on NetWare servers. It brings

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 012'
echo 'File patch-2.4.15 is continued in part 013'
echo "013" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:49 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part013

#!/bin/sh -x
# this is part 013 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 013; then

+ you case sensitive filenames. Say Y. You can disable it at
X mount-time with the `-N nfs' parameter of ncpmount.
X
-Use OS2/LONG namespace when available
+Use LONG (OS/2) namespace if available
X CONFIG_NCPFS_OS2_NS
X Allows you to utilize OS2/LONG namespace on NetWare servers.
X Filenames in this namespace are limited to 255 characters, they are
- case insensitive, and case in names is preserved. Say Y. You can
+ case insensitive, and case in names is preserved. Say Y. You can
X disable it at mount time with the -N os2 parameter of ncpmount.
X
X Lowercase DOS filenames on LONG namespace volume
@@ -13146,7 +14904,7 @@
X the OS2/LONG namespace and created under DOS or on a volume using
X DOS namespace will be converted to lowercase characters.
X Saying N here will give you these filenames in uppercase.
-
+
X This is only a cosmetic option since the OS2/LONG namespace is case
X insensitive. The only major reason for this option is backward
X compatibility when moving from DOS to OS2/LONG namespace support.
@@ -13158,25 +14916,7 @@
X effects by saying Y to "Allow using of Native Language Support"
X below.
X
-Allow mounting of volume subdirectories
-CONFIG_NCPFS_MOUNT_SUBDIR
- Allows you to mount not only whole servers or whole volumes, but
- also subdirectories from a volume. It can be used to reexport data
- and so on. There is no reason to say N, so Y is recommended unless
- you count every byte.
-
- To utilize this feature you must use ncpfs-2.0.12 or newer.
-
-NDS authentication support
-CONFIG_NCPFS_NDS_DOMAINS
- This allows storing NDS private keys in kernel space where they
- can be used to authenticate another server as interserver NDS
- accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
- this feature. Say Y if you are using NDS connections to NetWare
- servers. Do not say Y if security is primary for you because root
- can read your session key (from /proc/kcore).
-
-Allow using of Native Language Support
+Use Native Language Support
X CONFIG_NCPFS_NLS
X Allows you to use codepages and I/O charsets for file name
X translation between the server file system and input/output. This
@@ -13194,21 +14934,24 @@
X To use the new attributes, it is recommended to use the flags
X '-f 600 -d 755' on the ncpmount command line.
X
-nls default codepage
+Default NLS Option
X CONFIG_NLS_DEFAULT
- The default NLS used when mounting file system. Currently, the valid
- values are:
+ The default NLS used when mounting file system. Note, that this is
+ the NLS used by your console, not the NLS used by a specific file
+ system (if different) to store data (filenames) on a disk.
+ Currently, the valid values are:
X big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
X cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
- cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
- iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
- iso8859-14, iso8859-15, koi8-r, sjis
- If you specify a wrong value, it will use the built-in NLS; compatible
- with iso8859-1.
+ cp949, cp950, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1,
+ iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7,
+ iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15,
+ koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8.
+ If you specify a wrong value, it will use the built-in NLS;
+ compatible with iso8859-1.
X
X If unsure, specify it as "iso8859-1".
X
-nls codepage 437
+Codepage 437 (United States, Canada)
X CONFIG_NLS_CODEPAGE_437
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored
@@ -13219,7 +14962,7 @@
X say Y here if you want to include the DOS codepage that is used in
X the United States and parts of Canada. This is recommended.
X
-nls codepage 737
+Codepage 737 (Greek)
X CONFIG_NLS_CODEPAGE_737
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored
@@ -13230,7 +14973,7 @@
X say Y here if you want to include the DOS codepage that is used for
X Greek. If unsure, say N.
X
-nls codepage 775
+Codepage 775 (Baltic Rim)
X CONFIG_NLS_CODEPAGE_775
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored
@@ -13239,9 +14982,10 @@
X DOS/Windows partitions correctly. This does apply to the filenames
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage that is used
- for the Baltic Rim Languages. If unsure, say N.
+ for the Baltic Rim Languages (Latvian and Lithuanian). If unsure,
+ say N.
X
-nls codepage 850
+Codepage 850 (Europe)
X CONFIG_NLS_CODEPAGE_850
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13252,11 +14996,11 @@
X say Y here if you want to include the DOS codepage that is used for
X much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
X more countries here]. It has some characters useful to many European
- languages that are not part of the US codepage 437.
+ languages that are not part of the US codepage 437.
X
X If unsure, say Y.
X
-nls codepage 852
+Codepage 852 (Central/Eastern Europe)
X CONFIG_NLS_CODEPAGE_852
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13270,7 +15014,7 @@
X Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
X transcription), Slovak, Slovenian, and Sorbian.
X
-nls codepage 855
+Codepage 855 (Cyrillic)
X CONFIG_NLS_CODEPAGE_855
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13280,7 +15024,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Cyrillic.
X
-nls codepage 857
+Codepage 857 (Turkish)
X CONFIG_NLS_CODEPAGE_857
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13290,7 +15034,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Turkish.
X
-nls codepage 860
+Codepage 860 (Portuguese)
X CONFIG_NLS_CODEPAGE_860
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13300,7 +15044,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Portuguese.
X
-nls codepage 861
+Codepage 861 (Icelandic)
X CONFIG_NLS_CODEPAGE_861
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13310,7 +15054,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Icelandic.
X
-nls codepage 862
+Codepage 862 (Hebrew)
X CONFIG_NLS_CODEPAGE_862
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13320,7 +15064,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Hebrew.
X
-nls codepage 863
+Codepage 863 (Canadian French)
X CONFIG_NLS_CODEPAGE_863
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13331,7 +15075,7 @@
X say Y here if you want to include the DOS codepage for Canadian
X French.
X
-nls codepage 864
+Codepage 864 (Arabic)
X CONFIG_NLS_CODEPAGE_864
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13341,7 +15085,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Arabic.
X
-nls codepage 865
+Codepage 865 (Norwegian, Danish)
X CONFIG_NLS_CODEPAGE_865
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13352,7 +15096,7 @@
X say Y here if you want to include the DOS codepage for the Nordic
X European countries.
X
-nls codepage 866
+Codepage 866 (Cyrillic/Russian)
X CONFIG_NLS_CODEPAGE_866
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13363,7 +15107,7 @@
X say Y here if you want to include the DOS codepage for
X Cyrillic/Russian.
X
-nls codepage 869
+Codepage 869 (Greek)
X CONFIG_NLS_CODEPAGE_869
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13373,7 +15117,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Greek.
X
-nls codepage 874
+Thai charset (CP874, TIS-620)
X CONFIG_NLS_CODEPAGE_874
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13383,7 +15127,18 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Thai.
X
-nls codepage 932
+Windows CP1251 (Bulgarian, Belarusian)
+CONFIG_NLS_CODEPAGE_1251
+ The Microsoft FAT file system family can deal with filenames in
+ native language character sets. These character sets are stored in
+ so-called DOS codepages. You need to include the appropriate
+ codepage if you want to be able to read/write these filenames on
+ DOS/Windows partitions correctly. This does apply to the filenames
+ only, not to the file contents. You can include several codepages;
+ say Y here if you want to include the DOS codepage for Russian and
+ Bulgarian and Belarusian.
+
+Japanese charsets (Shift-JIS, EUC-JP)
X CONFIG_NLS_CODEPAGE_932
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13393,9 +15148,9 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for Shift-JIS
X or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
- NLS Default value during kernel configuration , instead of 'cp932'
+ NLS Default value during kernel configuration, instead of 'cp932'.
X
-nls codepage 936
+Simplified Chinese charset (CP936, GB2312)
X CONFIG_NLS_CODEPAGE_936
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13406,7 +15161,7 @@
X say Y here if you want to include the DOS codepage for Simplified
X Chinese(GBK).
X
-nls codepage 949
+Korean charset (CP949, EUC-KR)
X CONFIG_NLS_CODEPAGE_949
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13416,7 +15171,7 @@
X only, not to the file contents. You can include several codepages;
X say Y here if you want to include the DOS codepage for UHC.
X
-nls codepage 950
+Traditional Chinese charset (Big5)
X CONFIG_NLS_CODEPAGE_950
X The Microsoft FAT file system family can deal with filenames in
X native language character sets. These character sets are stored in
@@ -13427,10 +15182,10 @@
X say Y here if you want to include the DOS codepage for Traditional
X Chinese(Big5).
X
-nls iso8859-1
+NLS ISO 8859-1 (Latin 1; Western European Languages)
X CONFIG_NLS_ISO8859_1
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 1 character
X set, which covers most West European languages such as Albanian,
@@ -13438,101 +15193,110 @@
X Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
X and Swedish. It is also the default for the US. If unsure, say Y.
X
-nls iso8859-2
+NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)
X CONFIG_NLS_ISO8859_2
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 2 character
X set, which works for most Latin-written Slavic and Central European
X languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
X Slovak, Slovene.
X
-nls iso8859-3
+NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)
X CONFIG_NLS_ISO8859_3
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 3 character
X set, which is popular with authors of Esperanto, Galician, Maltese,
X and Turkish.
X
-nls iso8859-4
+NLS ISO 8859-4 (Latin 4; old Baltic charset)
X CONFIG_NLS_ISO8859_4
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 4 character
X set which introduces letters for Estonian, Latvian, and
- Lithuanian. It is an incomplete predecessor of Latin 6.
+ Lithuanian. It is an incomplete predecessor of Latin 7.
X
-nls iso8859-5
+NLS ISO 8859-5 (Cyrillic)
X CONFIG_NLS_ISO8859_5
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for ISO8859-5, a Cyrillic
- character set with which you can type Bulgarian, Byelorussian,
+ character set with which you can type Bulgarian, Belarusian,
X Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
X KOI8-R is preferred in Russia.
X
-nls iso8859-6
+NLS ISO 8859-6 (Arabic)
X CONFIG_NLS_ISO8859_6
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for ISO8859-6, the Arabic
X character set.
X
-nls iso8859-7
+NLS ISO 8859-7 (Modern Greek)
X CONFIG_NLS_ISO8859_7
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for ISO8859-7, the Modern
X Greek character set.
X
-nls iso8859-8
+Hebrew charsets (ISO-8859-8, CP1255)
X CONFIG_NLS_ISO8859_8
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for ISO8859-8, the Hebrew
X character set.
X
-nls iso8859-9
+NLS ISO 8859-9 (Latin 5; Turkish)
X CONFIG_NLS_ISO8859_9
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 5 character
X set, and it replaces the rarely needed Icelandic letters in Latin 1
X with the Turkish ones. Useful in Turkey.
X
-nls iso8859-10
+NLS ISO 8859-10 (Latin 6; Nordic)
X CONFIG_NLS_ISO8859_10
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 6 character
X set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
X letters that were missing in Latin 4 to cover the entire Nordic
X area.
X
+NLS ISO 8859-13 (Latin 7; Baltic)
+CONFIG_NLS_ISO8859_13
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the Latin 7 character
+ set, which supports modern Baltic languages including Latvian
+ and Lithuanian.
+
X NLS ISO 8859-14 (Latin 8; Celtic)
X CONFIG_NLS_ISO8859_14
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 8 character
X set, which adds the last accented vowels for Welsh (aka Cymraeg)
- (and Manx Gaelic) hat were missing in Latin 1.
- http://linux.speech.cymru.org/ has further information.
+ (and Manx Gaelic) that were missing in Latin 1.
+ <http://linux.speech.cymru.org/> has further information.
X
-nls iso8859-15
+NLS ISO 8859-15 (Latin 9; Western European languages with Euro)
X CONFIG_NLS_ISO8859_15
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the Latin 9 character
X set, which covers most West European languages such as Albanian,
@@ -13541,17 +15305,33 @@
X Portuguese, Spanish, and Swedish. Latin 9 is an update to
X Latin 1 (ISO 8859-1) that removes a handful of rarely used
X characters and instead adds support for Estonian, corrects the
- support for French and Finnish, and adds the new Euro character. If
- unsure, say Y.
+ support for French and Finnish, and adds the new Euro character.
+ If unsure, say Y.
X
-nls koi8-r
+NLS KOI8-R (Russian)
X CONFIG_NLS_KOI8_R
X If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
X correctly on the screen, you need to include the appropriate
X input/output character sets. Say Y here for the preferred Russian
X character set.
X
+NLS KOI8-U/RU (Ukrainian, Belarusian)
+CONFIG_NLS_KOI8_U
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the preferred Ukrainian
+ (koi8-u) and Belarusian (koi8-ru) character sets.
+
+NLS UTF8
+CONFIG_NLS_UTF8
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the UTF-8 encoding of
+ the Unicode/ISO9646 universal character set.
+
X Virtual terminal
X CONFIG_VT
X If you say Y here, you will get support for terminal devices with
@@ -13599,38 +15379,236 @@
X
X If unsure, say Y.
X
-Support for PowerMac keyboard
-CONFIG_MAC_KEYBOARD
+STI console
+CONFIG_STI_CONSOLE
+ The STI console is the builtin display/keyboard on HP-PARISC
+ machines. Say Y here to build support for it into your kernel.
+ The alternative is to use your primary serial port as a console.
+
+Use MDIO for PHY configuration
+CONFIG_USE_MDIO
+ On some boards the hardware configuration of the ethernet PHY can be
+ used without any software interaction over the MDIO interface, so
+ all MII code can be omitted. Say N here if unsure or if you don't
+ need link status reports.
+
+860T FEC Ethernet
+CONFIG_FEC_ENET
+ Enable Ethernet support via the Fast Ethernet Controller (FCC) on
+ the Motorola MPC8260.
+
+Ethernet on FCC1
+CONFIG_FCC1_ENET
+ Use MPC8260 fast Ethernet controller 1 to drive Ethernet (default).
+
+Ethernet on FCC2
+CONFIG_FCC2_ENET
+ Use MPC8260 fast Ethernet controller 2 to drive Ethernet.
+
+Ethernet on FCC3
+CONFIG_FCC3_ENET
+ Use MPC8260 fast Ethernet controller 3 to drive Ethernet.
+
+CPM SCC Ethernet
+CONFIG_SCC_ENET
+ Enable Ethernet support via the Motorola MPC8xx serial
+ commmunications controller.
+
+Ethernet on SCC1
+CONFIG_SCC1_ENET
+ Use MPC8xx serial communications controller 1 to drive Ethernet
+ (default).
+
+Ethernet on SCC2
+CONFIG_SCC2_ENET
+ Use MPC8xx serial communications controller 2 to drive Ethernet.
+
+Ethernet on SCC3
+CONFIG_SCC3_ENET
+ Use MPC8xx serial communications controller 3 to drive Ethernet.
+
+Use Big CPM Ethernet Buffers
+CONFIG_ENET_BIG_BUFFERS
+ Allocate large buffers for MPC8xx Etherenet. Increases throughput
+ and decreases the likelihood of dropped packets, but costs memory.
+
+Apple Desktop Bus (ADB) support
+CONFIG_ADB
+ Apple Desktop Bus (ADB) support is for support of devices which
+ are connected to an ADB port. ADB devices tend to have 4 pins.
+ If you have an Apple Macintosh prior to the iMac, or a
+ "Blue and White G3", you probably want to say Y here. Otherwise
+ say N.
+
+Support for CUDA based PowerMacs
+CONFIG_ADB_CUDA
+ This provides support for CUDA based Power Macintosh systems. This
+ includes most OldWorld PowerMacs, the first generation iMacs, the
+ Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
+ should use CONFIG_ADB_PMU instead.
+
+ If unsure say Y.
+
+Support for PMU-based PowerMacs
+CONFIG_ADB_PMU
+ On the PowerBook 3400 and 2400, the PMU is a 6805 microprocessor
+ core whose primary function is to control battery charging and
+ system power. The PMU also controls the ADB (Apple Desktop Bus)
+ which connects to the keyboard and mouse, as well as the
+ non-volatile RAM and the RTC (real time clock) chip. Say Y to
+ enable support for this device; you should do so if your machine
+ is one of these PowerBooks.
+
+Include MacIO ADB driver
+CONFIG_ADB_MACIO
+ Say Y here to include direct support for the ADB controller in the
+ Hydra chip used on PowerPC Macintoshes of the CHRP type. (The Hydra
+ also includes a MESH II SCSI controller, DBDMA controller, VIA chip,
+ OpenPIC controller and two RS422/Geoports.)
+
+Support for ADB keyboard (old driver)
+CONFIG_ADB_KEYBOARD
X This option allows you to use an ADB keyboard attached to your
X machine. Note that this disables any other (ie. PS/2) keyboard
X support, even if your machine is physically capable of using both at
X the same time.
-
+
X If you use an ADB keyboard (4 pin connector), say Y here.
X If you use a PS/2 keyboard (6 pin connector), say N here.
X
-Standard/generic serial support
+HIL keyboard support
+CONFIG_HIL
+ The "Human Interface Loop" is a older, 8-channel USB-like controller
+ used in Hewlette Packard PA-RISC based machines. There are a few
+ cases where it is seen on PC/MAC architectures as well, usually also
+ manufactured by HP. This driver is based off MACH and BSD drivers,
+ and implements support for a keyboard attached to the HIL port.
+ Full support for the USB-like functions and non-keyboard channels of
+ the HIL is not provided for in this driver. There are vestiges of
+ mouse support in the driver, but it is probably not working. The
+ necessary hardware documentation to fully support the HIL controller
+ and interface it to the linux-input API is lacking.
+
+ Enable this option if you intend to use a HIL keyboard.
+
+Include IOP (IIfx/Quadra 9x0) ADB driver
+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
+ support for it, say 'Y' here.
+
+Mac II style Apple Desktop Bus support
+CONFIG_ADB_MACII
+ Say Y here if want your kernel to support Macintosh systems that use
+ the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
+ Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
+ Centris 650.
+
+Mac IIsi style Apple Desktop Bus support
+CONFIG_ADB_MACIISI
+ Say Y here if want your kernel to support Macintosh systems that use
+ the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
+ II, LC, LC II, LC III, Performa 460, and the Performa 600.
+
+Apple 68K PowerBook Power Management and Desktop Bus support
+CONFIG_ADB_PMU68K
+ Say Y here if want your kernel to support the m68k based Powerbooks.
+ This includes the PowerBook 140, PowerBook 145, PowerBook 150,
+ PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
+ PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
+ PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
+ PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
+
+Macintosh IIfx/Quadra 900/Quadra 950 floppy support
+CONFIG_BLK_DEV_SWIM_IOP
+ Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
+ floppy controller on the Macintosh IIfx and Quadra 900/950.
+
+Macintosh NS8390 based Ethernet support
+CONFIG_MAC8390
+ If you want to include a driver to support Nubus or LC-PDS
+ Ethernet cards using an NS8390 chipset or its equivalent, say Y
+ and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh CS89x0 based Ethernet support
+CONFIG_MAC89x0
+ Support for CS89x0 chipset based Ethernet cards. If you have a
+ Nubus or LC-PDS network (Ethernet) card of this type, say Y and
+ read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ If you want to compile this as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want),

+ say M here and read <file:Documentation/modules.txt> as well as

+ <file:Documentation/networking/net-modules.txt>. This module will
+ be called mac89x0.o.
+
+Macintosh onboard AMD 79C940 MACE based Ethernet support
+CONFIG_MACMACE
+ Support for the onboard AMD 79C940 MACE Ethernet controller used in
+ the 660AV and 840AV Macintosh. If you have one of these Macintoshes
+ say Y and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh SONIC based Ethernet support (onboard, NuBus, LC, CS)
+CONFIG_MACSONIC
+ Support for NatSemi SONIC based Ethernet devices. This includes
+ the onboard Ethernet in many Quadras as well as some LC-PDS,
+ a few Nubus and all known Comm Slot Ethernet cards. If you have
+ one of these say Y and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ If you want to compile this as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want),

+ say M here and read <file:Documentation/modules.txt> as well as

+ <file:Documentation/networking/net-modules.txt>. This module will
+ be called macsonic.o.
+
+Macintosh NCR5380 SCSI support
+CONFIG_MAC_SCSI
+ This is the NCR 5380 SCSI controller included on most of the 68030
+ based Macintoshes. If you have one of these say Y and read the
+ SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh NCR53c9[46] SCSI support
+CONFIG_SCSI_MAC_ESP
+ This is the NCR 53c9x SCSI controller found on most of the 68040
+ based Macintoshes. If you have one of these say Y and read the
+ SCSI-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).

+ The module will be called mac_esp.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+Standard/generic (8250/16550 and compatible UARTs) serial support
X CONFIG_SERIAL
X This selects whether you want to include the driver for the standard
- serial ports. The standard answer is Y. People who might say N here
- are those that are setting up dedicated Ethernet WWW/FTP servers, or
- users that have one of the various bus mice instead of a serial
- mouse and don't intend to use their machine's standard serial port
- for anything. (Note that the Cyclades and Stallion multi serial port
- drivers do not need this driver built in for them to work.)
+ serial ports. The standard answer is Y. People who might say N
+ here are those that are setting up dedicated Ethernet WWW/FTP
+ servers, or users that have one of the various bus mice instead of a
+ serial mouse and don't intend to use their machine's standard serial
+ port for anything. (Note that the Cyclades and Stallion multi
+ serial port drivers do not need this driver built in for them to
+ work.)
X
X If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called serial.o.

+ <file:Documentation/modules.txt>. The module will be called

+ serial.o.
X [WARNING: Do not compile this driver as a module if you are using
X non-standard serial ports, since the configuration information will
- be lost when the driver is unloaded. This limitation may be lifted
+ be lost when the driver is unloaded. This limitation may be lifted
X in the future.]
X
X BTW1: If you have a mouseman serial mouse which is not recognized by
- the X window system, try running gpm first.
-
+ the X window system, try running gpm first.
+
X BTW2: If you intend to use a software modem (also called Winmodem)
- under Linux, forget it. These modems are crippled and require
+ under Linux, forget it. These modems are crippled and require
X proprietary drivers which are only available under Windows.
X
X Most people will say Y or M here, so that they can use serial mice,
@@ -13671,7 +15649,8 @@
X become a dial-in server.
X
X If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called rocket.o.

+ <file:Documentation/modules.txt>. The module will be called

+ rocket.o.
X
X Digiboard Intelligent async support
X CONFIG_DIGIEPCA
@@ -13681,14 +15660,14 @@
X box, for instance in order to become a dial-in server. This driver
X supports the original PC (ISA) boards as well as PCI, and EISA. If
X you have a card like this, say Y here and read the file
- Documentation/digiepca.txt.
+ <file:Documentation/digiepca.txt>.
X
X NOTE: There is another, separate driver for the Digiboard PC boards:
X "Digiboard PC/Xx Support" below. You should (and can) only select
- one of the two drivers.
+ one of the two drivers.
X
X If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called epca.o.
+ <file:Documentation/modules.txt>. The module will be called epca.o.
X
X Digiboard PC/Xx Support
X CONFIG_DIGI
@@ -13696,10 +15675,10 @@
X that give you many serial ports. You would need something like this
X to connect more than two modems to your Linux box, for instance in
X order to become a dial-in server. If you have a card like that, say
- Y here and read the file Documentation/digiboard.txt.
+ Y here and read the file <file:Documentation/digiboard.txt>.
X
X If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called pcxx.o.
+ <file:Documentation/modules.txt>. The module will be called pcxx.o.
X
X SDL RISCom/8 card support
X CONFIG_RISCOM8
@@ -13707,7 +15686,7 @@
X which gives you many serial ports. You would need something like
X this to connect more than two modems to your Linux box, for instance
X in order to become a dial-in server. If you have a card like that,
- say Y here and read the file Documentation/riscom8.txt.
+ say Y here and read the file <file:Documentation/riscom8.txt>.
X
X Also it's possible to say M here and compile this driver as kernel
X loadable module; the module will be called riscom8.o.
@@ -13715,37 +15694,50 @@
X Computone IntelliPort Plus serial support
X CONFIG_COMPUTONE
X This driver supports the entire family of Intelliport II/Plus
- controllers with the exception of the MicroChannel controllers and
+ controllers with the exception of the MicroChannel controllers and
X products previous to the Intelliport II. These are multiport cards,
- which give you many serial ports. You would need something like
- this to connect more than two modems to your Linux box, for
- instance in order to become a dial-in server. If you have a
- card like that, say Y here and read Documentation/computone.txt.
+ which give you many serial ports. You would need something like this
+ to connect more than two modems to your Linux box, for instance in
+ order to become a dial-in server. If you have a card like that, say
+ Y here and read <file:Documentation/computone.txt>.

X
X If you want to compile this as a module ( = code which can be
X inserted in and removed from the running kernel whenever you want),

- say M here and read Documentation/modules.txt. You will get two
- modules called ip2.o and ip2main.o.
+ say M here and read <file:Documentation/modules.txt>. You will get
+ two modules called ip2.o and ip2main.o.
X
X Specialix IO8+ card support
X CONFIG_SPECIALIX
X This is a driver for the Specialix IO8+ multiport card (both the
- ISA and the PCI version) which gives you many serial ports. You
- would need something like this to connect more than two modems to
+ ISA and the PCI version) which gives you many serial ports. You
+ would need something like this to connect more than two modems to
X your Linux box, for instance in order to become a dial-in server.
X
X If you have a card like that, say Y here and read the file
- Documentation/specialix.txt. Also it's possible to say M here and
- compile this driver as kernel loadable module which will be called
- specialix.o.
+ <file:Documentation/specialix.txt>. Also it's possible to say M here
+ and compile this driver as kernel loadable module which will be
+ called specialix.o.
X
X Specialix DTR/RTS pin is RTS
X CONFIG_SPECIALIX_RTSCTS
- The Specialix card can only support either RTS or DTR. If you say N
- here, the driver will use the pin as "DTR" when the tty is in
- software handshake mode. If you say Y here or hardware handshake is
- on, it will always be RTS. Read the file Documentation/specialix.txt
- for more information.
+ The Specialix IO8+ card can only support either RTS or DTR. If you
+ say N here, the driver will use the pin as "DTR" when the tty is in
+ software handshake mode. If you say Y here or hardware handshake is
+ on, it will always be RTS. Read the file
+ <file:Documentation/specialix.txt> for more information.
+
+Specialix RIO system support
+CONFIG_RIO
+ This is a driver for the Specialix RIO, a smart serial card which
+ drives an outboard box that can support up to 128 ports. Product
+ information is at <http://www.sphinxcst.co.uk/perle/multi.htm>.
+ There are both ISA and PCI versions.
+
+Support really old RIO/PCI cards
+CONFIG_RIO_OLDPCI
+ Older RIO PCI cards need some initialization-time configuration to
+ determine the IRQ and some control addresses. If you have a RIO and
+ this doesn't seem to work, try setting this to Y.
X
X Cyclades async mux support
X CONFIG_CYCLADES
@@ -13753,19 +15745,19 @@
X would need something like this to connect more than two modems to
X your Linux box, for instance in order to become a dial-in server.
X For information about the Cyclades-Z card, read
- drivers/char/README.cycladesZ.
+ <file:drivers/char/README.cycladesZ>.
X
X As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
X of 32.

- called cyclades.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called cyclades.o.
X
X If you haven't heard about it, it's safe to say N.
X
-Cyclades-Z interrupt mode operation (EXPERIMENTAL)
+Cyclades-Z interrupt mode operation
X CONFIG_CYZ_INTR
X The Cyclades-Z family of multiport cards allows 2 (two) driver op
X modes: polling and interrupt. In polling mode, the driver will check
@@ -13775,47 +15767,47 @@
X status of the Cyclades-Z ports. The default op mode is polling. If
X unsure, say N.
X
-Stallion multiport serial support
+Stallion multiport serial support
X CONFIG_STALDRV
- Stallion cards give you many serial ports. You would need something
+ Stallion cards give you many serial ports. You would need something
X like this to connect more than two modems to your Linux box, for
- instance in order to become a dial-in server. If you say Y here, you
- will be asked for your specific card model in the next questions.
- Make sure to read drivers/char/README.stallion in this case. If you
- have never heard about all this, it's safe to say N.
+ instance in order to become a dial-in server. If you say Y here,
+ you will be asked for your specific card model in the next
+ questions. Make sure to read <file:Documentation/stallion.txt> in
+ this case. If you have never heard about all this, it's safe to
+ say N.
X
-Stallion EasyIO or EC8/32 support
+Stallion EasyIO or EC8/32 support
X CONFIG_STALLION
X If you have an EasyIO or EasyConnection 8/32 multiport Stallion
- card, then this is for you; say Y. Make sure to read
- Documentation/stallion.txt.
+ card, then this is for you; say Y. Make sure to read
+ <file:Documentation/stallion.txt>.

- called stallion.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called stallion.o.
X
X Stallion EC8/64, ONboard, Brumby support
X CONFIG_ISTALLION
X If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
X serial multiport card, say Y here. Make sure to read
- Documentation/stallion.txt.
+ <file:Documentation/stallion.txt>.
X
X To compile it as a module ( = code which can be inserted in and
X removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt. The module will be called
+ read <file:Documentation/modules.txt>. The module will be called
X istallion.o.
X
X Microgate SyncLink adapter support
X CONFIG_SYNCLINK
- Provides support for the SyncLink ISA and PCI
- multiprotocol serial adapters. These adapters
- support asynchronous and HDLC bit synchronous
- communication up to 10Mbps (PCI adapter).
+ Provides support for the SyncLink ISA and PCI multiprotocol serial
+ adapters. These adapters support asynchronous and HDLC bit
+ synchronous communication up to 10Mbps (PCI adapter).
X
X This driver can only be built as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called synclink.o. If you want to do that, say M
+ The module will be called synclink.o. If you want to do that, say M
X here.
X
X Synchronous HDLC line discipline support
@@ -13831,7 +15823,7 @@
X Specialix SX (and SI) card support
X CONFIG_SX
X This is a driver for the SX and SI multiport serial cards.
- Please read the file Documentation/sx.txt for details.
+ Please read the file <file:Documentation/sx.txt> for details.
X
X This driver can only be built as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

@@ -13839,14 +15831,14 @@
X
X Hayes ESP serial port support
X CONFIG_ESPSERIAL
- This is a driver which supports Hayes ESP serial ports. Both single
- port cards and multiport cards are supported. Make sure to read
- Documentation/hayes-esp.txt.
+ This is a driver which supports Hayes ESP serial ports. Both single
+ port cards and multiport cards are supported. Make sure to read
+ <file:Documentation/hayes-esp.txt>.
X
X To compile this driver as a module ( = code which can be inserted in
X and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called esp.o.
- If unsure, say N.
+ and read <file:Documentation/modules.txt>. The module will be
+ called esp.o. If unsure, say N.
X
X Moxa Intellio support
X CONFIG_MOXA_INTELLIO
@@ -13866,13 +15858,14 @@
X The module will be called mxser.o. If you want to do that, say M
X here.
X
-Multi-Tech multiport card support (EXPERIMENTAL)
+Multi-Tech multiport card support
X CONFIG_ISI
X This is a driver for the Multi-Tech cards which provide several
- serial ports. The driver is experimental and can currently only be
+ serial ports. The driver is experimental and can currently only be
X built as a module ( = code which can be inserted in and removed from
- the running kernel whenever you want). Please read
- Documentation/modules.txt. The module will be called isicom.o
+ the running kernel whenever you want). Please read

+ <file:Documentation/modules.txt>. The module will be called

+ isicom.o.
X
X Unix98 PTY support
X CONFIG_UNIX98_PTYS
@@ -13882,7 +15875,7 @@
X read data from and write data to the slave, thereby emulating a
X terminal. Typical programs for the master side are telnet servers
X and xterms.
-
+
X Linux has traditionally used the BSD-like names /dev/ptyxx for
X masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
X has a number of problems. The GNU C library glibc 2.1 and later,
@@ -13898,8 +15891,8 @@
X
X If you want to say Y here, you need to have the C library glibc 2.1
X or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
- Read the instructions in Documentation/Changes pertaining to pseudo
- terminals. It's safe to say N.
+ Read the instructions in <file:Documentation/Changes> pertaining to
+ pseudo terminals. It's safe to say N.
X
X Maximum number of Unix98 PTYs in use (0-2048)
X CONFIG_UNIX98_PTY_COUNT
@@ -13916,23 +15909,23 @@
X CONFIG_PRINTER
X If you intend to attach a printer to the parallel port of your Linux
X box (as opposed to using a serial printer; if the connector at the
- printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
- read the Printing-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ printer has 9 or 25 holes ["female"], then it's serial), say Y.
+ Also read the Printing-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X It is possible to share one parallel port among several devices
X (e.g. printer and ZIP drive) and it is safe to compile the
- corresponding drivers into the kernel. If you want to compile this
+ corresponding drivers into the kernel. If you want to compile this
X driver as a module however ( = code which can be inserted in and
X removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt and Documentation/parport.txt. The
- module will be called lp.o.
+ read <file:Documentation/modules.txt> and
+ <file:Documentation/parport.txt>. The module will be called lp.o.
X
X If you have several parallel ports, you can specify which ports to
- use with the "lp" kernel command line option. (Try "man bootparam"
+ use with the "lp" kernel command line option. (Try "man bootparam"
X or see the documentation of your boot loader (lilo or loadlin) about
- how to pass options to the kernel at boot time.) The syntax of the
- "lp" command line option can be found in drivers/char/lp.c.
+ how to pass options to the kernel at boot time.) The syntax of the
+ "lp" command line option can be found in <file:drivers/char/lp.c>.
X
X If you have more than 8 printers, you need to increase the LP_NO
X macro in lp.c and the PARPORT_MAX macro in parport.h.
@@ -13949,7 +15942,7 @@
X By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
X can make the kernel continue when this happens,
X but it'll lose the kernel messages.
-

+
X If unsure, say N.
X

X Support for user-space parallel port device drivers
@@ -13963,74 +15956,206 @@
X It is safe to say N to this -- it is not needed for normal printing
X or parallel port CD-ROM/disk support.
X
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called ppdev.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read

+ <file:Documentation/modules.txt>. The module will be called

+ ppdev.o.

X
X If unsure, say N.
X

+Cobalt Networks support
+CONFIG_COBALT
+ Support for Cobalt Networks x86-based servers.
+
+Gen III (3000 series) system support
+CONFIG_COBALT_GEN_III
+ This option enables support for the 3000 series of Cobalt Networks
+ systems. This includes the RaQ 3, RaQ 4, and Qube 3 product lines.
+
+ This platform uses an AMD K6-2 processor, an ALI M1541/1533 chipset,
+ an optional NCR 53c875 SCSI controller, and two Intel 82559ER or
+ National Semiconductor DP83815 NICs.
+
+ Getting this option wrong will likely result in a kernel that does
+ not boot. Selecting support for more than 1 system series will add
+ bloat to your kernel, but will not cause anything bad to happen.
+
+ If you have a Cobalt Networks System, but aren't sure what kind,
+ say Y here.
+
+Gen V (5000 series) system support
+CONFIG_COBALT_GEN_V
+ This option enables support for the 5000 series of Cobalt Networks
+ systems. This includes the RaQ XTR product line.
+
+ This platform uses Intel Pentium III Coppermine FCPGA CPUs, the
+ ServerWorks LE chipset (with registered ECC DIMMs only!), two
+ HighPoint HPT370 IDE controllers, and two National Semiconductor
+ DP83815 NICs.
+
+ Getting this option wrong will likely result in a kernel that does
+ not boot. Selecting support for more than 1 system series will add
+ bloat to your kernel, but will not cause anything bad to happen.
+
+ If you have a Cobalt Networks System, but aren't sure what kind,
+ say Y here.
+
+Create legacy /proc files
+CONFIG_COBALT_OLDPROC
+ This option forces some Cobalt Networks drivers to support legacy
+ files in /proc. Older versions of these drivers exported files
+ directly in /proc, as opposed to the newer /proc/cobalt. If you say
+ N to this option, the old filenames will no longer be exported.
+ Regardless of your selection here, files in /proc/cobalt will be
+ exported. Of course, you have to include support for /proc fs, too.
+
+ It is safe to say Y here.
+
+Front panel LCD support
+CONFIG_COBALT_LCD
+ This enables support for the Cobalt Networks front panel. This is
+ for the LCD panel and buttons. The primary method for connection is
+ via the parallel port (IO base 0x370), but newer systems use an
+ I2C bus.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Software controlled LED support
+CONFIG_COBALT_LED
+ This enables support for the software-controlled LEDs on Cobalt
+ Networks systems. This includes the fault light and front panel
+ LEDs on the RaQ XTR, the lightbar on the Qube 3, and others.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Silicon serial number support
+CONFIG_COBALT_SERNUM
+ This enables support for the on-board serial number on Cobalt
+ Networks systems. This is a universally-unique 64-bit serial
+ number. Some systems use a Dallas DS2401 chip, others have an I2C
+ based EEPROM.
+
+ If you select Y here, the files /proc/cobalt/hostid and
+ /proc/cobalt/serialnumber will be created. The hostid file contains
+ a 32 bit integer generated from the serial number, in binary form.
+ The serialnumber file contains the hexadecimal representation of the
+ serial number, in ASCII.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Chipset watchdog timer support
+CONFIG_COBALT_WDT
+ This enables support for the watchdog timer built into Cobalt
+ chipsets. The timer wakes up periodically, to make find out if
+ system has hung, or disabled interrupts too long. The result of
+ detecting a hang is a hard reboot.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Thermal sensor support
+CONFIG_COBALT_THERMAL
+ This enables support for the thermal sensor(s) built into Cobalt
+ Networks systems. This driver exports /proc/cobalt/thermal_sensors.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Fan tachometer support
+CONFIG_COBALT_FANS
+ This enables support for the fan tachometers built into some Cobalt
+ Networks systems. This driver exports /proc/cobalt/faninfo. Some
+ Cobalt software depends on this feature, and enabling it does not
+ cause any risks.
+
+ If you have a Cobalt Networks system, you should say Y here, unless
+ you are absolutely sure.
+
+Disk drive ruler support
+CONFIG_COBALT_RULER
+ This enables support for the cobalt hard drive ruler, found on some
+ Cobalt systems, including the RaQ XTR. This is the device that
+ enables swapping of drives. It is not needed for basic disk
+ operation. Enabling this on a system with no ruler will have no
+ adverse effects.
+
+ If you have a Cobalt Networks system, you should say Y here,
+ unless you are absolutely sure.
+
X I2C support
X CONFIG_I2C
X I2C (pronounce: I-square-C) is a slow serial bus protocol used in
- many micro controller applications and developed by Philips. SMBus,
- or System Management Bus is a subset of the I2C protocol. More
- information is contained in the directory Documentation/i2c/,
+ many micro controller applications and developed by Philips. SMBus,
+ or System Management Bus is a subset of the I2C protocol. More
+ information is contained in the directory <file:Documentation/i2c/>,
X especially in the file called "summary" there.
X
X Both I2C and SMBus are supported here. You will need this for
- hardware sensors support, and also for Video for Linux support.
+ hardware sensors support, and also for Video For Linux support.
X Specifically, if you want to use a BT848 based frame grabber/overlay
X boards under Linux, say Y here and also to "I2C bit-banging
X interfaces", below.
X
X If you want I2C support, you should say Y here and also to the
- specific driver for your bus adapter(s) below. If you say Y to
+ specific driver for your bus adapter(s) below. If you say Y to
X "/proc file system" below, you will then get a /proc interface which
- is documented in Documentation/i2c/proc-interface.
+ is documented in <file:Documentation/i2c/proc-interface>.
X
- This I2C support is also available as a module. If you want to
+ This I2C support is also available as a module. If you want to

X compile it as a module, say M here and read

- Documentation/modules.txt. The module will be called i2c-core.o.
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-core.o.
+
+UltraSPARC-III bootbus i2c controller driver
+CONFIG_BBC_I2C
+ The BBC devices on the UltraSPARC III have two I2C controllers. The
+ first I2C controller connects mainly to configuration PROMs (NVRAM,
+ CPU configuration, DIMM types, etc.). The second I2C controller
+ connects to environmental control devices such as fans and
+ temperature sensors. The second controller also connects to the
+ smartcard reader, if present. Say Y to enable support for these.
X
X I2C bit-banging interfaces
X CONFIG_I2C_ALGOBIT
X This allows you to use a range of I2C adapters called bit-banging
- adapters. Say Y if you own an I2C adapter belonging to this class
+ adapters. Say Y if you own an I2C adapter belonging to this class
X and then say Y to the specific driver for you adapter below.
X
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-algo-bit.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-algo-bit.o.
X
X Philips style parallel port adapter
X CONFIG_I2C_PHILIPSPAR
- This supports parallel-port I2C adapters made by Philips. Say Y if
+ This supports parallel-port I2C adapters made by Philips. Say Y if
X you own such an adapter.
X
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-philips-par.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-philips-par.o.
X
X Note that if you want support for different parallel port devices,
X life will be much easier if you compile them all as modules.
X
X ELV adapter
X CONFIG_I2C_ELV
- This supports parallel-port I2C adapters called ELV. Say Y if you
+ This supports parallel-port I2C adapters called ELV. Say Y if you
X own such an adapter.
X
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-elv.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-elv.o.
X
X Velleman K9000 adapter
X CONFIG_I2C_VELLEMAN
- This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
- you own such an adapter.
+ This supports the Velleman K9000 parallel-port I2C adapter. Say Y
+ if you own such an adapter.
X
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-velleman.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-velleman.o.
X
X I2C PCF 8584 interfaces
X CONFIG_I2C_ALGOPCF
@@ -14038,29 +16163,41 @@
X Say Y if you own an I2C adapter belonging to this class and then say
X Y to the specific driver for you adapter below.
X
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-algo-pcf.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-algo-pcf.o.
X
X Elektor ISA card
X CONFIG_I2C_ELEKTOR
- This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
- an adapter.
+ This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
+ such an adapter.
X
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-elektor.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-elektor.o.
X
X I2C device interface
X CONFIG_I2C_CHARDEV
X Say Y here to use i2c-* device files, usually found in the /dev
- directory on your system. They make it possible to have user-space
- programs use the I2C bus. Information on how to do this is contained
- in the file Documentation/i2c/dev-interface.
+ directory on your system. They make it possible to have user-space
+ programs use the I2C bus. Information on how to do this is
+ contained in the file <file:Documentation/i2c/dev-interface>.
+
+ This code is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-dev.o.
+
+I2C /proc support
+CONFIG_I2C_PROC
+ This provides support for i2c device entries in the /proc filesystem.
+ The entries will be found in /proc/sys/dev/sensors.
X
X This code is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 013'
echo 'File patch-2.4.15 is continued in part 014'
echo "014" > _shar_seq_.tmp
exit 0

Thomas Kobienia

unread,

Nov 24, 2001, 3:58:50 AM11/24/01

Archive-name: v2.4/patch-2.4.15/part014

#!/bin/sh -x
# this is part 014 of a 115 - part archive

# do not concatenate these parts, unpack them in order with /bin/sh
# file patch-2.4.15 continued
if test ! -r _shar_seq_.tmp; then
echo 'Please unpack part 1 first!'
exit 1
fi
(read Scheck

if test "$Scheck" != 014; then

- module will be called i2c-dev.o.
+ it as a module, say M here and read <file:Documentation/modules.txt>.
+ The module will be called i2c-proc.o.
X
X Bus Mouse Support
X CONFIG_BUSMOUSE
@@ -14069,11 +16206,11 @@
X Microsoft mouse (made by Logitech) that plugs into a COM port
X (rectangular with 9 or 25 pins). These people say N here. If you
X have something else, read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , and say Y here.
+ <http://www.linuxdoc.org/docs.html#howto>, and say Y here.
X
X If you have a laptop, you either have to check the documentation or
X experiment a bit to find out whether the trackball is a serial mouse
- or not; it's best to say Y here for you.
+ or not; it's best to say Y here for you.
X
X This is the generic bus mouse driver code. If you have a bus mouse,
X you will have to say Y here and also to the specific driver for your
@@ -14082,7 +16219,7 @@
X This code is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called busmouse.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>.
X
X Mouse Support (not serial and bus mice)
X CONFIG_MOUSE
@@ -14092,30 +16229,30 @@
X MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
X COM port (rectangular with 9 or 25 pins). These people say N here.
X If you have something else, read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
+ <http://www.linuxdoc.org/docs.html#howto>. This HOWTO contains
X information about all non-serial mice, not just bus mice.
X
X If you have a laptop, you either have to check the documentation or
X experiment a bit to find out whether the trackball is a serial mouse
- or not; it's best to say Y here for you.
+ or not; it's best to say Y here for you.

X
X Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all

+ kernel: saying N will just cause the configurator to skip all

X the questions about non-serial mice. If unsure, say Y.
X
X Logitech busmouse support
X CONFIG_LOGIBUSMOUSE
- Logitech mouse connected to a proprietary interface card. It's
+ Logitech mouse connected to a proprietary interface card. It's
X generally a round connector with 9 pins. Note that the newer mice
X made by Logitech don't use the Logitech protocol anymore; for those,
- you don't need this option. You want to read the Busmouse-HOWTO ,
- available from http://www.linuxdoc.org/docs.html#howto .
+ you don't need this option. You want to read the Busmouse-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X

- called busmouse.o. If you are unsure, say N and read the HOWTO
- nevertheless: it will tell you what you have.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called busmouse.o. If you are unsure, say N and read the
+ HOWTO nevertheless: it will tell you what you have.
X
X PS/2 mouse (aka "auxiliary device") support
X CONFIG_PSMOUSE
@@ -14129,12 +16266,12 @@
X
X Although PS/2 mice are not technically bus mice, they are explained
X in detail in the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X When using a PS/2 mouse, you can get problems if you want to use the
X mouse both on the Linux console and under X. Using the "-R" option
X of the Linux mouse managing program gpm (available from
- ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
+ <ftp://metalab.unc.edu/pub/Linux/system/mouse>) solves this
X problem, or you can get the "mconv2" utility from the same location.
X
X C&T 82C710 mouse port support (as on TI Travelmate)
@@ -14142,25 +16279,25 @@
X This is a certain kind of PS/2 mouse used on the TI Travelmate. If
X you are unsure, try first to say N here and come back if the mouse
X doesn't work. Read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X PC110 digitizer pad support
X CONFIG_PC110_PAD
- This drives the digitizer pad on the IBM PC110 palmtop. It can turn
+ This drives the digitizer pad on the IBM PC110 palmtop. It can turn
X the digitizer pad into a PS/2 mouse emulation with tap gestures or
X into an absolute pad.

- called pc110pad.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called pc110pad.o.
X
X Microsoft busmouse support
X CONFIG_MS_BUSMOUSE
X These animals (also called Inport mice) are connected to an
X expansion board using a round connector with 9 pins. If this is what
X you have, say Y and read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X If you are unsure, say N and read the HOWTO nevertheless: it will
X tell you what you have. Also be aware that several vendors talk
@@ -14169,41 +16306,33 @@
X

- called msbusmouse.o.
-
-Apple Desktop Bus support
-CONFIG_ADB
- Apple Desktop Bus (ADB) support is for support of devices which
- are connected to an ADB port. ADB devices tend to have 4 pins.
- If you have an Apple Macintosh prior to the iMac, or a
- "Blue and White G3", you probably want to say Y here. Otherwise
- say N.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called msbusmouse.o.
X
X Apple Desktop Bus mouse support
X CONFIG_ADBMOUSE
X Say Y here if you have this type of bus mouse (4 pin connector) as
- is common on Macintoshes. You may want to read the Busmouse-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ is common on Macintoshes. You may want to read the Busmouse-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
X

- called adbmouse.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called adbmouse.o.
X
X ATIXL busmouse support
X CONFIG_ATIXL_BUSMOUSE
X This is a rare type of busmouse that is connected to the back of an
- ATI video card. Say Y if you have one of those. Note however that
+ ATI video card. Say Y if you have one of those. Note however that
X most mice by ATI are actually Microsoft busmice; you should say Y to
- "Microsoft busmouse support" above if you have one of those. Read
+ "Microsoft busmouse support" above if you have one of those. Read
X the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .

+ <http://www.linuxdoc.org/docs.html#howto>.
X

- called atixlmouse.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called atixlmouse.o.
X
X If you are unsure, say N and read the HOWTO nevertheless: it will
X tell you what you have.
@@ -14213,29 +16342,34 @@
X If you have a non-SCSI tape drive like that, say Y. Or, if you want
X to compile this driver as a module ( = code which can be inserted in

X and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called

+ and read <file:Documentation/modules.txt>. The module will be called
X tpqic02.o.
X
+iSeries Virtual Tape Support
+CONFIG_VIOTAPE
+ If you are running Linux on an iSeries system and you want Linux
+ to read and/or write a tape drive owned by OS/400, say Y here.
+
X Do you want runtime configuration for QIC-02
X CONFIG_QIC02_DYNCONF
X You can either configure this driver once and for all by editing a
- header file (include/linux/tpqic02.h), in which case you should
- say N, or you can fetch a program via anonymous FTP which is able
- to configure this driver during runtime. The program to do this is
- called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
- support package.
+ header file (<file:include/linux/tpqic02.h>), in which case you
+ should say N, or you can fetch a program via anonymous FTP which is
+ able to configure this driver during runtime. The program to do
+ this is called 'qic02conf' and it is part of the
+ tpqic02-support-X.Y.tar.gz support package.
X
X If you want to use the qic02conf program, say Y.
X
X Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
X CONFIG_FTAPE
X If you have a tape drive that is connected to your floppy
- controller, say Y here.
+ controller, say Y here.
X
X Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
X "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
X controller of their own. These drives (and their companion
- controllers) are also supported if you say Y here.
+ controllers) are also supported if you say Y here.
X
X If you have a special controller (such as the CMS FC-10, FC-20,
X Mountain Mach-II, or any controller that is based on the Intel 82078
@@ -14243,56 +16377,57 @@
X Iomega's "Ditto Dash") you must configure it by selecting the
X appropriate entries from the "Floppy tape controllers" sub-menu
X below and possibly modify the default values for the IRQ and DMA
- channel and the IO base in ftape's configuration menu.
+ channel and the IO base in ftape's configuration menu.
X
X If you want to use your floppy tape drive on a PCI-bus based system,
- please read the file drivers/char/ftape/README.PCI.
+ please read the file <file:drivers/char/ftape/README.PCI>.
X
X The ftape kernel driver is also available as a runtime loadable
X module ( = code which can be inserted in and removed from the
X running kernel whenever you want). If you want to compile it as a
- module, say M here and read Documentation/modules.txt. The module
- will be called ftape.o.
+ module, say M here and read <file:Documentation/modules.txt>. The
+ module will be called ftape.o.
X
X Note that the Ftape-HOWTO is out of date (sorry) and documents the
X 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
+ information. There is a web page with more recent documentation at
+ <http://www.math1.rwth-aachen.de/~heine/ftape/>. This page
X always contains the latest release of the ftape driver and useful
X information (backup software, ftape related patches and
- documentation, FAQ). Note that the file system interface has changed
- quite a bit compared to previous versions of ftape. Please read
- Documentation/ftape.txt.
+ documentation, FAQ). Note that the file system interface has
+ changed quite a bit compared to previous versions of ftape. Please
+ read <file:Documentation/ftape.txt>.
X
-The file system interface for ftape
+VFS interface for ftape
X CONFIG_ZFTAPE
X Normally, you want to say Y or M. DON'T say N here or you
X WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
X
X The ftape module itself no longer contains the routines necessary
X to interface with the kernel VFS layer (i.e. to actually write data
- to and read data from the tape drive). Instead the file system
+ to and read data from the tape drive). Instead the file system
X interface (i.e. the hardware independent part of the driver) has
X been moved to a separate module.
X
X If you say M zftape will be compiled as a runtime loadable
X module ( = code which can be inserted in and removed from the
- running kernel whenever you want). In this case you should read
- Documentation/modules.txt. The module will be called zftape.o.
+ running kernel whenever you want). In this case you should read

+ <file:Documentation/modules.txt>. The module will be called

+ zftape.o.
X
X Regardless of whether you say Y or M here, an additional runtime
X loadable module called `zft-compressor.o' which contains code to
X support user transparent on-the-fly compression based on Ross
- William's lzrw3 algorithm will be produced. If you have enabled the
+ William's lzrw3 algorithm will be produced. If you have enabled the
X kernel module loader (i.e. have said Y to "Kernel module loader
X support", above) then `zft-compressor.o' will be loaded
X automatically by zftape when needed.
X
- Despite its name, zftape does NOT use compression by default. The
- 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
+ Despite its name, zftape does NOT use compression by default. The
+ 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
X further information.
X
X IMPORTANT NOTE: zftape can read archives created by previous
@@ -14331,7 +16466,7 @@
X wastes 32 KB of memory. Please note that this memory cannot be
X swapped out.
X
-Procfs entry for ftape
+Enable procfs status report (+2kb)
X CONFIG_FT_PROC_FS
X Optional. Saying Y will result in creation of a directory
X `/proc/ftape' under the /proc file system. The files can be viewed
@@ -14348,6 +16483,7 @@
X interface. Accessing `/proc/ftape' while the module is unloaded will
X result in a kernel Oops. This cannot be fixed from inside ftape.
X
+# Choice: ftdebug
X Controlling the amount of debugging output of ftape
X CONFIG_FT_NORMAL_DEBUG
X This option controls the amount of debugging output the ftape driver
@@ -14369,9 +16505,22 @@
X printed to the console but only makes it possible to produce
X "Excessive" debugging output.
X
- Please read Documentation/ftape.txt for a short description
+ Please read <file:Documentation/ftape.txt> for a short description
X how to control the amount of debugging output.
X
+Excessive
+CONFIG_FT_FULL_DEBUG
+ Extremely verbose output for driver debugging purposes.
+
+Reduced
+CONFIG_FT_NO_TRACE
+ Reduced tape driver debugging output.
+
+None
+CONFIG_FT_NO_TRACE_AT_ALL
+ Suppress all debugging output from the tape drive.
+
+# Choice: ftcontroller
X The floppy drive controller for ftape
X CONFIG_FT_STD_FDC
X Only change this setting if you have a special controller. If you
@@ -14407,13 +16556,13 @@
X have said Y to "Floppy tape drive") or module load time (i.e. if you
X have said M to "Floppy tape drive").
X
- Please read also the file Documentation/ftape.txt which
+ Please read also the file <file:Documentation/ftape.txt> which
X contains a short description of the parameters that can be set at
X boot or load time. If you want to use your floppy tape drive on a
X PCI-bus based system, please read the file
- drivers/char/ftape/README.PCI.
+ <file:drivers/char/ftape/README.PCI>.
X
-IO base of the floppy disk controller used with Ftape
+IO base for the floppy disk controller used with Ftape
X CONFIG_FT_FDC_BASE
X You don't need to specify a value if the following default
X settings for the base IO address are correct:
@@ -14435,9 +16584,9 @@
X "Floppy tape drive") or module load time (i.e. if you have said M to
X "Floppy tape drive").
X
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
X
X IRQ channel for the floppy disk controller used with Ftape
X CONFIG_FT_FDC_IRQ
@@ -14461,9 +16610,9 @@
X "Floppy tape drive") or module load time (i.e. if you said M to
X "Floppy tape drive").
X
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
X
X DMA channel for the floppy disk controller used with Ftape
X CONFIG_FT_FDC_DMA
@@ -14487,9 +16636,9 @@
X "Floppy tape drive") or module load time (i.e. if you said M to
X "Floppy tape drive").
X
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
X
X FDC FIFO Threshold before requesting DMA service
X CONFIG_FT_FDC_THR
@@ -14521,10 +16670,16 @@
X introduced in XFree86 4.0. If you say Y here, you need to select
X the module that's right for your graphics card from the list below.
X 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
X details. You should also select and configure AGP
X (/dev/agpgart) support.
X
+Build drivers for new (XFree 4.1) DRM
+CONFIG_DRM_NEW
+ If you set this option, the new DRM version needed by XFree86 4.1
+ will be used. Otherwise, the old DRM version will be used,
+ appropriate for XFree86 4.0.
+
X 3dfx Banshee/Voodoo3+
X CONFIG_DRM_TDFX
X Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
@@ -14541,19 +16696,69 @@
X is selected, the module will be called r128.o. AGP support for
X this card is strongly suggested (unless you have a PCI version).
X
+ATI Radeon
+CONFIG_DRM_RADEON
+ Choose this option if you have an ATI Radeon graphics card. There
+ are both PCI and AGP versions. You don't need to choose this to
+ run the Radeon in plain VGA mode. There is a product page at
+ <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+ If M is selected, the module will be called radeon.o.
+
X Intel I810
X CONFIG_DRM_I810
X Choose this option if you have an Intel I810 graphics card. If M is
X selected, the module will be called i810.o. AGP support is required
X for this driver to work.
X
-Matrox g200/g400
+Matrox G200/G400/G450
X CONFIG_DRM_MGA
- Choose this option if you have a Matrox g200 or g400 graphics card. If M
- is selected, the module will be called mga.o. AGP support is required
+ Choose this option if you have a Matrox G200, G400 or G450 graphics
+ card. If M is selected, the module will be called mga.o. AGP
+ support is required for this driver to work.
+
+3dfx Banshee/Voodoo3+
+CONFIG_DRM40_TDFX
+ Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
+ graphics card. If M is selected, the module will be called tdfx.o.
+
+3dlabs GMX 2000
+CONFIG_DRM40_GAMMA
+ Choose this option if you have a 3dlabs GMX 2000 graphics card.
+ If M is selected, the module will be called gamma.o.
+
+ATI Rage 128
+CONFIG_DRM40_R128
+ Choose this option if you have an ATI Rage 128 graphics card. If M
+ is selected, the module will be called r128.o. AGP support for
+ this card is strongly suggested (unless you have a PCI version).
+
+ATI Radeon
+CONFIG_DRM40_RADEON
+ Choose this option if you have an ATI Radeon graphics card. There
+ are both PCI and AGP versions. You don't need to choose this to
+ run the Radeon in plain VGA mode. There is a product page at
+ <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+ If M is selected, the module will be called radeon.o.
+
+Intel I810
+CONFIG_DRM40_I810
+ Choose this option if you have an Intel I810 graphics card. If M is
+ selected, the module will be called i810.o. AGP support is required
X for this driver to work.
X
-MTRR control and configuration
+Matrox G200/G400/G450
+CONFIG_DRM40_MGA
+ Choose this option if you have a Matrox G200, G400 or G450 graphics
+ card. If M is selected, the module will be called mga.o. AGP
+ support is required for this driver to work.
+
+Creator/Creator3D/Elite3D
+CONFIG_DRM_FFB
+ Choose this option if you have one of Sun's Creator3D-based graphics
+ and frame buffer cards. Product page at
+ <http://www.sun.com/desktop/products/Graphics/creator3d.html>.
+
+MTRR (Memory Type Range Register) support
X CONFIG_MTRR
X On Intel P6 family processors (Pentium Pro, Pentium II and later)
X the Memory Type Range Registers (MTRRs) may be used to control
@@ -14563,10 +16768,10 @@
X before bursting over the PCI/AGP bus. This can increase performance
X of image write operations 2.5 times or more. Saying Y here creates a
X /proc/mtrr file which may be used to manipulate your processor's
- MTRRs. Typically the X server should use this.
+ MTRRs. Typically the X server should use this.
X
- This code has a reasonably generic interface so that similar
- control registers on other processors can be easily supported
+ This code has a reasonably generic interface so that similar
+ control registers on other processors can be easily supported
X as well:
X
X The Cyrix 6x86, 6x86MX and M II processors have Address Range
@@ -14584,9 +16789,9 @@
X You can safely say Y even if your machine doesn't have MTRRs, you'll
X just add about 9 KB to your kernel.
X
- See Documentation/mtrr.txt for more information.
+ See <file:Documentation/mtrr.txt> for more information.
X
-Main CPU frequency, only for DEC alpha machine
+CPU clock frequency of your DEC Alpha
X CONFIG_FT_ALPHA_CLOCK
X On some DEC Alpha machines the CPU clock frequency cannot be
X determined automatically, so you need to specify it here ONLY if
@@ -14595,11 +16800,11 @@
X Double Talk PC internal speech card support
X CONFIG_DTLK
X This driver is for the DoubleTalk PC, a speech synthesizer
- manufactured by RC Systems (http://www.rcsys.com/ ). It is also
+ manufactured by RC Systems (<http://www.rcsys.com/>). It is also
X called the `internal DoubleTalk'. If you want to compile this as a
X module ( = code which can be inserted in and removed from the
X running kernel whenever you want), say M here and read
- Documentation/modules.txt. The module will be called dtlk.o.
+ <file:Documentation/modules.txt>. The module will be called dtlk.o.
X
X Siemens R3964 serial protocol support
X CONFIG_R3964
@@ -14609,7 +16814,7 @@

X
X To compile this driver as a module ( = code which can be inserted in
X and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called

+ and read <file:Documentation/modules.txt>. The module will be called
X n_r3964.o.

X
X If unsure, say N.

@@ -14619,28 +16824,28 @@
X This driver provides the kernel-side support for the intelligent
X fieldbus cards made by Applicom International. More information
X about these cards can be found on the WWW at the address
- http://www.applicom-int.com/ , or by email from David Woodhouse
+ <http://www.applicom-int.com/>, or by email from David Woodhouse
X <dw...@infradead.org>.

+ and read <file:Documentation/modules.txt>. The module will be called
X applicom.o.

X
X If unsure, say N.
X

X Sony Vaio Programmable I/O Control Device support
X CONFIG_SONYPI
- This driver enables access to the Sony Programmable I/O Control Device
- which can be found in many (all ?) Sony Vaio laptops.
+ This driver enables access to the Sony Programmable I/O Control
+ Device which can be found in many (all ?) Sony Vaio laptops.
X
- If you have one of those laptops, read Documentation/sonypi.txt,
- and say Y or M here.
+ If you have one of those laptops, read
+ <file:Documentation/sonypi.txt>, and say Y or M here.
X
X If you want to compile the driver as a module ( = code which can be

X 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 sonypi.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called sonypi.o.
X
X Intel Random Number Generator support
X CONFIG_INTEL_RNG
@@ -14653,7 +16858,7 @@

+ and read <file:Documentation/modules.txt>. The module will be called
X i810_rng.o.

X
X If unsure, say N.

@@ -14662,50 +16867,76 @@
X CONFIG_PM
X "Power Management" means that parts of your computer are shut
X off or put into a power conserving "sleep" mode if they are not
- being used. There are two competing standards for doing this: APM
- and ACPI. If you want to use either one, say Y here and then also to
- the requisite support below.
+ being used. There are two competing standards for doing this: APM
+ and ACPI. If you want to use either one, say Y here and then also
+ to the requisite support below.
X
X Power Management is most important for battery powered laptop
X computers; if you have a laptop, check out the Linux Laptop home
X page on the WWW at
- http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
- Powered Linux mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.cs.utexas.edu/users/kharker/linux-laptop/> and the
+ Battery Powered Linux mini-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X Note that, even if you say N here, Linux on the x86 architecture
X will issue the hlt instruction if nothing is to be done, thereby
X sending the processor to sleep and saving power.
X
+USB SE401 Camera support
+CONFIG_USB_SE401
+ Say Y here if you want to connect this type of camera to your
+ computer's USB port. See <file:Documentation/usb/se401.txt> for more
+ information and for a list of supported cameras.
+
+ This driver uses the Video For Linux API. You must say Y or M to
+ "Video For Linux" (under Multimedia Devices) to use this driver.
+ Information on this API and pointers to "v4l" programs may be found
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ This code is also available as a module ( = code which can be

+ inserted in and removed from the running kernel whenever you want).

+ The module will be called se401.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
X ACPI support
X CONFIG_ACPI
- ACPI/OSPM support for Linux is currently under development. As such,
- this support is preliminary and EXPERIMENTAL. Configuring ACPI support
- enables kernel interfaces that allow higher level software (OSPM) to
- manipulate ACPI defined hardware and software interfaces, including
- the evaluation of ACPI control methods. If unsure, choose N here.
- Note, this option will enlarge your kernel by about 120K.
+ ACPI/OSPM support for Linux is currently under development. As such,
+ this support is preliminary and EXPERIMENTAL. Configuring ACPI
+ support enables kernel interfaces that allow higher level software
+ (OSPM) to manipulate ACPI defined hardware and software interfaces,
+ including the evaluation of ACPI control methods. If unsure, choose
+ N here. Note, this option will enlarge your kernel by about 120K.
X
X This support requires an ACPI compliant platform (hardware/firmware).
X If both ACPI and Advanced Power Management (APM) support are
X configured, whichever is loaded first shall be used.
X
- This code DOES NOT currently provide a complete OSPM implementation --
- it has not yet reached APM's level of functionality. When fully
+ This code DOES NOT currently provide a complete OSPM implementation
+ -- it has not yet reached APM's level of functionality. When fully
X implemented, Linux ACPI/OSPM will provide a more robust functional
- replacement for legacy configuration and power management interfaces,
- including the Plug-and-Play BIOS specification (PNP BIOS), the Multi-
- Processor Specification (MPS), and the Advanced Power Management
- specification (APM).
+ replacement for legacy configuration and power management
+ interfaces, including the Plug-and-Play BIOS specification (PnP
+ BIOS), the Multi-Processor Specification (MPS), and the Advanced
+ Power Management specification (APM).
X
X Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
X Component Architecture (ACPI CA). The latest ACPI CA source code,
X documentation, debug builds, and implementation status information
X can be downloaded from:
- http://developer.intel.com/technology/iapc/acpi/downloads.htm
-
+ <http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
+
X The ACPI mailing list may also be of interest:
- http://phobos.fs.tum.de/acpi/index.html
+ <http://phobos.fs.tum.de/acpi/index.html>.
+
+Enable ACPI 2.0 with errata 1.3
+CONFIG_ACPI20
+ Enable support for the 2.0 version of the ACPI interpreter. See the
+ help for ACPI for caveats and discussion.
+
+ACPI kernel configuration manager
+CONFIG_ACPI_KERNEL_CONFIG
+ If you say `Y' here, Linux's ACPI support will use the
+ hardware-level system descriptions found on IA64 machines.
X
X ACPI Debug Statements
X CONFIG_ACPI_DEBUG
@@ -14716,37 +16947,39 @@
X ACPI Bus Manager
X CONFIG_ACPI_BUSMGR
X The ACPI Bus Manager enumerates devices in the ACPI namespace, and
- handles PnP messages. All ACPI devices use its services, so using them
- requires saying Y here.
+ handles PnP messages. All ACPI devices use its services, so using
+ them requires saying Y here.
X
X ACPI System Driver
X CONFIG_ACPI_SYS
- This driver will enable your system to shut down using ACPI, and dump
- your ACPI DSDT table using /proc/acpi/dsdt.
+ This driver will enable your system to shut down using ACPI, and
+ dump your ACPI DSDT table using /proc/acpi/dsdt.
X
X ACPI Processor Driver
X CONFIG_ACPI_CPU
- This driver installs ACPI as the idle handler for Linux, and uses ACPI
- C2 and C3 processor states to save power, on systems that support it.
+ This driver installs ACPI as the idle handler for Linux, and uses
+ ACPI C2 and C3 processor states to save power, on systems that
+ support it.
X
X ACPI Button
X CONFIG_ACPI_BUTTON
- This driver registers for events based on buttons, such as the power,
- sleep, and lid switch. In the future, a daemon will read
+ This driver registers for events based on buttons, such as the
+ power, sleep, and lid switch. In the future, a daemon will read
X /proc/acpi/event and perform user-defined actions such as shutting
- down the system. Until then, you can cat it, and see output when
+ down the system. Until then, you can cat it, and see output when
X a button is pressed.
X
X ACPI AC Adapter
X CONFIG_ACPI_AC
X This driver adds support for the AC Adapter object, which indicates
- whether a system is on AC, or not. Typically, only laptops have this
- object, since desktops are always on AC.
+ whether a system is on AC, or not. Typically, only laptops have
+ this object, since desktops are always on AC.
X
X ACPI Embedded Controller
X CONFIG_ACPI_EC
- This driver is required on some systems for the proper operation of the
- battery and thermal drivers. If you are compiling for a laptop, say Y.
+ This driver is required on some systems for the proper operation of
+ the battery and thermal drivers. If you are compiling for a laptop,
+ say Y.
X
X ACPI Control Method Battery
X CONFIG_ACPI_CMBATT
@@ -14774,13 +17007,13 @@
X machines with more than one CPU.
X
X In order to use APM, you will need supporting software. For location
- and more information, read Documentation/pm.txt and the Battery
- Powered Linux mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ and more information, read <file:Documentation/pm.txt> and the
+ Battery Powered Linux mini-HOWTO, available from

+ <http://www.linuxdoc.org/docs.html#howto>.
X

X This driver does not spin down disk drives (see the hdparm(8)
X manpage ("man 8 hdparm") for that), and it doesn't turn off
- VESA-compliant "green" monitors.
+ VESA-compliant "green" monitors.
X
X This driver does not support the TI 4000M TravelMate and the ACER
X 486/DX4/75 because they don't have compliant BIOSes. Many "green"
@@ -14791,30 +17024,30 @@
X much point in using this driver and you should say N. If you get
X random kernel OOPSes or reboots that don't seem to be related to
X anything, try disabling/enabling this option (or disabling/enabling
- APM in your BIOS).
+ APM in your BIOS).
X
X Some other things you should try when experiencing seemingly random,
X "weird" problems:
X
X 1) make sure that you have enough swap space and that it is
- enabled.
- 2) pass the "no-hlt" option to the kernel
+ enabled.
+ 2) pass the "no-hlt" option to the kernel
X 3) switch on floating point emulation in the kernel and pass
X the "no387" option to the kernel
X 4) pass the "floppy=nodma" option to the kernel
- 5) pass the "mem=4M" option to the kernel (thereby disabling
+ 5) pass the "mem=4M" option to the kernel (thereby disabling
X all but the first 4 MB of RAM)
X 6) make sure that the CPU is not over clocked.
- 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
+ 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
X 8) disable the cache from your BIOS settings
X 9) install a fan for the video card or exchange video RAM
X 10) install a better fan for the CPU
- 11) exchange RAM chips
+ 11) exchange RAM chips
X 12) exchange the motherboard.

+ and read <file:Documentation/modules.txt>. The module will be called
X apm.o.
X
X Ignore USER SUSPEND
@@ -14839,7 +17072,7 @@
X T400CDT. This is off by default since most machines do fine without
X this feature.
X
-Do CPU IDLE calls
+Make CPU Idle calls when idle
X CONFIG_APM_CPU_IDLE
X Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
X On some machines, this can activate improved power savings, such as
@@ -14887,7 +17120,7 @@
X a work-around for a number of buggy BIOSes. Switch this option on if
X your computer crashes instead of powering off properly.
X
-Watchdog Timer Support
+Watchdog Timer Support
X CONFIG_WATCHDOG
X If you say Y here (and to one of the following options) and create a
X character special file /dev/watchdog with major number 10 and minor
@@ -14899,12 +17132,12 @@
X implementation entirely in software (which can sometimes fail to
X reboot the machine) and a driver for hardware watchdog boards, which
X are more robust and can also keep track of the temperature inside
- your computer. For details, read Documentation/watchdog.txt in the
- kernel source.
+ your computer. For details, read <file:Documentation/watchdog.txt>
+ in the kernel source.
X
- The watchdog is usually used together with the watchdog daemon
+ The watchdog is usually used together with the watchdog daemon
X which is available via FTP (user: anonymous) from
- ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
+ <ftp://tsx-11.mit.edu/pub/linux/sources/sbin/>. This daemon can also
X monitor NFS connections and can reboot the machine when the process
X table is full.
X
@@ -14929,22 +17162,22 @@
X

- called wdt.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called wdt.o.
X
X WDT PCI Watchdog timer
X CONFIG_WDTPCI
- If you have a PCI WDT500/501 watchdog board, say Y here,
- otherwise N. It is not possible to probe for this board, which means
- that you have to inform the kernel about the IO port and IRQ using
- the "wdt=" kernel option (try "man bootparam" or see the
- documentation of your boot loader (lilo or loadlin) about how to
- pass options to the kernel at boot time).
+ If you have a PCI WDT500/501 watchdog board, say Y here, otherwise
+ N. It is not possible to probe for this board, which means that you
+ have to inform the kernel about the IO port and IRQ using the "wdt="
+ kernel option (try "man bootparam" or see the documentation of your
+ boot loader (lilo or loadlin) about how to pass options to the
+ kernel at boot time).

- called wdt_pci.o.

+ say M here and read <file:Documentation/modules.txt>. The module

+ will be called wdt_pci.o.
X
X WDT501 features
X CONFIG_WDT_501
@@ -14964,12 +17197,13 @@
X CONFIG_SOFT_WATCHDOG
X A software monitoring watchdog. This will fail to reboot your system
X from some situations that the hardware watchdog will recover
- from. Equally it's a lot cheaper to install.
+ from. Equally it's a lot cheaper to install.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called softdog.o.

+ <file:Documentation/modules.txt>. The module will be called

+ softdog.o.
X
X Berkshire Products PC Watchdog
X CONFIG_PCWATCHDOG
@@ -14977,55 +17211,90 @@
X This card simply watches your kernel to make sure it doesn't freeze,
X and if it does, it reboots your computer after a certain amount of
X time. This driver is like the WDT501 driver but for different
- hardware. Please read Documentation/pcwd-watchdog.txt. The PC
- watchdog cards can be ordered from http://www.berkprod.com .
+ hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC
+ watchdog cards can be ordered from <http://www.berkprod.com>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module is called pcwd.o. If you want to compile it as a module,

- say M here and read Documentation/modules.txt.

+ say M here and read <file:Documentation/modules.txt>.

X
X Most people will say N.
X
X Acquire SBC Watchdog Timer
X CONFIG_ACQUIRE_WDT
X This is the driver for the hardware watchdog on the PSC-6x86 Single
- Board Computer produced by Acquire Inc (and others). This watchdog
+ Board Computer produced by Acquire Inc (and others). This watchdog
X simply watches your kernel to make sure it doesn't freeze, and if
X it does, it reboots your computer after a certain amount of time.
X
X This driver is like the WDT501 driver but for different hardware.
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called pscwdt.o. If you want to compile it as a
+ The module is called pscwdt.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
+
+Advantech SBC Watchdog Timer
+CONFIG_ADVANTECH_WDT
+ If you are configuring a Linux kernel for the Advantech single-board
+ computer, say `Y' here to support its built-in watchdog timer
+ feature. See the help for CONFIG_WATCHDOG for discussion.
+
+W83877F Watchdog Timer
+CONFIG_W83877F_WDT
+ This is the driver for the hardware watchdog on the W83877F chipset
+ as used in EMACS PC-104 motherboards (and likely others). This
+ watchdog simply watches your kernel to make sure it doesn't freeze,
+ and if it does, it reboots your computer after a certain amount of
+ time.

+
+ 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 is called mixcomwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
+
+IB700 SBC Watchdog Timer
+CONFIG_IB700_WDT
+ This is the driver for the hardware watchdog on the IB700 Single
+ Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
+ simply watches your kernel to make sure it doesn't freeze, and if
+ it does, it reboots your computer after a certain amount of time.
+
+ This driver is like the WDT501 driver but for slightly different hardware.

+
+ 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 is called ib700wdt.o. If you want to compile it as a
X module, say M here and read Documentation/modules.txt. Most people
X will say N.
X
X Mixcom Watchdog
-CONFIG_MIXCOMWD
- This is a driver for the Mixcom hardware watchdog cards. This
+CONFIG_MIXCOMWD
+ This is a driver for the Mixcom hardware watchdog cards. This
X watchdog simply watches your kernel to make sure it doesn't freeze,
X and if it does, it reboots your computer after a certain amount of
X time.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called mixcomwd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. Most people
- will say N.
+ The module is called mixcomwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
X
X ZF MachZ Watchdog
X CONFIG_MACHZ_WDT
- If you are using a ZF Micro MachZ processor, say Y here, otherwise N.
- This is the driver for the watchdog timer builtin on that processor
- using ZF-Logic interface. This watchdog simply watches your kernel to
- make sure it doesn't freeze, and if it does, it reboots your computer
- after a certain amount of time.
+ If you are using a ZF Micro MachZ processor, say Y here, otherwise
+ N. This is the driver for the watchdog timer builtin on that
+ processor using ZF-Logic interface. This watchdog simply watches
+ your kernel to make sure it doesn't freeze, and if it does, it
+ reboots your computer after a certain amount of time.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module is called machzwd.o. If you want to compile it as a module,

- say M here and read Documentation/modules.txt.

+ The module is called machzwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X SuperH 3/4 Watchdog
X CONFIG_SH_WDT
@@ -15040,13 +17309,14 @@
X
X Toshiba Laptop support
X CONFIG_TOSHIBA
- This adds a driver to safely access the System Management Mode
- of the CPU on Toshiba portables. The System Management Mode
+ This adds a driver to safely access the System Management Mode of
+ the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
+ not work on models with a Pheonix BIOS. The System Management Mode
X is used to set the BIOS and power saving options on Toshiba portables.
X
X For information on utilities to make use of this driver see the
X Toshiba Linux utilities web site at:
- http://www.buzzard.org.uk/toshiba/
+ <http://www.buzzard.org.uk/toshiba/>.
X
X Say Y if you intend to run this kernel on a Toshiba portable.
X Say N otherwise.
@@ -15065,7 +17335,7 @@
X
X For information on utilities to make use of this driver see the
X I8K Linux utilities web site at:
- http://www.debian.org/~dz/i8k/
+ <http://www.debian.org/~dz/i8k/>
X
X Say Y if you intend to run this kernel on a Dell Inspiron 8000.
X Say N otherwise.
@@ -15075,18 +17345,19 @@
X If you say Y here and also to "/dev file system support" in the
X 'File systems' section, you will be able to update the microcode on
X Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
- Pentium III, Pentium 4, Xeon etc. You will obviously need the actual
- microcode binary data itself which is not shipped with the Linux kernel.
+ Pentium III, Pentium 4, Xeon etc. You will obviously need the
+ actual microcode binary data itself which is not shipped with the
+ Linux kernel.
X
X For latest news and information on obtaining all the required
X ingredients for this driver, check:
- http://www.urbanmyth.org/microcode/
+ <http://www.urbanmyth.org/microcode/>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called microcode.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If you use
- modprobe or kmod you may also want to add the line
+ The module will be called microcode.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ you use modprobe or kmod you may also want to add the line
X 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
X
X /dev/cpu/*/msr - Model-specific register support
@@ -15120,7 +17391,7 @@
X CONFIG_RTC
X If you say Y here and create a character special file /dev/rtc with
X major number 10 and minor number 135 using mknod ("man mknod"), you
- will get access to the real time clock (or hardware clock) built
+ will get access to the real time clock (or hardware clock) built
X into your computer.
X
X Every PC has such a clock built in. It can be used to generate
@@ -15134,23 +17405,19 @@
X and set the RTC in an SMP compatible fashion.
X
X If you think you have a use for such a device (such as periodic data
- sampling), then say Y here, and read Documentation/rtc.txt for
- details.
+ sampling), then say Y here, and read <file:Documentation/rtc.txt>
+ for details.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module is called rtc.o. If you want to compile it as a module,

- say M here and read Documentation/modules.txt.

-
-### Add
-#EFI Real Time Clock Services
-#CONFIG_EFI_RTC

+ say M here and read <file:Documentation/modules.txt>.

X
X Tadpole ANA H8 Support
X CONFIG_H8
X The Hitachi H8/337 is a microcontroller used to deal with the power
X and thermal environment. If you say Y here, you will be able to
- communicate with it via a character special device.
+ communicate with it via a character special device.

X
X If unsure, say N.
X

@@ -15160,7 +17427,7 @@
X with major number 10 and minor number 144 using mknod ("man mknod"),
X you get read and write access to the 50 bytes of non-volatile memory
X in the real time clock (RTC), which is contained in every PC and
- most Ataris.
+ most Ataris.
X
X This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
X on Ataris. /dev/nvram may be used to view settings there, or to
@@ -15177,8 +17444,9 @@
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

X The module will be called nvram.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>.
X
+# Linus tree only
X Joystick support
X CONFIG_JOYSTICK
X If you have a joystick, 6dof controller, gamepad, steering wheel,
@@ -15186,232 +17454,299 @@
X enable generic support for these controllers. You will also need to
X say Y or M to at least one of the hardware specific drivers. This
X will make the controllers available as /dev/input/jsX devices.
- Please read the file Documentation/joystick.txt which contains more
- information and the location of the joystick package that you'll
- need.
+ Please read the file <file:Documentation/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
+ contains more information and the location of the joystick package
+ that you'll need if you use the gameport with a joystick.

+
+ 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 gameport.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.

X
-ns558 gameports
+Classic ISA/PnP gameports
X CONFIG_INPUT_NS558
- Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
+ Say Y here if you have an ISA or PnP gameport.
X For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called ns558.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called ns558.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X PDPI Lightning 4 gamecard
X CONFIG_INPUT_LIGHTNING
X Say Y here if you have a PDPI Lightning 4 gamecard. For more
X information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called lightning.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called lightning.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.
+

+Crystal SoundFusion gameports
+CONFIG_INPUT_CS461X
+ Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion"
+ PCI audio accelerator. A product page for the CS4614 is at
+ <http://www.cirrus.com/design/products/overview/index.cfm?ProductID=40>.

+
+ 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 cs461x.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X Aureal Vortex and Trident 4DWave gameports
X CONFIG_INPUT_PCIGAME
X Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
X card. For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/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).

+ The module will be called pcigame.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
+SoundBlaster Live! gameports
+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>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called pcigame.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called emu10k1-gp.o. If you want to compile it as

+ a module, say M here and read <file:Documentation/modules.txt>.

X
X Classic PC analog joysticks and gamepads
X CONFIG_INPUT_ANALOG
X Say Y here if you have a controller that connects to the PC
- gameport. This supports many different types, including joysticks
+ gameport. This supports many different types, including joysticks
X with throttle control, with rudders, or with extensions like
X additional hats and buttons compatible with CH Flightstick Pro,
X ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
- joysticks. For more information on how to use the driver please read
- Documentation/joystick.txt
+ joysticks. For more information on how to use the driver please
+ read <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called analog.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called analog.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
-Assasin 3D and MadCatz Panther devices
+Assassin 3D and MadCatz Panther devices
X CONFIG_INPUT_A3D
X 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 Documentation/joystick.txt
+ A3D protocol over the PC gameport. For more information on how to
+ use the driver please read <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called a3d.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called a3d.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X Logitech ADI digital joysticks and gamepads
X CONFIG_INPUT_ADI
X Say Y here if you have a Logitech controller using the ADI
X protocol over the PC gameport. For more information on how to use
- the driver please read Documentation/joystick.txt
+ the driver please read <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called adi.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called adi.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X Creative Labs Blaster Cobra gamepad
X CONFIG_INPUT_COBRA
X Say Y here if you have a Creative Labs Blaster Cobra gamepad.
X For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called cobra.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called cobra.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X Genius Flight2000 Digital joysticks and gamepads
X 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 Documentation/joystick.txt
+ 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>.
X
X This driver is also available as a module ( = code which can be

X inserted in and removed from the running kernel whenever you want).

- The module will be called gf2k.o. If you want to compile

- it as a module, say M here and read Documentation/modules.txt.

+ The module will be called gf2k.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
X
X Gravis GrIP joysticks and gamepads
X CONFIG_INPUT_GRIP
X 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 Documentation/joystick.txt
+ over the PC gameport. For more information on how to use the driver

SHAR_EOF
true || echo 'restore of patch-2.4.15 failed'
fi

echo 'End of part 014'
echo 'File patch-2.4.15 is continued in part 015'
echo "015" > _shar_seq_.tmp
exit 0

0 new messages