From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 38403@debbugs.gnu.org
Subject: [bug#38403] [PATCH] gnu: Add intel-vaapi-driver-g45-h264.
Date: Thu, 16 Apr 2020 00:32:05 +0200 [thread overview]
Message-ID: <87v9m0z8gq.fsf@nckx> (raw)
In-Reply-To: <87lfrzueuc.fsf@jlicht.xyz>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Necro tiem (thanks Vincent),
Jelle Licht 写道：
>> These devices don't have their own RAM chips, so ‘by default’
>> here
>> means the BIOS menu setting, right? If so, it should be
>> mentioned
>> in the description for lack of upstream documentation.
> This is correct. I think it makes sense to point people to the
> right
> documentation for at least libreboot and coreboot, and refer
> them to
> their BIOS supplier for other instructions.
>
> OTOH, I do not feel that the package description is the right
> place to
> do this.
I agree it's not ideal.
> Where would such instructions normally exist on GNU/Linux
> machines?
Well… /share/doc. I check it; I don't know how many people
(still) do.
It seems to be less well known than it used to be, which is a
shame, but it's technically the answer to your question.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-15 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 16:59 [bug#38403] [PATCH] gnu: Add intel-vaapi-driver-g45-h264 Jelle Licht
2019-11-27 18:58 ` Tobias Geerinckx-Rice via Guix-patches via
2019-11-29 11:00 ` Jelle Licht
2020-04-15 22:32 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-04-13 17:52 ` Vincent Legoll
2020-04-13 20:01 ` Jelle Licht
2020-04-15 22:06 ` Vincent Legoll
2020-09-12 11:20 ` Jelle Licht
2022-01-31 17:51 ` iung--- via Guix-patches via
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=87v9m0z8gq.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=38403@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=me@tobias.gr \
/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).