November 2023 - U-Boot

[PATCH v1 0/3] Implement support of simple PLL
by Svyatoslav Ryhel 16 Nov '23

16 Nov '23

Simple PLL clocks like PLLD2 were omitted since they do not share common 4 register structure with main clocks. Such clocks are contained in simple PLL group. Only clock_start_pll function supported them. This patch expands this support on clock_set_rate and clock_get_rate which should make simple PLL clocks equal to main PLL clocks. Implementation was tested on T30/T114 using PLLD2 simple PLL (PLLD2 can serve as a video subsystem main clock and this is how it was tested). Patches pass buildman ./tools/buildman/buildman tegra Building current source for 33 boards (12 threads, 1 job per thread) 33 0 0 /33 colibri_t30 Completed: 33 total built, 33 newly), duration 0:06:25, rate 0.09 Svyatoslav Ryhel (3): ARM: tegra: clock: support get and set rate for simple PLL ARM: tegra30: clock: implement PLLD2 support ARM: tegra114: clock: implement PLLD2 support arch/arm/include/asm/arch-tegra/clk_rst.h | 3 +- .../include/asm/arch-tegra114/clock-tables.h | 2 +- .../include/asm/arch-tegra30/clock-tables.h | 2 +- arch/arm/mach-tegra/clock.c | 78 ++++++++++++++----- arch/arm/mach-tegra/tegra114/clock.c | 22 ++++++ arch/arm/mach-tegra/tegra124/clock.c | 12 ++- arch/arm/mach-tegra/tegra20/clock.c | 15 ++++ arch/arm/mach-tegra/tegra210/clock.c | 15 ++++ arch/arm/mach-tegra/tegra30/clock.c | 22 ++++++ 9 files changed, 146 insertions(+), 25 deletions(-) -- 2.40.1

1 3

bug - bootflow: grub efi crashes when bootflow selected explicitly
by Shantur Rathore 16 Nov '23

16 Nov '23

Hi all, I am facing an issue with bootflow where grub efi crashes only when bootflow is selected manually. Board - RockPro64 OS - Armbian Bookworm CLI U-boot : 2024.01-rc2 Built and installed in SPI Boot Device = USB drive connected to USB 2.0 port Success scenario : => setenv boot_targets usb => setenv bootmeths efi => bootflow scan -lb Grub loads and Linux boots Full Log - https://pastebin.com/KUFtUcha Failure scenario Full Log : https://pastebin.com/GHyG2NDz > setenv boot_targets usb => setenv bootmeths efi => bootflow scan => bootflow list Showing all bootflows Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- 0 efi ready usb_mass_ 1 usb_mass_storage.lun0.boo efi/boot/bootaa64.efi --- ----------- ------ -------- ---- ------------------------ ---------------- (1 bootflow, 1 valid) => bootflow select 0 => bootflow boot ** Booting bootflow 'usb_mass_storage.lun0.bootdev.part_1' with efi Loading Linux 6.1.50-current-rockchip64 ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... "Synchronous Abort" handler, esr 0x96000044, far 0x300905a65 elr: 000000000022d634 lr : 0000000000208e14 (reloc) elr: 00000000f3f47634 lr : 00000000f3f22e14 x0 : 0000000300905a4d x1 : 0000000000000000 x2 : 0000000000000000 x3 : 000000000207fff0 x4 : 00000000f3fd6470 x5 : 000000000207fff0 x6 : 0000ffff00000004 x7 : 00000000f1f9fad0 x8 : 7f7f7f7f7f7f7f7f x9 : 000000000000d02c x10: 00000000f1efee8c x11: 000000000000d020 x12: 00000000f1efef88 x13: 00000000ad400000 x14: 00000000f1efef2c x15: 00000000f1eff057 x16: 00000000f3f21fc0 x17: 00000000d017a1d0 x18: 00000000f1f11d70 x19: 00000000f1f21eb0 x20: 0000000000000000 x21: 00000000f1f27b80 x22: 0000000000000000 x23: 0000000000000000 x24: 0000000000000000 x25: 00000000f3fc9ed7 x26: 00000000b0c36000 x27: 00000000f02cd000 x28: 00000000f03a210c x29: 00000000f1efee20 Code: f9400860 eb06001f 540004e0 f9400c66 (f9000c06) UEFI image [0x00000000f0da4000:0x00000000f0dbbfff] '/efi\boot\fbaa64.efi' UEFI image [0x00000000f0386000:0x00000000f07adfff] '/\EFI\debian\grubaa64.efi' UEFI image [0x00000000af4e0000:0x00000000b11dffff] Resetting CPU ... resetting ... I am unable to figure out what is the difference between the 2 ways of booting. Thanks for your help. Regards, Shantur

3 14

Bug in distro_efi_boot()
by Heinrich Schuchardt 16 Nov '23

16 Nov '23

Hello Simon, In function distro_efi_boot() the bootefi command is called. The second argument should only be passed if a device-tree has actually been loaded. But this is not what the code does: For network boot methods the value of $fdt_addr_r is passed as second parameter though possibly no file has been loaded there. We should not pass a second parameter to bootefi in this case if no device-tree was loaded. The bootefi command will fall back to the U-Boot device-tree in this case. For other boot methods gd->fdt_blob is passed as second parameter. We should not pass a second parameter in this case either. Best regards Heinrich

2 1

[BUG] usage of $kernel_addr_r in distro_efi_boot()
by Heinrich Schuchardt 16 Nov '23

16 Nov '23

If $kernel_addr_r cannot be read, distro_efi_boot() falls back to address 0. This will lead to a segmentation fault on many systems. distro_efi_read_bootflow_net() has a fallback to CONFIG_SYS_LOAD_ADDR and may have loaded to that address. Shouldn't we be consistent in what we program? Please, use a field in the bflow variable to indicate if and where an EFI binary has been loaded. Best regards Heinrich

2 1

Please pull u-boot-dm
by Simon Glass 15 Nov '23

15 Nov '23

Hi Tom, https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/18586 https://dev.azure.com/simon0972/u-boot/_build/results?buildId=55&view=resul… The following changes since commit 92b27528d777ce85362af45e7d2974a6c856219b: Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-sunxi (2023-11-12 16:36:52 -0500) are available in the Git repository at: git://git.denx.de/u-boot-dm.git tags/dm-pull-15nov23 for you to fetch changes up to 0d4d9f94c555577f78cddc372c307465fc92413e: bootstage: Correct exhasuted typo (2023-11-14 20:04:01 -0700) ---------------------------------------------------------------- patman correct import of u_boot_pylib correct long-standing EFI framebuffer bug minor test refactor ---------------------------------------------------------------- Heinrich Schuchardt (1): dm: Do not enable debug messages by default Sean Anderson (1): sandbox: Close file after mmaping it Simon Glass (10): efi: Correct handling of frame buffer bootstd: Refactor mmc prep to allow a different scan bootstd: Add a return code to bootflow menu expo: Correct background colour patman: Split out arg parsing into its own file patman: Move the main program into a function patman: Correct easy pylint warnings in __main__ patman: Avoid using func_test at top level patman: Correct Python 3.6 behaviour bootstage: Correct exhasuted typo arch/sandbox/cpu/os.c | 15 ++-- boot/expo.c | 4 +- cmd/bootflow.c | 53 ++++++++--- common/bootstage.c | 2 +- doc/usage/cmd/bootflow.rst | 67 ++++++++++++++ drivers/core/Kconfig | 1 - include/dm/util.h | 4 +- include/video.h | 9 +- lib/efi_loader/efi_gop.c | 12 +-- test/boot/bootflow.c | 64 +++++++++++-- tools/patman/__main__.py | 254 ++++++++++++++++------------------------------------ tools/patman/cmdline.py | 147 ++++++++++++++++++++++++++++++ 12 files changed, 413 insertions(+), 219 deletions(-) create mode 100644 tools/patman/cmdline.py Regards, Simon

2 1

[PATCH v3 0/4] arm: mach-snapdragon: Qualcomm pinctrl driver cleanup
by Caleb Connolly 15 Nov '23

15 Nov '23

This series moves the Qualcomm pinctrl drivers from mach-snapdragon and mach-ipq40xx to drivers/pinctrl/qcom. It then makes the necessary changes to enable compatibility with Linux DTs. The pinctrl hardware on most Qualcomm platforms is made up of "tiles", these are just banks of pins at different register addresses. The mapping between pin number and tile is totally arbitrary, this unfortunately means that it is necessary to have a map of pin to tile in order to support all pins. Up until now this driver has ignored tiles, meaning that the pin numbers and DT nodes are entirely different to the Linux DT and only a subset of pins are addressable. Patch 2 solves this by introducing the pin_offset map, initially supporting SDM845. This map is used for all pin register lookups for both the pinctrl and GPIO drivers. Similarly to the clock/reset drivers these are both associated with a single DT node, where the pinctrl driver is responsible for binding the GPIO drivers. Patch 3 introduces support for gpio-reserved-ranges, this property is used on some boards to mark pin ranges that shouldn't be touched (else firmware will trigger a fault and reset the board). This series loosely depends on the associated clock driver cleanup which can be found here (Makefile and perhaps DTS conflicts): https://lore.kernel.org/u-boot/20231103-b4-qcom-clk-v3-0-8d2d460ece84@linar… --- Changes in v3: * Fix header in msm_gpio.c * Link to v2: https://lore.kernel.org/r/20231106-b4-qcom-pinctrl-v2-0-406e8d8689ca@linaro… Changes in v2: * Drop msm -> qcom rename (will be handled in a future patch) * Drop "handle reserved ranges" patch to be introduced alongside a user * Re-order APQ4019 move to be the second patch * Change driver name to pinctrl_qcom instead of qcom_pinctrl * Add MAINTAINERS entry * Move shared GPIO header to mach-snapdragon * Link to v1: https://lore.kernel.org/r/20231025-b4-qcom-pinctrl-v1-0-9123d6a217eb@linaro… --- Caleb Connolly (4): pinctrl: qcom: move out of mach-snapdragon pinctrl: qcom: move ipq4019 driver from mach-ipq40xx pinctrl: qcom: make compatible with linux DTs msm_gpio: use unsigned int MAINTAINERS | 1 + arch/arm/Kconfig | 1 + arch/arm/dts/dragonboard845c-uboot.dtsi | 2 +- arch/arm/dts/sdm845.dtsi | 16 +- arch/arm/dts/starqltechn-uboot.dtsi | 5 +- arch/arm/dts/starqltechn.dts | 16 +- arch/arm/mach-ipq40xx/Makefile | 8 - arch/arm/mach-ipq40xx/pinctrl-snapdragon.c | 166 --------------------- arch/arm/mach-snapdragon/Kconfig | 4 + arch/arm/mach-snapdragon/Makefile | 5 - arch/arm/mach-snapdragon/include/mach/gpio.h | 28 +++- arch/arm/mach-snapdragon/pinctrl-sdm845.c | 44 ------ arch/arm/mach-snapdragon/pinctrl-snapdragon.h | 33 ---- drivers/gpio/msm_gpio.c | 42 +++--- drivers/pinctrl/Kconfig | 1 + drivers/pinctrl/Makefile | 1 + drivers/pinctrl/qcom/Kconfig | 46 ++++++ drivers/pinctrl/qcom/Makefile | 10 ++ .../pinctrl/qcom}/pinctrl-apq8016.c | 21 ++- .../pinctrl/qcom}/pinctrl-apq8096.c | 21 ++- .../pinctrl/qcom}/pinctrl-ipq4019.c | 25 +++- .../pinctrl/qcom/pinctrl-qcom.c | 70 +++++---- .../pinctrl/qcom/pinctrl-qcom.h | 15 +- .../pinctrl/qcom}/pinctrl-qcs404.c | 21 ++- drivers/pinctrl/qcom/pinctrl-sdm845.c | 100 +++++++++++++ 25 files changed, 350 insertions(+), 352 deletions(-) --- base-commit: 8c5e4ddf52ea3c1e85c44cdd5d5b2e2f6c892b4f // Caleb (they/them)

1 5

[PATCH] arm64: zynqmp: Remove description for 8T49N240
by Michal Simek 15 Nov '23

15 Nov '23

8T49N240 driver was never upstreamed by IDT and there is no user of this driver that's why remove description for this chip with also remove this driver. Signed-off-by: Michal Simek <michal.simek(a)amd.com> Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey(a)amd.com> --- arch/arm/dts/zynqmp-e-a2197-00-revA.dts | 8 +------- arch/arm/dts/zynqmp-p-a2197-00-revA.dts | 10 +--------- 2 files changed, 2 insertions(+), 16 deletions(-) diff --git a/arch/arm/dts/zynqmp-e-a2197-00-revA.dts b/arch/arm/dts/zynqmp-e-a2197-00-revA.dts index bf7569c6dda5..cc57c2a1b0be 100644 --- a/arch/arm/dts/zynqmp-e-a2197-00-revA.dts +++ b/arch/arm/dts/zynqmp-e-a2197-00-revA.dts @@ -311,13 +311,7 @@ #address-cells = <1>; #size-cells = <0>; reg = <2>; - clock_8t49n287: clock-generator@6c { /* u39 8T49N240 */ - #clock-cells = <1>; /* author David Cater <david.cater(a)idt.com>*/ - compatible = "idt,8t49n240", "idt,8t49n241"; /* FIXME no driver for 240 */ - reg = <0x6c>; - /* Documentation/devicetree/bindings/clock/idt,idt8t49n24x.txt */ - /* FIXME there input via J241 Samtec CLK1 and CLK0 from U38 - selection PIN */ - }; + /* u39 8T49N240 */ }; i2c@3 { /* PMBUS2_INA226 */ #address-cells = <1>; diff --git a/arch/arm/dts/zynqmp-p-a2197-00-revA.dts b/arch/arm/dts/zynqmp-p-a2197-00-revA.dts index c456c375ac80..9acccad40e77 100644 --- a/arch/arm/dts/zynqmp-p-a2197-00-revA.dts +++ b/arch/arm/dts/zynqmp-p-a2197-00-revA.dts @@ -532,15 +532,7 @@ /* u36 0xd8 or 0xde - pcie clk buf - 9ZML1241EKILF PCIe GEN 4 CLOCK BUFFER FIXME - no driver */ /* u37 0xd0 DNP - pcie clocking 1 - 9FGV1006BQ505LTGI - PCIe GEN 4 CLOCK GENERATOR FIXME - no linux driver */ /* u38 0xca - pcie clocking 2 - 9ZML1241EKILF PCIe GEN 4 CLOCK BUFFER FIXME - no driver */ - clock_8t49n287: clock-generator@60 { /* u39 8T49N240 - pcie clocking 3 */ - #clock-cells = <1>; /* author David Cater <david.cater(a)idt.com>*/ - compatible = "idt,8t49n240", "idt,8t49n241"; /* FIXME no driver for 240 */ - reg = <0x60>; - /* Documentation/devicetree/bindings/clock/idt,idt8t49n24x.txt */ - /* FIXME there input via J241 Samtec CLK1 and CLK0 from U38 - selection PIN */ - - }; - + /* u39 8T49N240 - pcie clocking 3 */ }; }; }; -- 2.36.1

1 1

[PATCH] arm64: zynqmp: Do not expose usbhub nodes
by Michal Simek 15 Nov '23

15 Nov '23

Upstream dwc3 U-Boot driver is not able to handle child nodes properly that's why comment them in DT for now. This patch should be reverted when dwc3 driver handles it properly. DT node itself is aligned with dt schema. Signed-off-by: Michal Simek <michal.simek(a)amd.com> --- arch/arm/dts/zynqmp-sck-kd-g-revA.dtso | 3 ++- arch/arm/dts/zynqmp-sck-kr-g-revA.dtso | 3 ++- arch/arm/dts/zynqmp-sck-kr-g-revB.dtso | 3 ++- arch/arm/dts/zynqmp-sck-kv-g-revA.dtso | 2 ++ arch/arm/dts/zynqmp-sck-kv-g-revB.dtso | 3 ++- 5 files changed, 10 insertions(+), 4 deletions(-) diff --git a/arch/arm/dts/zynqmp-sck-kd-g-revA.dtso b/arch/arm/dts/zynqmp-sck-kd-g-revA.dtso index 5a5c1efd6b96..8d0ddecdc14c 100644 --- a/arch/arm/dts/zynqmp-sck-kd-g-revA.dtso +++ b/arch/arm/dts/zynqmp-sck-kd-g-revA.dtso @@ -87,7 +87,7 @@ phys = <&psgtr 2 PHY_TYPE_USB3 0 2>; reset-gpios = <&slg7xl45106 0 GPIO_ACTIVE_LOW>; assigned-clock-rates = <250000000>, <20000000>; - +#if 0 usbhub0: usb-hub { /* u36 */ i2c-bus = <&i2c1>; compatible = "microchip,usb5744"; @@ -98,6 +98,7 @@ compatible = "microchip,usb2244"; reset-gpios = <&slg7xl45106 2 GPIO_ACTIVE_LOW>; }; +#endif }; &dwc3_0 { diff --git a/arch/arm/dts/zynqmp-sck-kr-g-revA.dtso b/arch/arm/dts/zynqmp-sck-kr-g-revA.dtso index 30a0230d4767..95b1dc5aa571 100644 --- a/arch/arm/dts/zynqmp-sck-kr-g-revA.dtso +++ b/arch/arm/dts/zynqmp-sck-kr-g-revA.dtso @@ -139,7 +139,7 @@ phys = <&psgtr 2 PHY_TYPE_USB3 0 2>; reset-gpios = <&slg7xl45106 0 GPIO_ACTIVE_LOW>; assigned-clock-rates = <250000000>, <20000000>; - +#if 0 usbhub0: usb-hub { /* u43 */ i2c-bus = <&usbhub_i2c0>; compatible = "microchip,usb5744"; @@ -150,6 +150,7 @@ compatible = "microchip,usb2244"; reset-gpios = <&slg7xl45106 2 GPIO_ACTIVE_LOW>; }; +#endif }; &dwc3_0 { diff --git a/arch/arm/dts/zynqmp-sck-kr-g-revB.dtso b/arch/arm/dts/zynqmp-sck-kr-g-revB.dtso index 8f4c52d6d643..e2387a2abb8f 100644 --- a/arch/arm/dts/zynqmp-sck-kr-g-revB.dtso +++ b/arch/arm/dts/zynqmp-sck-kr-g-revB.dtso @@ -139,7 +139,7 @@ phys = <&psgtr 2 PHY_TYPE_USB3 0 2>; reset-gpios = <&slg7xl45106 0 GPIO_ACTIVE_LOW>; assigned-clock-rates = <250000000>, <20000000>; - +#if 0 usbhub0: usb-hub { /* u43 */ i2c-bus = <&usbhub_i2c0>; compatible = "microchip,usb5744"; @@ -150,6 +150,7 @@ compatible = "microchip,usb2244"; reset-gpios = <&slg7xl45106 2 GPIO_ACTIVE_LOW>; }; +#endif }; &dwc3_0 { diff --git a/arch/arm/dts/zynqmp-sck-kv-g-revA.dtso b/arch/arm/dts/zynqmp-sck-kv-g-revA.dtso index c4f1da92186f..f43c159cdca9 100644 --- a/arch/arm/dts/zynqmp-sck-kv-g-revA.dtso +++ b/arch/arm/dts/zynqmp-sck-kv-g-revA.dtso @@ -131,10 +131,12 @@ pinctrl-0 = <&pinctrl_usb0_default>; phy-names = "usb3-phy"; phys = <&psgtr 2 PHY_TYPE_USB3 0 1>; +#if 0 usbhub: usb5744 { /* u43 */ compatible = "microchip,usb5744"; reset-gpios = <&gpio 44 GPIO_ACTIVE_LOW>; }; +#endif }; &dwc3_0 { diff --git a/arch/arm/dts/zynqmp-sck-kv-g-revB.dtso b/arch/arm/dts/zynqmp-sck-kv-g-revB.dtso index 6c5e0e566061..3643569cc7c8 100644 --- a/arch/arm/dts/zynqmp-sck-kv-g-revB.dtso +++ b/arch/arm/dts/zynqmp-sck-kv-g-revB.dtso @@ -113,13 +113,14 @@ phy-names = "usb3-phy"; phys = <&psgtr 2 PHY_TYPE_USB3 0 1>; assigned-clock-rates = <250000000>, <20000000>; - +#if 0 usb5744: usb-hub { /* u43 */ status = "okay"; compatible = "microchip,usb5744"; i2c-bus = <&i2c1>; reset-gpios = <&gpio 44 GPIO_ACTIVE_LOW>; }; +#endif }; &dwc3_0 { -- 2.36.1

1 1

u-boot fails to build on sparc64 due redefinition of 'struct termio'
by John Paul Adrian Glaubitz 15 Nov '23

15 Nov '23

Hello! On Linux sparc64, building u-boot fails with [1]: cc -o tools/mkenvimage tools/mkenvimage.o tools/os_support.o tools/lib/crc32.o In file included from /<<PKGBUILDDIR>>/tools/termios_linux.h:33, from /<<PKGBUILDDIR>>/tools/kwboot.c:153: /usr/include/sparc64-linux-gnu/asm/termbits.h:14:8: error: redefinition of 'struct termio' 14 | struct termio { | ^~~~~~ In file included from /usr/include/sparc64-linux-gnu/sys/ioctl.h:29, from /<<PKGBUILDDIR>>/tools/termios_linux.h:30: /usr/include/sparc64-linux-gnu/bits/ioctl-types.h:36:8: note: originally defined here 36 | struct termio | ^~~~~~ Reading through tools/termios_linux.h, it seems like the problem is that <asm/ioctl.h> and <asm/termbits.h> are included at the same time. Not sure whether this is allowed according to the glibc documentation. Full build log available in [1]. Adrian > [1] https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=sparc64&ver=2023… Bdfsg-1&stamp=1699723544&raw=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

2 2

[PATCH v5 00/20] x86: efi: Fixes and improvements for coreboot
by Simon Glass 15 Nov '23

15 Nov '23

This little series fixes various bugs and annoyances in coreboot and coreboot64. With this both coreboot and coreboot64 start up and work reasonably well on Brya (x86 Chromebook) and U-Boot can boot common Linux distros. - Make coreboot64 debug UART start reliably - Avoid the long USB-init delay on startup - Correct the timer speed on coreboo64 - Fix a bootstd cros bug (will likely be squashed into another patch) - Fix the terribly slow console scrolling With v2 I have also brought in some lost x86 patches so they are all in one series. Changes in v5: - Use 'lzma' instead of 'LZMA' - Drop unwanted space - Correct 'teechnique' typo in commit message - Make use of the uSE_PREBOOT mechanism Changes in v4: - Fix arm and riscv - Rewrite this to use events instead Changes in v3: - Allow SMBIOS if EFI_LOADER is enabled - Reword the help - Use log_debug() to show the message - Squash in the next patch Changes in v2: - Update the malloc size too - Add new patch - Add new patch - Add new patch - Add new patch - Add new patch - Add new patch - Add new patch - Add new patch - Add new patch Simon Glass (20): x86: coreboot: Add IDE and SATA x86: coreboot: Enable standard boot x86: coreboot: Rearrange arch_cpu_init() x86: Set the CPU vendor in SPL x86: Allow APCI in SPL x86: coreboot: Look for DBG2 UART in SPL too x86: coreboot: Enable CONFIG_SYS_NS16550_MEM32 x86: coreboot: Drop USB init on startup x86: coreboot: Align options between coreboot and coreboot64 x86: coreboot: Enable VIDEO_COPY efi: x86: Correct the condition for installing ACPI tables x86: smbios: Add a Kconfig indicating SMBIOS-table presence bootstd: Keep track of use of usb stop Record the position of the SMBIOS tables efi: Use the installed SMBIOS tables x86: coreboot: Record the position of the SMBIOS tables x86: doc: Move into its own directory x86: doc: Update summaries and add links x86: doc: Split out manual booting into its own file x86: doc: coreboot: Mention 64-bit Linux distros arch/arm/include/asm/global_data.h | 3 + arch/riscv/include/asm/global_data.h | 3 + arch/sandbox/include/asm/global_data.h | 1 + arch/x86/cpu/coreboot/Kconfig | 1 + arch/x86/cpu/coreboot/coreboot.c | 16 +- arch/x86/cpu/x86_64/cpu.c | 7 + arch/x86/dts/coreboot.dts | 1 + arch/x86/include/asm/global_data.h | 1 + arch/x86/lib/coreboot/cb_sysinfo.c | 1 + arch/x86/lib/tables.c | 3 + boot/bootdev-uclass.c | 27 +++ configs/coreboot64_defconfig | 25 ++- configs/coreboot_defconfig | 21 +- doc/arch/index.rst | 2 +- doc/arch/x86/index.rst | 12 + doc/arch/x86/manual_boot.rst | 276 +++++++++++++++++++++++ doc/arch/{ => x86}/x86.rst | 295 ++----------------------- doc/board/coreboot/coreboot.rst | 38 +++- drivers/serial/Kconfig | 2 +- drivers/usb/host/usb-uclass.c | 8 + drivers/video/coreboot.c | 12 + include/asm-generic/global_data.h | 8 + include/bootdev.h | 9 + lib/Kconfig | 24 +- lib/efi_loader/Makefile | 4 +- lib/efi_loader/efi_setup.c | 20 +- lib/efi_loader/efi_smbios.c | 72 +++--- test/py/tests/test_event_dump.py | 1 + 28 files changed, 543 insertions(+), 350 deletions(-) create mode 100644 doc/arch/x86/index.rst create mode 100644 doc/arch/x86/manual_boot.rst rename doc/arch/{ => x86}/x86.rst (64%) -- 2.42.0.459.ge4e396fd5e-goog

4 30