From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
To: youling257 <youling257@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, seanpaul@chromium.org,
hersenxs.wu@amd.com, Harry.Wentland@amd.com,
Nicholas.Kazlauskas@amd.com, Ching-shih.Li@amd.com
Subject: Re: [PATCH v2] drm/amd/display: Fix two cursor duplication when using overlay
Date: Mon, 10 May 2021 20:37:01 -0400 [thread overview]
Message-ID: <20210511003701.eik36vjufjbfegcl@outlook.office365.com> (raw)
In-Reply-To: <20210510022047.9323-1-youling257@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 906 bytes --]
On 05/10, youling257 wrote:
> I using amd 3400g running with android-x86, this patch is a bad commit when i use android-x86 on amdgpu.
>
> Revert "Revert "drm/amdgpu: Ensure that the modifier requested is supported by plane."" is the first bad commit, cause a androidx86 run on amdgpu problem, look the video, https://drive.google.com/file/d/1QklH_H2AlOTu8W1D3yl6_3rtZ7IqbjR_/view?usp=sharing
>
> "drm/amd/display: Fix two cursor duplication when using overlay" is the second bad commit, also cause this problem, https://drive.google.com/file/d/1QklH_H2AlOTu8W1D3yl6_3rtZ7IqbjR_/view?usp=sharing
Hmmm... I don't think that the two cursor patch would cause that
flickering. Are you using the latest amd-staging-drm-next? Do you have
this patch in your local branch:
drm/amd/display: Reject non-zero src_y and src_x for video planes
Thanks
--
Rodrigo Siqueira
https://siqueira.tech
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-05-11 0:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 0:06 [PATCH v2] drm/amd/display: Fix two cursor duplication when using overlay Rodrigo Siqueira
2021-04-14 13:29 ` Harry Wentland
2021-05-10 2:20 ` youling257
2021-05-11 0:37 ` Rodrigo Siqueira [this message]
2021-05-11 1:47 ` youling 257
2021-08-18 10:48 ` Simon Ser
2021-08-18 13:18 ` Rodrigo Siqueira
2021-08-24 13:59 ` Simon Ser
2021-08-24 14:56 ` Kazlauskas, Nicholas
2021-08-24 16:48 ` Harry Wentland
2021-08-27 13:53 ` Simon Ser
2021-08-27 14:04 ` Harry Wentland
2021-08-27 14:12 ` Simon Ser
2021-08-27 13:47 ` Simon Ser
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=20210511003701.eik36vjufjbfegcl@outlook.office365.com \
--to=rodrigo.siqueira@amd.com \
--cc=Ching-shih.Li@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=hersenxs.wu@amd.com \
--cc=seanpaul@chromium.org \
--cc=youling257@gmail.com \
/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).