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: <paksdvlwrbmdo7wg5cuzdazi4epu3oukxdavkkzoje2gw7aeuy@grsls7hp4khb>
Date: Thu, 3 Jul 2025 12:37:53 +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 Mon, Jun 30, 2025 at 02:26:06PM -0500, Aaron Kling wrote:
> 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?

There's been no decision either way, but it's fairly complicated because
the changes involved here are fairly large, even if the impact should be
fairly low.

If all else fails, do we have other alternatives? I suspect that adding
some sort of shim that runs prior to the kernel won't work because the
EMC tables just aren't accessible from the bootloader anymore. Would it
entail parsing the entirety of the DT EMC tables and transcribing them
into some memory and pass that to the kernel?

Thierry

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ