July 2023 - U-Boot

[PATCH 00/12] binman: Simple templating feature and mkimage conversion
by Simon Glass 07 Jul '23

07 Jul '23

This series converts the mkimage entry type to be a section, i.e. based on the entry_Section class. This makes it more consistent in its behaviour, e.g. allowing symbol writing and expanded entries. A simple templating feature is also introduced, to reduce duplication when a set of entries must be used in multiple images. The templating implementation works by appending the template nodes to the target node. It is probably better to insert the template nodes before any subnodes in the target, so that the ordering of nodes in the template is preserved. But that involves rewriting the Fdt classs, since it can currently only add a subnode after the existing ones. This is left for later. Marek Vasut (1): binman: Convert mkimage to Entry_section Simon Glass (11): binman: Init align_default in entry_Section binman: Use GetEntries() to obtain section contents binman: Read _multiple_data_files in the correct place binman: Allow disabling symbol writing stm32mp15: Avoid writing symbols in SPL binman: Provide a way to specific the fdt-list directly binman: Drop __bss_size variable in bss_data.c binman: Correct handling of zero bss size dtoc: Support copying the contents of a node into another dtoc: Allow inserting a list of nodes into another binman: Support simple templates arch/arm/dts/stm32mp15-u-boot.dtsi | 1 + tools/binman/binman.rst | 87 ++++++++++++++++++ tools/binman/control.py | 9 ++ tools/binman/elf_test.py | 5 ++ tools/binman/entries.rst | 6 ++ tools/binman/entry.py | 10 +-- tools/binman/etype/blob_phase.py | 5 ++ tools/binman/etype/fit.py | 9 ++ tools/binman/etype/mkimage.py | 79 ++++++++++------- tools/binman/etype/section.py | 22 ++--- tools/binman/etype/u_boot_spl_bss_pad.py | 2 +- tools/binman/etype/u_boot_tpl_bss_pad.py | 2 +- tools/binman/etype/u_boot_vpl_bss_pad.py | 2 +- tools/binman/ftest.py | 103 +++++++++++++++++++++- tools/binman/test/282_symbols_disable.dts | 25 ++++++ tools/binman/test/283_mkimage_special.dts | 24 +++++ tools/binman/test/284_fit_fdt_list.dts | 58 ++++++++++++ tools/binman/test/285_spl_expand.dts | 13 +++ tools/binman/test/286_entry_template.dts | 42 +++++++++ tools/binman/test/Makefile | 5 +- tools/binman/test/bss_data.c | 3 +- tools/binman/test/bss_data_zero.c | 16 ++++ tools/binman/test/bss_data_zero.lds | 15 ++++ tools/binman/test/embed_data.lds | 1 + tools/dtoc/fdt.py | 38 ++++++++ tools/dtoc/test/dtoc_test_simple.dts | 13 ++- tools/dtoc/test_fdt.py | 61 +++++++++++++ 27 files changed, 599 insertions(+), 57 deletions(-) create mode 100644 tools/binman/test/282_symbols_disable.dts create mode 100644 tools/binman/test/283_mkimage_special.dts create mode 100644 tools/binman/test/284_fit_fdt_list.dts create mode 100644 tools/binman/test/285_spl_expand.dts create mode 100644 tools/binman/test/286_entry_template.dts create mode 100644 tools/binman/test/bss_data_zero.c create mode 100644 tools/binman/test/bss_data_zero.lds -- 2.41.0.162.gfafddb0af9-goog

3 25

[PATCH] MAINTAINERS: correct at91 tree link
by Eugen Hristev 07 Jul '23

07 Jul '23

This was not done when the tree name was changed, fix it now. Signed-off-by: Eugen Hristev <eugen.hristev(a)collabora.com> --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index d724b6467344..2477923a5201 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -409,7 +409,7 @@ F: configs/uDPU_defconfig ARM MICROCHIP/ATMEL AT91 M: Eugen Hristev <eugen.hristev(a)microchip.com> S: Maintained -T: git https://source.denx.de/u-boot/custodians/u-boot-atmel.git +T: git https://source.denx.de/u-boot/custodians/u-boot-at91.git F: arch/arm/mach-at91/ F: board/atmel/ F: drivers/cpu/at91_cpu.c -- 2.34.1

2 1

[PATCH v2] efi_driver: fix duplicate efiblk#0 issue
by Masahisa Kojima 07 Jul '23

07 Jul '23

The devnum value of the blk_desc structure starts from 0, current efi_bl_create_block_device() function creates two "efiblk#0" devices for the cases that blk_find_max_devnum() returns -ENODEV and blk_find_max_devnum() returns 0(one device found in this case). This commit uses blk_next_free_devnum() instead of blk_find_max_devnum(). Signed-off-by: Masahisa Kojima <masahisa.kojima(a)linaro.org> --- Changes in v2: - uses blk_next_free_devnum() instead of blk_find_max_devnum() lib/efi_driver/efi_block_device.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/lib/efi_driver/efi_block_device.c b/lib/efi_driver/efi_block_device.c index add00eeebb..e3abd90275 100644 --- a/lib/efi_driver/efi_block_device.c +++ b/lib/efi_driver/efi_block_device.c @@ -124,10 +124,8 @@ efi_bl_create_block_device(efi_handle_t handle, void *interface) struct efi_block_io *io = interface; struct efi_blk_plat *plat; - devnum = blk_find_max_devnum(UCLASS_EFI_LOADER); - if (devnum == -ENODEV) - devnum = 0; - else if (devnum < 0) + devnum = blk_next_free_devnum(UCLASS_EFI_LOADER); + if (devnum < 0) return EFI_OUT_OF_RESOURCES; name = calloc(1, 18); /* strlen("efiblk#2147483648") + 1 */ -- 2.34.1

3 4

[PATCH v2 0/3] binman: Add support for externally encrypted blobs
by christian.taedcke-oss＠weidmueller.com 07 Jul '23

07 Jul '23

From: Christian Taedcke <christian.taedcke(a)weidmueller.com> This series adds the functionality to handle externally encrypted blobs to binman. It includes the functionality itself and the corresponding unit tests. The following block shows an example on how to use this functionality. In the device tree that is parsed by binman a new node encrypted is used: / { binman { filename = "u-boot.itb"; fit { ... images { some-bitstream { ... image_bitstream: blob-ext { filename = "bitstream.bin"; }; encrypted { content = <&image_bitstream>; algo = "aes256-gcm"; iv-filename = "bitstream.bin.iv"; key-filename = "bitstream.bin.key"; }; ... This results in an generated fit image containing the following information: \ { images { ... some-bitstream { ... data = [...] cipher { algo = "aes256-gcm"; key = <0x...>; iv = <0x...>; }; }; ... Changes in v2: - remove global /cipher node - replace key-name-hint with key-source property - add entry documentation - adapt tests for changed entry implementation Christian Taedcke (3): binman: Add support for externally encrypted blobs binman: Allow cipher node as special section binman: Add tests for etype encrypted tools/binman/etype/encrypted.py | 149 ++++++++++++++++++ tools/binman/etype/section.py | 2 +- tools/binman/ftest.py | 52 ++++++ .../binman/test/282_encrypted_no_content.dts | 15 ++ tools/binman/test/283_encrypted_no_algo.dts | 19 +++ .../test/284_encrypted_invalid_iv_file.dts | 23 +++ .../binman/test/285_encrypted_missing_key.dts | 28 ++++ .../binman/test/286_encrypted_key_source.dts | 29 ++++ tools/binman/test/287_encrypted_key_file.dts | 29 ++++ 9 files changed, 345 insertions(+), 1 deletion(-) create mode 100644 tools/binman/etype/encrypted.py create mode 100644 tools/binman/test/282_encrypted_no_content.dts create mode 100644 tools/binman/test/283_encrypted_no_algo.dts create mode 100644 tools/binman/test/284_encrypted_invalid_iv_file.dts create mode 100644 tools/binman/test/285_encrypted_missing_key.dts create mode 100644 tools/binman/test/286_encrypted_key_source.dts create mode 100644 tools/binman/test/287_encrypted_key_file.dts -- 2.34.1

2 6

[PATCH] binman: Support templating with multiple images
by Simon Glass 07 Jul '23

07 Jul '23

Allow a template to appear in the top level description when using multiple images. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- tools/binman/control.py | 5 ++-- tools/binman/ftest.py | 12 ++++++++++ tools/binman/test/287_template_multi.dts | 29 ++++++++++++++++++++++++ 3 files changed, 44 insertions(+), 2 deletions(-) create mode 100644 tools/binman/test/287_template_multi.dts diff --git a/tools/binman/control.py b/tools/binman/control.py index 0f98e9904fb1..b334fbc8ac8f 100644 --- a/tools/binman/control.py +++ b/tools/binman/control.py @@ -57,8 +57,9 @@ def _ReadImageDesc(binman_node, use_expanded): images = OrderedDict() if 'multiple-images' in binman_node.props: for node in binman_node.subnodes: - images[node.name] = Image(node.name, node, - use_expanded=use_expanded) + if 'template' not in node.name: + images[node.name] = Image(node.name, node, + use_expanded=use_expanded) else: images['image'] = Image('image', binman_node, use_expanded=use_expanded) return images diff --git a/tools/binman/ftest.py b/tools/binman/ftest.py index 389d3906371a..c783424c91da 100644 --- a/tools/binman/ftest.py +++ b/tools/binman/ftest.py @@ -6771,6 +6771,18 @@ fdt fdtmap Extract the devicetree blob from the fdtmap second = U_BOOT_DATA + b'#' + VGA_DATA + U_BOOT_DTB_DATA self.assertEqual(U_BOOT_IMG_DATA + first + second, data) + def testEntryTemplateBlobMulti(self): + """Test using a template with 'multiple-images' enabled""" + TestFunctional._MakeInputFile('my-blob.bin', b'blob') + TestFunctional._MakeInputFile('my-blob2.bin', b'other') + retcode = self._DoTestFile('287_template_multi.dts') + + self.assertEqual(0, retcode) + image = control.images['image'] + image_fname = tools.get_output_filename('my-image.bin') + data = tools.read_file(image_fname) + self.assertEqual(b'blob@@@@other', data) + if __name__ == "__main__": unittest.main() diff --git a/tools/binman/test/287_template_multi.dts b/tools/binman/test/287_template_multi.dts new file mode 100644 index 000000000000..15bd8701c671 --- /dev/null +++ b/tools/binman/test/287_template_multi.dts @@ -0,0 +1,29 @@ +// SPDX-License-Identifier: GPL-2.0+ + +/dts-v1/; + +/dts-v1/; +/ { + binman: binman { + multiple-images; + + my_template: template { + blob-ext@0 { + filename = "my-blob.bin"; + offset = <0>; + }; + blob-ext@8 { + offset = <8>; + }; + }; + + image { + pad-byte = <0x40>; + filename = "my-image.bin"; + insert-template = <&my_template>; + blob-ext@8 { + filename = "my-blob2.bin"; + }; + }; + }; +}; -- 2.41.0.390.g38632f3daf-goog

2 2

[RESEND PATCH v1 0/4] riscv: Initial support for Lichee PI 4A board
by Yixun Lan 07 Jul '23

07 Jul '23

Sipeed's Lichee PI 4A board is based on T-HEAD's TH1520 SoC which consists of quad core XuanTie C910 CPU, plus one C906 CPU and one E902 CPU. In this series, the UART, basic device tree, CPU, PLIC are enabled, making it capable of running in serial console mode. Please note that, we rely on pre shipped vendor u-boot which run in M-Mode to chain load this mainline u-boot either via eMMC storage or from tftp, thus the pinctrl and clock setting are not implemented in this series, which certainly can be improved later accordingly. Also the device tree is coming from kernel which is submitted by Jisheng Zhang in his patch V2 [1], it's still under review, so may change in the future. [1] https://lore.kernel.org/all/20230518184541.2627-1-jszhang@kernel.org Yixun Lan (4): riscv: t-head: licheepi4a: initial support added riscv: dts: t-head: Add basic device tree for Sipeed Lichee PI 4A board configs: th1520_lpi4a_defconfig: Add initial config doc: t-head: lpi4a: document Lichee PI 4A board arch/riscv/Kconfig | 5 + arch/riscv/dts/Makefile | 1 + arch/riscv/dts/th1520-lichee-module-4a.dtsi | 34 ++ arch/riscv/dts/th1520-lichee-pi-4a.dts | 32 ++ arch/riscv/dts/th1520.dtsi | 435 ++++++++++++++++++++ board/thead/th1520_lpi4a/Kconfig | 42 ++ board/thead/th1520_lpi4a/MAINTAINERS | 7 + board/thead/th1520_lpi4a/Makefile | 5 + board/thead/th1520_lpi4a/board.c | 14 + configs/th1520_lpi4a_defconfig | 82 ++++ doc/board/index.rst | 1 + doc/board/thead/index.rst | 9 + doc/board/thead/lpi4a.rst | 112 +++++ include/configs/th1520_lpi4a.h | 22 + 14 files changed, 801 insertions(+) create mode 100644 arch/riscv/dts/th1520-lichee-module-4a.dtsi create mode 100644 arch/riscv/dts/th1520-lichee-pi-4a.dts create mode 100644 arch/riscv/dts/th1520.dtsi create mode 100644 board/thead/th1520_lpi4a/Kconfig create mode 100644 board/thead/th1520_lpi4a/MAINTAINERS create mode 100644 board/thead/th1520_lpi4a/Makefile create mode 100644 board/thead/th1520_lpi4a/board.c create mode 100644 configs/th1520_lpi4a_defconfig create mode 100644 doc/board/thead/index.rst create mode 100644 doc/board/thead/lpi4a.rst create mode 100644 include/configs/th1520_lpi4a.h -- 2.40.0

4 22

[RFC] riscv: (visionfive2:) device tree binding for riscv_timer
by Torsten Duwe 07 Jul '23

07 Jul '23

Hi, following the existing device tree binding[1], here is a draft to use it in drivers/timer/riscv_timer.c. This would also fix the regression we see with commit 55171aedda8 ("dm: Emit the arch_cpu_init_dm() even only before relocation"), at least on the VisionFive2, as sketched out below. The device tree addition suits the Linux kernel dirver | riscv-timer: riscv_timer_init_dt: Registering clocksource cpuid [0] hartid [3] The of_match, along with the "timebase-frequency" property, provides a working timer (again) on the VF2. If this is the way to go, I'll turn this into a nicer patch series. Comments welcome! Torsten [1] linux/Documentation/devicetree/bindings/timer/riscv,timer.yaml --- arch/riscv/dts/jh7110.dtsi | 10 ++++++++++ configs/starfive_visionfive2_defconfig | 1 - drivers/timer/riscv_timer.c | 21 ++++++++++++++++++--- 3 files changed, 28 insertions(+), 4 deletions(-) diff --git a/drivers/timer/riscv_timer.c b/drivers/timer/riscv_timer.c index 3627ed79b8..03dda12f73 100644 --- a/drivers/timer/riscv_timer.c +++ b/drivers/timer/riscv_timer.c @@ -13,6 +13,7 @@ #include <common.h> #include <dm.h> #include <errno.h> +#include <fdt_support.h> #include <timer.h> #include <asm/csr.h> @@ -53,9 +54,18 @@ u64 notrace timer_early_get_count(void) static int riscv_timer_probe(struct udevice *dev) { struct timer_dev_priv *uc_priv = dev_get_uclass_priv(dev); - /* clock frequency was passed from the cpu driver as driver data */ - uc_priv->clock_rate = dev->driver_data; + u32 rate = dev->driver_data; + + if (!rate && gd->fdt_blob) { /* not called from CPU driver? */ + rate = fdt_getprop_u32_default(gd->fdt_blob, + "/cpus", "timebase-frequency", 0); + } + uc_priv->clock_rate = rate; + + /* timer uclass post_probe will later fail with -EINVAL. Hint at the cause! */ + if (!rate) + log_err("riscv_timer_probe with clock rate 0\n"); return 0; } @@ -64,10 +74,15 @@ static const struct timer_ops riscv_timer_ops = { .get_count = riscv_timer_get_count, }; +static const struct udevice_id riscv_timer_ids[] = { + { .compatible = "riscv,timer", }, + { } +}; + U_BOOT_DRIVER(riscv_timer) = { .name = "riscv_timer", .id = UCLASS_TIMER, + .of_match = of_match_ptr(riscv_timer_ids), .probe = riscv_timer_probe, .ops = &riscv_timer_ops, - .flags = DM_FLAG_PRE_RELOC, }; diff --git a/arch/riscv/dts/jh7110.dtsi b/arch/riscv/dts/jh7110.dtsi index c61730e8d1..9944f261b3 100644 --- a/arch/riscv/dts/jh7110.dtsi +++ b/arch/riscv/dts/jh7110.dtsi @@ -6,6 +6,7 @@ /dts-v1/; #include <dt-bindings/clock/starfive,jh7110-crg.h> #include <dt-bindings/reset/starfive,jh7110-crg.h> +#include <dt-bindings/interrupt-controller/riscv-hart.h> / { compatible = "starfive,jh7110"; @@ -204,6 +205,15 @@ }; }; + timer { + compatible = "riscv,timer"; + interrupts-extended = <&cpu0_intc HART_INT_S_TIMER>, + <&cpu1_intc HART_INT_S_TIMER>, + <&cpu2_intc HART_INT_S_TIMER>, + <&cpu3_intc HART_INT_S_TIMER>, + <&cpu4_intc HART_INT_S_TIMER>; + }; + osc: oscillator { compatible = "fixed-clock"; clock-output-names = "osc"; diff --git a/configs/starfive_visionfive2_defconfig b/configs/starfive_visionfive2_defconfig index 570a1f53a1..3a213b2601 100644 --- a/configs/starfive_visionfive2_defconfig +++ b/configs/starfive_visionfive2_defconfig @@ -102,4 +102,3 @@ CONFIG_PINCTRL_STARFIVE=y # CONFIG_RAM_SIFIVE is not set CONFIG_SYS_NS16550=y CONFIG_CADENCE_QSPI=y -CONFIG_TIMER_EARLY=y

1 0

[WIP] AXP313A(for Mango Pi MQ-Quad) support
by SASANO Takayoshi 07 Jul '23

07 Jul '23

Hello, Now I am trying to run U-Boot on Mango Pi MQ-Quad board. This board requires AXP313A driver and it is implemented. The diff is at GitHub, https://github.com/u-boot/u-boot/compare/master...jg1uaa:u-boot:mq Before submitting the diff, I want to know board configuration (configs/mangopi_mq_quad_defconfig and arch/arm/dts/sun50i-h616-mangopi-mq-quad.dts) is correct. At least OpenBSD for Allwinner H616 (RAMDISK kernel for installer) looks working like this: ---- U-Boot SPL 2023.07-rc6-gdc29b21fc2 (Jul 07 2023 - 20:19:06 +0900) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: lts-v2.8.4(debug): NOTICE: BL31: Built : 19:29:55, Apr 22 2023 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a08d048, model: MangoPi MQ-Quad INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot 2023.07-rc6-gdc29b21fc2 (Jul 07 2023 - 20:19:06 +0900) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: MangoPi MQ-Quad DRAM: 1 GiB Core: 45 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 18104 bytes read in 4 ms (4.3 MiB/s) No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 219050 bytes read in 12 ms (17.4 MiB/s) Booting /efi\boot\bootaa64.efi disks: sd0* >> OpenBSD/arm64 BOOTAA64 1.18 boot> boot bsd.rd cannot open sd0a:/etc/random.seed: No such file or directory booting sd0a:bsd.rd: 2858428+1077500+12724624+631888 [1705467+791232+168+26848]=0x1560490 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2023 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 7.3-current (RAMDISK) #56: Fri Jul 7 19:28:38 JST 2023 uaa@openbsd-current-vm.uaa.org.uk:/usr/src/sys/arch/arm64/compile/RAMDISK real mem = 1072021504 (1022MB) avail mem = 1000779776 (954MB) random: boothowto does not indicate good seed mainbus0 at root: MangoPi MQ-Quad psci0 at mainbus0: PSCI 1.1, SMCCC 1.2 cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4 cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,SHA2,SHA1,AES+PMULL,ASID16 efi0 at mainbus0: UEFI 2.10 efi0: Das U-Boot rev 0x20230700 smbios0 at efi0: SMBIOS 3.0 smbios0: vendor U-Boot version "2023.07-rc6-gdc29b21fc2" date 07/01/2023 smbios0: Unknown Unknown Product "secmon" at mainbus0 not configured "osc24M-clk" at mainbus0 not configured "pmu" at mainbus0 not configured agtimer0 at mainbus0: 24000 kHz simplebus0 at mainbus0: "soc" sxisyscon0 at simplebus0 sxiccmu0 at simplebus0 sxipio0 at simplebus0: 85 pins ampintc0 at simplebus0 nirq 192, ncpu 4: "interrupt-controller" sxiccmu1 at simplebus0 sxipio1 at simplebus0: 2 pins sxitwi0 at simplebus0 iic0 at sxitwi0 "x-powers,axp313a" at iic0 addr 0x36 not configured sxidog0 at simplebus0 sximmc0 at simplebus0 sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma com0 at simplebus0: dw16550 com0: console "usb" at simplebus0 not configured "phy" at simplebus0 not configured ehci0 at simplebus0 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 ohci0 at simplebus0: version 1.0 "rtc" at simplebus0 not configured gpio0 at sxipio0: 32 pins gpio1 at sxipio0: 32 pins gpio2 at sxipio0: 32 pins gpio3 at sxipio0: 32 pins gpio4 at sxipio0: 32 pins gpio5 at sxipio0: 32 pins gpio6 at sxipio0: 32 pins gpio7 at sxipio0: 32 pins gpio8 at sxipio0: 32 pins gpio9 at sxipio1: 32 pins usb1 at ohci0: USB revision 1.0 uhub1 at usb1 configuration 1 interface 0 "Generic OHCI root hub" rev 1.00/1.00 addr 1 "leds" at mainbus0 not configured "vcc5v" at mainbus0 not configured "vcc3v3" at mainbus0 not configured "binman" at mainbus0 not configured scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: <Apacer, SD16G, 0030> removable sd0: 14768MB, 512 bytes/sector, 30244864 sectors softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/arm64 7.3 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? ---- Any comments are welcomed. Regards, -- SASANO Takayoshi (JG1UAA) <uaa(a)mx5.nisiq.net>

1 0

[PATCH] zynqmp: config: Add proper dependency for CONFIG_DFU_MMC
by Ashok Reddy Soma 07 Jul '23

07 Jul '23

When CONFIG_CMD_MMC and CONFIG_MMC are disabled, still some compilation errors are seen as below due to unresolved symbols. drivers/dfu/dfu_mmc.o: in function `mmc_block_op': drivers/dfu/dfu_mmc.c:32: undefined reference to `find_mmc_device' drivers/dfu/dfu_mmc.c:54: undefined reference to `mmc_get_blk_desc' drivers/dfu/dfu_mmc.c:67: undefined reference to `mmc_get_blk_desc' drivers/dfu/dfu_mmc.c:70: undefined reference to `mmc_get_blk_desc' drivers/dfu/dfu_mmc.o: in function `dfu_fill_entity_mmc': drivers/dfu/dfu_mmc.c:369: undefined reference to `find_mmc_device' drivers/dfu/dfu_mmc.c:376: undefined reference to `mmc_init' drivers/dfu/dfu_mmc.c:403: undefined reference to `mmc_get_blk_desc' gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-ld.bfd: line 4: 31661 Segmentation fault (core dumped) $CC --sysroot=$LIBC --no-warn-rwx-segment "$@" Makefile:1760: recipe for target 'u-boot' failed make: *** [u-boot] Error 139 make: *** Deleting file 'u-boot' Add dependency of CONFIG_MMC for CONFIG_DFU_MMC config to fix the errors. Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma(a)amd.com> --- drivers/dfu/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/dfu/Kconfig b/drivers/dfu/Kconfig index 8d7f13dcb0..8e9e8eb4fe 100644 --- a/drivers/dfu/Kconfig +++ b/drivers/dfu/Kconfig @@ -35,6 +35,7 @@ config DFU_TIMEOUT config DFU_MMC bool "MMC back end for DFU" + depends on MMC help This option enables using DFU to read and write to MMC based storage. -- 2.17.1

2 1

[PATCH] lib: sparse: allocate blkcnt instead of arbitrary small number
by Mattijs Korpershoek 07 Jul '23

07 Jul '23

Commit 62649165cb02 ("lib: sparse: Make CHUNK_TYPE_RAW buffer aligned") fixed cache alignment for systems with a D-CACHE. However it introduced some performance regressions [1] on system flashing huge images, such as Android. On AM62x SK EVM, we also observe such performance penalty: Sending sparse 'super' 1/2 (768793 KB) OKAY [ 23.954s] Writing 'super' OKAY [ 75.926s] Sending sparse 'super' 2/2 (629819 KB) OKAY [ 19.641s] Writing 'super' OKAY [ 62.849s] Finished. Total time: 182.474s The reason for this is that we use an arbitrary small buffer (info->blksz * 100) for transferring. Fix it by using a bigger buffer (info->blksz * blkcnt) as suggested in the original's patch review [2]. With this patch, performance impact is mitigated: Sending sparse 'super' 1/2 (768793 KB) OKAY [ 24.006s] Writing 'super' OKAY [ 15.920s] Sending sparse 'super' 2/2 (629819 KB) OKAY [ 19.651s] Writing 'super' OKAY [ 14.665s] Finished. Total time: 74.346s [1] https://lore.kernel.org/r/20221118121323.4009193-1-gary.bisson@boundarydevi… [2] https://lore.kernel.org/r/all/43e4c17c-4483-ec8e-f843-9b4c5569bd18@seco.com/ Fixes: 62649165cb02 ("lib: sparse: Make CHUNK_TYPE_RAW buffer aligned") Signed-off-by: Mattijs Korpershoek <mkorpershoek(a)baylibre.com> --- lib/image-sparse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/image-sparse.c b/lib/image-sparse.c index 5ec0f94ab3eb..25aed0604192 100644 --- a/lib/image-sparse.c +++ b/lib/image-sparse.c @@ -55,7 +55,7 @@ static lbaint_t write_sparse_chunk_raw(struct sparse_storage *info, void *data, char *response) { - lbaint_t n = blkcnt, write_blks, blks = 0, aligned_buf_blks = 100; + lbaint_t n = blkcnt, write_blks, blks = 0, aligned_buf_blks = blkcnt; uint32_t *aligned_buf = NULL; if (CONFIG_IS_ENABLED(SYS_DCACHE_OFF)) { --- base-commit: 2f4664f5c3edc55b18d8906f256a4c8e303243c0 change-id: 20230616-sparse-flash-fix-9c2852aa8d16 Best regards, -- Mattijs Korpershoek <mkorpershoek(a)baylibre.com>

3 5