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: <47c966c7-8736-44a2-8ec7-4d7989efa9cd@kernel.org>
Date: Mon, 12 Aug 2024 08:15:45 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Tingwei Zhang <quic_tingweiz@...cinc.com>,
 Tengfei Fan <quic_tengfan@...cinc.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konrad.dybcio@...aro.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: kernel@...cinc.com, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: sa8775p-ride: Add QCS9100
 compatible

On 12/08/2024 04:16, Tingwei Zhang wrote:
> On 8/8/2024 7:05 PM, Krzysztof Kozlowski wrote:
>> On 07/08/2024 13:04, Tingwei Zhang wrote:
>>> On 8/7/2024 5:35 PM, Krzysztof Kozlowski wrote:
>>>> On 07/08/2024 11:17, Tengfei Fan wrote:
>>>>>
>>>>>
>>>>> On 8/7/2024 3:28 PM, Krzysztof Kozlowski wrote:
>>>>>> On 06/08/2024 06:19, Tengfei Fan wrote:
>>>>>>> Add QCS9100 compatible in sa8775p ride and sa8775p ride r3 board DTS.
>>>>>>> QCS9100 references SA8775p, they share the same SoC DTSI and board DTS.
>>>>>>>
>>>>>>
>>>>>> I don't understand this. You claim here that QCS9100 references SA8775p
>>>>>> but your diff says other way: SA8775p references QCS9100.
>>>>>>
>>>>>> Sorry, that's confusing.
>>>>>>
>>>>>> Best regards,
>>>>>> Krzysztof
>>>>>>
>>>>>
>>>>> I will update the compatible as follows to indicate that QCS9100
>>>>> references SA8775p.
>>>>>
>>>>> compatible = "qcom,sa8775p-ride", "qcom,qcs9100", "qcom,sa8775p";
>>>>
>>>> Is this still correct, though? sa8775p won't come with qcs9100 SoC.
>>> We have a new board. Hardware is same as sa877p-ride except sa8775p is
>>> replaced with qcs9100. We add qcs9100 SoC compatible to sa8775p-ride
>>
>> Does "new board" mean that "old board" disappears? No users to care
>> about it? Or just the existing board is being changed (like new revision)?
> 
> We will support both boards. Sa8775p-ride board with sa8775p chipset and 
> sa8775p-ride board with qcs9100 chipset. Both of them can be used for 
> development.

Patch does something else then - changes compatibles for the existing
(old) board.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ