[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ckimvttxjgx44xhfql3nov3qbf35y73nbu3p4m63nqbi22vh37@6p2ji7he5toy>
Date: Thu, 8 May 2025 14:48:21 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Aaron Kling <webgeek1234@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Jonathan Hunter <jonathanh@...dia.com>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/4] memory: tegra210-emc: Support Device Tree EMC
Tables
On Thu, May 08, 2025 at 07:27:52AM -0500, Aaron Kling wrote:
[...]
> The devices I'm talking about are not yet end of life, so it is
> physically possible for them to get a bootloader update to conform to
> the existing mainline model. But I'm just one guy trying to do 3rd
> party support for these devices, I can't affect what Nvidia does with
> the signed bootloader on these devices. I'd love to be able to swap
> out an open source bootloader on these, but the secure boot setup
> prevents that.
I've reached out to our Android team internally to see if there's
anything we can realistically do about this.
Thierry
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists