From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sun, 27 Dec 2015 14:48:21 -0500 Subject: [U-Boot] [PATCH 0/9] EFI payload / application support In-Reply-To: <20151227183916.GH25034@bivouac.eciton.net> References: <1450792676-109541-1-git-send-email-agraf@suse.de> <20151226153103.GW25034@bivouac.eciton.net> <20151227181039.GJ4093@bill-the-cat> <20151227183916.GH25034@bivouac.eciton.net> Message-ID: <20151227194821.GL4093@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sun, Dec 27, 2015 at 06:39:16PM +0000, Leif Lindholm wrote: > On Sun, Dec 27, 2015 at 01:10:39PM -0500, Tom Rini wrote: > > So, my only "big" concern here is, are we as a community able to view > > and implement the relevant parts of the UEFI spec (without having to > > agree to a potentially complicated enough license to have to bug a > > lawyer)? It's been a while since I tried to view a copy so I'm hoping > > the answer is now yes. Thanks! > > So: > 1) You can certainly read the specification without agreeing to > anything (click-through is now gone - docs accessible straight from > http://uefi.org/specifications/). Thats good. > 2) The potential complication would be with regards to implementing > and distributing - which requires signing the Adopters Agreement: > http://uefi.org/sites/default/files/resources/UEFI_Adopters_Agreement_100907.pdf > > I actually think the implications of 2) for a project like U-Boot > would be a useful thing to bring up for discussion on the FW/OS forum > mailing list at http://uefi.org/FWOSForum. OK, I'll bring it up over there, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: