linux-kernel - RE: [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896

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: <tencent_F0BF70A75A0E742E6000F7617EE53999E807@qq.com>
Date:   Wed, 11 Jan 2023 18:21:03 +0800
From:   <forbidden405@...mail.com>
To:     "'Krzysztof Kozlowski'" <krzysztof.kozlowski@...aro.org>,
        "'Andy Gross'" <agross@...nel.org>,
        "'Bjorn Andersson'" <andersson@...nel.org>,
        "'Konrad Dybcio'" <konrad.dybcio@...aro.org>,
        "'Rob Herring'" <robh+dt@...nel.org>,
        "'Krzysztof Kozlowski'" <krzysztof.kozlowski+dt@...aro.org>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Cc:     "'Jaime Breva'" <jbreva@...arsystems.com>,
        <~postmarketos/upstreaming@...ts.sr.ht>,
        "'Nikita Travkin'" <nikita@...n.ru>
Subject: RE: [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896

On 11/01/2023 09:32, krzysztof.kozlowski@...aro.org wrote:

> This does not solve my concerns. If you cannot point specific manufacturer 
> and
> model (if there is no manufacturer, there can be no official model, 
> right?), how
> anyone can be sure that their device is compatible with yours?

1. the best way is to take the device apart and compare the board design 
with others;
2. the label on board, though format unknown, seems to be different between 
different models and identical for one model;
3. read board-id from stock Android firmware. It's not reliable because a 
board-id might be shared by multiple models. Note this board-id has no other usage because the manufacturer reused a board-id defined by qcom.

We extract some special fields from the label(i.e. ufi001c or uf896) to be 
the model name for a device, currently it's enough to distinguish between 
different boards. 
For example, the label on ufi001c is 'UFI001C_MB_V01', we extract the first field to be the model name.