On Sat, 2013-12-07 at 14:38 -0800, ron minnich wrote:
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. :-)
Some things have to be binary blobs. Because the world will apparently end if we tell someone how to initialise a memory controller.
But the *infrastructure* that ties those binary blobs together, that knows how to invoke the individual PEI modules, doesn't have to be binary too.
That part could reasonably be done in source code (hell, most of it already exists in EDKII), and could give FSP users a lot more flexibility and debugability.
It would also help to combat the trend of including stuff in the FSP that *doesn't* belong there because we *can* have open code that does it (such as graphics setup).