On 12/06/2013 10:47 AM, ron minnich wrote:
Here are my thoughts on FSP.
FSP is how we deal with a bad situation: the fact that Intel chipsets are no longer open (the way they were until 2000 or so) and require a binary blob from Intel to get them working.
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.
Alex
On Sat, Dec 7, 2013 at 2:34 PM, mrnuke mr.nuke.me@gmail.com wrote:
On 12/06/2013 10:47 AM, ron minnich wrote:
Here are my thoughts on FSP.
FSP is how we deal with a bad situation: the fact that Intel chipsets are no longer open (the way they were until 2000 or so) and require a binary blob from Intel to get them working.
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. :-)
ron
-
mrnuke -
ron minnich