All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Vallejo <agarciav@amd.com>
To: "Jürgen Groß" <jgross@suse.com>,
	"Anthony PERARD" <anthony@xenproject.org>
Cc: xen-devel@lists.xenproject.org,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	Xen-devel <xen-devel-bounces@lists.xenproject.org>
Subject: Re: [PATCH v2 2/6] docs: remove qemu-traditional support from documentation
Date: Mon, 28 Apr 2025 16:31:59 +0100	[thread overview]
Message-ID: <D9IDPE8Q5XKK.2CSC9N1BMSU2Y@amd.com> (raw)
In-Reply-To: <198ec36e-15e3-491a-bd15-d440d9d578da@suse.com>

On Mon Apr 28, 2025 at 4:15 PM BST, Jürgen Groß wrote:
> On 28.04.25 17:12, Alejandro Vallejo wrote:
>> On Thu Apr 24, 2025 at 10:41 AM BST, Anthony PERARD wrote:
>>> On Tue, Apr 08, 2025 at 02:35:20PM +0200, Juergen Gross wrote:
>>>> @@ -1903,10 +1894,7 @@ it may be useful to request a different one, like UEFI.
>>>>   
>>>>   =item B<rombios>
>>>>   
>>>> -Loads ROMBIOS, a 16-bit x86 compatible BIOS. This is used by default
>>>> -when B<device_model_version=qemu-xen-traditional>. This is the only BIOS
>>>> -option supported when B<device_model_version=qemu-xen-traditional>. This is
>>>> -the BIOS used by all previous Xen versions.
>>>> +Loads ROMBIOS, a 16-bit x86 compatible BIOS.
>>>
>>> This option is not valid anymore, libxl will complain with:
>>>      "qemu-xen does not support bios=rombios."
>> 
>> Sounds like a good time to remove bios=rombios altogether and strictly
>> support bios=seabios only (plus the override).
>
> Fine with me.
>
> But probably we should NOT drop building RomBIOS, right?

On staging/master? I don't think we ought to waste cycles rebuilding it.
It'd only be a dependency for stable trees, so shouldn't it be built
there instead? Then by the time we don't support it in stable either
(because they all went EOL) it'd naturally just stop being built.

The mechanics of how that would work I'm not sure. We have per
stable-tree pipelines. Do they build everything, Anthony?

Cheers,
Alejandro


  reply	other threads:[~2025-04-28 15:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 12:35 [PATCH v2 0/6] remove qemu-traditional Juergen Gross
2025-04-08 12:35 ` [PATCH v2 1/6] SUPPORT.md: make Linux based stubdom fully supported Juergen Gross
2025-04-24 11:42   ` Oleksii Kurochko
2025-04-08 12:35 ` [PATCH v2 2/6] docs: remove qemu-traditional support from documentation Juergen Gross
2025-04-24  9:41   ` Anthony PERARD
2025-04-28 12:50     ` Jürgen Groß
2025-04-28 15:12     ` Alejandro Vallejo
2025-04-28 15:15       ` Jürgen Groß
2025-04-28 15:31         ` Alejandro Vallejo [this message]
2025-04-28 15:36           ` Jürgen Groß
2025-04-08 12:35 ` [PATCH v2 3/6] tools: remove support for running a guest with qemu-traditional Juergen Gross
2025-04-24 13:41   ` Anthony PERARD
2025-04-28 13:04     ` Juergen Gross
2025-04-08 12:35 ` [PATCH v2 4/6] tools: remove qemu-traditional Juergen Gross
2025-04-24 10:07   ` Oleksii Kurochko
2025-04-24 14:43   ` Anthony PERARD
2025-04-28 13:06     ` Jürgen Groß
2025-04-08 12:35 ` [PATCH v2 5/6] stubdom: remove ancient stubdom-dm script Juergen Gross
2025-04-24 14:47   ` Anthony PERARD
2025-04-08 12:35 ` [PATCH v2 6/6] build: don't require full tools build for building stubdoms Juergen Gross
2025-04-24 14:50   ` Anthony PERARD
2025-04-24  9:12 ` [PATCH v2 0/6] remove qemu-traditional Juergen Gross

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=D9IDPE8Q5XKK.2CSC9N1BMSU2Y@amd.com \
    --to=agarciav@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=anthony@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel-bounces@lists.xenproject.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.