From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Laszlo Ersek" <lersek@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] AVMF & OVMF blobs in QEMU tree???
Date: Mon, 7 Aug 2017 16:31:21 +0200 [thread overview]
Message-ID: <20170807163121.797e7ad6@nial.brq.redhat.com> (raw)
As I recall there were issues with FAT driver licensing in edk2,
but I've heard there were some changes in that regard.
Is there any other reasons why we are not putting subj.
in QEMU tree like we do with SeaBIOS and other roms?
PS:
Mostly I'm interested in having AVMF ROM in QEMU,
to make testing of ACPI tables (tests/bios-tables-test)
for virt-arm work (it has 0 coverage right now).
It would be useful to have OVMF blob as well so we could
notice if some OVMF related stuff is broken or changed
unexpectedly.
next reply other threads:[~2017-08-07 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 14:31 Igor Mammedov [this message]
2017-08-07 14:40 ` [Qemu-devel] AVMF & OVMF blobs in QEMU tree??? Peter Maydell
2017-08-07 16:51 ` Laszlo Ersek
2017-08-21 11:58 ` Gerd Hoffmann
2017-08-21 13:23 ` Igor Mammedov
2017-08-21 13:54 ` Peter Maydell
2017-08-24 10:55 ` Gerd Hoffmann
2017-08-24 13:49 ` Laszlo Ersek
2017-08-21 14:03 ` Alex Bennée
2017-08-21 16:07 ` Laszlo Ersek
2017-08-24 10:23 ` 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=20170807163121.797e7ad6@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=lersek@redhat.com \
--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).