The patchset adds support for the FWU Multi Bank Update[1]
feature. Certain aspects of the Dependable Boot[2] specification have
also been implemented.
The FWU multi bank update feature is used for supporting multiple
sets(also called banks) of firmware image(s), allowing the platform to
boot fr
Add bindings needed for accessing the FWU metadata partitions. These
include the compatible string which point to the access method and the
actual device which stores the FWU metadata.
The current patch adds basic bindings needed for accessing the
metadata structure on GPT partitioned block device
In the FWU Multi Bank Update feature, the information about the
updatable images is stored as part of the metadata, which is stored on
a dedicated partition. Add the metadata structure, and a driver model
uclass which provides functions to access the metadata. These are
generic API's, and implement
In the FWU Multi Bank Update feature, the information about the
updatable images is stored as part of the metadata, on a separate
partition. Add a driver for reading from and writing to the metadata
when the updatable images and the metadata are stored on a block
device which is formatted with GPT
The FWU metadata structure is accessed through the driver model
interface. On the stm32mp157c-dk2 board, the FWU metadata is stored on
the uSD card. Add the fwu-mdata node on the u-boot specifc dtsi file
for accessing the metadata structure.
Signed-off-by: Sughosh Ganu
Reviewed-by: Patrick Delaun
Enabling capsule update functionality on the platform requires
populating information on the images that are to be updated using the
functionality. Do so for the DK2 board.
Signed-off-by: Sughosh Ganu
Reviewed-by: Patrick Delaunay
Reviewed-by: Ilias Apalodimas
---
Changes since V9:
* Remove the
Add weak functions for getting the update index value and dfu
alternate number needed for FWU Multi Bank update
functionality.
The current implementation for getting the update index value is for
platforms with 2 banks. If a platform supports more than 2 banks, it
can implement it's own function.
The FWU Multi Bank Update feature allows the platform to boot the
firmware images from one of the partitions(banks). The first stage
bootloader(fsbl) passes the value of the boot index, i.e. the bank
from which the firmware images were booted from to U-Boot. On the
STM32MP157C-DK2 board, this value
Add an event type EVT_MAIN_LOOP that can be used for registering
events that need to be run after the platform has been initialised and
before the main_loop function is called.
Signed-off-by: Sughosh Ganu
Reviewed-by: Simon Glass
---
Changes since V9:
* Add a comment to indicate where the event
The FWU Multi Bank Update specification requires the Update Agent to
carry out certain checks at the time of platform boot. The Update
Agent is the component which is responsible for updating the firmware
components and maintaining and keeping the metadata in sync.
The spec requires that the Updat
The FWU Multi Bank Update feature supports updation of firmware images
to one of multiple sets(also called banks) of images. The firmware
images are clubbed together in banks, with the system booting images
from the active bank. Information on the images such as which bank
they belong to is stored
Add a command to read the metadata as specified in the FWU
specification and print the fields of the metadata.
Signed-off-by: Sughosh Ganu
Reviewed-by: Ilias Apalodimas
Reviewed-by: Etienne Carriere
---
Changes since V9:
* Add a document for the command
cmd/Kconfig | 6 +++
c
Add test cases for accessing the FWU Metadata on the sandbox
platform. The sandbox platform also uses the metadata access driver
for GPT partitioned block devices.
The FWU feature will be tested on the sandbox64 variant with a raw
capsule. Remove the FIT capsule testing from sandbox64 defconfig --
The Dependable Boot specification[1] describes the structure of the
firmware accept and revert capsules. These are empty capsules which
are used for signalling the acceptance or rejection of the updated
firmware by the OS. Add support for generating these empty capsules.
[1] -
https://git.codelin
Add support for setting OEM flags in the capsule header. As per the
UEFI specification, bits 0-15 of the flags member of the capsule
header can be defined per capsule GUID.
The oemflags will be used for the FWU Multi Bank update feature, as
specified by the Dependable Boot specification[1]. Bit
15
Add documentattion for the FWU Multi Bank Update feature. The document
describes the steps needed for setting up the platform for the
feature, as well as steps for enabling the feature on the platform.
Signed-off-by: Sughosh Ganu
---
Changes since V9: None
doc/develop/uefi/fwu_updates.rst | 165
From: Quentin Schulz
Puma RK3399 SoM struggled for a few releases already to boot because the
SPL was too big. Therefore, let's migrate to TPL like most RK3399-boards
already did a few releases ago.
This also fixes numerous issues around fallback booting (U-Boot proper
corrupted on the storage m
From: Quentin Schulz
distroboot should try first on the same MMC medium as the one the SPL
loaded U-Boot proper from. This was the case when the introducing commit
was merged because the default order was eMMC first and then SD card.
The check was therefore made only on whether we booted from SD
From: Quentin Schulz
On Haikou devkit, it is possible to disable eMMC and SPI-NOR to force
booting from SD card or USB via rkdeveloptool by toggling a switch. This
switch needs to be overridden in software to be able to access eMMC and
SPI-NOR once the device has booted from SD Card. Puma SoM can
From: Quentin Schulz
Trying to load U-Boot proper from SPL when SPL was not loaded from
SD-Card is currently not working because the SDMMC pins aren't muxed
correctly. It is assumed the BootROM is doing this for us when booting
from SD-Card hence why it's not needed when booting TPL/SPL from
SD-C
From: Quentin Schulz
CONFIG_ENV_OFFSET is set in the defconfig to a different value already
so this isn't used. Let's remove it as to not confuse users.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
Reviewed-by: Kever Yang
---
board/theobroma-systems/puma_rk3399/Kconfig | 3 ---
1 file ch
From: Quentin Schulz
Automatically detect which MMC device (SD-Card or eMMC) was used to load
U-Boot proper and load the environment from that MMC device instead of
a hardcoded one.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
Reviewed-by: Kever Yang
---
.../puma_rk3399/puma-rk3399.c
From: Quentin Schulz
There's a SPI-NOR flash available from which SPL and U-Boot proper can
be booted, it makes sense to also allow this medium to store U-Boot
environment so let's enable it.
The Device Tree advertises a max frequency of 50MHz so let's set the
config option appropriately.
Cc: Q
From: Quentin Schulz
Chances are when one boots U-Boot proper from a given storage medium,
they want the same medium to be used to load and store the environment.
This basically allows to have completely separate U-Boot (TPL/SPL/U-Boot
proper/environment) per storage medium which is convenient w
From: Quentin Schulz
The SPL payload offset when booting from SPI defaults to
CONFIG_SYS_SPI_U_BOOT_OFFS but can be overridden by
u-boot,spl-payload-offset. The Device Tree for Puma Haikou has this
property so there's no need to have this one option in the defconfig,
especially since they are not
From: Quentin Schulz
Depending on the toolchain used to compile the SPL for Puma RK3399-Q7
module, the board does not boot because the resulting binary is too big
to fit in SRAM.
Let's add a TPL so that there's no need to fiddle with or hack the
defconfig to have a working bootloader.
This foll
From: Quentin Schulz
The offset of the SPL payload on Lion is different than for other
Rockchip devices in that it is stored at offset 256K instead of much
further away in the MMC.
Flashing one binary instead of two at different offsets is much more
user friendly so let's migrate to it by modify
From: Quentin Schulz
The offset of the SPL payload on Puma is different than for other
Rockchip devices in that it is stored at offset 256K instead of much
further away in the MMC.
Flashing one binary instead of two at different offsets is much more
user friendly so let's migrate to it by modify
From: Quentin Schulz
Now that a single binary containing TPL/SPL correctly formatted for SPI
flashes and U-Boot proper, can be generated by binman, let's do it.
Also update the documentation to tell the user to use this newly
generated file instead of manually generating and flashing the binarie
Hi Peng,
On Wed, Sep 14, 2022 at 9:53 PM Peng Fan (OSS) wrote:
>
> From: Peng Fan
>
> "alloc space exhausted" happens in very early stage, which could be seen
> with DEBUG_UART options enabled and leeds to an non-functional board.
>
> kontron_pitx_imx8m:
> CONFIG_DEBUG_UART_BASE=0x3088 # f
From: Quentin Schulz
UART0 can obviously also be used for debug uart in U-Boot, so let's add
its support.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
arch/arm/include/asm/arch-rockchip/cru_px30.h | 19 ++
arch/arm/mach-rockchip/px30/px30.c| 37 ++-
From: Quentin Schulz
RAM_PX30_DDR4 is for DDR4 support and not DDR3 so let's fix the typo.
Fixes: 2db36c64bd5a ("ram: rockchip: px30: add a config-based ddr selection")
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
drivers/ram/rockchip/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1
This patch enables the following:
1) use preboot configuration to enable usb devices.
2) Enable USB configs so keyboards and other USB devices work,
update the number of ports of the usb root hub.
- with this addition the updated USB device Tree:
1 Hub (12 Mb/s, 0mA)
U-Bo
On Thu, Sep 15, 2022 at 06:53:42AM +0200, Jorge Ramirez-Ortiz, Foundries wrote:
> On 14/09/22, Tom Rini wrote:
> > On Tue, Aug 30, 2022 at 09:56:45PM +0200, Jorge Ramirez-Ortiz wrote:
> >
> > > Early instantiation of this I2C device would lock up when being
> > > probed.
> > >
> > > https://www.
With the recent changes in the Marvel mvneta network driver, the MDIO
bus is not connected any more. This patch updates the DT nodes to use
the nodes from the dtsi files instead of creating ad-hoc nodes.
Signed-off-by: Stefan Roese
---
arch/arm/dts/armada-xp-theadorable.dts | 27
- Remove EFI support as it's not used on this board
- Disable CONFIG_FIT_PRINT to reduce the serial output (minimal speedup)
Signed-off-by: Stefan Roese
---
configs/theadorable_debug_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configs/theadorable_debug_defconfig
b/configs/t
Signed-off-by: Pali Rohár
---
cmd/pci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/cmd/pci.c b/cmd/pci.c
index 6258699fec81..58a74755c8b2 100644
--- a/cmd/pci.c
+++ b/cmd/pci.c
@@ -450,11 +450,10 @@ static const struct pci_flag_info {
} pci_flag_info[] = {
{ PCI_REGION_IO, "io" }
On Wed, 31 Aug 2022 21:13:40 +0200, Heinrich Schuchardt wrote:
> Check the that the hash length is shorter than the message length. This
> avoids:
>
> ./tools/../lib/rsa/rsa-verify.c:275:11: warning:
> ‘*db’ may be used uninitialized [-Wmaybe-uninitialized]
> 275 | db[0] &=
On Tue, Jun 14, 2022 at 03:21:31PM +0200, Stefan Herbrechtsmeier wrote:
> From: Stefan Herbrechtsmeier
>
> The device tree binding [1] specify the vendor-id, product-id, device-id
> and language-id as 16 bit values and the linux driver reads the boost-up
> value as 8 bit value.
>
> [1]
> https
On Tue, Jun 14, 2022 at 03:21:30PM +0200, Stefan Herbrechtsmeier wrote:
> From: Stefan Herbrechtsmeier
>
> Add functions to read 8/16-bit integers like the existing functions for
> 32/64-bit to simplify read of 8/16-bit integers from device tree
> properties.
>
> Signed-off-by: Stefan Herbrecht
On Tue, Jun 14, 2022 at 04:12:00PM +0200, Stefan Herbrechtsmeier wrote:
> From: Stefan Herbrechtsmeier
>
> Allocate memory for buffers at a cache-line boundary to avoid
> misaligned buffer address for subsequent reads. This avoids an
> additional sector-based memory copy in the fat file system d
On Tue, Jul 26, 2022 at 04:21:41PM +0200, Etienne Carriere wrote:
> Removes local variable child in optee_probe() that is not used.
>
> Cc: Patrick Delaunay
> Reviewed-by: Patrick Delaunay
> Signed-off-by: Etienne Carriere
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description:
On Tue, Jul 26, 2022 at 04:21:42PM +0200, Etienne Carriere wrote:
> This change defines resources for OP-TEE service drivers to register
> themselves for being bound to when OP-TEE firmware reports the related
> service is supported. OP-TEE services are discovered during optee
> driver probe seque
On Tue, Aug 23, 2022 at 03:10:39PM -0400, Sean Anderson wrote:
> This fixes numerous cases of format strings not matching their
> arguments. Also keep the format strings on one line for easier grepping.
>
> Signed-off-by: Sean Anderson
> Reviewed-by: Simon Glass
Applied to u-boot/next, thanks!
On Tue, Jul 26, 2022 at 04:21:43PM +0200, Etienne Carriere wrote:
> Changes optee_rng driver to register itself has a OP-TEE service so
> that a device is bound for the driver when OP-TEE enumerates the
> PTA RNG service.
>
> Cc: Sughosh Ganu
> Cc: Patrick Delaunay
> Signed-off-by: Etienne Carr
On Sun, Aug 28, 2022 at 09:30:20PM +0200, Alexander Sowarka wrote:
> The nvme driver falsely assumed that the last entry on a page
> of the prp-list always points to the next page of the prp-list.
> This potentially can lead to the illegal creation of pages on
> the prp-list with only a single ent
On Mon, Aug 29, 2022 at 05:36:23PM +0200, Pali Rohár wrote:
> Signed-off-by: Pali Rohár
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Tue, Aug 30, 2022 at 02:09:11PM +0200, Patrice Chotard wrote:
> Currently, if pin's function is GPIOF_FUNC, only "func" if displayed
> without any other information. It would be interesting, if information is
> available, to indicate which pinmuxing's name is used.
>
> For example, for STM32 S
On Tue, Aug 30, 2022 at 02:09:13PM +0200, Patrice Chotard wrote:
> Populate uc_priv->name[] with pinmux node's name in order to indicate
> the pinmuxing's name in case GPIO is configured in alternate.
>
> For example, for STM32 SoC's based platform, "gpio status" command
> output :
>
> before
On Tue, Aug 30, 2022 at 02:09:14PM +0200, Patrice Chotard wrote:
> This allows to test if a pin's label if displayed using gpio_get_status()
> when this pin is configured in alternate function.
>
> Signed-off-by: Patrice Chotard
> Reviewed-by: Simon Glass
> Reviewed-by: Patrick Delaunay
Appli
On Tue, Aug 30, 2022 at 02:09:12PM +0200, Patrice Chotard wrote:
> Even pin with GPIOF_UNUSED function can have a label.
> The criteria to add or not a space character is linked to label not to
> the used/unused status.
>
> Signed-off-by: Patrice Chotard
> Reviewed-by: Simon Glass
> Reviewed-by
On Tue, Aug 30, 2022 at 04:40:37PM -0400, Sean Anderson wrote:
> Normally, readline is not used int SPL. However, it may be useful to
> enable the Freescale DDR interactive mode in SPL, while U-Boot is still
> executing from SRAM. The default settings for readline result in a large
> buffer being
On Mon, Aug 29, 2022 at 07:53:15AM +0800, Xiang W wrote:
> The bar of the structure virtio_pci_cap is the index, and each base
> address occupies 4 bytes, so it needs to be multiplied by 4.
>
> This patch fixes a bug reported by Felix Yan
> https://lists.denx.de/pipermail/u-boot/2022-August/49277
Gentle ping for this series.
On 8/25/2022 9:42 AM, Jae Hyun Yoo wrote:
Hello,
The FRU handling was added as a Xilinx board dependent support but it
is also useful for other boards, so this commit moves the FRU handling
support to the common region so that it can be enabled by CONFIG_CMD_FRU.
T
This patchset enhaces the recently added Orion Timer driver to support
all other Kirkwood & 32bit MVEBU Armada platforms. Additionally, this
timer support is then enabled per default for those platforms, so that
the board config files don't need to be changed. Also necessary is
some dts hacking, so
While testing on some Kirkwood platforms it was noticed that the timer
did not function correctly all the time. The driver did not correctly
handle 32bit timer value wrap arounds. Using the timer_conv_64()
conversion function fixes this issue.
Fixes: e9e73d78a8fb ("timer: add orion-timer support")
This patch adds support for other Marvell Armada SoC's, supporting the
25MHz fixed clock operation, like the Armada XP etc.
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- No change
v2:
- Use timer_conv_64() in timer_early_get_count()
drivers/timer/Kconfig | 5 -
drivers
Add timer_get_boot_us() to support boards, that have CONFIG_BOOTSTAGE
enabled, like pogo_v4.
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- Also support fixed input clock in early timer code
- Consolidate code for this
v2:
- Change timer_get_boot_us() to use the timer_early function
Now that the new timer support is available for these platforms, let's
select this IF for all these platforms. This way it's not necessary
that each board changes it's config header.
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- No change
v2:
- No change
arch/arm/Kconfig
This patch changes the compilation, so that the Armada 375 board(s) are
compiled in a separate step. This is necessary for the timer dts
conversion, as A375 has a different / timer description in the dts.
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- No change
v2:
- No change
arc
Add the DT bindings / descriptions for timer0 & timer1, exactly as done
in mainline Linux.
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- No change
v2:
- No change
arch/arm/dts/armada-375.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/dts/arm
Adding the "u-boot,dm-pre-reloc" DT property to the timer node is
necesssary to support the timer in the early boot phases (e.g.
SPL & pre-reloc).
Signed-off-by: Stefan Roese
Tested-by: Tony Dinh
---
v3:
- No change
v2:
- No change
arch/arm/dts/mvebu-u-boot.dtsi | 11 +++
1 file chang
With the recent changes in the Orion timer driver Kconfig setup, the
board specific enabling is not needed any more. This patch sync's these
2 boards with their current defconfig version.
Signed-off-by: Stefan Roese
Cc: Michael Walle
Tested-by: Tony Dinh
---
v3:
- New patch
v2:
- New patch
c
On 9/15/22 16:01, Jae Hyun Yoo wrote:
Gentle ping for this series.
On 8/25/2022 9:42 AM, Jae Hyun Yoo wrote:
Hello,
The FRU handling was added as a Xilinx board dependent support but it
is also useful for other boards, so this commit moves the FRU handling
support to the common region so th
On Thu, Sep 15, 2022 at 6:15 PM Kautuk Consul wrote:
>
> We add RISC-V semihosting based serial console for JTAG based early
> debugging.
>
> The RISC-V semihosting specification is available at:
> https://github.com/riscv/riscv-semihosting-spec/blob/main/riscv-semihosting-spec.adoc
>
> Signed-off
Hi,
On 9/9/22 11:57, Patrice CHOTARD wrote:
Hi Patrick
Don't forget to fix the confis/configs when applying this patch ;-)
On 9/7/22 18:18, Patrick Delaunay wrote:
Activate the support of SCMI regulator to support the scmi_reg11,
scmi_reg18 and scmi_usb33 regulators present in the scmi device
Hi,
On 8/15/22 16:52, Jorge Ramirez-Ortiz wrote:
Bits should be set to 0, not 1.
Signed-off-by: Jorge Ramirez-Ortiz
---
drivers/i2c/stm32f7_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/stm32f7_i2c.c b/drivers/i2c/stm32f7_i2c.c
index bf2a6c9b4b..3a727
Hi Alain,
On 9/12/22 10:41, Alain Volmat wrote:
Comment within stm32_i2c_message_start is misleading, indicating
that AUTOEND bit is setted while it is actually cleared.
Moreover, the bit is actually never setted so there is no need
to clear it hence get rid of this bit clear and the bit macro
a
Hi Kautuk,
On 9/15/22 8:45 AM, Kautuk Consul wrote:
> [You don't often get email from kcon...@ventanamicro.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Semihosting is a mechanism that enables code running on
> a target to communicate and use the Inpu
Hi Alain,
On 9/12/22 10:41, Alain Volmat wrote:
Functions stm32_i2c_message_start and stm32_i2c_handle_reload
both get a stop boolean indicating if the transfer should end with
a STOP or not. However no specific handling is needed in those
functions hence remove the parameter.
Signed-off-by: A
Hi Alain
On 9/12/22 10:42, Alain Volmat wrote:
Current function stm32_i2c_message_xfer is sending a STOP
whatever the result of the transaction is. This can cause issues
such as making the bus busy since the controller itself is already
sending automatically a STOP when a NACK is generated.
Th
Hi Alain,
On 9/12/22 10:42, Alain Volmat wrote:
Current function stm32_i2c_message_xfer is sending a STOP
whatever the result of the transaction is. This can cause issues
such as making the bus busy since the controller itself is already
sending automatically a STOP when a NACK is generated.
T
Hi Tom,
Please pull the STM32 related fixes for u-boot/master, v2022.10:
u-boot-stm32-20220915
- Fixes on STM32 I2C drivers
- Activate SCMI regulator for STM32MP15 defconfig, fix the usb start command
for scmi device tree
CI status:
https://source.denx.de/u-boot/custodians/u-boot-stm
Hi Alain,
On 9/12/22 10:42, Alain Volmat wrote:
From: Jorge Ramirez-Ortiz
These two device tree properties were not being applied.
Fixes: 1fd9eb68d6 ("i2c: stm32f7: move driver data of each instance in a
privdata")
Signed-off-by: Jorge Ramirez-Ortiz
Reviewed-by: Alain Volmat
---
drivers/
Hello! Now I have tested this patch series on Turris Omnia - A385,
loaded via UART kwboot and seems that everything is working fine.
On Thursday 15 September 2022 16:20:35 Stefan Roese wrote:
> This patchset enhaces the recently added Orion Timer driver to support
> all other Kirkwood & 32bit MVEB
Hi Kautuk,
I've already noted my general remarks on this approach in response to
your cover letter. This just has my comments on the RISC-V-specific
parts.
On 9/15/22 8:45 AM, Kautuk Consul wrote:
> We add RISC-V semihosting based serial console for JTAG based early
> debugging.
>
> The RISC-V s
On 9/15/22 8:45 AM, Kautuk Consul wrote:
> [You don't often get email from kcon...@ventanamicro.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> To use semihosting on qemu RISCV virt machine, we need the
> CONFIG_SPL_FS_LOAD_PAYLOAD_NAME define in qemu-
And support the 2 keys for STM32MP13x
- PKHTH : Hash of the 8 ECC Public Keys Hashes Table
(ECDSA is the authentication algorithm)
- EDMK : Encryption/Decryption Master Key
Only one key is supported for STM32MP15x
- PKH : Hash of the ECC Public Key
(ECDSA is the authentication
Add defines for value used in stm32key for BSEC permanent lock status
and error.
This patch is a preliminary step to support more lock status in BSEC
driver.
Signed-off-by: Patrick Delaunay
---
arch/arm/mach-stm32mp/cmd_stm32key.c | 15 +--
1 file changed, 9 insertions(+), 6 deleti
Update the command stm32key to support several keys selected by
key name and managed by the new sub-command:
stm32key list
stm32key select []
stm32key read -a
This patch doesn't change the STM32MP15 behavior, only PKH is
supported, but it is a preliminary patch for STM32MP13 support.
Signed-off-
Split the read_hash_otp function and introduce the helper function
read_close_status to read the close status in OTP separately of the PKH.
This patch is a preliminary step for STM32MP13 support.
Signed-off-by: Patrick Delaunay
---
arch/arm/mach-stm32mp/cmd_stm32key.c | 107 ---
Change the mask of OTP0 used to close the device on STM32MP
- STM32MP15x: bit 6 of OPT0
- STM32MP13x: 0b11 = 0x3F for OTP_SECURED closed device
And support the 2 keys for STM32MP13x
- PKHTH : Hash of the 8 ECC Public Keys Hashes Table
(ECDSA is the authentication algorithm)
- EDMK :
From: Quentin Schulz
CONFIG_SERIAL_TAG is not selectable for ARM64 machines. While
get_board_serial is weakly defined if ENV_VARS_UBOOT_RUNTIME_CONFIG is
defined, it is only called when CONFIG_SUPPORT_PASSING_ATAGS is defined,
which also is not selectable for ARM64 machines. Therefore this is dea
Unconditionally clearing DTO when RXDR is set leads to spurious timeouts
in FIFO mode transfers if events occur in the following order:
mask = dwmci_readl(host, DWMCI_RINTSTS);
// Hardware asserts DWMCI_INTMSK_DTO here
dwmci_writel(host, DWMCI_RINTSTS, DWMCI_INTMSK_DTO);
On Thu, Sep 15, 2022 at 05:37:58PM +0200, Patrick DELAUNAY wrote:
> Hi Tom,
>
> Please pull the STM32 related fixes for u-boot/master, v2022.10:
> u-boot-stm32-20220915
>
> - Fixes on STM32 I2C drivers
> - Activate SCMI regulator for STM32MP15 defconfig, fix the usb start
On Wed, Sep 14, 2022 at 04:39:18PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 14 Sept 2022 at 12:47, Tom Rini wrote:
> >
> > On Mon, Aug 29, 2022 at 07:57:04AM -0600, Simon Glass wrote:
> > > The existing shell script is a bit ugly. It was picked up by
> > > Chromium OS and then rewritten in
On Sun, Sep 04, 2022 at 03:29:06AM +0200, Pali Rohár wrote:
> Compile U-Boot with UBI/UBIFS support according to doc/board/nokia/rx51.rst
> instructions and add test case for loading kernel image from UBI volume.
>
> Signed-off-by: Pali Rohár
This I believe leads to this failure:
https://source
On Thursday 15 September 2022 14:34:27 Tom Rini wrote:
> On Sun, Sep 04, 2022 at 03:29:06AM +0200, Pali Rohár wrote:
>
> > Compile U-Boot with UBI/UBIFS support according to doc/board/nokia/rx51.rst
> > instructions and add test case for loading kernel image from UBI volume.
> >
> > Signed-off-by
Compile U-Boot with UBI/UBIFS support according to doc/board/nokia/rx51.rst
instructions and add test case for loading kernel image from UBI volume.
Signed-off-by: Pali Rohár
---
Changes in v2:
* Fix issue that script fails at the first run
- File zImage-2.6.28-omap1 needs to be unpacked earlie
The medium a device like 'mmc 0' or 'usb 0' points to may change over
time. Hence device type and number are not sufficient to identify the
inserted medium. The same is true for the device path generated for
such a device. This is why the EFI_BLOCK_IO_PROTOCOL provides a field
MediaId.
Whenever a
Currently block devices are only identified by uclass_id and device number.
When dealing with removable media this is not enough to uniquely identify
the medium.
E.g. after host unbind, host bind we can have the same device number but a
different backing file.
The EFI specification uses a 32bit n
Fill the media ID in the block IO protocol from the block device descriptor
of the driver model.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_disk.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/lib/efi_loader/efi_disk.c b/lib/efi_loader/efi_disk.c
index 7
From: Rafał Miłecki
DT binding allows specifying NVMEM cells as NVMEM device (provider)
subnodes. Looks for such subnodes when building NVMEM cells.
This allows NVMEM consumers to use U-Boot environment variables.
Signed-off-by: Rafał Miłecki
---
drivers/nvmem/u-boot-env.c | 1 +
1 file chang
On Thu, Aug 25, 2022 at 08:54:00AM +0200, Bernhard Messerklinger wrote:
> The SPI and NAND board variants never went into production.
> Drop those board variants.
>
> Signed-off-by: Bernhard Messerklinger
>
> Reviewed-by: Wolfgang Wallner
Applied to u-boot/next, thanks!
--
Tom
signature.a
On Thu, Aug 25, 2022 at 08:54:01AM +0200, Bernhard Messerklinger wrote:
> Commit 6337d53fdf45 ("arm: dts: sync am33xx with Linux 5.9-rc7") syncs
> the am335x device tree with the latest linux kernel am335x device tree.
> That causes problems with device tree in SPL stage.
> To fix the issues CONFI
On Thu, Aug 25, 2022 at 08:54:02AM +0200, Bernhard Messerklinger wrote:
> * Remove unnecessary device tree nodes which are not needed in
> U-Boot directly.
> * Move all U-Boot specific device tree properties to u-boot dtsi.
>
> Signed-off-by: Bernhard Messerklinger
>
> Reviewed-by: Wolfgang W
On Thu, Aug 25, 2022 at 08:54:03AM +0200, Bernhard Messerklinger wrote:
> Commit 0ea4fc4dcf90 ("board/BuR: invalidate ${dtbaddr} before cfgscr")
> destroys the boot targets b_t30lgcy#0 and b_t30lgcy#1. The reason behind
> this is, that b_t30lgcy#0 and b_t30lgcy#1 both load the for booting
> needed
On Thu, Aug 25, 2022 at 08:54:04AM +0200, Bernhard Messerklinger wrote:
> * Drop legacy /boot/PPTImage.md5 check
> * Update device tree naming
> * Update t30args#0 root cmd line property to support latest kernel
> versions (root=/dev/mmcblk0p2 for linux < 4 and
> root=/dev/mmcblk1p2 for linux
On Tue, Aug 30, 2022 at 03:54:29PM +0530, Jayesh Choudhary wrote:
> From: Andrew Davis
>
> Add J7200 High Security EVM defconfig.
>
> These defconfigs are the same as for the non-secure part, except for:
> CONFIG_TI_SECURE_DEVICE option set to 'y'
> CONFIG_BOOTCOMMAND uses FIT images fo
On Tue, Aug 30, 2022 at 03:54:30PM +0530, Jayesh Choudhary wrote:
> Add j721s2 High Security EVM defconfig.
>
> These configs are same as for the non-secure part, except for:
> CONFIG_TI_SECURE_DEVICE option set to 'y'
> CONFIG_FIT_IMAGE_POST_PROCESS option set to 'y'
> CO
1 - 100 of 128 matches
Mail list logo
