mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/6] common: boards: qemu: process some standard fw_cfg keys
Date: Mon, 19 Jan 2026 12:33:24 +0100	[thread overview]
Message-ID: <735063a4-5e0f-4b78-8461-aeb9f17b595e@barebox.org> (raw)
In-Reply-To: <aW4R2e0i8N5NF-OM@pengutronix.de>

Hi Sascha,

On 1/19/26 12:13 PM, Sascha Hauer wrote:
> On Thu, Jan 15, 2026 at 01:06:12PM +0100, Ahmad Fatoum wrote:
>> While we have FW_CFG support as file system, there is a number of keys
>> that precede the keys in the file system, which can be useful in some
>> scenarios.
>>
>> Add support for QEMU -uuid, -kernel, -initrd, -append options as well as
>> a /boot/qemu_fw_cfg script that continues booting according to the latter
>> three options.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
>> ---
>>  common/boards/Kconfig                         |   8 +
>>  common/boards/Makefile                        |   1 +
>>  common/boards/qemu/Makefile                   |   4 +
>>  .../defaultenv-qemu_fw_cfg/boot/qemu_fw_cfg   |  12 +
>>  common/boards/qemu/fw_cfg.c                   | 208 ++++++++++++++++++
>>  drivers/firmware/Kconfig                      |   1 +
>>  6 files changed, 234 insertions(+)
>>  create mode 100644 common/boards/qemu/Makefile
>>  create mode 100755 common/boards/qemu/defaultenv-qemu_fw_cfg/boot/qemu_fw_cfg
>>  create mode 100644 common/boards/qemu/fw_cfg.c
>>
>> diff --git a/common/boards/Kconfig b/common/boards/Kconfig
>> index 74947316954b..a9e1b75a7641 100644
>> --- a/common/boards/Kconfig
>> +++ b/common/boards/Kconfig
>> @@ -1,5 +1,13 @@
>>  # SPDX-License-Identifier: GPL-2.0-only
>>  
>> +config BOARD_QEMU
>> +	bool "Extra support for QEMU-emulated boards" if COMPILE_TEST
>> +
>> +config BOARD_QEMU_VIRT
>> +	bool
>> +	select OF_OVERLAY
>> +	select BOARD_QEMU
>> +
>>  config BOARD_QEMU_VIRT
>>  	bool
>>  	select OF_OVERLAY
> 
> You likely intended to just add "select BOARD_QEMU" instead of
> duplicating the option. I'll fix that while applying.

Indeed. Thank you.

Cheers,
Ahmad

> 
> Sascha
> 




  reply	other threads:[~2026-01-19 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 12:06 [PATCH 0/6] firmware: qemu_fw_cfg: improve support Ahmad Fatoum
2026-01-15 12:06 ` [PATCH 1/6] firmware: qemu_fw_cfg: use wider PIO reads if applicable Ahmad Fatoum
2026-01-15 12:06 ` [PATCH 2/6] param: support uuid/guid parameter type Ahmad Fatoum
2026-01-15 12:06 ` [PATCH 3/6] lib: smbios: add support for setting product UUID Ahmad Fatoum
2026-01-15 12:06 ` [PATCH 4/6] common: boards: qemu: process some standard fw_cfg keys Ahmad Fatoum
2026-01-19 11:13   ` Sascha Hauer
2026-01-19 11:33     ` Ahmad Fatoum [this message]
2026-01-15 12:06 ` [PATCH 5/6] firmware: qemu_fw_cfg: add proper DMA and PIO bidirectional operating modes Ahmad Fatoum
2026-01-15 12:06 ` [PATCH 6/6] ARM: configs: multi: enable QEMU FW_CFG Ahmad Fatoum
2026-01-19 12:11 ` [PATCH 0/6] firmware: qemu_fw_cfg: improve support 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=735063a4-5e0f-4b78-8461-aeb9f17b595e@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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