Whitebox
/
u-boot
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

rockchip: doc: clarify usage of CONFIG_SPL_ROCKCHIP_BACK_TO_BROM

Browse Source 
Change the description relating to CONFIG_SPL_ROCKCHIP_BACK_TO_BROM to
clarify that both RK3288 and RK3036 use

	CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Acked-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
lime2-spi
Heinrich Schuchardt 6 years ago committed by Philipp Tomsich
parent 19ee1fae09
commit 760b95789e
1 changed files with 4 additions and 4 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 8
      doc/README.rockchip

8
doc/README.rockchip
Unescape View File

@ -124,11 +124,11 @@ something like:
=> =>
The rockchip bootrom can load and boot an initial spl, then continue to The rockchip bootrom can load and boot an initial spl, then continue to
load a second-level bootloader(ie. U-BOOT) as soon as it returns to bootrom. load a second-stage bootloader (ie. U-Boot) as soon as the control is returned
Therefore RK3288 has another loading sequence like RK3036. The option of to the bootrom. Both the RK3288 and the RK3036 use this special boot sequence.
U-Boot is controlled with this setting in U-Boot: The configuration option enabling this is:
#define CONFIG_SPL_ROCKCHIP_BACK_TO_BROM CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
You can create the image via the following operations: You can create the image via the following operations:

Write Preview
Loading…
Cancel
Save