summaryrefslogtreecommitdiff
path: root/util/romcc/results/linux_test5.out
diff options
context:
space:
mode:
authorPatrick Georgi <patrick.georgi@coresystems.de>2009-04-03 12:52:43 +0000
committerPatrick Georgi <patrick.georgi@coresystems.de>2009-04-03 12:52:43 +0000
commitaed1f925a65a231ed008902f1946b3680227f098 (patch)
tree26f108d9094c9f31ad41ba507d9740b8e23df881 /util/romcc/results/linux_test5.out
parent73ad3264525c7d076ef2aafab63841685bf53679 (diff)
the attached patch is the last infrastructure change necessary for
romfs. Everything else to make a target romfs aware happens in the targets. What the patch does: 1. missing romfs.h include 2. special handling while creating coreboot.rom While the romfs code path in the makefile doesn't actually use the file, it's possible that the build of coreboot.rom fails in a romfs setup, because the individual buildrom image is too small to host both coreboot and payloads (as the payloads aren't supposed to be there). Thus, a special case to replace the payload with /dev/null in case of a romfs build. There would be cleaner ways, but they're not easily encoded in the Config.lb format. 3. config.g is changed to create rules for a romfs build Targets should still build (they do for me) Signed-off-by: Patrick Georgi <patrick.georgi@coresystems.de> Acked-by: Stefan Reinauer <stepan@coresystems.de> git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4049 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'util/romcc/results/linux_test5.out')
0 files changed, 0 insertions, 0 deletions