All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Igor Mammedov <imammedo@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Laszlo Ersek" <lersek@redhat.com>
Subject: Re: [Qemu-devel] AVMF & OVMF blobs in QEMU tree???
Date: Mon, 7 Aug 2017 15:40:47 +0100	[thread overview]
Message-ID: <CAFEAcA8=+8cPjKayq3Bre7y9=6jzFgjCCjRkNUeHxArJu9Ue6A@mail.gmail.com> (raw)
In-Reply-To: <20170807163121.797e7ad6@nial.brq.redhat.com>

On 7 August 2017 at 15:31, Igor Mammedov <imammedo@redhat.com> wrote:
> 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?

I suspect the primary answer is "nobody who's willing to
maintain, test and update the resulting binary blobs has
stepped forward to say they want to do so" :-)

(I think that shipping them in the QEMU tree would be
nice but is principally a convenience for our direct
users, since distros are going to want to build their
own ROM blobs from source anyway.)

thanks
-- PMM

  reply	other threads:[~2017-08-07 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 14:31 [Qemu-devel] AVMF & OVMF blobs in QEMU tree??? Igor Mammedov
2017-08-07 14:40 ` Peter Maydell [this message]
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='CAFEAcA8=+8cPjKayq3Bre7y9=6jzFgjCCjRkNUeHxArJu9Ue6A@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=imammedo@redhat.com \
    --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 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.