7 Dec
2013
7 Dec
'13
11:59 p.m.
On 12/07/2013 04:38 PM, ron minnich wrote:
On Sat, Dec 7, 2013 at 2:34 PM, mrnuke mr.nuke.me@gmail.com wrote:
The best option is to have the FSP source under src/vendorcode/fsp. That's also the only way people can comment on, and help improve the API. This already happened with CIMX and AGESA.
FSP is a delivery vehicle for binary code. It is designed to be a binary blob with well-defined entry points.
So, what you're saying is "the best option for delivering the binary blob is to be delivered as not a binary blob."
At that point my head explodes as I try to parse the contradiction. :-)
The best option is to have the source of FSP's payload under src/vendorcode/fsp.
There, I fixed it for you. Can I have a cookie now?
Alex