src/vboot: Capitalize RAM and CPU
Change-Id: Iff6b1b08b8159588b964d9637b16e1e0bfcca940 Signed-off-by: Elyes HAOUAS <ehaouas@noos.fr> Reviewed-on: https://review.coreboot.org/15986 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Martin Roth <martinroth@google.com>
This commit is contained in:
parent
91e0e3ccbe
commit
2a600263dc
|
@ -91,7 +91,7 @@ config RETURN_FROM_VERSTAGE
|
|||
help
|
||||
If this is set, the verstage returns back to the calling stage instead
|
||||
of exiting to the succeeding stage so that the verstage space can be
|
||||
reused by the succeeding stage. This is useful if a ram space is too
|
||||
reused by the succeeding stage. This is useful if a RAM space is too
|
||||
small to fit both the verstage and the succeeding stage.
|
||||
|
||||
config CHIPSET_PROVIDES_VERSTAGE_MAIN_SYMBOL
|
||||
|
@ -108,7 +108,7 @@ config VBOOT_DYNAMIC_WORK_BUFFER
|
|||
depends on VBOOT
|
||||
help
|
||||
This option is used when there isn't enough pre-main memory
|
||||
ram to allocate the vboot work buffer. That means vboot verification
|
||||
RAM to allocate the vboot work buffer. That means vboot verification
|
||||
is after memory init and requires main memory to back the work
|
||||
buffer.
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@ struct selected_region {
|
|||
/*
|
||||
* this is placed at the start of the vboot work buffer. selected_region is used
|
||||
* for the verstage to return the location of the selected slot. buffer is used
|
||||
* by the vboot2 core. Keep the struct cpu architecture agnostic as it crosses
|
||||
* by the vboot2 core. Keep the struct CPU architecture agnostic as it crosses
|
||||
* stage boundaries.
|
||||
*/
|
||||
struct vb2_working_data {
|
||||
|
|
Loading…
Reference in New Issue