Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
UBI block is virtual block device, which is an abstraction
over MTD layer. Therefore it is logical to use it in combination
with MTD drivers.
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 9 -
1 file changed, 8
Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
UBI partition is abstraction over UBI volumes.
Can be used by UBI block device.
Signed-off-by: Alexey Romanov
---
drivers/mtd/ubi/Makefile | 1 +
drivers/mtd/ubi/part.c | 99
include/part.h
Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
Block devices can already set partition type at initialization
stage, so, in this case is no point in searching for partition type.
Signed-off-by: Alexey Romanov
---
disk/part.c | 7 +++
1 file changed, 7 insertions(+)
Reviewed-by
Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
UBI block is an virtual device, that runs on top
of the MTD layer. The blocks are UBI volumes.
Intended to be used in combination with other MTD
drivers.
Despite the fact that it, like mtdblock abstraction,
it used with UCLASS_MTD, they can
Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
Introduce ubi_volume_offset_write() helper, which
allow to write to ubi volume with specified offset.
Signed-off-by: Alexey Romanov
---
cmd/ubi.c | 71 +++--
env/ubi.c | 10 +++
Hello Alexey,
On 06.03.24 14:49, Alexey Romanov wrote:
Now user can pass an additional parameter 'offset'
to ubi_volume_read() function.
Signed-off-by: Alexey Romanov
---
cmd/ubi.c | 6 +++---
env/ubi.c | 6 +++---
include/ubi_uboot.h | 2 +-
3 files changed, 7 inserti
On Thu, 21 Mar 2024 15:58:19 +0530, MD Danish Anwar wrote:
> Add APIs to set a firmware_name to a rproc and boot the rproc with the
> same firmware.
>
> Clients can call rproc_set_firmware() API to set firmware_name for a rproc
> whereas rproc_boot() will load the firmware set by rproc_set_firmwa
On Tue, 12 Mar 2024 15:14:34 +0530, Apurva Nandan wrote:
> This series adds relevant ip data in remoteproc driver for j721s2 compatible.
>
> Logs:
> https://gist.githubusercontent.com/apurvanandan1997/276098af439e11105ab9f809159fcc98/raw/
>
> Changes in v3:
> - Removed j721s2.env patch from the
Hi Michael,
On Fri, Mar 22, 2024 at 2:10 PM Michael Walle wrote:
>
> Hi Tony,
>
> On Fri Mar 22, 2024 at 3:17 AM CET, Tony Dinh wrote:
> > Enable OF_UPSTREAM to use upstream DT and add marvell/ prefix to the
> > DEFAULT_DEVICE_TREE for Kirkwood boards. And so we can directly build
> > DTBs from d
Hi Tony,
On Fri Mar 22, 2024 at 3:17 AM CET, Tony Dinh wrote:
> Enable OF_UPSTREAM to use upstream DT and add marvell/ prefix to the
> DEFAULT_DEVICE_TREE for Kirkwood boards. And so we can directly build
> DTBs from dts/upstream/src/arm/marvell, and including *-u-boot.dtsi
> files from arch/arm/d
Add missing boot source id <-> device tree node path mapping for SPI NOR
flash on PX30, RK3288, RK3308, RK3368 and RV1126.
Signed-off-by: Jonas Karlman
---
v2:
- New patch
---
arch/arm/mach-rockchip/px30/px30.c | 1 +
arch/arm/mach-rockchip/rk3288/rk3288.c | 1 +
arch/arm/mach-rockchip/rk330
Rockchip BROM writes a boot source id at CFG_IRAM_BASE + 0x10, this id
indicates from what storage media TPL/SPL was loaded from.
SPL uses this id to determine what device "same-as-spl" represent when
determining from where FIT should be loaded. This works as long as the
boot_devices array contain
From: Jason Zhu
Add more bootsource id:
1. BROM_BOOTSOURCE_UNKNOWN
2. BROM_BOOTSOURCE_I2C
3. BROM_BOOTSOURCE_SPI
Signed-off-by: Jason Zhu
[jo...@kwiboo.se: Update commit message]
Signed-off-by: Jonas Karlman
---
v2:
- New patch
---
arch/arm/include/asm/arch-rockchip/bootrom.h | 3 +++
1 file
This series fixes an issue where /chosen/u-boot,spl-boot-device prop
cannot be resolved to the SPI flash node path in spl_perform_fixups() if
the affected device was booted from SPI flash.
Changes in v2:
- Add patch that sync boot source id enum with bootrom
- Add patch that adds missing SPI flash
On Fri, Mar 22, 2024 at 4:31 PM Fabio Estevam wrote:
> As Pierre's explanation addresses Marc's concern,
> do you think this can go to 2024.01 to fix the boot regression on imx8qxp/8qm?
I meant 2024.04, sorry.
Hi Tom,
On Tue, Mar 19, 2024 at 9:39 AM Pierre-Clément Tosi wrote:
> For most AArch64 U-Boot ports (including the i.MX family), the answer is
> trivial
> because they use the arch code i.e. setup_all_pgtables(). However, as
> fsl-layerscape re-implements mmu_setup(), it had to be looked at sepa
On Wed, 20 Mar 2024 13:48:45 -0300, Hiago De Franco wrote:
> Increase the SPL_STACK_R_MALLOC_SIMPLE_LEN to 0x20 to accommodate the
> size of tispl.bin fit image. With the recent upgrade of ti-linux-firmware
> from version v9.1.0 to v9.2.5, the size of tispl.bin fit image has
> increased to 1.4
On Mon, 18 Mar 2024 11:47:16 +0100, Heinrich Schuchardt wrote:
> The Linaro mail address is not valid anymore.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Tue, 19 Mar 2024 11:04:27 -0300, Joao Paulo Goncalves wrote:
> The lowest speed grade of Toradex AM62 SoMs is K speed, resulting in a
> max value of 800MHz for the CPU operating frequency. A solution with
> runtime selection of the CPU frequency is already planned to avoid these
> kinds of prob
On Fri, 08 Mar 2024 17:13:15 -0300, Fabio Estevam wrote:
> Since commit cc7df0b9e8bc ("serial: lpuart: Enable IPG clock")
> the colibri-imx8qxp board no longer boots.
>
> The reason is that the imx8qxp clock driver does not handle the
> LPUART IPG clocks inside get_rate(), set_rate() and enable()
Hi Paul,
On Sun, Feb 11, 2024 at 4:42 PM Paul Liu wrote:
>
> Hi Fabio,
>
> I'm on vacation now (Chinese new year). I hope I'll find some time to revive
> my imx8 board.
> I've tried sandbox and qemu. Both of them are not reproducible. I'm wondering
> if it could be some packet loss that causes
Hi Jonas,
On Mon, 2024-03-18 at 11:37 +0100, Jonas Karlman wrote:
> Hi Christopher,
>
> On 2024-03-15 13:01, Christopher Obbard wrote:
> > Some variants of the ROCK Pi 4 series have an SPI flash chip populated
> > which can be booted from. This patch enables support in U-Boot for
> > building the
On 3/22/24 5:55 AM, Sumit Garg wrote:
Hi,
I think if people are concerned about power consumption then it
should be implemented properly in U-Boot to remove all the DT based
devices before passing on control to the next stage.
I would expect imx8mp_hsiomix_off() to be called either on 'usb st
On 3/22/24 07:53, Michal Simek wrote:
>
>
> On 3/21/24 17:20, Sean Anderson wrote:
>> On 3/20/24 07:18, Michal Simek wrote:
>>> if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot
>>> mode which is 0. When 0 was used origin(HW) boot mode was used instead.
>>> That's why dire
On 3/22/24 5:36 AM, Sumit Garg wrote:
On Fri, 22 Mar 2024 at 00:47, Marek Vasut wrote:
On 3/21/24 1:40 PM, Sumit Garg wrote:
On Thu, 14 Mar 2024 at 09:46, Marek Vasut wrote:
On 3/12/24 8:03 AM, Sumit Garg wrote:
Add initial support for i.MX8M{M/P} PCIe PHY. On i.MX8M{M/P} SoCs PCIe
PHY in
Hi Sumit,
On Thu, Mar 21, 2024 at 11:55 AM Sumit Garg wrote:
> Changes in v4:
> - Incorporated misc comments from Marek and added his review tag.
> - Dropped patch #4 (imx8mp: power-domain: Don't power off pd_bus)
> since power domain off path is never excercised for DT based devices.
> - Adde
Hi Lukasz,
On Fri, Mar 22, 2024 at 8:43 AM Lukasz Majewski wrote:
> arch/arm/dts/Makefile | 3 +-
> arch/arm/dts/imx28-xea-1-u-boot.dtsi | 11
> arch/arm/dts/imx28-xea-1.dts | 8 +++
> arch/arm/dts/imx28-xea-2-u-boot.dtsi | 11 ++
Clean up templatized boot binaries for all K3 boards. This includes
modifying the k3-binman.dtsi to use SPL_BOARD_DTB, BOARD_DESCRIPTION and
UBOOT_BOARD_DESCRIPTION from the files that include it to further reuse
code.
All k3--binman.dtsi will contain only templates. Only required boot
binaries ca
Dynamically going through the subnode array and deleting leads to
templates being skipped from deletion when templates are consecutive in
the subnode list. Prevent this from happening by first parsing the DT
and then deleting the nodes.
Signed-off-by: Neha Malcom Francis
---
tools/binman/control
Add defconfig for J721E SK R5 and A72 configuration.
This includes and modifies the J721E EVM defconfigs:
j721e_evm_r5_defconfig -> j721e_sk_r5_defconfig
j721e_evm_a72_defconfig -> j721e_sk_a72_defconfig
Signed-off-by: Neha Malcom Francis
---
board/ti/j721e/MAINTAINERS | 2 ++
configs/j72
This series does primarily three things:
1. Split out the common J721E defconfig for both EVM and SK
2. Cleanup k3-j721e-binman.dtsi to be SoC specific binman nodes
and -u-boot.dtsi files of the respective boards can pick and
edit according to their board. This
fs
+nfsroot=/srv/nfs
sd_dev=1
---
base-commit: 86b79cf131b64eadae023a127921893d30503093
change-id: 20240322-phycore_mx8mp_netboot_fixes-337ceb4ba0cc
Best regards,
--
Yannic Moog
HI
On Fri, Mar 22, 2024 at 1:02 PM Alexander Dahl wrote:
>
> Hello Michael,
>
> Am Fri, Mar 22, 2024 at 12:54:27PM +0100 schrieb Michael Nazzareno Trimarchi:
> > HI
> >
> > On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote:
> > >
> > > Hello Mihai,
> > >
> > > Am Fri, Mar 22, 2024 at 10:02:2
On 3/21/24 22:04, Caleb Connolly wrote:
This adjusts OF_UPSTREAM to behave more like the kernel by allowing for
all the devicetree files for a given vendor to be compiled. This is
useful for Qualcomm in particular as most boards are supported by a
single U-Boot build just provided with a diffe
On 3/21/24 22:03, Caleb Connolly wrote:
Drop in favour of dts/upstream
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/xlnx-versal-clk.h| 123 ---
include/dt-bindings/clock/xlnx-zynqmp-clk.h| 126
include/dt-bindings/dma/xl
Generate dfu_alt_info generation based on information from MTD partitions.
mtd_found_part() is trying to identify MTD partition which code is running
from. If partitions are not defined and location is not found it is going
to previous behavior.
Signed-off-by: Michal Simek
---
Changes in v2:
- U
Generate description only when CONFIG_SPL_FS_LOAD_PAYLOAD_NAME is not
empty. When name is empty there is no reason to generate description for
it because it is not aligned with dfu rules.
Signed-off-by: Michal Simek
---
Changes in v2:
- New patch is series coming from discussion at
https://lore.
Hello Michael,
Am Fri, Mar 22, 2024 at 12:54:27PM +0100 schrieb Michael Nazzareno Trimarchi:
> HI
>
> On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote:
> >
> > Hello Mihai,
> >
> > Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com:
> > > Hi Michael,
> > >
> > > -
On 2/23/24 17:18, Michal Simek wrote:
Generate dfu_alt_info generation based on information from MTD partitions.
mtd_found_part() is trying to identify MTD partition which code is running
from. If partitions are not defined and location is not found it is going
to previous behavior.
Signed-of
On 2/23/24 17:18, Michal Simek wrote:
There is no reason to describe u-boot.itb on system without SPL. Pretty
much this is cover all systems which are using only boot.bin which contains
all images inside.
Signed-off-by: Michal Simek
---
board/xilinx/common/board.c | 2 +-
1 file changed,
On 3/22/24 8:47 AM, Janne Grunau via B4 Relay wrote:
[...]
@@ -1099,6 +1142,20 @@ int usb_select_config(struct usb_device *dev)
le16_to_cpus(&dev->descriptor.idProduct);
le16_to_cpus(&dev->descriptor.bcdDevice);
+ /* ignore devices from usb_ignorelist */
+ err = usb_de
On 3/12/24 16:51, Michal Simek wrote:
mach Kconfig file select some options independently of if SPL is actually
enabled. It ends up in situation that SPL is disabled but symbols are still
present in .config. That's why add SPL dependency for them but also group
them with other SPL options in A
HI
On Fri, Mar 22, 2024 at 12:46 PM Alexander Dahl wrote:
>
> Hello Mihai,
>
> Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com:
> > Hi Michael,
> >
> > ---
> >
> > I think this command can be really useful.
> > Let try
On 3/21/24 17:20, Sean Anderson wrote:
On 3/20/24 07:18, Michal Simek wrote:
if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot
mode which is 0. When 0 was used origin(HW) boot mode was used instead.
That's why directly fill reg variable with requested boot mode and don
Hello Mihai,
Am Fri, Mar 22, 2024 at 10:02:29AM + schrieb mihai.s...@microchip.com:
> Hi Michael,
>
> ---
>
> I think this command can be really useful.
> Let try to have more testing on more boards
>
>
In the scenario of recovery, the FitImage is used to boot the system.
This patch provides support for deciding which dtb configuration shall
be used.
Signed-off-by: Lukasz Majewski
---
board/liebherr/xea/xea.env | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/liebherr
As now XEA has its second HW revision - this information is printed
when u-boot proper starts.
Signed-off-by: Lukasz Majewski
---
board/liebherr/xea/xea.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/board/liebherr/xea/xea.c b/board/liebherr/xea/xea.c
index 5bac614153..876e8a70a
The 'board_som_rev' environment variable will be used to point correct
configuration from the Linux FIT file.
Signed-off-by: Lukasz Majewski
---
board/liebherr/xea/xea.c | 12
configs/imx28_xea_defconfig| 1 +
configs/imx28_xea_sb_defconfig | 1 +
3 files changed, 14 in
After this change u-boot proper is able to support two HW revisions of the
XEA board.
Signed-off-by: Lukasz Majewski
---
configs/imx28_xea_defconfig| 2 ++
configs/imx28_xea_sb_defconfig | 2 ++
2 files changed, 4 insertions(+)
diff --git a/configs/imx28_xea_defconfig b/configs/imx28_xea_d
The imx287 based XEA board's revision 2 uses GPIO_3_21 for PHY reset
It is safe to keep the GPIO_2_13 as well, as in the SPL SPI1 is not
used for transmission. This simplifies the code, as the proper
configuration is performed either in falcon boot's read DTB or in
u-boot proper (with correct FIT
For SPL and u-boot proper, the difference between revsions boils
down only to the GPIO pin for PHY reset.
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/Makefile| 3 ++-
arch/arm/dts/imx28-xea-2-u-boot.dtsi | 11 +++
arch/arm/dts/imx28-xea-2.dts | 8
As XEA board uses imx287, which has some constrains on SPL (u-boot.sb)
size - it must be less than ~55 KiB, multiple boards versions are included
in u-boot proper's FIT image.
The decision of using proper configuration is based on information passed
from SPL (u-boot.sb) in OCRAM dedicated location
The comment in u-boot specific adjustment to XEA DTS is not valid anymore.
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/imx28-xea-1-u-boot.dtsi | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/dts/imx28-xea-1-u-boot.dtsi
b/arch/arm/dts/imx28-xea-1-u-boot.dtsi
index 2903be2089
The DTS description in XEA for mac0 node in u-boot differs considerably
from what we do have available in Linux, as u-boot is not supporting L2
switch (i.e. 'fixed-link' property is used).
To facilitate HW revision management - this particular property has been
moved to version specific file.
Sig
The former imx28-xea.dts file has been renamed to imx28-xea.dtsi, which
is included to new imx28-xea-1.dts file.
This is a preparatory work to add support for multiple versions of XEA
boards to u-boot.
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/Makefile | 2 +-
a
Private function for finding out location of environment is not working
when ENV_IS_NOWHERE is disabled.
The reason is that current fallback is ENVL_UNKNOWN when
CONFIG_ENV_IS_NOWHERE is not enabled. The code could be updated like this
- return ENVL_NOWHERE;
+ if (IS_EN
The XEA board now has several HW revisions for both SoM and base boards.
This patch provides support for reading those revision ID values in SPL
(u-boot.sb) and then pass this information to u-boot proper, as the
maximal SPL size (~55KiB) is not allowing for having FIT support in it.
It was necess
XEA is not supporting and using I2S codec, so there is no need to
configure pins for it.
Signed-off-by: Lukasz Majewski
---
board/liebherr/xea/spl_xea.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/board/liebherr/xea/spl_xea.c b/board/liebherr/xea/spl_xea.c
index df354cac64..551ed6
This patch set provides support for different XEA board revisions.
Due to very limited SPL size, the board's switch DTB decision is
performed very early in u-boot proper; before driver model is set.
Adjustments for DTS between revisions are for the u-boot adjustment code
(i.e. tweaks due to func
On Fri, 22 Mar 2024 at 12:58, Sughosh Ganu wrote:
>
> Support is to be added in the following commits for the FWU metadata
> version 2. Disable the FWU feature on platforms that enable it for the
> V2 addition work.
>
> Signed-off-by: Sughosh Ganu
> ---
> Changes since V2: None
>
> configs/corst
On Fri, 22 Mar 2024 at 12:59, Sughosh Ganu wrote:
>
> Add an entry for the FWU Multi Bank Update feature.
>
> Signed-off-by: Sughosh Ganu
> ---
> Changes since V2:
> * New patch
>
> MAINTAINERS | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cd9
When Falcon Mode is enabled on RISC-V, use CONFIG_VAL
to check PAYLOAD_ARGS_ADDR, not CONFIG_IS_ENABLED.
Signed-off-by: Randolph
---
common/spl/spl_opensbi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/spl/spl_opensbi.c b/common/spl/spl_opensbi.c
index 8127ebc946..
Now that support for FWU metadata version 2 has been added, the
feature can be enabled on platforms which had enabled it. A new config
symbol for selecting the metadata version for the platform is also
being added.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Add config symbol for selectin
Add an entry for the FWU Multi Bank Update feature.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cd9b2d42e8..5409b1d78a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1147,6
The FWU Update Agent in U-Boot supports both versions of the FWU
metadata. Make changes in the documentation to reflect this.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Changes to indicate support for both v1 and v2 instead of only v2.
doc/board/socionext/developerbox.rst | 7 +--
The version 2 of the FWU metadata allows for appending opaque vendor
specific data to the metadata structure. Add support for appending
this data to the metadata. The vendor specific data needs to be
provided through a file, passed through a command-line parameter. Make
corresponding changes to the
Make changes to the FWU metadata access tests corresponding to the
changes in the FWU metadata access code.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Make changes to have the test work with v1 metadata.
* Make changes to have the test work with updated logic in fwu code.
test/dm/fwu_m
Add support for generating the FWU metadata version 2. The tool now
requires the version to be provided as a command-line option. Make
corresponding changes to the tool's manpage.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Support both metadata versions instead of only v2.
doc/mkfwumda
Add support for displaying data specific to FWU metadata version
2. Because the size of the v2 metadata structure is read from the
structure itself, allocate memory for the metadata structure by first
getting the size of the structure.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Earlier p
Make changes to the functions used for generating the DFU's alt
variable so that the FWU image information is obtained from the common
version agnostic structure instead of reading the metadata.
While here, also update the name of the field used for storing the
image GUID in the FWU metadata.
Sig
Information about FWU images on MTD partitions is now stored with the
corresponding driver instead of a global variable. Get this
information from the driver.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch
lib/fwu_updates/fwu_mtd.c | 17 +++--
1 file changed, 11 inser
The third argument passed to the function gen_image_alt_info() is not
used and is superfluous. Remove this unused argument from the function
call.
Fixes: 4898679e190 (FWU: Add FWU metadata access driver for MTD storage regions)
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch
lib/f
Support has been added for version 2 of the FWU metadata
structure. Add config symbols to enable either of the two versions.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch
lib/fwu_updates/Kconfig | 14 ++
lib/fwu_updates/Makefile | 2 ++
2 files changed, 16 insertio
Transition the platform to either Trial State or Regular State on a
successful update. Do this by calling the fwu_state_machine_updates()
API function.
For version 1 of the FWU metadata, the transition to Trial State is
done by starting the Trial State counter, while for version 2, in
addition to
With addition of support for version 2 of the FWU metadata structure,
the metadata information is collected into a version agnostic
structure. Make changes to the FWU functions so that the information
that was earlier obtained by reading the metadata structure is now
obtained through this version a
Support is being added in U-Boot for version 2 of the FWU
metadata. Support for this version is to co-exist with version 1
support. To achieve this, a common, version agnostic structure has
been added to keep information provided by the FWU metadata
structure.
Add API's to handle the version speci
The FWU specification now has two versions of the FWU metadata
structure, and both are to be supported. Introduce a version agnostic
structure for storing information about the FWU updatable images. This
allows for a split of common version agnostic FWU code and version
specific code.
The version
Add support for version 2 of the FWU metadata structure. The top level
structure is kept separate through a config symbol. Most of the
fields, primarily used for providing information on updatable images
are common across the two versions.
Also change a few existing structure members used for imag
The FWU metadata access driver for MTD partitioned devices currently
uses a statically allocated array for storing the updatable image
information. This array depends on the number of banks and images per
bank. With migration of the FWU metadata to version 2, these
parameters are now obtained at ru
In version 2 of the metadata structure, the size of the structure
cannot be determined statically at build time. The structure is now
broken into the top level structure which contains a field indicating
the total size of the structure.
Add a size parameter to the metadata access API functions to
The fwrite call returns the number of bytes transferred as part of the
write only when the size parameter is 1. Pass the size parameter to
the library call as 1 so that the correct number of bytes transferred
are returned.
Fixes: fdd56bfd3ad ("tools: Add mkfwumdata tool for FWU metadata image")
Si
Support is to be added in the following commits for the FWU metadata
version 2. Disable the FWU feature on platforms that enable it for the
V2 addition work.
Signed-off-by: Sughosh Ganu
---
Changes since V2: None
configs/corstone1000_defconfig | 2 --
configs/sandbox64_defconfig
The following patch series adds support for version 2 of the FWU
metadata. The version 2 metadata structure is defined in the latest
revision of the FWU specification [1].
The earlier versions of these patches were migrating to a version 2
only support in U-Boot, similar to TF-A. However, based
Hi Simon,
út 22. 8. 2023 v 5:18 odesílatel Simon Glass napsal:
> Move the failure message outside the loop, so it is easier to follow the
> code. Avoid swallowing the error code - just pass it along.
>
> Drop the initcall-list address from the output. This is confusing since
> we show two addres
Hi Michael,
---
I think this command can be really useful.
Let try to have more testing on more boards
-
I managed to test the command on sama7g54-curiosity board.
I also forced timing m
Hi Kever,
On 2/19/24 10:50, Quentin Schulz wrote:
Hi Kever,
On 2/18/24 02:14, Kever Yang wrote:
Hi Quentin,
On 2024/2/9 21:18, Quentin Schulz wrote:
From: Quentin Schulz
The STM32_RST line is routed to the ATtiny microcontroller
PA0/RESET/UPDI pin. By driving the PX30 SoC pin as GPIO output
On jeu., mars 21, 2024 at 20:38, Marek Vasut wrote:
> On 3/21/24 11:01 AM, Mattijs Korpershoek wrote:
>> Hi Marek,
>>
>> Thank you for the patch.
>>
>> On dim., mars 17, 2024 at 05:42, Marek Vasut
>> wrote:
>>
>>> The dm_usb_gadget_handle_interrupts() has no place in board code. Move
>>> thi
Hi Caleb,
On jeu., mars 21, 2024 at 17:01, Caleb Connolly
wrote:
> On 21/03/2024 16:48, Mattijs Korpershoek wrote:
>> Hi Caleb,
>>
>> Thank you for the patch.
>>
>> On jeu., mars 21, 2024 at 15:28, Caleb Connolly
>> wrote:
>>
>>> The patch introducing support for dynamic sector sizes chang
Hi Viacheslav,
On 19/03/2024 15:42, Neil Armstrong wrote:
Enable OF_UPSTREAM to use upstream DT and add amlogic/ prefix to the
DEFAULT_DEVICE_TREE. And thereby directly build DTB from dts/upstream/src/
including *-u-boot.dtsi files from arch/$(ARCH)/dts/ directory and
drop redundant files from a
On 22.03.2024 11:17, Michael Nazzareno Trimarchi wrote:
> Hi Arseniy
>
> On Fri, Mar 22, 2024 at 9:14 AM Arseniy Krasnov
> wrote:
>>
>> Hi,
>>
>> On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote:
>>> Hi Arseniy
>>>
>>> On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov
>>> wrote:
Hi Arseniy
On Fri, Mar 22, 2024 at 9:14 AM Arseniy Krasnov
wrote:
>
> Hi,
>
> On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote:
> > Hi Arseniy
> >
> > On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov
> > wrote:
> >>
> >> Add access to OTP region. It supports info, dump, write and lock
> >>
On 3/22/24 08:47, Janne Grunau via B4 Relay wrote:
From: Janne Grunau
The xhci driver currently only does the necessary initialization for
endpoints found in the first interface descriptor. Apple USB keyboards
(released 2021) use the second interface descriptor for the HID keyboard
boot protoco
Hi,
On 22.03.2024 11:12, Michael Nazzareno Trimarchi wrote:
> Hi Arseniy
>
> On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov
> wrote:
>>
>> Add access to OTP region. It supports info, dump, write and lock
>> operations. Usage example:
>>
>> 'mtd otpread nand0 u 0 1024' - dump 1024 bytes of user
Hi Arseniy
On Wed, Mar 20, 2024 at 8:14 PM Arseniy Krasnov
wrote:
>
> Add access to OTP region. It supports info, dump, write and lock
> operations. Usage example:
>
> 'mtd otpread nand0 u 0 1024' - dump 1024 bytes of user area starting
> from offset 0 of device 'nand0'.
>
> 'mtd otpwrite nand0
Hi Venkatesh,
we're not using the firmware when running in el3, so that should still
work. The sdhci driver needs to know which controller it's operating on
and uses the power-domain node for that. I can't add the power domain
node without a firmware node (i think?), but the firmware node without
Provide a man-page for the itest command.
Signed-off-by: Heinrich Schuchardt
---
doc/usage/cmd/itest.rst | 113
doc/usage/index.rst | 1 +
2 files changed, 114 insertions(+)
create mode 100644 doc/usage/cmd/itest.rst
diff --git a/doc/usage/cmd/ite
Add a cross reference to the itest command.
Fix a typo: %s/Example/Examples/.
Signed-off-by: Heinrich Schuchardt
---
doc/usage/cmd/if.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/usage/cmd/if.rst b/doc/usage/cmd/if.rst
index 6b3dbe7b0a0..813f903a8d8 100644
-
Apple USB Keyboards from 2021 need quirks to be useable. The boot HID
keyboard protocol is unfortunately not described in the first interface
descriptor but the second. This needs several changes. The USB keyboard
driver has to look at all (2) interface descriptors during probing.
Since I didn't wa
From: Janne Grunau
In the next step endpoints for multiple interfaces are set up. Move most
of the per endpoint initialization to separate function to avoid another
identation level.
Reviewed-by: Marek Vasut
Reviewed-by: Neal Gompa
Signed-off-by: Janne Grunau
---
drivers/usb/host/xhci.c | 11
From: Janne Grunau
Apple USB keyboards (Magic Keyboard from 2021 (product id 0x029c)) carry
the HID keyboard boot protocol on the second interface descriptor.
Probe via vendor and product IDs since the class/subclass/protocol match
uses the first interface descriptor.
Probe the two first interfac
1 - 100 of 106 matches
Mail list logo