From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: "Simon Glass" <sjg@chromium.org>,
"Artem Lapkin" <email2tema@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
"Jerry Van Baren" <vanbaren@cideas.com>,
"John Keeping" <john@metanate.com>,
"Marek Behún" <kabel@kernel.org>, "Marek Vasut" <marex@denx.de>,
"Pali Rohár" <pali@kernel.org>,
"Patrick Delaunay" <patrick.delaunay@foss.st.com>,
"Pavel Herrmann" <morpheus.ibis@gmail.com>,
"Philippe Reynes" <philippe.reynes@softathome.com>,
"Qu Wenruo" <wqu@suse.com>, "Ramon Fried" <rfried.dev@gmail.com>,
"Stefan Roese" <sr@denx.de>,
linux-btrfs@vger.kernel.org
Subject: [PATCH v2 00/14] vbe: Support device tree fixups for OS requests
Date: Tue, 11 Oct 2022 09:47:06 -0600 [thread overview]
Message-ID: <20221011154720.550320-1-sjg@chromium.org> (raw)
VBE provides the ability for an OS to request that information be passed
to it when it is booted. This is added into the /chosen node, in addition
to things like the bootargs for Linux, for example.
VBE's OS requests are intended to replace the need for the EFI 'boot-time
services'. This works via a 'stub' which runs before Linux, collects the
information from U-Boot, writes it to the device tree (mostly) and then
jumps to Linux with the updated device tree.
Rather than just jumping into Linux and waiting for it to request things
from U-Boot, we can look at the requests in the FIT and process them
before jumping to Linux. This is simpler and easier to test. It is also
more deterministic, since we can tell whether we might lack something
needed by Linux, before jumping to it.
This series adds initial support for OS requests, with just a few simple
ones provided. Further work will expand these out.
Changes in v2:
- Add new patch to update docs about oftree_from_fdt()
Simon Glass (14):
bootm: Change incorrect 'unsupported' error
bootm: Avoid returning error codes from command
bootm: Drop #ifdef from do_bootm()
boot: Correct handling of addresses in boot_relocate_fdt()
fs: Quieten down the filesystems more
fdt: Show a message when the working FDT changes
bootstd: Move VBE setup into a shared function
sandbox: Support FDT fixups
boot: Pass the correct FDT to the EVT_FT_FIXUP event
boot: Tidy up logging and naming in vbe_simple
test: Move common FIT code into a separate fit_util file
vbe: Add fixups for a basic set of OS requests
dm: core: Update docs about oftree_from_fdt()
vbe: Add a test for VBE device tree fixups
arch/sandbox/lib/bootm.c | 17 ++
boot/Makefile | 2 +-
boot/bootm.c | 2 +-
boot/image-fdt.c | 37 ++--
boot/vbe_fixup.c | 233 ++++++++++++++++++++++++++
boot/vbe_simple.c | 16 +-
cmd/bootm.c | 25 +--
cmd/fdt.c | 1 +
configs/sandbox_flattree_defconfig | 2 +-
disk/part_efi.c | 15 +-
doc/develop/driver-model/livetree.rst | 2 +-
doc/develop/vbe.rst | 3 +-
doc/usage/cmd/fdt.rst | 1 +
fs/btrfs/disk-io.c | 7 +-
fs/ext4/ext4_common.c | 2 +-
fs/fs_internal.c | 3 +-
include/dm/ofnode.h | 3 +
test/boot/Makefile | 1 +
test/boot/bootflow.c | 2 +
test/boot/bootstd_common.c | 49 ++++++
test/boot/bootstd_common.h | 16 ++
test/boot/vbe_fixup.c | 59 +++++++
test/boot/vbe_simple.c | 34 +---
test/cmd/fdt.c | 11 +-
test/py/tests/fit_util.py | 93 ++++++++++
test/py/tests/test_event_dump.py | 1 +
test/py/tests/test_fit.py | 79 +--------
test/py/tests/test_vbe.py | 123 ++++++++++++++
28 files changed, 684 insertions(+), 155 deletions(-)
create mode 100644 boot/vbe_fixup.c
create mode 100644 test/boot/vbe_fixup.c
create mode 100644 test/py/tests/fit_util.py
create mode 100644 test/py/tests/test_vbe.py
--
2.38.0.rc1.362.ged0d419d3c-goog
next reply other threads:[~2022-10-11 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 15:47 Simon Glass [this message]
2022-10-11 15:47 ` [PATCH v2 05/14] fs: Quieten down the filesystems more Simon Glass
2022-10-17 21:30 ` Simon Glass
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=20221011154720.550320-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=daniel@makrotopia.org \
--cc=email2tema@gmail.com \
--cc=john@metanate.com \
--cc=kabel@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=marex@denx.de \
--cc=morpheus.ibis@gmail.com \
--cc=pali@kernel.org \
--cc=patrick.delaunay@foss.st.com \
--cc=philippe.reynes@softathome.com \
--cc=rfried.dev@gmail.com \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=vanbaren@cideas.com \
--cc=wqu@suse.com \
--cc=xypron.glpk@gmx.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;
as well as URLs for NNTP newsgroup(s).