I was told that to build an UEFI payload need to get two components from different sites,
sounds I got some information out-of-date. I will try getting the corebootPkg and then
build a payload myself.
Understood your point that entire coreboot code must contain source code only. I will
share this with inside our team.
From: Patrick Georgi [mailto:firstname.lastname@example.org]
Sent: Wednesday, February 04, 2015 6:22 AM
To: Yang, York
Subject: Re: [coreboot] Can I upstream an UEFI payload binary for MinnowMax board
Am 2015-02-04 01:18, schrieb Yang, York:
Can I upstream an UEFI payload binary for MinnowMax
No. We don't ship payload binaries, and there's no reason to start doing
coreboot is an Open Source project.
The reason is we want to reduce the effort that
coreboot user spends to
UEFI payload contains two component, 1) is EDK2
, and 2) coreboot library and package in
. User need to download them separately, and
put them together, and build it.
I like to think that the corebootPkg sources are rather easy to obtain:
$ git clone https://github.com/pgeorgi/edk2
So the reason that your UEFI payload's sources are harder to assemble
must be a problem within that project and its processes, not something
that's fundamental to Tianocore based payloads.
For example, I can't imagine a single good reason why that firmware site
ships Open Source code in an encrypted zip file.
It could be improved in the future, but for now it
Then take the time. What incentive is left to improve things in the
future if users can simply be diverted to those binaries?