Aaron Durbin 83bc0db777 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>		2015-09-09 19:36:08 +00:00
..
arm	linking: add and use LDFLAGS_common	2015-09-09 19:35:54 +00:00
arm64	linking: add and use LDFLAGS_common	2015-09-09 19:35:54 +00:00
mips	linking: add and use LDFLAGS_common	2015-09-09 19:35:54 +00:00
riscv	linking: add and use LDFLAGS_common	2015-09-09 19:35:54 +00:00
x86	x86: link ramstage the same way regardless of RELOCATABLE_RAMSTAGE	2015-09-09 19:36:08 +00:00