u-boot.git/examples, branch next

treewide: prefer func over FUNCTION and __PRETTY_FUNCTION__

2026-06-10T20:49:46Z

__FUNCTION__ and __PRETTY_FUNCTION__ are gcc extensions that predate the C99 __func__ identifier. scripts/checkpatch.pl emits a warning for any new use of __FUNCTION__ and recommends __func__ instead. In C (unlike C++) __PRETTY_FUNCTION__ is identical to __func__ because C function names do not carry signature information, so the distinction has no behavioural effect here. The majority of the tree already uses __func__, but a handful of older files in arch/, board/, boot/, drivers/, examples/ and include/ still carry the gcc spellings (55 occurrences of __FUNCTION__ across 19 files plus one __PRETTY_FUNCTION__ in drivers/usb/musb-new/omap2430.c). Convert them all to the C99 form so the tree is consistent and new patches in these areas do not have to follow an outdated local style. Ten "Unnecessary ftrace-like logging - prefer using ftrace" warnings remain on the printf("%s\n", __func__) and dbg("%s\n", __func__) function-entry traces in drivers/net/rtl8169.c (behind DEBUG_RTL8169* preprocessor guards) and drivers/usb/host/ohci-hcd.c. checkpatch matches the literal "%s\n", __func__ shape regardless of the wrapper, so silencing those warnings would require changing the debug message text or removing the traces entirely. Signed-off-by: Aristo Chen Reviewed-by: Tom Rini

examples: Fix checking id parameter in thread_start

2025-12-05T22:23:54Z

lthreads is of size MAX_THREADS, hence id must be lower than MAX_THREADS to avoid any potential buffer overflow in thread_start function. Signed-off-by: Francois Berder

examples: fix building on arm32

2025-02-04T17:57:36Z

Refer to the commit a3c101a61348 ("examples: fix building on arm64") fix for arm32. crt0.S does not even build with: operating system and architecture: 5.15.0-130-generic x86_64 installed version of gcc and binutils: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.3) GNU ld (GNU Binutils for Ubuntu) 2.34 used defconfig: stm32h750-art-pi_defconfig used commands for building: export CROSS_COMPILE=arm-none-eabi- ARCH=arm make stm32h750-art-pi_defconfig make menuconfig # to add make examples/api/crt0.S: Assembler messages: examples/api/crt0.S:32: Error: lo register required -- `ldr ip,=search_hint' examples/api/crt0.S:33: Error: lo register required -- `str sp,[ip]' examples/api/crt0.S:39: Error: lo register required -- `ldr ip,=syscall_ptr' examples/api/crt0.S:40: Error: lo register required -- `ldr pc,[ip]' make[2]: *** [scripts/Makefile.build:292：examples/api/crt0.o] Error 1 Use valid register names and instructions. Signed-off-by: Liya Huang <1425075683@qq.com>

examples: eliminate CONFIG_STANDALONE_LOAD_ADDR

2025-02-04T17:57:36Z

CONFIG_STANDALONE_LOAD_ADDR has been used for examples/standalone but not for examples/api. The suitability of an address to load an ELF binary and run it does not only depend on the architecture but also on the memory layout of the board which is not reflected in the default value of CONFIG_STANDALONE_LOAD_ADDR. Commit 32b7e39db4d3 ("Convert CONFIG_STANDALONE_LOAD_ADDR to Kconfig") set the default on RISC-V to 0x0 though most boards used 0x80200000 before the patch. On most boards we can assume 8 MiB of memory available above $loadaddr. So we can safely use $loadaddr + 4 MiB as load address for the standalone example and eliminate CONFIG_STANDALONE_LOAD_ADDR altogether. Fixes: 32b7e39db4d3 ("Convert CONFIG_STANDALONE_LOAD_ADDR to Kconfig") Signed-off-by: Heinrich Schuchardt

examples/api: improve determination of LOAD_ADDR

2025-02-04T17:57:36Z

The current load address for the 'demo' binary does not work for qemu_arm_defconfig. The suitability of an address to load an ELF binary and run it does not only depend on the architecture but also on the memory layout of the board. On most boards we can assume that 8 MiB of memory is available above $loadaddr. So $loadaddr + 0x400000 should work there. Signed-off-by: Heinrich Schuchardt

examples: use QEMU compatible LOAD_ADDR on RISC-V

2025-01-05T01:30:47Z

On some RISC-V including QEMU $loadaddr is 0x80200000. For bootelf to work choose a different LOAD_ADDR to which the demo ELF binary is relocated. Signed-off-by: Heinrich Schuchardt

examples: use architecture specific memset() on RISC-V

2025-01-05T01:30:47Z

Build the architecture specific memset() if configured. Signed-off-by: Heinrich Schuchardt

examples: implement _start and syscall for RISC-V

2025-01-05T01:30:47Z

To build the API examples on RISC-V we need to implement _start and syscall for RISC-V. Signed-off-by: Heinrich Schuchardt

examples: make glue and demo code compatible with 64-bit

2024-11-14T16:51:07Z

Commit f9886bc60f42 ("Added arm64 assembly for examples/api crt0") added a 64-bit target for the examples but did not adjust the demo code to be 64-bit compatible. Change variable size for pointers. Use %p to print pointers. Signed-off-by: Heinrich Schuchardt

examples: adjust LOAD_ADDR on arm64

2024-11-14T16:51:07Z

Change the load address on arm64 such that it is compatible with the memory available on qemu_arm64_defconfig. Signed-off-by: Heinrich Schuchardt

u-boot.git/examples, branch next

treewide: prefer __func__ over __FUNCTION__ and __PRETTY_FUNCTION__

examples: Fix checking id parameter in thread_start

examples: fix building on arm32

examples: eliminate CONFIG_STANDALONE_LOAD_ADDR

examples/api: improve determination of LOAD_ADDR

examples: use QEMU compatible LOAD_ADDR on RISC-V

examples: use architecture specific memset() on RISC-V

examples: implement _start and syscall for RISC-V

examples: make glue and demo code compatible with 64-bit

examples: adjust LOAD_ADDR on arm64

treewide: prefer func over FUNCTION and __PRETTY_FUNCTION__