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: <80e59b3b-2160-4e24-93f2-ab183a7cbc74@kernel.org>
Date: Wed, 15 Jan 2025 09:35:34 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wasim Nazir <quic_wasimn@...cinc.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, kernel@...cinc.com
Subject: Re: [PATCH v5 5/6] arm64: dts: qcom: Add support for QCS9075 Ride &
 Ride-r3

On 15/01/2025 06:48, Wasim Nazir wrote:
>> The the SoC, I am asking about the board. Why each of them is for
>> example r3?
>>
>> So this is not sufficient explanation, nothing about the board, and
>> again just look Renesas and NXP.
>>
> 
> Hi Krzysztof,
> 
> sa8775p(AUTO), qcs9100(IOT), qcs9075(IOT) are different SoCs based on
> safety capabilities and memory map, serving different purpose.
> Ride & Ride-r3 are different boards based on ethernet capabilities and
> are compatible with all the SoCs mentioned.

Compatible? What does it mean for a board?

Third time: did you look how other vendors do it?

> 
> With the combination of these 3 SoCs and 2 boards, we have 6 platforms,
> all of which we need.
> - sa8775p-ride.dts is auto grade Ride platform with safety feature.
> - qcs9100-ride.dts is IOT grade Ride platform with safety feature.
> - qcs9075-ride.dts is IOT grade Ride platform without safety feature.
> 
> Since the Ride-r3 boards are essentially Ride boards with Ethernet
> modifications, we can convert the Ride-r3 DTS to overlays.
How one board can be with multiple SoCs? If it is soldered, it's close
to impossible - that's just not the same board. If it is not soldered,
why you are not explaining it? What is Ride board? What is there? What
can go there? How it can be used in other SoCs? Or for which SoCs? Is
there a datasheet available?

You keep repeating my about SoC and I keep responding the same: don't care.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ