On Mon, Jun 3, 2013 at 4:12 PM, Anthony Liguori <anth...@codemonkey.ws> wrote: > Jordan Justen <jljus...@gmail.com> writes: >> I mentioned in the other thread that perhaps QEMU could also consider >> making the ACPI code available under some 'appropriate' license, which >> would allow firmware writers to leverage the code directly if desired. >> Perhaps a dual/multi license situation for the relevant files? > > Would the OVMF developers participate in a GPL version of OVMF that live > outside of the EDK2 tree? > > I think the only solution to the licensing problem is a GPL-friendly > UEFI build...
Sounds like there is no chance for a multi-license scenario then? My idea here was that QEMU could consider what potential licensing situations alternative firmware writers might desire, and attempt to multi-license the code so it could be used as reference code for those potential consumers. I guess if that is not possible and the fw-cfg method doesn't work out, then we'll probably need to keep doing our best in re-implementing the ASL/ACPI code. OVMF is an important part of the EDK II project, and thus a viable OVMF within the EDK II tree is important. Therefore, we need BSD licensed code for the core pieces of OVMF. (Such as producing ACPI tables.) You mentioned that FatBinPkg in the EDK II tree is a particular issue for some OVMF derivatives. To solve that (as I mentioned in the other thread) I'd be willing to publish a git-submodule version of OVMF. This would also allow OVMF derived projects to include other packages. (Potentially with different source licenses.) Given that there are no FAT driver alternatives, the only purpose I could see for this anytime soon would be something that incorporates the seabios-csm. -Jordan
