From: Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> Signed-off-by: Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> --- Changes: v2: leave iomem output as is Documentation/filesystems/pstore.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst index 74acd87..0f3a223 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,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':: -- 2.1.4 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
