linux-kernel - Re: [PATCH RFC v3 0/9] dt-bindings: hwinfo: Introduce board-id

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: <20240605100246481-0700.eberman@hu-eberman-lv.qualcomm.com>
Date: Wed, 5 Jun 2024 10:17:22 -0700
From: Elliot Berman <quic_eberman@...cinc.com>
To: Simon Glass <sjg@...omium.org>
CC: Rob Herring <robh+dt@...nel.org>, Frank Rowand <frowand.list@...il.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio
	<konrad.dybcio@...aro.org>,
        Amrit Anand <quic_amrianan@...cinc.com>,
        "Peter
 Griffin" <peter.griffin@...aro.org>,
        Caleb Connolly
	<caleb.connolly@...aro.org>,
        Andy Gross <agross@...nel.org>, Doug Anderson
	<dianders@...omium.org>,
        Chen-Yu Tsai <wenst@...omium.org>,
        Julius Werner
	<jwerner@...omium.org>,
        "Humphreys, Jonathan" <j-humphreys@...com>,
        "Sumit
 Garg" <sumit.garg@...aro.org>,
        Jon Hunter <jonathanh@...dia.org>,
        Michal
 Simek <michal.simek@....com>,
        <boot-architecture@...ts.linaro.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH RFC v3 0/9] dt-bindings: hwinfo: Introduce board-id

On Wed, Jun 05, 2024 at 07:17:35AM -0600, Simon Glass wrote:
> Hi Elliot,
> 
> I am just picking up the discussion here, which was started on another thread.
> 
> I can't see why this new feature is needed. We should be able to use
> compatible strings, as we do now. I added a 'usage' section to the FIT
> spec [1] which might help. I also incorporated the board revision and
> variant information and some notes on how to add to the available
> suffixes.
> 
> Does that handle your use case?

-rev and -sku don't fit the versioning scheme for QTI devices, so this
isn't a generic enough approach. Patch 5 in this series describes the
versioning scheme for us.

In the other thread, we had talked about using some regex based approach
for matching the root node compatible. I haven't had chance to work on
that proposal and will try to get to it in the next couple weeks.

Thanks,
Elliot