Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <tencent_F0BF70A75A0E742E6000F7617EE53999E807@qq.com>
From:   <forbidden405@foxmail.com>
To:     "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
        "'Andy Gross'" <agross@kernel.org>,
        "'Bjorn Andersson'" <andersson@kernel.org>,
        "'Konrad Dybcio'" <konrad.dybcio@linaro.org>,
        "'Rob Herring'" <robh+dt@kernel.org>,
        "'Krzysztof Kozlowski'" <krzysztof.kozlowski+dt@linaro.org>,
        <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Cc:     "'Jaime Breva'" <jbreva@nayarsystems.com>,
        <~postmarketos/upstreaming@lists.sr.ht>,
        "'Nikita Travkin'" <nikita@trvn.ru>
References: <20230110155014.31664-1-forbidden405@foxmail.com> <tencent_A7FA00B086BB0EFFDC1C64744FF85DAD2B06@qq.com> <8530aeef-8fdb-ede7-700e-856e5cbc6a5b@linaro.org> <tencent_98E029F744FE85B9FD68B570A45A01743F07@qq.com> <f909c1b0-97db-cc33-fa27-c5e901f11956@linaro.org> <tencent_235CAC16001D1C38CE7D86BF7B0E365A2105@qq.com> <0453b098-91db-1918-38ae-a7db0408460c@linaro.org> <tencent_2068AC70F1DA5AF46F600C7718FEB1B98307@qq.com> <3fb51f6a-84b7-c35b-d4b0-332671988594@linaro.org>
In-Reply-To: <3fb51f6a-84b7-c35b-d4b0-332671988594@linaro.org>
Subject: RE: [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896
Date:   Wed, 11 Jan 2023 18:21:03 +0800
MIME-Version: 1.0
Content-Type: text/plain;
        charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: zh-cn
Thread-Index: AQEO7BERPzOKD8mdDN9nK2Zc/pFyZgG3SCqUAZiImfcCstHu6AF93epXAffz5noBRJuEcQD3Xbi/AZKgzz8DEhceeQ==
Precedence: bulk

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

> This does not solve my concerns. If you cannot point specific =
manufacturer=20
> and
> model (if there is no manufacturer, there can be no official model,=20
> 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=20
different models and identical for one model;
3. read board-id from stock Android firmware. It's not reliable because =
a=20
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=20
the model name for a device, currently it's enough to distinguish =
between=20
different boards.=20
For example, the label on ufi001c is 'UFI001C_MB_V01', we extract the =
first field to be the model name.