GNU bug report logs - #36814
[PATCH 0/2] Add VA-API Intel back-end and utilities

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Subject: bug#36814: closed (Re: [bug#36814] [PATCH 0/2] Add VA-API Intel
 back-end and utilities)
Date: Sat, 27 Jul 2019 21:30:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#36814: [PATCH 0/2] Add VA-API Intel back-end and utilities

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 36814 <at> debbugs.gnu.org.

-- 
36814: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36814
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 36814-done <at> debbugs.gnu.org
Subject: Re: [bug#36814] [PATCH 0/2] Add VA-API Intel back-end and utilities
Date: Sat, 27 Jul 2019 23:29:35 +0200

[Message part 3 (text/plain, inline)]

Tobias Geerinckx-Rice via Guix-patches 写道：
> Guix,
>
> The following patches add the VA-API back end for Intel GEN 
> chips as
> well as libva-utils (which provides vainfo amongst many other 
> things).

Pushed atop master as 3563220e1e46b8a1b9af1e3a4c6cb3f9560c2460 &c.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Guix-patches <guix-patches <at> gnu.org>
Subject: [PATCH 0/2] Add VA-API Intel back-end and utilities
Date: Fri, 26 Jul 2019 05:27:36 +0200

[Message part 6 (text/plain, inline)]

Guix,

The following patches add the VA-API back end for Intel GEN chips 
as well as libva-utils (which provides vainfo amongst many other 
things).  I've tested them on my Ivy Bridge laptop and they work 
wonderfully.

However.

libva (I guess) searches for the back end in mesa's store output 
by default:

--8<---------------cut here---------------start------------->8---
vainfo 
libva info: VA-API version 1.4.1
libva info: va_getDriverName() returns 0
libva info: Trying to open 
/gnu/store/clhrbkacyrclwzkzdj2ql8y572whwjzi-mesa-19.1.1/lib/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
--8<---------------cut here---------------end--------------->8---

I don't know enough about libva or mesa to know how all this can 
be made to compose nicely.

I just tested and enjoyed VA-API acceleration by (icky icky boo 
boo) copying intel-vaapi-driver's library to the mesa store 
directory, so I need help in more ways than one.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.