Hi Tom,
please pull these patches to your tree. Nothing really significant there. Some
binman fixes which were not spot before and switching our platform to LWIP to
have cover it better.
Thanks,
Michal
The following changes since commit 97c125e6bb441a8062bdd28e82f17b1da1224416:
Gitlab: A
On 05/02/25 6:34 pm, Andrew Goodbody wrote:
USB tests on ext partitions can fail with the following output
test/py/tests/test_usb.py:245: in test_usb_part
'fstype usb %d:%d' % i, part_id
E TypeError: not enough arguments for format string
So add brackets around the format string argum
From: Hari Nagalla
Add remoteproc specific env support for am62px device. If the
remoteproc CMD is defined, include the K3 remoteproc environment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-of
This patch add support to read register base address by name if
provided.
Also devfdt_get_addr_* is changed to dev_read_addr_* to support DT
live tree.
Signed-off-by: Weijie Gao
---
drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --
The reg-names in mt7988.dtsi have no _base suffix. Remove the suffix
will also make it match upstream linux format.
Fixes: 8c2cb748ef5 (pinctrl: mediatek: mt7988: rename reg-names to upstream
linux format)
Signed-off-by: Weijie Gao
---
drivers/pinctrl/mediatek/pinctrl-mt7988.c | 3 +--
1 file c
From: Hari Nagalla
Add remoteproc specific env support for am62x device. If the
remoteproc CMD is defined, include the K3 remote procenvironment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-off
From: Hari Nagalla
Enable configs needed to enable remoteproc drivers for AM62
and AM64 devices.
While we are here, cleanup some remoteproc configs, there
is no DSP subsystem for am62px device.
Signed-off-by: Hari Nagalla
Signed-off-by: Judith Mendez
---
Changes since v3:
- Add remoteproc sup
From: Hari Nagalla
Some K3 devices like AM64, AM62 devices have a M4 processor in MCU
voltage domain.
Add a remote proc driver to support this subsystem to be able to load
and boot the M4 core.
Signed-off-by: Hari Nagalla
[Ryan: Fix implicitly include warning]
Signed-off-by: Ryan Eatmon
[Judi
From: Hari Nagalla
Add remoteproc specific env support for am64x device. If the
remoteproc CMD is defined, include the K3 remoteproc environment.
Also define rproc_fw_binaries which holds a list of remoteproc FW
binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla
Signed-off
Some K3 devices like am62x and am64x have a M4 processor in the MCU
voltage domain. This patch series introduces remoteproc M4 driver which
will be used to load firmware into and start the M4 remote core.
This series also adds support for R5F cores on am64x SoCs in patch 2,
sets up environment to
From: Hari Nagalla
AM64x SoCs have two R5F clusters in the main power domain.
Extend support for R5F remote proc driver on AM64x with compatible
strings.
Signed-off-by: Hari Nagalla
Signed-off-by: Judith Mendez
Reviewed-by: Daniel Schultz
---
Changes since v3:
- no change
---
drivers/remotep
The change from pinctrl to pio was missing in mt7986-u-boot.dtsi and will
cause build failure. Now fix it.
Fixes: f1775996ba9 (mediatek: mt7986: move gpio-controller up and rename
pinctrl to pio)
Signed-off-by: Weijie Gao
---
arch/arm/dts/mt7986-u-boot.dtsi | 2 +-
1 file changed, 1 insertion(+
On Wed, 5 Feb 2025 at 21:25, Tom Rini wrote:
>
> On Wed, Feb 05, 2025 at 09:18:50PM +0200, Ilias Apalodimas wrote:
> > Hi Tom,
> >
> > On Wed, 5 Feb 2025 at 19:33, Tom Rini wrote:
> > >
> > > On Wed, Feb 05, 2025 at 09:16:47AM +0200, Ilias Apalodimas wrote:
> > >
> > > > Upcoming patches are swit
On Wed, 29 Jan 2025 16:26:09 +0530, Aashvij Shenai wrote:
> AM62x BOOTM_LEN is too small to contain OS images. Removing this sets the
> size to a default 0x400 (for all arm64 devices).
>
> It is unnecessary to specifically call the default size for the other
> configs.
>
>
> [...]
Applied
On Tue, 28 Jan 2025 21:31:49 +0800, 1425075...@qq.com wrote:
> When I use arch armv7,
> menuconfig shows the STATIC_MACH_TYPE
> option causing me confusion.
> As we know, this should not occur when
> SUPPORT_PASSING_ATAGS is not selected
>
>
> [...]
Applied to u-boot/master, thanks!
--
Tom
On Tue, 28 Jan 2025 21:22:15 +0800, 1425075...@qq.com wrote:
> ARMv7-M architecture uses NVIC instead of GIC.
> NVIC is an interrupt controller specially designed for
> ARM Cortex-M series processors.
>
>
Applied to u-boot/master, thanks!
--
Tom
On Wed, 05 Feb 2025 18:48:45 +0100, Marek Vasut wrote:
> The following changes since commit 97c125e6bb441a8062bdd28e82f17b1da1224416:
>
> Gitlab: Add results.xml to the list of artifacts as well. (2025-02-04
> 11:57:36 -0600)
>
> are available in the Git repository at:
>
> https://source.d
Hi Simon,
On 2025-02-05 02:55, Simon Glass wrote:
> The U-Boot section is currently getting an invalid OS. Use the correct
> value to fix this.
>
> Signed-off-by: Simon Glass
This should happen earlier in the series or as a standalone fix, with
that fixed this is:
Reviewed-by: Jonas Karlman
Hi Simon,
On 2025-02-05 02:54, Simon Glass wrote:
> Move the FIT description into a template so that it can (later) be used
> in multiple places in the image.
>
> Signed-off-by: Simon Glass
> ---
>
> arch/arm/dts/rockchip-u-boot.dtsi | 57 ++-
> 1 file changed, 34 i
Hi Simon,
On 2025-02-05 02:54, Simon Glass wrote:
> Declare these at the top of the file to avoid needing #ifdefs in every
> usage.
>
> Add a few comments to help with the remaining #ifdefs
>
> Signed-off-by: Simon Glass
This patch should happen after the os = "U-Boot" fix if they are part of
Hi Simon,
On 2025-02-05 02:54, Simon Glass wrote:
> TPL runs before VPL. The earliest updatable phase with VBE is SPL. We
> want to be able to update the RAM-init code in the field.
If I understand your description here, you mean that both TPL and VPL
are meant to be "burned" onto the board and n
Hi Simon,
On 2025-02-05 02:54, Simon Glass wrote:
> VPL has the same needs as TPL in situations where the stack is at the
> top of SRAM. Add an option for this and implement it for arm
>
> Signed-off-by: Simon Glass
> ---
>
> arch/arm/lib/crt0_64.S | 4 +++-
> common/spl/Kconfig.vpl | 13
On Wed, Feb 05, 2025 at 09:18:50PM +0200, Ilias Apalodimas wrote:
> Hi Tom,
>
> On Wed, 5 Feb 2025 at 19:33, Tom Rini wrote:
> >
> > On Wed, Feb 05, 2025 at 09:16:47AM +0200, Ilias Apalodimas wrote:
> >
> > > Upcoming patches are switching the memory mappings to RW, RO, RX
> > > after the U-Boot
On Wed, Feb 05, 2025 at 01:41:46PM +0100, Michal Simek wrote:
> Hi,
>
> On 2/5/25 09:22, Ilias Apalodimas wrote:
> > I'm just replying to myself here but I'll send a v2 when the patches
> > are reviewed.
> >
> > I can add the linker under an ifdef, so u-boot size won't change
> > unless a Kconfig
On Wed, Feb 05, 2025 at 12:31:33PM +0200, Ilias Apalodimas wrote:
> Hi Jerome,
>
> On Wed, 5 Feb 2025 at 11:57, Jerome Forissier
> wrote:
> >
> >
> >
> > On 2/5/25 08:16, Ilias Apalodimas wrote:
> > > Now that we have everything in place switch the page permissions for
> > > .rodata, .text and .d
On 2/4/25 23:16, Ilias Apalodimas wrote:
@@ -98,18 +101,20 @@ SECTIONS
}
#endif
- . = ALIGN(8);
- .rodata : { *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*))) }
+ .rodata ALIGN(4096): {
+ __start_rodata = .;
+ *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))
On Wed, Feb 05, 2025 at 09:16:47AM +0200, Ilias Apalodimas wrote:
> Upcoming patches are switching the memory mappings to RW, RO, RX
> after the U-Boot binary and its data are relocated. Add
> annotations in the linker scripts to and mark text, data, rodata
> sections and align them to a page boun
Hi Tom,
On Wed, 5 Feb 2025 at 19:33, Tom Rini wrote:
>
> On Wed, Feb 05, 2025 at 09:16:47AM +0200, Ilias Apalodimas wrote:
>
> > Upcoming patches are switching the memory mappings to RW, RO, RX
> > after the U-Boot binary and its data are relocated. Add
> > annotations in the linker scripts to an
On Wed, Feb 05, 2025 at 09:16:46AM +0200, Ilias Apalodimas wrote:
> Since we added support in meminfo to dump live page tables, describe
> the only working architecture for now (aarch64) and add links to public
> documentation for further reading.
>
> Signed-off-by: Ilias Apalodimas
Generally l
Hi Tom,
On Wed, 5 Feb 2025 at 19:22, Tom Rini wrote:
>
> On Wed, Feb 05, 2025 at 09:16:46AM +0200, Ilias Apalodimas wrote:
>
> > Since we added support in meminfo to dump live page tables, describe
> > the only working architecture for now (aarch64) and add links to public
> > documentation for f
Hi Heinrich,
On Wed, 5 Feb 2025 at 18:48, Heinrich Schuchardt wrote:
>
> On 2/5/25 08:16, Ilias Apalodimas wrote:
> > For armv8 we are adding proper page permissions for the relocated U-Boot
> > binary. Add a weak function that can be used across architectures to change
> > the page permissions
>
With help from Michal Simek I have this running with Labgrid now, so
add it to the lab.
Signed-off-by: Simon Glass
---
.gitlab-ci.yml | 5 +
1 file changed, 5 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 1d4d3a85741..a55b0c9ee7a 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab
Hi Quentin,
On 2025-02-05 17:51, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> The v2 image format supports defining a load address and flag for each
>> embedded image.
>>
>> Add initial support for writing the image load address and flag to the
>> v2 image fo
Hi Quentin,
On 2025-02-05 16:57, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> The v2 image format can embed up to 4 data files compared to the two
>> init and boot data files using the older image format.
>>
>> Add support for displaying more of the image hea
Hi Quentin,
On 2025-02-05 17:48, Quentin Schulz wrote:
> Hi Jonas,
>
> On 2/5/25 5:42 PM, Jonas Karlman wrote:
>> Hi Quentin,
>>
>> On 2025-02-05 17:04, Quentin Schulz wrote:
>>> Hi Jonas,
>>>
>>> On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format embeds boot0 and boot1 parameters
Hi Jonas,
Hi Alex,
On 2025-01-27 19:59, Alex Bee wrote:
Hi Jonas,
thanks for working on this. Please see one comment below.
Am 27.01.25 um 00:48 schrieb Jonas Karlman:
A few Rockchip ARMv7 SoCs use 0x6000 as DRAM base address instead of
the more common 0x0 DRAM base address used on AAr
Hi Quentin,
On 2025-02-05 17:43, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> The v2 image format can support up to 4 embedded images that can be
>> loaded by the BootROM using the back-to-bootrom method.
>>
>> Currently two input files can be passed in using
Hi Quentin,
On 2025-02-05 16:40, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> Split 32-bit size_and_off and size_and_nimage fields of the v2 image
>> format header into their own 16-bit size, offset and num_images fields.
>>
>> Set num_images based on number
Hi Quentin,
On 2025-02-05 18:07, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/27/25 12:48 AM, Jonas Karlman wrote:
>> A few Rockchip ARMv7 SoCs use 0x6000 as DRAM base address instead of
>
> Are there known exceptions? Among the list you provided I see RV1126 is
> missing but is ARMv7-based.
The following changes since commit 97c125e6bb441a8062bdd28e82f17b1da1224416:
Gitlab: Add results.xml to the list of artifacts as well. (2025-02-04
11:57:36 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-sh.git master
for you to fetch changes
The NanoPi RK3399 boards support UHS-I (up to SDR104) SD cards, however
using any of these 1.8v modes results in a boot failure in SPL upon soft
reboot.
The issue is that the "vcc_sdio" regulator is left at 1.8v on reboot and
the corresponding GPIO defaults to 3.3v. This prevents the SD card fro
Hi Richard,
On Wed, 5 Feb 2025 at 19:23, Richard Henderson
wrote:
>
> On 2/4/25 23:16, Ilias Apalodimas wrote:
> > @@ -98,18 +101,20 @@ SECTIONS
> > }
> > #endif
> >
> > - . = ALIGN(8);
> > - .rodata : { *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*))) }
> > + .rodata ALIGN(4096):
This change removes the "regulator-always-on" property from the
"vcc3v0_sd" (vmmc-supply) and "vcc_sdio" (vqmmc-supply) regulators,
which otherwise prevents the MMC driver from being able to power cycle
the SD card as part of the initialization procedure.
It also removes the "regulator-boot-on" fr
Hi Quentin,
On Feb 4, 2025 at 09:30:33, Quentin Schulz wrote:
> Hi Justin,
>
> On 1/28/25 10:37 PM, Justin Klaassen wrote:
>
> Allows use of the regulator functions of the RK8XX PMIC in SPL, which is
>
> necessary to support the functionality of the Rockchip IO-domain driver
>
> on relevant pla
Hi Quentin,
On Feb 4, 2025 at 09:16:29, Quentin Schulz wrote:
> Hi Justin,
>
> On 1/28/25 10:37 PM, Justin Klaassen wrote:
>
> [You don't often get email from jus...@tidylabs.net. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
>
> Log the value of the regulat
Allows use of the Rockchip IO-domain driver in SPL to configure
the GPIO to match the voltage supplied by specific regulators
(e.g. "vcc_sdio").
Signed-off-by: Justin Klaassen
---
Changes in v3:
- Add depends on SPL_DM_REGULATOR
Changes in v2:
- Added separate patch for added CONFIG_SPL_ROCKCHI
The NanoPi RK3399 boards support UHS-I (up to SDR104) SD cards, however
using any of these 1.8v modes results in a boot failure in SPL upon soft
reboot.
The issue is that the "vcc_sdio" regulator is left at 1.8v on reboot
and the corresponding GPIO defaults to 3.3v. This prevents the SD card
from
Log the value of the regulators during initialization of the IO-domain
driver to aid in debugging GPIO voltage configuration problems.
Signed-off-by: Justin Klaassen
---
Changes in v3:
- Use dev_dbg instead of log_debug
Changes in v2:
- Made added IO-domain driver logs verbose and consistent
Allows use of the regulator functions of the RK8XX PMIC in SPL, which is
necessary to support the functionality of the Rockchip IO-domain driver
on relevant platforms.
Signed-off-by: Justin Klaassen
Reviewed-by: Quentin Schulz
---
(no changes since v2)
Changes in v2:
- Added separate patch for
Hi Quentin,
On Feb 4, 2025 at 09:20:56, Quentin Schulz wrote:
> Hi Justin
>
> On 1/28/25 10:37 PM, Justin Klaassen wrote:
>
> Allows use of the Rockchip IO-domain driver in SPL to configure
>
> the GPIO to match the voltage supplied by specific regulators
>
> (e.g. "vcc_sdio").
>
>
> Signed-off
On 03/02/2025 18:41, Simon Glass wrote:
This function calls dm_pci_read_bar32() which is only available if PCI
is enabled. Add this condition here too, so that the EFI app can build
without needing --gc-sections
Signed-off-by: Simon Glass
Reviewed-by: Matthias Brugger
---
lib/fdtdec.
Hi Jonas,
On 1/27/25 12:48 AM, Jonas Karlman wrote:
A few Rockchip ARMv7 SoCs use 0x6000 as DRAM base address instead of
Are there known exceptions? Among the list you provided I see RV1126 is
missing but is ARMv7-based. Is it an oversight or done on purpose? I
couldn't quickly find the
Dynamic memory, referenced by 'line', is allocated by calling
function 'calloc' and lost when the function terminates with code -1.
Signed-off-by: Maks Mishin
---
tools/proftool.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/proftool.c b/tools/proftool.c
index af2cdb6d58..c7b427
Hi Quentin,
On 2025-02-05 17:29, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> The vendor boot_merger tool support a ALIGN parameter that is used to
>> define offset alignment of the embedded images.
>>
>> Vendor use this for RK3576 to change offset alignment
On 2/5/25 08:16, Ilias Apalodimas wrote:
For armv8 we are adding proper page permissions for the relocated U-Boot
binary. Add a weak function that can be used across architectures to change
the page permissions
Signed-off-by: Ilias Apalodimas
---
arch/arc/lib/cache.c | 2 ++
arch/
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format supports defining a load address and flag for each
embedded image.
Add initial support for writing the image load address and flag to the
v2 image format header.
This may later be used for RK3576 to embed a minimal initial
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format can support up to 4 embedded images that can be
loaded by the BootROM using the back-to-bootrom method.
Currently two input files can be passed in using the datafile parameter,
separated by a colon (":").
Extend the datafi
Hi Quentin,
On 2025-02-05 17:04, Quentin Schulz wrote:
> Hi Jonas,
>
> On 1/29/25 11:36 PM, Jonas Karlman wrote:
>> The v2 image format embeds boot0 and boot1 parameters, the vendor tool
>> boot_merger may write these parameters based on the rkboot miniall.ini
>> files.
>>
>> E.g. a RK3576 boot i
Hi Jonas,
On 2/5/25 5:42 PM, Jonas Karlman wrote:
Hi Quentin,
On 2025-02-05 17:04, Quentin Schulz wrote:
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format embeds boot0 and boot1 parameters, the vendor tool
boot_merger may write these parameters based on the rkboot minia
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The vendor boot_merger tool support a ALIGN parameter that is used to
define offset alignment of the embedded images.
Vendor use this for RK3576 to change offset alignment from the common
2 KiB to 4 KiB, presumably it may have something to do
Hi Quentin and Naoki,
On 2025-02-05 12:37, Quentin Schulz wrote:
> Hi Naoki,
>
> On 1/29/25 2:25 PM, FUKAUMI Naoki wrote:
>> If CONFIG_EFI_CAPSULE_FIRMWARE_RAW, CONFIG_SPL_ENV_SUPPORT, and
>> CONFIG_SPL_DFU are enabled, linking u-boot-spl will fail.
>>
>>LD spl/u-boot-spl
>> ld.bfd: driv
Dynamic memories, referenced by 'ptr' and 'res' is allocated
by calling function 'hexport_r' and lost when the function success returns.
Signed-off-by: Maks Mishin
---
cmd/nvedit.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/cmd/nvedit.c b/cmd/nvedit.c
index 1f25980129..628f0a2935 100
Hi Tom,
As far as I know they did not. And I'm not sure they will.
That's why I've posted this as RFC.
Another problem is that RP1 driver in RPI kernel is still to be finished.
I was hoping that somebody from Raspberry will be interested in this
patch series and share some plans.
--
Oleksii
Hi,
st 5. 2. 2025 v 3:00 odesílatel Simon Glass napsal:
>
> The logic of this has become too confusing.
>
> The primary issue with the patch is that U-Boot needs to set up a
> bloblist in the first phase where BLOBLIST is enabled. Subsequent
> phases can then use that bloblist.
>
> But the first
Hi Simon,
On 2025-02-05 02:55, Simon Glass wrote:
> There doesn't seem to be a good reason to use a different value for TPL
> than SPL. Change the TPL value, since it allows a 256-byte bloblist to
> be safely located above the stack in all phases.
SPL is currently using DRAM memory as stack on al
Hi Simon,
On 2025-02-05 02:55, Simon Glass wrote:
> Add support for this new phase, which runs after TPL. It determines the
> state of the machine, then selects which SPL image to use. SDRAM init is
> then done in SPL, so that it is updatable.
I am still unsure how this makes it more updatable, w
On 2/5/25 2:04 PM, Andrew Goodbody wrote:
USB tests on ext partitions can fail with the following output
test/py/tests/test_usb.py:245: in test_usb_part
'fstype usb %d:%d' % i, part_id
E TypeError: not enough arguments for format string
So add brackets around the format string arguments
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format embeds boot0 and boot1 parameters, the vendor tool
boot_merger may write these parameters based on the rkboot miniall.ini
files.
E.g. a RK3576 boot image may contain a boot1 parameter that signals
BootROM or vendor blobs to
Introducing Generic Reset controller and Generic RESCAL
drivers for Broadcom boards.
Signed-off-by: Oleksii Moisieiev
Reviewed-by: Volodymyr Babchuk
---
drivers/reset/Kconfig| 14
drivers/reset/Makefile | 2 +
drivers/reset/reset-brcmstb-rescal.c | 103 +++
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
The v2 image format can embed up to 4 data files compared to the two
init and boot data files using the older image format.
Add support for displaying more of the image header information that
exists in the v2 image format, e.g. image load add
Hi Simon,
On 2025-02-05 02:55, Simon Glass wrote:
> When VPL is in use, memory init happens in SPL, so there is no need to
> include the DMC device before that. Adjust the tags to save space.
>
> Signed-off-by: Simon Glass
> ---
>
> arch/arm/dts/rk3399-u-boot.dtsi | 9 -
> 1 file chang
On Wed, Feb 05, 2025 at 10:15:41AM +, Oleksii Moisieiev wrote:
> Introducing device-tree bindings for the RP1 clocks.
>
> Signed-off-by: Oleksii Moisieiev
> Reviewed-by: Volodymyr Babchuk
> ---
>
> include/dt-bindings/clk/rp1.h | 56 +++
> 1 file changed, 5
Hi Jonas,
On 1/29/25 11:36 PM, Jonas Karlman wrote:
Split 32-bit size_and_off and size_and_nimage fields of the v2 image
format header into their own 16-bit size, offset and num_images fields.
Set num_images based on number of images passed by the datafile
parameter and size based on the offset
Hi Simon,
On Tue, 4 Feb 2025 at 20:57, Simon Glass wrote:
>
> Where the bloblist is located in internal memory and TF-A's BL31 blob
> removes access to this memory, the best option seems to be to relocate
> the bloblist just before running TF-A.
>
> Add an option to select this behaviour and prov
On 2/4/25 11:50 PM, Manorit Chawdhry wrote:
Hi Andrew,
On 09:43-20250204, Andrew Davis wrote:
On 2/3/25 10:43 PM, Manorit Chawdhry wrote:
Hi Andrew,
On 14:44-20250203, Andrew Davis wrote:
On 1/6/25 3:34 AM, Manorit Chawdhry wrote:
From: Neha Malcom Francis
Clean up templatized boot binari
Hi Simon,
On 2025-02-05 02:55, Simon Glass wrote:
> The rockchip image is written to the media at block 64, which is a 32K
> offset, so set the skip-at-start property to 0x8000
>
> Update CONFIG_SPL_PAD_TO to point to the offset in the image, since
> Binman is dealing with the 'missing' 32K now.
+CC Ilias,
Hi Simon,
On Tue, 4 Feb 2025 at 20:57, Simon Glass wrote:
>
> The logic of this has become too confusing.
>
> The primary issue with the patch is that U-Boot needs to set up a
> bloblist in the first phase where BLOBLIST is enabled. Subsequent
> phases can then use that bloblist.
>
>
Hi Simon,
On 2025-02-05 02:54, Simon Glass wrote:
> Move this up higher on kevin and bob so we can accommodate a larger
> U-Boot, e.g. with debugging info enabled.
These targets have moved to use ROCKCHIP_COMMON_STACK_ADDR and now use a
completely different CUSTOM_SYS_INIT_SP_ADDR, please rebase.
On 2/3/25 10:04, Padmarao Begari wrote:
The mini u-boot is hanging because of an initial stack
pointer address is used at half of the memory, when mini
u-boot is called reloc_fdt() function and doing memcpy()
for the fdt before relocation, and there is no sufficient
memory for the stack pointe
The -V version parameter is missing in the optional list of parameters
in help text. Add it.
Signed-off-by: Marek Vasut
---
Cc: Joe Hershberger
Cc: Tom Rini
---
tools/mkenvimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/mkenvimage.c b/tools/mkenvimage.c
index
On Wed, Feb 05, 2025 at 12:01:36AM -0800, Daniel Schultz wrote:
> This patch series adds support to boot PHYTEC's reference distros for
> RAUC and Secure Boot.
>
> It adds a new Kconfig entry to embed the RAUC boot logic into the K3 MMC
> boot logic. The boot flow itself got extended to run the r
Hi Tom,
On Mon, 3 Feb 2025 at 10:14, Tom Rini wrote:
>
> On Mon, Feb 03, 2025 at 09:25:54AM -0700, Simon Glass wrote:
>
> > When running multiple runners on the same machine, each should be in its
> > own container to avoid them interfering with either other.
> >
> > Add a container name for this
Add implementation of mkenvimage written purely in bourne shell.
This is not a replacement for mkenvimage tool, but rather a simple
implementation which can be used in environments where mkenvimage
itself cannot be deployed due to various constraints, like hardware
manufacturing plants, but where
On Wed, Feb 05, 2025 at 11:01:03AM +0800, Michael Chang wrote:
> Add a new event which handles this function refer commit
> id 91caa3bb89b112a1421ee2ee3661baf67c64bab9.
Please rephrase this as:
... refer to commit ("91caa3bb89b1 event: Use an event to replace
last_stage_init()")
I'd do that when
On Wed, Feb 05, 2025 at 10:56:52AM +0800, Hal Feng wrote:
> Update the maintainer file and mark jh7110 related files with N: pattern.
>
> Signed-off-by: Hal Feng
> ---
>
> Changes since v1:
> - Mark jh7110 related files with N: pattern.
>
> History:
> v1:
> https://lore.kernel.org/all/2025012
On Tue, Feb 04, 2025 at 06:55:19PM -0700, Simon Glass wrote:
> Where the bloblist is located in internal memory and TF-A's BL31 blob
> removes access to this memory, the best option seems to be to relocate
> the bloblist just before running TF-A.
>
> Add an option to select this behaviour and pro
On Tue, Feb 04, 2025 at 06:54:52PM -0700, Simon Glass wrote:
> Update for the new xPL naming, which was missed in a previous patch
> which proported to do this.
>
> Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: PGP signature
On Tue, Feb 04, 2025 at 06:54:51PM -0700, Simon Glass wrote:
> VPL has the same needs as TPL in situations where the stack is at the
> top of SRAM. Add an option for this and implement it for arm
>
> Signed-off-by: Simon Glass
> ---
>
> arch/arm/lib/crt0_64.S | 4 +++-
> common/spl/Kconfig.vpl
On Tue, Feb 04, 2025 at 06:55:18PM -0700, Simon Glass wrote:
> The logic of this has become too confusing.
>
> The primary issue with the patch is that U-Boot needs to set up a
> bloblist in the first phase where BLOBLIST is enabled. Subsequent
> phases can then use that bloblist.
>
> But the fi
Hi Jerome,
On Wed, 5 Feb 2025 at 11:57, Jerome Forissier
wrote:
>
>
>
> On 2/5/25 08:16, Ilias Apalodimas wrote:
> > Now that we have everything in place switch the page permissions for
> > .rodata, .text and .data just after we relocate everything in top of the
> > RAM.
> >
> > Unfortunately we
On Wed, 5 Feb 2025 at 14:42, Michal Simek wrote:
>
> Hi,
>
> On 2/5/25 09:22, Ilias Apalodimas wrote:
> > I'm just replying to myself here but I'll send a v2 when the patches
> > are reviewed.
> >
> > I can add the linker under an ifdef, so u-boot size won't change
> > unless a Kconfig options is
Hi,
On 2/5/25 09:22, Ilias Apalodimas wrote:
I'm just replying to myself here but I'll send a v2 when the patches
are reviewed.
I can add the linker under an ifdef, so u-boot size won't change
unless a Kconfig options is selected
I think you can just do it for alignment not really big ifdef i
On Wed, 5 Feb 2025 at 11:27, Jerome Forissier
wrote:
>
>
>
> On 2/5/25 08:16, Ilias Apalodimas wrote:
> > Upcoming patches are mapping memory with RO, RW^X etc permsissions.
> > Fix the meminfo command to display them properly
> >
> > Acked-by: Jerome Forissier
> > Signed-off-by: Ilias Apalodimas
From: Volodymyr Babchuk
This change is needed to make OP-TEE operable on RPI5.
This is somewhat convoluted, but in the essence, OP-TEE image is being
loaded at address 0x8 and we can't change that. Problem is that
last versions (like 2024/06/05) of RPI5 firmware tries to load
non-kernel imag
From: Volodymyr Babchuk
RP1 chip is the PCIe device which should provide transparent access to
the peripheral connected to it for the main Soc.
Current RP1 device tree node structure and RP1 driver implementation
don't allow PCIe subsystem to make a proper initialization of RP1
device with child
For the controllers that are utilizing reset for bridge sw init,
such as BCM2712, reset should be deasserted after assertion.
Leaving it in asserted state may lead to unexpected hangs in
the Linux Kernel driver because it do not perform reset initialization
and start accessing the device memory.
W
Add the default configuration file for RPI5 board.
To build u-boot for Raspberrypi 5 the following command should be
used:
> make rpi_arm64_defconfig CROSS_COMPILE=aarch64-linux-gnu-
Signed-off-by: Oleksii Moisieiev
Reviewed-by: Volodymyr Babchuk
---
configs/rpi_arm64_defconfig | 19 ++
Introduce clock driver for RPI5 RP1 chip. It is intended to
work with a clock controller connected to the RP1 chip of RPI5.
Current implementation supports only RP1_CLK_ETH_TSU clock.
Additional clock could be added to the rp1_data array if needed.
Signed-off-by: Oleksii Moisieiev
Reviewed-by: Vo
On BCM2712 connected devices, such as RPI5 has an external chip called
RP1 connected to the main SOC over ePCI. Macb is connectet to the RP1
chip and should be transparent to the SOC. Introduced changes are
intended to solve mapping issues and implement full support for the
macb driver.
Signed-off
Raspberry PI 5 has RP1 chip connected over PCIE and working as a
bridge to different hardware.
This driver implementation was inspired by MFD RP1 driver in the Linux
Kernel.
Signed-off-by: Oleksii Moisieiev
Reviewed-by: Volodymyr Babchuk
---
drivers/mfd/Kconfig | 10
drivers/mfd/Makefil
1 - 100 of 147 matches
Mail list logo
