UPSTREAM: USB: option: blacklist QMI interface on ZTE MF683

[cascardo/linux.git] / Documentation / ramoops.txt

diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 8fb1ba7..2cf8cb9 100644 (file)
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramoops.txt
@@ -3,7 +3,7 @@ Ramoops oops/panic logger
 
 Sergiu Iordache <sergiu@chromium.org>
 
-Updated: 8 August 2011
+Updated: 4 June 2012
 
 0. Introduction
 
@@ -33,8 +33,20 @@ on restart (i.e. new dumps after the restart will overwrite old ones).
 2. Setting the parameters
 
 Setting the ramoops parameters can be done in 2 different manners:
- 1. Use the module parameters (which have the names of the variables described
- as before).
+ 1. Use the Flattened Device Tree to specify the platform data.
+ An example of this is:
+  arch/arm/boot/dts/$BOARD.dts:
+        ramoops {
+                compatible = "ramoops";
+                reg = <0x41f00000 0x00100000>;
+                record-size = <0x00020000>;
+                dump-oops;
+        };
+ The "reg = <0x41f00000 0x00100000>" line tells ramoops to use 1MB at
+ physical address 0x41f00000.
+ The "record-size = <0x00020000>" line specifies a record size of 128KB.
+ The optional "dump-oops" line tells ramoops to dump oopses as well as panics.
+
  2. Use a platform device and set the platform data. The parameters can then
  be set through that platform data. An example of doing that is: