From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Adrian Negreanu <adrian.negreanu@nxp.com>
Subject: [PATCH 00/11] firmware: qemu_fw_cfg: implement file system
Date: Thu, 13 Mar 2025 11:17:17 +0100 [thread overview]
Message-ID: <20250313101728.3546902-1-a.fatoum@pengutronix.de> (raw)
The character device we currently have is cumbersome to use.
The Linux way to access it at /sys/firmware/qemu_fw_cfg
is much nicer to use, so this series adds support for a similar
FS to barebox.
A very nice result of having file system access to the QEMU variables
in barebox is that we get a trivial way to pass data to barebox.
To make it even more convenient to use, this series enables overriding
individual files in the environment via the new mechanism, e.g.:
pytest --env nv/boot.default=fit --env boot/fit=@boot.sh
Ahmad Fatoum (11):
video: ramfb: fix frame buffer screen size
firmware: qemu_fw_cfg: drop duplicate definitions
firmware: qemu_fw_cfg: add support for seeking
firmware: qemu_fw_cfg: rename from /dev/fw_cfg0 to /dev/fw_cfg
fs: add qemu_fw_cfg file system
firmware: qemu_fw_cfg: register at device initcall level
video: ramfb: use new qemu fw_cfg FS
libfile: give copy_file a flags parameter
libfile: pass copy_file flags through copy_recursive
libfile: add support for not clobbering files in copy_file
fs: qemu_fw_cfg: support populating environment via QEMU fw_cfg
commands/Kconfig | 4 +-
commands/cp.c | 18 +-
commands/defaultenv.c | 2 +-
commands/tftp.c | 2 +-
common/fastboot.c | 2 +-
conftest.py | 22 ++
defaultenv/defaultenv.c | 22 ++
drivers/firmware/qemu_fw_cfg.c | 63 +++--
drivers/video/Kconfig | 2 +-
drivers/video/ramfb.c | 116 ++++------
fs/Kconfig | 7 +
fs/Makefile | 1 +
fs/qemu_fw_cfg.c | 404 +++++++++++++++++++++++++++++++++
include/envfs.h | 5 +
include/libfile.h | 8 +-
include/string.h | 5 +
lib/libfile.c | 43 +++-
17 files changed, 592 insertions(+), 134 deletions(-)
create mode 100644 fs/qemu_fw_cfg.c
--
2.39.5
next reply other threads:[~2025-03-13 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 10:17 Ahmad Fatoum [this message]
2025-03-13 10:17 ` [PATCH 01/11] video: ramfb: fix frame buffer screen size Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 02/11] firmware: qemu_fw_cfg: drop duplicate definitions Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 03/11] firmware: qemu_fw_cfg: add support for seeking Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 04/11] firmware: qemu_fw_cfg: rename from /dev/fw_cfg0 to /dev/fw_cfg Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 05/11] fs: add qemu_fw_cfg file system Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 06/11] firmware: qemu_fw_cfg: register at device initcall level Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 07/11] video: ramfb: use new qemu fw_cfg FS Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 08/11] libfile: give copy_file a flags parameter Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 09/11] libfile: pass copy_file flags through copy_recursive Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 10/11] libfile: add support for not clobbering files in copy_file Ahmad Fatoum
2025-03-13 10:17 ` [PATCH 11/11] fs: qemu_fw_cfg: support populating environment via QEMU fw_cfg Ahmad Fatoum
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=20250313101728.3546902-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=adrian.negreanu@nxp.com \
--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