Actually we also work on a solution to build an UEFI payload easier (open source too), but
it takes time to complete. Hence we are looking for a short team solution, and the binary
upstreaming is just an idea to ask whether community is allowing such work. Never mind,
we will keep evaluating another solution and make it happen as soon as possible. Github
is a very good suggestion.
Thank you very much Patrick.
From: Patrick Georgi [mailto:email@example.com]
Sent: Wednesday, February 04, 2015 11:55 AM
To: Yang, York
Subject: RE: [coreboot] Can I upstream an UEFI payload binary for MinnowMax board
Am 2015-02-04 19:27, schrieb Yang, York:
I was told that to build an UEFI payload need to get
from different sites, sounds I got some information out-of-date. I
will try getting the corebootPkg and then build a payload myself.
corebootPkg is very likely a different project from yours. There are several
attempts to make Tianocore into a payload.
The thing is, if you want to make it easier on MinnowMax users, you (or anyone else) could
open an account on github, fork the Tianocore repository there
and integrate the stuff from firmware.intel.com/develop
After that, users of that payload version can just pull the entire code with a single git
clone, too. And participate in the development through github's pull request feature
and issue tracker.
(Of course, if you want to do this, all this may require some sign-off by your team)
But since that's possible (and really easy, too), there's no need to burden
with more binaries.
Understood your point that entire coreboot code must
code only. I will share this with inside our team.
We compromise here and there, but that's not some thing we want to encourage -
it is really just a compromise, and it's risky to try to push its boundaries.