From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103408] [bisected] frames dropped during video replay due to "add hardware_planes_only to list of affected planes"
Date: Thu, 26 Oct 2017 14:04:26 +0000 [thread overview]
Message-ID: <bug-103408-502-G9Zg6QBXqw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103408-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103408
--- Comment #4 from shirish.s@amd.com ---
I have tested the bisected patch:
drm/amd/display: add hardware_planes_only to list of affected planes
in ChromeOS on Stoney platform and did not find any regression during rendering
or video p/b, also may be the reason why Andy Furniss did not see the issue on
composited full screen.
I have attached a patch in anticipation to the description of bug, please try
it and let me know if it works.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1478 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:[~2017-10-26 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 23:22 [Bug 103408] [bisected] frames dropped during video replay due to "add hardware_planes_only to list of affected planes" bugzilla-daemon
2017-10-23 23:18 ` bugzilla-daemon
2017-10-25 18:56 ` bugzilla-daemon
2017-10-26 14:00 ` bugzilla-daemon
2017-10-26 14:04 ` bugzilla-daemon [this message]
2017-10-26 20:51 ` bugzilla-daemon
2017-10-26 21:45 ` bugzilla-daemon
2017-10-27 3:28 ` 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-103408-502-G9Zg6QBXqw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.