linux-kernel - Re: [PATCH RFC] arm64: tegra: Add reserved-memory node for P3450

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABr+WTnn2qOXEMCiRDywySAxn0UeKAcx5XOJNpn731tXxbCPDQ@mail.gmail.com>
Date: Thu, 3 Jul 2025 18:23:58 +0200
From: Nicolas Chauvet <kwizart@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Aaron Kling <webgeek1234@...il.com>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Jonathan Hunter <jonathanh@...dia.com>, devicetree@...r.kernel.org, 
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] arm64: tegra: Add reserved-memory node for P3450

Le jeu. 3 juil. 2025 à 13:00, Thierry Reding
<thierry.reding@...il.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@...nel.org> wrote:
> > >
> > > From: Aaron Kling <webgeek1234@...il.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.