hexagon-dsp-binaries
====================

hexagon-dsp-binaries is based on the upstream repo from the linux-msm project.
The project provides (semi-)monthly tagged releases and tarballs in the form of
YYYYMMDD.

The package is assembled from two upstream tarballs: the
`hexagon-dsp-binaries` release and the `firmware` component, the part of
`linux-firmware` carrying the DSP firmware (see `debian/watch`). Both release
under the same `YYYYMMDD` tag.

Original files are not included into the Debian packaging repo. In order to
prepare for building the package:
0. Update to the new version, either with `debian/release-update` (see
   Changelog below) or with a plain `dch -v 0~YYYYMMDD-1`,
1. run `uscan --download-current-version`,
2. run `debian/rules orig` in order to unpack the orig file into build tree,
3. run `debian/rules debian/control`.

Licences
--------

Upstream tracks all licensing information in the WHENCE file. Currently all
binary files are covered by one of the two licences which allow redistribution
of the files. Qualcomm DSP firmware in the linux-firmware repository is
covered by the same licence files.

Changelog
---------

`debian/release-update` collects the changelog of a new version from the git
history of both upstreams:

    debian/release-update ~/src/hexagon-dsp-binaries ~/src/linux-firmware \
        20260810

When ran from the top of the source package, it adds a `New upstream
release` and a `New linux-firmware release` item listing the commits between
the last uploaded version and the new one, starting a new UNRELEASED entry
with `dch` if needed. Items already there, added by hand or by an earlier
run, are kept.

Of `linux-firmware` only the commits touching the files we ship are taken.
The file list comes from the `Files-Included-firmware` field of
`debian/copyright`, so it is not maintained twice. `WHENCE` is the exception,
as it is rewritten for every firmware file `linux-firmware` carries: each
commit touching it is run through `debian/filter-firmware-whence.py`, the
filter `debian/rules` applies, and is kept only if the filtered result
changes. That way a licence change to our entries shows up even when no
firmware file changes at all.

The items are upstream commit subjects, so the result is meant to be edited
afterwards -- keeping in mind that a re-run adds dropped ones back.

 -- Dmitry Baryshkov <dbaryshkov@gmail.com>, Thu, 20 Aug 2026 09:55:41 +0530
