From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically
Date: Tue, 20 Feb 2018 12:56:22 +0000 [thread overview]
Message-ID: <bug-105145-502-J9LeMrXF9y@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105145-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105145
Christian König <ckoenig.leichtzumerken@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |enhancement
Status|RESOLVED |VERIFIED
--- Comment #6 from Christian König <ckoenig.leichtzumerken@gmail.com> ---
(In reply to k.philipp from comment #5)
> There are some surface hints, but I'm not sure if they fit this use case.
Setting the DISPLAY hint can be used with KMS to display the result without
copying it, so that is not what we are searching for.
But checking the documentation once more VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ
actually sounds exactly like what we need.
E.g. we switch over to allocate all surfaces in the progressive/frame format
and only use the interlaced/field format when
VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ is given.
Now you just need to find somebody volunteering to implement that :)
I can assist finding the proper places in the code, but I don't have time to do
it myself.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3075 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-20 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 12:47 [Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically bugzilla-daemon
2018-02-17 13:48 ` bugzilla-daemon
2018-02-18 8:31 ` bugzilla-daemon
2018-02-19 7:49 ` bugzilla-daemon
2018-02-20 11:55 ` bugzilla-daemon
2018-02-20 12:56 ` bugzilla-daemon [this message]
2018-02-20 12:56 ` bugzilla-daemon
2018-02-20 13:51 ` bugzilla-daemon
2018-02-20 14:23 ` bugzilla-daemon
2018-03-07 7:43 ` bugzilla-daemon
2018-04-14 10:14 ` bugzilla-daemon
2018-06-11 12:58 ` bugzilla-daemon
2018-06-11 13:09 ` bugzilla-daemon
2018-06-13 11:15 ` bugzilla-daemon
2019-02-03 12:41 ` bugzilla-daemon
2019-09-25 18:02 ` bugzilla-daemon
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=bug-105145-502-J9LeMrXF9y@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox