From: Shaoqin Huang <shahuang@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: qemu-arm@nongnu.org, "Eric Auger" <eauger@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v1] ramfb: Add property to control if load the romfile
Date: Fri, 6 Jun 2025 11:20:21 +0800 [thread overview]
Message-ID: <27ea9c1e-61eb-4ea4-b3e4-e9d06b4b4ce5@redhat.com> (raw)
In-Reply-To: <68f4f244-db07-4f65-9ca5-3cb9b70c9e61@linaro.org>
Hi, guys
Thanks for all of your suggestions.
On 6/5/25 11:11 PM, Philippe Mathieu-Daudé wrote:
> On 5/6/25 14:21, Gerd Hoffmann wrote:
>> Hi,
>>
>>>> Now the ramfb will load the vgabios-ramfb.bin unconditionally, but only
>>>> the x86 need the vgabios-ramfb.bin, this can cause that when use the
>>>> release package on arm64 it can't find the vgabios-ramfb.bin.
>>
>>> Simpler to directly pass the ROM path instead of using a boolean,
>>> so board (or CLI) could pass path to non-x86 rom.
>>
>> The rom is loaded into a fw_cfg file which only seabios will look at.
>> So this rom logic is x86-specific.
>>
>> edk2 ships an EFI driver for ramfb, that is how ramfb is used on !x86
>> platforms today, and I don't expect that to change.
>>
>> IMHO a bool is perfectly fine here, I don't think we will ever need the
>> flexibility to specify some other rom here.
>
> Understood, better then! Maybe name the boolean "use_legacy_x86_rom" and
> add a comment explaining EFI driver is expected on !x86?
I think the "use_legacy_x86_rom" is good, I will change the name to it.
And I will add a comment to explain it.
Thanks,
Shaoqin
>
> Regards,
>
> Phil.
>
--
Shaoqin
next prev parent reply other threads:[~2025-06-06 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 3:03 [PATCH v1] ramfb: Add property to control if load the romfile Shaoqin Huang
2025-06-05 5:11 ` Philippe Mathieu-Daudé
2025-06-05 12:21 ` Gerd Hoffmann
2025-06-05 14:24 ` Cédric Le Goater
2025-06-05 14:40 ` Daniel P. Berrangé
2025-06-06 6:59 ` Shaoqin Huang
2025-06-05 15:11 ` Philippe Mathieu-Daudé
2025-06-06 3:20 ` Shaoqin Huang [this message]
2025-06-06 6:36 ` Philippe Mathieu-Daudé
2025-06-05 14:26 ` Cédric Le Goater
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=27ea9c1e-61eb-4ea4-b3e4-e9d06b4b4ce5@redhat.com \
--to=shahuang@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eauger@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).