summaryrefslogtreecommitdiff
path: root/src/ec/lenovo
diff options
context:
space:
mode:
authorRonald G. Minnich <rminnich@gmail.com>2012-07-02 09:46:42 -0700
committerPatrick Georgi <patrick@georgi-clan.de>2012-07-03 09:43:38 +0200
commit9b4c92ad80d691e9e2a4e5a84ad035fbe8e8d977 (patch)
tree687f28876f704aff9791ef7a6214659abb8882c9 /src/ec/lenovo
parent2c08f6ade4ac904e9eb762c71f95daa372be0072 (diff)
Fix the error message for romstage when .bss or .data are non-zero
The error message from romstage is annoying and misleading: "Do not use global variables in romstage" Because it can occur even when global variables are not used in some circumstances, but also because it gives you only a rough idea where to look. This change sucks but sucks less. We still don't know which file the problem is in but at least we know if it is data or bss. Replace the error message with something that provides more information and less guessing on the part of the script: ".bss is non-zero size in romstage which is not allowed -- global variable?" or ".data is non-zero size in romstage which is not allowed -- global variable?" To test: build coreboot as normal. It builds. Add char d[32]; to romstage.c and get the first error message; add int x = 32; to romstage.c and get the second. Change-Id: I300ec05bdb4b30d7ef3f5112e6cc09b1fafe8263 Signed-off-by: Ronald G. Minnich <rminnich@gmail.com> Reviewed-on: http://review.coreboot.org/1160 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <patrick@georgi-clan.de>
Diffstat (limited to 'src/ec/lenovo')
0 files changed, 0 insertions, 0 deletions