From: Enrico Jorns <ejo@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Enrico Jorns <ejo@pengutronix.de>
Subject: [PATCH 5/8] doc: bootchooser: note how to actually start the bootchooser
Date: Fri, 15 Feb 2019 13:53:45 +0100 [thread overview]
Message-ID: <20190215125348.12851-6-ejo@pengutronix.de> (raw)
In-Reply-To: <20190215125348.12851-1-ejo@pengutronix.de>
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
---
Documentation/user/bootchooser.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index 7d7564b552..0c5e56407a 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -16,6 +16,17 @@ and a storage backend for saving status information.
Currently supported storage backends are either nv variables or the
barebox *state* framework.
+The *Bootchooser* itself is executed as a normal barebox boot target, i.e. one
+can start it via::
+
+ boot bootchooser
+
+or by e.g. setting ``boot.default`` to ``bootchooser``.
+
+.. note:: As ``boot.default`` accepts multiple values, it can also be used to
+ specify a fallback boot target in case the bootchooser fails booting, e.g.
+ ``bootchooser recovery``.
+
Bootchooser Targets
-------------------
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-02-15 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 12:53 [PATCH 0/8] Bootchooser Documentation Update Enrico Jorns
2019-02-15 12:53 ` [PATCH 1/8] doc: bootchooser: fix typos etc Enrico Jorns
2019-02-15 12:53 ` [PATCH 2/8] doc: bootchooser: explicitly note configuration vs. storage backend Enrico Jorns
2019-02-15 12:53 ` [PATCH 3/8] doc: bootchooser: be more explicit what bootchooser.state_prefix is for Enrico Jorns
2019-02-15 12:53 ` [PATCH 4/8] doc: bootchooser: be more explicit about attempts reset on successful boot Enrico Jorns
2019-02-15 12:53 ` Enrico Jorns [this message]
2019-02-15 12:53 ` [PATCH 6/8] doc: bootchooser: be more explicit about when the bootchooser terminates Enrico Jorns
2019-02-15 12:53 ` [PATCH 7/8] doc: bootchooser: add details about bootchooser.reset_attempts handling Enrico Jorns
2019-02-15 12:53 ` [PATCH 8/8] doc: bootchooser: add retry handling to algorithm description Enrico Jorns
2019-02-18 8:30 ` [PATCH 0/8] Bootchooser Documentation Update 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=20190215125348.12851-6-ejo@pengutronix.de \
--to=ejo@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