dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98604] [VDPAU, DRI3] Fullscreen flash video fails when hardware acceleration is enabled.
Date: Sun, 06 Nov 2016 20:26:16 +0000	[thread overview]
Message-ID: <bug-98604-502-qtqhPsg3bK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98604-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 782 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98604

--- Comment #5 from Chris Rankin <rankincj@googlemail.com> ---
(In reply to smoki from comment #4)
> In couple months 11.2.x seems will cease to be supported anymore, so this
> might be time fixable... well in case they did not decide to enable VDPAU
> again :)

I don't see your point here. AFAIK the Flash plugin knows nothing about either
DRI2 or DRI3, and it works fine with DRI2. So why shouldn't it work with DRI3
too? Especially since Broadwell + DRI3 is unaffected.

To my mind, the Flash plugin has probably revealed a bug in Gallium's DRI3
layer. In which case, hoping that Adobe will "shoot the messenger" soon is just
silly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1717 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

  parent reply	other threads:[~2016-11-06 20:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 21:03 [Bug 98604] [VDPAU, radeonsi] Fullscreen flash video fails when hardware acceleration is enabled bugzilla-daemon
2016-11-05 21:03 ` bugzilla-daemon
2016-11-05 23:08 ` bugzilla-daemon
2016-11-06 13:13 ` [Bug 98604] [VDPAU, DRI3] " bugzilla-daemon
2016-11-06 17:27 ` bugzilla-daemon
2016-11-06 20:01 ` bugzilla-daemon
2016-11-06 20:15 ` bugzilla-daemon
2016-11-06 20:26 ` bugzilla-daemon [this message]
2016-11-06 21:48 ` bugzilla-daemon
2016-11-07  4:09 ` bugzilla-daemon
2017-01-03 22:47 ` bugzilla-daemon
2017-01-03 22:54 ` bugzilla-daemon
2017-01-03 23:04 ` bugzilla-daemon
2017-01-05  1:13 ` bugzilla-daemon
2017-01-13  4:44 ` bugzilla-daemon
2017-01-18  7:58 ` bugzilla-daemon
2017-03-20 12:02 ` bugzilla-daemon
2017-04-13 15:49 ` bugzilla-daemon
2017-04-14  1:30 ` bugzilla-daemon
2017-04-14  7:33 ` bugzilla-daemon
2017-06-01 15:55 ` bugzilla-daemon
2017-06-01 15:58 ` bugzilla-daemon
2019-09-25 17:55 ` 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-98604-502-qtqhPsg3bK@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