qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios <seabios@seabios.org>, qemu-devel <qemu-devel@nongnu.org>,
	Marcel Apfelbaum <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] [SeaBIOS] qemu freeze, seabios release
Date: Thu, 11 Jun 2015 10:17:58 +0200	[thread overview]
Message-ID: <55794436.6080803@redhat.com> (raw)
In-Reply-To: <1434008536.27114.18.camel@redhat.com>

On 06/11/15 09:42, Gerd Hoffmann wrote:
>   Hi,
> 
> qemu soft freeze for 2.4 is just around the corner, time to think about
> the seabios release which should be included there.
> 
> A new release from master isn't even planned yet[1], so I think we
> should go for a 1.8.2 stable release.  So, if there are any fixes which
> should be cherry-picked into stable please speak up now.  So far my list
> is pretty short:
> 
>   87f848e vga: rework virtio-vga support
> 
> cheers,
>   Gerd
> 
> [1] It probably makes sense to plan once the tpm support merge
>     is complete.

For the next master release: we've been working with Marcel on properly
formatting OFW devpaths in QEMU, for the "bootorder" fw_cfg file, for
booting off devices behind a PXB. Patches are on qemu-devel (meaning
they should be okay for 2.4). I have patches for OVMF and Marcel is
looking into SeaBIOS. So, I think support for these devpaths too should
be included in the next master release of SeaBIOS.

Thanks
Laszlo

  reply	other threads:[~2015-06-11  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  7:42 [Qemu-devel] qemu freeze, seabios release Gerd Hoffmann
2015-06-11  8:17 ` Laszlo Ersek [this message]
2015-06-12  7:00 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2015-06-12 20:10   ` Kevin O'Connor
2015-06-15 13:01     ` Gerd Hoffmann
2015-06-15 14:36       ` Kevin O'Connor
2015-06-16  8:10         ` Gerd Hoffmann
2015-06-17  7:03 ` [Qemu-devel] " Gerd Hoffmann

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=55794436.6080803@redhat.com \
    --to=lersek@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).