All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "marek.vasut@mailbox.org" <marek.vasut@mailbox.org>,
	 "paul@pbarker.dev" <paul@pbarker.dev>,
	 Chris Paterson <Chris.Paterson2@renesas.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"anton.reding@landisgyr.com" <anton.reding@landisgyr.com>
Subject: Re: RZG2L and DTB blob from TF-A
Date: Thu, 18 Sep 2025 14:54:58 +0200	[thread overview]
Message-ID: <87plbnhqe5.fsf@gnu.org> (raw)
In-Reply-To: <TY3PR01MB11346F452EAE530A0931C9D228614A@TY3PR01MB11346.jpnprd01.prod.outlook.com> (Biju Das's message of "Tue, 16 Sep 2025 14:02:36 +0000")


Hey,

> Also, you need a patch to identify the device and pass it as blob
> to the mainline u-boot
>
> On TF-A:
> .ep_info.args.arg1 = (uintptr_t)fdt_blob,
>
> Also you should fill the memory blob(fdt_blob).
>
> Hope you can take over from here.

Thanks Marek and Biju. The current state is still that people will take
the forked Renesas TF-A, the mainline U-Boot with the
renesas_rzg2l_smarc_defconfig configuration and expect things to work
out of the box.

Currently, before figuring out that the TF-A needs to be patched
manually, U-Boot is just crashing without outputing anything, which is
painful to debug.

As the only RZG2L supported by U-Boot is the r9a07g044l2-smarc, and we
are not receiving any blob from the TF-A, I think it is fair to assume
that we are booting from the platform we are compiling U-Boot for.

I have proposed a patch here:
https://lists.denx.de/pipermail/u-boot/2025-September/598712.html

Thanks,

Mathieu

  reply	other threads:[~2025-09-18 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 12:49 RZG2L and DTB blob from TF-A Mathieu Othacehe
2025-09-16 13:29 ` Marek Vasut
2025-09-16 14:02   ` Biju Das
2025-09-18 12:54     ` Mathieu Othacehe [this message]
2025-09-18 13:11       ` Biju Das
2025-09-18 14:33         ` Mathieu Othacehe
2025-09-18 14:41           ` Biju Das
2025-10-07  6:41             ` Biju Das
2025-09-18 13:14       ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plbnhqe5.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=anton.reding@landisgyr.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=marek.vasut@mailbox.org \
    --cc=paul@pbarker.dev \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.