From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36786@debbugs.gnu.org
Subject: bug#36786: Warn of AMD GPUs unusable with Guix System
Date: Fri, 26 Jul 2019 01:04:40 +0200 [thread overview]
Message-ID: <87zhl1pvg7.fsf@gnu.org> (raw)
In-Reply-To: <874l3bb6e5.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 24 Jul 2019 21:05:06 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> writes:
>
>> On Wed, Jul 24, 2019 at 05:42:49PM +0200, pelzflorian (Florian Pelz) wrote:
>>> We could make a list of known bad GPUs.
>>>
>>
>> When thinking about it, a list of known bad GPUs might be legally
>> safer than saying AMD GPUs are often bad.
>
> I sympathize with the frustration that comes along with the realization
> that hardware you own cannot be used with free software. I would like
> to alert people to the fact that certain GPUs won’t be usable with
> linux-libre.
>
> I just think that there might be a better distro-independent place for
> this kind of information. Some free distros suggest checking for free
> software compatibility on h-node.org, a shared resource. That’s also
> where we could record known bad GPUs.
>
> (h-node.org isn’t the prettiest resource out there, but perhaps this can
> be changed.)
What about adding a few words under “Hardware Considerations”?
Ludo’.
next prev parent reply other threads:[~2019-07-25 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 14:56 bug#36786: Warn of AMD GPUs unusable with Guix System pelzflorian (Florian Pelz)
2019-07-24 15:42 ` pelzflorian (Florian Pelz)
2019-07-24 17:53 ` pelzflorian (Florian Pelz)
2019-07-24 19:05 ` Ricardo Wurmus
2019-07-24 21:22 ` pelzflorian (Florian Pelz)
2019-07-25 23:04 ` Ludovic Courtès [this message]
2019-07-26 5:57 ` pelzflorian (Florian Pelz)
2019-07-26 15:56 ` Ludovic Courtès
2019-07-26 20:03 ` pelzflorian (Florian Pelz)
2021-12-07 17:42 ` Denis 'GNUtoo' Carikli
2022-11-15 23:28 ` 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=87zhl1pvg7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36786@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).