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]
Date: Tue, 23 Jan 2024 17:18:49 +0000
From: Conor Dooley <conor@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Amrit Anand <quic_amrianan@...cinc.com>,
	Trilok Soni <quic_tsoni@...cinc.com>, robh+dt@...nel.org,
	krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
	agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-msm@...r.kernel.org, kernel@...cinc.com,
	Elliot Berman <quic_eberman@...cinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: Introduce board-id

On Tue, Jan 23, 2024 at 12:50:07PM +0100, Krzysztof Kozlowski wrote:
> On 22/01/2024 11:10, Amrit Anand wrote:
> > 
> > On 1/21/2024 12:40 AM, Trilok Soni wrote:
> >> On 1/20/2024 3:20 AM, Amrit Anand wrote:
> >>> From: Elliot Berman <quic_eberman@...cinc.com>
> >>>
> >>> Device manufacturers frequently ship multiple boards or SKUs under a
> >>> single software package. These software packages will ship multiple
> >>> devicetree blobs and require some mechanism to pick the correct DTB for
> >>> the board the software package was deployed. Introduce a common
> >>> definition for adding board identifiers to device trees. board-id
> >>> provides a mechanism for bootloaders to select the appropriate DTB which
> >>> is vendor/OEM-agnostic.
> >> Please extend CC list to more architectures? linux-arm-kernel, risc-v etc; since
> >> the proposal below is not specific to ARM but any architecture is using the
> >> devicetree.
> > Wouldn't devicetree@...r.kernel.org will have concern folks from all the 
> > architectures?
> > Please correct me.
> 
> No.

The chromium guys should get a CC on future versions of this stuff,
since they like doing wacky things with compatible strings in their
bootloader and this problem is one they also face. Doug Anderson and the
mediatek chromebook folks would be a good start.

Thanks,
Conor.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ