AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: KARBOWSKI Piotr <piotr.karbowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Harry Wentland <harry.wentland-5C7GfCeVMHo@public.gmane.org>,
	Tom St Denis <tstdenis-5C7GfCeVMHo@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Modesetting (amdgpudrmfb) artifacts on RAVEN APU
Date: Wed, 7 Mar 2018 20:54:48 +0100	[thread overview]
Message-ID: <4e05ffe5-477f-8764-9c87-30113ae0a7a7@gmail.com> (raw)
In-Reply-To: <c397a678-aa2d-275a-dd6d-5876a7a7dcc1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 2018-03-07 20:31, KARBOWSKI Piotr wrote:
> On 2018-03-07 20:12, Harry Wentland wrote:
>> Thanks for testing.
>>
>> What do you mean with broken video? I tried going back in the email 
>> thread but I'm not 100% clear what you mean by this.
>>
>> BTW, drm-fixes-4.16 are fixes we intend to get into the 4.16 upstream 
>> kernel. amd-staging-drm-next is our development tree and quite a bit 
>> farther ahead in development. I'm trying to find fixes to backmerge to 
>> 4.16 to make everyone happy when it releases.
> 
> Like on those screenshots
> 
> 
>      https://i.imgur.com/qnDOKY7.jpg
>      https://i.imgur.com/XH42zit.jpg
> 
> To describe it better, lets split the screen into 4 segments
> 
> +-----+-----+
> |  A  |  B  |
> +-----+-----+
> |  C  |  D  |
> +-----+-----+
> 
> The screen resolution kicks in as it should, 1080p, then A displays 
> proper part of screen, around 25%, then B contain a copy of what A 
> displays, so the same 25% of top-left part of screen, then C and D 
> remain black, if I scroll the screen a bit, C and D an get a bold 
> vertical line of whatever color was on screen, if I had a white/gray 
> font, it will be it, if there was some blue text, it will be blue until 
> I scroll a bit more.
> 
> 
> drm-fixes-4.16 yield the same effect as amd-staging-drm-next without 
> 0001-drm-amd-display-Fix-takeover-from-VGA-mode.patch, but it seems that 
> htis patch is already in drm-fixes-4.16 so I am confused.

I was not correct.

The drm-fixes-4.16 is a bit better It fixes half of my issue! So with 
this handy ascii art of mine

   +-----+-----+
   |  A  |  B  |
   +-----+-----+
   |  C  |  D  |
   +-----+-----+

A and C works, so I have full termianl on left side. but B remains copy 
of A and D either is black of have the fancy line.

I compared manually the patch that did worked for me and it seems it was 
not fully applied, the .h and .c does not look the same. Perhaps that's 
the source here.

-- Piotr.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-03-07 19:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 16:40 Modesetting (amdgpudrmfb) artifacts on RAVEN APU KARBOWSKI Piotr
     [not found] ` <58ac616f-a10a-3452-03c9-a85e6bd88626-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-06 11:18   ` Tom St Denis
     [not found]     ` <6919064d-1d4e-0497-b362-930385386817-5C7GfCeVMHo@public.gmane.org>
2018-03-06 16:13       ` Alex Deucher
     [not found]         ` <CADnq5_PHLLUqmZEnJwvpiYeJNRWT3VXnUGG63G-isLiAW0mjow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-03-06 16:54           ` Harry Wentland
2018-03-06 17:27       ` KARBOWSKI Piotr
     [not found]         ` <9a7a291e-389f-7489-4c12-2f5ca5414231-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-06 17:28           ` Tom St Denis
     [not found]             ` <06b14296-69ce-d9cc-65f2-3f177f16699a-5C7GfCeVMHo@public.gmane.org>
2018-03-06 17:38               ` KARBOWSKI Piotr
     [not found]                 ` <8f4384fe-afe3-08d0-595e-ab8b1c875bf9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-07 12:55                   ` Tom St Denis
     [not found]                     ` <631c113d-759a-46ef-bdc5-3440a73f65ec-5C7GfCeVMHo@public.gmane.org>
2018-03-07 14:55                       ` Harry Wentland
     [not found]                         ` <194c1d6d-b95d-94ec-32be-054c08fcdd95-5C7GfCeVMHo@public.gmane.org>
2018-03-07 16:14                           ` Harry Wentland
     [not found]                             ` <2aaf5555-06a0-02e0-7ea8-e5bfa20c7894-5C7GfCeVMHo@public.gmane.org>
2018-03-07 16:34                               ` Tom St Denis
2018-03-07 16:48                               ` KARBOWSKI Piotr
     [not found]                                 ` <4f02bd26-8fe9-fac4-f069-73e4b20fc375-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-07 17:38                                   ` KARBOWSKI Piotr
     [not found]                                     ` <9ea4725e-013e-8ea1-0e1a-72e0a4e0967d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-07 19:12                                       ` Harry Wentland
     [not found]                                         ` <5cbfa859-13f4-fc2a-54b7-a72ff641e5c8-5C7GfCeVMHo@public.gmane.org>
2018-03-07 19:16                                           ` Tom St Denis
     [not found]                                             ` <bf171213-db45-a4f0-1e76-2a411183c65d-5C7GfCeVMHo@public.gmane.org>
2018-03-07 19:37                                               ` Harry Wentland
2018-03-07 19:31                                           ` KARBOWSKI Piotr
     [not found]                                             ` <c397a678-aa2d-275a-dd6d-5876a7a7dcc1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-07 19:54                                               ` KARBOWSKI Piotr [this message]
     [not found]                                                 ` <4e05ffe5-477f-8764-9c87-30113ae0a7a7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-07 21:15                                                   ` Harry Wentland
     [not found]                                                     ` <d5cd41f1-07d6-0e6f-ce8e-b03b4c72f145-5C7GfCeVMHo@public.gmane.org>
2018-03-07 21:23                                                       ` KARBOWSKI Piotr

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=4e05ffe5-477f-8764-9c87-30113ae0a7a7@gmail.com \
    --to=piotr.karbowski-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=harry.wentland-5C7GfCeVMHo@public.gmane.org \
    --cc=tstdenis-5C7GfCeVMHo@public.gmane.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