From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 38403@debbugs.gnu.org
Subject: [bug#38403] [PATCH] gnu: Add intel-vaapi-driver-g45-h264.
Date: Wed, 27 Nov 2019 19:58:19 +0100 [thread overview]
Message-ID: <875zj59mes.fsf@nckx> (raw)
In-Reply-To: <87y2w1uug9.fsf@jlicht.xyz>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
Jelle,
Jelle Licht 写道:
> I am not sure if this package offers any practical benefit or
> not, so I
> defer to someone who actually knows what they are talking about
> to make
> a judgment call ;-).
I don't have a G45, but if this driver verifiably works for you
(and the regular version does not) I think it's good to to include
it. Also because I expect this card to be overrepresented amongst
Guix users: there aren't that many common Librebootable machines.
It needs its own clear synopsis, description, and home page
though. Is there a home page? I'm not good at navigating
BitBucket.
> This variant of intel-vaapi-driver is a backport of the ancient
> g45-h264
> branch that used to be maintained by the intel-vaapi-driver
> team. As far
> as I know, the reason they don't maintain this branch anymore is
> that
> hardware accelerated h264 decoding on the G45 chipset was much
> too slow
> for 1080p video, as by default it only had 32MB of VRAM to work
> with.
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.
I'm guessing that your card identifies as an Intel® GMA X4500MHD.
Is that correct? We should include the marketing name in the
synopsis & description too, even if it might not map 1:1 to the
chipset.
> This variant of intel-vaapi-driver is a backport of the ancient
> g45-h264
> branch that used to be maintained by the intel-vaapi-driver
> team. As far
> as I know, the reason they don't maintain this branch anymore is
> that
> hardware accelerated h264 decoding on the G45 chipset was much
> too slow
> for 1080p video, as by default it only had 32MB of VRAM to work
> with.
This is good! :-) It should be slightly edited and used as a
description together with the original intel-vaapi-driver text.
Apart from that, the package LGTM. Thanks!
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-11-27 18:59 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 [this message]
2019-11-29 11:00 ` Jelle Licht
2020-04-15 22:32 ` Tobias Geerinckx-Rice via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zj59mes.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=38403@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.