%s/formatted/format/
Fixes: 4211fb2ef6dd ("doc: Migrate CodingStyle wiki page to Sphinx")
Signed-off-by: Heinrich Schuchardt
---
doc/develop/codingstyle.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst
index
Hi
Il ven 15 lug 2022, 21:21 Heiko Thiery ha scritto:
> Hi Michael,
>
> Am Fr., 15. Juli 2022 um 12:21 Uhr schrieb Michael Nazzareno Trimarchi
> :
> >
> > Hi Heiko
> >
> > On Fri, Jul 15, 2022 at 12:06 PM Heiko Thiery
> wrote:
> > >
> > > Hi Marek
> > >
> > > Am Fr., 15. Juli 2022 um 11:29 Uhr
es by default...
> The linux-next kernel has the following commit, which disables
> the job ring 0 and fixes the problem:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
> next.git/commit/?h=next-20220715=dc9c1ceb555ff661e6fc1081434600771f29657c
>
> [1] htt
I just checked this still works in next. No v2 needed (until feedback,
because I've heard about nodes providing two devices and maybe you
prefer that, so far I'd still see it too complex).
El Fri, Jul 01, 2022 at 08:59:59PM +0200, Xavier Drudis Ferran deia:
>
> arch/arm/dts/rk3399.dtsi has a
Hi Marek,
Am Fr., 15. Juli 2022 um 12:24 Uhr schrieb Marek Vasut :
>
> On 7/15/22 12:05, Heiko Thiery wrote:
> > Hi Marek
> >
> > Am Fr., 15. Juli 2022 um 11:29 Uhr schrieb Marek Vasut :
> >>
> >> On 7/15/22 10:33, Heiko Thiery wrote:
> >>> Hi,
> >>
> >> Hi,
> >>
> >>> I see since the change to
Hi Michael,
Am Fr., 15. Juli 2022 um 12:21 Uhr schrieb Michael Nazzareno Trimarchi
:
>
> Hi Heiko
>
> On Fri, Jul 15, 2022 at 12:06 PM Heiko Thiery wrote:
> >
> > Hi Marek
> >
> > Am Fr., 15. Juli 2022 um 11:29 Uhr schrieb Marek Vasut :
> > >
> > > On 7/15/22 10:33, Heiko Thiery wrote:
> > > >
On Thu, Jul 07, 2022 at 10:41:34AM +0200, Michal Suchánek wrote:
> Hello,
>
> this causes regression on pinebook pro:
>
> resetting ...
> System reset not supported on this platform
> ### ERROR ### Please RESET the board ###
>
> Is there something missing in the DT for this board?
>
> Or
There is no default boot command set for de0-nano-soc.
This results in simply dropping to the u-boot shell.
With this, the target now automatically invokes distro_bootcmd
to boot the kernel.
Signed-off-by: Vijai Kumar K
---
configs/socfpga_de0_nano_soc_defconfig | 1 -
1 file changed, 1
The ISW_ENTRY_ADDR symbol was used for OMAP devices in place of
SPL_TEXT_BASE. Keystone2 HS devices were not using it right either.
Remove ISW_ENTRY_ADDR and use SPL_TEXT_BASE directly.
Signed-off-by: Andrew Davis
---
arch/arm/Kconfig | 15 ---
On Fri, Jul 15, 2022 at 12:10:47PM -0500, Chris Morgan wrote:
> On Thu, Jul 07, 2022 at 10:41:34AM +0200, Michal Suchánek wrote:
> > Hello,
> >
> > this causes regression on pinebook pro:
> >
> > resetting ...
> > System reset not supported on this platform
> > ### ERROR ### Please RESET the
://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220715=dc9c1ceb555ff661e6fc1081434600771f29657c
[1]
https://lore.kernel.org/u-boot/am6pr06mb46912207d9460cd9924f35daa6...@am6pr06mb4691.eurprd06.prod.outlook.com/T/#t
Signed-off-by: Fabio Estevam
---
arch/arm/dts/imx8mm.dtsi
Hi Sughosh,
On Thu, 14 Jul 2022 at 21:40, Sughosh Ganu wrote:
>
> 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
Read the swrv.txt file from the TI Security Development Tools when
TI_SECURE_DEVICE is enabled. This allows us to set our software
revision in one place and have it used by all the tools that create
TI x509 boot certificates.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/config.mk | 8
From: Yogesh Siraswar
The x509 certificate SWRV is currently hard-coded to 0. This need to be
updated to 1 for j721e 1.1, j7200 and am64x. It is don't care for other
k3 devices.
Added new config K3_X509_SWRV to k3. Default is set to 1.
Signed-off-by: Yogesh Siraswar
Reviewed-by: Dave Gerlach
Oops. Sorry to mess up the Reply-To.
I meant to send 1/5 .. 5/5 as replies to 0/5 but I sent them out of
mail thread.
On 7/15/22 18:13, Stefan Herbrechtsmeier wrote:
Am 15.07.2022 um 11:39 schrieb Ashok Reddy Soma:
Try loading pmufw config overlay for core0, if it doesn't return any
error it means pmufw is accepting nodes for other IP's. Otherwise dont
try to load config object for any other IP, just return
If the device is a GP and we detect a signing certificate then remove it.
It would fail to authenticate otherwise as the device is GP and has no
secure authentication services in SYSFW.
This shouldn't happen often as trying to boot signed images on GP devices
doesn't make much sense, but if we
K3 SoCs are available in a number of device types such as
GP, HS-FS, EMU, etc. Like OMAP SoCs we can detect this at runtime
and should print this out as part of the SoC information line.
We add this as part of the common.c file as it will be used
to also modify our security state early in the
We can skip the image authentication check at runtime if the device is GP.
This reduces the delta between GP and HS U-Boot builds. End goal is
to re-unify the two build types into one build that can run on all
device types.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/Makefile | 3 +--
On HS-FS devices signing boot images is optional. To ease use
we check if we are HS-FS and if no certificate is attached
to the image we skip the authentication step with a warning
that this will fail when the device is set to security enforcing.
Signed-off-by: Andrew Davis
---
Spi0 is not needed in SPL and SPL could be a little smaller without it,
but then the SF_DEFAULT_BOOT would have to be 0 to refer to spi1, and
that's confusing, because once U-Boot proper runs, it numbers the bus 1.
Add spi0 to the pre-reloc and spl trees so that the flash is always
connected to
Trying to boot my Rock Pi 4B from its XTX SPI NOR Flash failed when my
custom compiled TF-A had a load address of 0.
The same TF-A booted correctly from MMC.
Add a local variable to spi_mem_exec_op() to determine operation
direction, instead of testing rx_buf or tx_buf for null value, so that
a
XTX25F32B does not use octal mode and accepts soft reset,
despite its SFDP tables. Soft reset at U-Boot exit seems to be
required to write to /dev/mtd0 from flashrom in linux. Soft reset
at U-Boot start seems to help booting from SPI (at least with the
dts properties I'm using).
The first soft
Configure Rock Pi 4 to boot from SPI NOR Flash.
Based on flash chip, board documentation and tests, this is the
fastest I could use it.
This seems to be the minimum necessary configuration for Rock Pi 4 to
be able to boot from SPI NOR Flash.
With the next patch, it works to sf probe 1:0, sf
Radxa Rock Pi 4B from version 1.4 on carries a 4MiB XTX Technology Inc
25F32B SPI NOR Flash. (previous versions had pads where users could
solder different chips).
Add its parameters to spi-nor-ids.c so U-Boot can discover it and
(after further changes) we can boot from SPI.
Note that the Flash
The Radxa Rock Pi 4 board is sold from revision 1.4 with a soldered
4Mb SPI NOR Flash. This series allows to use it from U-Boot and boot
from it.
This series applies to u-boot/next.
Changes since v1:
- Changed bus number to 1 in SPL to match U-Boot proper (before it
was bus 0 in SPL and
This isn't strictly needed as these firewalls should all be disabled on
GP, but it also doesn't hurt, so do this unconditionally to remove this
use of CONFIG_TI_SECURE_DEVICE.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/am6_init.c | 4
arch/arm/mach-k3/j721e_init.c | 4
2 files
Sync new additions to non-HS defconfig with HS defconfig.
Signed-off-by: Andrew Davis
---
configs/am57xx_hs_evm_defconfig | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/configs/am57xx_hs_evm_defconfig b/configs/am57xx_hs_evm_defconfig
index
Additions have been made to the non-HS defconfig without the same
being made to the HS defconfig, sync them.
Signed-off-by: Andrew Davis
---
configs/j721e_hs_evm_a72_defconfig | 42 ++
configs/j721e_hs_evm_r5_defconfig | 56 +-
2 files changed,
Additions have been made to the non-HS defconfig without the same
being made to the HS defconfig, sync them.
Signed-off-by: Andrew Davis
---
configs/am65x_hs_evm_a53_defconfig | 23 ++-
configs/am65x_hs_evm_r5_defconfig | 8
2 files changed, 30 insertions(+), 1
Am 15.07.2022 um 11:39 schrieb Ashok Reddy Soma:
Try loading pmufw config overlay for core0, if it doesn't return any
error it means pmufw is accepting nodes for other IP's. Otherwise dont
try to load config object for any other IP, just return from
zynqmp_pmufw_node function.
Signed-off-by:
On Fri, 15 Jul 2022 at 17:37, Quentin Schulz wrote:
>
> From: Quentin Schulz
>
> On MMC storage media, the TPL/SPL needs to be flashed at offset 32KB.
> Instead of requesting the user to put the input the appropriate offsets,
> let's create u-boot-rockchip.bin with the padding already added.
On AM43xx HS devices, QSPI boot is XIP and we use a single stage
bootloader. Add a defconfig for this.
Signed-off-by: Andrew Davis
---
MAINTAINERS | 1 +
configs/am43xx_hs_evm_qspi_defconfig | 74
2 files changed, 75 insertions(+)
create
Hi,
On Thu, 14 Jul 2022 at 11:55, Rob Herring wrote:
>
> On Wed, Jul 13, 2022 at 9:28 AM Simon Glass wrote:
> >
> > Hi Rob,
> >
> > On Tue, 12 Jul 2022 at 08:11, Rob Herring wrote:
> > >
> > > On Tue, Jul 12, 2022 at 5:04 AM Simon Glass wrote:
> > > >
> > > > Hi Ilias,
> > > >
> > > > On Fri,
From: Quentin Schulz
This new image is similar to u-boot-rockchip.bin except that it's
destined to be flashed on SPI-NOR flashes.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
arch/arm/dts/rockchip-u-boot.dtsi | 29 +
1 file changed, 29 insertions(+)
diff
From: Quentin Schulz
Some image types handled by mkimage require the datafiles to be passed
independently (-d data1:data2) for specific handling of each. A
concatenation of datafiles prior to passing them to mkimage wouldn't
work.
That is the case for rksd and rkspi for example, which require
From: Quentin Schulz
This prepares for the creation of a u-boot-rockchip-spi.bin image
similar to u-boot-rockchip.bin to the exception it's destined for
SPI-NOR flashes instead of MMC storage medium.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
arch/arm/dts/rk3288-u-boot.dtsi | 2 +-
From: Quentin Schulz
By factoring SPL check in the first condition, this makes the checks a
bit less convoluted and more readable.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
Makefile | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/Makefile b/Makefile
From: Quentin Schulz
On MMC storage media, the TPL/SPL needs to be flashed at offset 32KB.
Instead of requesting the user to put the input the appropriate offsets,
let's create u-boot-rockchip.bin with the padding already added.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
From: Quentin Schulz
Since binman takes care of setting the appropriate offset for the SPL
payload, there's no need to define this variable anymore.
Moreover, it is technically incorrect since the padding is different
depending on whether the first stage bootloader is for a SPI flash or
MMC
From: Quentin Schulz
This allows to build u-boot-rockchip.bin binary with binman for Rockchip
ARM64 boards instead of the legacy Makefile way.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
Makefile | 28 ++--
arch/arm/Kconfig
From: Quentin Schulz
idbloader.img content - currently created by way of Makefile - can be
created by binman directly.
So let's do that for Rockchip ARM platforms.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
Makefile | 2 +-
From: Quentin Schulz
This migrates the generation of u-boot-rockchip.bin from Makefile to binman
completely. There is therefore no idbloader.img anymore as it is created on
the fly by binman.
This also adds support for generating the same kind of image than
u-boot-rockchip.bin but for SPI
From: "Andrew F. Davis"
Print statements in SPL depend on lib/common support, due to this many
such print statements are ifdef'd. Instead of checking at each call site
move the check to the common.h header and remove these inline checks.
Signed-off-by: Andrew F. Davis
Reviewed-by: Simon Glass
The first AM6x device was the AM654x, but being the first we named it
just AM6, since more devices have come out with this same prefix we
should switch it to the normal convention of using the full name of the
first compatibility device the series. This makes what device we are
talking about more
The content of these files are only used in SPL builds. The contents are
already ifdef for the same, remove that and only include the whole file
in the build when building for SPL.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/Makefile | 13 -
arch/arm/mach-k3/am625_init.c
Hello Andrey
> -Original Message-
> From: ZHIZHIKIN Andrey
> Sent: Friday, July 15, 2022 8:36 PM
> To: Gaurav Jain
> Cc: u-boot@lists.denx.de; feste...@denx.de; sba...@denx.de; Michael
> Walle ; Tommaso Merciai
> ; Michael Trimarchi
> ; Marek Vasut ; Simon
> Glass ; Patrick Delaunay
> ;
From: Quentin Schulz
While technically not a bug, let's have some consistency in paths
returned by u-boot,spl-boot-order look-up and the one saved in
u-boot,spl-boot-device by syncing spl_boot_devices_tbl and boot_devices
node paths.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
From: Quentin Schulz
On RK3399, mmc0 is eMMC and mmc1 is SD card, c.f. console:
MMC: mmc@fe32: 1, mmc@fe33: 0
In arch/arm/mach-rockchip/spl-boot-order.c:board_boot_order, the
boot_device (BOOT_DEVICE_*) value is gotten from spl_node_to_boot_device
function. Said function returns
From: Quentin Schulz
An earlier commit makes the common SPL code call
regulators_enable_boot_on and regulators_enable_boot_off before
iterating over possible boot media for U-Boot proper. There is therefore
no need to do this in the rk3399-specific code, so let's remove it.
Cc: Quentin Schulz
From: Quentin Schulz
This makes sure regulators that need to be turned on or off at boot are
turned on or off in the SPL.
This may be required for the SPL to do some operations, such as finding
possible loading media for U-Boot proper.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
-
Hi Andrey,
On Fri, Jul 15, 2022 at 12:06 PM ZHIZHIKIN Andrey
wrote:
> From what I can see, since patch from Fabio [2] is planned for inclusion to
> linux-5.20.y (see [3] for PR) - it might be that the SHA computation will stay
> broken on i.MX8M derivatives until v2022.10 at least, or the HW
From: Quentin Schulz
The check to perform is on CONFIG_SPL_GPIO and not SPL_GPIO.
Because this was never compiled in, it missed an include of cru.h that
was not detected before. Let's include it too.
Also switch to IS_ENABLED ifdef and in-code check.
Fixes: 07586ee4322a ("rockchip: rk3399:
From: Quentin Schulz
The check to perform is on CONFIG_SPL_DM_REGULATOR and not
SPL_DM_REGULATOR. Also switch to in-code check instead of ifdefs.
Fixes: 07586ee4322a ("rockchip: rk3399: Support common spl_board_init")
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
v2:
- use IS_ENABLED
Hello Gaurav,
Cc: Tom here for integration points.
> -Original Message-
> From: U-Boot On Behalf Of Gaurav Jain
> Sent: Friday, July 15, 2022 4:01 PM
> To: ZHIZHIKIN Andrey
> Cc: u-boot@lists.denx.de; feste...@denx.de; sba...@denx.de; Michael Walle
> ; Tommaso Merciai ;
> Michael
Add documentation for eficonfig command.
Signed-off-by: Masahisa Kojima
---
No change sinch v8
Changes in v8:
- command name is changed from "efimenu" to "eficonfig"
Newly created in v7
doc/usage/cmd/eficonfig.rst | 49 +
doc/usage/index.rst | 1 +
UEFI specification requires booting from removal media using
a architecture-specific default image name such as BOOTAA64.EFI.
This commit adds the removable media entries into bootmenu,
so that user can select the removable media and boot with
default image.
The bootmenu automatically enumerates
The bootmenu enumerates the UEFI boot options
for boot device selection.
This commit adds the description how the UEFI boot work
in bootmenu. This commit also adds "Synopsis", "Description"
and "Configuration" sections to follow the U-Boot command
documentation format.
Signed-off-by: Masahisa
This commit adds the menu entry to update UEFI BootOrder variable.
User moves the entry with UP/DOWN key, changes the order
with PLUS/MINUS key, then finalizes the order by ENTER key.
The U-Boot menu framework is well designed for static menu,
this commit implements the own menu display and key
This commit adds the menu entry to delete the UEFI boot option.
User moves the entry with UP/DOWN key, changes, then presses
ENTER key to delete the selected boot option.
Signed-off-by: Masahisa Kojima
---
Changes in v9:
- add function comment
Changes in v8:
- function and structure prefix is
This commit add the "eficonfig" command.
The "eficonfig" command implements the menu-driven UEFI boot option
maintenance feature. This commit implements the addition of
new boot option. User can select the block device volume having
efi_simple_file_system_protocol and select the file corresponding
This is preparation to support menu-driven UEFI BootOrder
variable updated by KEY_PLUS and KEY_MINUS.
Signed-off-by: Masahisa Kojima
Reviewed-by: Heinrich Schuchardt
---
No change since v7
Newly created in v7
common/menu.c | 6 ++
include/menu.h | 2 ++
2 files changed, 8 insertions(+)
This commit adds the menu entry to edit the existing
BOOT variable contents.
User selects the item from the boot option list, then
user can edit the description, file path and optional_data.
Note that automatically generated boot option entry by bootmenu
to support the removable media device
This is a preparation patch to provide the unified method
to access udevice pointer associated with the block io device.
The EFI handles of both EFI block io driver implemented in
lib/efi_loader/efi_disk.c and EFI block io driver implemented
as EFI payload can posess the udevice pointer in the
Let me resend this series because previous post did not contain
the version number of patches.
This series adds the menu-driven UEFI boot variable maintenance
through the "eficonfig" new command.
This series also adds the removable media support in bootmenu.
The python based test will follow
UEFI specification requires booting from removal media using
a architecture-specific default image name such as BOOTAA64.EFI.
This commit adds the removable media entries into bootmenu,
so that user can select the removable media and boot with
default image.
The bootmenu automatically enumerates
Add documentation for eficonfig command.
Signed-off-by: Masahisa Kojima
---
No change sinch v8
Changes in v8:
- command name is changed from "efimenu" to "eficonfig"
Newly created in v7
doc/usage/cmd/eficonfig.rst | 49 +
doc/usage/index.rst | 1 +
This commit adds the menu entry to delete the UEFI boot option.
User moves the entry with UP/DOWN key, changes, then presses
ENTER key to delete the selected boot option.
Signed-off-by: Masahisa Kojima
---
cmd/eficonfig.c | 76 +
1 file changed,
On 7/14/22 20:39, Sughosh Ganu wrote:
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 V6: None
The bootmenu enumerates the UEFI boot options
for boot device selection.
This commit adds the description how the UEFI boot work
in bootmenu. This commit also adds "Synopsis", "Description"
and "Configuration" sections to follow the U-Boot command
documentation format.
Signed-off-by: Masahisa
This commit add the "eficonfig" command.
The "eficonfig" command implements the menu-driven UEFI boot option
maintenance feature. This commit implements the addition of
new boot option. User can select the block device volume having
efi_simple_file_system_protocol and select the file corresponding
This commit adds the menu entry to update UEFI BootOrder variable.
User moves the entry with UP/DOWN key, changes the order
with PLUS/MINUS key, then finalizes the order by ENTER key.
The U-Boot menu framework is well designed for static menu,
this commit implements the own menu display and key
This is preparation to support menu-driven UEFI BootOrder
variable updated by KEY_PLUS and KEY_MINUS.
Signed-off-by: Masahisa Kojima
Reviewed-by: Heinrich Schuchardt
---
No change since v7
Newly created in v7
common/menu.c | 6 ++
include/menu.h | 2 ++
2 files changed, 8 insertions(+)
This commit adds the menu entry to edit the existing
BOOT variable contents.
User selects the item from the boot option list, then
user can edit the description, file path and optional_data.
Note that automatically generated boot option entry by bootmenu
to support the removable media device
This is a preparation patch to provide the unified method
to access udevice pointer associated with the block io device.
The EFI handles of both EFI block io driver implemented in
lib/efi_loader/efi_disk.c and EFI block io driver implemented
as EFI payload can posess the udevice pointer in the
This series adds the menu-driven UEFI boot variable maintenance
through the "eficonfig" new command.
This series also adds the removable media support in bootmenu.
The python based test will follow this series.
Source code can be cloned with:
$ git clone
On Tue, 12 Jul 2022 at 19:59, Masahisa Kojima
wrote:
>
> On Sun, 10 Jul 2022 at 18:03, Heinrich Schuchardt wrote:
> >
> > On 6/19/22 06:56, Masahisa Kojima wrote:
> > > This commit add the "eficonfig" command.
> > > The "eficonfig" command implements the menu-driven UEFI boot option
> > >
When programming qspi flash speed we need to check the requested flash
speed not to exceed the spi max frequency. In the current implementation
we are checking qspi ref clk instead. This commit fixes the issue by
checking the requested speed and programs the specified max frequency.
Add support_ops function zynq_qspi_mem_exec_op to check controller
supported operations by spi-mem framework. Current default support ops
function does not allow dummy buswidth no more than 1, unless we are
using buswidth is 4 for TX.
Signed-off-by: Ashok Reddy Soma
---
drivers/spi/zynq_qspi.c
From: T Karthik Reddy
Fix dummy bytes calculation incase of valid dummy bytes when dummy
buswidth is > 1. Current dummy bytes calculation does not provide
correct dummy values for dummy buswidth > 1.
Signed-off-by: T Karthik Reddy
Signed-off-by: Ashok Reddy Soma
---
drivers/spi/zynq_qspi.c
From: Siva Durga Prasad Paladugu
Add child pre probe function in the driver. Update max_hz of priv from
spi_slave structure.
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Ashok Reddy Soma
---
drivers/spi/zynq_qspi.c | 12
1 file changed, 12 insertions(+)
diff --git
This patch series does below things
- Add child preprobe function
- Use dummy buswidth in dummy byte calculation
- Add support for zynq_qspi_mem_exec_op
- Fix qspi speed issue
Ashok Reddy Soma (2):
spi: zynq_qspi: Add support for zynq_qspi_mem_exec_op
spi: zynq_qspi: Fix programming
Hello Andrey
Right now I am not sure what could cause the issue.
As per our previous discussions, JR0 can not be used in uboot, so you need to
mark it as disabled until kernel device tree is not sync.
To debug more, can you run hash command with HASH_VERIFY.
Regards
Gaurav Jain
> -Original
Hi Sughosh,
On Thu, 14 Jul 2022 at 21:40, Sughosh Ganu wrote:
>
> 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.
Hello Gaurav,
> -Original Message-
> From: U-Boot On Behalf Of Gaurav Jain
> Sent: Friday, July 15, 2022 2:56 PM
> To: ZHIZHIKIN Andrey
> Cc: u-boot@lists.denx.de; feste...@denx.de; sba...@denx.de; Michael Walle
> ; Tommaso Merciai ;
> Michael Trimarchi ; Marek Vasut ;
> Simon Glass ;
Hello Andrey
There is a patch in review related caam hash.
Please check if it fixes your problem.
http://patchwork.ozlabs.org/project/uboot/patch/20220616101009.809953-1-gaurav.j...@nxp.com/
Regards
Gaurav Jain
> -Original Message-
> From: ZHIZHIKIN Andrey
> Sent: Friday, July 15, 2022
Hello Gaurav,
In the new v2022.07, I've stumbled upon the issue with calculating the SHA256 of
memory blocks with CAAM hashing. This causes the FIT image not to pass the hash
validation, and also `sha256` command not operable.
I'm also wondering if any i.MX8M-based board maintainers have seen
HI,
Am Fr., 15. Juli 2022 um 13:18 Uhr schrieb Fabio Estevam :
>
> Hi Heiko,
>
> On Fri, Jul 15, 2022 at 5:33 AM Heiko Thiery wrote:
>
> > Error binding driver 'serial_mxc': -12
>
> Does the attached patch help?
Unfortunately not .. I think the problem is not the SPL. Since the SPL
does not use
Hi Sughosh,
[...]
> #endif /* CONFIG_EFI_CAPSULE_AUTHENTICATE */
>
> +static bool fwu_empty_capsule(struct efi_capsule_header *capsule)
> +{
> + return !guidcmp(>capsule_guid,
> + _guid_os_request_fw_revert) ||
> + !guidcmp(>capsule_guid,
> +
Am Fr., 15. Juli 2022 um 13:35 Uhr schrieb Fabio Estevam :
>
> On Fri, Jul 15, 2022 at 8:18 AM Fabio Estevam wrote:
> >
> > Hi Heiko,
> >
> > On Fri, Jul 15, 2022 at 5:33 AM Heiko Thiery wrote:
> >
> > > Error binding driver 'serial_mxc': -12
> >
> > Does the attached patch help?
>
> Also, try
On Fri, Jul 15, 2022 at 8:18 AM Fabio Estevam wrote:
>
> Hi Heiko,
>
> On Fri, Jul 15, 2022 at 5:33 AM Heiko Thiery wrote:
>
> > Error binding driver 'serial_mxc': -12
>
> Does the attached patch help?
Also, try increasing CONFIG_SYS_SPL_MALLOC_SIZE.
Hi Heiko,
On Fri, Jul 15, 2022 at 5:33 AM Heiko Thiery wrote:
> Error binding driver 'serial_mxc': -12
Does the attached patch help?
From 93d2c1604f644e6362cb5dc4c434d32f3a06 Mon Sep 17 00:00:00 2001
From: Fabio Estevam
Date: Fri, 15 Jul 2022 08:11:03 -0300
Subject: [PATCH]
On Tue, Jul 12, 2022 at 05:34:15PM -0400, Tom Rini wrote:
> For quite a long time we've been using a 3 week, rather than 2 week,
> merge window as it was only 2 weeks during the timeframe where we did 2
> month rather than 3 month releases. This corrects the places that still
> had 2 weeks and
On Tue, Jul 12, 2022 at 05:34:14PM -0400, Tom Rini wrote:
> Migrate the RelaseCycle wiki page to Sphinx. In terms of visible
> changes, we stop having a dynamic countdown to when the release is. And
> we drop the year-based statistics, that were not being kept up to date.
> For the moment, we
On Thu, Jul 14, 2022 at 08:07:40AM -0400, Tom Rini wrote:
> Move the current CodingStyle wiki page to doc/develop/codingstyle.rst.
> The changes here are for formatting or slight rewording so that it reads
> well when linking to other Sphinx documents.
>
> Cc: Heinrich Schuchardt
>
On Thu, Jul 14, 2022 at 05:05:00PM +0200, Marek Vasut wrote:
> The following changes since commit 36b661dc919da318c163a45f4a220d2e3d9db608:
>
> Merge branch 'next' (2022-07-11 14:58:57 -0400)
>
> are available in the Git repository at:
>
> git://source.denx.de/u-boot-usb.git master
>
>
On 7/13/22 03:38, Kunihiko Hayashi wrote:
Since the calulation of "bgen" is rounded down, using a higher
baudrate will result in a larger difference from the actual
baudrate. Should use DIV_ROUND_CLOSEST() like the Linux driver.
Signed-off-by: Kunihiko Hayashi
---
On 7/15/22 12:05, Heiko Thiery wrote:
Hi Marek
Am Fr., 15. Juli 2022 um 11:29 Uhr schrieb Marek Vasut :
On 7/15/22 10:33, Heiko Thiery wrote:
Hi,
Hi,
I see since the change to CLK_IMX8MQ that the kontron_pitx_imx8m board
does not start anymore. I have enabled the DUBUG_UART and see the
On Thu, 14 Jul 2022 at 23:57, Stephan Gerhold wrote:
>
> On Thu, Jul 14, 2022 at 01:10:45PM +0530, Sumit Garg wrote:
> > On Thu, 14 Jul 2022 at 01:02, Stephan Gerhold wrote:
> > > Can you check how hard it would be to reuse the upstream QCS404 DT?
> > >
> >
> > It turned out to be patch [1] on
On Thu, 14 Jul 2022 at 21:40, Sughosh Ganu wrote:
>
> 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
> ---
> Changes since V6: None
>
> cmd/Kconfig | 7 +
> cmd/Makefile| 1 +
>
1 - 100 of 150 matches
Mail list logo
