[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_2068AC70F1DA5AF46F600C7718FEB1B98307@qq.com>
Date: Wed, 11 Jan 2023 03:56:23 +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 10/01/2023 20:32, krzysztof.kozlowski@...aro.org wrote:
>
> Then I am not sure if we want to support such devices mainline. It is not
only
> anonymity but simply not following standards and practices.
> What's more there is no guarantee what this device is. If there is no
known
> manufacturer, anytime another device from anyone can claim it is also
uf896.
> IOW, what guarantees you have that other person who has something looking
> like "uf896" actually has something the same as you and can use your DTB?
There is a label printed (i.e. ufi001c or uf896 or something else but not
getting mainlined now) on the board, different models have different
labels(and different board design). And currently I know all ufi001c(even
some other models) shares the same device tree, as a downstream device tree
has been tested by thousands of people. I'm not familiar with uf896 as it is
owned by Nikita Travkin and tested by him. The device sells very well and
many people will benefit from mainlining.
Powered by blists - more mailing lists