[U-Boot] [RFC] x86: Intel FSP integration

[Bin Meng]

Hi Simon,

I am preparing patches for my U-Boot port on Intel Crown Bay CRB which uses
Intel FSP for the memory and chipset initialization. Intel FSP is a binary
blob inside which 3 pre-defined entry pointes are available for 3rd party
bootloader to call to perform various jobs at different initialization stage.
With the help of FSP, U-Boot can boot directly from the x86 reset vector
without knowing any secrect Intel wants to hide in their chipset. Before I
post them, I would like to hear your thoughts about whether it is OK to get
such stuff into the U-Boot mainline.

My patches integrate the FSP binary blob into the U-Boot ROM image directly
and update the U-Boot to call these 3 routines at proper timing. There are
other supported codes like parsing FSP image header and HOB (hand over blob,
a UEFI concept) in the FSP package that can be integrated as well. Per the
license header from the FSP package released by Intel, it looks to me that
the FSP binary as well as the utility source codes can be redistributed
as is, however I would like post it here to hear your comments.

Additional information can be found at http://www.intel.com/fsp.

Here is the license extracted from the FSP package.

/** @file

Copyright (C) 2013, Intel Corporation

Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this
  list of conditions and the following disclaimer in the documentation and/or
  other materials provided with the distribution.
* Neither the name of Intel Corporation nor the names of its contributors may
  be used to endorse or promote products derived from this software without
  specific prior written permission.

  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
  AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
  LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
  CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
  SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
  INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
  CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
  THE POSSIBILITY OF SUCH DAMAGE.

**/

Regards,
Bin