From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sof-firmware: update to 1.9.
Date: Fri, 15 Oct 2021 06:55:31 +0200 [thread overview]
Message-ID: <20211015045531.M6-KwYRrww58LYpfhdsMsaj0jAsEiiA_b0vJp8JFqAk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33318@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/33318#issuecomment-943989565
Comment:
@ericonr
> Hm, any reason it can't be the same package?
According to earlier discussions (that I think took place on IRC) the consensus was that it would be best to install pre-built firmware binaries instead of building them manually. As such, if we're building the tools from source, the firmware would come from the `sof-bin` repo and the tools would come from the `sof` repo. Unless you're suggesting using two distfiles in one package?
Also, regarding that musl error, that parsing step is performed by a tool from `alsa-utils`. Unless we have examples of that working correctly on musl in other circumstances, it is equally likely to be the fault of their topologies as it is that tool.
next prev parent reply other threads:[~2021-10-15 4:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 16:13 [PR PATCH] " kkga
2021-10-04 16:15 ` kkga
2021-10-04 16:44 ` kkga
2021-10-04 19:16 ` cinerea0
2021-10-04 23:01 ` kkga
2021-10-08 13:42 ` [PR REVIEW] " ericonr
2021-10-14 18:45 ` cinerea0
2021-10-14 18:46 ` [PR REVIEW] " cinerea0
2021-10-14 20:55 ` [PR PATCH] [Updated] " kkga
2021-10-14 20:59 ` kkga
2021-10-14 23:22 ` kkga
2021-10-15 4:03 ` ericonr
2021-10-15 4:04 ` ericonr
2021-10-15 4:38 ` cinerea0
2021-10-15 4:39 ` cinerea0
2021-10-15 4:43 ` cinerea0
2021-10-15 4:55 ` cinerea0 [this message]
2021-10-15 5:29 ` ericonr
2021-10-25 0:54 ` ericonr
2021-10-25 1:58 ` cinerea0
2021-10-25 2:02 ` ericonr
2021-10-25 3:23 ` cinerea0
2021-10-25 7:57 ` [PR PATCH] [Updated] " kkga
2021-10-25 13:21 ` ericonr
2021-10-25 13:21 ` ericonr
2021-10-25 19:31 ` [PR PATCH] [Updated] " kkga
2021-10-29 3:31 ` [PR PATCH] [Merged]: " ericonr
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=20211015045531.M6-KwYRrww58LYpfhdsMsaj0jAsEiiA_b0vJp8JFqAk@z \
--to=cinerea0@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).