diff options
author | Cornelia Huck <cornelia.huck@de.ibm.com> | 2006-12-08 09:56:02 -0500 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2006-12-08 09:56:02 -0500 |
commit | 7f090145a14afc35844dce80174c9c24f9e66ec5 (patch) | |
tree | 14ee3ba84574ed147ea779c2747d4bec2cc72915 /Documentation/s390 | |
parent | 529192f3b90682e37c5fcab461d968d062f1e0e4 (diff) |
[S390] Update documentation for dynamic subchannel mapping.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'Documentation/s390')
-rw-r--r-- | Documentation/s390/driver-model.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/s390/driver-model.txt b/Documentation/s390/driver-model.txt index 77bf450ec39b..e938c442277d 100644 --- a/Documentation/s390/driver-model.txt +++ b/Documentation/s390/driver-model.txt | |||
@@ -18,11 +18,18 @@ devices/ | |||
18 | - 0.0.0002/ | 18 | - 0.0.0002/ |
19 | - 0.1.0000/0.1.1234/ | 19 | - 0.1.0000/0.1.1234/ |
20 | ... | 20 | ... |
21 | - defunct/ | ||
21 | 22 | ||
22 | In this example, device 0815 is accessed via subchannel 0 in subchannel set 0, | 23 | In this example, device 0815 is accessed via subchannel 0 in subchannel set 0, |
23 | device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O | 24 | device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O |
24 | subchannel. Device 1234 is accessed via subchannel 0 in subchannel set 1. | 25 | subchannel. Device 1234 is accessed via subchannel 0 in subchannel set 1. |
25 | 26 | ||
27 | The subchannel named 'defunct' does not represent any real subchannel on the | ||
28 | system; it is a pseudo subchannel where disconnnected ccw devices are moved to | ||
29 | if they are displaced by another ccw device becoming operational on their | ||
30 | former subchannel. The ccw devices will be moved again to a proper subchannel | ||
31 | if they become operational again on that subchannel. | ||
32 | |||
26 | You should address a ccw device via its bus id (e.g. 0.0.4711); the device can | 33 | You should address a ccw device via its bus id (e.g. 0.0.4711); the device can |
27 | be found under bus/ccw/devices/. | 34 | be found under bus/ccw/devices/. |
28 | 35 | ||