Re: [PATCH v2 3/4] mtd: rawnand: brcmnand: Default bcmbca parameter_page_big_endian to zero

2024-11-12 Thread Linus Walleij
On Wed, Nov 13, 2024 at 7:27 AM david regan wrote: > Set parameter_page_big_endian to zero for bcmbca > > Signed-off-by: david regan > Reviewed-by: William Zhang > Reviewed-by: Anand Gore Reviewed-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH v2] cmd: add a fetch utility

2024-11-12 Thread Ilias Apalodimas
On Wed, 13 Nov 2024 at 06:26, Caleb Connolly wrote: > > Add a small utility for displaying some information about U-Boot and the > hardware it's running on in a similar fashion to the popular neofetch > tool for Linux [1]. > > While the output is meant to be useful, it should also be pleasing to >

Re: [PATCH] mmc: don't print 'MMC:' if there are no MMC devices

2024-11-12 Thread Ilias Apalodimas
On Wed, 13 Nov 2024 at 07:30, Caleb Connolly wrote: > > It may be the case that MMC support is enabled even though the board > we're booting on doesn't have any MMC devices. Move the print over to > the print_mmc_devices() function where we can only print it if we > actually have MMC devices. > >

Re: [u-boot PATCH] fs: btrfs: hide 'Cannot lookup file' errors on 'load'

2024-11-12 Thread Dominique Martinet
Dominique Martinet wrote on Wed, Nov 06, 2024 at 09:56:42AM +0900: > Running commands such as 'load mmc 2:1 $addr $path' when path does not > exists historically do not print any error on filesystems such as ext4 > or fat. > Changing the root filesystem to btrfs would make existing boot script > pr

[PATCH] mmc: don't print 'MMC:' if there are no MMC devices

2024-11-12 Thread Caleb Connolly
It may be the case that MMC support is enabled even though the board we're booting on doesn't have any MMC devices. Move the print over to the print_mmc_devices() function where we can only print it if we actually have MMC devices. Signed-off-by: Caleb Connolly --- common/board_r.c | 1 -

Re: [PATCH v9 11/12] test: Correct regex string in test_spi

2024-11-12 Thread Love Kumar
On 12/11/24 7:43 pm, Simon Glass wrote: Use an 'r' string to avoid a warning: test/py/tests/test_spi.py:698: DeprecationWarning: invalid escape sequence '\s' Signed-off-by: Simon Glass --- (no changes since v2) Changes in v2: - Add new patch to correct a regex string in test_spi

Re: [PATCH] treewide: remove Qualcomm dt-binding headers that are available upstream

2024-11-12 Thread Sumit Garg
On Wed, 13 Nov 2024 at 10:06, Caleb Connolly wrote: > > Some dt-binding headers mask the upstream ones which can lead to build > failures, or worse: super weird bugs, if they get out of sync. > > Remove these headers so our devicetree and binding headers will both be > in sync with upstream. > > S

RE: [PATCH v1] imx: Fix critical thermal threshold

2024-11-12 Thread Peng Fan
Hi Francesco, > Subject: [PATCH v1] imx: Fix critical thermal threshold > > From: Francesco Dolcini > > Fix the critical thermal threshold for i.MX processors, this was changed > while moving the code from imx8m/imx9 directories into a shared > place. > > There is no need to keep the critical

[PATCH] dm: core: ofnode: safely fallback in ofnode_lookup_fdt

2024-11-12 Thread Caleb Connolly
Under some conditions it's possible to hit the null condition here like when running with OF_LIVE and using the ofnode API before initr_of_live() is called. There is very little null checking for this in the FDT framework, so returning null here can result in weird null pointer conditions. Instead

[PATCH] iommu: qcom-smmu: handle running in el2

2024-11-12 Thread Caleb Connolly
We only need to configure the SMMU when running in EL1. In EL2 the hypervisor isn't running so peripherals can just do DMA as they wish. Signed-off-by: Caleb Connolly --- drivers/iommu/qcom-hyp-smmu.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/iommu/qcom-hyp-smmu.c b/driv

[PATCH] fastboot: properly handle unknown partition type

2024-11-12 Thread Caleb Connolly
In getvar_partition_type() we attempt to find a filesystem driver for the partition (of the list of driver enabled in U-Boot), on failure we return the error to fastboot and completely bail out of the operation. However, this should not be a failure, instead we should just default to "raw". This a

[PATCH] mach-snapdragon: configure logging

2024-11-12 Thread Caleb Connolly
Set LOG_CATEGORY and pr_fmt. Also fix the time.h include. Signed-off-by: Caleb Connolly --- arch/arm/mach-snapdragon/board.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-snapdragon/board.c b/arch/arm/mach-snapdragon/board.c index 2ab2ceb51389..bbe9d3de763

[PATCH] iommu: qcom-smmu: allow SID 0

2024-11-12 Thread Caleb Connolly
It turns out this is a very real stream ID. Who woulda thought? Drop the 0 check on the SID, there's no reason for it to be there in the first place. Signed-off-by: Caleb Connolly --- drivers/iommu/qcom-hyp-smmu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu

[PATCH] button: gpio: handle broken controller

2024-11-12 Thread Caleb Connolly
Avoid crashing U-Boot when the GPIO controller for a button is disabled or failed to probe. We also need to check the priv data for each button since even if a button fails to probe it will still be polled by the core code. Signed-off-by: Caleb Connolly --- drivers/button/button-gpio.c | 9 +

Re: [PATCH] dm: button: support remapping phone keys

2024-11-12 Thread Caleb Connolly
Just bumping this again, any reason this can't be merged? Kind regards, On 14/07/2024 21:49, Caleb Connolly wrote: > We don't have audio support in U-Boot, but we do have boot menus. Add an > option to re-map the volume and power buttons to up/down/enter so that > in situations where these are th

[PATCH] button: qcom-pmic: add software debounce

2024-11-12 Thread Caleb Connolly
This helps with reliability on some platforms. We should probably also configure the hardware debounce timer eventually. Signed-off-by: Caleb Connolly --- drivers/button/button-qcom-pmic.c | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/drivers/button/button-q

[PATCH] fs: fat: allow FS and device to have mismatching sector sizes

2024-11-12 Thread Caleb Connolly
The Qualcomm Robotics RB1 and RB2 boards feature MMC storage provisioned with a 4k sector size GPT, with factory partitions formatted with filesystems using 512 byte sector sizes. Whilst certainly unusual, and really not ideal, this appears to work fine in practise. So demote this failure conditio

[PATCH v2] cmd: add a fetch utility

2024-11-12 Thread Caleb Connolly
Add a small utility for displaying some information about U-Boot and the hardware it's running on in a similar fashion to the popular neofetch tool for Linux [1]. While the output is meant to be useful, it should also be pleasing to look at and perhaps entertaining. The ufetch command aims to brin

Re: [PATCH RFC v1] Dockerfile: Have "sandbox" build with i386 toolchain not x86_64 toolchain

2024-11-12 Thread Tom Rini
On Sat, Nov 09, 2024 at 10:34:15AM -0700, Simon Glass wrote: > Hi Tom, > > On Tue, 5 Nov 2024 at 10:03, Simon Glass wrote: > > > > Hi Tom, > > > > On Tue, 5 Nov 2024 at 09:54, Tom Rini wrote: > > > > > > A long time ago, we had to use "i386" and "x86_64" toolchains for our > > > x86 platforms, d

Re: [PATCH 3/9] buildman: Support #include files in defconfigs

2024-11-12 Thread Tom Rini
On Fri, Nov 08, 2024 at 08:23:44AM -0700, Simon Glass wrote: > This is used by some boards in U-Boot and is a convenient way to deal > with common settings where using a Kconfig files is not desirable. > > Detect #include files and process them as if they were part of the > original file. > > Si

Re: [PATCH 8/9] buildman: Propose a format for extra boards

2024-11-12 Thread Tom Rini
On Fri, Nov 08, 2024 at 08:23:49AM -0700, Simon Glass wrote: > It has become more common to use config fragments to extend or adjust > the functionality of boards in U-Boot. > > Propose a format for how to deal with this. It is not implemented as > yet. > > Signed-off-by: Simon Glass I think t

Re: [PATCH v2 1/2] armv8: Fix get_sctlr() return type

2024-11-12 Thread Sam Protsenko
On Mon, Nov 11, 2024 at 8:48 AM Ilias Apalodimas wrote: > > On Thu, 7 Nov 2024 at 04:58, Sam Protsenko wrote: > > > > SCTLR_EL2 is a 64-bit register [1]. Return its value as long (64 bit) > > instead of int (32 bit) in get_sctlr() to make sure it's not trimmed. > > > > [1] > > https://developer.

Re: [PATCH] cmd: add a fetch utility

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 04:40:44PM -0800, Tony Dinh wrote: > Hi Tom, > > On Fri, Aug 9, 2024 at 3:41 PM Tom Rini wrote: > > > > On Fri, Aug 09, 2024 at 07:23:42PM +0200, Caleb Connolly wrote: > > > > > > > > > On 09/08/2024 08:18, Heinrich Schuchardt wrote: > > > > > > > > > > > > Am 8. August 20

Re: [PATCH 01/18] scripts: Add a script for building and booting QEMU

2024-11-12 Thread Tom Rini
On Wed, Nov 13, 2024 at 01:49:30AM +0100, Heinrich Schuchardt wrote: > Am 12. November 2024 14:58:54 MEZ schrieb Simon Glass : > >It is handy to be able to quickly build and boot a QEMU image for a > >particular architecture and distro. > > > >Add a script for this purpose. It supports only arm and

Re: [PATCH 01/18] scripts: Add a script for building and booting QEMU

2024-11-12 Thread Heinrich Schuchardt
Am 12. November 2024 14:58:54 MEZ schrieb Simon Glass : >It is handy to be able to quickly build and boot a QEMU image for a >particular architecture and distro. > >Add a script for this purpose. It supports only arm and x86 at present. >For distros it only supports Ubuntu. Both 32- and 64-bit buil

Re: [PATCH] cmd: add a fetch utility

2024-11-12 Thread Tony Dinh
Hi Tom, On Fri, Aug 9, 2024 at 3:41 PM Tom Rini wrote: > > On Fri, Aug 09, 2024 at 07:23:42PM +0200, Caleb Connolly wrote: > > > > > > On 09/08/2024 08:18, Heinrich Schuchardt wrote: > > > > > > > > > Am 8. August 2024 18:24:24 MESZ schrieb Caleb Connolly > > > : > > > > While U-Boot does a pret

Re: [PATCH 01/18] scripts: Add a script for building and booting QEMU

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 06:58:54AM -0700, Simon Glass wrote: > It is handy to be able to quickly build and boot a QEMU image for a > particular architecture and distro. > > Add a script for this purpose. It supports only arm and x86 at present. > For distros it only supports Ubuntu. Both 32- and

Re: [PATCH v3 7/9] docker: Install toolchains on arm64 host

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 07:11:03AM -0700, Simon Glass wrote: > Refactor the code to support downloading toolchains for arm64 as well as > x86_64 > > There doesn't seem to be an xtensa toolchain for arm64 at the same > location, so download that only on x86 > > Signed-off-by: Simon Glass Review

Re: [PATCH v3 3/9] docker: Support building for multiple architectures

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 04:08:17PM +0100, Heinrich Schuchardt wrote: > On 12.11.24 15:10, Simon Glass wrote: > > Add instructions on how to build the file for multiple architectures. > > Add a message indicating what is happening. > > > > Update the documentation as well. Drop the 'sudo' since the

Re: [PATCH v3 4/9] docker: Adjust packages for arm64

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 07:11:00AM -0700, Simon Glass wrote: > The package names are slightly different for arm64 and we don't seem to > have a linux-image-kvm package. Provide some extra ones for x86 > > Signed-off-by: Simon Glass Reviewed-by: Tom Rini -- Tom signature.asc Description: PG

Re: [PATCH 0/5] fs: ext4: implement opendir, readdir, closedir

2024-11-12 Thread Tom Rini
On Thu, Nov 07, 2024 at 10:47:38AM +0100, Heinrich Schuchardt wrote: > On 11/7/24 10:31, Michael Nazzareno Trimarchi wrote: > > Hi > > > > On Thu, Nov 7, 2024 at 10:27 AM Heinrich Schuchardt > > wrote: > > > > > > On 11/3/24 00:36, Michael Nazzareno Trimarchi wrote: > > > > Hi Tom > > > > > >

[PATCH] board: phytec: common: Introduce CONFIG_PHYTEC_K3_DDR_PATCH

2024-11-12 Thread Garrett Giordano
Introduce CONFIG_PHYTEC_K3_DDR_PATCH to make DDR timing patch code optional for PHYTEC K3 boards. This allows better control over which boards receive DDR timing patches, rather than compiling the code for all boards with K3_DDRSS enabled. Also enable the feature by default for PHYCORE_AM62X_R5.

Re: [PATCH v11 3/7] usb: onboard-hub: add support for Microchip USB5744

2024-11-12 Thread Marek Vasut
On 11/12/24 7:42 AM, Abbarapu, Venkatesh wrote: Hi, -Original Message- From: Marek Vasut Sent: Tuesday, November 12, 2024 11:28 AM To: Abbarapu, Venkatesh ; u-boot@lists.denx.de Cc: Simek, Michal ; fabrice.gasn...@foss.st.com; git (AMD-Xilinx) Subject: Re: [PATCH v11 3/7] usb: onboard

Re: [PATCH] Revert "efi_memory: do not add U-Boot memory to the memory map"

2024-11-12 Thread Tom Rini
On Tue, Nov 12, 2024 at 06:18:30AM -0700, Simon Glass wrote: > A bisect of Ubuntu 2022.04 boot-failure on qemu-x86_64 resulted in this > patch. I am not sure how to investigate it. > > The boot hangs at some point during booting of the install image, before > the Ubuntu logo appears. > > I will

Re: [RFC U-Boot Upstream] board: phytec: common: Introduce CONFIG_PHYTEC_K3_DDR_PATCH

2024-11-12 Thread Wadim Egorov
Hi Garrett, no need to tag as RFC. Otherwise, it looks good to me. Am 12.11.24 um 19:40 schrieb Garrett Giordano: Introduce CONFIG_PHYTEC_K3_DDR_PATCH to make DDR timing patch code optional for PHYTEC K3 boards. This allows better control over which boards receive DDR timing patches, rather tha

[PATCH 3/3] board: add support for LicheeRV Nano

2024-11-12 Thread Thomas Bonnefille
The LicheeRV Nano is a small SBC using the Sophgo SG2002 RISCV SoC. Signed-off-by: Thomas Bonnefille --- arch/riscv/Kconfig | 4 +++ board/sophgo/licheerv_nano/Kconfig | 28 board/sophgo/licheerv_nano/MAINTAINERS | 4 +++ board/sophgo/licheerv_nano/

[PATCH 0/3] Add support for LicheeRV Nano

2024-11-12 Thread Thomas Bonnefille
This patch series adds support in U-Boot for the Sophgo SG2002 RISCV SoC and one board using this SoC, the LicheeRV Nano. Signed-off-by: Thomas Bonnefille --- Thomas Bonnefille (3): doc: add LicheeRV Nano and SG2002 SoC riscv: dts: sophgo: add device tree for LicheeRV Nano board

Re: [PATCH] Revert "efi_memory: do not add U-Boot memory to the memory map"

2024-11-12 Thread Sughosh Ganu
On Tue, 12 Nov 2024 at 18:48, Simon Glass wrote: > > A bisect of Ubuntu 2022.04 boot-failure on qemu-x86_64 resulted in this > patch. I am not sure how to investigate it. > > The boot hangs at some point during booting of the install image, before > the Ubuntu logo appears. > > I will sent a serie

[RFC U-Boot Upstream] board: phytec: common: Introduce CONFIG_PHYTEC_K3_DDR_PATCH

2024-11-12 Thread Garrett Giordano
Introduce CONFIG_PHYTEC_K3_DDR_PATCH to make DDR timing patch code optional for PHYTEC K3 boards. This allows better control over which boards receive DDR timing patches, rather than compiling the code for all boards with K3_DDRSS enabled. Also enable the feature by default for PHYCORE_AM62X_R5.

Re: [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function()

2024-11-12 Thread Zixun LI
On Tue, Nov 12, 2024 at 4:59 PM Eugen Hristev wrote: > > > > On 11/12/24 17:57, Zixun LI wrote: > > Hello, > > > > > > On Tue, Nov 12, 2024 at 2:13 PM Eugen Hristev > > wrote: > >> > >> > >>> +static bool at91_get_port_pio(struct at91_port *at91_port, int offset) > >> > >> The name get_port_pio

Re: [PATCH v2 3/3] gpio: at91: Implement ops get_flags

2024-11-12 Thread Zixun LI
Hi, On Tue, Nov 12, 2024 at 2:27 PM Eugen Hristev wrote: > > Use clamp (!!) to turn this into a bool. > Should I also fix the existing function at91_get_port_output() ?

Re: [PATCH 2/3] gpio: at91: Implement ops set_flags

2024-11-12 Thread Zixun LI
Hi, On Tue, Nov 12, 2024 at 2:21 PM Eugen Hristev wrote: > > Does this change the current behavior? there is no set_flag ops > implemented, previously it would use a default that would just return > success regardless of the given flags parameters ? > Btw maybe ENOTSUPP ? > Currently without .se

Re: [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function()

2024-11-12 Thread Zixun LI
Hello, On Tue, Nov 12, 2024 at 2:13 PM Eugen Hristev wrote: > > > > +static bool at91_get_port_pio(struct at91_port *at91_port, int offset) > > The name get_port_pio is a bit confusing, can you rename it to something > more meaningful, like maybe is_periph_func or something ? How about at91_is_

[PATCH 2/3] riscv: dts: sophgo: add device tree for LicheeRV Nano

2024-11-12 Thread Thomas Bonnefille
Import a slightly modified version of the LicheeRV Nano and SG2002 device trees from the Linux Kernel. The current supported IPs are UART, MMC, Timer, PLIC and CLINT. Signed-off-by: Thomas Bonnefille --- arch/riscv/dts/Makefile | 1 + arch/riscv/dts/sg2002-licheerv-nano-b.dts

[PATCH 1/3] doc: add LicheeRV Nano and SG2002 SoC

2024-11-12 Thread Thomas Bonnefille
Provide a page describing the usage of U-Boot on the LicheeRV Nano and a description of the board. Signed-off-by: Thomas Bonnefille --- doc/board/sophgo/licheerv_nano.rst | 72 ++ 1 file changed, 72 insertions(+) diff --git a/doc/board/sophgo/licheerv_nano.rs

Using secondary UART for board initialization

2024-11-12 Thread Alexander Koch
Hi all, I need to write to (and read from) a UART during board initialization that is not the same UART the U-Boot serial console is running on. I'm using CONFIG_DM_SERIAL so I've extended my .dts to enable the additional UART (including pinmux registers). In my board init code I can find the ser

Re: EFI File renaming

2024-11-12 Thread Traut Manuel LCPF-CH
Hi Ilias, On Tue, Nov 12, 2024 at 03:46:48PM +0200, Ilias Apalodimas wrote: > Hello Manuel, > > On Tue, 12 Nov 2024 at 15:21, Traut Manuel LCPF-CH > wrote: > > > > Hi, > > > > systemd-boot counting logic requires [0] to be implemented. > > > > Is anybody already working on this? > > I am not a

[PATCH v1] imx: Fix critical thermal threshold

2024-11-12 Thread Francesco Dolcini
From: Francesco Dolcini Fix the critical thermal threshold for i.MX processors, this was changed while moving the code from imx8m/imx9 directories into a shared place. There is no need to keep the critical threshold 5 degrees less than the SoC maximum temperature threshold, what is actually goin

Re: [PATCH v4 5/8] sunxi: Move to bootstd

2024-11-12 Thread Andre Przywara
On Mon, 04 Nov 2024 16:29:20 +0100 Mark Kettenis wrote: Hi Mark, Simon, > > Date: Mon, 4 Nov 2024 13:34:29 + > > From: Andre Przywara > > > > On Sun, 03 Nov 2024 18:54:38 +0100 > > Mark Kettenis wrote: > > > > Hi Mark, > > > > > > Date: Sun, 3 Nov 2024 10:36:26 + > > > > From: And

[PATCH] configs: visionfive2: re-enable SPL_SYS_MMCSD_RAW_MODE

2024-11-12 Thread Andreas Schwab
To restore MMC boot, enable SPL_SYS_MMCSD_RAW_MODE and recover SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION and SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION. Fixes: 2a00d73d081 ("spl: mmc: Try to clean up raw-mode options") Signed-off-by: Andreas Schwab --- configs/starfive_visionfive2_defconfig | 3 +++ 1 fi

Re: [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function()

2024-11-12 Thread Eugen Hristev
On 11/12/24 18:17, Zixun LI wrote: > On Tue, Nov 12, 2024 at 4:59 PM Eugen Hristev > wrote: >> >> >> >> On 11/12/24 17:57, Zixun LI wrote: >>> Hello, >>> >>> >>> On Tue, Nov 12, 2024 at 2:13 PM Eugen Hristev >>> wrote: > +static bool at91_get_port_pio(struct at91_port *at91_por

Re: [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function()

2024-11-12 Thread Eugen Hristev
On 11/12/24 17:57, Zixun LI wrote: > Hello, > > > On Tue, Nov 12, 2024 at 2:13 PM Eugen Hristev > wrote: >> >> >>> +static bool at91_get_port_pio(struct at91_port *at91_port, int offset) >> >> The name get_port_pio is a bit confusing, can you rename it to something >> more meaningful, like m

[PATCH v2] Kconfig: describe NET, NO_NET, LWIP_DEBUG and LWIP_ASSERT

2024-11-12 Thread Jerome Forissier
Some Kconfig symbols introduced in commit 8cb330355bd5 ("net: introduce alternative implementation as net/lwip/") need a full description. The NET symbol needs one, too. Signed-off-by: Jerome Forissier Reviewed-by: Ilias Apalodimas --- Kconfig | 5 + net/lwip/Kconfig | 7 +++ 2

Re: EFI File renaming

2024-11-12 Thread Ilias Apalodimas
On Tue, 12 Nov 2024 at 16:55, Traut Manuel LCPF-CH wrote: > > > > > > systemd-boot counting logic requires [0] to be implemented. > > > > > > > > If not we plan to add the functionality in fs/fs.c and fs/fat - > > > > > correct? > > > > > > > > We don't have plans for it, but explaining any use c

Re: [PATCH v3 1/9] sandbox: efi_loader: Correct use of addresses as pointers

2024-11-12 Thread Simon Glass
Hi Heinrich, On Tue, 12 Nov 2024 at 07:28, Heinrich Schuchardt wrote: > > On 12.11.24 15:10, Simon Glass wrote: > > The cache-flush function is incorrect which causes a crash in the > > remoteproc tests with arm64. > > We should throw out all these sandbox virtual addresses where they are > not n

Re: [PATCH v3 3/9] docker: Support building for multiple architectures

2024-11-12 Thread Heinrich Schuchardt
On 12.11.24 15:10, Simon Glass wrote: Add instructions on how to build the file for multiple architectures. Add a message indicating what is happening. Update the documentation as well. Drop the 'sudo' since these should not be needed if Docker is correctly configured. Please, explain what you

Re: EFI File renaming

2024-11-12 Thread Traut Manuel LCPF-CH
> > > > systemd-boot counting logic requires [0] to be implemented. > > > > > > If not we plan to add the functionality in fs/fs.c and fs/fat - correct? > > > > > > We don't have plans for it, but explaining any use cases you have might > > > help > > > > systemd-boot is able to do bootcounting by

Re: [PATCH 4/5] mtd: nand: Update NAND manufacturer Ids

2024-11-12 Thread Eugen Hristev
On 11/12/24 15:57, Benedikt Spranger wrote: > On Tue, 12 Nov 2024 15:39:23 +0200 > Eugen Hristev wrote: > > Hi Eugen, >> On 10/18/24 11:30, Benedikt Spranger wrote: >>> Align manufacturer Ids with the Id list from Linux kernel v6.11. >>> While at it, sort the entries in alphabetical order. >>>

Re: [PATCH v3 1/9] sandbox: efi_loader: Correct use of addresses as pointers

2024-11-12 Thread Heinrich Schuchardt
On 12.11.24 15:28, Heinrich Schuchardt wrote: On 12.11.24 15:10, Simon Glass wrote: The cache-flush function is incorrect which causes a crash in the remoteproc tests with arm64. We should throw out all these sandbox virtual addresses where they are not needed. Just add the missing conversion

Re: [PATCH v3 1/9] sandbox: efi_loader: Correct use of addresses as pointers

2024-11-12 Thread Heinrich Schuchardt
On 12.11.24 15:10, Simon Glass wrote: The cache-flush function is incorrect which causes a crash in the remoteproc tests with arm64. We should throw out all these sandbox virtual addresses where they are not needed. Just add the missing conversion to drivers/remoteproc/rproc-elf-loader.c. And

Re: EFI File renaming

2024-11-12 Thread Ilias Apalodimas
On Tue, 12 Nov 2024 at 16:22, Traut Manuel LCPF-CH wrote: > > Hi Ilias, > > On Tue, Nov 12, 2024 at 03:46:48PM +0200, Ilias Apalodimas wrote: > > Hello Manuel, > > > > On Tue, 12 Nov 2024 at 15:21, Traut Manuel LCPF-CH > > wrote: > > > > > > Hi, > > > > > > systemd-boot counting logic requires [

Re: EFI File renaming

2024-11-12 Thread Traut Manuel LCPF-CH
Hello Heinrich, > The file system layer in fs/fat/fat_write.c does not support renaming, yet. > > You would have to start your contributions there. thanks - so the rough roadmap in my head seems to be fine. Manuel

Re: [Uboot-stm32] [PATCH 2/2] ARM: stm32: Deduplicate DH STM32MP1xx DHSOM defconfigs

2024-11-12 Thread Patrick DELAUNAY
On 11/12/24 12:49, Patrick DELAUNAY wrote: Hi, On 10/27/24 02:03, Marek Vasut wrote: Deduplicate defconfigs for all DH STM32MP1xx DHSOM systems by factoring out the common parts into generic stm32mp_dhsom.config and including those using the #include preprocessor macro in the current set of

Re: [PATCH] ARM: dts: stm32: Drop duplicate pinmux on DH STM32 DHCOM

2024-11-12 Thread Patrick DELAUNAY
On 11/12/24 12:33, Patrick DELAUNAY wrote: Hi, On 10/21/24 21:44, Marek Vasut wrote: The ethernet0_rmii_pins_a pinmux change has no effect on any DHSOM based hardware. The mco2_pins_a and mco2_sleep_pins_a are both part of stm32mp15-pinctrl.dtsi . Drop both pinmux changes. Signed-off-by: Mar

Re: [PATCH] ARM: dts: stm32: Drop remnants of upstream DT switch on DH STM32 DHSOM

2024-11-12 Thread Patrick DELAUNAY
On 11/12/24 12:29, Patrick DELAUNAY wrote: Hi, On 10/21/24 21:34, Marek Vasut wrote: Remove unused local DT copies after the OF_UPSTREAM conversion. Fixes: cccb29fc1270 ("ARM: dts: stm32: Switch to using upstream DT on DH STM32 DHSOM") Reported-by: Patrick Delaunay Signed-off-by: Marek Va

Re: [PATCH 1/2] ARM: stm32: Deduplicate DH STM32MP15xx DHSOM defconfigs

2024-11-12 Thread Patrick DELAUNAY
On 11/12/24 12:48, Patrick DELAUNAY wrote: Hi, On 10/27/24 02:03, Marek Vasut wrote: Deduplicate defconfigs for all DH STM32MP15xx DHSOM systems by factoring out the common parts into generic stm32mp15_dhsom.config and including those using the #include preprocessor macro in the current set

Re: [PATCH] ARM: stm32: Add optional manufacturing environment to DH STM32MP15xx DHSOM

2024-11-12 Thread Patrick DELAUNAY
On 11/12/24 12:23, Patrick DELAUNAY wrote: Hi, On 11/6/24 20:04, Marek Vasut wrote: Add manufacturing environment into STM32MP15xx DH electronics DHSOM configuration. This environment is part of every board build, but only takes effect on systems booted with the dh,stm32mp15xx-dhcor-testbench

[PATCH v9 12/12] CI: Allow running tests on sjg lab

2024-11-12 Thread Simon Glass
Add a way to run tests on a real hardware lab. This is in the very early experimental stages. There are only 23 boards and 3 of those are broken! (bob, ff3399, samus). A fourth fails due to problems with the TPM tests. To try this, assuming you have gitlab access, set SJG_LAB=1, e.g.: git push

[PATCH v9 11/12] test: Correct regex string in test_spi

2024-11-12 Thread Simon Glass
Use an 'r' string to avoid a warning: test/py/tests/test_spi.py:698: DeprecationWarning: invalid escape sequence '\s' Signed-off-by: Simon Glass --- (no changes since v2) Changes in v2: - Add new patch to correct a regex string in test_spi test/py/tests/test_spi.py | 2 +- 1 file chan

[PATCH v9 10/12] test: Support testing with two board-builds

2024-11-12 Thread Simon Glass
The Beagleplay board uses an SoC from the TI K3 family. This has both a Cortex-R core and a Cortex-A core and the R core needs to come up before the A core. In both cases we have U-Boot SPL then U-Boot proper being used. In practice this means we need two entirely separate builds to produce an ima

[PATCH v9 09/12] test: Add a section for closing the connection

2024-11-12 Thread Simon Glass
This can take a while and involve multiple steps (e.g. turning the board back off). Add a section for it and show the output. Signed-off-by: Simon Glass Reviewed-by: Tom Rini --- (no changes since v1) test/py/u_boot_console_base.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) di

[PATCH v9 08/12] test: Try to shut down the lab console gracefully

2024-11-12 Thread Simon Glass
Send the Labgrid quit characters to ask it to exit gracefully. This typically allows it to power off the board being used. Only do this when labgrid is being used (detected with an env var). If that doesn't work, try the less graceful approach. The normal approach for pytest is to simply kill the

[PATCH v9 07/12] test: Avoid double echo when starting up

2024-11-12 Thread Simon Glass
There is a very annoying bug at present where the terminal echos part of the first command sent to the board. This happens because the terminal is still set to echo for a period until Labgrid starts up and can change this. Fix this by disabling echo (and other terminal features) as soon as the spa

[PATCH v9 06/12] test: Improve handling of sending commands

2024-11-12 Thread Simon Glass
We expect commands to be echoed and this should happen quite quickly, since U-Boot is sitting at the prompt waiting for a command. Reduce the timeout for this situation. Try to produce a more useful error message when something goes wrong. Also handle the case where the connection has gone away si

[PATCH v9 05/12] test: Introduce lab mode

2024-11-12 Thread Simon Glass
There is quite a bit of code in pytest to try to start up U-Boot on a board, with timeouts, expects, etc. This is tedious to maintain and is peripheral to the test system's purpose. It seems better to put this logic in the lab itself, where is can provide such support. With Labgrid we can use the

[PATCH v9 02/12] test: Release board after tests complete

2024-11-12 Thread Simon Glass
When a board is finished with, the lab may want to power it off, or perform some other function. Add a new script which is called when tests are complete. Reviewed-by: Tom Rini Signed-off-by: Simon Glass --- (no changes since v1) test/py/u_boot_console_exec_attach.py | 10 ++ 1 file c

[PATCH v9 04/12] test: Introduce the concept of a role

2024-11-12 Thread Simon Glass
In Labgrid there is the concept of a 'role', which is similar to the U-Boot board ID in U-Boot's pytest subsystem. The role indicates both the target and information about the U-Boot build to use. It can also provide any amount of other configuration. The information is obtained using the 'labgrid

[PATCH v9 03/12] test: Allow connecting to a running board

2024-11-12 Thread Simon Glass
Sometimes we know that the board is already running the right software, so provide an option to allow running of tests directly, without first resetting the board. This saves time when re-running a test where only the Python code is changing. Note that this feature is open to errors, since the us

[PATCH v9 01/12] test: Allow signaling that U-Boot is ready

2024-11-12 Thread Simon Glass
When Labgrid is used, it can get U-Boot ready for running tests. It prints a message when it has done so. Add logic to detect this message and accept it. Note that this does not change pytest, which still (also) looks for the U-Boot banner. This change merely makes it possible for pytest to belie

[PATCH v9 00/12] labgrid: Provide an integration with Labgrid

2024-11-12 Thread Simon Glass
Labgrid provides access to a hardware lab in an automated way. It is possible to boot U-Boot on boards in the lab without physically touching them. It relies on relays, USB UARTs and SD muxes, among other things. By way of background, about 4 years ago I wrong a thing called Labman[1] which allowe

[PATCH v3 9/9] WIP: CI: Update for arm64

2024-11-12 Thread Simon Glass
Do not apply. This is an unfinished attempt to update gitlab to run on an arm64 host. For now it just adjusts grub and selects the multiarch image Signed-off-by: Simon Glass --- (no changes since v1) .gitlab-ci.yml | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git

[PATCH v3 8/9] CI: Add platform variable

2024-11-12 Thread Simon Glass
Add a list of possible platforms that can be used by gitlab runners. Signed-off-by: Simon Glass Reviewed-by: Tom Rini --- Changes in v3: - Drop patches which remove grub and tracing for arm64 .gitlab-ci.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml in

[PATCH v3 7/9] docker: Install toolchains on arm64 host

2024-11-12 Thread Simon Glass
Refactor the code to support downloading toolchains for arm64 as well as x86_64 There doesn't seem to be an xtensa toolchain for arm64 at the same location, so download that only on x86 Signed-off-by: Simon Glass --- Changes in v3: - Add patch to install toolchains on arm64 host tools/docker/

[PATCH v3 6/9] docker: Fix LegacyKeyValueFormat warning with PYTHONPATH

2024-11-12 Thread Simon Glass
Fix a warning due to the syntax used for PYTHONPATH: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 304) Signed-off-by: Simon Glass Reviewed-by: Heinrich Schuchardt Reviewed-by: Tom Rini --- (no changes since v1) tools/docker/Doc

[PATCH v3 5/9] docker: Drop coreboot for arm64

2024-11-12 Thread Simon Glass
This isn't needed for sandbox builds and coreboot isn't much used on arm64, nor does U-Boot have a build that supports running from coreboot on any ARM target. So drop it. Signed-off-by: Simon Glass Reviewed-by: Tom Rini --- (no changes since v1) tools/docker/Dockerfile | 6 -- 1 file ch

[PATCH v3 4/9] docker: Adjust packages for arm64

2024-11-12 Thread Simon Glass
The package names are slightly different for arm64 and we don't seem to have a linux-image-kvm package. Provide some extra ones for x86 Signed-off-by: Simon Glass --- Changes in v3: - Use grub-efi and linux-image-generic for both archs Changes in v2: - Swap order so that amd64 is the exception

[PATCH v3 2/9] test: Adjust print_ut test to use unsigned char

2024-11-12 Thread Simon Glass
Since char is unsigned on arm64, this test currently fails. It seems better to use unsigned anyway, since 0xff is written into the string at the start. Update the terminator-assert to use a character instead of a byte. Signed-off-by: Simon Glass Reviewed-by: Heinrich Schuchardt --- (no changes

[PATCH v3 3/9] docker: Support building for multiple architectures

2024-11-12 Thread Simon Glass
Add instructions on how to build the file for multiple architectures. Add a message indicating what is happening. Update the documentation as well. Drop the 'sudo' since these should not be needed if Docker is correctly configured. Signed-off-by: Simon Glass --- Changes in v3: - Move ARGs to th

[PATCH v3 1/9] sandbox: efi_loader: Correct use of addresses as pointers

2024-11-12 Thread Simon Glass
The cache-flush function is incorrect which causes a crash in the remoteproc tests with arm64. Fix both problems by using map_sysmem() to convert an address to a pointer and map_to_sysmem() to convert a pointer to an address. Also update the image-loader's cache-flushing logic. Signed-off-by: Si

[PATCH v3 0/9] CI: Set up for an arm64 runner

2024-11-12 Thread Simon Glass
All gitlab runners are currently amd64 machines. This series attempts to create a docker image which can also support arm64 so that sandbox tests can be run on it. The TARGET_... environment variables for grub could perhaps be adjusted, using the new variables, but I have not done that for now. C

Re: EFI File renaming

2024-11-12 Thread Heinrich Schuchardt
On 12.11.24 14:46, Ilias Apalodimas wrote: Hello Manuel, On Tue, 12 Nov 2024 at 15:21, Traut Manuel LCPF-CH wrote: Hi, systemd-boot counting logic requires [0] to be implemented. Is anybody already working on this? I am not aware of any patches If not we plan to add the functionality i

[PATCH 17/18] x86: Use the same GDT when jumping to long mode

2024-11-12 Thread Simon Glass
Make use the existing GDT which now includes entries for 64-bit code. Leave the interrupt descriptors alone. They can be tidied up once U-Boot starts up. With this, kvm mode works with QEMU. Signed-off-by: Simon Glass Fixes: https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/31 --- ar

Re: [PATCH v3 12/15] efi_loader: efi_net: add EFI_HTTP_PROTOCOL

2024-11-12 Thread Heinrich Schuchardt
On 11.11.24 22:09, Adriano Cordova wrote: Add an EFI HTTP driver. This commit implements the EFI_HTTP_PROTOCOL and the EFI_HTTP_SERVICE_BINDING_PROTOCOL. The latter is attached to the handle of th efi network device. This is the same handle where snp, pxe, and ipconfig are attached to. Signed-of

[PATCH 18/18] x86: Use a simple jump into long mode

2024-11-12 Thread Simon Glass
With the 64-bit descriptor we can use a jump instruction, rather than pushing things on the stack. Since the processor is in 64-bit mode by this point, pop a 64-bit value from the stack, containing the target address. This simplifies the code slightly, in particular its use of the stack. Signed-

[PATCH 13/18] x86: Drop the message about features missing in 64-bit

2024-11-12 Thread Simon Glass
This functions normally and has done for a while, so drop this scary message. Signed-off-by: Simon Glass --- arch/x86/lib/spl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/lib/spl.c b/arch/x86/lib/spl.c index 2586a81093b..715c8cdc3ac 100644 --- a/arch/x86/lib/sp

[PATCH 16/18] x86: Disable paging before changing to long mode

2024-11-12 Thread Simon Glass
This is required as part of the procedure. The existing code works because it changes the GDT at the same time, but this makes kvm unhappy. Update the algorithm to disable and then re-enable paging. Signed-off-by: Simon Glass --- arch/x86/cpu/i386/call64.S | 8 +++- 1 file changed, 7 inser

[PATCH 15/18] x86: Tidy up the GDT size in start/16.S

2024-11-12 Thread Simon Glass
Use a symbol to select the size of the GDT, rather than hard-coding a value. This matches how it is done in start64 Signed-off-by: Simon Glass --- arch/x86/cpu/start.S | 4 +++- arch/x86/cpu/start16.S | 3 ++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/arch/x86/cpu/start.S

[PATCH 14/18] x86: Include stdbool.h in interrupt header

2024-11-12 Thread Simon Glass
This makes use of a 'bool' type, so include the required header. Signed-off-by: Simon Glass --- arch/x86/include/asm/interrupt.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/include/asm/interrupt.h b/arch/x86/include/asm/interrupt.h index e23fb2c8e72..c689fc23d08 100644 --- a/ar

[PATCH 12/18] x86: spl: Drop duplicate CPU init

2024-11-12 Thread Simon Glass
x86_cpu_init_f() is called by arch_cpu_init() a few lines below this code. Drop the duplicate call. Signed-off-by: Simon Glass --- arch/x86/lib/spl.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/lib/spl.c b/arch/x86/lib/spl.c index f761fbc8bc3..2586a81093b 100644 --- a/arch/x86

[PATCH 10/18] x86: Add 64-bit entries to the GDT

2024-11-12 Thread Simon Glass
At present it is not possible to execution 64-bit code without installing an entire new Global Descriptor Table. This is inconvenient since kvm does not seem to like switching into long mode with a new table. It isn't actually necessary, since we can just extend the existing table. Add some new en

  1   2   >