linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Chauvet <kwizart@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Aaron Kling <webgeek1234@gmail.com>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org,  linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] arm64: tegra: Add reserved-memory node for P3450
Date: Thu, 3 Jul 2025 18:23:58 +0200	[thread overview]
Message-ID: <CABr+WTnn2qOXEMCiRDywySAxn0UeKAcx5XOJNpn731tXxbCPDQ@mail.gmail.com> (raw)
In-Reply-To: <nuicekbfdgjbfudtlul74ifsqckfg6itybb76bkzuaxfcp5ve5@yevlttgtobxy>

Le jeu. 3 juil. 2025 à 13:00, Thierry Reding
<thierry.reding@gmail.com> a écrit :
>
> On Mon, May 26, 2025 at 02:07:35PM -0500, Aaron Kling wrote:
> > On Mon, May 26, 2025 at 2:06 PM Aaron Kling via B4 Relay
> > <devnull+webgeek1234.gmail.com@kernel.org> wrote:
> > >
> > > From: Aaron Kling <webgeek1234@gmail.com>
> > >
> > > The Tegra210 L4T bootloader ram training will corrupt the in-ram kernel
> > > dt if no reserved-memory node exists. This prevents said bootloader from
> > > being able to boot a kernel without this node, unless a chainloaded
> > > bootloader loads the dt. Add the node to eliminate the requirement for
> > > extra boot stages.

Is there any particular reason why this applies on jetson-nano but not
jetson-tx1 (or any other l4t based boards ?)
I wonder if it would be enough to boot an upstream kernel with the l4t
bootloader (and no chainloaded upstream u-boot) as I cannot do the
other way for some reason (using fedora based upstream u-boot cannot
boot downstream l4t kernel anymore)

Thanks for the hints.

  reply	other threads:[~2025-07-03 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 19:06 [PATCH RFC] arm64: tegra: Add reserved-memory node for P3450 Aaron Kling via B4 Relay
2025-05-26 19:07 ` Aaron Kling
2025-06-30 19:34   ` Aaron Kling
2025-07-03 10:29   ` Thierry Reding
2025-07-03 16:23     ` Nicolas Chauvet [this message]
2025-07-03 16:40       ` Aaron Kling
2025-07-14  5:39         ` Aaron Kling
2025-07-31 21:37           ` Aaron Kling
2025-08-01  9:39             ` Thierry Reding

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=CABr+WTnn2qOXEMCiRDywySAxn0UeKAcx5XOJNpn731tXxbCPDQ@mail.gmail.com \
    --to=kwizart@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=webgeek1234@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).