From af85a0f8864e5888406bb13c3e3f99c5770959ca Mon Sep 17 00:00:00 2001
From: Philipp Zabel
Date: Fri, 15 Mar 2019 10:14:51 +0100
Subject: pstore: pass ramoops configuration to kernel via device tree
Instead of setting ramoops module parameters on the kernel command line,
add a /reserved-memory/ramoops node to the device tree via of_fixup.
Signed-off-by: Philipp Zabel
Documentation-added-by: Juergen Borleis
Signed-off-by: Sascha Hauer
---
Documentation/filesystems/pstore.rst | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
(limited to 'Documentation')
diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst
index c128daae9f..00a5a05537 100644
--- a/Documentation/filesystems/pstore.rst
+++ b/Documentation/filesystems/pstore.rst
@@ -42,10 +42,12 @@ written):
To use pstore/RAMOOPS both Barebox and Kernel have to be compiled with pstore
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.
+layout via devicetree or - as a fallback - over the kernel command line.
+To ensure both worlds are using the same memory layout, the required
+configuration data for the kernel is generated on-the-fly prior booting a kernel.
+For the devicetree use case Barebox adapts the kernel's devicetree, for the
+kernel command line fallback the variable ``global.linux.bootargs.ramoops`` is
+created and its content used to build the kernel command line.
You can adapt the *pstore* parameters in Barebox menuconfig.
--
cgit v1.2.3