From: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Mathieu Othacehe <othacehe@gnu.org>, Ry Pemberton <rpem66@pm.me>,
help-guix@gnu.org
Subject: Re: Regarding implementing sof-firmware in GUIX.
Date: Sun, 12 Dec 2021 05:20:44 +0100 [thread overview]
Message-ID: <87sfuyjtgs.fsf@nckx> (raw)
In-Reply-To: <871r2jkplk.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Mathieu Othacehe 写道:
>> I'm not sure what's the point of letting users build their
>> firmware
>> if it cannot be loaded.
By bizarre coincidence, I was looking at our kernel configuration
for unrelated reasons and happened to notice:
CONFIG_SND_SOC_SOF=y
For the record, here's what I asked on #gnu-linux-libre:
<nckx> I ask because linux-libre provides SND_SOC_SOF_TOPLEVEL
et al.
<nckx> I'd disable it in Guix but seems better to pull it out at
the root if it is problematic.
<lxo> nckx, I left it in because there were reports of hardware
that used the unsigned images
<lxo> I found it suspicious, but borderline acceptable
<nckx> Ah, OK, so this is a known ‘hm’ already.
<nckx> I guess we'll leave it enabled for the same reason as
long as it's part of linux-libre.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-12-12 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 20:13 Regarding implementing sof-firmware in GUIX Ry Pemberton via
2021-12-10 22:38 ` Tobias Geerinckx-Rice
2021-12-10 23:58 ` Ry Pemberton via
2021-12-11 8:40 ` Mathieu Othacehe
2021-12-11 17:37 ` Tobias Geerinckx-Rice
2021-12-12 4:20 ` Tobias Geerinckx-Rice [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfuyjtgs.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=othacehe@gnu.org \
--cc=rpem66@pm.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).