From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37431) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UmCRt-0002rH-4n for qemu-devel@nongnu.org; Mon, 10 Jun 2013 20:28:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UmCRs-0007H2-2M for qemu-devel@nongnu.org; Mon, 10 Jun 2013 20:28:33 -0400 Received: from mail-ie0-x233.google.com ([2607:f8b0:4001:c03::233]:34032) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UmCRr-0007Gv-TQ for qemu-devel@nongnu.org; Mon, 10 Jun 2013 20:28:31 -0400 Received: by mail-ie0-f179.google.com with SMTP id c10so9865462ieb.10 for ; Mon, 10 Jun 2013 17:28:31 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <87mwqxzlke.fsf@codemonkey.ws> References: <1370882347-31129-1-git-send-email-mst@redhat.com> <87r4g9rdwe.fsf@codemonkey.ws> <51B62C48.5060303@redhat.com> <87ehc920ym.fsf@codemonkey.ws> <51B63A74.1030905@redhat.com> <87mwqxzlke.fsf@codemonkey.ws> Date: Mon, 10 Jun 2013 17:28:30 -0700 Message-ID: From: Jordan Justen Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Peter Maydell , "Michael S. Tsirkin" , Laszlo Ersek , seabios@seabios.org, qemu-devel , Kevin O'Connor , Gerd Hoffmann , David Woodhouse On Mon, Jun 10, 2013 at 2:45 PM, Anthony Liguori 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