diff options
| author | Aaron Durbin <adurbin@chromium.org> | 2015-09-06 10:45:18 -0500 |
|---|---|---|
| committer | Aaron Durbin <adurbin@chromium.org> | 2015-09-09 19:36:08 +0000 |
| commit | 83bc0db777ef4906b0e0d2b588bfb14e1b82c84e (patch) | |
| tree | 3bee4a5d1a725a29774680fbc40d289665f6deaa /util | |
| parent | c9b053d07d1edbd2b0016d19cb6730597ee0a21e (diff) | |
| download | coreboot-83bc0db777ef4906b0e0d2b588bfb14e1b82c84e.tar.xz | |
x86: link ramstage the same way regardless of RELOCATABLE_RAMSTAGE
Previously there were 2 paths in linking ramstage. One was used for
RELOCATABLE_RAMSTAGE while the other was fixed location. Now that
rmodtool can handle multiple secitons for a single proram segment
there's no need for linking ramstage using lib/rmodule.ld. That
also means true rmodules don't have symbols required for ramstage
purposes so fix memlayout.h. Lastly add default rules for creating
rmod files from the known file names and locations.
BUG=chrome-os-partner:44827
BRANCH=None
TEST=Built rambi. Inspected ramstage.debug as well as rmodules
created during the build.
Change-Id: I98d249036c27cb4847512ab8bca5ea7b02ce04bd
Signed-off-by: Aaron Durbin <adubin@chromium.org>
Reviewed-on: http://review.coreboot.org/11524
Tested-by: build bot (Jenkins)
Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions