linux-kernel - Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4gx66y2oncjppqjhap5q2fmwlgkhv74rupeo4iwbyqw6ipoddn@fpp56byglnwe>
Date: Mon, 15 Sep 2025 22:26:30 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Bjorn Andersson <bjorn.andersson@....qualcomm.com>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon

On Fri, Sep 12, 2025 at 04:22:18AM +0300, Dmitry Baryshkov wrote:
> On Thu, Sep 11, 2025 at 02:19:39PM -0500, Bjorn Andersson wrote:
> > On Thu, Sep 11, 2025 at 03:01:35AM +0300, Dmitry Baryshkov wrote:
> > > On Wed, Sep 10, 2025 at 06:05:36PM -0500, Bjorn Andersson wrote:
> > > > Introduce the Particle Tachyon board (https://www.particle.io/tachyon/),
> > > > a single board compute with 5G connectivity and AI accelerator.
> > > > 
> > > > The boards currently ships with the Android Boot Loader, but replacing
> > > > this with abl2esp allows writing a EFI System Parition and OS partitions
> > > > to all of LUN0, and a more UEFI boot experience. A prebuilt version of
> > > > abl2esp is provided at [1], as abl2esp-v6.elf.
> > > > 
> > > > With a (very) recent version of QDL, a flash programmer from a Tachyon
> > > > software release, and a full distro image, this can be achieved with:
> > > > 
> > > >   qdl prog_firehose_ddr.elf write abl_a abl2esp-v6.elf write abl_b abl2esp-v6.elf write 0 image.raw
> > > > 
> > > > The following firmware files are currently used, on top of what's in
> > > > linux-firmware already:
> > > >   qcom/qcm6490/particle/tachyon/a660_zap.mbn
> > > >   qcom/qcm6490/particle/tachyon/adsp.mbn
> > > >   qcom/qcm6490/particle/tachyon/cdsp.mbn
> > > >   qcom/qcm6490/particle/tachyon/ipa_fws.mbn
> > > >   qcom/qcm6490/particle/tachyon/modem.mbn
> > > 
> > > Is it locked?
> > 
> > It doesn't look that way.
> 
> Then anything preventing us from using the default, non-signed FW?
> 

Looking at the version, they are not from the same branch or year.

I suggest that we stick with the firmware that the vendor has validated
on their piece of hardware together with the other pieces of firmware,
at least for now.

Once/if we built confidence in the QLI firmware, we can replace these
paths.

Regards,
Bjorn

> > 
> > > Would it be possible to Particle-signed firmware into linux-firmware?
> > 
> > That is something that would have to be discussed...
> 
> It would be really nice...
> 
> -- 
> With best wishes
> Dmitry