summaryrefslogtreecommitdiff
path: root/payloads/libpayload
diff options
context:
space:
mode:
authorAlexandru Gagniuc <mr.nuke.me@gmail.com>2016-01-26 18:22:43 -0800
committerStefan Reinauer <stefan.reinauer@coreboot.org>2016-01-30 03:11:46 +0100
commit6be6c8f2820db761c09ee4bd2cb4e3fd76285207 (patch)
tree62481c112048742d71a1894d4c6af5723df34f36 /payloads/libpayload
parentf8e491339f685bc43a0b8812f9f00a2918ce7611 (diff)
downloadcoreboot-6be6c8f2820db761c09ee4bd2cb4e3fd76285207.tar.xz
arch/x86: Implement minimal bootblock for C_ENVIRONMENT_BOTOBLOCK
Some newer x86 systems can boot from non-memory-mapped boot media (e.g. EMMC). The bootblock may be backed by small amounts of SRAM, or other memory, similar to how most ARM chipsets work. In such cases, we may not have enough code space for romstage very early on. This means that CAR setup and early boot media (e.g. SPI, EMMC) drivers need to be implemented within the limited amount memory of storage available. Since the reset vector has to be contained in this early code memory, the bootblock is the best place to implement loading of other stages. Implement a bootblock which does the minimal initialization, up to, and including switch to protected mode. This then transfers control to platform-specific code. No stack is needed, and control is transferred via a "jmp" such that no stack operations are involved. Change-Id: I009b42b9a707cf11a74493bd4d8c189dc09b8ace Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Reviewed-on: https://review.coreboot.org/13485 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'payloads/libpayload')
0 files changed, 0 insertions, 0 deletions