From: "Vivek Puar" <vpuar@qti.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-firmware: upgrade 20260110 -> 20260221
Date: Sun, 22 Feb 2026 21:21:59 -0800 [thread overview]
Message-ID: <1030996.1771824119017163262@lists.openembedded.org> (raw)
In-Reply-To: <20260222212156.55731-1-dmitry.baryshkov@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Mon, Feb 23, 2026 at 02:52 AM, Dmitry Baryshkov wrote:
>
> +FILES:${PN}-qcom-sm8750-audio =
> "${nonarch_base_libdir}/firmware/qcom/sm8750/adsp*.*
> ${nonarch_base_libdir}/firmware/qcom/sm8750/*tplg.bin.*"
There is a type, no "." after bin
>
> + ${nonarch_base_libdir}/firmware/qcom/x1e80100/X1E80100-CRD-tplg.bin.zst*
> \
>
It will be, X1E80100-CRD-tplg.bin*?
>
> +LICENSE:${PN}-qcom-qcs6490-radxa-dragon-q6a-compute = "Firmware-qcom"
>
Will it have linaro license also?
Missing RDEPENDS for " qcom-qcs6490-radxa-dragon-q6a-compute"?
[-- Attachment #2: Type: text/html, Size: 4882 bytes --]
next prev parent reply other threads:[~2026-02-23 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 21:21 [PATCH] linux-firmware: upgrade 20260110 -> 20260221 Dmitry Baryshkov
2026-02-23 5:21 ` Vivek Puar [this message]
2026-02-23 5:28 ` Vivek Puar
2026-02-23 18:43 ` Dmitry Baryshkov
2026-02-24 5:09 ` Vivek Puar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1030996.1771824119017163262@lists.openembedded.org \
--to=vpuar@qti.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox