From: Ry Pemberton via <help-guix@gnu.org>
To: me@tobias.gr
Cc: help-guix@gnu.org
Subject: Re: Regarding implementing sof-firmware in GUIX.
Date: Fri, 10 Dec 2021 23:58:56 +0000 [thread overview]
Message-ID: <rtq796p976DdxyVFYxCUwhQxRl9t7aQMrZLDFtl2dJ3Obm1ycAhevJK1r8fy0BQXoDWyGDi8IrJchBiPh3355Dhes2vYwx_gidZffFYnZbw=@pm.me> (raw)
In-Reply-To: <87a6h83wlz.fsf@nckx>
Is there anything I could do to help? I have little to no experience with these kinds of things but maybe this is a fine jumping off point.
And thank you for the correction, I wasn't aware it was case sensitive (or a meme for that matter).
Thanks!
-------- Original Message --------
On Dec 10, 2021, 2:38 PM, Tobias Geerinckx-Rice wrote:
> Ry, [PSA: It's just ‘[GNU] Guix’, never ‘GUIX’ :-) I'm not sure why the ‘GUIX’ meme appears to be picking up steam again as of late…] Ry Pemberton via 写道： > I have an X1 Carbon (2021) that requires sof-firmware. It is > libre > software, and I believe is included in the linux-libre kernel > since > 5.2. Is there a way to get this firmware working on this laptop > with > GNU GUIX? I tried to start a basic SOF package (attached), but quickly ran into ‘The GNU C library is currently unavailable for this platform.’ Without a cross-libc the build fails, looking for , which AFAICT is provided (only) by libc. I've never cross-compiled firmware before so I don't know any next steps. Of course, this being ostensibly libre software, we could package prebuilt binaries[0] as I'm sure 99% of users actually use. It's not a good option, and hardly Guixy, but not unprecedented. Kind regards, T G-R [0]: https://github.com/thesofproject/sof-bin/
next prev parent reply other threads:[~2021-12-10 23:59 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 [this message]
2021-12-11 8:40 ` Mathieu Othacehe
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='rtq796p976DdxyVFYxCUwhQxRl9t7aQMrZLDFtl2dJ3Obm1ycAhevJK1r8fy0BQXoDWyGDi8IrJchBiPh3355Dhes2vYwx_gidZffFYnZbw=@pm.me' \
--to=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).