diff options
Diffstat (limited to 'Documentation/s390')
| -rw-r--r-- | Documentation/s390/Debugging390.txt | 16 | ||||
| -rw-r--r-- | Documentation/s390/cds.txt | 4 | ||||
| -rw-r--r-- | Documentation/s390/crypto/crypto-API.txt | 4 | ||||
| -rw-r--r-- | Documentation/s390/s390dbf.txt | 4 |
4 files changed, 14 insertions, 14 deletions
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt index e506e8d..2d826d8 100644 --- a/Documentation/s390/Debugging390.txt +++ b/Documentation/s390/Debugging390.txt @@ -366,8 +366,8 @@ Register Usage & Stackframes on Linux for s/390 & z/Architecture Overview: --------- This is the code that gcc produces at the top & the bottom of -each function, it usually is fairly consistent & similar from -function to function & if you know its layout you can probalby +each function. It usually is fairly consistent & similar from +function to function & if you know its layout you can probably make some headway in finding the ultimate cause of a problem after a crash without a source level debugger. @@ -1703,7 +1703,7 @@ concentrate on data processing. IOP's can use one or more links ( known as channel paths ) to talk to each IO device. It first checks for path availability & chooses an available one, then starts ( & sometimes terminates IO ). -There are two types of channel path ESCON & the Paralell IO interface. +There are two types of channel path: ESCON & the Parallel IO interface. IO devices are attached to control units, control units provide the logic to interface the channel paths & channel path IO protocols to @@ -1742,11 +1742,11 @@ controllers or a control unit which connects to 1000 3270 terminals ). The 390 IO systems come in 2 flavours the current 390 machines support both -The Older 360 & 370 Interface,sometimes called the paralell I/O interface, +The Older 360 & 370 Interface,sometimes called the Parallel I/O interface, sometimes called Bus-and Tag & sometimes Original Equipment Manufacturers Interface (OEMI). -This byte wide paralell channel path/bus has parity & data on the "Bus" cable +This byte wide Parallel channel path/bus has parity & data on the "Bus" cable & control lines on the "Tag" cable. These can operate in byte multiplex mode for sharing between several slow devices or burst mode & monopolize the channel for the whole burst. Upto 256 devices can be addressed on one of these cables. These cables are @@ -1776,7 +1776,7 @@ Consoles 3270 & 3215 ( a teletype emulated under linux for a line mode console ) DASD's direct access storage devices ( otherwise known as hard disks ). Tape Drives. CTC ( Channel to Channel Adapters ), -ESCON or Paralell Cables used as a very high speed serial link +ESCON or Parallel Cables used as a very high speed serial link between 2 machines. We use 2 cables under linux to do a bi-directional serial link. @@ -1802,8 +1802,8 @@ OSA 7C09 ON OSA 7C09 SUBCHANNEL = 0001 OSA 7C14 ON OSA 7C14 SUBCHANNEL = 0002 OSA 7C15 ON OSA 7C15 SUBCHANNEL = 0003 -If you have a guest with certain priviliges you may be able to see devices -which don't belong to you to avoid this do add the option V. +If you have a guest with certain privileges you may be able to see devices +which don't belong to you. To avoid this, add the option V. e.g. Q V OSA diff --git a/Documentation/s390/cds.txt b/Documentation/s390/cds.txt index 59a5616..b2acf4b 100644 --- a/Documentation/s390/cds.txt +++ b/Documentation/s390/cds.txt @@ -177,11 +177,11 @@ This routine returns the characteristics for the device specified. The function is meant to be called with an irq handler in place; that is, at earliest during set_online() processing. -While the request is procesed synchronously, the device interrupt +While the request is processed synchronously, the device interrupt handler is called for final ending status. In case of error situations the interrupt handler may recover appropriately. The device irq handler can recognize the corresponding interrupts by the interruption parameter be -0x00524443.The ccw_device must not be locked prior to calling read_dev_chars(). +0x00524443. The ccw_device must not be locked prior to calling read_dev_chars(). The function may be called enabled or disabled. diff --git a/Documentation/s390/crypto/crypto-API.txt b/Documentation/s390/crypto/crypto-API.txt index 78a7762..29dee79 100644 --- a/Documentation/s390/crypto/crypto-API.txt +++ b/Documentation/s390/crypto/crypto-API.txt @@ -61,9 +61,9 @@ Example: z990 crypto instruction for SHA1 algorithm is available -> when the sha1 algorithm is requested through the crypto API (which has a module autoloader) the z990 module will be loaded. -TBD: a userspace module probin mechanism +TBD: a userspace module probing mechanism something like 'probe sha1 sha1_z990 sha1' in modprobe.conf - -> try module sha1_z990, if it fails to load load standard module sha1 + -> try module sha1_z990, if it fails to load standard module sha1 the 'probe' statement is currently not supported in modprobe.conf diff --git a/Documentation/s390/s390dbf.txt b/Documentation/s390/s390dbf.txt index 2095a27..389e0e5 100644 --- a/Documentation/s390/s390dbf.txt +++ b/Documentation/s390/s390dbf.txt @@ -83,8 +83,8 @@ Example: It is also possible to deactivate the debug feature globally for every debug log. You can change the behavior using 2 sysctl parameters in /proc/sys/s390dbf: -There are currently 2 possible triggers, which stop the debug feature -globally. The first possbility is to use the "debug_active" sysctl. If +There are currently 2 possible triggers, which stop the debug feature +globally. The first possibility is to use the "debug_active" sysctl. If set to 1 the debug feature is running. If "debug_active" is set to 0 the debug feature is turned off. The second trigger which stops the debug feature is an kernel oops. |
