est master
- reworked patch 1 to be less invasive to the code
- added "iot2050: use the named gpio to control the user-button"
Jan
CC: chao zeng
CC: Su Baocheng
Jan Kiszka (11):
iot2050: Update firmware layout
iot2050: Migrate settings into board env file
iot2050: Add watch
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
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
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
From: Jan Kiszka
Anything that is not boot-env related is better kept there by now.
At this chance, also drop a stale comment from iot2050.h
Signed-off-by: Jan Kiszka
---
board/siemens/iot2050/iot2050.env | 9 +
include/configs/iot2050.h | 11 ++-
2 files changed, 11
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 th
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
On 13.02.23 05:26, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 7 Feb 2023 at 11:39, Simon Glass wrote:
>>
>> Hi Jan,
>>
>> On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
>>>
>>> On 07.02.23 16:28, Simon Glass wrote:
>>>> H
On 07.02.23 16:28, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
>>
>> On 06.02.23 11:47, Jan Kiszka wrote:
>>> On 04.02.23 23:26, Simon Glass wrote:
>>>> Hi Jan,
>>>>
>>>> On Fri, 3 Feb 2023 at
On 07.02.23 05:02, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 05:23, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> This completes what 890feecaab72 started by selecting ENV_APPEND and
>> loading the default env before any other sources. This
On 07.02.23 05:02, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 6 Feb 2023 at 03:42, Jan Kiszka wrote:
>>
>> On 04.02.23 23:23, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>>>
>>>> O
On 06.02.23 11:47, Jan Kiszka wrote:
> On 04.02.23 23:26, Simon Glass wrote:
>> Hi Jan,
>>
>> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>>
>>> On 03.02.23 19:51, Tom Rini wrote:
>>>> On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wr
On 04.02.23 23:26, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>
>> On 03.02.23 19:51, Tom Rini wrote:
>>> On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
>>>
>>>> From: Jan Kiszka
>>>
On 06.02.23 11:42, Jan Kiszka wrote:
> On 04.02.23 23:23, Simon Glass wrote:
>> Hi Jan,
>>
>> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>>
>>> On 04.02.23 01:20, Simon Glass wrote:
>>>> Hi Jan,
>>>>
>>>> O
On 04.02.23 23:23, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>
>> On 04.02.23 01:20, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 3 Feb 2023 at 05:29, Jan Kiszka wrote:
>>>>
>>>> Fr
On 18.01.23 09:11, Yanhong Wang wrote:
> This series of patches base on the latest branch/master, and add support
> for the StarFive JH7110 RISC-V SoC and VisionFive V2 board. In order for
> this to be achieved, the respective DT nodes have been added, and the
> required defconfigs have been added
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
From: chao zeng
User-button is controlled by the mcu domain gpio number 25.
But main0 main1 mcu domain all have gpio number 25.
To identify where the gpio is from, Using gpio controll base as the prefix
to indicate the gpio resource.
Signed-off-by: chao zeng
---
board/siemens/iot2050/board.c
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 feature is desired on the platform.
Signed-off-by: Jan Kiszka
---
configs/iot2050_pg1_defconfig | 6 +++---
configs/iot2050_pg2_defconfig | 7 +++
2 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/configs/iot2050_pg1_defconfig b/configs
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
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
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 th
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
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
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
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
Anything that is not boot-env related is better kept there by now.
At this chance, also drop a stale comment from iot2050.h
Signed-off-by: Jan Kiszka
---
board/siemens/iot2050/iot2050.env | 9 +
include/configs/iot2050.h | 11 ++-
2 files changed, 11
re under review
now.
Jan
CC: chao zeng
CC: Su Baocheng
Jan Kiszka (10):
iot2050: Update firmware layout
iot2050: Migrate settings into board env file
iot2050: Add watchdog start to bootcmd
iot2050: Add CFG_ENV_FLAGS_LIST_STATIC
arm: dts: iot2050: Allow verifying U-Boot proper
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
On 03.02.23 19:51, Tom Rini wrote:
> On Fri, Feb 03, 2023 at 01:26:33PM +0100, Jan Kiszka wrote:
>
>> 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 zer
On 04.02.23 01:20, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 05:29, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> Allows to create a public key device tree dtsi for inclusion into U-Boot
>> SPL and proper during first
On 03.02.23 19:52, Tom Rini wrote:
> On Fri, Feb 03, 2023 at 01:26:34PM +0100, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Will be needed when CONFIG_ENV_WRITEABLE_LIST is enabled. The listed
>> variables shall remain writable, for informational purposes - they have
&g
On 03.02.23 19:51, Tom Rini wrote:
> On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
>
>> 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 o
On 03.02.23 13:37, Lothar Waßmann wrote:
> Hi,
>
> On Fri, 3 Feb 2023 13:26:38 +0100 Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Use external blob otpcmd.bin to replace the 0xff filled OTP programming
>> command block to create a firmware image that provisio
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 feature is desired on the platform.
Signed-off-by: Jan Kiszka
---
configs/iot2050_pg1_defconfig | 6 +++---
configs/iot2050_pg2_defconfig | 7 +++
2 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/configs/iot2050_pg1_defconfig b/configs
From: chao zeng
User-button is controlled by the mcu domain gpio number 25.
But main0 main1 mcu domain all have gpio number 25.
To identify where the gpio is from, Using gpio controll base as the prefix
to indicate the gpio resource.
Signed-off-by: chao zeng
---
board/siemens/iot2050/board.c
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
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
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
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
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
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
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
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 th
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
rt for a new variant that comes with M.2
slots. Related DT patches were sent to the kernel and are under review
now.
Jan
CC: chao zeng
CC: Su Baocheng
Jan Kiszka (9):
iot2050: Update firmware layout
iot2050: Add watchdog start to bootcmd
iot2050: Add CONFIG_ENV_FLAGS_LIST_STATIC
arm:
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
From: Jan Kiszka
This completes what 890feecaab72 started by selecting ENV_APPEND and
loading the default env before any other sources. This ensures that load
operations pick up all non-writable vars from the default env and only
permitted parts from other locations according to the regular
This was factored out of [1] upon request in the hope of easing the
merge.
Jan
[1] https://lore.kernel.org/u-boot/cover.1675325279.git.jan.kis...@siemens.com
CC: Joe Hershberger
CC: Marek Vasut
CC: Stefan Herbrechtsmeier
Jan Kiszka (2):
env: Complete generic support for writable list
On 02.02.23 13:48, Marek Vasut wrote:
> On 2/2/23 09:07, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This completes what 890feecaab72 started by selecting ENV_APPEND and
>> loading the default env before any other sources. This ensures that load
>> operations p
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
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
From: Jan Kiszka
This feature is desired on the platform.
Signed-off-by: Jan Kiszka
---
configs/iot2050_pg1_defconfig | 6 +++---
configs/iot2050_pg2_defconfig | 7 +++
2 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/configs/iot2050_pg1_defconfig b/configs
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
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
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
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
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 th
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
From: chao zeng
User-button is controlled by the mcu domain gpio number 25.
But main0 main1 mcu domain all have gpio number 25.
To identify where the gpio is from, Using gpio controll base as the prefix
to indicate the gpio resource.
Signed-off-by: chao zeng
---
board/siemens/iot2050/board.c
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
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
From: Jan Kiszka
This completes what 890feecaab72 started by selecting ENV_APPEND and
loading the default env before any other sources. This ensures that load
operations pick up all non-writable vars from the default env and only
permitted parts from other locations according to the regular
e the named gpio to control the user-button"
Still in our backlog is support for a new variant that comes with M.2
slots. Related DT patches were sent to the kernel and are under review
now.
Jan
CC: chao zeng
CC: Joe Hershberger
CC: Marek Vasut
CC: Stefan Herbrechtsmeier
CC: Su Baocheng
Changes to v4:
- move cursor to bottom-right before scrolling
Jan
Jan Kiszka (2):
efi_loader: Avoid overwriting previous outputs on console screen
clearing
efi_loader: Set default console colors on efi_cout_clear_screen if
needed
lib/efi_loader/Kconfig | 9 +
lib
From: Jan Kiszka
Before clearing the screen, ensure that no previous output of firmware
or UEFI programs will be overwritten on serial devices or other
streaming consoles. This helps generating complete boot logs.
Tested regarding multi-output against qemu-x86_defconfig. Still, there
were
From: Jan Kiszka
Ensures a consistent background color of the whole screen for succeeding
outputs as both demanded by the spec and implemented in EDK2 as well.
Signed-off-by: Jan Kiszka
---
lib/efi_loader/efi_console.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/lib/efi_loader
On 18.01.23 22:02, Heinrich Schuchardt wrote:
>
>
> Am 18. Januar 2023 21:58:42 MEZ schrieb Jan Kiszka :
>> On 18.01.23 21:56, Heinrich Schuchardt wrote:
>>>
>>>
>>> Am 18. Januar 2023 21:44:58 MEZ schrieb Jan Kiszka :
>>>> From: Jan Kiszka
On 18.01.23 21:56, Heinrich Schuchardt wrote:
>
>
> Am 18. Januar 2023 21:44:58 MEZ schrieb Jan Kiszka :
>> From: Jan Kiszka
>>
>> Before clearing the screen, ensure that no previous output of firmware
>> or UEFI programs will be overwritten on serial devic
From: Jan Kiszka
Before clearing the screen, ensure that no previous output of firmware
or UEFI programs will be overwritten on serial devices or other
streaming consoles. This helps generating complete boot logs.
Tested regarding multi-output against qemu-x86_defconfig. Still, there
were
Changes to earlier versions:
- dropped merged "Let networking support depend on NETDEVICES"
- made scrolling on clear-screen a Kconfig option
Jan
Jan Kiszka (2):
efi_loader: Avoid overwriting previous outputs on console screen
clearing
efi_loader: Set default console
From: Jan Kiszka
Ensures a consistent background color of the whole screen for succeeding
outputs as both demanded by the spec and implemented in EDK2 as well.
Signed-off-by: Jan Kiszka
---
lib/efi_loader/efi_console.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/lib/efi_loader
> static int sst_write_byteprogram(struct spi_nor *nor, loff_t to, size_t len,
Indeed...
Reviewed-by: Jan Kiszka
Hope you were also able to test this on real HW (which I wasn't).
Thanks,
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
On 07.11.22 18:18, Heinrich Schuchardt wrote:
> On 11/7/22 17:41, Jan Kiszka wrote:
>> On 07.11.22 17:29, Heinrich Schuchardt wrote:
>>> On 11/4/22 09:06, Jan Kiszka wrote:
>>>> From: Jan Kiszka
>>>>
>>>> Before clearing the screen, ensure tha
On 07.11.22 18:06, Heinrich Schuchardt wrote:
> On 11/4/22 09:06, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Ensures a consistent background color of the whole screen for succeeding
>> outputs as both demanded by the spec and implemented in EDK2 as well.
>
> T
On 04.11.22 09:06, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Ensures a consistent background color of the whole screen for succeeding
> outputs as both demanded by the spec and implemented in EDK2 as well.
>
> Signed-off-by: Jan Kiszka
> ---
> lib/efi_loader/efi_consol
On 07.11.22 17:29, Heinrich Schuchardt wrote:
> On 11/4/22 09:06, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Before clearing the screen, ensure that no previous output of firmware
>> or UEFI programs will be overwritten on serial devices or other
>> streamin
On 04.11.22 20:08, Simon Glass wrote:
> Hi,
>
> On Fri, 4 Nov 2022 at 02:07, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> Before clearing the screen, ensure that no previous output of firmware
>> or UEFI programs will be overwritten on serial devices or
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 th
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
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
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
From: chao zeng
User-button is controlled by the mcu domain gpio number 25.
But main0 main1 mcu domain all have gpio number 25.
To identify where the gpio is from, Using gpio controll base as the prefix
to indicate the gpio resource.
Signed-off-by: chao zeng
---
board/siemens/iot2050/board.c
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
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
From: Jan Kiszka
This completes what 890feecaab72 started by selecting ENV_APPEND and
loading the default env before any other sources. This ensures that load
operations pick up all non-writable vars from the default env and only
permitted parts from other locations according to the regular
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
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
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
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
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
that comes with M.2
slots.
Jan
CC: chao zeng
CC: Joe Hershberger
CC: Marek Vasut
CC: Stefan Herbrechtsmeier
CC: Su Baocheng
Jan Kiszka (10):
env: Complete generic support for writable list
env: Couple networking-related variable flags to CONFIG_NET
tools: Add script for converting publi
From: Jan Kiszka
CONFIG_NET does not imply that there are actually network devices
available. Neither does CONFIG_NETDEVICES, but it is much closer, and
changing to this dependency obsoletes the check in Kconfig because it
means DM_ETH.
Along this change, make sure that efi_net_set_dhcp_ack is
From: Jan Kiszka
Before clearing the screen, ensure that no previous output of firmware
or UEFI programs will be overwritten on serial devices or other
streaming consoles. This helps generating complete boot logs.
Tested regarding multi-output against qemu-x86_defconfig.
Signed-off-by: Jan
write protection and background color fix
- addressed missing efi_net_set_dhcp_ack symbol
- converted some #ifdefs to CONFIG_IS_ENABLED
Jan
Jan Kiszka (3):
efi_loader: Avoid overwriting previous outputs on console screen
clearing
efi_loader: Set default console colors on efi_cout_clear_
From: Jan Kiszka
Ensures a consistent background color of the whole screen for succeeding
outputs as both demanded by the spec and implemented in EDK2 as well.
Signed-off-by: Jan Kiszka
---
lib/efi_loader/efi_console.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/lib/efi_loader
101 - 200 of 717 matches
Mail list logo
