diff options
| author | Simon Glass <sjg@chromium.org> | 2017-01-16 07:03:44 -0700 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2017-02-06 11:38:46 +0800 |
| commit | 13f1dc64fd09d2894d13ca0db08ddd168bc12387 (patch) | |
| tree | f249ea504d30810dd92b8316ee76f77477bffe56 /Makefile | |
| parent | a66ad67ff26a2c4940aa7b6ddba40cf202edf108 (diff) | |
| download | u-boot-13f1dc64fd09d2894d13ca0db08ddd168bc12387.zip u-boot-13f1dc64fd09d2894d13ca0db08ddd168bc12387.tar.gz u-boot-13f1dc64fd09d2894d13ca0db08ddd168bc12387.tar.bz2 | |
x86: Kconfig: Add location options for 16/32-bit init
At present all 16/32-bit init is controlled by CONFIG_X86_RESET_VECTOR. If
this is enabled, then U-Boot is the 'first' boot loader and handles execution
from the reset vector through to U-Boot's command prompt. If it is not
enabled then U-Boot starts at the 32-bit entry and skips most of its init,
assuming that the previous boot loader has done this already.
With the move to suport 64-bit operation, we have more cases to consider.
The 16-bit and 32-bit init may be in SPL rather than in U-Boot proper.
Add Kconfig options which control the location of the 16-bit and the 32-bit
init. These are not intended to be user-setting except for experimentation.
Their values should be determined by whether 64-bit U-Boot is used.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions