The commit 2158b0da220c ("bootmenu: add Kconfig option
not to enter U-Boot console") disables to enter U-Boot
console from bootmenu as default, this change affects the
existing bootmenu users.
This commit reverts the default behavior, the bootmenu can
enter U-Boot console same as before.
CMD_BOOTM
The commit a3d0aa87acbe ("bootmenu: update bootmenu_entry structure")
changes the bootmenu title type from char to u16(UTF16 string)
to support EFI based system. If EFI_LOADER is not enabled,
printf("%ls") is not supported, so bootmenu does not appear
correctly.
This commit changes the type of men
This series fixes the issue in bootmenu after adding efi entries.
Masahisa Kojima (2):
bootmenu: use utf-8 for menu title
bootmenu: U-Boot console is enabled as default
boot/Kconfig | 7 +++
cmd/Kconfig| 10 --
cmd/bootmenu.c | 48 ++
On 5/28/22 15:02, Jan Kiszka wrote:
From: Jan Kiszka
This completes what 890feecaab72 started by selecting ENV_APPEND and
ENV_IS_NOWHERE and by moving this driver to top if the list. This
s@if the list@of the list@
ensures that load operations pick up both the default env and the
permitted
On Sat, 28 May 2022 at 17:37, Heinrich Schuchardt wrote:
>
> On 5/26/22 12:09, Masahisa Kojima wrote:
> > The commit a3d0aa87acbe ("bootmenu: update bootmenu_entry structure")
> > changes the bootmenu title type from char to u16(UTF16 string)
> > to support EFI based system. If EFI_LOADER is not e
CONFIG_SPL_BOOT_DEVICE was made obsolete by
CONFIG_MVEBU_SPL_BOOT_DEVICE_{SPI,MMC,SATA,UART}.
CONFIG_MVEBU_SPL_BOOT_DEVICE_SPI is the default so existing users of
CONFIG_SPL_BOOT_DEVICE can simply have the option removed.
Signed-off-by: Chris Packham
---
include/configs/controlcenterdc.h | 11 -
CONFIG_FIXED_SDHCI_ALIGNED_BUFFER is needed on some Marvell SoCs when
booting from MMC. All existing usages of this have the same value so
make this the default and have the Kconfig option depend on SPL &&
MVEBU_SPL_BOOT_DEVICE_MMC.
Signed-off-by: Chris Packham
---
drivers/mmc/Kconfig
Update the way KWB_CFG_SEC_BOOT_DEV is determined to use
CONFIG_MVEBU_SPL_BOOT_DEVICE_{SPI,MMC} instead of
CONFIG_SPL_BOOT_DEVICE.
Signed-off-by: Chris Packham
---
arch/arm/mach-mvebu/Makefile | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-mvebu/Mak
On Sun, May 29, 2022 at 10:07:20AM +1200, Chris Packham wrote:
> On Sun, May 29, 2022 at 9:37 AM Tom Rini wrote:
> >
> > On Sun, May 29, 2022 at 09:35:59AM +1200, Chris Packham wrote:
> > > Hi Tom,
> > >
> > > On Sun, 29 May 2022, 4:52 AM Tom Rini, wrote:
> > >
> > > > Hey folks,
> > > >
> > > >
On Sun, May 29, 2022 at 9:37 AM Tom Rini wrote:
>
> On Sun, May 29, 2022 at 09:35:59AM +1200, Chris Packham wrote:
> > Hi Tom,
> >
> > On Sun, 29 May 2022, 4:52 AM Tom Rini, wrote:
> >
> > > Hey folks,
> > >
> > > As part of converting outstanding CONFIG symbols to Kconfig, I've run in
> > > to C
On Sun, May 29, 2022 at 09:35:59AM +1200, Chris Packham wrote:
> Hi Tom,
>
> On Sun, 29 May 2022, 4:52 AM Tom Rini, wrote:
>
> > Hey folks,
> >
> > As part of converting outstanding CONFIG symbols to Kconfig, I've run in
> > to CONFIG_SPL_BOOT_DEVICE and while I think I see how to do it, it
> >
Hi Tom,
On Sun, 29 May 2022, 4:52 AM Tom Rini, wrote:
> Hey folks,
>
> As part of converting outstanding CONFIG symbols to Kconfig, I've run in
> to CONFIG_SPL_BOOT_DEVICE and while I think I see how to do it, it
> would be better I think if someone that has the hardware and can test
> the logic
Hey folks,
As part of converting outstanding CONFIG symbols to Kconfig, I've run in
to CONFIG_SPL_BOOT_DEVICE and while I think I see how to do it, it
would be better I think if someone that has the hardware and can test
the logic out, does it.
In short, I believe we need to:
- SPL_BOOT_SPI_NOR_F
From: Jan Kiszka
Add hashes and configuration signature stubs to prepare verified boot
of main U-Boot by SPL.
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/dts/k3-am65-iot2050-boot-image
From: Su Baocheng
Due to different signature keys, the PG1 and the PG2 boards can no
longer use the same FSBL (tiboot3). This makes it impossible anyway to
maintaine a single flash.bin for both variants, so we can also split the
build.
A new target is added to indicates the build is for PG1 vs.
From: Jan Kiszka
Allows run-time control over watchdog auto-start and the timeout via
setting the environment variable watchdog_timeout_ms. A value of zero
means "do not start". Use CONFIG_WATCHDOG_TIMEOUT_MSECS as initial value
and this to zero by default. Users can then enable the watchdog once
From: Jan Kiszka
Use external blob otpcmd.bin to replace the 0xff filled OTP programming
command block to create a firmware image that provisions the OTP on
first boot. This otpcmd.bin is generated from the customer keys using
steps described in the meta-iot2050 integration layer for the device.
From: Jan Kiszka
This is enabled by default, thus should be described as well.
Signed-off-by: Jan Kiszka
---
doc/board/siemens/iot2050.rst | 4
1 file changed, 4 insertions(+)
diff --git a/doc/board/siemens/iot2050.rst b/doc/board/siemens/iot2050.rst
index cb49a0e36bf..efe94a448a9 100644
From: Jan Kiszka
There are many ways to get a signed firmware for the IOT2050 devices,
namely for the parts under user-control. This script documents one way
of doing it, given a signing key. Augment the board documentation with
the required procedure around it.
Signed-off-by: Jan Kiszka
---
d
From: Jan Kiszka
Boards may set networking variables programmatically, thus may have
CONFIG_NET on but CONFIG_CMD_NET off. The IOT2050 is an example.
CC: Joe Hershberger
Signed-off-by: Jan Kiszka
---
env/flags.c | 10 +-
include/env_flags.h | 4 ++--
2 files changed, 7 insert
From: Su Baocheng
Refactor according to the entry `fit: Entry containing a FIT` of
document tools/binman/README.entries.
As the generator uses the device tree name for the config description,
board_fit_config_name_match requires a small adjustment as well.
Signed-off-by: Su Baocheng
[Jan: re-a
From: Jan Kiszka
Will be needed when CONFIG_ENV_WRITEABLE_LIST is enabled. The listed
variables shall remain writable, for informational purposes - they have
to be considered untrusted because the persistent U-Boot env is not
protected.
Signed-off-by: Jan Kiszka
---
include/configs/iot2050.h |
From: Jan Kiszka
The latest version of the binary-only firmware parts come in a combined
form of FSBL and sysfw containers. This implies some layout changes to
the generated firmware image but also makes handling of artifacts much
simpler (4 files less). The env locations will not change, just th
From: Jan Kiszka
Allows to create a public key device tree dtsi for inclusion into U-Boot
SPL and proper during first build already. This can be achieved via
CONFIG_DEVICE_TREE_INCLUDES.
Signed-off-by: Jan Kiszka
---
tools/key2dtsi.py | 64 +++
1 fil
From: Jan Kiszka
This completes what 890feecaab72 started by selecting ENV_APPEND and
ENV_IS_NOWHERE and by moving this driver to top if the list. This
ensures that load operations pick up both the default env and the
permitted parts of the next-prio location. When writing though, we must
not use
Flushing our upstream queue for the IOT2050 device, this mostly brings
board-specific changes such as:
- updated build process and firmware layout for PG1 vs. PG2 devices
- more watchdog preparations
- preparations for verified boot on IOT2050 Advanced devices
There are also some generic exten
On 02.03.22 15:01, Jan Kiszka wrote:
> Changes in v6:
> - fixed embarrassingly inverted logic in unlock check
>(and properly tested it this time)
>
> Changes in v5:
> - adjust unused is_locked callback to our is_unlocked needs
> - use this callback in sf command instead
>
> Jan
>
> Jan Ki
On Fri, May 27, 2022 at 09:30:49AM -0400, Tom Rini wrote:
> On Fri, May 27, 2022 at 02:36:29AM +, Leo Liang wrote:
>
> > Hi Tom,
> >
> > The following changes since commit 7e0edcadb09d55d5319fdc862041fd1b874476f5:
> >
> > Merge branch 'master' of
> > https://source.denx.de/u-boot/custodi
On 5/26/22 12:09, Masahisa Kojima wrote:
The commit a3d0aa87acbe ("bootmenu: update bootmenu_entry structure")
changes the bootmenu title type from char to u16(UTF16 string)
to support EFI based system. If EFI_LOADER is not enabled,
printf("%ls") is not supported, so bootmenu does not appear
corr
On 5/27/22 15:25, Sean Anderson wrote:
On 5/27/22 3:14 AM, Heinrich Schuchardt wrote:
On 5/27/22 05:36, Sean Anderson wrote:
This document some additional options which can be used with
valgrind, as
Thanks for enhancing this document
nits
%s/document/documents/
well as directions for futur
On 5/27/22 16:03, Sean Anderson wrote:
There are no defined instruction sequences in include/valgrind.h for
Risc-V, so CONFIG_VALGRIND will do nothing on this arch (and possibly won't
compile?). Update Kconfig accordingly.
RISC-V support for valgrind has not been merged upstream yet but is
unde
31 matches
Mail list logo
