aboutsummaryrefslogtreecommitdiff
path: root/doc/arch/x86/x86.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/arch/x86/x86.rst')
-rw-r--r--doc/arch/x86/x86.rst17
1 files changed, 10 insertions, 7 deletions
diff --git a/doc/arch/x86/x86.rst b/doc/arch/x86/x86.rst
index 8781c16e2a1..87401008617 100644
--- a/doc/arch/x86/x86.rst
+++ b/doc/arch/x86/x86.rst
@@ -11,9 +11,9 @@ including supported boards, build instructions, todo list, etc.
Status
------
U-Boot supports running as a `coreboot`_ payload on x86. So far only Link
-(Chromebook Pixel) and `QEMU`_ x86 targets have been tested, but it should
-work with minimal adjustments on other x86 boards since coreboot deals with
-most of the low-level details.
+(Chromebook Pixel), Brya (Alder Lake Chromebook) and `QEMU`_ x86 targets have
+been tested, but it should work with minimal adjustments on other x86 boards
+since coreboot deals with most of the low-level details.
U-Boot is a main bootloader on Intel Edison board.
@@ -32,12 +32,14 @@ are supported:
- Link (Ivy Bridge - Chromebook Pixel)
- Minnowboard MAX
- Samus (Broadwell - Chromebook Pixel 2015)
+ - Coral (Apollo Lake Chromebooks circa 2017)
- QEMU x86 (32-bit & 64-bit)
As for loading an OS, U-Boot supports directly booting a 32-bit or 64-bit
Linux kernel as part of a FIT image. It also supports a compressed zImage.
U-Boot supports loading an x86 VxWorks kernel. Please check README.vxworks
-for more details.
+for more details. Finally, U-Boot can boot Linux distributions with a UEFI
+interface.
Build Instructions for U-Boot as BIOS replacement (bare mode)
-------------------------------------------------------------
@@ -701,9 +703,10 @@ for details of EFI support in U-Boot.
Chain-loading
-------------
-U-Boot can be chain-loaded from another bootloader, such as coreboot or
-Slim Bootloader. Typically this is done by building for targets 'coreboot' or
-'slimbootloader'.
+U-Boot can be chain-loaded from another bootloader, such as
+:doc:`../../board/coreboot/index` coreboot or
+:doc:`../../board/intel/slimbootloader`. Typically this is done by building for
+targets 'coreboot' or 'slimbootloader'.
For example, at present we have a 'coreboot' target but this runs very
different code from the bare-metal targets, such as coral. There is very little