diff options
author | Felix Held <felix.held@amd.corp-partner.google.com> | 2020-04-04 02:37:04 +0200 |
---|---|---|
committer | Aaron Durbin <adurbin@chromium.org> | 2020-04-29 05:38:08 +0000 |
commit | 466732262817aadb1d9464883912112fd5d03fba (patch) | |
tree | bda037f6df0ef07d400e71df516ef0b34de4a873 /util/chromeos/extract_blobs.sh | |
parent | ca928c6768ba143f619a99cca44f9f8153511270 (diff) |
soc/amd/picasso: Add bootblock support
The original plan for Picasso was to combine the features of bootblock
with romstage due to its unique way of coming out of reset. Early in
development, all bootblock support was removed from the directory.
All Picasso designs will now use a bootblock as their first stage. The
reason being that it requires less invasive changes than using a hybrid
romstage.
Add a basic bootblock back to the directory, and compatible with the
design of lib/bootblock.c. The files support RESET_VECTOR_IN_RAM
and add appropriate settings in Kconfig. Make Makefile.inc calculates
the size and base of bootblock from known parameters.
* Future work may attempt to streamline this further, in conjunction
with changes in amdfwtool. See b/154957411.
BUG=b:147042464, b:153675909
Change-Id: I1d0784025f2b39f140b16f37726d4a7f36df6c6c
Signed-off-by: Marshall Dawson <marshalldawson3rd@gmail.com>
Signed-off-by: Felix Held <felix-coreboot@felixheld.de>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/37490
Reviewed-by: Furquan Shaikh <furquan@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'util/chromeos/extract_blobs.sh')
0 files changed, 0 insertions, 0 deletions