forked from Minki/linux
Fix several typos in drivers/
Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
parent
c73a668c09
commit
095096038d
@ -64,7 +64,7 @@ config DELL_RBU
|
||||
help
|
||||
Say m if you want to have the option of updating the BIOS for your
|
||||
DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
|
||||
supporting application to comunicate with the BIOS regarding the new
|
||||
supporting application to communicate with the BIOS regarding the new
|
||||
image for the image update to take effect.
|
||||
See <file:Documentation/dell_rbu.txt> for more details on the driver.
|
||||
|
||||
|
@ -333,10 +333,10 @@ config I2C_PARPORT_LIGHT
|
||||
|
||||
This driver is a light version of i2c-parport. It doesn't depend
|
||||
on the parport driver, and uses direct I/O access instead. This
|
||||
might be prefered on embedded systems where wasting memory for
|
||||
might be preferred on embedded systems where wasting memory for
|
||||
the clean but heavy parport handling is not an option. The
|
||||
drawback is a reduced portability and the impossibility to
|
||||
dasiy-chain other parallel port devices.
|
||||
daisy-chain other parallel port devices.
|
||||
|
||||
Don't say Y here if you said Y or M to i2c-parport. Saying M to
|
||||
both is possible but both modules should not be loaded at the same
|
||||
|
@ -140,7 +140,7 @@ config IEEE1394_SBP2_PHYS_DMA
|
||||
help
|
||||
This builds sbp2 for use with non-OHCI host adapters which do not
|
||||
support physical DMA or for when ohci1394 is run with phys_dma=0.
|
||||
Physical DMA is data movement without assistence of the drivers'
|
||||
Physical DMA is data movement without assistance of the drivers'
|
||||
interrupt handlers. This option includes the interrupt handlers
|
||||
that are required in absence of this hardware feature.
|
||||
|
||||
|
@ -177,7 +177,7 @@ config KEYBOARD_HIL_OLD
|
||||
However, it has been thoroughly tested and is stable.
|
||||
|
||||
If you want full HIL support including support for multiple
|
||||
keyboards, mices and tablets, you have to enable the
|
||||
keyboards, mice, and tablets, you have to enable the
|
||||
"HP System Device Controller i8042 Support" in the input/serio
|
||||
submenu.
|
||||
|
||||
|
@ -115,9 +115,9 @@ config HP_SDC
|
||||
depends on GSC && SERIO
|
||||
default y
|
||||
---help---
|
||||
This option enables supports for the the "System Device
|
||||
This option enables support for the "System Device
|
||||
Controller", an i8042 carrying microcode to manage a
|
||||
few miscellanous devices on some Hewlett Packard systems.
|
||||
few miscellaneous devices on some Hewlett Packard systems.
|
||||
The SDC itself contains a 10ms resolution timer/clock capable
|
||||
of delivering interrupts on a periodic and one-shot basis.
|
||||
The SDC may also be connected to a battery-backed real-time
|
||||
|
@ -47,7 +47,7 @@ config ISDN_DIVAS_MAINT
|
||||
tristate "DIVA Maint driver support"
|
||||
depends on ISDN_DIVAS && m
|
||||
help
|
||||
Enable Divas Maintainance driver.
|
||||
Enable Divas Maintenance driver.
|
||||
|
||||
endmenu
|
||||
|
||||
|
@ -321,7 +321,7 @@ config HISAX_HFC_PCI
|
||||
help
|
||||
This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
|
||||
|
||||
For more informations see under
|
||||
For more information see under
|
||||
<file:Documentation/isdn/README.hfc-pci>.
|
||||
|
||||
config HISAX_W6692
|
||||
|
@ -186,7 +186,7 @@ config THERM_ADT746X
|
||||
depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64
|
||||
help
|
||||
This driver provides some thermostat and fan control for the
|
||||
iBook G4, and the ATI based aluminium PowerBooks, allowing slighlty
|
||||
iBook G4, and the ATI based aluminium PowerBooks, allowing slightly
|
||||
better fan behaviour by default, and some manual control.
|
||||
|
||||
config THERM_PM72
|
||||
|
@ -56,7 +56,7 @@ config DVB_CINERGYT2_QUERY_INTERVAL
|
||||
measurements.
|
||||
|
||||
Please keep in mind that these updates cause traffic on the tuner
|
||||
control bus and thus may or may not affect receiption sensitivity.
|
||||
control bus and thus may or may not affect reception sensitivity.
|
||||
|
||||
The default value should be a safe choice for common applications.
|
||||
|
||||
|
@ -351,7 +351,7 @@ config VIDEO_SAA6588
|
||||
help
|
||||
Support for Radio Data System (RDS) decoder. This allows seeing
|
||||
radio station identification transmitted using this standard.
|
||||
Currentlly, it works only with bt8x8 chips.
|
||||
Currently, it works only with bt8x8 chips.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called saa6588.
|
||||
|
@ -270,7 +270,7 @@ config MTD_JEDEC
|
||||
tristate "JEDEC device support"
|
||||
depends on MTD && MTD_OBSOLETE_CHIPS && BROKEN
|
||||
help
|
||||
Enable older older JEDEC flash interface devices for self
|
||||
Enable older JEDEC flash interface devices for self
|
||||
programming flash. It is commonly used in older AMD chips. It is
|
||||
only called JEDEC because the JEDEC association
|
||||
<http://www.jedec.org/> distributes the identification codes for the
|
||||
|
@ -21,7 +21,7 @@ config MTD_NAND_VERIFY_WRITE
|
||||
NAND flash device internally checks only bits transitioning
|
||||
from 1 to 0. There is a rare possibility that even though the
|
||||
device thinks the write was successful, a bit could have been
|
||||
flipped accidentaly due to device wear or something else.
|
||||
flipped accidentally due to device wear or something else.
|
||||
|
||||
config MTD_NAND_ECC_SMC
|
||||
bool "NAND ECC Smart Media byte order"
|
||||
|
@ -21,7 +21,7 @@ config MTD_ONENAND_VERIFY_WRITE
|
||||
OneNAND flash device internally checks only bits transitioning
|
||||
from 1 to 0. There is a rare possibility that even though the
|
||||
device thinks the write was successful, a bit could have been
|
||||
flipped accidentaly due to device wear or something else.
|
||||
flipped accidentally due to device wear or something else.
|
||||
|
||||
config MTD_ONENAND_GENERIC
|
||||
tristate "OneNAND Flash device via platform device driver"
|
||||
|
@ -301,7 +301,7 @@ config HERMES
|
||||
tristate "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)"
|
||||
depends on NET_RADIO && (PPC_PMAC || PCI || PCMCIA)
|
||||
---help---
|
||||
A driver for 802.11b wireless cards based based on the "Hermes" or
|
||||
A driver for 802.11b wireless cards based on the "Hermes" or
|
||||
Intersil HFA384x (Prism 2) MAC controller. This includes the vast
|
||||
majority of the PCMCIA 802.11b cards (which are nearly all rebadges)
|
||||
- except for the Cisco/Aironet cards. Cards supported include the
|
||||
|
@ -15,4 +15,4 @@ config RAPIDIO_DISC_TIMEOUT
|
||||
default "30"
|
||||
---help---
|
||||
Amount of time a discovery node waits for a host to complete
|
||||
enumeration beforing giving up.
|
||||
enumeration before giving up.
|
||||
|
@ -40,10 +40,10 @@ config SCSI_PROC_FS
|
||||
default y
|
||||
---help---
|
||||
This option enables support for the various files in
|
||||
/proc/scsi. In Linux 2.6 this has been superceeded by
|
||||
/proc/scsi. In Linux 2.6 this has been superseded by
|
||||
files in sysfs but many legacy applications rely on this.
|
||||
|
||||
If unusure say Y.
|
||||
If unsure say Y.
|
||||
|
||||
comment "SCSI support type (disk, tape, CD-ROM)"
|
||||
depends on SCSI
|
||||
|
@ -22,12 +22,12 @@ config AIC79XX_CMDS_PER_DEVICE
|
||||
to be used for any device. The aic7xxx driver will automatically
|
||||
vary this number based on device behavior. For devices with a
|
||||
fixed maximum, the driver will eventually lock to this maximum
|
||||
and display a console message inidicating this value.
|
||||
and display a console message indicating this value.
|
||||
|
||||
Due to resource allocation issues in the Linux SCSI mid-layer, using
|
||||
a high number of commands per device may result in memory allocation
|
||||
failures when many devices are attached to the system. For this reason,
|
||||
the default is set to 32. Higher values may result in higer performance
|
||||
the default is set to 32. Higher values may result in higher performance
|
||||
on some devices. The upper bound is 253. 0 disables tagged queueing.
|
||||
|
||||
Per device tag depth can be controlled via the kernel command line
|
||||
|
@ -27,12 +27,12 @@ config AIC7XXX_CMDS_PER_DEVICE
|
||||
to be used for any device. The aic7xxx driver will automatically
|
||||
vary this number based on device behavior. For devices with a
|
||||
fixed maximum, the driver will eventually lock to this maximum
|
||||
and display a console message inidicating this value.
|
||||
and display a console message indicating this value.
|
||||
|
||||
Due to resource allocation issues in the Linux SCSI mid-layer, using
|
||||
a high number of commands per device may result in memory allocation
|
||||
failures when many devices are attached to the system. For this reason,
|
||||
the default is set to 32. Higher values may result in higer performance
|
||||
the default is set to 32. Higher values may result in higher performance
|
||||
on some devices. The upper bound is 253. 0 disables tagged queueing.
|
||||
|
||||
Per device tag depth can be controlled via the kernel command line
|
||||
|
@ -121,7 +121,7 @@ config SERIAL_8250_RUNTIME_UARTS
|
||||
default "4"
|
||||
help
|
||||
Set this to the maximum number of serial ports you want
|
||||
the kernel to register at boot time. This can be overriden
|
||||
the kernel to register at boot time. This can be overridden
|
||||
with the module parameter "nr_uarts", or boot-time parameter
|
||||
8250.nr_uarts
|
||||
|
||||
@ -205,7 +205,7 @@ config SERIAL_8250_BOCA
|
||||
depends on SERIAL_8250 != n && ISA && SERIAL_8250_MANY_PORTS
|
||||
help
|
||||
Say Y here if you have a Boca serial board. Please read the Boca
|
||||
mini-HOWTO, avaialble from <http://www.tldp.org/docs.html#howto>
|
||||
mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>
|
||||
|
||||
To compile this driver as a module, choose M here: the module
|
||||
will be called 8250_boca.
|
||||
@ -667,7 +667,7 @@ config SERIAL_68328
|
||||
depends on M68328 || M68EZ328 || M68VZ328
|
||||
help
|
||||
This driver supports the built-in serial port of the Motorola 68328
|
||||
(standard, EZ and VZ varities).
|
||||
(standard, EZ and VZ varieties).
|
||||
|
||||
config SERIAL_68328_RTS_CTS
|
||||
bool "Support RTS/CTS on 68328 serial port"
|
||||
|
@ -119,7 +119,7 @@ config USB_STORAGE_ALAUDA
|
||||
Say Y here to include additional code to support the Olympus MAUSB-10
|
||||
and Fujifilm DPC-R1 USB Card reader/writer devices.
|
||||
|
||||
These devices are based on the Alauda chip and support support both
|
||||
These devices are based on the Alauda chip and support both
|
||||
XD and SmartMedia cards.
|
||||
|
||||
config USB_STORAGE_ONETOUCH
|
||||
|
@ -403,7 +403,7 @@ config FB_ARC
|
||||
is based on the KS-108 lcd controller and is typically a matrix
|
||||
of 2*n chips. This driver was tested with a 128x64 panel. This
|
||||
driver supports it for use with x86 SBCs through a 16 bit GPIO
|
||||
interface (8 bit data, 8 bit control). If you anticpate using
|
||||
interface (8 bit data, 8 bit control). If you anticipate using
|
||||
this driver, say Y or M; otherwise say N. You must specify the
|
||||
GPIO IO address to be used for setting control and data.
|
||||
|
||||
@ -771,7 +771,7 @@ config FB_RIVA_DEBUG
|
||||
default n
|
||||
help
|
||||
Say Y here if you want the Riva driver to output all sorts
|
||||
of debugging informations to provide to the maintainer when
|
||||
of debugging information to provide to the maintainer when
|
||||
something goes wrong.
|
||||
|
||||
config FB_RIVA_BACKLIGHT
|
||||
@ -865,7 +865,7 @@ config FB_INTEL_DEBUG
|
||||
depends on FB_INTEL
|
||||
---help---
|
||||
Say Y here if you want the Intel driver to output all sorts
|
||||
of debugging informations to provide to the maintainer when
|
||||
of debugging information to provide to the maintainer when
|
||||
something goes wrong.
|
||||
|
||||
config FB_INTEL_I2C
|
||||
@ -1062,7 +1062,7 @@ config FB_RADEON_DEBUG
|
||||
default n
|
||||
help
|
||||
Say Y here if you want the Radeon driver to output all sorts
|
||||
of debugging informations to provide to the maintainer when
|
||||
of debugging information to provide to the maintainer when
|
||||
something goes wrong.
|
||||
|
||||
config FB_ATY128
|
||||
|
@ -21,7 +21,7 @@ config W1_CON
|
||||
There are three types of messages between w1 core and userspace:
|
||||
1. Events. They are generated each time new master or slave device found
|
||||
either due to automatic or requested search.
|
||||
2. Userspace commands. Includes read/write and search/alarm search comamnds.
|
||||
2. Userspace commands. Includes read/write and search/alarm search commands.
|
||||
3. Replies to userspace commands.
|
||||
|
||||
source drivers/w1/masters/Kconfig
|
||||
|
Loading…
Reference in New Issue
Block a user