Fix typos in Documentation/: 'Q'-'R'
This patch fixes typos in various Documentation txts. The patch addresses some words starting with the letters 'Q'-'R'. Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
Matt LaPlante
Adrian Bunk
parent
84eb8d0608
commit
d6bc8ac9e1
26 changed files with 40 additions and 40 deletions
|
|
@ -267,7 +267,7 @@ y = The number of MSI capable devices populated in the system.
|
|||
vector reserved to avoid the case where some MSI-X capable
|
||||
drivers may attempt to claim all available vector resources.
|
||||
|
||||
z = The number of MSI-X capable devices pupulated in the system.
|
||||
z = The number of MSI-X capable devices populated in the system.
|
||||
This policy ensures that maximum (x - y) is distributed
|
||||
evenly among MSI-X capable devices.
|
||||
|
||||
|
|
|
|||
|
|
@ -783,7 +783,7 @@ all the outstanding requests. There's a third helper to do that:
|
|||
|
||||
blk_queue_invalidate_tags(request_queue_t *q)
|
||||
|
||||
Clear the internal block tag queue and readd all the pending requests
|
||||
Clear the internal block tag queue and re-add all the pending requests
|
||||
to the request queue. The driver will receive them again on the
|
||||
next request_fn run, just like it did the first time it encountered
|
||||
them.
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@ the driver to that device.
|
|||
|
||||
A driver's probe() may return a negative errno value to indicate that
|
||||
the driver did not bind to this device, in which case it should have
|
||||
released all reasources it allocated.
|
||||
released all resources it allocated.
|
||||
|
||||
int (*remove) (struct device * dev);
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ WARNING
|
|||
Make sure you understand that this is alpha software. This means that the
|
||||
implementation is neither complete nor well-tested.
|
||||
|
||||
I DISCLAIM ALL RESPONSIBILTY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
|
||||
I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
|
||||
|
||||
LICENSE
|
||||
=====
|
||||
|
|
|
|||
|
|
@ -422,7 +422,7 @@ support mkdir(2) or rmdir(2) either. It only allows rename(2). The
|
|||
"pending" directory does allow mkdir(2) and rmdir(2). An item is
|
||||
created in the "pending" directory. Its attributes can be modified at
|
||||
will. Userspace commits the item by renaming it into the "live"
|
||||
directory. At this point, the subsystem recieves the ->commit_item()
|
||||
directory. At this point, the subsystem receives the ->commit_item()
|
||||
callback. If all required attributes are filled to satisfaction, the
|
||||
method returns zero and the item is moved to the "live" directory.
|
||||
|
||||
|
|
|
|||
|
|
@ -450,7 +450,7 @@ his laptop (the location of sensors may vary on other models):
|
|||
|
||||
No commands can be written to this file.
|
||||
|
||||
EXPERIMENTAL: Embedded controller reigster dump -- /proc/acpi/ibm/ecdump
|
||||
EXPERIMENTAL: Embedded controller register dump -- /proc/acpi/ibm/ecdump
|
||||
------------------------------------------------------------------------
|
||||
|
||||
This feature is marked EXPERIMENTAL because the implementation
|
||||
|
|
|
|||
|
|
@ -281,7 +281,7 @@ Summary of ide driver parameters for kernel command line
|
|||
|
||||
"idex=serialize" : do not overlap operations on idex. Please note
|
||||
that you will have to specify this option for
|
||||
both the respecitve primary and secondary channel
|
||||
both the respective primary and secondary channel
|
||||
to take effect.
|
||||
|
||||
"idex=four" : four drives on idex and ide(x^1) share same ports
|
||||
|
|
|
|||
|
|
@ -79,10 +79,10 @@ JOY0DAT Y7 Y6 Y5 Y4 Y3 Y2 Y1 Y0 X7 X6 X5 X4 X3 X2 X1 X0
|
|||
JOY1DAT Y7 Y6 Y5 Y4 Y3 Y2 Y1 Y0 X7 X6 X5 X4 X3 X2 X1 X0
|
||||
|
||||
0=LEFT CONTROLLER PAIR, 1=RIGHT CONTROLLER PAIR.
|
||||
(4 counters total).The bit usage for both left and right
|
||||
(4 counters total). The bit usage for both left and right
|
||||
addresses is shown below. Each 6 bit counter (Y7-Y2,X7-X2) is
|
||||
clocked by 2 of the signals input from the mouse serial
|
||||
stream. Starting with first bit recived:
|
||||
stream. Starting with first bit received:
|
||||
|
||||
+-------------------+-----------------------------------------+
|
||||
| Serial | Bit Name | Description |
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ selected.
|
|||
4.2 Absolute Position reporting
|
||||
|
||||
The ikbd can also maintain absolute mouse position. Commands exist for
|
||||
reseting the mouse position, setting X/Y scaling, and interrogating the
|
||||
resetting the mouse position, setting X/Y scaling, and interrogating the
|
||||
current mouse position.
|
||||
|
||||
4.3 Mouse Cursor Key Mode
|
||||
|
|
|
|||
|
|
@ -456,8 +456,8 @@ uses the following kernel/module command line:
|
|||
8 | Sony PSX DDR controller
|
||||
9 | SNES mouse
|
||||
|
||||
The exact type of the PSX controller type is autoprobed when used so
|
||||
hot swapping should work (but is not recomended).
|
||||
The exact type of the PSX controller type is autoprobed when used, so
|
||||
hot swapping should work (but is not recommended).
|
||||
|
||||
Should you want to use more than one of parallel ports at once, you can use
|
||||
gamecon.map2 and gamecon.map3 as additional command line parameters for two
|
||||
|
|
|
|||
|
|
@ -307,8 +307,8 @@ Each directory contains:
|
|||
This applies only to raid1 arrays.
|
||||
spare - device is working, but not a full member.
|
||||
This includes spares that are in the process
|
||||
of being recoverred to
|
||||
This list make grow in future.
|
||||
of being recovered to
|
||||
This list may grow in future.
|
||||
This can be written to.
|
||||
Writing "faulty" simulates a failure on the device.
|
||||
Writing "remove" removes the device from the array.
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Transmit path guidelines:
|
|||
...
|
||||
}
|
||||
|
||||
And then at the end of your TX reclaimation event handling:
|
||||
And then at the end of your TX reclamation event handling:
|
||||
|
||||
if (netif_queue_stopped(dp->dev) &&
|
||||
TX_BUFFS_AVAIL(dp) > (MAX_SKB_FRAGS + 1))
|
||||
|
|
|
|||
|
|
@ -495,7 +495,7 @@ icmp_errors_use_inbound_ifaddr - BOOLEAN
|
|||
|
||||
Note that if no primary address exists for the interface selected,
|
||||
then the primary address of the first non-loopback interface that
|
||||
has one will be used regarldess of this setting.
|
||||
has one will be used regardless of this setting.
|
||||
|
||||
Default: 0
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ History
|
|||
Per-interface rather than per-driver message level setting.
|
||||
More selective control over the type of messages emitted.
|
||||
|
||||
The netif_msg recommandation adds these features with only a minor
|
||||
The netif_msg recommendation adds these features with only a minor
|
||||
complexity and code size increase.
|
||||
|
||||
The recommendation is the following points
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ red: green: meaning:
|
|||
|
||||
- - no frame-sync, no signal received, or signal SNAFU.
|
||||
- on "Everything is OK"
|
||||
on on Recepion is ok, but the remote end sends Remote Alarm
|
||||
on on Reception is ok, but the remote end sends Remote Alarm
|
||||
on - The interface is unconfigured
|
||||
|
||||
-----------------------------------------------------------------
|
||||
|
|
@ -257,7 +257,7 @@ which begin with '//' are the comments.
|
|||
// No alarms - Everything OK
|
||||
//
|
||||
// LOS - Loss Of Signal - No signal sensed on the input
|
||||
// AIS - Alarm Indication Signal - The remot side sends '11111111'-s,
|
||||
// AIS - Alarm Indication Signal - The remote side sends '11111111'-s,
|
||||
// it tells, that there's an error condition, or it's not
|
||||
// initialised.
|
||||
// AUXP - Auxiliary Pattern Indication - 01010101.. received.
|
||||
|
|
|
|||
|
|
@ -245,7 +245,7 @@ the block to RAM before passing it to the kernel.
|
|||
---------
|
||||
|
||||
The kernel is entered with r3 pointing to an area of memory that is
|
||||
roughtly described in include/asm-powerpc/prom.h by the structure
|
||||
roughly described in include/asm-powerpc/prom.h by the structure
|
||||
boot_param_header:
|
||||
|
||||
struct boot_param_header {
|
||||
|
|
@ -1068,13 +1068,13 @@ while all this has been defined and implemented.
|
|||
around. It contains no internal offsets or pointers for this
|
||||
purpose.
|
||||
|
||||
- An example of code for iterating nodes & retreiving properties
|
||||
- An example of code for iterating nodes & retrieving properties
|
||||
directly from the flattened tree format can be found in the kernel
|
||||
file arch/ppc64/kernel/prom.c, look at scan_flat_dt() function,
|
||||
it's usage in early_init_devtree(), and the corresponding various
|
||||
its usage in early_init_devtree(), and the corresponding various
|
||||
early_init_dt_scan_*() callbacks. That code can be re-used in a
|
||||
GPL bootloader, and as the author of that code, I would be happy
|
||||
do discuss possible free licencing to any vendor who wishes to
|
||||
to discuss possible free licencing to any vendor who wishes to
|
||||
integrate all or part of this code into a non-GPL bootloader.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ EEH-isolated, there is a firmware call it can make to determine if
|
|||
this is the case. If so, then the device driver should put itself
|
||||
into a consistent state (given that it won't be able to complete any
|
||||
pending work) and start recovery of the card. Recovery normally
|
||||
would consist of reseting the PCI device (holding the PCI #RST
|
||||
would consist of resetting the PCI device (holding the PCI #RST
|
||||
line high for two seconds), followed by setting up the device
|
||||
config space (the base address registers (BAR's), latency timer,
|
||||
cache line size, interrupt line, and so on). This is followed by a
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ determine the device driver owning the device that raised the interrupt.
|
|||
In order not to introduce a new I/O concept to the common Linux code,
|
||||
Linux/390 preserves the IRQ concept and semantically maps the ESA/390
|
||||
subchannels to Linux as IRQs. This allows Linux/390 to support up to 64k
|
||||
different IRQs, uniquely representig a single device each.
|
||||
different IRQs, uniquely representing a single device each.
|
||||
|
||||
Up to kernel 2.4, Linux/390 used to provide interfaces via the IRQ (subchannel).
|
||||
For internal use of the common I/O layer, these are still there. However,
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ notify: This function is called by the common I/O layer for some state changes
|
|||
* In online state, device detached (CIO_GONE) or last path gone
|
||||
(CIO_NO_PATH). The driver must return !0 to keep the device; for
|
||||
return code 0, the device will be deleted as usual (also when no
|
||||
notify function is registerd). If the driver wants to keep the
|
||||
notify function is registered). If the driver wants to keep the
|
||||
device, it is moved into disconnected state.
|
||||
* In disconnected state, device operational again (CIO_OPER). The
|
||||
common I/O layer performs some sanity checks on device number and
|
||||
|
|
|
|||
|
|
@ -36,18 +36,18 @@ Socket 1:
|
|||
product info: "IO DATA", "CBSC16 ", "1"
|
||||
|
||||
|
||||
[2] Get Linux kernel source, and extract it to /usr/src.
|
||||
Because NinjaSCSI driver requiers some SCSI header files in Linux kernel
|
||||
source.
|
||||
I recomend rebuilding your kernel. This eliminate some versioning problem.
|
||||
[2] Get the Linux kernel source, and extract it to /usr/src.
|
||||
Because the NinjaSCSI driver requires some SCSI header files in Linux
|
||||
kernel source, I recommend rebuilding your kernel; this eliminates
|
||||
some versioning problems.
|
||||
$ cd /usr/src
|
||||
$ tar -zxvf linux-x.x.x.tar.gz
|
||||
$ cd linux
|
||||
$ make config
|
||||
...
|
||||
|
||||
[3] If you use this driver with Kernel 2.2, Unpack pcmcia-cs in some directory
|
||||
and make & install. This driver requies pcmcia-cs header file.
|
||||
[3] If you use this driver with Kernel 2.2, unpack pcmcia-cs in some directory
|
||||
and make & install. This driver requires the pcmcia-cs header file.
|
||||
$ cd /usr/src
|
||||
$ tar zxvf cs-pcmcia-cs-3.x.x.tar.gz
|
||||
...
|
||||
|
|
|
|||
|
|
@ -182,10 +182,10 @@ When the problem is related with PCM, first try to turn on xrun_debug
|
|||
mode. This will give you the kernel messages when and where xrun
|
||||
happened.
|
||||
|
||||
If it's really a bug, report it with the following information
|
||||
If it's really a bug, report it with the following information:
|
||||
|
||||
- the name of the driver/card, show in /proc/asound/cards
|
||||
- the reigster dump, if available (e.g. card*/cmipci)
|
||||
- the register dump, if available (e.g. card*/cmipci)
|
||||
|
||||
when it's a PCM problem,
|
||||
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ in your .remove method.
|
|||
|
||||
Any memory allocated, registers mapped, IRQs registered,
|
||||
etc. must be undone by your .remove method so that all resources
|
||||
of your device are relased by the time it returns.
|
||||
of your device are released by the time it returns.
|
||||
|
||||
You should _NOT_ use the for_each_sbus(), for_each_sbusdev(),
|
||||
and for_all_sbusdev() interfaces. They are deprecated, will be
|
||||
|
|
|
|||
|
|
@ -3903,9 +3903,9 @@
|
|||
|
||||
1133..55.. UUMMLL ddooeessnn''tt wwoorrkk wwhheenn //ttmmpp iiss aann NNFFSS ffiilleessyysstteemm
|
||||
|
||||
This seems to be a similar situation with the resierfs problem above.
|
||||
This seems to be a similar situation with the ReiserFS problem above.
|
||||
Some versions of NFS seems not to handle mmap correctly, which UML
|
||||
depends on. The workaround is have /tmp be non-NFS directory.
|
||||
depends on. The workaround is have /tmp be a non-NFS directory.
|
||||
|
||||
|
||||
1133..66.. UUMMLL hhaannggss oonn bboooott wwhheenn ccoommppiilleedd wwiitthh ggpprrooff ssuuppppoorrtt
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ provide for a handler)
|
|||
GP_SAMPLE register is at 0x35C058
|
||||
|
||||
Bits are then right shifted into the GP_SAMPLE register at the specified
|
||||
rate; you get an interrupt when a full DWORD is recieved.
|
||||
rate; you get an interrupt when a full DWORD is received.
|
||||
You need to recover the actual RC5 bits out of the (oversampled) IR sensor
|
||||
bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data) An
|
||||
actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment.
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ provide for a handler)
|
|||
GP_SAMPLE register is at 0x35C058
|
||||
|
||||
Bits are then right shifted into the GP_SAMPLE register at the specified
|
||||
rate; you get an interrupt when a full DWORD is recieved.
|
||||
rate; you get an interrupt when a full DWORD is received.
|
||||
You need to recover the actual RC5 bits out of the (oversampled) IR sensor
|
||||
bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data) An
|
||||
actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment.
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ Idle loop
|
|||
Rebooting
|
||||
|
||||
reboot=b[ios] | t[riple] | k[bd] [, [w]arm | [c]old]
|
||||
bios Use the CPU reboto vector for warm reset
|
||||
bios Use the CPU reboot vector for warm reset
|
||||
warm Don't set the cold reboot flag
|
||||
cold Set the cold reboot flag
|
||||
triple Force a triple fault (init)
|
||||
|
|
|
|||
Loading…
Reference in a new issue