diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2007-10-19 19:34:40 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@kernel.org> | 2007-10-19 19:34:40 -0400 |
commit | 01dd2fbf0da4019c380b6ca22a074538fb31db5a (patch) | |
tree | 210291bd341c4450c8c51d8db890af0978f4035d /Documentation/scsi/ibmmca.txt | |
parent | 0f035b8e8491f4ff87f6eec3e3f754d36b39d7a2 (diff) |
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: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Diffstat (limited to 'Documentation/scsi/ibmmca.txt')
-rw-r--r-- | Documentation/scsi/ibmmca.txt | 58 |
1 files changed, 29 insertions, 29 deletions
diff --git a/Documentation/scsi/ibmmca.txt b/Documentation/scsi/ibmmca.txt index a08e225653d..a810421f1fb 100644 --- a/Documentation/scsi/ibmmca.txt +++ b/Documentation/scsi/ibmmca.txt | |||
@@ -21,7 +21,7 @@ | |||
21 | versions older than 4.0 do not work with kernels 2.4.0 or later! If you | 21 | versions older than 4.0 do not work with kernels 2.4.0 or later! If you |
22 | try to compile your kernel with the wrong driver source, the | 22 | try to compile your kernel with the wrong driver source, the |
23 | compilation is aborted and you get a corresponding error message. This is | 23 | compilation is aborted and you get a corresponding error message. This is |
24 | no bug in the driver. It prevents you from using the wrong sourcecode | 24 | no bug in the driver; it prevents you from using the wrong source code |
25 | with the wrong kernel version. | 25 | with the wrong kernel version. |
26 | 26 | ||
27 | Authors of this Driver | 27 | Authors of this Driver |
@@ -58,7 +58,7 @@ | |||
58 | 5 Users' Manual | 58 | 5 Users' Manual |
59 | 5.1 Commandline Parameters | 59 | 5.1 Commandline Parameters |
60 | 5.2 Troubleshooting | 60 | 5.2 Troubleshooting |
61 | 5.3 Bugreports | 61 | 5.3 Bug reports |
62 | 5.4 Support WWW-page | 62 | 5.4 Support WWW-page |
63 | 6 References | 63 | 6 References |
64 | 7 Credits to | 64 | 7 Credits to |
@@ -71,13 +71,13 @@ | |||
71 | 71 | ||
72 | 1 Abstract | 72 | 1 Abstract |
73 | ---------- | 73 | ---------- |
74 | This README-file describes the IBM SCSI-subsystem low level driver for | 74 | This README-file describes the IBM SCSI-subsystem low level driver for |
75 | Linux. The descriptions which were formerly kept in the source-code have | 75 | Linux. The descriptions which were formerly kept in the source code have |
76 | been taken out to this file to easify the codes' readability. The driver | 76 | been taken out of this file to simplify the codes readability. The driver |
77 | description has been updated, as most of the former description was already | 77 | description has been updated, as most of the former description was already |
78 | quite outdated. The history of the driver development is also kept inside | 78 | quite outdated. The history of the driver development is also kept inside |
79 | here. Multiple historical developments have been summarized to shorten the | 79 | here. Multiple historical developments have been summarized to shorten the |
80 | textsize a bit. At the end of this file you can find a small manual for | 80 | text size a bit. At the end of this file you can find a small manual for |
81 | this driver and hints to get it running on your machine. | 81 | this driver and hints to get it running on your machine. |
82 | 82 | ||
83 | 2 Driver Description | 83 | 2 Driver Description |
@@ -186,7 +186,7 @@ | |||
186 | between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two | 186 | between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two |
187 | busses and provides support for 30 logical devices at the same time, where | 187 | busses and provides support for 30 logical devices at the same time, where |
188 | in wide-addressing mode you can have 16 puns with 32 luns on each device. | 188 | in wide-addressing mode you can have 16 puns with 32 luns on each device. |
189 | This section dexribes you the handling of devices on non-F/W adapters. | 189 | This section describes the handling of devices on non-F/W adapters. |
190 | Just imagine, that you can have 16 * 32 = 512 devices on a F/W adapter | 190 | Just imagine, that you can have 16 * 32 = 512 devices on a F/W adapter |
191 | which means a lot of possible devices for such a small machine. | 191 | which means a lot of possible devices for such a small machine. |
192 | 192 | ||
@@ -209,10 +209,10 @@ | |||
209 | -------------------------------------------------------- | 209 | -------------------------------------------------------- |
210 | One consequence of information hiding is that the real (pun,lun) | 210 | One consequence of information hiding is that the real (pun,lun) |
211 | numbers are also hidden. The two possibilities to get around this problem | 211 | numbers are also hidden. The two possibilities to get around this problem |
212 | is to offer fake pun/lun combinations to the operating system or to | 212 | are to offer fake pun/lun combinations to the operating system or to |
213 | delete the whole mapping of the adapter and to reassign the ldns, using | 213 | delete the whole mapping of the adapter and to reassign the ldns, using |
214 | the immediate assign command of the SCSI-subsystem for probing through | 214 | the immediate assign command of the SCSI-subsystem for probing through |
215 | all possible pun/lun combinations. a ldn is a "logical device number" | 215 | all possible pun/lun combinations. An ldn is a "logical device number" |
216 | which is used by IBM SCSI-subsystems to access some valid SCSI-device. | 216 | which is used by IBM SCSI-subsystems to access some valid SCSI-device. |
217 | At the beginning of the development of this driver, the following approach | 217 | At the beginning of the development of this driver, the following approach |
218 | was used: | 218 | was used: |
@@ -251,9 +251,9 @@ | |||
251 | lun>0 or to non-existing devices, in order to satisfy the subsystem, if | 251 | lun>0 or to non-existing devices, in order to satisfy the subsystem, if |
252 | there are less than 15 SCSI-devices connected. In the case of more than 15 | 252 | there are less than 15 SCSI-devices connected. In the case of more than 15 |
253 | devices, the dynamical mapping goes active. If the get_scsi[][] reports a | 253 | devices, the dynamical mapping goes active. If the get_scsi[][] reports a |
254 | device to be existant, but it has no ldn assigned, it gets a ldn out of 7 | 254 | device to be existent, but it has no ldn assigned, it gets an ldn out of 7 |
255 | to 14. The numbers are assigned in cyclic order. Therefore it takes 8 | 255 | to 14. The numbers are assigned in cyclic order, therefore it takes 8 |
256 | dynamical reassignments on the SCSI-devices, until a certain device | 256 | dynamical reassignments on the SCSI-devices until a certain device |
257 | loses its ldn again. This assures that dynamical remapping is avoided | 257 | loses its ldn again. This assures that dynamical remapping is avoided |
258 | during intense I/O between up to 15 SCSI-devices (means pun,lun | 258 | during intense I/O between up to 15 SCSI-devices (means pun,lun |
259 | combinations). A further advantage of this method is that people who | 259 | combinations). A further advantage of this method is that people who |
@@ -551,7 +551,7 @@ | |||
551 | than devices are available, they are assigned to non existing pun,lun | 551 | than devices are available, they are assigned to non existing pun,lun |
552 | combinations to satisfy the adapter. With this, the dynamical mapping | 552 | combinations to satisfy the adapter. With this, the dynamical mapping |
553 | was possible to implement. (For further info see the text in the | 553 | was possible to implement. (For further info see the text in the |
554 | source-code and in the description below. Read the description | 554 | source code and in the description below. Read the description |
555 | below BEFORE installing this driver on your system!) | 555 | below BEFORE installing this driver on your system!) |
556 | 2) Changed the name IBMMCA_DRIVER_VERSION to IBMMCA_SCSI_DRIVER_VERSION. | 556 | 2) Changed the name IBMMCA_DRIVER_VERSION to IBMMCA_SCSI_DRIVER_VERSION. |
557 | 3) The LED-display shows on PS/2-95 no longer the ldn, but the SCSI-ID | 557 | 3) The LED-display shows on PS/2-95 no longer the ldn, but the SCSI-ID |
@@ -762,9 +762,9 @@ | |||
762 | - Michael Lang | 762 | - Michael Lang |
763 | 763 | ||
764 | Apr 23, 2000 (v3.2pre1) | 764 | Apr 23, 2000 (v3.2pre1) |
765 | 1) During a very long time, I collected a huge amount of bugreports from | 765 | 1) During a very long time, I collected a huge amount of bug reports from |
766 | various people, trying really quite different things on their SCSI- | 766 | various people, trying really quite different things on their SCSI- |
767 | PS/2s. Today, all these bugreports are taken into account and should be | 767 | PS/2s. Today, all these bug reports are taken into account and should be |
768 | mostly solved. The major topics were: | 768 | mostly solved. The major topics were: |
769 | - Driver crashes during boottime by no obvious reason. | 769 | - Driver crashes during boottime by no obvious reason. |
770 | - Driver panics while the midlevel-SCSI-driver is trying to inquire | 770 | - Driver panics while the midlevel-SCSI-driver is trying to inquire |
@@ -819,7 +819,7 @@ | |||
819 | - Michael Lang | 819 | - Michael Lang |
820 | 820 | ||
821 | July 17, 2000 (v3.2pre8) | 821 | July 17, 2000 (v3.2pre8) |
822 | A long period of collecting bugreports from all corners of the world | 822 | A long period of collecting bug reports from all corners of the world |
823 | now lead to the following corrections to the code: | 823 | now lead to the following corrections to the code: |
824 | 1) SCSI-2 F/W support crashed with a COMMAND ERROR. The reason for this | 824 | 1) SCSI-2 F/W support crashed with a COMMAND ERROR. The reason for this |
825 | was that it is possible to disable Fast-SCSI for the external bus. | 825 | was that it is possible to disable Fast-SCSI for the external bus. |
@@ -873,7 +873,7 @@ | |||
873 | July 26, 2000 (v3.2pre11) | 873 | July 26, 2000 (v3.2pre11) |
874 | 1) I passed a horrible weekend getting mad with NMIs on kernel 2.2.14 and | 874 | 1) I passed a horrible weekend getting mad with NMIs on kernel 2.2.14 and |
875 | a model 9595. Asking around in the community, nobody except of me has | 875 | a model 9595. Asking around in the community, nobody except of me has |
876 | seen such errors. Weired, but I am trying to recompile everything on | 876 | seen such errors. Weird, but I am trying to recompile everything on |
877 | the model 9595. Maybe, as I use a specially modified gcc, that could | 877 | the model 9595. Maybe, as I use a specially modified gcc, that could |
878 | cause problems. But, it was not the reason. The true background was, | 878 | cause problems. But, it was not the reason. The true background was, |
879 | that the kernel was compiled for i386 and the 9595 has a 486DX-2. | 879 | that the kernel was compiled for i386 and the 9595 has a 486DX-2. |
@@ -886,7 +886,7 @@ | |||
886 | alive rotator during boottime. This makes sense, when no monitor is | 886 | alive rotator during boottime. This makes sense, when no monitor is |
887 | connected to the system. You can get rid of all display activity, if | 887 | connected to the system. You can get rid of all display activity, if |
888 | you do not use any parameter or just ibmmcascsi=activity, for the | 888 | you do not use any parameter or just ibmmcascsi=activity, for the |
889 | harddrive activity LED, existant on all PS/2, except models 8595-XXX. | 889 | harddrive activity LED, existent on all PS/2, except models 8595-XXX. |
890 | If no monitor is available, please use ibmmcascsi=display, which works | 890 | If no monitor is available, please use ibmmcascsi=display, which works |
891 | fine together with the linuxinfo utility for the LED-panel. | 891 | fine together with the linuxinfo utility for the LED-panel. |
892 | - Michael Lang | 892 | - Michael Lang |
@@ -1115,7 +1115,7 @@ | |||
1115 | If this really happens, do also send e-mail to the maintainer, as | 1115 | If this really happens, do also send e-mail to the maintainer, as |
1116 | forced detection should be never necessary. Forced detection is in | 1116 | forced detection should be never necessary. Forced detection is in |
1117 | principal some flaw of the driver adapter detection and goes into | 1117 | principal some flaw of the driver adapter detection and goes into |
1118 | bugreports. | 1118 | bug reports. |
1119 | Q: The driver screws up, if it starts to probe SCSI-devices, is there | 1119 | Q: The driver screws up, if it starts to probe SCSI-devices, is there |
1120 | some way out of it? | 1120 | some way out of it? |
1121 | A: Yes, that was some recognition problem of the correct SCSI-adapter | 1121 | A: Yes, that was some recognition problem of the correct SCSI-adapter |
@@ -1172,7 +1172,7 @@ | |||
1172 | recommended version is 3.2 or later. Here, the F/W support is in | 1172 | recommended version is 3.2 or later. Here, the F/W support is in |
1173 | a stable and reliable condition. Wide-addressing is in addition | 1173 | a stable and reliable condition. Wide-addressing is in addition |
1174 | supported. | 1174 | supported. |
1175 | Q: I get a Ooops message and something like "killing interrupt". | 1175 | Q: I get an Oops message and something like "killing interrupt". |
1176 | A: The reason for this is that the IBM SCSI-subsystem only sends a | 1176 | A: The reason for this is that the IBM SCSI-subsystem only sends a |
1177 | termination status back, if some error appeared. In former releases | 1177 | termination status back, if some error appeared. In former releases |
1178 | of the driver, it was not checked, if the termination status block | 1178 | of the driver, it was not checked, if the termination status block |
@@ -1213,21 +1213,21 @@ | |||
1213 | problem. Not yet tried, but guessing that it could work. To get this, | 1213 | problem. Not yet tried, but guessing that it could work. To get this, |
1214 | set unchecked_isa_dma argument of ibmmca.h from 0 to 1. | 1214 | set unchecked_isa_dma argument of ibmmca.h from 0 to 1. |
1215 | 1215 | ||
1216 | 5.3 Bugreports | 1216 | 5.3 Bug reports |
1217 | -------------- | 1217 | -------------- |
1218 | If you really find bugs in the sourcecode or the driver will successfully | 1218 | If you really find bugs in the source code or the driver will successfully |
1219 | refuse to work on your machine, you should send a bug report to me. The | 1219 | refuse to work on your machine, you should send a bug report to me. The |
1220 | best for this is to follow the instructions on the WWW-page for this | 1220 | best for this is to follow the instructions on the WWW-page for this |
1221 | driver. Fill out the bug-report form, placed on the WWW-page and ship it, | 1221 | driver. Fill out the bug-report form, placed on the WWW-page and ship it, |
1222 | so the bugs can be taken into account with maximum efforts. But, please | 1222 | so the bugs can be taken into account with maximum efforts. But, please |
1223 | do not send bug reports about this driver to Linus Torvalds or Leonard | 1223 | do not send bug reports about this driver to Linus Torvalds or Leonard |
1224 | Zubkoff, as Linus is burried in E-Mail and Leonard is supervising all | 1224 | Zubkoff, as Linus is buried in E-Mail and Leonard is supervising all |
1225 | SCSI-drivers and won't have the time left to look inside every single | 1225 | SCSI-drivers and won't have the time left to look inside every single |
1226 | driver to fix a bug and especially DO NOT send modified code to Linus | 1226 | driver to fix a bug and especially DO NOT send modified code to Linus |
1227 | Torvalds or Alan J. Cox which has not been checked here!!! They are both | 1227 | Torvalds or Alan J. Cox which has not been checked here!!! They are both |
1228 | quite burried in E-mail (as me, sometimes, too) and one should first check | 1228 | quite buried in E-mail (as me, sometimes, too) and one should first check |
1229 | for problems on my local teststand. Recently, I got a lot of | 1229 | for problems on my local teststand. Recently, I got a lot of |
1230 | bugreports for errors in the ibmmca.c code, which I could not imagine, but | 1230 | bug reports for errors in the ibmmca.c code, which I could not imagine, but |
1231 | a look inside some Linux-distribution showed me quite often some modified | 1231 | a look inside some Linux-distribution showed me quite often some modified |
1232 | code, which did no longer work on most other machines than the one of the | 1232 | code, which did no longer work on most other machines than the one of the |
1233 | modifier. Ok, so now that there is maintenance service available for this | 1233 | modifier. Ok, so now that there is maintenance service available for this |
@@ -1261,7 +1261,7 @@ | |||
1261 | some e-mail directly, but at least with the same information as required by | 1261 | some e-mail directly, but at least with the same information as required by |
1262 | the formular. | 1262 | the formular. |
1263 | 1263 | ||
1264 | If you have extensive bugreports, including Ooops messages and | 1264 | If you have extensive bug reports, including Oops messages and |
1265 | screen-shots, please feel free to send it directly to the address | 1265 | screen-shots, please feel free to send it directly to the address |
1266 | of the maintainer, too. The current address of the maintainer is: | 1266 | of the maintainer, too. The current address of the maintainer is: |
1267 | 1267 | ||
@@ -1318,7 +1318,7 @@ | |||
1318 | detailed bug reports and ideas for this driver (and his | 1318 | detailed bug reports and ideas for this driver (and his |
1319 | patience ;-)). | 1319 | patience ;-)). |
1320 | Alan J. Cox | 1320 | Alan J. Cox |
1321 | for his bugreports and his bold activities in cross-checking | 1321 | for his bug reports and his bold activities in cross-checking |
1322 | the driver-code with his teststand. | 1322 | the driver-code with his teststand. |
1323 | 1323 | ||
1324 | 7.2 Sponsors & Supporters | 1324 | 7.2 Sponsors & Supporters |