1. Patchew
  2. linux
  3. View series

[PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon

Bjorn Andersson posted 3 patches 3 weeks ago
There is a newer version of this series
Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
.../devicetree/bindings/vendor-prefixes.yaml       |   2 +
arch/arm64/boot/dts/qcom/Makefile                  |   1 +
.../boot/dts/qcom/qcm6490-particle-tachyon.dts     | 877 +++++++++++++++++++++
4 files changed, 881 insertions(+)
[PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Bjorn Andersson 3 weeks ago 
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

In addition to bug fixes that has landed in v6.17-rc this depends on
[2], which is available in linux-next.

[1] https://github.com/qualcomm/abl2esp/releases/tag/v1.0
[2] https://lore.kernel.org/all/20250811-sc7280-mdss-reset-v1-0-83ceff1d48de@oss.qualcomm.com/

Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
---
Bjorn Andersson (3):
      dt-bindings: vendor-prefixes: Add Particle Industries
      dt-bindings: arm: qcom: Add Particle Tachyon
      arm64: dts: qcom: qcm6490: Introduce the Particle Tachyon

 Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
 .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
 arch/arm64/boot/dts/qcom/Makefile                  |   1 +
 .../boot/dts/qcom/qcm6490-particle-tachyon.dts     | 877 +++++++++++++++++++++
 4 files changed, 881 insertions(+)
---
base-commit: 5f540c4aade9f1d58fb7b9490b4b7d5214ec9746
change-id: 20250910-tachyon-e3548941397d

Best regards,
-- 
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Dmitry Baryshkov 3 weeks ago 
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? Would it be possible to Particle-signed firmware into
linux-firmware?

> 
> In addition to bug fixes that has landed in v6.17-rc this depends on
> [2], which is available in linux-next.
> 
> [1] https://github.com/qualcomm/abl2esp/releases/tag/v1.0
> [2] https://lore.kernel.org/all/20250811-sc7280-mdss-reset-v1-0-83ceff1d48de@oss.qualcomm.com/
> 
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
> Bjorn Andersson (3):
>       dt-bindings: vendor-prefixes: Add Particle Industries
>       dt-bindings: arm: qcom: Add Particle Tachyon
>       arm64: dts: qcom: qcm6490: Introduce the Particle Tachyon
> 
>  Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
>  .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
>  arch/arm64/boot/dts/qcom/Makefile                  |   1 +
>  .../boot/dts/qcom/qcm6490-particle-tachyon.dts     | 877 +++++++++++++++++++++
>  4 files changed, 881 insertions(+)
> ---
> base-commit: 5f540c4aade9f1d58fb7b9490b4b7d5214ec9746
> change-id: 20250910-tachyon-e3548941397d
> 
> Best regards,
> -- 
> Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> 

-- 
With best wishes
Dmitry
Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Bjorn Andersson 3 weeks ago 
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.

> Would it be possible to Particle-signed firmware into linux-firmware?

That is something that would have to be discussed...

Regards,
Bjorn

> 
> > 
> > In addition to bug fixes that has landed in v6.17-rc this depends on
> > [2], which is available in linux-next.
> > 
> > [1] https://github.com/qualcomm/abl2esp/releases/tag/v1.0
> > [2] https://lore.kernel.org/all/20250811-sc7280-mdss-reset-v1-0-83ceff1d48de@oss.qualcomm.com/
> > 
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> > ---
> > Bjorn Andersson (3):
> >       dt-bindings: vendor-prefixes: Add Particle Industries
> >       dt-bindings: arm: qcom: Add Particle Tachyon
> >       arm64: dts: qcom: qcm6490: Introduce the Particle Tachyon
> > 
> >  Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
> >  .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
> >  arch/arm64/boot/dts/qcom/Makefile                  |   1 +
> >  .../boot/dts/qcom/qcm6490-particle-tachyon.dts     | 877 +++++++++++++++++++++
> >  4 files changed, 881 insertions(+)
> > ---
> > base-commit: 5f540c4aade9f1d58fb7b9490b4b7d5214ec9746
> > change-id: 20250910-tachyon-e3548941397d
> > 
> > Best regards,
> > -- 
> > Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> > 
> 
> -- 
> With best wishes
> Dmitry
Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Dmitry Baryshkov 2 weeks, 6 days ago 
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?

> 
> > 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
Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Bjorn Andersson 2 weeks, 2 days ago 
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
Re: [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce Particle Tachyon
Posted by Dmitry Baryshkov 2 weeks, 2 days ago 
On Mon, Sep 15, 2025 at 10:26:30PM -0500, Bjorn Andersson wrote:
> 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.


Ack.


-- 
With best wishes
Dmitry

Patchew 2.1-devel-b67e4c2

© 2016 - 2025 Red Hat, Inc.