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] [day] [month] [year] [list]
Message-ID: <3qk6i5infwcahkmwn5p4n5hfspdvjd3azimrfkk637z6ar2hpe@vb7zvytl3zk4>
Date: Thu, 13 Nov 2025 22:40:24 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Sudarshan Shetty <tessolveupstream@...il.com>, konradybcio@...nel.org, 
	robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
	linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/2] arm64: dts: qcom: talos-evk: Add support for
 QCS615 talos evk board

On Thu, Nov 13, 2025 at 10:08:20PM +0200, Dmitry Baryshkov wrote:
> On Fri, Nov 07, 2025 at 04:27:35PM +0530, Sudarshan Shetty wrote:
> > Introduce the device tree support for the QCS615-based talos-evk
> 
> You can't introduce DT _support_. It's either introducing a DT or
> supporting.
> 
> > platform, which follows the SMARC (Smart Mobility ARChitecture)
> > standard. The platform is composed of two main hardware
> > components: the talos-evk-som and the talos-evk-cb.
> 
> are those the actual names? I'd say, the platform is composed of the SoM
> (following some standard or not) and a Carrier Board.
> 

That's likely accurate, but in the patch the "carrier board" includes
the talos-evk-som.dtsi. So, while what you say probably is correct,
"talos-evk-cb.dtsi" describes what I believe is actually the EVK.

Regards,
Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ