mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/2] Documentation: blspec: Add blspec fixup documentation
Date: Mon, 18 Jan 2021 21:48:50 +0100	[thread overview]
Message-ID: <20210118204850.8420-2-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20210118204850.8420-1-m.felsch@pengutronix.de>

Document the fixup mechanism.

Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
 Documentation/user/booting-linux.rst | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 60babb513c..fd7575bbe9 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -232,6 +232,28 @@ device where the entry is found on. This makes it possible to use the same rootf
 image on different devices without having to specify a different root= option each
 time.
 
+The following environment variables can be used to update the bootloader spec entry
+values on the fly.
+
+.. warning::
+
+  In most use cases this is not necessary. Modifying the bootloader spec values on
+  the fly can trigger unwanted boot behaviours.
+
++-----------------------------------------+
+| name                                    |
++=========================================+
+| global.blspec.fixup.devicetree          |
++-----------------------------------------+
+| global.blspec.fixup.initrd              |
++-----------------------------------------+
+| global.blspec.fixup.options             |
++-----------------------------------------+
+| global.blspec.fixup.linux               |
++-----------------------------------------+
+| global.blspec.fixup.devicetree-overlay  |
++-----------------------------------------+
+
 Network boot
 ------------
 
-- 
2.20.1


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

  reply	other threads:[~2021-01-18 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 20:48 [PATCH 1/2] blspec: allow board files to overwrite config file settings Marco Felsch
2021-01-18 20:48 ` Marco Felsch [this message]
2021-01-19 11:01 ` Sascha Hauer
2021-01-19 11:42   ` Marco Felsch
2021-01-20  9:03     ` Sascha Hauer
2021-01-20 10:54       ` Marco Felsch
2021-01-20 12:31         ` Michael Olbrich
2021-01-20 13:26           ` Marco Felsch

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=20210118204850.8420-2-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --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