Skip to content

L
linux
Commit 176c1451 authored by Linus Torvalds's avatar Linus Torvalds
Browse files
Options

Manual merge of Kconfig file module comments

parents 722c4748 77215b89
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 1492 additions and 2776 deletions
arch/arm/Kconfig
View file @ 176c1451
......@@ -532,10 +532,8 @@ config APM
11) exchange RAM chips
12) exchange the motherboard.
To compile this driver 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
apm.
To compile this driver as a module, choose M here: the
module will be called apm.
config ARTHUR
tristate "RISC OS personality"
......
arch/arm/mach-integrator/Kconfig
View file @ 176c1451
......@@ -8,9 +8,7 @@ config INTEGRATOR_IMPD1
allows ARM(R) Ltd PrimeCells to be developed and evaluated.
The IM-PD1 can be found on the Integrator/PP2 platform.
If you want to compile this as a module (=code which can be
inserted into and removed from the running kernel), say M
here and read <file:Documentation/modules.txt>. The module
will be called impd1.
To compile this driver as a module, choose M here: the
module will be called impd1.
endmenu
arch/i386/Kconfig
View file @ 176c1451
......@@ -595,11 +595,9 @@ config MICROCODE
ingredients for this driver, check:
<http://www.urbanmyth.org/microcode/>.
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 microcode. 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
To compile this driver as a module, choose M here: the
module will be called microcode.
If you use modprobe or kmod you may also want to add the line
'alias char-major-10-184 microcode' to your /etc/modules.conf file.
config X86_MSR
......@@ -909,10 +907,8 @@ config APM
11) exchange RAM chips
12) exchange the motherboard.
To compile this driver 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
apm.
To compile this driver as a module, choose M here: the
module will be called apm.
config APM_IGNORE_USER_SUSPEND
bool "Ignore USER SUSPEND"
......
arch/m68k/Kconfig
View file @ 176c1451
......@@ -67,11 +67,8 @@ config PCMCIA
for location). Please also read the PCMCIA-HOWTO, available from
<http://www.tldp.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).
When compiled this way, there will be modules called pcmcia_core
and ds. If you want to compile it as a module, say M here and
read <file:Documentation/modules.txt>.
To compile this driver as modules, choose M here: the
modules will be called pcmcia_core and ds.
config AMIGA
bool "Amiga support"
......@@ -425,13 +422,11 @@ config PARPORT
It is possible to share a single parallel port among several devices
and it is safe to compile all the corresponding drivers into the
kernel. If you want to compile parallel port support as a module
( = code which can be inserted in and removed from the running
kernel whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called
parport. If you have more than one parallel port and want to
specify which port and IRQ to be used by this driver at module load
time, take a look at <file:Documentation/parport.txt>.
kernel. To compile parallel port support as a module, choose M here:
the module will be called parport.
If you have more than one parallel port and want to specify which
port and IRQ to be used by this driver at module load time, take a
look at <file:Documentation/parport.txt>.
If unsure, say Y.
......@@ -460,11 +455,8 @@ config PARPORT_PC
PC compatible computers and some Alphas have PC-style parallel
ports.
This code is also available as a module. If you want to compile it
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
parport_pc.
To compile this driver as a module, choose M here: the
module will be called parport_pc.
If unsure, say Y.
......@@ -488,10 +480,8 @@ config PRINTER
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt> and
corresponding drivers into the kernel.
To compile this driver as a module, choose M here and read
<file:Documentation/parport.txt>. The module will be called lp.
If you have several parallel ports, you can specify which ports to
......@@ -571,9 +561,8 @@ config SERIAL
serial port drivers do not need this driver built in for them to
work.)
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
serial.
To compile this driver as a module, choose M here: the
module will be called serial.
[WARNING: Do not compile this driver as a module if you are using
non-standard serial ports, since the configuration information will
be lost when the driver is unloaded. This limitation may be lifted
......@@ -717,10 +706,8 @@ config NVRAM
On Atari machines, /dev/nvram is always configured and does not need
to be selected.
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 nvram. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called nvram.
config ATARI_MFPSER
tristate "Atari MFP serial support"
......@@ -730,10 +717,7 @@ config ATARI_MFPSER
Linux, say Y. The driver equally supports all kinds of MFP serial
ports and automatically detects whether Serial1 is available.
This driver is also available 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>.
To compile this driver as a module, choose M here.
Note for Falcon users: You also have an MFP port, it's just not
wired to the outside... But you could use the port under Linux.
......@@ -748,10 +732,7 @@ config ATARI_SCC
two connectors for channel A (Serial2 and LAN), they are visible as
two separate devices.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config ATARI_SCC_DMA
bool "Atari SCC serial DMA support"
......@@ -769,10 +750,7 @@ config ATARI_MIDI
help
If you want to use your Atari's MIDI port in Linux, say Y.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config ATARI_DSP56K
tristate "Atari DSP56k support (EXPERIMENTAL)"
......@@ -782,10 +760,7 @@ config ATARI_DSP56K
driver is still experimental, and if you don't know what it is, or
if you don't have this processor, just say N.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config AMIGA_BUILTIN_SERIAL
tristate "Amiga builtin serial support"
......@@ -794,10 +769,7 @@ config AMIGA_BUILTIN_SERIAL
If you want to use your Amiga's built-in serial port in Linux,
answer Y.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config WHIPPET_SERIAL
tristate "Hisoft Whippet PCMCIA serial support"
......@@ -813,10 +785,7 @@ config MULTIFACE_III_TTY
If you want to use a Multiface III card's serial port in Linux,
answer Y.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config A2232
tristate "Commodore A2232 serial support (EXPERIMENTAL)"
......@@ -832,8 +801,7 @@ config A2232
This driver can be built as a module; but then "generic_serial"
will also be built as a module. This has to be loaded before
"ser_a2232". If you want to do this, answer M here and read
"<file:Documentation/modules.txt>".
"ser_a2232". If you want to do this, answer M here.
config GVPIOEXT
tristate "GVP IO-Extender support"
......@@ -1086,11 +1054,8 @@ config SOFT_WATCHDOG
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
This driver is also available 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>. The module will be called
softdog.
To compile this driver as a module, choose M here: the
module will be called softdog.
config GEN_RTC
tristate "Generic /dev/rtc emulation" if !SUN3
......@@ -1107,12 +1072,9 @@ config GEN_RTC
for RTC_UIE which is required by some programs and may improve
precision in some cases.
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 genrtc. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>. To load the
module automatically add 'alias char-major-10-135 genrtc' to your
/etc/modules.conf
To compile this driver as a module, choose M here: the
module will be called genrtc. To load the module automatically
add 'alias char-major-10-135 genrtc' to your /etc/modules.conf
config GEN_RTC_X
bool "Extended RTC operation"
......
arch/mips/Kconfig
View file @ 176c1451
......@@ -1272,12 +1272,10 @@ config SOUND
If you have a PnP sound card and you want to configure it at boot
time using the ISA PnP tools (read
<http://www.roestock.demon.co.uk/isapnptools/>), then you need to
compile the sound card support as a module ( = code which can be
inserted in and removed from the running kernel whenever you want)
and load that module after the PnP configuration is finished. To do
this, say M here and read <file:Documentation/modules.txt> as well
as <file:Documentation/sound/README.modules>; the module will be
called soundcore.
compile the sound card support as a module and load that module
after the PnP configuration is finished. To do this, choose M here
and read <file:Documentation/sound/README.modules>; the module
will be called soundcore.
I'm told that even without a sound card, you can make your computer
say more than an occasional beep, by programming the PC speaker.
......
arch/ppc/Kconfig
View file @ 176c1451
......@@ -849,10 +849,7 @@ config AMIGA_BUILTIN_SERIAL
If you want to use your Amiga's built-in serial port in Linux,
answer Y.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config GVPIOEXT
tristate "GVP IO-Extender support"
......@@ -882,10 +879,7 @@ config MULTIFACE_III_TTY
If you want to use a Multiface III card's serial port in Linux,
answer Y.
This driver is also available 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>.
To compile this driver as a module, choose M here.
config A2232
tristate "Commodore A2232 serial support (EXPERIMENTAL)"
......@@ -901,8 +895,7 @@ config A2232
This driver can be built as a module; but then "generic_serial"
will also be built as a module. This has to be loaded before
"ser_a2232". If you want to do this, answer M here and read
"<file:Documentation/modules.txt>".
"ser_a2232". If you want to do this, answer M here.
config WHIPPET_SERIAL
tristate "Hisoft Whippet PCMCIA serial support"
......@@ -918,10 +911,8 @@ config APNE
If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
say N.
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 apne. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called apne.
config SERIAL_CONSOLE
bool "Support for serial port console"
......
arch/s390/Kconfig
View file @ 176c1451
......@@ -166,10 +166,8 @@ config QDIO
For details please refer to the documentation provided by IBM at
<http://www10.software.ibm.com/developerworks/opensource/linux390>
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 qdio. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called qdio.
If unsure, say Y.
......
arch/sh/Kconfig
View file @ 176c1451
......@@ -839,9 +839,8 @@ config SERIAL
serial port drivers do not need this driver built in for them to
work.)
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
serial.
To compile this driver as a module, choose M here: the
module will be called serial.
[WARNING: Do not compile this driver as a module if you are using
non-standard serial ports, since the configuration information will
be lost when the driver is unloaded. This limitation may be lifted
......@@ -973,10 +972,8 @@ config PRINTER
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt> and
corresponding drivers into the kernel.
To compile this driver as a module, choose M here and read
<file:Documentation/parport.txt>. The module will be called lp.
If you have several parallel ports, you can specify which ports to
......@@ -1018,10 +1015,8 @@ config PPDEV
It is safe to say N to this -- it is not needed for normal printing
or parallel port CD-ROM/disk support.
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.
To compile this support as a module, choose M here: the
module will be called ppdev.
If unsure, say N.
......@@ -1097,10 +1092,8 @@ config SH_WDT
some performance issues. As such, the WDT should be avoided here
unless it is absolutely necessary.
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 shwdt. If you want to compile it as a module,
say M here and read Documentation/modules.txt.
To compile this driver as a module, choose M here: the
module will be called shwdt.
endmenu
......@@ -1126,10 +1119,8 @@ config RTC
sampling), then say Y here, and read <file:Documentation/rtc.txt>
for details.
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 rtc. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called rtc.
source "drivers/char/pcmcia/Kconfig"
......
arch/sparc/Kconfig
View file @ 176c1451
......@@ -162,11 +162,8 @@ config PCMCIA
for location). Please also read the PCMCIA-HOWTO, available from
<http://www.tldp.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).
When compiled this way, there will be modules called pcmcia_core
and ds. If you want to compile it as a module, say M here and
read <file:Documentation/modules.txt>.
To compile this driver as modules, choose M here: the
modules will be called pcmcia_core and ds.
config SBUS
bool
......@@ -248,11 +245,8 @@ config SUN_OPENPROMFS
virtual file system, which you can mount to /proc/openprom by "mount
-t openpromfs none /proc/openprom".
If you want to compile the /proc/openprom support as a module ( =
code which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>.
The module will be called openpromfs. If unsure, say M.
To compile the /proc/openprom support as a module, choose M here: the
module will be called openpromfs. If unsure, choose M.
source "fs/Kconfig.binfmt"
......@@ -280,9 +274,7 @@ config PRINTER
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt> and
driver as a module however, choose M here and read
<file:Documentation/parport.txt>. The module will be called lp.
If you have several parallel ports, you can specify which ports to
......@@ -321,10 +313,8 @@ config BLK_DEV_FD
well as location of the fdutils package used to configure additional
parameters of the driver at run 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 will be called floppy. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called floppy.
config BLK_DEV_LOOP
tristate "Loopback device support"
......@@ -370,10 +360,8 @@ config BLK_DEV_LOOP
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called loop.
To compile this driver as a module, choose M here: the
module will be called loop.
Most users will answer N here.
......@@ -399,10 +387,8 @@ config BLK_DEV_NBD
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called nbd.
To compile this driver as a module, choose M here: the
module will be called nbd.
If unsure, say N.
......@@ -421,10 +407,8 @@ config BLK_DEV_RAM
Note that the kernel command line option "ramdisk=XX" is now
obsolete. For details, read <file:Documentation/ramdisk.txt>.
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 and read <file:Documentation/modules.txt>. The module will be
called rd.
To compile this driver as a module, choose M here: the
module will be called rd.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
......@@ -534,11 +518,8 @@ config SOFT_WATCHDOG
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
This driver is also available 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>. The module will be called
softdog.
To compile this driver as a module, choose M here: the
module will be called softdog.
endmenu
......
arch/sparc64/Kconfig
View file @ 176c1451
......@@ -230,10 +230,8 @@ config ISAPNP
Say Y here if you would like support for ISA Plug and Play devices.
Some information is in <file:Documentation/isapnp.txt>.
This support is also available as a module called isapnp ( =
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>.
To compile this driver as a module, choose M here: the
module will be called isapnp.
If unsure, say Y.
......@@ -275,11 +273,8 @@ config PCMCIA
for location). Please also read the PCMCIA-HOWTO, available from
<http://www.tldp.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).
When compiled this way, there will be modules called pcmcia_core
and ds. If you want to compile it as a module, say M here and
read <file:Documentation/modules.txt>.
To compile this driver as modules, choose M here: the
modules will be called pcmcia_core and ds.
config SBUS
bool
......@@ -338,10 +333,8 @@ config RTC
sampling), then say Y here, and read <file:Documentation/rtc.txt>
for details.
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 rtc. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called rtc.
source "drivers/pci/Kconfig"
......@@ -352,11 +345,8 @@ config SUN_OPENPROMFS
virtual file system, which you can mount to /proc/openprom by "mount
-t openpromfs none /proc/openprom".
If you want to compile the /proc/openprom support as a module ( =
code which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>.
The module will be called openpromfs. If unsure, say M.
To compile the /proc/openprom support as a module, choose M here: the
module will be called openpromfs. If unsure, choose M.
config SPARC32_COMPAT
bool "Kernel support for Linux/Sparc 32bit binary compatibility"
......@@ -402,10 +392,8 @@ config SOLARIS_EMUL
This is experimental code which will enable you to run (many)
Solaris binaries on your SPARC Linux machine.
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 solaris. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this code as a module, choose M here: the
module will be called solaris.
source "drivers/parport/Kconfig"
......@@ -421,10 +409,8 @@ config PRINTER
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt> and
corresponding drivers into the kernel.
To compile this driver as a module, choose M here and read
<file:Documentation/parport.txt>. The module will be called lp.
If you have several parallel ports, you can specify which ports to
......@@ -443,10 +429,8 @@ config ENVCTRL
Kernel support for temperature and fan monitoring on Sun SME
machines.
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 envctrl. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called envctrl.
config DISPLAY7SEG
tristate "7-Segment Display support"
......@@ -455,10 +439,8 @@ config DISPLAY7SEG
This is the driver for the 7-segment display and LED present on
Sun Microsystems CompactPCI models CP1400 and CP1500.
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 display7seg. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called display7seg.
If you do not have a CompactPCI model CP1400 or CP1500, or
another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
......@@ -471,10 +453,8 @@ config WATCHDOG_CP1XXX
This is the driver for the hardware watchdog timers present on
Sun Microsystems CompactPCI models CP1400 and CP1500.
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 cpwatchdog. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called cpwatchdog.
If you do not have a CompactPCI model CP1400 or CP1500, or
another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
......@@ -513,10 +493,8 @@ config BLK_DEV_FD
well as location of the fdutils package used to configure additional
parameters of the driver at run 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 will be called floppy. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called floppy.
config BLK_DEV_LOOP
tristate "Loopback device support"
......@@ -562,10 +540,8 @@ config BLK_DEV_LOOP
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called loop.
To compile this driver as a module, choose M here: the
module will be called loop.
Most users will answer N here.
......@@ -591,10 +567,8 @@ config BLK_DEV_NBD
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called nbd.
To compile this driver as a module, choose M here: the
module will be called nbd.
If unsure, say N.
......@@ -613,10 +587,8 @@ config BLK_DEV_RAM
Note that the kernel command line option "ramdisk=XX" is now
obsolete. For details, read <file:Documentation/ramdisk.txt>.
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 and read <file:Documentation/modules.txt>. The module will be
called rd.
To compile this driver as a module, choose M here: the
module will be called rd.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
......@@ -775,11 +747,8 @@ config SOFT_WATCHDOG
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
This driver is also available 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>. The module will be called
softdog.
To compile this driver as a module, choose M here: the
module will be called softdog.
endmenu
......
drivers/block/Kconfig
View file @ 176c1451
......@@ -15,10 +15,8 @@ config BLK_DEV_FD
well as location of the fdutils package used to configure additional
parameters of the driver at run 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 will be called floppy. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called floppy.
config AMIGA_FLOPPY
tristate "Amiga floppy support"
......@@ -49,10 +47,8 @@ config BLK_DEV_PS2
Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
hard disk.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ps2esdi.
To compile this driver as a module, choose M here: the
module will be called ps2esdi.
config AMIGA_Z2RAM
tristate "Amiga Zorro II ramdisk support"
......@@ -60,11 +56,10 @@ config AMIGA_Z2RAM
help
This enables support for using Chip RAM and Zorro II RAM as a
ramdisk or as a swap partition. Say Y if you want to include this
driver in the kernel. 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 z2ram. If you want
to compile it as a module, say M here and read
<file:Documentation/modules.txt>.
driver in the kernel.
To compile this driver as a module, choose M here: the
module will be called z2ram.
config ATARI_ACSI
tristate "Atari ACSI support"
......@@ -80,9 +75,8 @@ config ATARI_ACSI
Ethernet, and PAMsNet Ethernet. If you want to use one of these
devices, you need ACSI support, too.
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 acsi.
To compile this driver as a module, choose M here: the
module will be called acsi.
comment "Some devices (e.g. CD jukebox) support multiple LUNs"
depends on ATARI && ATARI_ACSI
......@@ -116,10 +110,8 @@ config BLK_DEV_XD
Very old 8 bit hard disk controllers used in the IBM XT computer
will be supported if you say Y here.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called xd.
To compile this driver as a module, choose M here: the
module will be called xd.
It's pretty unlikely that you have one of these: say N.
......@@ -195,10 +187,8 @@ config BLK_DEV_DAC960
<file:Documentation/README.DAC960> for further information about
this driver.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called DAC960.
To compile this driver as a module, choose M here: the
module will be called DAC960.
config BLK_DEV_UMEM
tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
......@@ -211,10 +201,8 @@ config BLK_DEV_UMEM
The cards appear as block devices that can be partitioned into
as many as 15 partitions.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read Documentation/modules.txt. The module will be
called umem.
To compile this driver as a module, choose M here: the
module will be called umem.
The umem driver has not yet been allocated a MAJOR number, so
one is chosen dynamically. Use "devfs" or look in /proc/devices
......@@ -255,10 +243,8 @@ config BLK_DEV_LOOP
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called loop.
To compile this driver as a module, choose M here: the
module will be called loop.
Most users will answer N here.
......@@ -293,10 +279,8 @@ config BLK_DEV_NBD
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called nbd.
To compile this driver as a module, choose M here: the
module will be called nbd.
If unsure, say N.
......@@ -313,10 +297,8 @@ config BLK_DEV_RAM
Note that the kernel command line option "ramdisk=XX" is now
obsolete. For details, read <file:Documentation/ramdisk.txt>.
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 and read <file:Documentation/modules.txt>. The module will be
called rd.
To compile this driver as a module, choose M here: the
module will be called rd.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
......
drivers/cdrom/Kconfig
View file @ 176c1451
......@@ -24,10 +24,7 @@ config CD_NO_IDESCSI
file drivers/cdrom/{driver_name}.h where you can define your
interface parameters and switch some internal goodies.
All these CD-ROM drivers are also usable as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want). If you want to compile them as module, say M instead of Y and
read <file:Documentation/modules.txt>.
To compile these CD-ROM drivers as a module, choose M instead of Y.
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
......@@ -49,10 +46,8 @@ config AZTCD
file system support" below, because that's the file system used on
CD-ROMs.
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 aztcd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called aztcd.
config GSCD
tristate "Goldstar R420 CDROM support"
......@@ -67,10 +62,8 @@ config GSCD
file system support" below, because that's the file system used on
CD-ROMs.
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 gscd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called gscd.
config SBPCD
tristate "Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support"
......@@ -107,10 +100,8 @@ config SBPCD
file system support" below, because that's the file system used on
CD-ROMs.
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 sbpcd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sbpcd.
config MCD
tristate "Mitsumi (standard) [no XA/Multisession] CDROM support"
......@@ -132,10 +123,8 @@ config MCD
file system support" below, because that's the file system used on
CD-ROMs.
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 mcd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called mcd.
config MCD_IRQ
int "MCD IRQ"
......@@ -173,10 +162,8 @@ config MCDX
file system support" below, because that's the file system used on
CD-ROMs.
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 mcdx. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called mcdx.
config OPTCD
tristate "Optics Storage DOLPHIN 8000AT CDROM support"
......@@ -192,10 +179,8 @@ config OPTCD
file system support" below, because that's the file system used on
CD-ROMs.
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 optcd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called optcd.
config CM206
tristate "Philips/LMS CM206 CDROM support"
......@@ -209,10 +194,8 @@ config CM206
file system support" below, because that's the file system used on
CD-ROMs.
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 cm206. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called cm206.
config SJCD
tristate "Sanyo CDR-H94A CDROM support"
......@@ -223,10 +206,8 @@ config SJCD
"ISO 9660 CD-ROM file system support" below, because that's the
file system used on CD-ROMs.
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 sjcd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sjcd.
config ISP16_CDI
tristate "ISP16/MAD16/Mozart soft configurable cdrom interface support"
......@@ -238,10 +219,8 @@ config ISP16_CDI
to a driver for the particular cdrom drive you have attached to the
card. Read <file:Documentation/cdrom/isp16> for details.
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 isp16. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called isp16.
config CDU31A
tristate "Sony CDU31A/CDU33A CDROM support"
......@@ -260,10 +239,8 @@ config CDU31A
file system support" below, because that's the file system used on
CD-ROMs.
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 cdu31a. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called cdu31a.
config CDU535
tristate "Sony CDU535 CDROM support"
......@@ -276,9 +253,7 @@ config CDU535
file system support" below, because that's the file system used on
CD-ROMs.
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 sonycd535. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sonycd535.
endmenu
drivers/char/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/char/agp/Kconfig
View file @ 176c1451
......@@ -21,8 +21,7 @@ config AGP
You should say Y here if you use XFree86 3.3.6 or 4.x and want to
use GLX or DRI. If unsure, say N.
This driver is available as a module. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. The
To compile this driver as a module, choose M here: the
module will be called agpgart.
config AGP_ALI
......
drivers/char/ftape/Kconfig
View file @ 176c1451
......@@ -14,11 +14,8 @@ config ZFTAPE
interface (i.e. the hardware independent part of the driver) has
been moved to a separate module.
If you say M zftape will be compiled as a runtime loadable
module ( = code which can be inserted in and removed from the
running kernel whenever you want). In this case you should read
<file:Documentation/modules.txt>. The module will be called
zftape.
To compile this driver as a module, choose M here: the
module will be called zftape.
Regardless of whether you say Y or M here, an additional runtime
loadable module called `zft-compressor' which contains code to
......
drivers/char/watchdog/Kconfig
View file @ 176c1451
......@@ -46,11 +46,8 @@ config SOFT_WATCHDOG
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
This driver is also available 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>. The module will be called
softdog.
To compile this driver as a module, choose M here: the
module will be called softdog.
config WDT
tristate "WDT Watchdog timer"
......@@ -63,10 +60,8 @@ config WDT
documentation of your boot loader (lilo or loadlin) about how to
pass options to the kernel at boot time).
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 wdt.
To compile this driver as a module, choose M here: the
module will be called wdt.
config WDT_501
bool "WDT501 features"
......@@ -97,10 +92,8 @@ config WDTPCI
boot loader (lilo or loadlin) about how to pass options to the
kernel at boot time).
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 wdt_pci.
To compile this driver as a module, choose M here: the
module will be called wdt_pci.
config WDT_501_PCI
bool "WDT501-PCI features"
......@@ -124,10 +117,8 @@ config PCWATCHDOG
hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC
watchdog cards can be ordered from <http://www.berkprod.com/>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called pcwd. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called pcwd.
Most people will say N.
......@@ -139,13 +130,12 @@ config ACQUIRE_WDT
Board Computer produced by Acquire Inc (and 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 like the WDT501 driver but for 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 acquirewdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called acquirewdt.
Most people will say N.
config ADVANTECH_WDT
tristate "Advantech SBC Watchdog Timer"
......@@ -187,10 +177,8 @@ config SA1100_WATCHDOG
system when timeout is reached.
NOTE, that once enabled, this timer cannot be disabled.
This driver is also available 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>. The module will be called sa1100_wdt.
To compile this driver as a module, choose M here: the
module will be called sa1100_wdt.
config EUROTECH_WDT
tristate "Eurotech CPU-1220/1410 Watchdog Timer"
......@@ -211,11 +199,10 @@ config IB700_WDT
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. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most people
will say N.
To compile this driver as a module, choose M here: the
module will be called ib700wdt.
Most people will say N.
config I810_TCO
tristate "Intel i8xx TCO timer / Watchdog"
......@@ -234,9 +221,8 @@ config I810_TCO
machine. If this is the case you will get a kernel message like
"i810tco init: failed to reset NO_REBOOT flag".
If you want to compile this as a module, say M and read
<file:Documentation/modules.txt>. The module will be called
i810-tco.
To compile this driver as a module, choose M here: the
module will be called i810-tco.
config MIXCOMWD
tristate "Mixcom Watchdog"
......@@ -247,11 +233,10 @@ config MIXCOMWD
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. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called mixcomwd.
Most people will say N.
config SCx200_WDT
tristate "NatSemi SCx200 Watchdog"
......@@ -286,11 +271,10 @@ config W83877F_WDT
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 w83877f_wdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called w83877f_wdt.
Most people will say N.
config MACHZ_WDT
tristate "ZF MachZ Watchdog"
......@@ -302,10 +286,8 @@ config MACHZ_WDT
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 machzwd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called machzwd.
config SC520_WDT
tristate "AMD Elan SC520 processor Watchdog"
......@@ -340,11 +322,10 @@ config ALIM7101_WDT
This is the driver for the hardware watchdog on the ALi M7101 PMU
as used in the x86 Cobalt servers.
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 alim7101_wdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called alim7101_wdt.
Most people will say N.
config ALIM1535_WDT
tristate "ALi M1535 PMU Watchdog Timer"
......@@ -352,11 +333,10 @@ config ALIM1535_WDT
---help---
This is the driver for the hardware watchdog on the ALi M1535 PMU.
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 alim1535_wdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called alim1535_wdt.
Most people will say N.
config SC1200_WDT
tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
......@@ -367,11 +347,10 @@ config SC1200_WDT
for power management purposes and can be used to power down the device
during inactivity periods (includes interrupt activity monitoring).
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 sc1200wdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. Most
people will say N.
To compile this driver as a module, choose M here: the
module will be called sc1200wdt.
Most people will say N.
config WAFER_WDT
tristate "ICP Wafer 5823 Single Board Computer Watchdog"
......@@ -380,20 +359,15 @@ config WAFER_WDT
This is a driver for the hardware watchdog on the ICP Wafer 5823
Single Board Computer (and probably other similar models).
This driver is also available 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>. The module will be called
wafer5823wdt.
To compile this driver as a module, choose M here: the
module will be called wafer5823wdt.
config CPU5_WDT
tristate "SMA CPU5 Watchdog"
depends on WATCHDOG
---help---
TBD.
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 cpu5wdt. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called cpu5wdt.
endmenu
drivers/fc4/Kconfig
View file @ 176c1451
......@@ -33,10 +33,8 @@ config FC4_SOC
that if you have older firmware in the card, you'll need the
microcode from the Solaris driver to make it work.
This support is also available as a module called soc ( = 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>.
To compile this support as a module, choose M here: the module will
be called soc.
config FC4_SOCAL
tristate "Sun SOC+ (aka SOCAL)"
......@@ -48,10 +46,8 @@ config FC4_SOCAL
Interface Board). You'll probably need the microcode from the
Solaris driver to make it work.
This support is also available as a module called socal ( = 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>.
To compile this support as a module, choose M here: the module will
be called socal.
comment "FC4 targets"
depends on FC4
......@@ -62,10 +58,8 @@ config SCSI_PLUTO
help
If you never bought a disk array made by Sun, go with N.
This support is also available as a module called pluto ( = 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>.
To compile this support as a module, choose M here: the module will
be called pluto.
config SCSI_FCAL
tristate "Sun Enterprise Network Array (A5000 and EX500)" if SPARC32 || SPARC64
......@@ -76,10 +70,8 @@ config SCSI_FCAL
common is either A5000 array or internal disks in E[3-6]000
machines.
This support is also available as a module called fcal ( = 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>. If unsure, say N.
To compile this support as a module, choose M here: the module will
be called fcal.
config SCSI_FCAL
prompt "Generic FC-AL disk driver"
......
drivers/ide/Kconfig
View file @ 176c1451
......@@ -43,10 +43,8 @@ config IDE
number of user programs such as smart that can query the status of
SMART parameters from disk drives.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ide.
To compile this driver as a module, choose M here: the
module will be called ide.
For further information, please read <file:Documentation/ide.txt>.
......@@ -83,9 +81,7 @@ config BLK_DEV_IDE
performance, look for the hdparm package at
<ftp://ibiblio.org/pub/Linux/system/hardware/>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt> and
To compile this driver as a module, choose M here and read
<file:Documentation/ide.txt>. The module will be called ide-mod.
Do not compile this driver as a module if your root file system (the
one containing the directory /) is located on an IDE device.
......@@ -143,12 +139,12 @@ config BLK_DEV_IDEDISK
the old hard disk driver instead, say Y. If you have an SCSI-only
system, you can say N here.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ide-disk. Do not compile this driver as a module
if your root file system (the one containing the directory /) is
located on the IDE disk. If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called ide-disk.
Do not compile this driver as a module if your root file system
(the one containing the directory /) is located on the IDE disk.
If unsure, say Y.
config IDEDISK_MULTI_MODE
bool "Use multi-mode by default"
......@@ -201,10 +197,8 @@ config BLK_DEV_IDECD
with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
<ftp://brun.dyndns.org/pub/linux/lilo/>.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ide-cd.
To compile this driver as a module, choose M here: the
module will be called ide-cd.
config BLK_DEV_IDETAPE
tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)"
......@@ -226,10 +220,8 @@ config BLK_DEV_IDETAPE
<file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
for usage information.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ide-tape.o.
To compile this driver as a module, choose M here: the
module will be called ide-tape.
config BLK_DEV_IDEFLOPPY
tristate "Include IDE/ATAPI FLOPPY support"
......@@ -250,10 +242,8 @@ config BLK_DEV_IDEFLOPPY
other IDE devices, as "hdb" or "hdc", or something similar (check
the boot messages with dmesg).
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ide-floppy.
To compile this driver as a module, choose M here: the
module will be called ide-floppy.
config BLK_DEV_IDESCSI
tristate "SCSI emulation support"
......
drivers/ieee1394/Kconfig
View file @ 176c1451
......@@ -15,10 +15,8 @@ config IEEE1394
is the core support only, you will also need to select a driver for
your IEEE 1394 adapter.
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 ieee1394.
To compile this driver as a module, choose M here: the
module will be called ieee1394.
comment "Subsystem Options"
depends on IEEE1394
......@@ -64,10 +62,8 @@ config IEEE1394_PCILYNX
Instruments PCILynx chip. Note: this driver is written for revision
2 of this chip and may not work with revision 0.
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 pcilynx.
To compile this driver as a module, choose M here: the
module will be called pcilynx.
# Non-maintained pcilynx options
# if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then
......@@ -84,10 +80,8 @@ config IEEE1394_OHCI1394
use one of these chipsets. It should work with any OHCI-1394
compliant card, however.
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 ohci1394.
To compile this driver as a module, choose M here: the
module will be called ohci1394.
comment "Protocol Drivers"
depends on IEEE1394
......@@ -128,10 +122,8 @@ config IEEE1394_DV1394
The user-space API for dv1394 is documented in dv1394.h.
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 dv1394.
To compile this driver as a module, choose M here: the
module will be called dv1394.
config IEEE1394_RAWIO
tristate "Raw IEEE1394 I/O support"
......@@ -142,10 +134,8 @@ config IEEE1394_RAWIO
direct communication of user programs with the IEEE 1394 bus and
thus with the attached peripherals.
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 raw1394.
To compile this driver as a module, choose M here: the
module will be called raw1394.
config IEEE1394_CMP
tristate "IEC61883-1 Plug support"
......@@ -154,10 +144,8 @@ config IEEE1394_CMP
This option enables the Connection Management Procedures
(IEC61883-1) driver, which implements input and output plugs.
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 amdtp.
To compile this driver as a module, choose M here: the
module will be called cmp.
config IEEE1394_AMDTP
tristate "IEC61883-6 (Audio transmission) support"
......@@ -169,9 +157,7 @@ config IEEE1394_AMDTP
The userspace interface is documented in amdtp.h.
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 amdtp.
To compile this driver as a module, choose M here: the
module will be called amdtp.
endmenu
drivers/input/Kconfig
View file @ 176c1451
......@@ -19,10 +19,8 @@ config INPUT
If unsure, say Y.
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 input. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called input.
comment "Userland interfaces"
......@@ -39,10 +37,8 @@ config INPUT_MOUSEDEV
If unsure, say Y.
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 mousedev. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called mousedev.
config INPUT_MOUSEDEV_PSAUX
bool "Provide legacy /dev/psaux device" if EMBEDDED
......@@ -80,10 +76,8 @@ config INPUT_JOYDEV
More information is available: <file:Documentation/input/joystick.txt>
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called joydev. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called joydev.
config INPUT_TSDEV
tristate "Touchscreen interface"
......@@ -95,10 +89,8 @@ config INPUT_TSDEV
If unsure, say N.
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 tsdev. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called tsdev.
config INPUT_TSDEV_SCREEN_X
int "Horizontal screen resolution"
......@@ -117,10 +109,8 @@ config INPUT_EVDEV
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
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 evdev. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called evdev.
config INPUT_EVBUG
tristate "Event debugging"
......@@ -134,10 +124,8 @@ config INPUT_EVBUG
If unsure, say N.
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 joydev. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called evbug.
comment "Input I/O drivers"
......
drivers/input/gameport/Kconfig
View file @ 176c1451
......@@ -16,10 +16,8 @@ config GAMEPORT
If unsure, say Y.
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. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called gameport.
config SOUND_GAMEPORT
tristate
......@@ -34,10 +32,8 @@ config GAMEPORT_NS558
If unsure, say Y.
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 ns558. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called ns558.
config GAMEPORT_L4
tristate "PDPI Lightning 4 gamecard support"
......@@ -45,10 +41,8 @@ config GAMEPORT_L4
help
Say Y here if you have a PDPI Lightning 4 gamecard.
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 lightning. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called lightning.
config GAMEPORT_EMU10K1
tristate "SB Live and Audigy gameport support"
......@@ -57,10 +51,8 @@ config GAMEPORT_EMU10K1
Say Y here if you have a SoundBlaster Live! or SoundBlaster
Audigy card and want to use its gameport.
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 emu10k1-gp. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called emu10k1-gp.
config GAMEPORT_VORTEX
tristate "Aureal Vortex, Vortex 2 gameport support"
......@@ -69,10 +61,8 @@ config GAMEPORT_VORTEX
Say Y here if you have an Aureal Vortex 1 or 2 card and want
to use its gameport.
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 vortex. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called vortex.
config GAMEPORT_FM801
tristate "ForteMedia FM801 gameport support"
......
drivers/input/joystick/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/input/joystick/iforce/Kconfig
View file @ 176c1451
......@@ -9,10 +9,8 @@ config JOYSTICK_IFORCE
You also must choose at least one of the two options below.
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 iforce. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called iforce.
config JOYSTICK_IFORCE_USB
bool "I-Force USB joysticks and wheels"
......
drivers/input/keyboard/Kconfig
View file @ 176c1451
......@@ -24,10 +24,8 @@ config KEYBOARD_ATKBD
If unsure, say Y.
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 atkbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called atkbd.
config KEYBOARD_SUNKBD
tristate "Sun Type 4 and Type 5 keyboard support"
......@@ -38,10 +36,8 @@ config KEYBOARD_SUNKBD
connected either to the Sun keyboard connector or to an serial
(RS-232) port via a simple adapter.
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 sunkbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sunkbd.
config KEYBOARD_XTKBD
tristate "XT Keyboard support"
......@@ -53,10 +49,8 @@ config KEYBOARD_XTKBD
parallel port keyboard adapter, you cannot connect it to the
keyboard port on a PC that runs Linux.
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 xtkbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called xtkbd.
config KEYBOARD_NEWTON
tristate "Newton keyboard"
......@@ -65,10 +59,8 @@ config KEYBOARD_NEWTON
help
Say Y here if you have a Newton keyboard on a serial port.
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 maple_keyb. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called newtonkbd.
config KEYBOARD_MAPLE
tristate "Maple bus keyboard support"
......@@ -77,10 +69,8 @@ config KEYBOARD_MAPLE
Say Y here if you have a DreamCast console running Linux and have
a keyboard attached to its Maple bus.
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 maple_keyb. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called maple_keyb.
config KEYBOARD_AMIGA
tristate "Amiga keyboard"
......@@ -89,10 +79,8 @@ config KEYBOARD_AMIGA
Say Y here if you are running Linux on any AMIGA and have a keyboard
attached.
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 amikbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called amikbd.
config KEYBOARD_98KBD
tristate "NEC PC-9800 Keyboard support"
......@@ -102,8 +90,6 @@ config KEYBOARD_98KBD
Say Y here if you want to use the NEC PC-9801/PC-9821 keyboard (or
compatible) on your system.
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 xtkbd.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called 98kbd.
drivers/input/misc/Kconfig
View file @ 176c1451
......@@ -21,10 +21,8 @@ config INPUT_PCSPKR
If unsure, say Y.
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 pcspkr. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called pcspkr.
config INPUT_SPARCSPKR
tristate "SPARC Speaker support"
......@@ -35,10 +33,8 @@ config INPUT_SPARCSPKR
If unsure, say Y.
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 pcspkr. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sparcspkr.
config INPUT_M68K_BEEP
tristate "M68k Beeper support"
......@@ -55,10 +51,8 @@ config INPUT_UINPUT
Say Y here if you want to support user level drivers for input
subsystem accessible under char device 10:223 - /dev/input/uinput.
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 uinput. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called uinput.
config INPUT_GSC
tristate "PA-RISC GSC PS/2 keyboard/mouse support"
......
drivers/input/mouse/Kconfig
View file @ 176c1451
......@@ -24,10 +24,8 @@ config MOUSE_PS2
If unsure, say Y.
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 psmouse. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called psmouse.
config MOUSE_PS2_SYNAPTICS
bool "Synaptics TouchPad"
......@@ -56,10 +54,8 @@ config MOUSE_SERIAL
If unsure, say N.
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 sermouse. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called sermouse.
config MOUSE_INPORT
tristate "InPort/MS/ATIXL busmouse"
......@@ -68,10 +64,8 @@ config MOUSE_INPORT
Say Y here if you have an InPort, Microsoft or ATI XL busmouse.
They are rather rare these days.
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 inport. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called inport.
config MOUSE_ATIXL
bool "ATI XL variant"
......@@ -86,10 +80,8 @@ config MOUSE_LOGIBM
Say Y here if you have a Logitech busmouse.
They are rather rare these days.
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 logibm. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called logibm.
config MOUSE_PC110PAD
tristate "IBM PC110 touchpad"
......@@ -98,10 +90,8 @@ config MOUSE_PC110PAD
Say Y if you have the IBM PC-110 micro-notebook and want its
touchpad supported.
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 pc110pad. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called pc110pad.
config MOUSE_MAPLE
tristate "Maple bus mouse"
......@@ -110,10 +100,8 @@ config MOUSE_MAPLE
Say Y if you have a DreamCast console and a mouse attached to
its Maple bus.
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 maplemouse. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called maplemouse.
config MOUSE_AMIGA
tristate "Amiga mouse"
......@@ -122,10 +110,8 @@ config MOUSE_AMIGA
Say Y here if you have an Amiga and want its native mouse
supported by the kernel.
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 amimouse. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called amimouse.
config MOUSE_RISCPC
tristate "Acorn RiscPC mouse"
......@@ -134,10 +120,8 @@ config MOUSE_RISCPC
Say Y here if you have the Acorn RiscPC computer and want its
native mouse supported.
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 rpcmouse. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called rpcmouse.
config MOUSE_PC9800
tristate "NEC PC-9800 busmouse"
......@@ -146,8 +130,6 @@ config MOUSE_PC9800
Say Y here if you have NEC PC-9801/PC-9821 computer and want its
native mouse supported.
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 logibm.o. If you want to compile it as a
module, say M here and read <file.:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called 98busmouse.
drivers/input/serio/Kconfig
View file @ 176c1451
......@@ -13,10 +13,8 @@ config SERIO
If unsure, say Y.
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 serio. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called serio.
config SERIO_I8042
tristate "i8042 PC Keyboard controller" if EMBEDDED || !X86
......@@ -29,10 +27,8 @@ config SERIO_I8042
If unsure, say Y.
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 i8042. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called i8042.
config SERIO_SERPORT
tristate "Serial port line discipline"
......@@ -46,10 +42,8 @@ config SERIO_SERPORT
If unsure, say Y.
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 serport. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called serport.
config SERIO_CT82C710
tristate "ct82c710 Aux port controller"
......@@ -61,10 +55,8 @@ config SERIO_CT82C710
If unsure, say N.
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 ct82c710. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called ct82c710.
config SERIO_Q40KBD
tristate "Q40 keyboard controller"
......@@ -81,10 +73,8 @@ config SERIO_PARKBD
If unsure, say N.
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 parkbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called parkbd.
config SERIO_RPCKBD
tristate "Acorn RiscPC keyboard controller"
......@@ -94,10 +84,8 @@ config SERIO_RPCKBD
Say Y here if you have the Acorn RiscPC and want to use an AT
keyboard connected to its keyboard controller.
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 rpckbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called rpckbd.
config SERIO_AMBAKMI
tristate "AMBA KMI keyboard controller"
......@@ -114,10 +102,8 @@ config SERIO_98KBD
Say Y here if you have the NEC PC-9801/PC-9821 and want to use its
standard keyboard connected to its keyboard controller.
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 rpckbd.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called 98kbd-io.
config SERIO_PCIPS2
tristate "PCI PS/2 keyboard and PS/2 mouse controller"
......@@ -126,7 +112,5 @@ config SERIO_PCIPS2
Say Y here if you have a Mobility Docking station with PS/2
keyboard and mice ports.
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 rpckbd. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called pcips2.
drivers/input/touchscreen/Kconfig
View file @ 176c1451
......@@ -19,10 +19,8 @@ config TOUCHSCREEN_BITSY
If unsure, say N.
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 gunze. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called h3600_ts_input.
config TOUCHSCREEN_GUNZE
tristate "Gunze AHL-51S touchscreen"
......@@ -34,8 +32,6 @@ config TOUCHSCREEN_GUNZE
If unsure, say N.
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 gunze. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called gunze.
drivers/isdn/sc/Kconfig
View file @ 176c1451
......@@ -6,9 +6,8 @@ config ISDN_DRV_SC
depends on ISDN && ISA
help
This enables support for the Spellcaster BRI ISDN boards. This
driver currently builds only in a modularized version ( = code which
can be inserted in and removed from the running kernel whenever you
want, details in <file:Documentation/modules.txt>); the module will
be called sc. See <file:Documentation/isdn/README.sc> and
driver currently builds only in a modularized version.
To build it, choose M here: the module will be called sc.
See <file:Documentation/isdn/README.sc> and
<http://www.spellcast.com/> for more information.
drivers/media/Kconfig
View file @ 176c1451
......@@ -21,10 +21,8 @@ config VIDEO_DEV
Documentation/video4linux/API.html. Documentation for V4L2 is
available on the web at http://bytesex.org/v4l/
This driver is also available as a module called videodev ( = 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>.
To compile this driver as a module, choose M here: the
module will be called videodev.
source "drivers/media/video/Kconfig"
......
drivers/media/dvb/ttpci/Kconfig
View file @ 176c1451
......@@ -33,11 +33,8 @@ config DVB_BUDGET
Say Y if you own such a card and want to use it.
This driver is available as a module called
dvb-ttpci-budget.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>.
To compile this driver as a module, choose M here: the
module will be called budget.
config DVB_BUDGET_CI
tristate "Budget cards with onboard CI connector"
......@@ -49,11 +46,8 @@ config DVB_BUDGET_CI
Say Y if you own such a card and want to use it.
This driver is available as a module called
dvb-ttpci-budget-av.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>.
To compile this driver as a module, choose M here: the
module will be called budget-ci.
config DVB_BUDGET_AV
tristate "Budget cards with analog video inputs"
......@@ -65,10 +59,8 @@ config DVB_BUDGET_AV
Say Y if you own such a card and want to use it.
This driver is available as a module called
dvb-ttpci-budget-av.o ( = code which can be inserted in
and removed from the running kernel whenever you want).
here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the
module will be called budget-av.
config DVB_BUDGET_PATCH
tristate "AV7110 cards with Budget Patch"
......@@ -85,8 +77,5 @@ config DVB_BUDGET_PATCH
Say Y if you own such a card and want to use it.
This driver is available as a module called
dvb-ttpci-budget-patch.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>.
To compile this driver as a module, choose M here: the
module will be called budget-patch.
drivers/media/radio/Kconfig
View file @ 176c1451
......@@ -20,10 +20,8 @@ config RADIO_CADET
Further documentation on this driver can be found on the WWW at
<http://linux.blackhawke.net/cadet.html>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-cadet.
To compile this driver as a module, choose M here: the
module will be called radio-cadet.
config RADIO_RTRACK
tristate "AIMSlab RadioTrack (aka RadioReveal) support"
......@@ -48,10 +46,8 @@ config RADIO_RTRACK
information is contained in the file
<file:Documentation/video4linux/radiotrack.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-aimslab.
To compile this driver as a module, choose M here: the
module will be called radio-aimslab.
config RADIO_RTRACK_PORT
hex "RadioTrack i/o port (0x20f or 0x30f)"
......@@ -73,10 +69,8 @@ config RADIO_RTRACK2
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-rtrack2.
To compile this driver as a module, choose M here: the
module will be called radio-rtrack2.
config RADIO_RTRACK2_PORT
hex "RadioTrack II i/o port (0x20c or 0x30c)"
......@@ -98,10 +92,8 @@ config RADIO_AZTECH
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-aztech.
To compile this driver as a module, choose M here: the
module will be called radio-aztech.
config RADIO_AZTECH_PORT
hex "Aztech/Packard Bell I/O port (0x350 or 0x358)"
......@@ -124,10 +116,8 @@ config RADIO_GEMTEK
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-gemtek.
To compile this driver as a module, choose M here: the
module will be called radio-gemtek.
config RADIO_GEMTEK_PORT
hex "GemTek i/o port (0x20c, 0x30c, 0x24c or 0x34c)"
......@@ -150,10 +140,8 @@ config RADIO_GEMTEK_PCI
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-gemtek-pci.
To compile this driver as a module, choose M here: the
module will be called radio-gemtek-pci.
config RADIO_MAXIRADIO
tristate "Guillemot MAXI Radio FM 2000 radio"
......@@ -167,10 +155,8 @@ config RADIO_MAXIRADIO
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-maxiradio.
To compile this driver as a module, choose M here: the
module will be called radio-maxiradio.
config RADIO_MAESTRO
tristate "Maestro on board radio"
......@@ -184,10 +170,8 @@ config RADIO_MAESTRO
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-maestro.
To compile this driver as a module, choose M here: the
module will be called radio-maestro.
config RADIO_MIROPCM20
tristate "miroSOUND PCM20 radio"
......@@ -202,10 +186,8 @@ config RADIO_MIROPCM20
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called miropcm20.
To compile this driver as a module, choose M here: the
module will be called miropcm20.
config RADIO_MIROPCM20_RDS
tristate "miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)"
......@@ -221,7 +203,8 @@ config RADIO_MIROPCM20_RDS
availability of RDS is reported over V4L by the basic driver
already. Here RDS can be read from files in /dev/v4l/rds.
As module the driver will be called miropcm20-rds.
To compile this driver as a module, choose M here: the
module will be called miropcm20-rds.
config RADIO_SF16FMI
tristate "SF16FMI Radio"
......@@ -237,10 +220,8 @@ config RADIO_SF16FMI
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-sf16fmi.
To compile this driver as a module, choose M here: the
module will be called radio-sf16fmi.
config RADIO_TERRATEC
tristate "TerraTec ActiveRadio ISA Standalone"
......@@ -260,10 +241,8 @@ config RADIO_TERRATEC
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-terratec.
To compile this driver as a module, choose M here: the
module will be called radio-terratec.
config RADIO_TERRATEC_PORT
hex "Terratec i/o port (normally 0x590)"
......@@ -280,10 +259,8 @@ config RADIO_TRUST
This is a driver for the Trust FM radio cards. Say Y if you have
such a card and want to use it under Linux.
This driver is also available as a module called radio-trust ( =
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>.
To compile this driver as a module, choose M here: the
module will be called radio-trust.
config RADIO_TRUST_PORT
hex "Trust i/o port (usually 0x350 or 0x358)"
......@@ -305,10 +282,8 @@ config RADIO_TYPHOON
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-typhoon.
To compile this driver as a module, choose M here: the
module will be called radio-typhoon.
config RADIO_TYPHOON_PROC_FS
bool "Support for /proc/radio-typhoon"
......@@ -351,10 +326,8 @@ config RADIO_ZOLTRIX
this API and pointers to "v4l" programs may be found on the WWW at
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-zoltrix.
To compile this driver as a module, choose M here: the
module will be called radio-zoltrix.
config RADIO_ZOLTRIX_PORT
hex "ZOLTRIX I/O port (0x20c or 0x30c)"
......
drivers/media/video/Kconfig
View file @ 176c1451
......@@ -18,20 +18,17 @@ config VIDEO_BT848
If you say Y or M here, you need to say Y or M to "I2C support" and
"I2C bit-banging interfaces" in the character device section.
This driver is available as a module called bttv ( = 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>.
To compile this driver as a module, choose M here: the
module will be called bttv.
config VIDEO_PMS
tristate "Mediavision Pro Movie Studio Video For Linux"
depends on VIDEO_DEV && ISA
help
Say Y if you have such a thing. This driver is also available as a
module called pms ( = 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>.
Say Y if you have such a thing.
To compile this driver as a module, choose M here: the
module will be called pms.
config VIDEO_PLANB
tristate "PlanB Video-In on PowerMac"
......@@ -51,10 +48,8 @@ config VIDEO_BWQCAM
Say Y have if you the black and white version of the QuickCam
camera. See the next option for the color version.
This driver is also available as a module called bw-qcam ( = 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>.
To compile this driver as a module, choose M here: the
module will be called bw-qcam.
config VIDEO_CQCAM
tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
......@@ -122,10 +117,8 @@ config VIDEO_SAA5249
Support for I2C bus based teletext using the SAA5249 chip. At the
moment this is only useful on some European WinTV cards.
This driver is also available as a module called saa5249 ( = 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>.
To compile this driver as a module, choose M here: the
module will be called saa5249.
config TUNER_3036
tristate "SAB3036 tuner"
......@@ -159,10 +152,8 @@ config VIDEO_ZORAN
a driver homepage at <http://mjpeg.sf.net/driver-zoran/>. For
more information, check <file:Documentation/video4linux/Zoran>.
This driver is available as a module called zr36067 ( = 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>.
To compile this driver as a module, choose M here: the
module will be called zr36067.
config VIDEO_ZORAN_BUZ
tristate "Iomega Buz support"
......@@ -208,10 +199,8 @@ config VIDEO_ZR36120
and Buster boards. Please read the material in
<file:Documentation/video4linux/zr36120.txt> for more information.
This driver is also available as a module called zr36120 ( = 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>.
To compile this driver as a module, choose M here: the
module will be called zr36120.
config VIDEO_MEYE
tristate "Sony Vaio Picturebook Motion Eye Video For Linux (EXPERIMENTAL)"
......@@ -224,10 +213,8 @@ config VIDEO_MEYE
If you say Y or M here, you need to say Y or M to "Sony Programmable
I/O Control Device" in the character device section.
This driver is available as a module called meye ( = 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>.
To compile this driver as a module, choose M here: the
module will be called meye.
config VIDEO_SAA7134
tristate "Philips SAA7134 support"
......@@ -236,10 +223,8 @@ config VIDEO_SAA7134
This is a video4linux driver for Philips SAA7130/7134 based
TV cards.
This driver is available as a module called saa7134 ( = 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>.
To compile this driver as a module, choose M here: the
module will be called saa7134.
config VIDEO_MXB
tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
......@@ -248,10 +233,8 @@ config VIDEO_MXB
This is a video4linux driver for the 'Multimedia eXtension Board'
TV card by Siemens-Nixdorf.
This driver is available as a module called mxb ( = 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>.
To compile this driver as a module, choose M here: the
module will be called mxb.
config VIDEO_DPC
tristate "Philips-Semiconductors 'dpc7146 demonstration board'"
......@@ -263,10 +246,8 @@ config VIDEO_DPC
saa7146 based, analog video card, chances are good that it
will work with this skeleton driver.
This driver is available as a module called dpc7146 ( = 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>.
To compile this driver as a module, choose M here: the
module will be called dpc7146.
config VIDEO_HEXIUM_ORION
tristate "Hexium HV-PCI6 and Orion frame grabber"
......@@ -275,10 +256,8 @@ config VIDEO_HEXIUM_ORION
This is a video4linux driver for the Hexium HV-PCI6 and
Orion frame grabber cards by Hexium.
This driver is available as a module called hexium_orion
( = 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>.
To compile this driver as a module, choose M here: the
module will be called hexium_orion.
config VIDEO_HEXIUM_GEMINI
tristate "Hexium Gemini frame grabber"
......@@ -288,10 +267,8 @@ config VIDEO_HEXIUM_GEMINI
grabber card by Hexium. Please note that the Gemini Dual
card is *not* fully supported.
This driver is available as a module called hexium_gemini
( = 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>.
To compile this driver as a module, choose M here: the
module will be called hexium_gemini.
endmenu
drivers/message/fusion/Kconfig
View file @ 176c1451
......@@ -29,11 +29,7 @@ config FUSION
[2] In order enable capability to boot the linux kernel
natively from a Fusion MPT target device, you MUST
answer Y here! (currently requires CONFIG_BLK_DEV_SD)
[3] This support is also available as a module ( = code
which can be inserted in and removed from the running
kernel whenever you want). If you want to compile as
modules, say M here and read
<file:Documentation/modules.txt>.
[3] To compile this support as modules, choose M here.
If unsure, say N.
......
drivers/message/i2o/Kconfig
View file @ 176c1451
......@@ -19,11 +19,8 @@ config I2O
If you say Y here, you will get a choice of interface adapter
drivers and OSM's with the following questions.
This support is also available 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>. You will get modules called
i2o_core and i2o_config.
To compile this support as a module, choose M here: the
modules will be called i2o_core and i2o_config.
If unsure, say N.
......@@ -34,10 +31,8 @@ config I2O_PCI
Say Y for support of PCI bus I2O interface adapters. Currently this
is the only variety supported, so you should say Y.
This support is also available as a module called i2o_pci ( = 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>.
To compile this support as a module, choose M here: the
module will be called i2o_pci.
config I2O_BLOCK
tristate "I2O Block OSM"
......@@ -46,10 +41,8 @@ config I2O_BLOCK
Include support for the I2O Block OSM. The Block OSM presents disk
and other structured block devices to the operating system.
This support is also available as a module called i2o_block ( =
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>.
To compile this support as a module, choose M here: the
module will be called i2o_block.
config I2O_SCSI
tristate "I2O SCSI OSM"
......@@ -59,10 +52,8 @@ config I2O_SCSI
I2O controller. You can use both the SCSI and Block OSM together if
you wish.
This support is also available as a module called i2o_scsi ( =
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>.
To compile this support as a module, choose M here: the
module will be called i2o_scsi.
config I2O_PROC
tristate "I2O /proc support"
......@@ -72,10 +63,8 @@ config I2O_PROC
able to read I2O related information from the virtual directory
/proc/i2o.
This support is also available as a module called i2o_proc ( =
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>.
To compile this support as a module, choose M here: the
module will be called i2o_proc.
endmenu
drivers/net/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/net/appletalk/Kconfig
View file @ 176c1451
......@@ -65,10 +65,8 @@ config IPDDP
decapsulation, but not both. With the following two questions, you
decide which one you want.
If you say M here, the AppleTalk-IP support will be compiled as a
module ( = code which can be inserted in and removed from the
running kernel whenever you want, read
<file:Documentation/modules.txt>). The module is called ipddp.
To compile the AppleTalk-IP support as a module, choose M here: the
module will be called ipddp.
In this case, you will be able to use both encapsulation and
decapsulation simultaneously, by loading two copies of the module
and specifying different values for the module option ipddp_mode.
......
drivers/net/hamradio/Kconfig
View file @ 176c1451
......@@ -12,9 +12,7 @@ config MKISS
the advantage that it is already supported by most modern TNCs
without the need for a firmware upgrade.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
To compile this driver as a module, choose M here: the module
will be called mkiss.
config 6PACK
......@@ -32,9 +30,7 @@ config 6PACK
problems. For details about the features and the usage of the
driver, read <file:Documentation/networking/6pack.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
To compile this driver as a module, choose M here: the module
will be called 6pack.
config BPQETHER
......@@ -91,9 +87,7 @@ config SCC
<http://www.tldp.org/docs.html#howto>. Also make sure to say Y
to "Amateur Radio AX.25 Level 2" support.
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
To compile this driver as a module, choose M here: the module
will be called scc.
config SCC_DELAY
......@@ -129,10 +123,8 @@ config BAYCOM_SER_FDX
information on the modems, see <http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_ser_fdx.
To compile this driver as a module, choose M here: the module
will be called baycom_ser_fdx. This is recommended.
config BAYCOM_SER_HDX
tristate "BAYCOM ser12 halfduplex driver for AX.25"
......@@ -148,10 +140,8 @@ config BAYCOM_SER_HDX
<http://www.baycom.de/> and
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_ser_hdx.
To compile this driver as a module, choose M here: the module
will be called baycom_ser_hdx. This is recommended.
config BAYCOM_PAR
tristate "BAYCOM picpar and par96 driver for AX.25"
......@@ -164,10 +154,8 @@ config BAYCOM_PAR
the modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_par.
To compile this driver as a module, choose M here: the module
will be called baycom_par. This is recommended.
config BAYCOM_EPP
tristate "BAYCOM epp driver for AX.25"
......@@ -180,10 +168,8 @@ config BAYCOM_EPP
modems, see <http://www.baycom.de/> and the file
<file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. This is
recommended. The module will be called baycom_par.
To compile this driver as a module, choose M here: the module
will be called baycom_epp. This is recommended.
config YAM
tristate "YAM driver for AX.25"
......@@ -193,7 +179,6 @@ config YAM
port and includes some of the functions of a Terminal Node
Controller. If you have one of those, say Y here.
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>.
To compile this driver as a module, choose M here: the module
will be called yam.
drivers/net/irda/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/net/pcmcia/Kconfig
View file @ 176c1451
......@@ -28,11 +28,8 @@ config PCMCIA_3C589
Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
(PC-card) Ethernet card to your computer.
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 3c589_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called 3c589_cs. If unsure, say N.
config PCMCIA_3C574
tristate "3Com 3c574 PCMCIA support"
......@@ -41,11 +38,8 @@ config PCMCIA_3C574
Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
(PC-card) Fast Ethernet card to your computer.
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 3c574_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called 3c574_cs. If unsure, say N.
config PCMCIA_FMVJ18X
tristate "Fujitsu FMV-J18x PCMCIA support"
......@@ -54,11 +48,8 @@ config PCMCIA_FMVJ18X
Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
PCMCIA (PC-card) Ethernet card to your computer.
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 fmvj18x_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called fmvj18x_cs. If unsure, say N.
config PCMCIA_PCNET
tristate "NE2000 compatible PCMCIA support"
......@@ -67,11 +58,8 @@ config PCMCIA_PCNET
Say Y here if you intend to attach an NE2000 compatible PCMCIA
(PC-card) Ethernet or Fast Ethernet card to your computer.
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 pcnet_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called pcnet_cs. If unsure, say N.
config PCMCIA_NMCLAN
tristate "New Media PCMCIA support"
......@@ -80,11 +68,8 @@ config PCMCIA_NMCLAN
Say Y here if you intend to attach a New Media Ethernet or LiveWire
PCMCIA (PC-card) Ethernet card to your computer.
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 nmclan_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called nmclan_cs. If unsure, say N.
config PCMCIA_SMC91C92
tristate "SMC 91Cxx PCMCIA support"
......@@ -93,11 +78,8 @@ config PCMCIA_SMC91C92
Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
(PC-card) Ethernet or Fast Ethernet card to your computer.
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 smc91c92_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called smc91c92_cs. If unsure, say N.
config PCMCIA_XIRC2PS
tristate "Xircom 16-bit PCMCIA support"
......@@ -106,11 +88,8 @@ config PCMCIA_XIRC2PS
Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card)
Ethernet or Fast Ethernet card to your computer.
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 xirc2ps_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called xirc2ps_cs. If unsure, say N.
config PCMCIA_AXNET
tristate "Asix AX88190 PCMCIA support"
......@@ -121,11 +100,8 @@ config PCMCIA_AXNET
nearly NE2000 compatible but need a separate driver due to a few
misfeatures.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called axnet_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called axnet_cs. If unsure, say N.
config ARCNET_COM20020_CS
tristate "COM20020 ARCnet PCMCIA support"
......@@ -134,11 +110,8 @@ config ARCNET_COM20020_CS
Say Y here if you intend to attach this type of ARCnet PCMCIA card
to your computer.
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 com20020_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called com20020_cs. If unsure, say N.
config PCMCIA_IBMTR
tristate "IBM PCMCIA tokenring adapter support"
......@@ -148,10 +121,8 @@ config PCMCIA_IBMTR
card to your computer. You then also need to say Y to "Token Ring
driver support".
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 ibmtr_cs. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called ibmtr_cs.
endmenu
drivers/net/tokenring/Kconfig
View file @ 176c1451
......@@ -31,10 +31,8 @@ config IBMTR
Warning: this driver will almost definitely fail if more than one
active Token Ring card is present.
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 ibmtr. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called ibmtr.
config IBMOL
tristate "IBM Olympic chipset PCI adapter support"
......@@ -47,10 +45,8 @@ config IBMOL
If you have such an adapter, say Y and read the Token-Ring
mini-HOWTO, available from <http://www.tldp.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 olympic. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called olympic.
Also read <file:Documentation/networking/olympic.txt> or check the
Linux Token Ring Project site for the latest information at
......@@ -65,10 +61,8 @@ config IBMLS
If you have such an adapter, say Y and read the Token-Ring
mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
This driver is also available as a modules ( = code which can be
inserted in and removed from the running kernel whenever you want).
The modules will be called lanstreamer. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called lanstreamer.
config 3C359
tristate "3Com 3C359 Token Link Velocity XL adapter support"
......@@ -81,10 +75,8 @@ config 3C359
If you have such an adapter, say Y and read the Token-Ring
mini-HOWTO, available from <http://www.tldp.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 will be called 3c359. If you want to compile it
as a module, say M here and read Documentation/modules.txt.
To compile this driver as a module, choose M here: the module will be
called 3c359.
Also read the file <file:Documentation/networking/3c359.txt> or check the
Linux Token Ring Project site for the latest information at
......@@ -110,10 +102,8 @@ config TMS380TR
Also read the file <file:Documentation/networking/tms380tr.txt> or
check <http://www.auk.cx/tms380tr/>.
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 tms380tr. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called tms380tr.
config TMSPCI
tristate "Generic TMS380 PCI support"
......@@ -127,10 +117,8 @@ config TMSPCI
- Thomas-Conrad TC4048 PCI 4/16
- 3Com Token Link Velocity
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 tmspci. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called tmspci.
config SKISA
tristate "SysKonnect TR4/16 ISA support"
......@@ -141,10 +129,8 @@ config SKISA
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 skisa. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called skisa.
config PROTEON
tristate "Proteon ISA support"
......@@ -156,10 +142,8 @@ config PROTEON
- Proteon 1392
- Proteon 1392 plus
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 proteon. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called proteon.
config ABYSS
tristate "Madge Smart 16/4 PCI Mk2 support"
......@@ -168,10 +152,8 @@ config ABYSS
This tms380 module supports the Madge Smart 16/4 PCI Mk2
cards (51-02).
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 abyss. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called abyss.
config MADGEMC
tristate "Madge Smart 16/4 Ringnode MicroChannel"
......@@ -180,10 +162,8 @@ config MADGEMC
This tms380 module supports the Madge Smart 16/4 MC16 and MC32
MicroChannel adapters.
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 madgemc. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called madgemc.
config SMCTR
tristate "SMC ISA/MCA adapter support"
......@@ -198,10 +178,8 @@ config SMCTR
<http://www.tldp.org/docs.html#howto> and the file
<file:Documentation/networking/smctr.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 smctr. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
To compile this driver as a module, choose M here: the module will be
called smctr.
endmenu
drivers/net/wan/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/net/wireless/Kconfig
View file @ 176c1451
......@@ -53,9 +53,7 @@ config STRIP
in saying Y to STRIP now, except that it makes the kernel a bit
bigger.
You can also 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
To compile this as a module, choose M here: the module will be
called strip.
config ARLAN
......@@ -97,11 +95,8 @@ config WAVELAN
<http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
Please read the man pages contained therein.
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 wavelan. 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>.
To compile this driver as a module, choose M here: the module will be
called wavelan.
config PCMCIA_WAVELAN
tristate "AT&T/Lucent old WaveLAN Pcmcia wireless support"
......@@ -111,11 +106,8 @@ config PCMCIA_WAVELAN
(PC-card) wireless Ethernet networking card to your computer. This
driver is for the non-IEEE-802.11 Wavelan cards.
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 wavelan_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called wavelan_cs. If unsure, say N.
config PCMCIA_NETWAVE
tristate "Xircom Netwave AirSurfer Pcmcia wireless support"
......@@ -124,11 +116,8 @@ config PCMCIA_NETWAVE
Say Y here if you intend to attach this type of PCMCIA (PC-card)
wireless Ethernet networking card to your computer.
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 netwave_cs. If you want to compile it
as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be
called netwave_cs. If unsure, say N.
comment "Wireless 802.11 Frequency Hopping cards support"
depends on NET_RADIO && PCMCIA
......@@ -142,11 +131,8 @@ config PCMCIA_RAYCS
Please read the file <file:Documentation/networking/ray_cs.txt> for
details.
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 ray_cs. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
To compile this driver as a module, choose M here: the module will be
called ray_cs. If unsure, say N.
comment "Wireless 802.11b ISA/PCI cards support"
depends on NET_RADIO && (ISA || PCI || PPC_PMAC || PCMCIA)
......
drivers/parport/Kconfig
View file @ 176c1451
......@@ -24,13 +24,11 @@ config PARPORT
It is possible to share a single parallel port among several devices
and it is safe to compile all the corresponding drivers into the
kernel. If you want to compile parallel port support as a module
( = code which can be inserted in and removed from the running
kernel whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called
parport. If you have more than one parallel port and want to
specify which port and IRQ to be used by this driver at module load
time, take a look at <file:Documentation/parport.txt>.
kernel. To compile parallel port support as a module, choose M here:
the module will be called parport.
If you have more than one parallel port and want to specify which
port and IRQ to be used by this driver at module load time, take a
look at <file:Documentation/parport.txt>.
If unsure, say Y.
......@@ -43,11 +41,8 @@ config PARPORT_PC
parallel ports. PA-RISC owners should only say Y here if they
have a SuperIO parallel port.
This code is also available as a module. If you want to compile it
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
parport_pc.
To compile this driver as a module, choose M here: the
module will be called parport_pc.
If unsure, say Y.
......
drivers/pci/hotplug/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/pcmcia/Kconfig
View file @ 176c1451
......@@ -23,11 +23,8 @@ config PCMCIA
for location). Please also read the PCMCIA-HOWTO, available from
<http://www.tldp.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).
When compiled this way, there will be modules called pcmcia_core
and ds. If you want to compile it as a module, say M here and
read <file:Documentation/modules.txt>.
To compile this driver as modules, choose M here: the
modules will be called pcmcia_core and ds.
config YENTA
tristate "CardBus yenta-compatible bridge support"
......
drivers/s390/Kconfig
View file @ 176c1451
......@@ -49,10 +49,8 @@ config BLK_DEV_LOOP
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called loop.
To compile this driver as a module, choose M here: the
module will be called loop.
Most users will answer N here.
......@@ -78,10 +76,8 @@ config BLK_DEV_NBD
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called nbd.
To compile this driver as a module, choose M here: the
module will be called nbd.
If unsure, say N.
......@@ -98,10 +94,8 @@ config BLK_DEV_RAM
Note that the kernel command line option "ramdisk=XX" is now
obsolete. For details, read <file:Documentation/ramdisk.txt>.
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 and read <file:Documentation/modules.txt>. The module will be
called rd.
To compile this driver as a module, choose M here: the
module will be called rd.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
......
drivers/s390/net/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/sbus/char/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/scsi/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/scsi/aic7xxx/Kconfig.aic7xxx
View file @ 176c1451
This diff is collapsed.
drivers/scsi/pcmcia/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/serial/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/telephony/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/class/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/host/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/image/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/input/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/media/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/misc/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/net/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/serial/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/usb/storage/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/video/Kconfig
View file @ 176c1451
This diff is collapsed.
drivers/video/console/Kconfig
View file @ 176c1451
This diff is collapsed.
fs/Kconfig
View file @ 176c1451
This diff is collapsed.
fs/Kconfig.binfmt
View file @ 176c1451
This diff is collapsed.
net/Kconfig
View file @ 176c1451
This diff is collapsed.
net/ax25/Kconfig
View file @ 176c1451
This diff is collapsed.
net/bridge/netfilter/Kconfig
View file @ 176c1451
This diff is collapsed.
net/ipv4/ipvs/Kconfig
View file @ 176c1451
This diff is collapsed.
net/ipv4/netfilter/Kconfig
View file @ 176c1451
This diff is collapsed.
net/ipv6/netfilter/Kconfig
View file @ 176c1451
This diff is collapsed.
net/irda/irlan/Kconfig
View file @ 176c1451
This diff is collapsed.
net/sched/Kconfig
View file @ 176c1451
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7