ron minnich has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/33142 )
Change subject: Kconfig: Create coreboot separate stage kconfigs ......................................................................
Patch Set 2:
Just to clarify, I'm not saying you should build a ramstage and include it in CBFS. You should have ifeqs in the Makefile to exclude the ramstage ELF from the dependencies and the files included in CBFS. I'm just saying you should use CONFIG_RAMPAYLOAD to control that, not the toolchain options. Having the toolchain defined doesn't mean you actually need to build anything (and thanks to Makefile dependencies you shouldn't need to touch all the details about how the ramstage is built, just make the final image not depend on it).
Hi Julius, building on your careful comments here, are you ok with the goal that we can, on a per stage basis, pick what to build and include in the ROM? I just had a requirement drop in my lap that's kind of interesting: the need to build a coreboot.rom with ONLY a ramstage and a payload, to be passed to kexec. This is the converse of RAMPAYLOAD.
I realize this "pick you stages" model is a very new request for coreboot, but it's not a new requirement, it's been on my plate since the first riscv port 5 years ago. I just can't figure out the right way to do it.
Can you advise on a good way to get where we're trying to go, if this CL is not the way? I can see the point of the reviewers, I'm just not sure what to do. It would be nice to get this right.
Thanks.