qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Justen <jljusten@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>,
	Kevin O'Connor <kevin@koconnor.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support
Date: Mon, 10 Jun 2013 17:28:30 -0700	[thread overview]
Message-ID: <CAFe8ug-HU7Xf=GyoSmY+LSYsoFZ1GCG3+UQt0eB-KPLMQg4z1A@mail.gmail.com> (raw)
In-Reply-To: <87mwqxzlke.fsf@codemonkey.ws>

On Mon, Jun 10, 2013 at 2:45 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> OVMF is proprietary.

I don't agree that not-OSI means proprietary.

I agree that the FAT driver is not 'free software' and I agree that is
a problem for usage with free software projects, such as QEMU. This is
a big deal, but unfortunately, as an Intel employee, I think I've done
as much as I can to address this.

It couldn't hurt if more people that actually care about this spoke up
on edk2-devel about the issue, or perhaps within a UEFI working group.
Because, I know that they've stopped listening to me about it.

> It is not "supported" by QEMU.

No, but I've always thought that QEMU was happy to have alternative
firmware projects.

> I'm not really convinced that
> QEMU<->firmware is a GPL boundary because of how tightly the two are
> linked.

Where has 'linked' in terms of the GPL ever been anything other than
actual executable linking?

> Moving large chunks of firmware code into QEMU just to avoid solving
> licensing issues is a non-starter with me.

Is this a licensing issue? I thought this was a "let's save time by
doing it in one place" thing. I'm pretty ambivalent about this
feature, really. I don't think it is even worth all this bickering.

I'm certain OVMF has ACPI issues on QEMU, but I don't think it is a
huge deal to resolve them independently of this feature.

I was not a huge fan of supporting this type of thing for Xen in OVMF,
but it does seem to work fine.

-Jordan

  parent reply	other threads:[~2013-06-11  0:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 16:41 [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support Michael S. Tsirkin
2013-06-10 18:58 ` Anthony Liguori
2013-06-10 19:17   ` Peter Maydell
2013-06-10 19:50     ` Anthony Liguori
2013-06-10 19:43   ` Laszlo Ersek
2013-06-10 19:57     ` Anthony Liguori
2013-06-10 20:43       ` Laszlo Ersek
2013-06-10 21:14         ` Laszlo Ersek
2013-06-10 21:45         ` Anthony Liguori
2013-06-10 23:05           ` Kevin O'Connor
2013-06-10 23:34             ` Anthony Liguori
2013-06-10 23:52               ` David Woodhouse
2013-06-11  0:11                 ` Anthony Liguori
2013-06-11 14:11                   ` David Woodhouse
2013-06-11  0:23               ` Kevin O'Connor
2013-06-11  0:51                 ` Anthony Liguori
2013-06-11  1:19                   ` Kevin O'Connor
2013-06-11  1:25                     ` Anthony Liguori
2013-06-11  1:49                       ` Kevin O'Connor
2013-06-11  6:49                       ` Michael S. Tsirkin
2013-06-11  0:28           ` Jordan Justen [this message]
2013-06-11  1:03             ` Anthony Liguori
2013-06-11  1:32               ` Jordan Justen
2013-06-11  7:35               ` Michael S. Tsirkin
2013-06-13 23:05                 ` Paolo Bonzini
2013-06-14  0:59                   ` Anthony Liguori
2013-06-14  1:23                     ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2013-06-11 14:04               ` David Woodhouse
2013-06-13 23:02               ` [Qemu-devel] " Paolo Bonzini
2013-06-14  0:26                 ` Laszlo Ersek
2013-06-16 10:00                   ` Laszlo Ersek
2013-06-11  5:22   ` Michael S. Tsirkin
2013-06-11  5:33 ` Gerd Hoffmann
2013-06-11  6:55   ` Michael S. Tsirkin
2013-06-11  7:42     ` Gerd Hoffmann
2013-06-11  7:53       ` Michael S. Tsirkin
2013-06-11  8:00         ` Gerd Hoffmann
2013-06-11  8:18           ` Michael S. Tsirkin
2013-06-11  8:27             ` Michael S. Tsirkin

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='CAFe8ug-HU7Xf=GyoSmY+LSYsoFZ1GCG3+UQt0eB-KPLMQg4z1A@mail.gmail.com' \
    --to=jljusten@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=dwmw2@infradead.org \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).