mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: yegorslists@googlemail.com
To: barebox@lists.infradead.org
Subject: [PATCH 2/2] Documentation/filesystems: pstore: fix formatting
Date: Mon, 29 Feb 2016 15:39:52 +0100	[thread overview]
Message-ID: <1456756792-21321-2-git-send-email-yegorslists@googlemail.com> (raw)
In-Reply-To: <1456756792-21321-1-git-send-email-yegorslists@googlemail.com>

From: Yegor Yefremov <yegorslists@googlemail.com>

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 Documentation/filesystems/pstore.rst | 51 ++++++++++++++++++------------------
 1 file changed, 26 insertions(+), 25 deletions(-)

diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst
index 74acd87..a8079c2 100644
--- a/Documentation/filesystems/pstore.rst
+++ b/Documentation/filesystems/pstore.rst
@@ -12,6 +12,7 @@ messages are stored by the kernel in a specified RAM area which is never
 overwritten by any user. This data can be accessed after a reboot through
 /pstore in Barebox or the kernel. The pstore filesystem is automatically mounted
 at boot::
+
 	none on / type ramfs
 	none on /dev type devfs
 	none on /pstore type pstore
@@ -40,35 +41,35 @@ and RAM backend support. The kernel receives the parameters describing the
 layout over the kernel command line. These parameters are automatically
 generated by Barebox. You can change these parameters in Barebox menuconfig. The
 RAMOOPS parameters for the Kernel are stored in the variable
-global.linux.bootargs.ramoops::
+global.linux.bootargs.ramoops.
 
 To see where the RAMOOPS area is located, you can execute iomem in Barebox. The
 RAMOOPS area is listed as 'persistent ram'::
 
-  0x10000000 - 0x1fffffff (size 0x10000000) ram0
-    0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
-    0x1fcf8180 - 0x1fcfffff (size 0x00007e80) board data
-    0x1fd00000 - 0x1fd6eeff (size 0x0006ef00) barebox
-    0x1fd6ef00 - 0x1fd88dff (size 0x00019f00) barebox data
-    0x1fd88e00 - 0x1fd8c3db (size 0x000035dc) bss
-    0x1fdf4000 - 0x1fe13fff (size 0x00020000) persistent ram
-    0x1fe14000 - 0x1fe33fff (size 0x00020000) persistent ram
-    0x1fe34000 - 0x1fe53fff (size 0x00020000) persistent ram
-    0x1fe54000 - 0x1fe73fff (size 0x00020000) persistent ram
-    0x1fe74000 - 0x1fe93fff (size 0x00020000) persistent ram
-    0x1fe94000 - 0x1feb3fff (size 0x00020000) persistent ram
-    0x1feb4000 - 0x1fed3fff (size 0x00020000) persistent ram
-    0x1fed4000 - 0x1fef3fff (size 0x00020000) persistent ram
-    0x1fef4000 - 0x1ff13fff (size 0x00020000) persistent ram
-    0x1ff14000 - 0x1ff33fff (size 0x00020000) persistent ram
-    0x1ff34000 - 0x1ff53fff (size 0x00020000) persistent ram
-    0x1ff54000 - 0x1ff73fff (size 0x00020000) persistent ram
-    0x1ff74000 - 0x1ff93fff (size 0x00020000) persistent ram
-    0x1ff94000 - 0x1ffb3fff (size 0x00020000) persistent ram
-    0x1ffb4000 - 0x1ffd3fff (size 0x00020000) persistent ram
-    0x1ffd4000 - 0x1fff3fff (size 0x00020000) persistent ram
-    0x1fff4000 - 0x1fff7fff (size 0x00004000) ttb
-    0x1fff8000 - 0x1fffffff (size 0x00008000) stack
+        0x10000000 - 0x1fffffff (size 0x10000000) ram0
+        0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
+        0x1fcf8180 - 0x1fcfffff (size 0x00007e80) board data
+        0x1fd00000 - 0x1fd6eeff (size 0x0006ef00) barebox
+        0x1fd6ef00 - 0x1fd88dff (size 0x00019f00) barebox data
+        0x1fd88e00 - 0x1fd8c3db (size 0x000035dc) bss
+        0x1fdf4000 - 0x1fe13fff (size 0x00020000) persistent ram
+        0x1fe14000 - 0x1fe33fff (size 0x00020000) persistent ram
+        0x1fe34000 - 0x1fe53fff (size 0x00020000) persistent ram
+        0x1fe54000 - 0x1fe73fff (size 0x00020000) persistent ram
+        0x1fe74000 - 0x1fe93fff (size 0x00020000) persistent ram
+        0x1fe94000 - 0x1feb3fff (size 0x00020000) persistent ram
+        0x1feb4000 - 0x1fed3fff (size 0x00020000) persistent ram
+        0x1fed4000 - 0x1fef3fff (size 0x00020000) persistent ram
+        0x1fef4000 - 0x1ff13fff (size 0x00020000) persistent ram
+        0x1ff14000 - 0x1ff33fff (size 0x00020000) persistent ram
+        0x1ff34000 - 0x1ff53fff (size 0x00020000) persistent ram
+        0x1ff54000 - 0x1ff73fff (size 0x00020000) persistent ram
+        0x1ff74000 - 0x1ff93fff (size 0x00020000) persistent ram
+        0x1ff94000 - 0x1ffb3fff (size 0x00020000) persistent ram
+        0x1ffb4000 - 0x1ffd3fff (size 0x00020000) persistent ram
+        0x1ffd4000 - 0x1fff3fff (size 0x00020000) persistent ram
+        0x1fff4000 - 0x1fff7fff (size 0x00004000) ttb
+        0x1fff8000 - 0x1fffffff (size 0x00008000) stack
 
 All pstore files that could be found are added to the /pstore directory. This is
 a read-only filesystem. If you disable the Kconfig option FS_PSTORE_RAMOOPS_RO,
-- 
2.1.4


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-02-29 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 14:39 [PATCH 1/2] Documentation/filesystems: add barebox prompt to the shell commands yegorslists
2016-02-29 14:39 ` yegorslists [this message]
2016-03-01  8:46   ` [PATCH 2/2] Documentation/filesystems: pstore: fix formatting Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1456756792-21321-2-git-send-email-yegorslists@googlemail.com \
    --to=yegorslists@googlemail.com \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox