Documentation/filesystems: pstore: fix formatting
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
This commit is contained in:
parent
74d09efa54
commit
1a0cebc572
|
@ -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,7 +41,7 @@ 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'::
|
||||
|
|
Loading…
Reference in New Issue