On Mon, Sep 16, 2024 at 5:41 PM Simon Glass wrote:
>
> Hi Patrick,
>
> On Thu, 12 Sept 2024 at 00:23, Patrick Rudolph
> wrote:
> >
> > On Thu, Sep 12, 2024 at 2:58 AM Simon Glass wrote:
> > >
> > > Hi Patrick,
> > >
> > > On Wed, 11 Sept 2024 at 00:26, Patrick Rudolph
> > > wrote:
> > > >
> > >
If 0 is passed to the 'bytes' parameter in the ubi_start_update(),
there is no need to call the ubi_more_update_data(). Otherwise,
there will be a double-free of 'vol->upd_buf'.
Also check that the ubi_start_update() was called before calling
the ubi_more_update_data().
Signed-off-by: Martin Kurb
Signed-off-by: Martin Kurbanov
---
cmd/ubi.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/cmd/ubi.c b/cmd/ubi.c
index 151afb9803..23b6211f6c 100644
--- a/cmd/ubi.c
+++ b/cmd/ubi.c
@@ -249,7 +249,7 @@ static int ubi_create_vol(char *volume, int64_t size, int
dy
If 0 is passed to the 'bytes' parameter in the ubi_start_update(),
there is no need to call the ubi_more_update_data(). Otherwise,
there will be a double-free of 'vol->upd_buf'.
Also check that the ubi_start_update() was called before calling
the ubi_more_update_data().
Martin Kurbanov (2):
cmd
Hi Raymond,
This looks correct, but as we discussed please drop this and use the
internal U-Boot hashing for now.
I still think we should enable mbedTLS hashing in the future, since we
can use new hash algorithms with minimal coding, but integrating this
with the existing U-Boot hardware offloadin
Several Enclustra devices store MAC address in a secure eeprom device. In
most cases this is the atsha204a (alternatively DS28). The atsha204a device
is preconfigured accordingly. Reading then is based on u-boot's atsha204a
driver. Add such support for Enclustra's AA1 SoMs.
Signed-off-by: Lothar R
Provide additional uboot.env text environment files meant as a generic
demo. The default environment uses a uboot.env. The default environment
works somehow. This environment provides better support but only shows
one possible approach used in the Enclustra reference design setups.
Signed-off-by:
Add support to boot Enclustra SoMs from MMC, SD or QSPI flash.
Signed-off-by: Lothar Rubusch
---
board/enclustra/bootscripts/qspi-aa1.cmd | 12
board/enclustra/bootscripts/sd-aa1.cmd | 10 ++
2 files changed, 22 insertions(+)
create mode 100644 board/enclustra/bootscripts
Introduce initial support for the Enclustra SoMs:
- Mercury AA1
Cover general board files for SD/MMC and QSPI boot modes. Integrate the
boards to kconfig. All build variants will depend on Quartus handoff
files, thus they depend on the particular Quartus design. The approach is
covered in the acc
Add command files for boot scripts and initial boot environment.
Signed-off-by: Andreas Buerkler
Signed-off-by: Lothar Rubusch
---
include/configs/socfpga_mercury_aa1.h | 35 +++
1 file changed, 35 insertions(+)
diff --git a/include/configs/socfpga_mercury_aa1.h
b/incl
Introduce device-tree files for Enclustra Intel AA1 SoMs and related
support.
- Mercury AA1
The setup depends on a selected boot mode. Various fragments for SD/MMC
and QSPI flash boot are provided.
In combination, the following Enclustra carrier boards are supported:
- ST1
- PE1
- PE3
Signed-o
Start documentation section for Enclustra. Cover Enclustra Intel SoMs and
related carrier board setups.
- Mercury AA1 (Arria10)
Signed-off-by: Lothar Rubusch
---
doc/board/enclustra/index.rst | 9 ++
doc/board/enclustra/mercury-aa1.rst | 207
doc/board/index
Introduce the support for three variants of Enclustra's Intel Mercury AA1 (with
Intel Arria10) SoMs and additional configs. This is supposed to be the first
step to upstream several of Enclustras SoC FPGA Modules. There are still things
to be modified. So, this is supposed to start the discussion a
Hi Chris,
Please update the subject with something like "Enable the VO PD before
driver access",
and the commit message for the change reason is enough.
and the config is more soc level, I think you can add this to
arch_cpu_init() for we don't have a power domain driver.
On 2024/9/17 05:01
> Subject: Re: [PATCH 21/21] imx93_evk: Enable M.2 VPCIe_3V3 and
> deassert SD3_nRST
>
> On Tue, Sep 17, 2024 at 9:21 PM Peng Fan
> wrote:
>
> > The linux changes still in downstream as below:
> > /*
> > * For this spi-nor on M.2 card, need first enable the VPCIe_3.3v.
> >
On Tue, Sep 17, 2024 at 9:21 PM Peng Fan wrote:
> The linux changes still in downstream as below:
> /*
> * For this spi-nor on M.2 card, need first enable the VPCIe_3.3v.
> * Note, VPCIe_3.3v need about 1.74ms to change from 0v to 3.3v.
> * U-boot already enable
Hi Fabio,
> Subject: Re: [PATCH 21/21] imx93_evk: Enable M.2 VPCIe_3V3 and
> deassert SD3_nRST
>
> Hi Peng,
>
> On Mon, Sep 16, 2024 at 11:31 PM Peng Fan (OSS)
> wrote:
>
> > + /* Enable EXT1_PWREN for PCIE_3.3V */
> > + ret = dm_gpio_lookup_name("gpio@22_13", &desc);
> > + i
Hi Peng,
On Mon, Sep 16, 2024 at 11:31 PM Peng Fan (OSS) wrote:
> + /* Enable EXT1_PWREN for PCIE_3.3V */
> + ret = dm_gpio_lookup_name("gpio@22_13", &desc);
> + if (ret)
> + return;
> +
> + ret = dm_gpio_request(&desc, "EXT1_PWREN");
> + if (ret)
> +
On Thu, Sep 12, 2024 at 04:50:41PM +0100, Oliver Gaskell via B4 Relay wrote:
> ADSP-SC5xx is a series of ARM-based DSPs.
> This comprises the armv7 based SC57x, SC58x and SC594 series, and the
> armv8 based SC598.
>
> This patch series includes configurations, init code, and minimal DTs
> to enab
On Mon, Sep 02, 2024 at 08:49:17PM +0200, Tomas Paukrt wrote:
> The mmc erase command currently requires blk# and cnt parameters
> which can be obtained using the part start and part size commands
> if the entire partition needs to be erased.
>
> Simplify the use of the mmc erase command by allow
On Fri, 06 Sep 2024 19:12:23 +0200, Marek Vasut wrote:
> The OSD command calls functions from video_osd-uclass.o ,
> which is built only when CONFIG_OSD is enabled. Add the
> missing dependency into Kconfig.
>
>
Applied to u-boot/next, thanks!
--
Tom
On Mon, 02 Sep 2024 15:37:09 +0200, Marek Vasut wrote:
> The mmc speed command configuration option keeps showing up in
> Kconfig directly in 'Command line interface'. Move MMC_SPEED_MODE_SET
> under CMD_MMC to make it show up alongside the MMC command.
>
>
Applied to u-boot/next, thanks!
--
On Wed, 04 Sep 2024 10:41:03 +0800, Jim Liu wrote:
> Modify npcm8xx new boot design.
> Correct memory setting and set gpio default value.
>
> Jim Liu (2):
> board: arbel: correct the dram bank size
> configs: arbel_evb: change env offset and boot address
>
> [...]
Applied to u-boot/next, th
On Fri, 30 Aug 2024 15:23:34 +0800, Chia-Wei Wang wrote:
> Aspeed AST27xx SoCs integrate the CPTRA 1.0 secure IP, which
> export a SHA accelerator interface for SoC to use.
>
> Note that CPTRA 1.0 supports only SHA384 and SHA512 and this
> patch is verified by the 'hash test sha384/sha512' comman
On Tue, Sep 17, 2024 at 05:52:09AM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 16 Sept 2024 at 18:34, Tom Rini wrote:
> >
> > On Mon, Sep 16, 2024 at 05:42:42PM +0200, Simon Glass wrote:
> > > Hi Heinrich,
> > >
> > > On Thu, 12 Sept 2024 at 09:09, Heinrich Schuchardt
> > > wrote:
> > > >
>
The buck variable is zero based, i.e. buck=0 match BUCK1 in datasheet.
Remove any buck + 1 calculation to be more consistent in usage of the
buck variable across the different RK8xx variants in the driver.
Signed-off-by: Jonas Karlman
---
v2:
- Move buck + 1 related changes into a separate patch
Wrong POWER_EN reg is used to get and set enabled state for the RK806
buck 4 and 8 regulators, also wrong POWER_SLP_EN0 bit is used for
suspend state for the RK806 buck 1-8 regulators.
Fix this by not adding one to the zero based buck variable.
Fixes: f172575d92cd ("power: rk8xx: add support for
On Tue, Sep 17, 2024 at 2:19 AM William Zhang
wrote:
> > > What SoC do you use?
> >
> > This is on BCM6846.
> >
> 6846 will work. Let me know if it still does not work after dts fix.
Yes it work just fine! I dropped
CONFIG_SYS_NAND_ONFI_DETECTION and then it detects
and works fine on Genexis XG
On Mon, Aug 19, 2024 at 11:11:36AM -0600, Tom Rini wrote:
> On Sun, Aug 18, 2024 at 10:06:05PM +0200, Richard Weinberger wrote:
> > Simon,
> >
> > Am Sonntag, 18. August 2024, 17:47:01 CEST schrieb Simon Glass:
> > > In that file, this is the line that builds the tools:
> > >
> > > ./to
On 9/17/2024 10:24 PM, Tom Rini wrote:
On Tue, Sep 17, 2024 at 01:43:29PM +0530, Udit Kumar wrote:
beagleboneai64 boot was broken after OF_UPSTREAM support for
J721E SOC.
So add bootph in chipid node similar to other boards of
this SOC.
Fixes: 46bb1405b461 ("arm: dts: k3-j721e: Move to OF_UPS
On Mon, Sep 16, 2024 at 05:42:31PM +0200, Simon Glass wrote:
> Hi Heinrich,
>
> On Thu, 12 Sept 2024 at 09:12, Heinrich Schuchardt wrote:
> >
> > On 02.09.24 03:18, Simon Glass wrote:
> > > While sandbox supports virtio it cannot support actually using the block
> > > devices to read files, since
On Tue, Sep 17, 2024 at 05:54:36AM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 16 Sept 2024 at 18:33, Tom Rini wrote:
> >
> > On Mon, Sep 16, 2024 at 05:42:12PM +0200, Simon Glass wrote:
> > > Hi Heinrich,
> > >
> > > On Thu, 12 Sept 2024 at 08:58, Heinrich Schuchardt
> > > wrote:
> > > >
>
On Tue, Sep 17, 2024 at 01:43:29PM +0530, Udit Kumar wrote:
> beagleboneai64 boot was broken after OF_UPSTREAM support for
> J721E SOC.
> So add bootph in chipid node similar to other boards of
> this SOC.
>
> Fixes: 46bb1405b461 ("arm: dts: k3-j721e: Move to OF_UPSTREAM")
> Reported-by: Robert Ne
+Tom
Any update on this?
Thanks
Venkatesh
> -Original Message-
> From: Abbarapu, Venkatesh
> Sent: Tuesday, May 7, 2024 9:51 AM
> To: Abbarapu, Venkatesh ; u-boot@lists.denx.de
> Cc: Simek, Michal ; ja...@amarulasolutions.com;
> g...@xilinx.com
> Subject: RE: [PATCH] mtd: spi-nor: scale
From: Fabio Estevam
The DA9063 PMIC is a multi-function device that provides
regulator, watchdog, RTC, and ON key functionalities.
Add support for the DA9063 PMIC watchdog functionality.
Based on the 6.11 kernel drivers/watchdog/da9063_wdt.c driver.
Signed-off-by: Fabio Estevam
---
Changes si
From: Fabio Estevam
The DA9063 PMIC is a multi-function device that provides
regulator, watchdog, RTC, and ON key functionalities.
Add support for the DA9063 PMIC watchdog functionality.
Based on the 6.11 kernel drivers/watchdog/da9063_wdt.c driver.
Signed-off-by: Fabio Estevam
---
Changes si
On 9/16/24 16:02, Fabio Estevam wrote:
From: Fabio Estevam
The DA9063 PMIC is a multi-function device that provides
regulator, watchdog, RTC, and ON key functionalities.
Add support for the DA9063 PMIC RTC functionality.
Based on the 6.11 kernel drivers/watchdog/da9063_wdt.c driver.
Signed-o
Hi Simon,
On Mon, 16 Sept 2024 at 18:43, Simon Glass wrote:
>
> Hi Ilias,
>
> On Fri, 13 Sept 2024 at 09:04, Ilias Apalodimas
> wrote:
> >
> >
> > Hi Simon,
> >
> > Apologies lost that email
> >
> > > On Sun, Sep 01, 2024 at 02:09:44PM -0600, Simon Glass wrote:
> > > Hi Ilias,
> > >
> > > On Fri
On Sat, 14 Sept 2024 at 20:41, Heinrich Schuchardt wrote:
>
> On 9/5/24 10:28, Sughosh Ganu wrote:
> > Add a Kconfig symbol to enable getting updates on any memory map
> > changes that might be done by the LMB module. This notification
> > mechanism can then be used to have a synchronous view of a
Since the aml-s805-cc works well using EFI, and now the capsule updates
backend has been merged, let's enable the missing configs and add
the required structures to support it.
The GUID is dynamically generated for the board, to get it:
=> efidebug capsule esrt
The libretech-ac aka aml-s805x-ac supports mainline U-boot
from a dedicated SPI flash, move the board support into
a dedicated vendor/board subdirectory in order to support
vendor specific customization.
It also aligns with the vendor downstream changes.
Signed-off-by: Neil Armstrong
---
board/
The necessary changes were made in U-Boot to easily support
EFI Capsules Update and be compliant with Arm SystemReady IR.
Let's add support for the libretech-ac/AML-S805X-CC since
it's an easy well-supported target having a dedicated SPI
Flash to store U-Boot.
Signed-off-by: Neil Armstrong
---
C
On Sat, 14 Sept 2024 at 20:38, Heinrich Schuchardt wrote:
>
> On 9/5/24 10:27, Sughosh Ganu wrote:
> > Add an event which would be used for notifying changes in the
> > LMB modules' memory map. This is to be used for having a
> > synchronous view of the memory that is currently in use, and that is
Typo in the Subject: Generalize
On Mon, Sep 16, 2024 at 11:31 PM Peng Fan (OSS) wrote:
>
> From: Peng Fan
>
> disable_cpu_nodes could be reused by i.MX9, so move disable_cpu_nodes
> out from mach-imx/imx8m/soc.c to mach-imx/fdt.c and update
> disable_cpu_nodes to make it easy to support differen
On Tue, Sep 17, 2024 at 9:24 AM Fabio Estevam wrote:
> Should the IMX9_LOW_DRIVE_MODE symbol be deleted then?
Ah, I see it gets removed in patch 19.
> Subject: Re: [PATCH 06/21] imx9: soc: Change second Ethernet MAC
> fuse layout
>
> On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS)
> wrote:
>
> > +void build_info(void)
> > +{
> > + u32 fw_version, sha1, res, status;
> > + int ret;
> > +
> > + printf("\nBuildInfo:\n");
> > +
On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS) wrote:
>
> From: Ye Li
>
> Replace the static CONFIG_IMX9_LOW_DRIVE_MODE with runtime target
Should the IMX9_LOW_DRIVE_MODE symbol be deleted then?
",
bus, cs, speed, mode);
---
base-commit: 19dbc09405d3503ce3efef3c2e4b4f0f1a03372d
change-id: 20240917-uboot-topic-dfu-sf-dt-8ae62e5c7d79
Best regards,
--
Neil Armstrong
> Subject: Re: [PATCH 21/21] imx93_evk: Enable M.2 VPCIe_3V3 and
> deassert SD3_nRST
>
> Hi Peng,
>
> On Mon, Sep 16, 2024 at 11:31 PM Peng Fan (OSS)
> wrote:
> >
> > From: Ye Li
> >
> > VPCIe_3V3 is used to supply the power to M.2 card, we must enable
> it
> > before using the flash.
>
> Flas
On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS) wrote:
> +void build_info(void)
> +{
> + u32 fw_version, sha1, res, status;
> + int ret;
> +
> + printf("\nBuildInfo:\n");
> +
> + ret = ele_get_fw_status(&status, &res);
> + if (ret) {
> + printf(" - ELE
> Subject: Re: [PATCH 04/21] imx9: soc: Print UID in big endian format
> for EL2GO
>
> On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS)
> wrote:
> >
> > From: Ye Li
> >
> > Print UID in big endian format and as one buffer of bytes, so
> customer
> > can directly use it for EL2GO.
>
> What is EL2
On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS) wrote:
> - fuse_read(2, 3, &val);
> + ret = fuse_read(2, 3, &val);
Please use proper definitions for the 2 and 3 here.
> +
> + ret = fuse_read(2, 3, &val);
Same here.
> + if (ret)
> + val = 0; /* If read fus
Subject could be improved:
imx9: soc: Align UID endianness with ROM
On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS) wrote:
>
> From: Frank Li
>
> ROM use UID[0] and UID[1] as serial number with big endian when usb serial
> download.
On Mon, Sep 16, 2024 at 11:30 PM Peng Fan (OSS) wrote:
>
> From: Ye Li
>
> Print UID in big endian format and as one buffer of bytes, so customer
> can directly use it for EL2GO.
What is EL2GO?
Hi Peng,
On Mon, Sep 16, 2024 at 11:31 PM Peng Fan (OSS) wrote:
>
> From: Ye Li
>
> VPCIe_3V3 is used to supply the power to M.2 card, we must enable it
> before using the flash.
Flash? Which flash are you referring to?
On Sat, 14 Sept 2024 at 20:35, Heinrich Schuchardt wrote:
>
> On 9/5/24 10:27, Sughosh Ganu wrote:
> > Use the LMB API's for allocating and freeing up memory. With this, the
> > LMB module becomes the common backend for managing non U-Boot image
> > memory that might be requested by other modules.
On Sat, 14 Sept 2024 at 20:14, Heinrich Schuchardt wrote:
>
> On 9/5/24 10:27, Sughosh Ganu wrote:
> > Add a flag LMB_NONOTIFY that can be passed to the LMB API's for
> > reserving memory. This will then result in no notification being sent
> > from the LMB module for the changes to the LMB's memo
On Sat, 14 Sept 2024 at 20:01, Heinrich Schuchardt wrote:
>
> On 9/5/24 10:27, Sughosh Ganu wrote:
> > The LMB module is to be used as a backend for allocating and freeing
> > up memory requested from other modules like EFI. These memory requests
> > are different from the typical LMB reservations
On Tue, 17 Sept 2024 at 17:11, Ilias Apalodimas
wrote:
>
> On Tue, 17 Sept 2024 at 13:05, Sughosh Ganu wrote:
> >
> > On Tue, 17 Sept 2024 at 14:32, Ilias Apalodimas
> > wrote:
> > >
> > > The EFI spec defines special-purpose memory in §7.2. That memory
> > > serves as a hint to the OS to avoid
On Tue, 17 Sept 2024 at 13:05, Sughosh Ganu wrote:
>
> On Tue, 17 Sept 2024 at 14:32, Ilias Apalodimas
> wrote:
> >
> > The EFI spec defines special-purpose memory in §7.2. That memory
> > serves as a hint to the OS to avoid allocating this memory for core
> > OS data or code that can not be relo
On Mon, 16 Sept 2024 at 11:10, Vaishnav Achath wrote:
>
> The reserved memory region in fs_read() is not being
> freed after read, free that. The issue was uncovered by
> commit ed17a33fed29 ("lmb: make LMB memory map persistent and global")
> as now the region used to load from fs cannot be reuse
On Tue, 17 Sept 2024 at 14:32, Ilias Apalodimas
wrote:
>
> The EFI spec defines special-purpose memory in §7.2. That memory
> serves as a hint to the OS to avoid allocating this memory for core
> OS data or code that can not be relocated. So let's ignore it when
> allocating from conventional memo
The EFI spec defines special-purpose memory in §7.2. That memory
serves as a hint to the OS to avoid allocating this memory for core
OS data or code that can not be relocated. So let's ignore it when
allocating from conventional memory.
Signed-off-by: Ilias Apalodimas
---
lib/efi_loader/efi_memo
Hi Heinrich,
On Tue, 17 Sept 2024 at 11:49, Heinrich Schuchardt
wrote:
>
> For measured be boot we must avoid any volatile values in the device-tree.
> We already delete /chosen/kaslr-seed if we provide and EFI RNG protocol.
>
> Additionally remove /chosen/rng-seed provided by QEMU or U-Boot.
>
>
For measured be boot we must avoid any volatile values in the device-tree.
We already delete /chosen/kaslr-seed if we provide and EFI RNG protocol.
Additionally remove /chosen/rng-seed provided by QEMU or U-Boot.
Signed-off-by: Heinrich Schuchardt
---
v2:
Use an index instead of a positi
On 16/09/2024 18:29, Tom Rini wrote:
On Mon, Sep 16, 2024 at 11:41:47AM +0200, Neil Armstrong wrote:
The necessary changes were made in U-Boot to easily support
EFI Capsules Update and be compliant with Arm SystemReady SR.
To be clear, "SR" or "IR" ? I assume you meant IR here.
Indeed IR, I
On 9/17/24 08:38, Ilias Apalodimas wrote:
Hi Heinrich,
On Sat, Sep 14, 2024 at 06:08:12PM +0200, Heinrich Schuchardt wrote:
For measured be boot we must avoid any volatile values in the device-tree.
We already delete /chosen/kaslr-seed if we provide and EFI RNG protocol.
Additionally remove /c
beagleboneai64 boot was broken after OF_UPSTREAM support for
J721E SOC.
So add bootph in chipid node similar to other boards of
this SOC.
Fixes: 46bb1405b461 ("arm: dts: k3-j721e: Move to OF_UPSTREAM")
Reported-by: Robert Nelson
Signed-off-by: Udit Kumar
---
Boot logs
https://gist.github.com/udi
The SBI 3.0 specification [1] adds the following extensions:
* Firmware Features Extension
* Message Proxy Extension
Let the sbi command detect their availability.
The Firmware Features Extension is already implemented in OpenSBI.
Correct the text for the DBTR extension and move it to the same
On 16/09/24 20:50, Sughosh Ganu wrote:
Use the lmb_read_check() function to verify if it is safe to use a
region of memory to load data from a tftp command. The current logic
checks the amount of free memory available, starting from the 'load
address'. This call fails if the same region of mem
On 16/09/24 20:50, Sughosh Ganu wrote:
Use the lmb_read_check() function to verify if it is safe to use a
region of memory to load data from the wget command. The current logic
checks the amount of free memory available, starting from the 'load
address'. This call fails if the same region of m
71 matches
Mail list logo