diff options
Diffstat (limited to 'Documentation/scsi/ibmmca.txt')
-rw-r--r-- | Documentation/scsi/ibmmca.txt | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/Documentation/scsi/ibmmca.txt b/Documentation/scsi/ibmmca.txt index d16ce5b540f4..35f6b8ed2295 100644 --- a/Documentation/scsi/ibmmca.txt +++ b/Documentation/scsi/ibmmca.txt | |||
@@ -229,7 +229,7 @@ | |||
229 | 229 | ||
230 | In a second step of the driver development, the following improvement has | 230 | In a second step of the driver development, the following improvement has |
231 | been applied: The first approach limited the number of devices to 7, far | 231 | been applied: The first approach limited the number of devices to 7, far |
232 | fewer than the 15 that it could usem then it just maped ldn -> | 232 | fewer than the 15 that it could use, then it just mapped ldn -> |
233 | (ldn/8,ldn%8) for pun,lun. We ended up with a real mishmash of puns | 233 | (ldn/8,ldn%8) for pun,lun. We ended up with a real mishmash of puns |
234 | and luns, but it all seemed to work. | 234 | and luns, but it all seemed to work. |
235 | 235 | ||
@@ -254,12 +254,12 @@ | |||
254 | device to be existant, but it has no ldn assigned, it gets a ldn out of 7 | 254 | device to be existant, but it has no ldn assigned, it gets a 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 |
260 | build their kernel without probing on all luns will get what they expect, | 260 | build their kernel without probing on all luns will get what they expect, |
261 | because the driver just won't assign everything with lun>0 when | 261 | because the driver just won't assign everything with lun>0 when |
262 | multpile lun probing is inactive. | 262 | multiple lun probing is inactive. |
263 | 263 | ||
264 | 2.4 SCSI-Device Order | 264 | 2.4 SCSI-Device Order |
265 | --------------------- | 265 | --------------------- |
@@ -309,9 +309,9 @@ | |||
309 | 2.6 Abort & Reset Commands | 309 | 2.6 Abort & Reset Commands |
310 | -------------------------- | 310 | -------------------------- |
311 | These are implemented with busy waiting for interrupt to arrive. | 311 | These are implemented with busy waiting for interrupt to arrive. |
312 | ibmmca_reset() and ibmmca_abort() do not work sufficently well | 312 | ibmmca_reset() and ibmmca_abort() do not work sufficiently well |
313 | up to now and need still a lot of development work. But, this seems | 313 | up to now and need still a lot of development work. This seems |
314 | to be even a problem with other SCSI-low level drivers, too. However, | 314 | to be a problem with other low-level SCSI drivers too, however |
315 | this should be no excuse. | 315 | this should be no excuse. |
316 | 316 | ||
317 | 2.7 Disk Geometry | 317 | 2.7 Disk Geometry |
@@ -684,8 +684,8 @@ | |||
684 | not like sending commands to non-existing SCSI-devices and will react | 684 | not like sending commands to non-existing SCSI-devices and will react |
685 | with a command error as a sign of protest. While this error is not | 685 | with a command error as a sign of protest. While this error is not |
686 | present on IBM SCSI Adapter w/cache, it appears on IBM Integrated SCSI | 686 | present on IBM SCSI Adapter w/cache, it appears on IBM Integrated SCSI |
687 | Adapters. Therefore, I implemented a workarround to forgive those | 687 | Adapters. Therefore, I implemented a workaround to forgive those |
688 | adapters their protests, but it is marked up in the statisctis, so | 688 | adapters their protests, but it is marked up in the statistics, so |
689 | after a successful boot, you can see in /proc/scsi/ibmmca/<host_number> | 689 | after a successful boot, you can see in /proc/scsi/ibmmca/<host_number> |
690 | how often the command errors have been forgiven to the SCSI-subsystem. | 690 | how often the command errors have been forgiven to the SCSI-subsystem. |
691 | If the number is bigger than 0, you have a SCSI subsystem of older | 691 | If the number is bigger than 0, you have a SCSI subsystem of older |
@@ -778,15 +778,15 @@ | |||
778 | not accept this, as they stick quite near to ANSI-SCSI and report | 778 | not accept this, as they stick quite near to ANSI-SCSI and report |
779 | a COMMAND_ERROR message which causes the driver to panic. The main | 779 | a COMMAND_ERROR message which causes the driver to panic. The main |
780 | problem was located around the INQUIRY command. Now, for all the | 780 | problem was located around the INQUIRY command. Now, for all the |
781 | mentioned commands, the buffersize, sent to the adapter is at | 781 | mentioned commands, the buffersize sent to the adapter is at |
782 | maximum 255 which seems to be a quite reasonable solution. | 782 | maximum 255 which seems to be a quite reasonable solution. |
783 | TEST_UNIT_READY gets a buffersize of 0 to make sure, that no | 783 | TEST_UNIT_READY gets a buffersize of 0 to make sure that no |
784 | data is transferred in order to avoid any possible command failure. | 784 | data is transferred in order to avoid any possible command failure. |
785 | 2) On unsuccessful TEST_UNIT_READY, the midlevel-driver has to send | 785 | 2) On unsuccessful TEST_UNIT_READY, the mid-level driver has to send |
786 | a REQUEST_SENSE in order to see, where the problem is located. This | 786 | a REQUEST_SENSE in order to see where the problem is located. This |
787 | REQUEST_SENSE may have various length in its answer-buffer. IBM | 787 | REQUEST_SENSE may have various length in its answer-buffer. IBM |
788 | SCSI-subsystems report a command failure, if the returned buffersize | 788 | SCSI-subsystems report a command failure if the returned buffersize |
789 | is different from the sent buffersize, but this can be supressed by | 789 | is different from the sent buffersize, but this can be suppressed by |
790 | a special bit, which is now done and problems seem to be solved. | 790 | a special bit, which is now done and problems seem to be solved. |
791 | 2) Code adaption to all kernel-releases. Now, the 3.2 code compiles on | 791 | 2) Code adaption to all kernel-releases. Now, the 3.2 code compiles on |
792 | 2.0.x, 2.1.x, 2.2.x and 2.3.x kernel releases without any code-changes. | 792 | 2.0.x, 2.1.x, 2.2.x and 2.3.x kernel releases without any code-changes. |
@@ -1086,7 +1086,7 @@ | |||
1086 | 1086 | ||
1087 | Q: "Reset SCSI-devices at boottime" halts the system at boottime, why? | 1087 | Q: "Reset SCSI-devices at boottime" halts the system at boottime, why? |
1088 | A: This is only tested with the IBM SCSI Adapter w/cache. It is not | 1088 | A: This is only tested with the IBM SCSI Adapter w/cache. It is not |
1089 | yet prooved to run on other adapters, however you may be lucky. | 1089 | yet proven to run on other adapters, however you may be lucky. |
1090 | In version 3.1d this has been hugely improved and should work better, | 1090 | In version 3.1d this has been hugely improved and should work better, |
1091 | now. Normally you really won't need to activate this flag in the | 1091 | now. Normally you really won't need to activate this flag in the |
1092 | kernel configuration, as all post 1989 SCSI-devices should accept | 1092 | kernel configuration, as all post 1989 SCSI-devices should accept |
@@ -1104,7 +1104,7 @@ | |||
1104 | The parameter 'normal' sets the new industry standard, starting | 1104 | The parameter 'normal' sets the new industry standard, starting |
1105 | from pun 0, scanning up to pun 6. This allows you to change your | 1105 | from pun 0, scanning up to pun 6. This allows you to change your |
1106 | opinion still after having already compiled the kernel. | 1106 | opinion still after having already compiled the kernel. |
1107 | Q: Why I cannot find the IBM MCA SCSI support in the config menue? | 1107 | Q: Why can't I find IBM MCA SCSI support in the config menu? |
1108 | A: You have to activate MCA bus support, first. | 1108 | A: You have to activate MCA bus support, first. |
1109 | Q: Where can I find the latest info about this driver? | 1109 | Q: Where can I find the latest info about this driver? |
1110 | A: See the file MAINTAINERS for the current WWW-address, which offers | 1110 | A: See the file MAINTAINERS for the current WWW-address, which offers |
@@ -1156,7 +1156,7 @@ | |||
1156 | Guide) what has to be done for reset, we still share the bad shape of | 1156 | Guide) what has to be done for reset, we still share the bad shape of |
1157 | the reset functions with all other low level SCSI-drivers. | 1157 | the reset functions with all other low level SCSI-drivers. |
1158 | Astonishingly, reset works in most cases quite ok, but the harddisks | 1158 | Astonishingly, reset works in most cases quite ok, but the harddisks |
1159 | won't run in synchonous mode anymore after a reset, until you reboot. | 1159 | won't run in synchronous mode anymore after a reset, until you reboot. |
1160 | Q: Why does my XXX w/Cache adapter not use read-prefetch? | 1160 | Q: Why does my XXX w/Cache adapter not use read-prefetch? |
1161 | A: Ok, that is not completely possible. If a cache is present, the | 1161 | A: Ok, that is not completely possible. If a cache is present, the |
1162 | adapter tries to use it internally. Explicitly, one can use the cache | 1162 | adapter tries to use it internally. Explicitly, one can use the cache |