mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Adrian Negreanu <adrian.negreanu@nxp.com>
Subject: [PATCH v2 0/4] firmware: qemu_fw_cfg: implement file system
Date: Fri,  6 Jun 2025 09:29:35 +0200	[thread overview]
Message-ID: <20250606072939.2082971-1-a.fatoum@barebox.org> (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

v1 -> v2:
  - drop already upstream patches
  - drop truncate (Sascha)
  - make writing files besides "raw" an error (Sascha)
  - mount file system unconditionally, so environment can be read
    from it

Ahmad Fatoum (4):
  fs: add qemu_fw_cfg file system
  firmware: qemu_fw_cfg: register at device initcall level
  video: ramfb: use new qemu fw_cfg FS
  fs: qemu_fw_cfg: support populating environment via QEMU fw_cfg

 conftest.py                    |  22 ++
 defaultenv/defaultenv.c        |  22 ++
 drivers/firmware/qemu_fw_cfg.c |   2 +-
 drivers/video/Kconfig          |   2 +-
 drivers/video/ramfb.c          |  98 ++------
 fs/Kconfig                     |   7 +
 fs/Makefile                    |   1 +
 fs/qemu_fw_cfg.c               | 446 +++++++++++++++++++++++++++++++++
 include/envfs.h                |   5 +
 include/string.h               |   5 +
 10 files changed, 525 insertions(+), 85 deletions(-)
 create mode 100644 fs/qemu_fw_cfg.c

-- 
2.39.5




             reply	other threads:[~2025-06-06  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  7:29 Ahmad Fatoum [this message]
2025-06-06  7:29 ` [PATCH v2 1/4] fs: add qemu_fw_cfg " Ahmad Fatoum
2025-06-06  7:29 ` [PATCH v2 2/4] firmware: qemu_fw_cfg: register at device initcall level Ahmad Fatoum
2025-06-06  7:29 ` [PATCH v2 3/4] video: ramfb: use new qemu fw_cfg FS Ahmad Fatoum
2025-06-06  7:29 ` [PATCH v2 4/4] 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=20250606072939.2082971-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --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