Fix misc Kconfig typos
Fix various Kconfig typos. Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Acked-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
parent
5d3f083d8f
commit
3cb2fccc5f
24 changed files with 34 additions and 34 deletions
|
@ -133,7 +133,7 @@ config IXP4XX_INDIRECT_PCI
|
|||
into the kernel and we can use the standard read[bwl]/write[bwl]
|
||||
macros. This is the preferred method due to speed but it
|
||||
limits the system to just 64MB of PCI memory. This can be
|
||||
problamatic if using video cards and other memory-heavy devices.
|
||||
problematic if using video cards and other memory-heavy devices.
|
||||
|
||||
2) If > 64MB of memory space is required, the IXP4xx can be
|
||||
configured to use indirect registers to access PCI This allows
|
||||
|
|
|
@ -8,7 +8,7 @@ config MACH_KEV7A400
|
|||
help
|
||||
Say Y here if you are using the Sharp KEV7A400 development
|
||||
board. This hardware is discontinued, so I'd be very
|
||||
suprised if you wanted this option.
|
||||
surprised if you wanted this option.
|
||||
|
||||
config MACH_LPD7A400
|
||||
bool "LPD7A400 Card Engine"
|
||||
|
|
|
@ -91,7 +91,7 @@ config SMDK2440_CPU2442
|
|||
config MACH_S3C2413
|
||||
bool
|
||||
help
|
||||
Internal node for S3C2413 verison of SMDK2413, so that
|
||||
Internal node for S3C2413 version of SMDK2413, so that
|
||||
machine_is_s3c2413() will work when MACH_SMDK2413 is
|
||||
selected
|
||||
|
||||
|
|
|
@ -197,7 +197,7 @@ config CPU_ARM940T
|
|||
select CPU_CP15_MPU
|
||||
help
|
||||
ARM940T is a member of the ARM9TDMI family of general-
|
||||
purpose microprocessors with MPU and seperate 4KB
|
||||
purpose microprocessors with MPU and separate 4KB
|
||||
instruction and 4KB data cases, each with a 4-word line
|
||||
length.
|
||||
|
||||
|
|
|
@ -323,7 +323,7 @@ config ETRAX_DEF_R_WAITSTATES
|
|||
depends on ETRAX_ARCH_V10
|
||||
default "95a6"
|
||||
help
|
||||
Waitstates for SRAM, Flash and peripherials (not DRAM). 95f8 is a
|
||||
Waitstates for SRAM, Flash and peripherals (not DRAM). 95f8 is a
|
||||
good choice for most Axis products...
|
||||
|
||||
config ETRAX_DEF_R_BUS_CONFIG
|
||||
|
|
|
@ -839,7 +839,7 @@ config ETRAX_DS1302_TRICKLE_CHARGE
|
|||
default "0"
|
||||
help
|
||||
This controls the initial value of the trickle charge register.
|
||||
0 = disabled (use this if you are unsure or have a non rechargable battery)
|
||||
0 = disabled (use this if you are unsure or have a non rechargeable battery)
|
||||
Otherwise the following values can be OR:ed together to control the
|
||||
charge current:
|
||||
1 = 2kohm, 2 = 4kohm, 3 = 4kohm
|
||||
|
|
|
@ -88,7 +88,7 @@ config ETRAX_SERIAL_PORT0_DMA7_IN
|
|||
help
|
||||
Enables the DMA7 input channel for ser0 (ttyS0).
|
||||
If you do not enable DMA, an interrupt for each character will be
|
||||
used when receiveing data.
|
||||
used when receiving data.
|
||||
Normally you want to use DMA, unless you use the DMA channel for
|
||||
something else.
|
||||
|
||||
|
@ -157,7 +157,7 @@ config ETRAX_SERIAL_PORT1_DMA5_IN
|
|||
help
|
||||
Enables the DMA5 input channel for ser1 (ttyS1).
|
||||
If you do not enable DMA, an interrupt for each character will be
|
||||
used when receiveing data.
|
||||
used when receiving data.
|
||||
Normally you want this on, unless you use the DMA channel for
|
||||
something else.
|
||||
|
||||
|
@ -228,7 +228,7 @@ config ETRAX_SERIAL_PORT2_DMA3_IN
|
|||
help
|
||||
Enables the DMA3 input channel for ser2 (ttyS2).
|
||||
If you do not enable DMA, an interrupt for each character will be
|
||||
used when receiveing data.
|
||||
used when receiving data.
|
||||
Normally you want to use DMA, unless you use the DMA channel for
|
||||
something else.
|
||||
|
||||
|
@ -297,7 +297,7 @@ config ETRAX_SERIAL_PORT3_DMA9_IN
|
|||
help
|
||||
Enables the DMA9 input channel for ser3 (ttyS3).
|
||||
If you do not enable DMA, an interrupt for each character will be
|
||||
used when receiveing data.
|
||||
used when receiving data.
|
||||
Normally you want to use DMA, unless you use the DMA channel for
|
||||
something else.
|
||||
|
||||
|
|
|
@ -565,7 +565,7 @@ config ROMVEC
|
|||
depends on ROM
|
||||
help
|
||||
This is almost always the same as the base of the ROM. Since on all
|
||||
68000 type varients the vectors are at the base of the boot device
|
||||
68000 type variants the vectors are at the base of the boot device
|
||||
on system startup.
|
||||
|
||||
config ROMVECSIZE
|
||||
|
@ -574,7 +574,7 @@ config ROMVECSIZE
|
|||
depends on ROM
|
||||
help
|
||||
Define the size of the vector region in ROM. For most 68000
|
||||
varients this would be 0x400 bytes in size. Set to 0 if you do
|
||||
variants this would be 0x400 bytes in size. Set to 0 if you do
|
||||
not want a vector region at the start of the ROM.
|
||||
|
||||
config ROMSTART
|
||||
|
|
|
@ -865,7 +865,7 @@ config MIPS_DISABLE_OBSOLETE_IDE
|
|||
bool
|
||||
|
||||
#
|
||||
# Endianess selection. Suffiently obscure so many users don't know what to
|
||||
# Endianess selection. Sufficiently obscure so many users don't know what to
|
||||
# answer,so we try hard to limit the available choices. Also the use of a
|
||||
# choice statement should be more obvious to the user.
|
||||
#
|
||||
|
@ -874,7 +874,7 @@ choice
|
|||
help
|
||||
Some MIPS machines can be configured for either little or big endian
|
||||
byte order. These modes require different kernels and a different
|
||||
Linux distribution. In general there is one prefered byteorder for a
|
||||
Linux distribution. In general there is one preferred byteorder for a
|
||||
particular system but some systems are just as commonly used in the
|
||||
one or the other endianess.
|
||||
|
||||
|
|
|
@ -425,7 +425,7 @@ config PPC_MAPLE
|
|||
default n
|
||||
help
|
||||
This option enables support for the Maple 970FX Evaluation Board.
|
||||
For more informations, refer to <http://www.970eval.com>
|
||||
For more information, refer to <http://www.970eval.com>
|
||||
|
||||
config PPC_PASEMI
|
||||
depends on PPC_MULTIPLATFORM && PPC64
|
||||
|
|
|
@ -21,7 +21,7 @@ config MPC834x_SYS
|
|||
Be aware that PCI buses can only function when SYS board is plugged
|
||||
into the PIB (Platform IO Board) board from Freescale which provide
|
||||
3 PCI slots. The PIBs PCI initialization is the bootloader's
|
||||
responsiblilty.
|
||||
responsibility.
|
||||
|
||||
config MPC834x_ITX
|
||||
bool "Freescale MPC834x ITX"
|
||||
|
@ -30,7 +30,7 @@ config MPC834x_ITX
|
|||
This option enables support for the MPC 834x ITX evaluation board.
|
||||
|
||||
Be aware that PCI initialization is the bootloader's
|
||||
responsiblilty.
|
||||
responsibility.
|
||||
|
||||
config MPC8360E_PB
|
||||
bool "Freescale MPC8360E PB"
|
||||
|
|
|
@ -724,7 +724,7 @@ config MPC834x_SYS
|
|||
Be aware that PCI buses can only function when SYS board is plugged
|
||||
into the PIB (Platform IO Board) board from Freescale which provide
|
||||
3 PCI slots. The PIBs PCI initialization is the bootloader's
|
||||
responsiblilty.
|
||||
responsibility.
|
||||
|
||||
config EV64360
|
||||
bool "Marvell-EV64360BP"
|
||||
|
|
|
@ -217,7 +217,7 @@ config SH_SHMIN
|
|||
bool "SHMIN"
|
||||
select CPU_SUBTYPE_SH7706
|
||||
help
|
||||
Select SHMIN if configureing for the SHMIN board
|
||||
Select SHMIN if configuring for the SHMIN board.
|
||||
|
||||
config SH_UNKNOWN
|
||||
bool "BareCPU"
|
||||
|
|
|
@ -212,8 +212,8 @@ config SPARC_LED
|
|||
tristate "Sun4m LED driver"
|
||||
help
|
||||
This driver toggles the front-panel LED on sun4m systems
|
||||
in a user-specifyable manner. It's state can be probed
|
||||
by reading /proc/led and it's blinking mode can be changed
|
||||
in a user-specifiable manner. Its state can be probed
|
||||
by reading /proc/led and its blinking mode can be changed
|
||||
via writes to /proc/led
|
||||
|
||||
source "fs/Kconfig.binfmt"
|
||||
|
|
|
@ -994,7 +994,7 @@ config HPET
|
|||
help
|
||||
If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
|
||||
open selects one of the timers supported by the HPET. The timers are
|
||||
non-periodioc and/or periodic.
|
||||
non-periodic and/or periodic.
|
||||
|
||||
config HPET_RTC_IRQ
|
||||
bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
|
||||
|
|
|
@ -24,7 +24,7 @@ config VIDEO_HELPER_CHIPS_AUTO
|
|||
decode audio/video standards. This option will autoselect
|
||||
all pertinent modules to each selected video module.
|
||||
|
||||
Unselect this only if you know exaclty what you are doing, since
|
||||
Unselect this only if you know exactly what you are doing, since
|
||||
it may break support on some boards.
|
||||
|
||||
In doubt, say Y.
|
||||
|
|
|
@ -607,7 +607,7 @@ config MTD_BAST_MAXSIZE
|
|||
default "4"
|
||||
|
||||
config MTD_SHARP_SL
|
||||
bool "ROM maped on Sharp SL Series"
|
||||
bool "ROM mapped on Sharp SL Series"
|
||||
depends on MTD && ARCH_PXA
|
||||
help
|
||||
This enables access to the flash chip on the Sharp SL Series of PDAs.
|
||||
|
|
|
@ -32,7 +32,7 @@ config IFB
|
|||
tristate "Intermediate Functional Block support"
|
||||
depends on NET_CLS_ACT
|
||||
---help---
|
||||
This is an intermidiate driver that allows sharing of
|
||||
This is an intermediate driver that allows sharing of
|
||||
resources.
|
||||
To compile this driver as a module, choose M here: the module
|
||||
will be called ifb. If you want to use more than one ifb
|
||||
|
@ -2136,7 +2136,7 @@ config SK98LIN
|
|||
This driver supports the original Yukon chipset. A cleaner driver is
|
||||
also available (skge) which seems to work better than this one.
|
||||
|
||||
This driver does not support the newer Yukon2 chipset. A seperate
|
||||
This driver does not support the newer Yukon2 chipset. A separate
|
||||
driver, sky2, is provided to support Yukon2-based adapters.
|
||||
|
||||
The following adapters are supported by this driver:
|
||||
|
|
|
@ -61,8 +61,8 @@ config FIXED_PHY
|
|||
depends on PHYLIB
|
||||
---help---
|
||||
Adds the driver to PHY layer to cover the boards that do not have any PHY bound,
|
||||
but with the ability to manipulate with speed/link in software. The relavant MII
|
||||
speed/duplex parameters could be effectively handled in user-specified fuction.
|
||||
but with the ability to manipulate the speed/link in software. The relevant MII
|
||||
speed/duplex parameters could be effectively handled in a user-specified function.
|
||||
Currently tested with mpc866ads.
|
||||
|
||||
config FIXED_MII_10_FDX
|
||||
|
|
|
@ -27,7 +27,7 @@ config PCI_MULTITHREAD_PROBE
|
|||
smaller speedup on single processor machines.
|
||||
|
||||
But it can also cause lots of bad things to happen. A number
|
||||
of PCI drivers can not properly handle running in this way,
|
||||
of PCI drivers cannot properly handle running in this way,
|
||||
some will just not work properly at all, while others might
|
||||
decide to blow up power supplies with a huge load all at once,
|
||||
so use this option at your own risk.
|
||||
|
|
|
@ -16,7 +16,7 @@ config SPI
|
|||
controller and a chipselect. Most SPI slaves don't support
|
||||
dynamic device discovery; some are even write-only or read-only.
|
||||
|
||||
SPI is widely used by microcontollers to talk with sensors,
|
||||
SPI is widely used by microcontrollers to talk with sensors,
|
||||
eeprom and flash memory, codecs and various other controller
|
||||
chips, analog to digital (and d-to-a) converters, and more.
|
||||
MMC and SD cards can be accessed using SPI protocol; and for
|
||||
|
|
|
@ -153,7 +153,7 @@ config USB_U132_HCD
|
|||
adapter will *NOT* work with PC cards that do not contain an OHCI
|
||||
controller.
|
||||
|
||||
For those PC cards that contain multiple OHCI controllers only ther
|
||||
For those PC cards that contain multiple OHCI controllers only the
|
||||
first one is used.
|
||||
|
||||
The driver consists of two modules, the "ftdi-elan" module is a
|
||||
|
|
|
@ -1145,7 +1145,7 @@ config BEFS_FS
|
|||
help
|
||||
The BeOS File System (BeFS) is the native file system of Be, Inc's
|
||||
BeOS. Notable features include support for arbitrary attributes
|
||||
on files and directories, and database-like indeces on selected
|
||||
on files and directories, and database-like indices on selected
|
||||
attributes. (Also note that this driver doesn't make those features
|
||||
available at this time). It is a 64 bit filesystem, so it supports
|
||||
extremely large volumes and files.
|
||||
|
|
|
@ -64,11 +64,11 @@ source "sound/arm/Kconfig"
|
|||
|
||||
source "sound/mips/Kconfig"
|
||||
|
||||
# the following will depenend on the order of config.
|
||||
# the following will depend on the order of config.
|
||||
# here assuming USB is defined before ALSA
|
||||
source "sound/usb/Kconfig"
|
||||
|
||||
# the following will depenend on the order of config.
|
||||
# the following will depend on the order of config.
|
||||
# here assuming PCMCIA is defined before ALSA
|
||||
source "sound/pcmcia/Kconfig"
|
||||
|
||||
|
|
Loading…
Reference in a new issue