UEFI License confusion

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
doberman
Posts: 1
Joined: Sat Jun 27, 2020 7:27 pm

UEFI License confusion

Post by doberman »

I'm interested in making my own, private implementation of UEFI headers, instead of using EDK. I have looked at uefi[dot]org and on download page for specification and in documentation itself stated that this document and herein content is read only, and I have no license (I assume also permission) to reproduce, implement or otherwise use for any purpose (other than to read only) the UEFI Specifications.

Do I misunderstood the statement and the specification is open for everyone to implement?


Actual quote:
By downloading any of the UEFI Specifications, you acknowledge that no license, express or implied, is granted to you to distribute, additionally reproduce, implement or otherwise use for any purpose (other than to read only) the UEFI Specifications, and that all rights, title and interest in and to the UEFI Specifications, including all intellectual property rights of any type whatsoever, are owned by the UEFI Forum, or subject to rights granted to the UEFI Forum.
Octocontrabass
Member
Member
Posts: 5575
Joined: Mon Mar 25, 2013 7:01 pm

Re: UEFI License confusion

Post by Octocontrabass »

A license to distribute, additionally reproduce, implement or otherwise use (other than to read only) the UEFI Specifications can be obtained by executing and returning the UEFI Adopter Membership Agreement (free membership).
It's open for anyone who signs the agreement.

(I suspect no one will care if you don't sign the agreement, as long as there's no money involved. Don't take this as legal advice, I'm not a lawyer.)
User avatar
zaval
Member
Member
Posts: 657
Joined: Fri Feb 17, 2017 4:01 pm
Location: Ukraine, Bachmut
Contact:

Re: UEFI License confusion

Post by zaval »

that license is about the specification itself. not the headers (no headers exist in the spec in fact). of course, you can make your own ones, in accordance with the specification's C structures and definitions. I did so. it's not a reproduction of the specification. and if you are going to implement UEFI, yes, it's open to everybody to implement without additional agreements or whatever things.
ANT - NT-like OS for x64 and arm64.
efify - UEFI for a couple of boards (mips and arm). suspended due to lost of all the target park boards (russians destroyed our town).
Post Reply