December 2023 - U-Boot

[PATCH v5 0/5] Implement fastboot multiresponce
by Svyatoslav Ryhel 28 Dec '23

28 Dec '23

Currently u-boot fastboot can only send one message back to host, so if there is a need to print more than one line messages must be kept sending until all the required data is obtained. This behavior can be adjusted using multiresponce ability (getting multiple lines of response) proposed in this patch set. Implementation of multiresponce leads to ability to dump content of console buffer which, with use of "oem run", allows to entirely avoid need in UART. --- Changes in v5: - restored membuff_readline behavior changed in v4 Changes in v4: - adjust membuff_readline behavior with overflow Changes in v3: - fix missing function calls if CONFIG_CONSOLE_RECORD is not enabled Changes in v2: - changed variables to static - fixed multiresponce for udp - documented use of "MORE" - converted #if to if (...) --- Ion Agorria (5): fastboot: multiresponse support fastboot: implement "getvar all" common: console: introduce overflow and isempty calls lib: membuff: fix readline not returning line in case of overflow fastboot: add oem console command support boot/bootmeth_extlinux.c | 2 +- common/console.c | 17 +++++-- doc/android/fastboot-protocol.rst | 3 ++ doc/android/fastboot.rst | 1 + drivers/fastboot/Kconfig | 7 +++ drivers/fastboot/fb_command.c | 52 +++++++++++++++++++++ drivers/fastboot/fb_getvar.c | 77 +++++++++++++++++++++++++------ drivers/usb/gadget/f_fastboot.c | 29 ++++++++++++ include/console.h | 26 +++++++++++ include/fastboot-internal.h | 7 +++ include/fastboot.h | 19 ++++++++ include/membuff.h | 5 +- lib/membuff.c | 4 +- net/fastboot_udp.c | 29 +++++++++--- test/ut.c | 9 ++-- 15 files changed, 254 insertions(+), 33 deletions(-) -- 2.40.1

2 6

[PATCH v3 00/14] Support Firmware Handoff spec via bloblist
by Raymond Mao 28 Dec '23

28 Dec '23

Major changes: Update bloblist to align to Firmware Handoff spec v0.9 (up to commit #3592349 of the spec) (https://github.com/FirmwareHandoff/firmware_handoff). Includes: - Align bloblist tags with the FW handoff spec - Add an explicit alignment field in the header - Update bloblist magic and version - Use a packed format for blob record header - Change the checksum alorigthm - Use a void entry to handle the alignment - Adjust the headers of bloblist and blob record - Align the bloblist record data section start address In v3, the implementation from boot arguments to bloblist and how to load the FDT from the bloblist are moved to a forthcoming patch serie. Raymond Mao (1): bloblist: Align bloblist used_size and total_size to spec Simon Glass (13): bloblist: Update the tag numbering bloblist: Adjust API to align in powers of 2 bloblist: Change the magic value bloblist: Set version to 1 bloblist: Access record hdr_size and tag via a function bloblist: Drop spare value from bloblist record bloblist: Change the checksum algorithm bloblist: Checksum the entire bloblist bloblist: Handle alignment with a void entry bloblist: Reduce blob-header size bloblist: Adjust the bloblist header bloblist: Add alignment to bloblist_new() bloblist: Update documentation and header comment arch/x86/lib/tables.c | 3 +- common/bloblist.c | 205 ++++++++++++++++++++++++--------------- doc/develop/bloblist.rst | 4 +- include/bloblist.h | 166 ++++++++++++++++++------------- test/bloblist.c | 105 +++++++++++--------- 5 files changed, 287 insertions(+), 196 deletions(-) -- 2.25.1

3 39

[RFC PATCH 0/2] Passing U-Boot logs to the OS
by Bence Cs 28 Dec '23

28 Dec '23

The problem of sending boot logs to the booted OS has not been solved, but it is high time we do it. This proposed patch aims to give a crude solution, utilizing CONFIG_CONSOLE_RECORD to capture the logs and saving them to RAM, along with a struct residing at CONFIG_CONSOLE_RECORD_SAVE_BASE. There may be more sophisticated methods than this, which may be implemented if time permits. Please note that this patch is not the final solution, but we do intend to finish it by the end of the MW. Also I am WFH for the holidays, so if someone could smoke-test, I'd appreciate it. The patch series was based on the current tip of `next` branch: Commit: 4b151562bb bootmeth: pass size to efi_binary_run() Previous discussion thread can be found here: Link: https://lists.denx.de/pipermail/u-boot/2023-December/541138.html Bence Cs (2): Add U_BOOT_VERSION_CODE macro for packing the version number into a single int common: console: Add support of passing the saved console log to the OS boot/bootm.c | 27 +++++++++++++++++++++++++-- common/Kconfig | 13 +++++++++++++ common/console.c | 13 +++++++++++++ include/console.h | 19 +++++++++++++++++++ include/version.h | 3 +++ 5 files changed, 73 insertions(+), 2 deletions(-) -- 2.25.1

2 3

[XEN] Re: I'm looking for the source code of a specific u-boot version.
by Heinrich Schuchardt 27 Dec '23

27 Dec '23

Am 27. Dezember 2023 19:54:06 MEZ schrieb Mario Marietto <marietto2008(a)gmail.com>: >Hello. > >I'm trying to boot FreeBSD for arm32 bit as DomU on my ARM Chromebook >SNOW with xen. Basically there are two ways to accomplish this task : > > >1) to write a patch that allows the FreeBSD kernel to boot as a zImage >file. This could be accomplished applying this patch to a specific >file that's on the source code of FreeBSD : > > >https://xenbits.xen.org/gitweb/?p=p...8;hb=0782e25d98cc1391472717035f986c97… > > > >This patch was written by Julien Grall a lot of time ago and now it >does not work anymore. This is the reason explain by the xen >developers : > > > >It appears FreeBSD-CURRENT removed the last step converting the kernel >file to kernel.bin.The patch can be readily rebased, but without >kernel.bin that doesn't do too much. > > > >So,without a rebase of that patch the first option is not applicable. >And I'm not able to fix it. > > >2) booting FreeBSD using U-Boot,as explained to me by a xen developer : > > >I was trying to explain why and how Julien's patch works so that you >could be the one to re-do something similar or fix the patch on the >FreeBSD kernel that you are working with. I am happy to help review >and write patches but I don't work with the FreeBSD kernel so I >wouldn't be able to help you quickly. However, I might have a >suggestion. Do you know if FreeBSD can be booted by U-Boot ? Because >U-Boot definitely boots as Xen on ARM guest firmware/bootloader. You >should be able to build U-Boot and use the U-Boot binary as Xen guest >kernel, then U-Boot could load FreeBSD from disk or network and start >it. For instance as domU config file: > >kernel="/home/petalinux/u-boot.bin" >disk = [ '/home/petalinux/test.img,raw,xvda' ] > > >Actually I'm working on the idea n. 2. Basically I need to find the >proper u-boot file that's able to boot the image of FreeBSD that I >have installed (13.2 for arm32 bit). Maybe I found it here : > > >http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv_u… > > >I found that link inside this tutorial : > > >https://wiki.freebsd.org/arm/Chromebook > > >the version of u-boot that has been embedded in that file is the following one : > > ># strings nv_uboot-snow-simplefb.kpart | grep U-Boot >U-Boot 2011.12-gc1f6280 (May 27 2013 - 15:06:59) for SMDK5250 > > >So the question is easy : I need to find the source code of that old >version of u-boot,because once compiled,it will give me the proper >u-boot.bin kernel / bootloader file that maybe will be able to boot >FreeBSD. > > Hello Mario, U-Boot supports booting EFI binaries since 2016. I don't know if some arm32 bits are still missing in FreeBSD (see https://wiki.freebsd.org/UEFI). But looking at https://cgit.freebsd.org/src/plain/stand/efi/loader/Makefile.depend.arm and https://cgit.freebsd.org/src/plain/stand/efi/loader/arch/arm/start.S arm32 should be supported. I guess the wiki needs an update. The U-Boot documentation only describes arm64 Xen support: https://docs.u-boot.org/en/latest/board/xen/xenguest_arm64.html . I have CCed the U-Boot Xen maintainers hoping they can indicate the missing pieces for arm32. Best regards Heinrich

1 0

[PATCH v2 0/5] Implement fastboot multiresponce
by Svyatoslav Ryhel 27 Dec '23

27 Dec '23

Currently u-boot fastboot can only send one message back to host, so if there is a need to print more than one line messages must be kept sending until all the required data is obtained. This behavior can be adjusted using multiresponce ability (getting multiple lines of response) proposed in this patch set. Implementation of multiresponce leads to ability to dump content of console buffer which, with use of "oem run", allows to entirely avoid need in UART. --- Changes from v1: - changed variables to static - fixed multiresponce for udp - documented use of "MORE" - converted #if to if (...) --- Ion Agorria (5): fastboot: multiresponse support fastboot: implement "getvar all" common: console: introduce overflow and isempty calls lib: membuff: fix readline not returning line in case of overflow fastboot: add oem console command support boot/bootmeth_extlinux.c | 2 +- common/console.c | 17 +++++-- doc/android/fastboot-protocol.rst | 3 ++ doc/android/fastboot.rst | 1 + drivers/fastboot/Kconfig | 7 +++ drivers/fastboot/fb_command.c | 52 +++++++++++++++++++++ drivers/fastboot/fb_getvar.c | 75 +++++++++++++++++++++++++------ drivers/usb/gadget/f_fastboot.c | 29 ++++++++++++ include/console.h | 14 ++++++ include/fastboot-internal.h | 7 +++ include/fastboot.h | 19 ++++++++ include/membuff.h | 5 ++- lib/membuff.c | 4 +- net/fastboot_udp.c | 29 +++++++++--- test/ut.c | 9 ++-- 15 files changed, 240 insertions(+), 33 deletions(-) -- 2.40.1

3 11

[PATCH v2 0/6] smbios: Deal with tables beyond 4GB
by Simon Glass 27 Dec '23

27 Dec '23

When the malloc() region extends beyond 4GB on ARM we may end up with an SMBIOS table in that region. Add support for writing an SMBIOS3 table, which supports a 64-bit address. Note that this problem does not happen on x86 since it requires the tables to be placed just below 1MB in memory, unless CONFIG_BLOBLIST_TABLES is enabled. Changes in v2: - Check the end of the table rather than the start. - Add a new patch to correct gd_smbios_start() - Add a note about why unmap_system() is called Simon Glass (6): smbios: Refactor 32-bit code into an else statement smbios: Move the rest of the SMBIOS2 code smbios: Use SMBIOS 3.0 to support an address above 4GB smbios: Correct gd_smbios_start() efi: Use the correct GUID for the SMBIOS table smbios: Require the caller to align the SMBIOS table include/asm-generic/global_data.h | 2 +- include/efi_api.h | 4 ++ include/smbios.h | 27 +++++++++-- lib/efi_loader/efi_smbios.c | 14 ++++-- lib/smbios.c | 79 ++++++++++++++++++------------- 5 files changed, 85 insertions(+), 41 deletions(-) -- 2.42.0.655.g421f12c284-goog

4 22

[PATCH] include: env: ti: ti_common: Run main_cpsw0_qsgmii_phyinit conditionally
by Siddharth Vadapalli 27 Dec '23

27 Dec '23

From: Manorit Chawdhry <m-chawdhry(a)ti.com> The main_cpsw0_qsgmii_phyinit command is defined only for certain TI SoCs which have the do_main_cpsw0_qsgmii_phyinit variable set. Add a check to ensure that the main_cpsw0_qsgmii_phyinit command is run only for such SoCs. Signed-off-by: Manorit Chawdhry <m-chawdhry(a)ti.com> Signed-off-by: Siddharth Vadapalli <s-vadapalli(a)ti.com> --- Hello, This patch is based on commit 65eed68772 test/py: Disable error E0611 in two cases for pylint Regards, Siddharth. include/env/ti/ti_common.env | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/include/env/ti/ti_common.env b/include/env/ti/ti_common.env index f5d84216e3..f0f89a2287 100644 --- a/include/env/ti/ti_common.env +++ b/include/env/ti/ti_common.env @@ -25,7 +25,10 @@ run_fit=run get_fit_config; bootm ${addr_fit}#${name_fit_config}${overlaystring} bootcmd_ti_mmc= run findfdt; run init_${boot}; #if CONFIG_CMD_REMOTEPROC - run main_cpsw0_qsgmii_phyinit; run boot_rprocs; + if test ${do_main_cpsw0_qsgmii_phyinit} -eq 1; + then run main_cpsw0_qsgmii_phyinit; + fi + run boot_rprocs; #endif if test ${boot_fit} -eq 1; then run get_fit_${boot}; run get_fit_overlaystring; run run_fit; -- 2.34.1

4 4

[PATCH 1/1] smbios: type2: contained object handles
by Heinrich Schuchardt 27 Dec '23

27 Dec '23

The type 2 structure must include information about the contained objects. It is fine to set the number of contained object handles to 0. Add the missing field. Fixes: 721e992a8af5 ("x86: Add SMBIOS table support") Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- include/smbios.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/smbios.h b/include/smbios.h index e601283d29..88c19ae062 100644 --- a/include/smbios.h +++ b/include/smbios.h @@ -139,6 +139,7 @@ struct __packed smbios_type2 { u8 chassis_location; u16 chassis_handle; u8 board_type; + u8 number_contained_objects; char eos[SMBIOS_STRUCT_EOS_BYTES]; }; -- 2.43.0

3 2

[PATCH 1/1] lib: smbios: verify_checksum() is duplicate
by Heinrich Schuchardt 27 Dec '23

27 Dec '23

The function verify_checksum() duplicates what table_compute_checksum() does. Replace it. Fixes: 415eab0655a8 ("smbios: add parsing API") Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- lib/smbios-parser.c | 18 ++---------------- 1 file changed, 2 insertions(+), 16 deletions(-) diff --git a/lib/smbios-parser.c b/lib/smbios-parser.c index f4de350e6e..a29a06398d 100644 --- a/lib/smbios-parser.c +++ b/lib/smbios-parser.c @@ -5,23 +5,9 @@ #define LOG_CATEGORY LOGC_BOOT +#include <tables_csum.h> #include <smbios.h> -static inline int verify_checksum(const struct smbios_entry *e) -{ - /* - * Checksums for SMBIOS tables are calculated to have a value, so that - * the sum over all bytes yields zero (using unsigned 8 bit arithmetic). - */ - u8 *byte = (u8 *)e; - u8 sum = 0; - - for (int i = 0; i < e->length; i++) - sum += byte[i]; - - return sum; -} - const struct smbios_entry *smbios_entry(u64 address, u32 size) { const struct smbios_entry *entry = (struct smbios_entry *)(uintptr_t)address; @@ -32,7 +18,7 @@ const struct smbios_entry *smbios_entry(u64 address, u32 size) if (memcmp(entry->anchor, "_SM_", 4)) return NULL; - if (verify_checksum(entry)) + if (table_compute_checksum(entry, entry->length)) return NULL; return entry; -- 2.43.0

3 2

[PATCH v2 0/8] An effort to bring DT bindings compliance within U-Boot
by Sumit Garg 27 Dec '23

27 Dec '23

Changes in v2: -------------- - Patch #1: excluded gitab CI config check and added commit description. - Patch #3: s/UBOOT_DTSI_LOC/u_boot_dtsi_loc/ - Patch #4: s/DEVICE_TREE_LOC/dt_dir/ and s/U-boot/U-Boot/ - Patch #5: s/U-boot/U-Boot/ - Patch #6 and #7: Picked up review tags Prerequisite ------------ This patch series requires devicetree-rebasing git repo to be added as a subtree to the main U-Boot repo via: $ git subtree add --prefix devicetree-rebasing \ git://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasin… \ v6.6-dts --squash Background ---------- This effort started while I was reviewing patch series corresponding to Qcom platforms [1] which was about to import modified devicetree source files from Linux kernel. I suppose keeping devicetree files sync with Linux kernel without any DT bindings schema validation has been a pain for U-Boot SoC/platform maintainers. There has been past discussions about a single DT repo but that hasn't come up and Linux kernel remained the place where DT source files as well as bindings are placed and maintained. However, Linux kernel DT maintainers proposed [2] for U-Boot to rather use devicetree-rebasing repo [3] which is a forked copy from Linux kernel for DT source files as well as bindings. It is tagged at every Linux kernel major release or intermideate release candidates. So here I have tried to reuse that to bring DT bingings compliance as well as a standard way to maintain a regular sync of DT source files with Linux kernel. In order to maintain devicetree files sync, U-Boot will maintains a Git subtree for devicetee-rebasing repo as `devicetee-rebasing/` sub-directory. It will be regularly updated with every new kernel major release via subtree pull as follows: $ git subtree pull --prefix devicetree-rebasing \ git://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasin… \ <release-tag> --squash The RFC/prototype for this series has been discussed with Linux DT maintainers as well as U-Boot maintainers here [4]. Now we would like to reach out to wider U-Boot community to seek feedback. [1] https://lore.kernel.org/all/CAFA6WYMLUD9cnkr=R0Uur+1UeTMkKjM2zDdMJtXb3nmrLk… [2] https://lore.kernel.org/all/CAL_JsqKEjv2tSGmT+0ZiO7_qbBfhTycbGnhJhYpKDFzfO9… [3] https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… [4] https://github.com/u-boot/u-boot/pull/451 Changes ------- Traditionally, U-Boot placed copies of devicetree source files from Linux kernel into `arch/<arch>/dts/<name>.dts`, which can be selected via: CONFIG_DEFAULT_DEVICE_TREE "<name>" SoC/board maintainers are encouraged to migrate to using mirrored copies from `devicetree-rebasing/` into `dts/arch/<arch>/<vendor>` via: CONFIG_OF_UPSTREAM=y CONFIG_DEFAULT_DEVICE_TREE "<vendor>/<name>" An example have been shown for Amlogic meson-gxbb SoC and corresponding derived boards via patch #7 and #8. Devicetree bindings schema checks --------------------------------- With devicetee-rebasing Git subtree, the devicetree bindings are also regularly synced with Linux kernel as `devicetree-rebasing/Bindings/` sub-directory. This allows U-Boot to run devicetree bindings schema checks which will bring compliance to U-Boot core/drivers regarding usage of devicetree. Dependencies ------------ The DT schema project must be installed in order to validate the DT schema binding documents and validate DTS files using the DT schema. The DT schema project can be installed with pip: $ pip3 install dtschema Note that 'dtschema' installation requires 'swig' and Python development files installed first. On Debian/Ubuntu systems: $ apt install swig python3-dev Several executables (dt-doc-validate, dt-mk-schema, dt-validate) will be installed. Ensure they are in your PATH (~/.local/bin by default). Recommended is also to install yamllint (used by dtschema when present). Running checks -------------- In order to perform validation of DTB files, use the ``dtbs_check`` target: $ make dtbs_check It is also possible to run checks with a subset of matching schema files by setting the ``DT_SCHEMA_FILES`` variable to 1 or more specific schema files or patterns (partial match of a fixed string). Each file or pattern should be separated by ':'. $ make dtbs_check DT_SCHEMA_FILES=trivial-devices.yaml:rtc.yaml $ make dtbs_check DT_SCHEMA_FILES=/gpio/ $ make dtbs_check DT_SCHEMA_FILES=trivial-devices.yaml Sumit Garg (8): CI: Exclude devicetree-rebasing subtree for CONFIG checks Makefile: Add support for DT bindings schema checks scripts/Makefile.lib: Statically define *-u-boot.dtsi files location dts: Add alternative location for upstream DTB builds doc: devicetree: Updates for devicetree-rebasing subtree MAINTAINERS: Add myself as devicetree-rebasing maintainer dts: meson-gxbb: Switch to using upstream DT dts: meson-gxbb: Drop redundant devicetree files .azure-pipelines.yml | 3 +- .gitlab-ci.yml | 3 +- MAINTAINERS | 6 + Makefile | 20 +- arch/arm/dts/Makefile | 8 - arch/arm/dts/meson-gxbb-kii-pro.dts | 140 ---- arch/arm/dts/meson-gxbb-nanopi-k2.dts | 415 ------------ arch/arm/dts/meson-gxbb-odroidc2.dts | 418 ------------ arch/arm/dts/meson-gxbb-p200.dts | 100 --- arch/arm/dts/meson-gxbb-p201.dts | 26 - arch/arm/dts/meson-gxbb-p20x.dtsi | 250 ------- arch/arm/dts/meson-gxbb-wetek-hub.dts | 58 -- arch/arm/dts/meson-gxbb-wetek-play2.dts | 119 ---- arch/arm/dts/meson-gxbb-wetek.dtsi | 292 -------- arch/arm/dts/meson-gxbb.dtsi | 856 ------------------------ configs/nanopi-k2_defconfig | 3 +- configs/odroid-c2_defconfig | 3 +- configs/p200_defconfig | 3 +- configs/p201_defconfig | 3 +- configs/videostrong-kii-pro_defconfig | 3 +- configs/wetek-hub_defconfig | 3 +- configs/wetek-play2_defconfig | 3 +- doc/develop/devicetree/control.rst | 108 ++- dts/Kconfig | 11 + dts/Makefile | 17 +- dts/arch/arm64/Makefile | 23 + dts/arch/arm64/amlogic | 1 + scripts/Makefile.lib | 42 +- 28 files changed, 206 insertions(+), 2731 deletions(-) delete mode 100644 arch/arm/dts/meson-gxbb-kii-pro.dts delete mode 100644 arch/arm/dts/meson-gxbb-nanopi-k2.dts delete mode 100644 arch/arm/dts/meson-gxbb-odroidc2.dts delete mode 100644 arch/arm/dts/meson-gxbb-p200.dts delete mode 100644 arch/arm/dts/meson-gxbb-p201.dts delete mode 100644 arch/arm/dts/meson-gxbb-p20x.dtsi delete mode 100644 arch/arm/dts/meson-gxbb-wetek-hub.dts delete mode 100644 arch/arm/dts/meson-gxbb-wetek-play2.dts delete mode 100644 arch/arm/dts/meson-gxbb-wetek.dtsi delete mode 100644 arch/arm/dts/meson-gxbb.dtsi create mode 100644 dts/arch/arm64/Makefile create mode 120000 dts/arch/arm64/amlogic -- 2.34.1

7 35