Zoltan Baldaszti has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/45482 )
Change subject: payloads/external: add support for BOOTBOOT payload ......................................................................
Patch Set 4:
(1 comment)
https://review.coreboot.org/c/coreboot/+/45482/2//COMMIT_MSG Commit Message:
https://review.coreboot.org/c/coreboot/+/45482/2//COMMIT_MSG@8 PS2, Line 8:
You could add some more less obvious information. For instance, I was […]
Ok, I've added more description to the commit message. But to answer your question adequately (which would be too long for a commit message I think), the place where initrd can be loaded from mostly depends on libpayload's configuration. - can be in ROM as a Flashmap partition (this is the default) - if libpayload has cbfs support, then can be in ROM as a cbfs file - if libpayload has serial port support, can be loaded over serial - if libpayload has storage or USB disk support, can be on disk For that latter, initrd can be on a GPT partition, or can be a file on ESP (for that the implementation has a GPT and a FAT16/32 parser). As for the initrd, statically linked executable, tar, cpio and some other formats supported, with optional gzip compression (and if libpayload compiled with LZMA or LZ4, then those too). If the format of initrd is not recognized, then it is scanned for the first executable compiled for the architecture (therefore it can load kernels from unknown image formats as well, provided the kernel is contiguous in them).