From: Michael Olbrich <m.olbrich@pengutronix.de>
To: oss-tools@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [OSS-Tools] [PATCH 0/4] improve barebox-state support on EFI system
Date: Mon, 24 Jan 2022 12:21:39 +0100 [thread overview]
Message-ID: <20220124112143.3016473-1-m.olbrich@pengutronix.de> (raw)
Hi,
This adds support for backend-diskuuid / backend-offset. The corresponding
barebox patches can be found here:
https://lore.barebox.org/barebox/20220124100458.2924679-1-m.olbrich@pengutronix.de/
The mount point for the ESP is quite standardized. So let barebox-state
look there if nothing is found in sysfs/procfs. This way, barebox-state
works on EFI without manually specifying the dtb file.
Michael
Michael Olbrich (4):
state: support deep probe
state: implement helper to find device path from diskuuid
state: support backend-diskuuid / backend-offset
state: automatically find state.dtb in the ESP
Makefile.am | 1 +
src/barebox-state-compat.c | 64 ++++++++++++++++++++++++++++++++++++++
src/barebox-state.c | 24 ++++++++++++++
src/barebox-state/state.c | 53 ++++++++++++++++++++++---------
src/libbb.h | 2 ++
5 files changed, 129 insertions(+), 15 deletions(-)
create mode 100644 src/barebox-state-compat.c
--
2.30.2
_______________________________________________
OSS-Tools mailing list
OSS-Tools@pengutronix.de
next reply other threads:[~2022-01-24 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 11:21 Michael Olbrich [this message]
2022-01-24 11:21 ` [OSS-Tools] [PATCH 1/4] state: support deep probe Michael Olbrich
2022-01-24 11:21 ` [OSS-Tools] [PATCH 2/4] state: implement helper to find device path from diskuuid Michael Olbrich
2022-01-24 11:21 ` [OSS-Tools] [PATCH 3/4] state: support backend-diskuuid / backend-offset Michael Olbrich
2022-01-24 11:21 ` [OSS-Tools] [PATCH 4/4] state: automatically find state.dtb in the ESP Michael Olbrich
2022-02-05 23:37 ` [OSS-Tools] [PATCH 0/4] improve barebox-state support on EFI system Roland Hieber
2022-02-06 7:22 ` Michael Olbrich
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=20220124112143.3016473-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=oss-tools@pengutronix.de \
/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