From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98005] VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface
Date: Fri, 25 Nov 2016 21:15:08 +0000 [thread overview]
Message-ID: <bug-98005-502-Kwz4tOWp00@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98005-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 744 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98005
--- Comment #27 from Boyuan Zhang <boyuan.zhang@amd.com> ---
(In reply to Andy Furniss from comment #26)
> So far the patches seem good :-)
>
> cbr and vbr are behaving as expected - including md5sums always being the
> same.
Sounds cool! =)
Sorry for taking a long time to fully solve these issues. The two/three
reported issues are caused by 2 root causes, however these 2 root causes can
actually affect each other in certain way. Thanks for catching all these
issues.
I will let you run more tests a bit. If everything seems fine, I will push the
patches to upstream.
Regards,
Boyuan
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1723 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:[~2016-11-25 21:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 15:06 [Bug 98005] VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface bugzilla-daemon
2016-10-03 22:16 ` bugzilla-daemon
2016-10-17 20:20 ` bugzilla-daemon
2016-10-17 23:59 ` bugzilla-daemon
2016-10-18 17:58 ` bugzilla-daemon
2016-10-18 20:25 ` bugzilla-daemon
2016-11-10 22:57 ` bugzilla-daemon
2016-11-10 23:35 ` bugzilla-daemon
2016-11-11 16:31 ` bugzilla-daemon
2016-11-11 21:40 ` bugzilla-daemon
2016-11-11 21:51 ` bugzilla-daemon
2016-11-13 0:03 ` bugzilla-daemon
2016-11-13 0:04 ` bugzilla-daemon
2016-11-18 21:17 ` bugzilla-daemon
2016-11-19 0:37 ` bugzilla-daemon
2016-11-20 14:01 ` bugzilla-daemon
2016-11-20 14:03 ` bugzilla-daemon
2016-11-20 23:25 ` bugzilla-daemon
2016-11-21 19:54 ` bugzilla-daemon
2016-11-21 22:01 ` bugzilla-daemon
2016-11-21 22:51 ` bugzilla-daemon
2016-11-22 0:29 ` bugzilla-daemon
2016-11-22 0:51 ` bugzilla-daemon
2016-11-22 1:03 ` bugzilla-daemon
2016-11-24 19:53 ` bugzilla-daemon
2016-11-24 22:04 ` bugzilla-daemon
2016-11-25 0:53 ` bugzilla-daemon
2016-11-25 21:15 ` bugzilla-daemon [this message]
2016-11-26 19:45 ` bugzilla-daemon
2016-11-26 21:59 ` bugzilla-daemon
2016-11-26 23:23 ` bugzilla-daemon
2016-11-27 0:53 ` bugzilla-daemon
2016-11-28 22:34 ` bugzilla-daemon
2016-11-28 23:47 ` bugzilla-daemon
2016-11-29 20:02 ` bugzilla-daemon
2016-11-30 19:35 ` bugzilla-daemon
2016-11-30 20:53 ` bugzilla-daemon
2016-12-06 0:25 ` bugzilla-daemon
2016-12-06 15:23 ` bugzilla-daemon
2016-12-08 11:54 ` 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-98005-502-Kwz4tOWp00@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;
as well as URLs for NNTP newsgroup(s).