linux-kernel - Re: [PATCH v2 0/4] memory: tegra210-emc: Support Device Tree EMC Tables

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CALHNRZ8qyu6wsTTnmRWtNgYL4XWR8G7TFammqTFPfHH5d==LbA@mail.gmail.com>
Date: Mon, 30 Jun 2025 14:26:06 -0500
From: Aaron Kling <webgeek1234@...il.com>
To: Thierry Reding <thierry.reding@...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 Wed, May 28, 2025 at 12:41 PM Aaron Kling <webgeek1234@...il.com> wrote:
>
> On Thu, May 8, 2025 at 7:48 AM Thierry Reding <thierry.reding@...il.com> wrote:
> >
> > 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
>
> Thierry, has there been any feedback about this?
>

Reminder about this question. Has there been any response from the
Nvidia Android team? Or do I/we need to continue pursuing independent
solutions?

Aaron