summaryrefslogtreecommitdiff
path: root/src/cpu/intel
diff options
context:
space:
mode:
authorAlexandru Gagniuc <mr.nuke.me@gmail.com>2015-10-02 10:59:13 -0700
committerAlexandru Gagniuc <mr.nuke.me@gmail.com>2015-10-07 03:08:58 +0000
commit72bb66eb9cecf94b66a4aca3586165d5495fcfdb (patch)
tree181f29ae1450f1a3596c4ba70c40688e35671137 /src/cpu/intel
parent3f4a997529dfedaa4eefd00dc7d5ab32aa8e7b77 (diff)
downloadcoreboot-72bb66eb9cecf94b66a4aca3586165d5495fcfdb.tar.xz
x86/bootblock: Use LDFLAGS_bootblock to enable garbage collection
The x86 bootblock linking is a mess. The bootblock is treated in a very special manner, and never received the update to link-time garbage collection. On newer x86 platforms, the boot media is no longer memory-mapped. That means we need to do a lot more setup in the bootblock. ROMCC is unsuitable for this task, and walkcbfs only works on memory-mapped CBFS. We need to revise the x86 bootflow for this new case. The approach this patch series takes is to perform CAR setup in the bootblock, and load the following stage (either romstage or verstage) from the boot media. This approach is not new, but has been done on our ARM ports for years. Since we will be adding .c files to the bootblock, it is prudent to use link-time garbage collection. This is also consistent to how we do things on other architectures. Unification FTW! Change-Id: I16b78456df56e0053984a9aca9367e2542adfdc9 Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Reviewed-on: http://review.coreboot.org/11781 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/cpu/intel')
-rw-r--r--src/cpu/intel/fit/fit.ld2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cpu/intel/fit/fit.ld b/src/cpu/intel/fit/fit.ld
index 9ccfe82c5f..5817e1ded2 100644
--- a/src/cpu/intel/fit/fit.ld
+++ b/src/cpu/intel/fit/fit.ld
@@ -1,6 +1,6 @@
SECTIONS {
. = 0xffffffc0;
.fit_pointer (.): {
- *(.fit_pointer)
+ KEEP(*(.fit_pointer))
}
}