unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: guix-devel@gnu.org,  phodina@protonmail.com,  ludo@gnu.org
Subject: Re: 04/04: gnu: Add fwupd.
Date: Thu, 01 Sep 2022 16:35:52 -0400	[thread overview]
Message-ID: <87edwu96jb.fsf@gmail.com> (raw)
In-Reply-To: <20220901154232.1a568486@primary_laptop> (Denis Carikli's message of "Thu, 1 Sep 2022 15:42:32 +0200")

Hello Denis,

Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:

> Hi,
>
> On Wed, 31 Aug 2022 09:26:21 -0400
> Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> > commit 23152ff70f0ed4966d8207846f54c793d7cb4f86
>> > Author: Petr Hodina <phodina@protonmail.com>
>> > AuthorDate: Tue Jan 4 06:58:51 2022 +0100
>> >
>> >     gnu: Add fwupd.
>> >     
>> >     * gnu/packages/firmware.scm (fwupd): New variable.
>> >     
>> >     Signed-off-by: Ludovic Courtès <ludo@gnu.org>
>> 
>> Just a quick question: does this tool talks to a remote server that
>> serves non-free software as well as free one?  If so, it'd need to be
>> patched to comply with the FSDG.
> It does.
>
> By default it at least uses the LVFS repository which has nonfree
> software. I don't remember if it also has other repositories or if
> there was a way to easily download updates from the repository
> without fwupd or LVFS.
>
> It is at least possible to search for specific software in LVFS at this
> address: https://fwupd.org/lvfs/search?value=microcode
>
> You also have UEFI updates and so on there, so it's pretty clear that
> there is some nonfree software.
>
> And we actually have the opposite issue here: It is way harder to find
> firmware updates that are fully free and that they can at least in
> theory be built with 100% free software on top of FSDG compliant
> distributions.
>
> Maybe small free software firmwares like the colorhug firmware could be
> OK. Somebody would need to check the dependencies for build the
> firmware update.
>
> Bigger firmwares like with firmwares using Coreboot are probably not
> OK because while coreboot is under the GPL, to work on recent
> hardware nonfree software is likely to be used (like microcode updates,
> Intel FSP, nonfree AGESA, etc).

Thanks.

With this in mind, I've disabled the default "remotes", which seem to be
the metadata for specifying which remote server to interrogate for
firmware.  Users knowing what they want can enable them manually.

See commit 4d361a6b5147e3f91573e9d3c8c540a233e7e142.

Testers welcome!

Thanks,

Maxim


      reply	other threads:[~2022-09-01 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166194391661.31756.9547474130907902222@vcs2.savannah.gnu.org>
     [not found] ` <20220831110517.76C23C04F0B@vcs2.savannah.gnu.org>
2022-08-31 13:26   ` 04/04: gnu: Add fwupd Maxim Cournoyer
2022-08-31 14:58     ` Liliana Marie Prikler
2022-09-01  6:27       ` Reza Housseini
2022-09-01  7:03         ` Maxime Devos
2022-09-01  7:44           ` phodina
2022-09-01 13:42     ` Denis 'GNUtoo' Carikli
2022-09-01 20:35       ` Maxim Cournoyer [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=87edwu96jb.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=GNUtoo@cyberdimension.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=phodina@protonmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).