unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: jbranso@dismail.de, efraim@flashner.co.il, 58357@debbugs.gnu.org
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Mon, 17 Oct 2022 18:35:00 +0200	[thread overview]
Message-ID: <87zgdupfwr.fsf@gnu.org> (raw)
In-Reply-To: <87sfjqqqm7.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Fri, 14 Oct 2022 19:09:20 +0200")

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>> This discussion and others we had at the Ten Years of Guix event makes
>> me think we should strive to avoid bad surprises by being more
>> explicit.  Concretely, we could:
>>
>>   • Under “Hardware Considerations”, list common devices known not to
>>     work without non-free {firm,soft}ware, such as Intel Wifi (iwlwifi).
>>     We cannot be exhaustive but we should at least mention common
>>     problems with recent x86_64 laptops.
>
> My impression is that the dire wifi situation is explained well enough
> in Hardware Considerations already.

It is, but:

  1. It’s not as prominent and explicit as it could be: it’s within a
     paragraph (as opposed to a table), there’s no mention of iwlwifi,
     etc.

  2. The situation got worse in the meantime: see “Background” in
     <https://blog.einval.com/2022/04/19>.

>>   • Under “Hardware Considerations”, make the list of devices known to
>>     work clearer, in tabular form, perhaps expanding it.
>
> There is a list of image types like novena and pine64.

By devices, I meant primarily WiFi devices, sound cards, etc. for the
more common x86_64 hardware.

Thanks,
Ludo’.




  parent reply	other threads:[~2022-10-17 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yz/FHD608HeU6iIM@3900XT>
2022-10-07 14:24 ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55   ` pelzflorian (Florian Pelz)
2022-10-08 15:33   ` jbranso--- via Guix-patches via
2022-10-10 10:07     ` pelzflorian (Florian Pelz)
2022-10-14 15:12       ` Ludovic Courtès
2022-10-14 15:47         ` kiasoc5 via Guix-patches via
2022-10-15  9:47           ` pelzflorian (Florian Pelz)
2022-10-16 11:53             ` pelzflorian (Florian Pelz)
2022-10-14 17:09         ` pelzflorian (Florian Pelz)
2022-10-15 15:51           ` pelzflorian (Florian Pelz)
2022-10-17 16:35           ` Ludovic Courtès [this message]
2022-10-14 19:28         ` jbranso--- via Guix-patches via
2022-11-03 19:21         ` Ludovic Courtès
2022-11-16  0:22   ` pelzflorian (Florian Pelz)
2022-11-16 23:16     ` jbranso--- via Guix-patches via
2022-11-17 16:26       ` pelzflorian (Florian Pelz)
2022-11-19 14:06         ` Joshua Branson via Guix-patches via
2022-12-08 17:02           ` pelzflorian (Florian Pelz)
2023-03-09 21:06     ` pelzflorian (Florian Pelz)
2023-08-20 17:44       ` pelzflorian (Florian Pelz)

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=87zgdupfwr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=58357@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=jbranso@dismail.de \
    --cc=pelzflorian@pelzflorian.de \
    /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).