From: Robert Karszniewicz <r.karszniewicz@phytec.de>
To: barebox@lists.infradead.org
Subject: [RFC PATCH v2 0/3] Introduce global.bootm.root_dev env var for booting via PARTUUID
Date: Wed, 5 Aug 2020 12:10:04 +0200 [thread overview]
Message-ID: <1596622207-286083-1-git-send-email-r.karszniewicz@phytec.de> (raw)
This patch introduces a new env var which specifies which device is the
rootfs device to be used in Linux, passed to Linux via bootargs,
identified by the rootfs partition's PARTUUID.
global.bootm.root_dev supplements global.bootm.appendroot, in that it
overrides appendroot's naïve default, which picks the partition that the
kernel resides on (global.bootm.image).
Example:
detect mmc2
global.bootm.image='/mnt/mmc2.0/zImage'
global.bootm.appendroot=1
global.bootm.root_dev=/dev/mmc2.1
boot mmc
For proper patch, I would squash all commits.
Changes from v1:
- renamed env var s/root/root_dev/
- used filesystem-agnostic approach (root_dev now takes a /dev/ instead
of a mounted partition)
Robert Karszniewicz (3):
bootm: add env var root_dev
globalvar: add bootm.root_dev
bootm: handle global.bootm.root_dev
common/bootm.c | 18 ++++++++++++++++--
include/bootm.h | 2 ++
2 files changed, 18 insertions(+), 2 deletions(-)
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-08-05 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 10:10 Robert Karszniewicz [this message]
2020-08-05 10:10 ` [RFC PATCH v2 1/3] bootm: add env var root_dev Robert Karszniewicz
2020-08-05 10:10 ` [RFC PATCH v2 2/3] globalvar: add bootm.root_dev Robert Karszniewicz
2020-08-05 10:10 ` [RFC PATCH v2 3/3] bootm: handle global.bootm.root_dev Robert Karszniewicz
2020-08-05 10:15 ` Robert Karszniewicz
2020-08-10 9:45 ` 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=1596622207-286083-1-git-send-email-r.karszniewicz@phytec.de \
--to=r.karszniewicz@phytec.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