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: Sat, 20 Jan 2024 11:10:32 -0800
From: Trilok Soni <quic_tsoni@...cinc.com>
To: Amrit Anand <quic_amrianan@...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>
CC: <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 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. 

-- 
---Trilok Soni


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ