From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49352) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1djlLl-0007vh-3W for qemu-devel@nongnu.org; Mon, 21 Aug 2017 07:58:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1djlLh-0007Vk-1W for qemu-devel@nongnu.org; Mon, 21 Aug 2017 07:58:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42536) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1djlLg-0007VN-RQ for qemu-devel@nongnu.org; Mon, 21 Aug 2017 07:58:28 -0400 Message-ID: <1503316706.26016.11.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 21 Aug 2017 13:58:26 +0200 In-Reply-To: References: <20170807163121.797e7ad6@nial.brq.redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] AVMF & OVMF blobs in QEMU tree??? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek , Peter Maydell , Igor Mammedov Cc: QEMU Developers , Alex =?ISO-8859-1?Q?Benn=E9e?= On Mon, 2017-08-07 at 18:51 +0200, Laszlo Ersek wrote: > On 08/07/17 16:40, Peter Maydell wrote: > > On 7 August 2017 at 15:31, Igor Mammedov > > 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.) > > I agree that OVMF and ArmVirtQemu firmware binaries (and matching > varstore templates, likely compressed) should be bundled with QEMU. > There are no license-related reasons left that would prevent this. > > Please let us discuss this when Gerd returns from vacation. (CC'ing > Gerd.) slighly oldish wip branch: https://www.kraxel.org/cgit/qemu/log/?h=work/edk2 Related question (as the edk2 blobs are pretty big): Do we want commit this to the qemu repo directly? Or should we create a qemu-firmware repo for the precompiled blobs and hook it up as submodule? cheers, Gerd