unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org, Ry Pemberton <rpem66@pm.me>
Subject: Re: Regarding implementing sof-firmware in GUIX.
Date: Sat, 11 Dec 2021 09:40:08 +0100	[thread overview]
Message-ID: <87bl1nzg9j.fsf@gnu.org> (raw)
In-Reply-To: <87a6h83wlz.fsf@nckx> (Tobias Geerinckx-Rice's message of "Fri, 10 Dec 2021 23:38:30 +0100")


Hello Tobias,

> * gnu/packages/firmware.scm (sof): New public variable.

Thanks for the package definition. Last time I checked, some devices
required signed firmware:

--8<---------------cut here---------------start------------->8---
The firmware file, /lib/firmware/intel/sof/sof-tgl.ri, contains all DSP
code and tables. On PCI devices, the firmware can only be signed by an
Intel production key which prevents community users from installing
their own firmware. Notable exceptions include Google Chromebooks and
Up2/Up-Extreme boards, where the community key is used.
--8<---------------cut here---------------end--------------->8---

I'm not sure what's the point of letting users build their firmware if
it cannot be loaded. Looks like multiple projects are in fact packaging
the signed sof firmware, which is non-free[2].

Thanks,

Mathieu

[1]: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html
[2]: https://packages.debian.org/search?keywords=firmware-sof-signed


  parent reply	other threads:[~2021-12-11  8:40 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 [this message]
2021-12-11 17:37     ` Tobias Geerinckx-Rice
2021-12-12  4:20       ` Tobias Geerinckx-Rice

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=87bl1nzg9j.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    --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).