From: jbranso--- via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 58357@debbugs.gnu.org, efraim@flashner.co.il
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Fri, 14 Oct 2022 19:28:58 +0000 [thread overview]
Message-ID: <fd4f624a3d5ee6942a42e45d3dcbef21@dismail.de> (raw)
In-Reply-To: <87sfjqqqm7.fsf@pelzflorian.de>
October 14, 2022 1:10 PM, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> Hello! Some comments:
>
> 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.
>
OpenBSD lists supported hardware on their website:
https://www.openbsd.org/arm64.html as an example.
Joshua
next prev parent reply other threads:[~2022-10-14 19:30 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
2022-10-14 19:28 ` jbranso--- via Guix-patches via [this message]
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=fd4f624a3d5ee6942a42e45d3dcbef21@dismail.de \
--to=guix-patches@gnu.org \
--cc=58357@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jbranso@dismail.de \
--cc=ludo@gnu.org \
--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).