From: Michael Olbrich <m.olbrich@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [PATCH 0/3] state: find backend with UUID but without a partition
Date: Mon, 24 Jan 2022 11:04:55 +0100 [thread overview]
Message-ID: <20220124100458.2924679-1-m.olbrich@pengutronix.de> (raw)
Hi,
When adding state with a barebox update on existing devices, then it's not
always possible to add a partition for it. But currently that's the only
way to specify the state backend on x86_64/EFI devices.
This adds support backend-diskuuid / backend-offset. This way the backend
is defined by a UUID that selects a disk and an offset within that disk.
Michael
Michael Olbrich (3):
cdev: rename partuuid to uuid
cdev: add diskuuid support
state: support backend-diskuuid / backend-offset
common/bootm.c | 6 ++---
common/partitions.c | 2 +-
common/partitions/dos.c | 3 +++
common/partitions/efi.c | 2 ++
common/partitions/parser.h | 2 +-
common/state/state.c | 55 +++++++++++++++++++++++++-------------
fs/devfs-core.c | 16 ++++++++++-
fs/fs.c | 4 +--
include/driver.h | 5 ++--
include/fs.h | 12 +++++++++
10 files changed, 79 insertions(+), 28 deletions(-)
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2022-01-24 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:04 Michael Olbrich [this message]
2022-01-24 10:04 ` [PATCH 1/3] cdev: rename partuuid to uuid Michael Olbrich
2022-01-24 10:04 ` [PATCH 2/3] cdev: add diskuuid support Michael Olbrich
2022-01-24 10:04 ` [PATCH 3/3] state: support backend-diskuuid / backend-offset Michael Olbrich
2022-01-26 7:57 ` Sascha Hauer
2022-01-26 9:35 ` Michael Olbrich
2022-01-26 10:15 ` Sascha Hauer
2022-01-26 11:16 ` Michael Olbrich
2022-01-27 0:18 ` Trent Piepho
2022-01-27 12:39 ` Sascha Hauer
2022-01-27 18:53 ` Trent Piepho
2022-01-28 7:48 ` 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=20220124100458.2924679-1-m.olbrich@pengutronix.de \
--to=m.olbrich@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