On Wed, Feb 21, 2024 at 11:57:51AM +0530, Sumit Garg wrote:
> On Tue, 20 Feb 2024 at 21:02, Marek Vasut wrote:
> > On 2/20/24 14:10, Sumit Garg wrote:
> > > Also, enable reset driver which is a prerequisite for PCIe support.
> > Commit message needs to be fixed.
>
> Let me reiterate the header he
On 2/22/24 21:05, Sean Anderson wrote:
Currently, when we boot from JTAG we try to boot U-Boot from RAM.
However, this is a bit tricky to time, since the debugger has to wait
for SPL to initialize RAM before it can load U-Boot. This can result in
long waits, since occasionally initializing RAM
On Sat, 3 Feb 2024 at 18:38, Raymond Mao wrote:
>
> Save boot arguments x[0-3] into an array for handover of bloblist from
> previous boot stage.
>
> Signed-off-by: Raymond Mao
> Suggested-by: Ard Biesheuvel
> ---
> Changes in v2
> - New patch file created for v2.
> Changes in V5
> - Drop the de
On Sat, 3 Feb 2024 at 18:37, Raymond Mao wrote:
>
> Save boot arguments r[0-3] into an array for handover of bloblist from
> previous boot stage.
>
> Signed-off-by: Raymond Mao
> Suggested-by: Ard Biesheuvel
> ---
> Changes in v2
> - New patch file created for v2.
> Changes in v3
> - Swap value
Add boot ROM XSPI bootmode, and set to BOOT_DEVICE_SPI if detected.
Signed-off-by: Jonathan Humphreys
---
arch/arm/mach-k3/include/mach/j721e_spl.h | 5 +++--
arch/arm/mach-k3/j721e_init.c | 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-k3/includ
This series enables OSPI storage and boot.
fixes: 58d61fb5a77ef31f6aa5973b3ef9650c92edf5ed ("arm: dts: k3-j721e-sk: Add
initial A72 specific dts support")
Jonathan Humphreys (2):
configs: j721e: Enable OSPI memory
arm: mach-k3: j721e: Enable OSPI boot
arch/arm/mach-k3/include/mach/j721e_sp
Set config values to enable OSPI functionality.
Signed-off-by: Jonathan Humphreys
---
configs/j721e_evm_a72_defconfig | 7 +++
configs/j721e_evm_r5_defconfig | 6 ++
2 files changed, 13 insertions(+)
diff --git a/configs/j721e_evm_a72_defconfig b/configs/j721e_evm_a72_defconfig
index 7
On 2/22/24 17:18, Bob Wolff wrote:
If mixed rsa and ecdsa keys are specified in dtsi, an rsa key can be sent
into the ecdsa verify. Without the ecdsa,curve property, this function will
crash due to lack of checking the null pointer return.
nit: there should be a blank line here
Signed-off-by:
Peter,
Thanks for helping lead me down the right path here.
WRT tinycrypt, the license is quite permissive.
https://github.com/intel/tinycrypt
Also, I'd like your advice - I was thinking for the larger patch that I'd
do it in two commits. The first would be the addition of the tinycrypt
files and
If mixed rsa and ecdsa keys are specified in dtsi, an rsa key can be sent
into the ecdsa verify. Without the ecdsa,curve property, this function will
crash due to lack of checking the null pointer return.
Signed-off-by: Bob Wolff
---
lib/ecdsa/ecdsa-verify.c | 5 +
1 file changed, 5 insertio
Currently, when we boot from JTAG we try to boot U-Boot from RAM.
However, this is a bit tricky to time, since the debugger has to wait
for SPL to initialize RAM before it can load U-Boot. This can result in
long waits, since occasionally initializing RAM (and other things in
psu_init) takes a long
On 2/22/24 14:36, Fabio Estevam wrote:
> On Thu, Feb 22, 2024 at 1:53 PM Sean Anderson wrote:
>>
>> From: Sean Anderson
> ...
>> Signed-off-by: Sean Anderson
>> ---
>> I'm resending this from my linux.dev email as my regular email is
>> mangling my patches.
>
> That's OK, but you need to make s
On Thu, Feb 22, 2024 at 1:53 PM Sean Anderson wrote:
>
> From: Sean Anderson
...
> Signed-off-by: Sean Anderson
> ---
> I'm resending this from my linux.dev email as my regular email is
> mangling my patches.
That's OK, but you need to make sure that the From and Signed-off-by
fields match.
Ot
Hi all,
On 2/21/24 18:07, Quentin Schulz wrote:
From: Quentin Schulz
This adds support for the SARADCv2 found on RK3588.
There is no stop callback as it is currently configured in single
conversion mode, where the ADC is powered down after a single conversion
has been made.
Cc: Quentin Schul
On Mon, Feb 19, 2024 at 06:18:38PM +, Ivan Orlov wrote:
> We should have CONFIG_DM_I2C or CONFIG_(SPL_)SYS_I2C_LEGACY enabled in
> order for `cmd/eeprom.c` to compile as it depends on the i2c functions
> which are not compiled otherwise. Update the Kconfig entry for the
> 'eeprom' command corr
On 2/22/24 05:34, Michal Simek wrote:
>
>
> On 2/20/24 20:30, Sean Anderson wrote:
>> On 2/20/24 14:18, Michal Simek wrote:
>>>
>>>
>>> On 2/20/24 19:43, Sean Anderson wrote:
On 2/20/24 13:24, Michal Simek wrote:
>
>
> On 2/16/24 17:09, Sean Anderson wrote:
>> On 2/16/24 11:03,
On Thu, Feb 22, 2024 at 04:08:45PM +, Caleb Connolly wrote:
> Hi Tom,
>
> Just a few button fixes that I realise should probably make it in.
>
> The following changes since commit 37345abb97ef0dd9c50a03b2a72617612dcae585:
>
> Prepare v2024.04-rc2 (2024-02-13 18:16:57 -0500)
>
> are avail
From: Sean Anderson
Currently, when we boot from JTAG we try to boot U-Boot from RAM.
However, this is a bit tricky to time, since the debugger has to wait
for SPL to initialize RAM before it can load U-Boot. This can result in
long waits, since occasionally initializing RAM (and other things in
Hi Tom,
Just a few button fixes that I realise should probably make it in.
The following changes since commit 37345abb97ef0dd9c50a03b2a72617612dcae585:
Prepare v2024.04-rc2 (2024-02-13 18:16:57 -0500)
are available in the Git repository at:
g...@source.denx.de:/u-boot/custodians/u-boot-sna
On 12:15-20240222, Neha Malcom Francis wrote:
> From: Sekhar Nori
>
> An entry in memory map table for MMU configuration is spilling over and
> inadvertently mapping DDR available at higher address (above 4GB address
> space) as device memory (nGnRnE).
>
> Fix this by
Set CONFIG_TARGET_SOCFPGA_ARRIA10_ALWAYS_REPROGRAM as enabled in
chameleon v3 board's defconfig.
Signed-off-by: Michał Barnaś
---
configs/socfpga_chameleonv3_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/socfpga_chameleonv3_defconfig
b/configs/socfpga_chameleonv3_defcon
Add Kconfig that enables FPGA reprogramming with warm boot on Arria 10.
This option allows to change the bitstream on the filesystem and apply
changes with warm reboot without the need for a power cycle.
Signed-off-by: Michał Barnaś
---
arch/arm/mach-socfpga/Kconfig | 8
arch/arm/mac
By default, the board requires power cycle (cold boot) to program the
FPGA with bitstream. This change adds Kconfig that allows to enable
reprogramming the FPGA with every boot. This makes the update process
of the bitstream on the filesystem to be applied with simple system
reboot.
Michał Barn
From: Thomas Perrot
It appears that there is some timing marginality either in the
board layout or the SoC that results in occasional data corruption
on some boards.
We observed this issue on some of the new HiFive Unmatched RevB
boards during volume production as well as some of the original
HiF
On Thu, Feb 22, 2024 at 08:16:19AM -0500, Tom Rini wrote:
>
> That we have 'config 64BIT' in arch/{mips,riscv}/Kconfig as well is a
> leftover of thinking this is like the Linux Kernel where there's no
> top-level arch/Kconfig file, can you please move the two existing config
> 64BIT entries to ar
On Thu, Feb 22, 2024 at 09:47:58AM +0300, Dan Carpenter wrote:
> In the Makefile there is a line that says this:
>
> # the checker needs the correct machine size
> CHECKFLAGS += $(if $(CONFIG_64BIT),-m64,-m32)
>
> So set CONFIG_64BIT so that we don't pass -m32 to the static checker.
>
>
Update simple-framebuffer device-tree node by enumerating framebuffer
related information in existing simple-framebuffer node in Linux
device-tree file and enabling it.
In case there is no simple-framebuffer stub detected in Linux kernel
device-tree and video is still active, then update the devic
Create separate helper for just reserving framebuffer region without
creating or enabling simple-framebuffer node.
This is useful for scenarios where user want to preserve the bootloader
splash screen till OS boots up and display server gets started without
displaying anything else in between and
If SPL is passing video handoff structure to U-boot then it is safe to
assume that SPL has already enabled video and that's why it is passing
video handoff structure to U-boot so that U-boot can preserve the
framebuffer.
Signed-off-by: Devarsh Thakkar
---
drivers/video/video-uclass.c | 4
1
Enable and update simple-framebuffer node using the video handoff
bloblist if video was enabled at SPL stage and corresponding video
bloblist was received at u-boot proper with necessary parameters.
Signed-off-by: Devarsh Thakkar
---
boot/fdt_simplefb.c | 34 +-
1
This adds support for simple-framebuffer reservation using video handoff
when splash is enabled at SPL stage.
Also adds helper function to only enable framebuffer reservation without
enabling simple-framebuffer in case user want to continue display
bootloader splash without displaying anything els
Hi Quentin,
On 2024-02-22 11:18, Quentin Schulz wrote:
> Hi Jonas,
>
> On 2/17/24 01:22, Jonas Karlman wrote:
>> Similar to RK35xx the BootRom in RK3328 can read all data and look for
>> idbloader at 0x8000, same as it does for SD and eMMC.
>>
>> Use the rksd format and modify the mkimage offset
On Wed, 2024-02-21 at 15:31 +0100, Francesco Dolcini wrote:
> On Wed, Feb 21, 2024 at 09:18:51AM +, Marcel Ziswiler wrote:
> > On Wed, 2024-02-21 at 08:55 +0100, Francesco Dolcini wrote:
> > > On Tue, Feb 20, 2024 at 06:40:56PM +0530, Sumit Garg wrote:
> > > > Also, enable reset driver which is
On 21.02.24 18:59, Conor Dooley wrote:
Yo,
I mentioned this last night to Heinrich on IRC, supports_extension() is
broken for ISA strings longer than 32 characters. M-Mode U-Boot doesn't
parse a devicetree, so this doesn't apply there, but for S-mode
supports_extension() looks like:
static inli
Allow platforms to reuse DT headers and dtsi includes directly form
upstream DT subtree which will be frequently synced with Linux kernel.
This will further allow us to drop corresponding DT includes copy from
U-Boot tree.
Also, since the DT includes from upstream DT subtree are done after DT
incl
Allow platform owners to mirror devicetree files from devitree-rebasing
directory into dts/upstream/src/$(ARCH) (special case for arm64). Then
build then along with any *-u-boot.dtsi file present in arch/$(ARCH)/dts
directory. Also add a new Makefile for arm64.
This will help easy migration for pl
Since meson-gxbb based boards switched to using upstream DT, so drop
redundant files from arch/arm/dts directory. Only *-u-boot.dtsi files
kept in arch/arm/dts directory for these boards.
Reviewed-by: Neil Armstrong
Signed-off-by: Sumit Garg
---
Changes in v6:
- None
Changes in v5:
- None
Cha
Encourage SoC/board maintainers to migrate to using devicetree-rebasing
subtree and maintain a regular sync with Linux kernel devicetree files
and bindings.
Along with that add documentation regarding how to run DT bindings
schema checks.
Signed-off-by: Sumit Garg
---
Changes in v6:
- Incorpora
Add myself as devicetree-rebasing maintainer.
Reviewed-by: Simon Glass
Reviewed-by: Ilias Apalodimas
Signed-off-by: Sumit Garg
---
Changes in v6:
- None
Changes in v5:
- None
Changes in v4:
- Switched subtree to be imported as dts/upstream sub-directory rather
than devicetree-rebasing sub-
Although there were still some variations in board DTS files based on
meson-gxbb SoC but I think those were minor differences from upstream
and shouldn't impact boot on these devices.
So enable OF_UPSTREAM to use upstream DT and add amlogic/ prefix to the
DEFAULT_DEVICE_TREE. And thereby directly
Since U-Boot switched away from manual CONFIG_* defines to Kconfig
options, align devicetree documentation accordingly.
Signed-off-by: Sumit Garg
---
Changes in v6:
- None
Changes in v5:
- Fixed inappropriate documentation update.
Changes in v4:
- Separate patch to align documentation to use K
dts/update-dts-subtree.sh is just a wrapper around git subtree commands.
Usage from the top level U-Boot source tree, run:
$ ./dts/update-dts-subtree.sh pull
$ ./dts/update-dts-subtree.sh pick
Signed-off-by: Sumit Garg
---
Changes in v6:
- Incorporate shell script comments from Marek.
Change
Allow u-boot to build DTB from a different directory tree such that
*-u-boot.dtsi files can be included from a common location. Currently
that location is arch/$(ARCH)/dts/, so statically define that common
location.
This is needed for platform owners to start building DTB files from
devicetree-re
Since devicetree-rebasing is an external repo with its own coding style,
exclude it from Azure and gitlab CI CONFIG checks.
Reviewed-by: Tom Rini
Reviewed-by: Ilias Apalodimas
Reviewed-by: Simon Glass
Signed-off-by: Sumit Garg
---
Changes in v6:
- None
Changes in v5:
- None
Changes in v4:
-
This adds the build infrastructure for checking DT binding schema
documents and validating dtb files using the binding schema. Here we use
devicetree-rebasing subtree to provide the DT bindings. Along with that
adapt dts/upstream/Bindings/Makefile to align with old U-Boot Kbuild
infrastructure.
De
Changes in v6:
--
- v6_dt: https://github.com/b49020/u-boot/tree/v6_dt
- Patch #3: Incorporate fix for sandbox CI failure.
- Patch #6: Incorporate shell script comments from Marek.
- Patch #8: Incorporate documentation review comments from Paul.
Changes in v5:
--
- Rebased
Hi Illias
sure I pushed it here:
https://github.com/nieknooijens/u-boot/tree/tpm_policy_patch
Niek
差出人: Ilias Apalodimas
送信日時: 2024年2月21日 18:01
宛先: Niek Nooijens / OC-IAB PBD-C DEVEL 1-1
CC: Dan Carpenter ; u-boot@lists.denx.de
件名: Re: [PATCH] implement poli
On 2/20/24 20:30, Sean Anderson wrote:
On 2/20/24 14:18, Michal Simek wrote:
On 2/20/24 19:43, Sean Anderson wrote:
On 2/20/24 13:24, Michal Simek wrote:
On 2/16/24 17:09, Sean Anderson wrote:
On 2/16/24 11:03, Sean Anderson wrote:
On 2/16/24 10:06, Michal Simek wrote:
On 2/16/24 1
Hi Jonas,
On 2/17/24 01:22, Jonas Karlman wrote:
Similar to RK35xx the BootRom in RK3328 can read all data and look for
idbloader at 0x8000, same as it does for SD and eMMC.
Use the rksd format and modify the mkimage offset to generate a bootable
u-boot-rockchip-spi.bin that can be written to 0
Hi Jonas,
On 2/17/24 01:22, Jonas Karlman wrote:
The U-Boot driver try to base the gpio bank id on the gpio-ranges prop
and fall back to base the bank id on the node name. However, the linux
driver try to base the bank id on the gpio alias id and fall back on
node order.
This can cause issues w
Hi Jonas,
On 2/21/24 20:05, Jonas Karlman wrote:
Hi Quentin,
On 2024-02-21 19:18, Quentin Schulz wrote:
Hi Jonas,
On 2/17/24 19:35, Jonas Karlman wrote:
Port the RK3399 part of the Rockchip IO-domain driver from linux.
This differs from linux version in that pmu io iodomain bit is enabled
i
On Tue, 20 Feb 2024 11:29:53 -0500
Sean Anderson wrote:
> On 2/20/24 04:50, Benjamin Lemouzy wrote:
> > Using fdtdump shows that crc32 is used as hash algorithm for FIT image
> > which is a super weak one.
> > I tried to pass another algo (sha256) using mkimage -o option but that
> > doesn't wo
52 matches
Mail list logo
