Hi Andy,
On Mon, Jul 15, 2019 at 5:31 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
On Mon, Jul 15, 2019 at 12:58 AM Park, Aiden aiden.park@intel.com wrote:
This patch is to enable U-Boot as a payload which runs on top of Slim Bootloader(https://github.com/slimbootloader/slimbootloader) boot firmware for x86 platforms.
The Slim Bootloader is designed with multi-stage architecture for the execution from reset vector to OS hand-off, and supports qemu, Apollolake, Whiskeylake and Coffeelake platforms consuming Intel FSP(https://github.com/IntelFsp/FSP) for silicon initialization including CAR and memory initialization. As multi-stage architecture, the Slim Bootloader adopts payload concept which is responsible for OS load from media devices and boot OS and it supports 32-bit PE32, EFI FV, ELF and RAW format payloads. The Slim Bootloader generate HOB(Hand Off Block) list pointer, which has debug serial port info, memory map info, performance data info and etc., and passes it to a payload. U-Boot configures serial port, dram, pci, tsc and others with the information from the HOB.
The compiled U-Boot supports usb, sata and sd/mmc boot which have been verified on qemu and other supported platforms.
Thanks for the series. I have some questions.
Is it chained bootloader in the sense of how it's done? Can it use rather SPL part of U-Boot? Can it simple run Linux kernel as an EFI payload?
Very briefly looking I didn't notice (may be simple missed it) the use of X86_32BIT_INIT. Why do you not use it (it it's the case)?
Bin, may you give me couple of days to briefly review this in order to see if there is any similarities with what Intel Edison firmware is doing?
Yes, for sure.
P.S. Aiden, please, Cc me for the next series.
Regards, Bin