From: Jon Hunter <jonathanh@nvidia.com>
To: webgeek1234@gmail.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: tegra: Add reserved-memory node for P2180
Date: Fri, 24 Oct 2025 17:17:02 +0100 [thread overview]
Message-ID: <b31b45f1-4ef9-46b4-8b8b-bbfdfbfa3cf5@nvidia.com> (raw)
In-Reply-To: <20250803-p3450-mts-bug-v2-2-6307125408c3@gmail.com>
On 04/08/2025 04:14, Aaron Kling via B4 Relay 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.
Same comment applies here as I mentioned on the previous patch.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-10-24 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 3:14 [PATCH v2 0/2] arm64: tegra: Add reserved-memory node to L4T Tegra210 devices Aaron Kling via B4 Relay
2025-08-04 3:14 ` [PATCH v2 1/2] arm64: tegra: Add reserved-memory node for P3450 Aaron Kling via B4 Relay
2025-10-24 16:16 ` Jon Hunter
2025-10-24 17:46 ` Aaron Kling
2025-10-28 10:32 ` Jon Hunter
2025-10-29 19:54 ` Aaron Kling
2025-10-31 10:47 ` Jon Hunter
2025-08-04 3:14 ` [PATCH v2 2/2] arm64: tegra: Add reserved-memory node for P2180 Aaron Kling via B4 Relay
2025-10-24 16:17 ` Jon Hunter [this message]
2025-10-20 19:28 ` [PATCH v2 0/2] arm64: tegra: Add reserved-memory node to L4T Tegra210 devices Aaron Kling
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=b31b45f1-4ef9-46b4-8b8b-bbfdfbfa3cf5@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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