On Tue, 6 May 2025 at 15:36, Vincent Stehlé wrote:
>
> The help string for the `setenv -e' command shows a comma being used as
> the separator between address and size for the -i option, which deals
> with UEFI Variables contents passed as a buffer in memory.
> This is no longer the case since com
Since GNU binutils version 2.44, assembly functions must include
the assembler directive .type name, %function. If not a call to
these functions fails with the error message 'Unknown destination
type (ARM/Thumb)' and the error message 'dangerous relocation:
unsupported relocation' at linking.
Joha
Since GNU binutils version 2.44, assembly functions must include
the assembler directive .type name, %function. If not a call to
these functions fails with the error message 'Unknown destination
type (ARM/Thumb)' and the error message 'dangerous relocation:
unsupported relocation' at linking.
Sign
Hi Tim,
Am Di., 6. Mai 2025 um 17:31 Uhr schrieb Tim Harvey :
> On Tue, May 6, 2025 at 2:33 AM Heiko Thiery
> wrote:
> >
> > Hi Alice, Hi Marek,
> >
> >
> >
> > Am Di., 29. Apr. 2025 um 03:19 Uhr schrieb Wei Fang :
> >>
> >> > > > With commit cc4e8af2c552, fsl_enetc register accessors have been
On 5/6/2025 11:42 PM, Andrew Davis wrote:
On 5/6/25 12:19 PM, Tom Rini wrote:
On Tue, May 06, 2025 at 10:47:57PM +0530, Kumar, Udit wrote:
On 5/6/2025 8:38 PM, Andrew Davis wrote:
On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote:
Hi Andrew,
On 5/6/2025 4:38 PM, Andrew Davis wrote:
On 5/6/2
Mention that RISC-V supports semihosting.
Update SPDX identifier to current format.
Signed-off-by: Heinrich Schuchardt
---
doc/usage/semihosting.rst | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/doc/usage/semihosting.rst b/doc/usage/semihosting.rst
i
On Tue May 6, 2025 at 8:03 PM IST, Andrew Davis wrote:
> On 4/28/25 9:12 AM, Anshul Dalal wrote:
>> Falcon mode was disabled for TI_SECURE_DEVICE at commit e95b9b4437bc
>> ("ti_armv7_common: Disable Falcon Mode on HS devices") for older 32-bit
>> HS devices and can be enabled on K3 devices.
>>
>>
So far the 64-bit SoCs were relying on Trusted-Firmware to do the PMIC
setup, which was quite static: enabling most rails, regardless of
whether they are needed or not.
We have a fully DM compliant AXP regulator driver for a while, so that
U-Boot proper can do its own PMIC setup, based on the actu
The X-Powers AXP PMICs contain a special pin that can be used to drive
USB VBUS power, which requires a special AXP (sub-)driver.
Enable that for the 64-bit boards that use this pin, so that they can
enable VBUS power on their own, without relying on the help of TF-A.
Signed-off-by: Andre Przywar
Hi,
this series enables the build of the AXP driver in U-Boot proper for all
boards using the Allwinner A64 SoC. So far some static PMIC rail setup
was done by TF-A, but this was rather static (enabling too many) and
increases the code size of the rather limited BL31 build.
Do this for the A64 on
On Wed, 23 Apr 2025 08:49:13 -0600, Tom Rini wrote:
> The bootstd code itself does not have any dependency on BLK in order to
> build. However, in order to minimize size growth of non-migrated
> platforms, change this from being "default y" to "default y if BLK".
> This will make it easier to begi
On Wed, 09 Apr 2025 12:26:20 -0500, Bryan Brattlof wrote:
> !A || (A && B) is equivalent to !A || B
>
> Drop the unused middle expression to simplify the statement.
>
>
Applied to u-boot/master, thanks!
[1/1] mips: octeon: remove unused middle expression
commit: 13d1bd5bbbfaf725a4c15985
On Tue, 19 Nov 2024 12:09:18 +0530, Venkatesh Yadav Abbarapu wrote:
> Write enable(06h) command will be sent to a flash device to
> set the write enable latch bit before every program, erase,
> write command. After that write disable command (04h) needs
> to be sent to clear the write enable latch
On Mon, 25 Nov 2024 16:19:47 +0530, Prasanth Babu Mantena wrote:
> MT35XU512ABA has only BFPT and 4-Byte Address Instruction Table
> in SFDP. commit bebdc237507c ("mtd: spi-nor: Parse SFDP SCCR Map")
> added checks in spi_nor_octal_dtr_enable() to bail out if the 22nd DWORD
> in SCCR does not ind
On Tue, May 06 2025, Tom Rini wrote:
> On Tue, May 06, 2025 at 09:07:05PM +0200, Rasmus Villemoes wrote:
>> On Tue, May 06 2025, Tom Rini wrote:
>>
>> > On Tue, May 06, 2025 at 10:49:31AM -0600, Tom Rini wrote:
>> >> On Tue, May 06, 2025 at 04:10:25PM +0200, Rasmus Villemoes wrote:
>> >>
>> >>
Add documentation for the test command, including the newly added =~
operator and some gotchas wrt. the numeric comparisons.
Signed-off-by: Rasmus Villemoes
---
This should be considered on top of
https://lore.kernel.org/u-boot/20250506141035.385756-1-r...@prevas.dk/
, but everything other than
On Tue, May 06, 2025 at 03:23:39PM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 5 May 2025 at 22:38, Tom Rini wrote:
> >
> > On Thu, May 01, 2025 at 07:37:01AM -0600, Simon Glass wrote:
> >
> > > This construct appears in various places. Reduce code size by adding a
> > > function for it.
> >
On Tue, May 06, 2025 at 08:10:30PM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 6 May 2025 at 18:25, Tom Rini wrote:
> >
> > On Tue, May 06, 2025 at 03:23:59PM +0200, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 5 May 2025 at 20:18, Tom Rini wrote:
> > > >
> > > > On Sat, May 03, 2025
On Tue, May 06, 2025 at 09:07:05PM +0200, Rasmus Villemoes wrote:
> On Tue, May 06 2025, Tom Rini wrote:
>
> > On Tue, May 06, 2025 at 10:49:31AM -0600, Tom Rini wrote:
> >> On Tue, May 06, 2025 at 04:10:25PM +0200, Rasmus Villemoes wrote:
> >>
> >> > Currently, the only way to make use of regex
On Tue, May 06 2025, Tom Rini wrote:
> On Tue, May 06, 2025 at 10:49:31AM -0600, Tom Rini wrote:
>> On Tue, May 06, 2025 at 04:10:25PM +0200, Rasmus Villemoes wrote:
>>
>> > Currently, the only way to make use of regex matching in the shell is
>> > by using "setexpr [g]sub" command. That's rathe
On 5/6/25 12:19 PM, Tom Rini wrote:
On Tue, May 06, 2025 at 10:47:57PM +0530, Kumar, Udit wrote:
On 5/6/2025 8:38 PM, Andrew Davis wrote:
On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote:
Hi Andrew,
On 5/6/2025 4:38 PM, Andrew Davis wrote:
On 5/6/25 5:41 AM, Beleswar Padhi wrote:
Some TI K3
Hi Tom,
On Tue, 6 May 2025 at 18:25, Tom Rini wrote:
>
> On Tue, May 06, 2025 at 03:23:59PM +0200, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 5 May 2025 at 20:18, Tom Rini wrote:
> > >
> > > On Sat, May 03, 2025 at 08:29:13AM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Fri,
On Tue, 6 May 2025 at 16:04, Tom Rini wrote:
>
> There are a few differences between how the test.py stage invokes
> test.py and how the sjg-lab stage invokes test.py. As a start of making
> both the code and the output and artifacts similar, this updates the
> sjg-lab stage with the following:
>
On Tue, May 06, 2025 at 09:30:11AM +0200, Rasmus Villemoes wrote:
> On Mon, May 05 2025, Tom Rini wrote:
>
> > On Mon, May 05, 2025 at 10:19:24PM +0200, Mark Kettenis wrote:
> >> > Date: Mon, 5 May 2025 07:48:43 -0600
> >> > From: Tom Rini
> >> >
> >> > On Mon, May 05, 2025 at 11:45:05AM +0200,
On Tue, May 06, 2025 at 10:47:57PM +0530, Kumar, Udit wrote:
>
> On 5/6/2025 8:38 PM, Andrew Davis wrote:
> > On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote:
> > > Hi Andrew,
> > >
> > > On 5/6/2025 4:38 PM, Andrew Davis wrote:
> > > > On 5/6/25 5:41 AM, Beleswar Padhi wrote:
> > > > > Some TI K3
On 5/6/2025 8:38 PM, Andrew Davis wrote:
On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote:
Hi Andrew,
On 5/6/2025 4:38 PM, Andrew Davis wrote:
On 5/6/25 5:41 AM, Beleswar Padhi wrote:
Some TI K3 SoCs like J721S2, and J784S4 have a HSM (High Security
Module) M4F core in the Wakeup Voltage Doma
On Tue, May 06, 2025 at 12:49:55PM +, Eric Schikschneit wrote:
> Hello Tom,
>
> The link that Simon sent does not add padding at the end. I have tried
> the approach with SYS_FDT_PAD first and my platform (imx6) still has
> issues when trying to modify the device tree from the board file. It
On Tue, May 06, 2025 at 10:49:31AM -0600, Tom Rini wrote:
> On Tue, May 06, 2025 at 04:10:25PM +0200, Rasmus Villemoes wrote:
>
> > Currently, the only way to make use of regex matching in the shell is
> > by using "setexpr [g]sub" command. That's rather awkward for asking
> > whether a string mat
On Tue, May 06, 2025 at 04:10:25PM +0200, Rasmus Villemoes wrote:
> Currently, the only way to make use of regex matching in the shell is
> by using "setexpr [g]sub" command. That's rather awkward for asking
> whether a string matches a regex. At the very least, it requires
> providing setexpr wit
On Tue, May 06, 2025 at 04:10:24PM +0200, Rasmus Villemoes wrote:
> This started as a rather simple patch, 1/11, adding the ability to
> more conveniently do regex matching in shell.
>
> But with that, it became very easy to see what the slre library can
> and especially what it cannot do, and th
On Tue, May 06, 2025 at 03:24:21PM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 5 May 2025 at 20:14, Tom Rini wrote:
> >
> > On Thu, May 01, 2025 at 07:18:32AM -0600, Simon Glass wrote:
> >
> > > This series restores the original behaviour of extlinux booting linux
> > > 'Image' files, which i
On Tue, May 06, 2025 at 03:23:59PM +0200, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 5 May 2025 at 20:18, Tom Rini wrote:
> >
> > On Sat, May 03, 2025 at 08:29:13AM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Fri, 2 May 2025 at 14:04, Tom Rini wrote:
> > > >
> > > > On Fri, May 02, 2025
From: Dmitrii Merkurev
Switch the mmc backend to this new shared block helpers,
reducing block logic and only leaving MMC specific logic.
Signed-off-by: Dmitrii Merkurev
Signed-off-by: Neil Armstrong
---
drivers/fastboot/Kconfig | 4 +-
drivers/fastboot/Makefile | 3 +-
drivers/fastboot/
From: Dmitrii Merkurev
1. Get partition info/size
2. Erase partition
3. Flash partition
4. BCB
Signed-off-by: Dmitrii Merkurev
Reviewed-by: Mattijs Korpershoek
Signed-off-by: Neil Armstrong
---
drivers/fastboot/Kconfig | 24
drivers/fastboot/Makefile | 1 +
This serie permits using any block device as target
for fastboot by moving the generic block logic into
a common set of helpers and also use them as generic
backend.
The erase logic has been extended to support software
erase since only 2 block drivers exposes the erase
operation.
Tests are welco
From: Dmitrii Merkurev
Introduce fastboot block flashing functions and helpers
to be shared with the MMC implementation.
The write logic comes from the mmc implementation, while
the partition lookup is much simpler and could be extended.
For the erase logic, allmost no block drivers exposes the
On Tue, 6 May 2025 at 17:29, Tom Rini wrote:
>
> On Tue, May 06, 2025 at 12:24:24PM +0200, Mark Kettenis wrote:
> > > Date: Mon, 5 May 2025 17:43:19 -0600
> > > From: Tom Rini
> > >
> > > On Tue, May 06, 2025 at 01:18:16AM +0200, Heinrich Schuchardt wrote:
> > > > On 5/6/25 00:10, Tom Rini wrote:
Hey all,
Unfortunately it looks like Coverity scan no longer generates the email
report with code snippets and only send me a high level report now. So,
the latest report is visible only to project members when logged in, and
is:
https://scan8.scan.coverity.com/#/project-view/22486/10710
So I'm m
On Tue, May 6, 2025 at 2:33 AM Heiko Thiery wrote:
>
> Hi Alice, Hi Marek,
>
>
>
> Am Di., 29. Apr. 2025 um 03:19 Uhr schrieb Wei Fang :
>>
>> > > > With commit cc4e8af2c552, fsl_enetc register accessors have been
>> > > > split to
>> > >
>> > > With 'commit cc4e8af2c552 ("net: fsl_enetc: Split re
On 5/6/25 9:51 AM, Beleswar Prasad Padhi wrote:
Hi Andrew,
On 5/6/2025 4:38 PM, Andrew Davis wrote:
On 5/6/25 5:41 AM, Beleswar Padhi wrote:
Some TI K3 SoCs like J721S2, and J784S4 have a HSM (High Security
Module) M4F core in the Wakeup Voltage Domain which could be used to
run secure service
Hi Andrew,
On 5/6/2025 4:38 PM, Andrew Davis wrote:
On 5/6/25 5:41 AM, Beleswar Padhi wrote:
Some TI K3 SoCs like J721S2, and J784S4 have a HSM (High Security
Module) M4F core in the Wakeup Voltage Domain which could be used to
run secure services like Authentication. Boot flow for HSM M4 core
Hello Tom,
The link that Simon sent does not add padding at the end. I have tried the
approach with SYS_FDT_PAD first and my platform (imx6) still has issues when
trying to modify the device tree from the board file. It still returns
FDT_ERR_NOSPACE with that option. The commit I sent simply ad
Hi Andrew,
On 5/6/2025 4:36 PM, Andrew Davis wrote:
On 5/6/25 5:42 AM, Beleswar Padhi wrote:
The tispl.bin fit image is packed with the HSM firmware image. Populate
the "os" info of the image so that it can be detected and used to load
the HSM core. Further, invoke the load and boot of HSM core
On 4/28/25 9:12 AM, Anshul Dalal wrote:
Falcon mode was disabled for TI_SECURE_DEVICE at commit e95b9b4437bc
("ti_armv7_common: Disable Falcon Mode on HS devices") for older 32-bit
HS devices and can be enabled on K3 devices.
For secure boot, the kernel with x509 headers can be packaged in a fit
On Tue, May 06, 2025 at 12:24:24PM +0200, Mark Kettenis wrote:
> > Date: Mon, 5 May 2025 17:43:19 -0600
> > From: Tom Rini
> >
> > On Tue, May 06, 2025 at 01:18:16AM +0200, Heinrich Schuchardt wrote:
> > > On 5/6/25 00:10, Tom Rini wrote:
> > > > On Tue, May 06, 2025 at 12:07:20AM +0200, Heinrich
On 06.05.25 04:58, Tony Dinh wrote:
Remove DS109 board reset_misc() function. U-Boot generic reset is enough.
Signed-off-by: Tony Dinh
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
board/Synology/ds109/ds109.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/board
On 06.05.25 04:58, Tony Dinh wrote:
Enable DM_SERIAL for Marvell Kirkwood Synology DS109.
Note that this patch depends on:
https://patchwork.ozlabs.org/project/uboot/patch/20250505220853.23679-1-mibo...@gmail.com/
Signed-off-by: Tony Dinh
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
a
On 06.05.25 00:08, Tony Dinh wrote:
Enable DM_SERIAL for Marvell Kirkwood boards that have not been converted.
Signed-off-by: Tony Dinh
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
arch/arm/mach-kirkwood/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/mach
The first of these, { "U-Boot", "^[B-Uo-t]*$", 0 }, would match
previously when the - and the letters were all interpreted literally.
Signed-off-by: Rasmus Villemoes
---
test/lib/slre.c | 8
1 file changed, 8 insertions(+)
diff --git a/test/lib/slre.c b/test/lib/slre.c
index 053d046075
When trying to use U-Boot's regex facility, it is a rather large
gotcha that [a-z] range syntax is not supported. It doesn't require a
lot of extra code to implement that; we just let the regular parsing
emit the start and end literal symbols as usual, and add a new
"escape" code RANGE.
At match t
Signed-off-by: Rasmus Villemoes
---
test/lib/slre.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/test/lib/slre.c b/test/lib/slre.c
index 9b41ea92f38..053d046075e 100644
--- a/test/lib/slre.c
+++ b/test/lib/slre.c
@@ -26,6 +26,9 @@ static const struct re_test re_test[] = {
{ "Gad
At the compile stage, the anyof() function clearly intends to handle escape
sequences like \d (for digits) inside square brackets, since the logic
emits a 0 byte followed by the code representing the character
class (NONSPACE, SPACE or DIGIT).
However, this is not handled in the corresponding matc
As preparation for fixing the handling of backslash-escapes used
inside a character class, refactor is_any_but() to be defined in terms
of is_any_of() so we don't have to repeat the same logic in two places.
Signed-off-by: Rasmus Villemoes
---
lib/slre.c | 15 ++-
1 file changed, 6 i
Signed-off-by: Rasmus Villemoes
---
test/lib/slre.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/test/lib/slre.c b/test/lib/slre.c
index b76d33475dd..9b41ea92f38 100644
--- a/test/lib/slre.c
+++ b/test/lib/slre.c
@@ -23,6 +23,9 @@ static const struct re_test re_test[] = {
{ "",
Add some tests for the "drop wrong anchored optimization". Without
the previous commit, the first, fifth and seventh of these would fail,
i.e. those:
{ "xby", "^a|b", 1},
{ "", "x*$", 1},
{ "yy", "x*$", 1},
Signed-off-by: Rasmus Villemoes
---
test/lib/slre.c | 8
The regex '^a|b' means "does the string start with a, or does it have
a b anywhere", not "does the string start with a or b" (the latter
should be spelled '^[ab]' or '^(a|b)'). It should match exactly the
same strings as 'b|^a'. But the current implementation hard-codes an
assumption that when the
Inspecting the slre.c code reveals a few bugs; those are easy to
demonstrate with the new '=~' test operator. Before fixing them, let's
add a place to add test cases.
Signed-off-by: Rasmus Villemoes
---
MAINTAINERS | 1 +
test/lib/Makefile | 1 +
test/lib/slre.c | 36 ++
I guess that touching these files means "tag, you're it". That's fine
with me.
Signed-off-by: Rasmus Villemoes
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d62dd35a385..94c62daf834 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1628,6
Currently, the only way to make use of regex matching in the shell is
by using "setexpr [g]sub" command. That's rather awkward for asking
whether a string matches a regex. At the very least, it requires
providing setexpr with a dummy target variable, but also, the return
value of setexpr doesn't sa
This started as a rather simple patch, 1/11, adding the ability to
more conveniently do regex matching in shell.
But with that, it became very easy to see what the slre library can
and especially what it cannot do, and that way I found both outright
bugs and a "wow, doesn't it support that syntax"
Add ECC scrubbing with Dcache enabled to speed up the scrubbing time.
Change the SDRAM region to writethrough before scrubbing and restore back
to its original behavior after that. This is to avoid triggering of false
double-bit error.
Signed-off-by: Naresh Kumar Ravulapalli
Signed-off-by: Tien F
Move common code sdram_init_ecc_bits() to new common file.
Preparation for next gen devices which uses the same ECC scrubbing
function.
Signed-off-by: Naresh Kumar Ravulapalli
---
drivers/ddr/altera/Makefile| 2 +-
drivers/ddr/altera/sdram_arria10.c | 20 ++-
drivers/ddr
SOCFPGA_SDR_FIREWALL_MPU_FPGA_ADDRESS is added in
SOCFPGA_SDR_FIREWALL_MPU_FPGA_ADDRESS_OFFSET() macro already.
Remove extra SOCFPGA_SDR_FIREWALL_MPU_FPGA_ADDRESS in mpu1 address
computation.
Signed-off-by: Naresh Kumar Ravulapalli
---
drivers/ddr/altera/sdram_arria10.c | 1 -
1 file changed, 1
Add call to get_ram_size() function to check memory range
for valid RAM.
Signed-off-by: Naresh Kumar Ravulapalli
---
drivers/ddr/altera/sdram_arria10.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/ddr/altera/sdram_arria10.c
b/drivers/ddr/altera/sdram_arria10.c
Add DRAM size checking compare between size from device tree and actual
hardware.
Trigger hang if DRAM size from device tree is greater than actual hardware.
Display warning message if DRAM size mismatch between device tree and
actual hardware.
Signed-off-by: Naresh Kumar Ravulapalli
---
driver
DDR driver of Arria10 SoCFPGA is enhanced in below ways:
a) Check DRAM size from device tree and actual hardware,
mismatch is notified to the user
b) Fix a bug during computation of mpu1 address
c) Move common code specifically, initializing SDRAM ECC bits to a
common sdram_soc32 file. This a
There are a few differences between how the test.py stage invokes
test.py and how the sjg-lab stage invokes test.py. As a start of making
both the code and the output and artifacts similar, this updates the
sjg-lab stage with the following:
- Pass "-ra" so that we get the summary information in the
Am 06.05.25 um 16:11 schrieb Bryan Brattlof:
TI's Foundational Security (TIFS), Device Management (DM) and Device
Management and Security Control (DMSC) firmware are required for a
successful boot. Remove the 'optional' flag so binman will emit an error
if these firmware components are not found
On Tue, May 06, 2025 at 12:59:56PM +0530, Varadarajan Narayanan wrote:
> On Tue, Apr 01, 2025 at 04:37:40PM +0200, neil.armstr...@linaro.org wrote:
> > On 01/04/2025 16:10, Tom Rini wrote:
> > > On Tue, Apr 01, 2025 at 01:30:12PM +0530, Varadarajan Narayanan wrote:
> > >
> > > > The qcs9100 based R
Hi Sumit
On Tue, 6 May 2025 at 15:37, Sumit Garg wrote:
>
> + Heinrich
>
> On Tue, May 06, 2025 at 01:33:33PM +0200, Casey Connolly wrote:
> >
> >
> > On 5/6/25 09:13, Sumit Garg wrote:
> > > Hi Casey,
> > >
> > > On Fri, Apr 11, 2025 at 05:03:33PM +0200, Caleb Connolly wrote:
> > > > The initial
Hi Tom,
On Sat, 3 May 2025 at 18:58, Tom Rini wrote:
>
> On Fri, May 02, 2025 at 08:09:48PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Fri, 2 May 2025 at 10:26, Tom Rini wrote:
> > >
> > > On Fri, 11 Apr 2025 14:47:37 +0200, Caleb Connolly wrote:
> > >
> > > > Introduce a new event to sign
Hi Tom,
On Mon, 5 May 2025 at 20:14, Tom Rini wrote:
>
> On Thu, May 01, 2025 at 07:18:32AM -0600, Simon Glass wrote:
>
> > This series restores the original behaviour of extlinux booting linux
> > 'Image' files, which is to ignore CONFIG_SYS_BOOTM_LEN and instead uses
> > a limit of 10x the comp
Hi Tom,
On Mon, 5 May 2025 at 18:41, Tom Rini wrote:
>
> On Mon, May 05, 2025 at 05:37:33PM +0200, Simon Glass wrote:
> > Hi Quentin,
> >
> > On Mon, 5 May 2025 at 10:34, Quentin Schulz
> > wrote:
> > >
> > > Hi Simon,
> > >
> > > On 5/1/25 3:37 PM, Simon Glass wrote:
> > > [...]
> > > > diff -
Hi Eric,
On Tue, 6 May 2025 at 14:50, Eric Schikschneit
wrote:
>
> Hello Tom,
>
> The link that Simon sent does not add padding at the end. I have tried the
> approach with SYS_FDT_PAD first and my platform (imx6) still has issues when
> trying to modify the device tree from the board file. It
Hi Mark, Tom,
On Tue, 6 May 2025 at 12:24, Mark Kettenis wrote:
>
> > Date: Mon, 5 May 2025 17:43:19 -0600
> > From: Tom Rini
> >
> > On Tue, May 06, 2025 at 01:18:16AM +0200, Heinrich Schuchardt wrote:
> > > On 5/6/25 00:10, Tom Rini wrote:
> > > > On Tue, May 06, 2025 at 12:07:20AM +0200, Hein
Hi Tom,
On Mon, 5 May 2025 at 20:18, Tom Rini wrote:
>
> On Sat, May 03, 2025 at 08:29:13AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Fri, 2 May 2025 at 14:04, Tom Rini wrote:
> > >
> > > On Fri, May 02, 2025 at 09:42:56PM +0200, Heinrich Schuchardt wrote:
> > > > On 5/2/25 21:30, Tom Rin
Hi Tom,
On Mon, 5 May 2025 at 22:38, Tom Rini wrote:
>
> On Thu, May 01, 2025 at 07:37:01AM -0600, Simon Glass wrote:
>
> > This construct appears in various places. Reduce code size by adding a
> > function for it.
> >
> > It inits the abuf, then allocates it to the requested size.
> >
> > Signe
TI's Foundational Security (TIFS), Device Management (DM) and Device
Management and Security Control (DMSC) firmware are required for a
successful boot. Remove the 'optional' flag so binman will emit an error
if these firmware components are not found
Signed-off-by: Bryan Brattlof
---
Changes in
On May 5, 2025 thus sayeth Tom Rini:
> On Tue, Apr 29, 2025 at 03:01:56PM -0500, Bryan Brattlof wrote:
>
> > TI's Foundational Security (TIFS), Device Management (DM) and Device
> > Management and Security Control (DMSC) firmware are required for a
> > successful boot. Remove the 'optional' flag
Hi Dang,
On 2025/5/6 0:58, Dang Huynh wrote:
VOP2 (Video Output Processor v2) is a display controller on Rockchip
SoCs. It can be found on RK3566/8 and RK3588.
This commit currently only supports RK3566/8.
Signed-off-by: Dang Huynh
---
arch/arm/include/asm/arch-rockchip/vop_rk3568.h | 280 +
+ Heinrich
On Tue, May 06, 2025 at 01:33:33PM +0200, Casey Connolly wrote:
>
>
> On 5/6/25 09:13, Sumit Garg wrote:
> > Hi Casey,
> >
> > On Fri, Apr 11, 2025 at 05:03:33PM +0200, Caleb Connolly wrote:
> > > The initial capsule update support only worked on the RB3 Gen 2 and made
> > > a lot of
The help string for the `setenv -e' command shows a comma being used as
the separator between address and size for the -i option, which deals
with UEFI Variables contents passed as a buffer in memory.
This is no longer the case since commit 2b3fbcb59f41 ("efi_loader: use
':' as separator for setenv
On 5/6/25 09:13, Sumit Garg wrote:
Hi Casey,
On Fri, Apr 11, 2025 at 05:03:33PM +0200, Caleb Connolly wrote:
The initial capsule update support only worked on the RB3 Gen 2 and made
a lot of assumptions specific to that board.
Implement the logic necessary to update U-Boot no matter where i
On 2025/2/5 01:23, Chen-Yu Tsai wrote:
From: Chen-Yu Tsai
The IO domain driver controls the I/O voltage for various pins,
MMC included.
Enable it by default for all supported Rockchip SoCs.
Signed-off-by: Chen-Yu Tsai
Reviewed-by: Kever Yang
Thanks,
- Kever
---
configs/chromebook_bo
Hi,
On 05/05/2025 19:58, ver...@hpe.com wrote:
From: Jean-Marie Verdun
Add support for the Wiznet W5500 spi to ethernet controller
Signed-off-by: Jean-Marie Verdun
---
drivers/net/Kconfig | 9 +
drivers/net/Makefile | 1 +
drivers/net/w5500.c | 618 +
On Mon, 5 May 2025 at 15:47, Quentin Schulz wrote:
>
> From: Quentin Schulz
>
> This was only used on RK3288 Chromebooks and the EVB.
>
> If it follows the same pattern as for RK3399 Chromebooks where their
> maintainer (Simon) agreed[1] to removal of u-boot.rom on the basis that
> the generic u-
On Mon, 5 May 2025 at 15:47, Quentin Schulz wrote:
>
> From: Quentin Schulz
>
> This was only used on RK3399 Gru Chromebooks and their maintainer
> (Simon) agreed[1] to its removal on the basis that the generic
> u-boot-rockchip-spi.bin is now enough, so let's do that.
>
> At the same time, remov
On Tue, May 06, 2025 at 03:15:01PM +0800, Weijie Gao wrote:
> 1. As this is for MTD-based devices, the Kconfig dependency should be MTD
>instead of only spi-nor flashes
> 2. Initialize saved_buf to avoid crash on free()
> 3. Remaining size shoule be set correctly to write_size
>
> Fixes: 03fb0
Hello Zixun,
On 4/28/25 12:16, Zixun LI wrote:
> This patch series includes some code refactor and adds new device support
> for at91sam9_wdt driver.
>
> Instead of add a new driver like Linux kernel, at91sam9_wdt driver is
> extended as new watchdog variant is similar to existing one, especially
On Tue, 6 May 2025 at 16:35, Heinrich Schuchardt
wrote:
>
>
>
> Sughosh Ganu schrieb am Di., 6. Mai 2025, 12:50:
>>
>> On Tue, 6 May 2025 at 15:19, Heinrich Schuchardt
>> wrote:
>> >
>> > On 5/6/25 11:24, Sughosh Ganu wrote:
>> > > U-Boot has support for both the 32-bit and 64-bit RiscV platform
On 5/6/25 5:41 AM, Beleswar Padhi wrote:
Some TI K3 SoCs like J721S2, and J784S4 have a HSM (High Security
Module) M4F core in the Wakeup Voltage Domain which could be used to
run secure services like Authentication. Boot flow for HSM M4 core is
different than the general purpose M4F cores, and i
On 5/6/25 5:42 AM, Beleswar Padhi wrote:
The tispl.bin fit image is packed with the HSM firmware image. Populate
the "os" info of the image so that it can be detected and used to load
the HSM core. Further, invoke the load and boot of HSM core at R5 SPL
stage. Boot flow for HSM M4 core is as belo
Sughosh Ganu schrieb am Di., 6. Mai 2025, 12:50:
> On Tue, 6 May 2025 at 15:19, Heinrich Schuchardt
> wrote:
> >
> > On 5/6/25 11:24, Sughosh Ganu wrote:
> > > U-Boot has support for both the 32-bit and 64-bit RiscV platforms. Set
> > > the width of the phys_{addr,size}_t data types based on the
On Tue, 6 May 2025 at 15:19, Heinrich Schuchardt
wrote:
>
> On 5/6/25 11:24, Sughosh Ganu wrote:
> > U-Boot has support for both the 32-bit and 64-bit RiscV platforms. Set
> > the width of the phys_{addr,size}_t data types based on the register
> > size of the architecture.
> >
> > Currently, even
The tispl.bin fit image is packed with the HSM firmware image. Populate
the "os" info of the image so that it can be detected and used to load
the HSM core. Further, invoke the load and boot of HSM core at R5 SPL
stage. Boot flow for HSM M4 core is as below:
1. Request control of HSM M4F remote pr
The board_fit_image_post_process() function assumes that all TIFSSTUB
images appear at the end of the image_os_match[] array by using
the condition:
i > IMAGE_ID_DM_FW
However, this assumption breaks when new image types are appended to the
enum and the array, causing unintended image typ
It is possible for FIT Images to skip mentioning the pre-defined 'load'
address property. In those cases, SPL uses the actual address of the FIT
Image data as the fallback load address. Use this FIT data address for
referencing the image when the 'load' property is missing.
Signed-off-by: Beleswar
Pack the HSM firmware in tispl.bin fit image so that it can be unloaded
and used by R5 SPL to boot the HSM core. By default, point to the
firmware for HS-SE device type. This needs to be changed to point to
appropriate firmware when using a different device type.
Signed-off-by: Beleswar Padhi
---
The HSM M4 core needs to be booted at R5 SPL stage so that it can be
used for further Authentication and security services. Therefore, the
firmware for the HSM core needs to be packed in tispl.bin fit image so
that it can be used by R5 SPL to boot the HSM core.
Add a template for packing the HSM f
In cases where the 'load' property is not defined in a FIT image node,
fallback to using the data address returned by `fit_image_get_data()`.
This enables FIT images to omit the 'load' property during FIT creation.
Signed-off-by: Beleswar Padhi
---
v2: Changelog:
1. New patch. Add support to load
1 - 100 of 138 matches
Mail list logo
