From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gud20-0000XG-VQ for barebox@lists.infradead.org; Fri, 15 Feb 2019 12:55:55 +0000 From: Enrico Jorns Date: Fri, 15 Feb 2019 13:53:42 +0100 Message-Id: <20190215125348.12851-3-ejo@pengutronix.de> In-Reply-To: <20190215125348.12851-1-ejo@pengutronix.de> References: <20190215125348.12851-1-ejo@pengutronix.de> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: [PATCH 2/8] doc: bootchooser: explicitly note configuration vs. storage backend To: barebox@lists.infradead.org Cc: Enrico Jorns It is quite confusing for some users sometimes where to set what. Signed-off-by: Enrico Jorns --- Documentation/user/bootchooser.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst index 667ab7d736..f1251d0c2e 100644 --- a/Documentation/user/bootchooser.rst +++ b/Documentation/user/bootchooser.rst @@ -11,6 +11,11 @@ from scratch over and over again. The *bootchooser* works on abstract boot targets, each with a set of properties and implements an algorithm which selects the highest priority target to boot. +To make the *bootchooser* work requires a fixed set of configuration parameters +and a storage backend for saving status information. +Currently supported storage backends are either nv variables or the +barebox *state* framework. + Bootchooser Targets ------------------- -- 2.20.1 _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox