qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Shaoqin Huang <shahuang@redhat.com>
Cc: "Cédric Le Goater" <clg@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-arm@nongnu.org, "Eric Auger" <eauger@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v2] ramfb: Add property to control if load the romfile
Date: Tue, 10 Jun 2025 10:00:46 -0600	[thread overview]
Message-ID: <20250610100046.3577ee29.alex.williamson@redhat.com> (raw)
In-Reply-To: <c2e0ece0-1ee1-4867-b01c-20e847ef6af3@redhat.com>

On Mon, 9 Jun 2025 13:16:14 +0800
Shaoqin Huang <shahuang@redhat.com> wrote:

> On 6/6/25 4:07 PM, Cédric Le Goater wrote:
> > On 6/6/25 10:06, Cédric Le Goater wrote:  
> >> On 6/6/25 09:52, Daniel P. Berrangé wrote:  
> >>> On Fri, Jun 06, 2025 at 03:02:34AM -0400, Shaoqin Huang wrote:  
> >>>> 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.
> >>>>
> >>>> Because only seabios will use the vgabios-ramfb.bin, load the rom logic
> >>>> is x86-specific. For other !x86 platforms, the edk2 ships an EFI driver
> >>>> for ramfb, so they don't need to load the romfile.
> >>>>
> >>>> So add a new property use_legacy_x86_rom in both ramfb and vfio_pci
> >>>> device, because the vfio display also use the ramfb_setup() to load
> >>>> the vgabios-ramfb.bin file.
> >>>>
> >>>> After have this property, the machine type can set the compatibility to
> >>>> not load the vgabios-ramfb.bin if the arch doesn't need it.  
> >>>
> >>> Can you make this a series, with an additional patch that updates the
> >>> current in-dev machine types to use this new property, so we're clear
> >>> about the proposed usage.  
> >>
> >> yes. And please change the vfio-pci property name to use underscores.  
> > 
> > Sorry, to *not* use underscores : use-legacy-x86-rom  
> 
> Thanks for pointing out it. Will fix it.

It's also not evident from the property that this is restricted to
ramfb behavior.  Should the option on the vfio-pci device be prefixed
with ramfb?  Thanks,

Alex



  reply	other threads:[~2025-06-10 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  7:02 [PATCH v2] ramfb: Add property to control if load the romfile Shaoqin Huang
2025-06-06  7:52 ` Daniel P. Berrangé
2025-06-06  8:06   ` Cédric Le Goater
2025-06-06  8:07     ` Cédric Le Goater
2025-06-09  5:16       ` Shaoqin Huang
2025-06-10 16:00         ` Alex Williamson [this message]
2025-06-06  9:04   ` Philippe Mathieu-Daudé
2025-06-06  9:15     ` Daniel P. Berrangé
2025-06-06 16:22     ` Pierrick Bouvier
2025-06-09  3:37   ` Shaoqin Huang

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=20250610100046.3577ee29.alex.williamson@redhat.com \
    --to=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=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shahuang@redhat.com \
    /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).