Patched in Tegra support.

2 files changed, 45 insertions, 10 deletions

diff --git a/Documentation/s390/3270.txt b/Documentation/s390/3270.txt
index 7c715de9977..7a5c73a7ed7 100644
--- a/Documentation/s390/3270.txt
+++ b/Documentation/s390/3270.txt
@@ -47,9 +47,9 @@ including the console 3270, changes subchannel identifier relative to
 one another.  ReIPL as soon as possible after running the configuration
 script and the resulting /tmp/mkdev3270.
 
-If you have chosen to make tub3270 a module, you add a line to a
-configuration file under /etc/modprobe.d/.  If you are working on a VM
-virtual machine, you can use DEF GRAF to define virtual 3270 devices.
+If you have chosen to make tub3270 a module, you add a line to
+/etc/modprobe.conf.  If you are working on a VM virtual machine, you
+can use DEF GRAF to define virtual 3270 devices.
 
 You may generate both 3270 and 3215 console support, or one or the
 other, or neither.  If you generate both, the console type under VM is
@@ -60,7 +60,7 @@ at boot time to a 3270 if it is a 3215.
 
 In brief, these are the steps:
         1. Install the tub3270 patch
-        2. (If a module) add a line to a file in /etc/modprobe.d/*.conf
+        2. (If a module) add a line to /etc/modprobe.conf
         3. (If VM) define devices with DEF GRAF
         4. Reboot
         5. Configure
@@ -84,12 +84,13 @@ Here are the installation steps in detail:
                 make modules_install
 
         2. (Perform this step only if you have configured tub3270 as a
-        module.)  Add a line to a file /etc/modprobe.d/*.conf to automatically
-        load the driver when it's needed.  With this line added, you will see
-        login prompts appear on your 3270s as soon as boot is complete (or
-        with emulated 3270s, as soon as you dial into your vm guest using the
-        command "DIAL <vmguestname>").  Since the line-mode major number is
-        227, the line to add should be:
+        module.)  Add a line to /etc/modprobe.conf to automatically
+        load the driver when it's needed.  With this line added,
+        you will see login prompts appear on your 3270s as soon as
+        boot is complete (or with emulated 3270s, as soon as you dial
+        into your vm guest using the command "DIAL <vmguestname>").
+        Since the line-mode major number is 227, the line to add to
+        /etc/modprobe.conf should be:
                 alias char-major-227 tub3270
 
         3. Define graphic devices to your vm guest machine, if you
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt
index 462321c1aee..efe998becc5 100644
--- a/Documentation/s390/Debugging390.txt
+++ b/Documentation/s390/Debugging390.txt
@@ -41,6 +41,7 @@ ldd
 Debugging modules
 The proc file system
 Starting points for debugging scripting languages etc.
+Dumptool & Lcrash
 SysRq
 References
 Special Thanks
@@ -2454,6 +2455,39 @@ jdb <filename> another fully interactive gdb style debugger.
 
 
 
+Dumptool & Lcrash ( lkcd )
+==========================
+Michael Holzheu & others here at IBM have a fairly mature port of 
+SGI's lcrash tool which allows one to look at kernel structures in a
+running kernel.
+
+It also complements a tool called dumptool which dumps all the kernel's
+memory pages & registers to either a tape or a disk.
+This can be used by tech support or an ambitious end user do
+post mortem debugging of a machine like gdb core dumps.
+
+Going into how to use this tool in detail will be explained
+in other documentation supplied by IBM with the patches & the 
+lcrash homepage http://oss.sgi.com/projects/lkcd/ & the lcrash manpage.
+
+How they work
+-------------
+Lcrash is a perfectly normal program,however, it requires 2 
+additional files, Kerntypes which is built using a patch to the 
+linux kernel sources in the linux root directory & the System.map.
+
+Kerntypes is an objectfile whose sole purpose in life
+is to provide stabs debug info to lcrash, to do this
+Kerntypes is built from kerntypes.c which just includes the most commonly
+referenced header files used when debugging, lcrash can then read the
+.stabs section of this file.
+
+Debugging a live system it uses /dev/mem
+alternatively for post mortem debugging it uses the data 
+collected by dumptool.
+
+
+
 SysRq
 =====
 This is now supported by linux for s/390 & z/Architecture.