unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Vincent Legoll <vincent.legoll@gmail.com>, 38403@debbugs.gnu.org
Subject: [bug#38403] [PATCH] gnu: Add intel-vaapi-driver-g45-h264.
Date: Sat, 12 Sep 2020 13:20:23 +0200	[thread overview]
Message-ID: <87pn6rkzrc.fsf@jlicht.xyz> (raw)
In-Reply-To: <7e6c8e91-39b9-b640-c1e3-03dcb42fe738@gmail.com>



Vincent Legoll <vincent.legoll@gmail.com> writes:

> On 13/04/2020 22:01, Jelle Licht wrote:
>> I have it on my agenda for early May to backport the latest
>> intel-vaapi-driver changes to the g45-h264 branch and subsequently push
>> it to Guix.
>
> Just ping me when needed

Some changes made in linux kernel 5.X made it harder to get this to work
reliably. Since getting this to work allows me to watch videos on my
laptop without melting my pants off, I'm still very much motivated to
get it to work in the long run ;-).

I been made aware that the 5.x series of kernels have seen a lot of
regressions (and improvements, probably) for intel-drm related code
paths; my hope is that this still somehow stabilizes in the coming
months.

For now, it seems to work on linux kernel 4.19.143. See [1] for the
maintainer of the AUR package that I based my work on.

Is there some way to 'park' this debbugs issue? As in, keep it open, but
rather as a reminder to revisit this issue in the future?

Thanks,
Jelle

[1] https://aur.archlinux.org/packages/libva-intel-driver-g45-h264




  reply	other threads:[~2020-09-12 11:21 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
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 [this message]
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=87pn6rkzrc.fsf@jlicht.xyz \
    --to=jlicht@fsfe.org \
    --cc=38403@debbugs.gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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).