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:   Wed, 11 Jan 2023 10:06:03 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     forbidden405@...mail.com, '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:56, forbidden405@...mail.com wrote:
> 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.

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?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ