diff options
Diffstat (limited to 'Documentation/s390')
| -rw-r--r-- | Documentation/s390/Debugging390.txt | 4 | ||||
| -rw-r--r-- | Documentation/s390/cds.txt | 2 | ||||
| -rw-r--r-- | Documentation/s390/driver-model.txt | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt index 844c03f..0bb4512 100644 --- a/Documentation/s390/Debugging390.txt +++ b/Documentation/s390/Debugging390.txt @@ -188,7 +188,7 @@ Bytes 0-512 ( 200 hex ) on s/390 & 0-512,4096-4544,4604-5119 currently on z/Arch are used by the processor itself for holding such information as exception indications & entry points for exceptions. Bytes after 0xc00 hex are used by linux for per processor globals on s/390 & z/Architecture -( there is a gap on z/Architecure too currently between 0xc00 & 1000 which linux uses ). +( there is a gap on z/Architecture too currently between 0xc00 & 1000 which linux uses ). The closest thing to this on traditional architectures is the interrupt vector table. This is a good thing & does simplify some of the kernel coding however it means that we now cannot catch stray NULL pointers in the @@ -861,7 +861,7 @@ Linux source tree. 6) rm /arch/s390/kernel/signal.o 7) make /arch/s390/kernel/signal.o 8) watch the gcc command line emitted -9) type it in again or alernatively cut & paste it on the console adding the -g option. +9) type it in again or alternatively cut & paste it on the console adding the -g option. 10) objdump --source arch/s390/kernel/signal.o > signal.lst This will output the source & the assembly intermixed, as the snippet below shows This will unfortunately output addresses which aren't the same diff --git a/Documentation/s390/cds.txt b/Documentation/s390/cds.txt index f0be389..079d886 100644 --- a/Documentation/s390/cds.txt +++ b/Documentation/s390/cds.txt @@ -348,7 +348,7 @@ The ccw_device_start() function returns : not online. When the I/O request completes, the CDS first level interrupt handler will -accumalate the status in a struct irb and then call the device interrupt handler. +accumulate the status in a struct irb and then call the device interrupt handler. The intparm field will contain the value the device driver has associated with a particular I/O request. If a pending device status was recognized, intparm will be set to 0 (zero). This may happen during I/O initiation or delayed diff --git a/Documentation/s390/driver-model.txt b/Documentation/s390/driver-model.txt index efb674e..5295a83 100644 --- a/Documentation/s390/driver-model.txt +++ b/Documentation/s390/driver-model.txt @@ -262,7 +262,7 @@ attribute 'online' which can be 0 or 1. ----------- The netiucv driver creates an attribute 'connection' under -bus/iucv/drivers/netiucv. Piping to this attibute creates a new netiucv +bus/iucv/drivers/netiucv. Piping to this attribute creates a new netiucv connection to the specified host. Netiucv connections show up under devices/iucv/ as "netiucv<ifnum>". The interface |
