Commit 01dd2fbf authored by Matt LaPlante's avatar Matt LaPlante Committed by Adrian Bunk
Browse files

typo fixes



Most of these fixes were already submitted for old kernel versions, and were
approved, but for some reason they never made it into the releases.

Because this is a consolidation of a couple old missed patches, it touches both
Kconfigs and documentation texts.
Signed-off-by: default avatarMatt LaPlante <kernel1@cyberdogtech.com>
Acked-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: default avatarAdrian Bunk <bunk@kernel.org>
parent 0f035b8e
...@@ -5,7 +5,7 @@ Introduction ...@@ -5,7 +5,7 @@ Introduction
------------ ------------
The kernel provides an interface to manage DMA transfers The kernel provides an interface to manage DMA transfers
using the DMA channels in the cpu, so that the central using the DMA channels in the CPU, so that the central
duty of managing channel mappings, and programming the duty of managing channel mappings, and programming the
channel generators is in one place. channel generators is in one place.
...@@ -17,24 +17,24 @@ DMA Channel Ordering ...@@ -17,24 +17,24 @@ DMA Channel Ordering
channels to all sources, which means that some devices channels to all sources, which means that some devices
have a restricted number of channels that can be used. have a restricted number of channels that can be used.
To allow flexibilty for each cpu type and board, the To allow flexibility for each CPU type and board, the
dma code can be given an dma ordering structure which DMA code can be given a DMA ordering structure which
allows the order of channel search to be specified, as allows the order of channel search to be specified, as
well as allowing the prohibition of certain claims. well as allowing the prohibition of certain claims.
struct s3c24xx_dma_order has a list of channels, and struct s3c24xx_dma_order has a list of channels, and
each channel within has a slot for a list of dma each channel within has a slot for a list of DMA
channel numbers. The slots are searched in order, for channel numbers. The slots are searched in order for
the presence of a dma channel number with DMA_CH_VALID the presence of a DMA channel number with DMA_CH_VALID
orred in. or-ed in.
If the order has the flag DMA_CH_NEVER set, then after If the order has the flag DMA_CH_NEVER set, then after
checking the channel list, the system will return no checking the channel list, the system will return no
found channel, thus denying the request. found channel, thus denying the request.
A board support file can call s3c24xx_dma_order_set() A board support file can call s3c24xx_dma_order_set()
to register an complete ordering set. The routine will to register a complete ordering set. The routine will
copy the data, so the original can be discared with copy the data, so the original can be discarded with
__initdata. __initdata.
......
...@@ -2188,7 +2188,7 @@ Your cooperation is appreciated. ...@@ -2188,7 +2188,7 @@ Your cooperation is appreciated.
136-143 char Unix98 PTY slaves 136-143 char Unix98 PTY slaves
0 = /dev/pts/0 First Unix98 pseudo-TTY 0 = /dev/pts/0 First Unix98 pseudo-TTY
1 = /dev/pts/1 Second Unix98 pesudo-TTY 1 = /dev/pts/1 Second Unix98 pseudo-TTY
... ...
These device nodes are automatically generated with These device nodes are automatically generated with
......
...@@ -32,7 +32,7 @@ braindamaged document, if it's finally working, well, it's working. ...@@ -32,7 +32,7 @@ braindamaged document, if it's finally working, well, it's working.
For one reason or another, low level drivers don't receive as much For one reason or another, low level drivers don't receive as much
attention or testing as core code, and bugs on driver detach or attention or testing as core code, and bugs on driver detach or
initilaization failure doesn't happen often enough to be noticeable. initialization failure don't happen often enough to be noticeable.
Init failure path is worse because it's much less travelled while Init failure path is worse because it's much less travelled while
needs to handle multiple entry points. needs to handle multiple entry points.
...@@ -160,7 +160,7 @@ resources on failure. For example, ...@@ -160,7 +160,7 @@ resources on failure. For example,
devres_release_group(dev, NULL); devres_release_group(dev, NULL);
return err_code; return err_code;
As resource acquision failure usually means probe failure, constructs As resource acquisition failure usually means probe failure, constructs
like above are usually useful in midlayer driver (e.g. libata core like above are usually useful in midlayer driver (e.g. libata core
layer) where interface function shouldn't have side effect on failure. layer) where interface function shouldn't have side effect on failure.
For LLDs, just returning error code suffices in most cases. For LLDs, just returning error code suffices in most cases.
......
...@@ -3,7 +3,7 @@ Deferred IO ...@@ -3,7 +3,7 @@ Deferred IO
Deferred IO is a way to delay and repurpose IO. It uses host memory as a Deferred IO is a way to delay and repurpose IO. It uses host memory as a
buffer and the MMU pagefault as a pretrigger for when to perform the device buffer and the MMU pagefault as a pretrigger for when to perform the device
IO. The following example may be a useful explaination of how one such setup IO. The following example may be a useful explanation of how one such setup
works: works:
- userspace app like Xfbdev mmaps framebuffer - userspace app like Xfbdev mmaps framebuffer
...@@ -28,7 +28,7 @@ a relatively more expensive operation. ...@@ -28,7 +28,7 @@ a relatively more expensive operation.
For some types of nonvolatile high latency displays, the desired image is For some types of nonvolatile high latency displays, the desired image is
the final image rather than the intermediate stages which is why it's okay the final image rather than the intermediate stages which is why it's okay
to not update for each write that is occuring. to not update for each write that is occurring.
It may be the case that this is useful in other scenarios as well. Paul Mundt It may be the case that this is useful in other scenarios as well. Paul Mundt
has mentioned a case where it is beneficial to use the page count to decide has mentioned a case where it is beneficial to use the page count to decide
......
...@@ -54,7 +54,7 @@ OPTIONS ...@@ -54,7 +54,7 @@ OPTIONS
aname=name aname specifies the file tree to access when the server is aname=name aname specifies the file tree to access when the server is
offering several exported file systems. offering several exported file systems.
cache=mode specifies a cacheing policy. By default, no caches are used. cache=mode specifies a caching policy. By default, no caches are used.
loose = no attempts are made at consistency, loose = no attempts are made at consistency,
intended for exclusive, read-only mounts intended for exclusive, read-only mounts
......
...@@ -21,10 +21,10 @@ software test suits to do stressful testing on IPF. ...@@ -21,10 +21,10 @@ software test suits to do stressful testing on IPF.
Below is a sample application as part of the whole tool. The sample Below is a sample application as part of the whole tool. The sample
can be used as a working test tool. Or it can be expanded to include can be used as a working test tool. Or it can be expanded to include
more features. It also can be a integrated into a libary or other user more features. It also can be a integrated into a library or other user
application to have more thorough test. application to have more thorough test.
The sample application takes err.conf as error configuation input. Gcc The sample application takes err.conf as error configuration input. GCC
compiles the code. After you install err_inject driver, you can run compiles the code. After you install err_inject driver, you can run
this sample application to inject errors. this sample application to inject errors.
...@@ -809,7 +809,7 @@ int err_inj() ...@@ -809,7 +809,7 @@ int err_inj()
} }
/* Create semaphore: If one_lock, one semaphore for all processors. /* Create semaphore: If one_lock, one semaphore for all processors.
Otherwise, one sempaphore for each processor. */ Otherwise, one semaphore for each processor. */
if (one_lock) { if (one_lock) {
if (create_sem(0)) { if (create_sem(0)) {
printf("Can not create semaphore...exit\n"); printf("Can not create semaphore...exit\n");
......
...@@ -170,7 +170,7 @@ major controller faults (ROM checksum and RAM test) and such things as stuck ...@@ -170,7 +170,7 @@ major controller faults (ROM checksum and RAM test) and such things as stuck
keys. Any keys down at power-up are presumed to be stuck, and their BREAK keys. Any keys down at power-up are presumed to be stuck, and their BREAK
(sic) code is returned (which without the preceding MAKE code is a flag for a (sic) code is returned (which without the preceding MAKE code is a flag for a
keyboard error). If the controller self-test completes without error, the code keyboard error). If the controller self-test completes without error, the code
0xF0 is returned. (This code will be used to indicate the version/rlease of 0xF0 is returned. (This code will be used to indicate the version/release of
the ikbd controller. The first release of the ikbd is version 0xF0, should the ikbd controller. The first release of the ikbd is version 0xF0, should
there be a second release it will be 0xF1, and so on.) there be a second release it will be 0xF1, and so on.)
The ikbd defaults to a mouse position reporting with threshold of 1 unit in The ikbd defaults to a mouse position reporting with threshold of 1 unit in
...@@ -413,7 +413,7 @@ INTERROGATION MODE. ...@@ -413,7 +413,7 @@ INTERROGATION MODE.
%nnnnmmmm ; where m is JOYSTICK1 state %nnnnmmmm ; where m is JOYSTICK1 state
; and n is JOYSTICK0 state ; and n is JOYSTICK0 state
Sets the ikbd to do nothing but monitor the serial command lne, maintain the Sets the ikbd to do nothing but monitor the serial command line, maintain the
time-of-day clock, and monitor the joystick. The rate sets the interval time-of-day clock, and monitor the joystick. The rate sets the interval
between joystick samples. between joystick samples.
N.B. The user should not set the rate higher than the serial communications N.B. The user should not set the rate higher than the serial communications
...@@ -446,10 +446,10 @@ The sample interval should be as constant as possible. ...@@ -446,10 +446,10 @@ The sample interval should be as constant as possible.
; until vertical cursor key is generated before RY ; until vertical cursor key is generated before RY
; has elapsed ; has elapsed
VX ; length (in tenths of seconds) of joystick closure VX ; length (in tenths of seconds) of joystick closure
; until horizontal cursor keystokes are generated ; until horizontal cursor keystrokes are generated
; after RX has elapsed ; after RX has elapsed
VY ; length (in tenths of seconds) of joystick closure VY ; length (in tenths of seconds) of joystick closure
; until vertical cursor keystokes are generated ; until vertical cursor keystrokes are generated
; after RY has elapsed ; after RY has elapsed
In this mode, joystick 0 is scanned in a way that simulates cursor keystrokes. In this mode, joystick 0 is scanned in a way that simulates cursor keystrokes.
......
...@@ -7,7 +7,7 @@ This is not a reference. Comments and corrections are welcome. To contact me, ...@@ -7,7 +7,7 @@ This is not a reference. Comments and corrections are welcome. To contact me,
send an email to: johann.deneux@gmail.com send an email to: johann.deneux@gmail.com
** WARNING ** ** WARNING **
I may not be held responsible for any dammage or harm caused if you try to I shall not be held responsible for any damage or harm caused if you try to
send data to your I-Force device based on what you read in this document. send data to your I-Force device based on what you read in this document.
** Preliminary Notes: ** Preliminary Notes:
...@@ -151,13 +151,13 @@ OP= ff ...@@ -151,13 +151,13 @@ OP= ff
Query command. Length varies according to the query type. Query command. Length varies according to the query type.
The general format of this packet is: The general format of this packet is:
ff 01 QUERY [INDEX] CHECKSUM ff 01 QUERY [INDEX] CHECKSUM
reponses are of the same form: responses are of the same form:
FF LEN QUERY VALUE_QUERIED CHECKSUM2 FF LEN QUERY VALUE_QUERIED CHECKSUM2
where LEN = 1 + length(VALUE_QUERIED) where LEN = 1 + length(VALUE_QUERIED)
**** Query ram size **** **** Query ram size ****
QUERY = 42 ('B'uffer size) QUERY = 42 ('B'uffer size)
The device should reply with the same packet plus two additionnal bytes The device should reply with the same packet plus two additional bytes
containing the size of the memory: containing the size of the memory:
ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available. ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available.
...@@ -234,12 +234,16 @@ is the amount of memory apparently needed for every set of parameters: ...@@ -234,12 +234,16 @@ is the amount of memory apparently needed for every set of parameters:
** Appendix: How to study the protocol ? ** ** Appendix: How to study the protocol ? **
1. Generate effects using the force editor provided with the DirectX SDK, or use Immersion Studio (freely available at their web site in the developer section: www.immersion.com) 1. Generate effects using the force editor provided with the DirectX SDK, or
2. Start a soft spying RS232 or USB (depending on where you connected your joystick/wheel). I used ComPortSpy from fCoder (alpha version!) use Immersion Studio (freely available at their web site in the developer section:
www.immersion.com)
2. Start a soft spying RS232 or USB (depending on where you connected your
joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
3. Play the effect, and watch what happens on the spy screen. 3. Play the effect, and watch what happens on the spy screen.
A few words about ComPortSpy: A few words about ComPortSpy:
At first glance, this soft seems, hum, well... buggy. In fact, data appear with a few seconds latency. Personnaly, I restart it every time I play an effect. At first glance, this software seems, hum, well... buggy. In fact, data appear with a
few seconds latency. Personally, I restart it every time I play an effect.
Remember it's free (as in free beer) and alpha! Remember it's free (as in free beer) and alpha!
** URLS ** ** URLS **
......
...@@ -79,7 +79,7 @@ In the _init function, which is called either upon module load or when ...@@ -79,7 +79,7 @@ In the _init function, which is called either upon module load or when
booting the kernel, it grabs the required resources (it should also check booting the kernel, it grabs the required resources (it should also check
for the presence of the device). for the presence of the device).
Then it allocates a new input device structure with input_aloocate_device() Then it allocates a new input device structure with input_allocate_device()
and sets up input bitfields. This way the device driver tells the other and sets up input bitfields. This way the device driver tells the other
parts of the input systems what it is - what events can be generated or parts of the input systems what it is - what events can be generated or
accepted by this input device. Our example device can only generate EV_KEY accepted by this input device. Our example device can only generate EV_KEY
......
...@@ -76,9 +76,9 @@ ...@@ -76,9 +76,9 @@
* Title: "Conceptual Architecture of the Linux Kernel" * Title: "Conceptual Architecture of the Linux Kernel"
Author: Ivan T. Bowman. Author: Ivan T. Bowman.
URL: http://plg.uwaterloo.ca/~itbowman/papers/CS746G-a1.html URL: http://plg.uwaterloo.ca/~itbowman/papers/CS746G-a1.html
Keywords: conceptual software arquitecture, extracted design, Keywords: conceptual software architecture, extracted design,
reverse engineering, system structure. reverse engineering, system structure.
Description: Conceptual software arquitecture of the Linux kernel, Description: Conceptual software architecture of the Linux kernel,
automatically extracted from the source code. Very detailed. Good automatically extracted from the source code. Very detailed. Good
figures. Gives good overall kernel understanding. figures. Gives good overall kernel understanding.
......
...@@ -37,7 +37,7 @@ all, distributions. There is, however, additional software that is ...@@ -37,7 +37,7 @@ all, distributions. There is, however, additional software that is
required. The firmware used by the chip is the intellectual property required. The firmware used by the chip is the intellectual property
of Broadcom and they have not given the bcm43xx team redistribution of Broadcom and they have not given the bcm43xx team redistribution
rights to this firmware. Since we cannot legally redistribute rights to this firmware. Since we cannot legally redistribute
the firwmare we cannot include it with the driver. Furthermore, it the firmware we cannot include it with the driver. Furthermore, it
cannot be placed in the downloadable archives of any distributing cannot be placed in the downloadable archives of any distributing
organization; therefore, the user is responsible for obtaining the organization; therefore, the user is responsible for obtaining the
firmware and placing it in the appropriate location so that the driver firmware and placing it in the appropriate location so that the driver
......
...@@ -689,7 +689,7 @@ such as the AFS filesystem. This permits such a utility to: ...@@ -689,7 +689,7 @@ such as the AFS filesystem. This permits such a utility to:
buffers manipulated directly. buffers manipulated directly.
To use the RxRPC facility, a kernel utility must still open an AF_RXRPC socket, To use the RxRPC facility, a kernel utility must still open an AF_RXRPC socket,
bind an addess as appropriate and listen if it's to be a server socket, but bind an address as appropriate and listen if it's to be a server socket, but
then it passes this to the kernel interface functions. then it passes this to the kernel interface functions.
The kernel interface functions are as follows: The kernel interface functions are as follows:
......
...@@ -12,7 +12,7 @@ ...@@ -12,7 +12,7 @@
For in-depth information, you can consult: For in-depth information, you can consult:
o The UDP-Lite Homepage: http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/ o The UDP-Lite Homepage: http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/
Fom here you can also download some example application source code. From here you can also download some example application source code.
o The UDP-Lite HOWTO on o The UDP-Lite HOWTO on
http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/files/UDP-Lite-HOWTO.txt http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/files/UDP-Lite-HOWTO.txt
...@@ -223,7 +223,7 @@ ...@@ -223,7 +223,7 @@
While it is important that such cases are dealt with correctly, they While it is important that such cases are dealt with correctly, they
are (annoyingly) rare: UDP-Lite is designed for optimising multimedia are (annoyingly) rare: UDP-Lite is designed for optimising multimedia
performance over wireless (or generally noisy) links and thus smaller performance over wireless (or generally noisy) links and thus smaller
coverage lenghts are likely to be expected. coverage lengths are likely to be expected.
V) UDP-LITE RUNTIME STATISTICS AND THEIR MEANING V) UDP-LITE RUNTIME STATISTICS AND THEIR MEANING
...@@ -259,7 +259,7 @@ ...@@ -259,7 +259,7 @@
VI) IPTABLES VI) IPTABLES
There is packet match support for UDP-Lite as well as support for the LOG target. There is packet match support for UDP-Lite as well as support for the LOG target.
If you copy and paste the following line into /etc/protcols, If you copy and paste the following line into /etc/protocols,
udplite 136 UDP-Lite # UDP-Lite [RFC 3828] udplite 136 UDP-Lite # UDP-Lite [RFC 3828]
......
...@@ -39,7 +39,7 @@ resume=<swap_file_partition> resume_offset=<swap_file_offset> ...@@ -39,7 +39,7 @@ resume=<swap_file_partition> resume_offset=<swap_file_offset>
where <swap_file_partition> is the partition on which the swap file is located where <swap_file_partition> is the partition on which the swap file is located
and <swap_file_offset> is the offset of the swap header determined by the and <swap_file_offset> is the offset of the swap header determined by the
application in 2) (of course, this step may be carried out automatically application in 2) (of course, this step may be carried out automatically
by the same application that determies the swap file's header offset using the by the same application that determines the swap file's header offset using the
FIBMAP ioctl) FIBMAP ioctl)
OR OR
......
...@@ -36,8 +36,8 @@ Causes of EEH Errors ...@@ -36,8 +36,8 @@ Causes of EEH Errors
EEH was originally designed to guard against hardware failure, such EEH was originally designed to guard against hardware failure, such
as PCI cards dying from heat, humidity, dust, vibration and bad as PCI cards dying from heat, humidity, dust, vibration and bad
electrical connections. The vast majority of EEH errors seen in electrical connections. The vast majority of EEH errors seen in
"real life" are due to eithr poorly seated PCI cards, or, "real life" are due to either poorly seated PCI cards, or,
unfortunately quite commonly, due device driver bugs, device firmware unfortunately quite commonly, due to device driver bugs, device firmware
bugs, and sometimes PCI card hardware bugs. bugs, and sometimes PCI card hardware bugs.
The most common software bug, is one that causes the device to The most common software bug, is one that causes the device to
......
...@@ -17,12 +17,12 @@ passed by the boot loader to the kernel at boot time. The device tree ...@@ -17,12 +17,12 @@ passed by the boot loader to the kernel at boot time. The device tree
describes what devices are present on the board and how they are describes what devices are present on the board and how they are
connected. The device tree can either be passed as a binary blob (as connected. The device tree can either be passed as a binary blob (as
described in Documentation/powerpc/booting-without-of.txt), or passed described in Documentation/powerpc/booting-without-of.txt), or passed
by Open Firmare (IEEE 1275) compatible firmware using an OF compatible by Open Firmware (IEEE 1275) compatible firmware using an OF compatible
client interface API. client interface API.
This document specifies the requirements on the device-tree for mpc5200 This document specifies the requirements on the device-tree for mpc5200
based boards. These requirements are above and beyond the details based boards. These requirements are above and beyond the details
specified in either the OpenFirmware spec or booting-without-of.txt specified in either the Open Firmware spec or booting-without-of.txt
All new mpc5200-based boards are expected to match this document. In All new mpc5200-based boards are expected to match this document. In
cases where this document is not sufficient to support a new board port, cases where this document is not sufficient to support a new board port,
...@@ -73,8 +73,8 @@ match on the compatible list; the 'most compatible' driver should be ...@@ -73,8 +73,8 @@ match on the compatible list; the 'most compatible' driver should be
selected. selected.
The split between the MPC5200 and the MPC5200B leaves a bit of a The split between the MPC5200 and the MPC5200B leaves a bit of a
connundrum. How should the compatible property be set up to provide conundrum. How should the compatible property be set up to provide
maximum compatability information; but still acurately describe the maximum compatibility information; but still accurately describe the
chip? For the MPC5200; the answer is easy. Most of the SoC devices chip? For the MPC5200; the answer is easy. Most of the SoC devices
originally appeared on the MPC5200. Since they didn't exist anywhere originally appeared on the MPC5200. Since they didn't exist anywhere
else; the 5200 compatible properties will contain only one item; else; the 5200 compatible properties will contain only one item;
...@@ -84,7 +84,7 @@ The 5200B is almost the same as the 5200, but not quite. It fixes ...@@ -84,7 +84,7 @@ The 5200B is almost the same as the 5200, but not quite. It fixes
silicon bugs and it adds a small number of enhancements. Most of the silicon bugs and it adds a small number of enhancements. Most of the
devices either provide exactly the same interface as on the 5200. A few devices either provide exactly the same interface as on the 5200. A few
devices have extra functions but still have a backwards compatible mode. devices have extra functions but still have a backwards compatible mode.
To express this infomation as completely as possible, 5200B device trees To express this information as completely as possible, 5200B device trees
should have two items in the compatible list; should have two items in the compatible list;
"mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended "mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended
that 5200B device trees follow this convention (instead of only listing that 5200B device trees follow this convention (instead of only listing
...@@ -199,7 +199,7 @@ ethernet@<addr> network mpc5200-fec MPC5200 ethernet device ...@@ -199,7 +199,7 @@ ethernet@<addr> network mpc5200-fec MPC5200 ethernet device
ata@<addr> ata mpc5200-ata IDE ATA interface ata@<addr> ata mpc5200-ata IDE ATA interface
i2c@<addr> i2c mpc5200-i2c I2C controller i2c@<addr> i2c mpc5200-i2c I2C controller
usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller
xlb@<addr> xlb mpc5200-xlb XLB arbritrator xlb@<addr> xlb mpc5200-xlb XLB arbitrator
Important child node properties Important child node properties
name type description name type description
......
...@@ -120,7 +120,7 @@ The following information is available in this file: ...@@ -120,7 +120,7 @@ The following information is available in this file:
list size to avoid SCSI malloc pool fragmentation. list size to avoid SCSI malloc pool fragmentation.
- Cleanup channel display in our /proc output. - Cleanup channel display in our /proc output.
- Workaround duplicate device entries in the mid-layer - Workaround duplicate device entries in the mid-layer
devlice list during add-single-device. device list during add-single-device.
1.3.6 (March 28th, 2003) 1.3.6 (March 28th, 2003)
- Correct a double free in the Domain Validation code. - Correct a double free in the Domain Validation code.
......
...@@ -159,7 +159,7 @@ The following information is available in this file: ...@@ -159,7 +159,7 @@ The following information is available in this file:
- Add support for 2.5.X's scsi_report_device_reset(). - Add support for 2.5.X's scsi_report_device_reset().
6.2.34 (May 5th, 2003) 6.2.34 (May 5th, 2003)
- Fix locking regression instroduced in 6.2.29 that - Fix locking regression introduced in 6.2.29 that
could cause a lock order reversal between the io_request_lock could cause a lock order reversal between the io_request_lock
and our per-softc lock. This was only possible on RH9, and our per-softc lock. This was only possible on RH9,
SuSE, and kernel.org 2.4.X kernels. SuSE, and kernel.org 2.4.X kernels.
...@@ -264,7 +264,7 @@ The following information is available in this file: ...@@ -264,7 +264,7 @@ The following information is available in this file:
Option: tag_info:{{value[,value...]}[,{value[,value...]}...]} Option: tag_info:{{value[,value...]}[,{value[,value...]}...]}
Definition: Set the per-target tagged queue depth on a Definition: Set the per-target tagged queue depth on a
per controller basis. Both controllers and targets per controller basis. Both controllers and targets
may be ommitted indicating that they should retain may be omitted indicating that they should retain
the default tag depth. the default tag depth.
Examples: tag_info:{{16,32,32,64,8,8,,32,32,32,32,32,32,32,32,32} Examples: tag_info:{{16,32,32,64,8,8,,32,32,32,32,32,32,32,32,32}
On Controller 0 On Controller 0
...@@ -290,7 +290,7 @@ The following information is available in this file: ...@@ -290,7 +290,7 @@ The following information is available in this file:
----------------------------------------------------------------- -----------------------------------------------------------------
Option: dv: {value[,value...]} Option: dv: {value[,value...]}
Definition: Set Domain Validation Policy on a per-controller basis. Definition: Set Domain Validation Policy on a per-controller basis.
Controllers may be ommitted indicating that Controllers may be omitted indicating that
they should retain the default read streaming setting. they should retain the default read streaming setting.
Example: dv:{-1,0,,1,1,0} Example: dv:{-1,0,,1,1,0}
On Controller 0 leave DV at its default setting. On Controller 0 leave DV at its default setting.
......
...@@ -21,7 +21,7 @@ ...@@ -21,7 +21,7 @@
versions older than 4.0 do not work with kernels 2.4.0 or later! If you versions older than 4.0 do not work with kernels 2.4.0 or later! If you
try to compile your kernel with the wrong driver source, the try to compile your kernel with the wrong driver source, the
compilation is aborted and you get a corresponding error message. This is compilation is aborted and you get a corresponding error message. This is
no bug in the driver. It prevents you from using the wrong sourcecode no bug in the driver; it prevents you from using the wrong source code
with the wrong kernel version. with the wrong kernel version.
Authors of this Driver Authors of this Driver
...@@ -58,7 +58,7 @@ ...@@ -58,7 +58,7 @@
5 Users' Manual 5 Users' Manual
5.1 Commandline Parameters 5.1 Commandline Parameters
5.2 Troubleshooting 5.2 Troubleshooting
5.3 Bugreports 5.3 Bug reports
5.4 Support WWW-page 5.4 Support WWW-page
6 References 6 References
7 Credits to 7 Credits to
...@@ -71,13 +71,13 @@ ...@@ -71,13 +71,13 @@
1 Abstract 1 Abstract
---------- ----------
This README-file describes the IBM SCSI-subsystem low level driver for This README-file describes the IBM SCSI-subsystem low level driver for
Linux. The descriptions which were formerly kept in the source-code have Linux. The descriptions which were formerly kept in the source code have
been taken out to this file to easify the codes' readability. The driver been taken out of this file to simplify the codes readability. The driver
description has been updated, as most of the former description was already description has been updated, as most of the former description was already
quite outdated. The history of the driver development is also kept inside quite outdated. The history of the driver development is also kept inside
here. Multiple historical developments have been summarized to shorten the here. Multiple historical developments have been summarized to shorten the
textsize a bit. At the end of this file you can find a small manual for text size a bit. At the end of this file you can find a small manual for
this driver and hints to get it running on your machine. this driver and hints to get it running on your machine.
2 Driver Description 2 Driver Description
...@@ -186,7 +186,7 @@ ...@@ -186,7 +186,7 @@
between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two
busses and provides support for 30 logical devices at the same time, where busses and provides support for 30 logical devices at the same time, where
in wide-addressing mode you can have 16 puns with 32 luns on each device. in wide-addressing mode you can have 16 puns with 32 luns on each device.
This section dexribes you the handling of devices on non-F/W adapters. This section describes the handling of devices on non-F/W adapters.
Just imagine, that you can have 16 * 32 = 512 devices on a F/W adapter Just imagine, that you can have 16 * 32 = 512 devices on a F/W adapter
which means a lot of possible devices for such a small machine. which means a lot of possible devices for such a small machine.
...@@ -209,10 +209,10 @@ ...@@ -209,10 +209,10 @@
-------------------------------------------------------- --------------------------------------------------------
One consequence of information hiding is that the real (pun,lun) One consequence of information hiding is that the real (pun,lun)
numbers are also hidden. The two possibilities to get around this problem numbers are also hidden. The two possibilities to get around this problem
is to offer fake pun/lun combinations to the operating system or to are to offer fake pun/lun combinations to the operating system or to
delete the whole mapping of the adapter and to reassign the ldns, using delete the whole mapping of the adapter and to reassign the ldns, using
the immediate assign command of the SCSI-subsystem for probing through the immediate assign command of the SCSI-subsystem for probing through
all possible pun/lun combinations. a ldn is a "logical device number" all possible pun/lun combinations. An ldn is a "logical device number"
which is used by IBM SCSI-subsystems to access some valid SCSI-device. which is used by IBM SCSI-subsystems to access some valid SCSI-device.
At the beginning of the development of this driver, the following approach At the beginning of the development of this driver, the following approach
was used: was used:
...@@ -251,9 +251,9 @@ ...@@ -251,9 +251,9 @@
lun>0 or to non-existing devices, in order to satisfy the subsystem, if lun>0 or to non-existing devices, in order to satisfy the subsystem, if
there are less than 15 SCSI-devices connected. In the case of more than 15