On 26.07.2012, at 16:44, Loïc Minier loic.minier@linaro.org wrote:
On Thu, Jul 26, 2012, Alexander Graf wrote:
It might however be an interesting idea to have a similar split to coreboot / tianocore in the u-boot world. U-boot could still be the bit implementing the initial initialization and maybe even device i/o drivers, while a uefi capable payload could then implement all the uefi layering on top. Then we could either load Linux directly from u-boot like we do today, or bootstrap outselves into a uefi implementation that would allow for generic booting across the board.
Exactly; my point about an UEFI boot cmd in U-Boot was to try to store this UEFI-implementing payload in an UEFI-compatible place itself as much as possible, and then have U-Boot discover it.
It's a bit chicken-and-egg though :-)
It depends. In the cordboot world, the payload (UEFI in this case) gets glued onto the firmware itself. That makes discovery trivial ;)
Alex