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 93866] Tonga: Weston-drm direct scan out corruption
Date: Mon, 25 Jan 2016 23:00:14 +0000	[thread overview]
Message-ID: <bug-93866-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 93866
           Summary: Tonga: Weston-drm direct scan out corruption
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 121287
  --> https://bugs.freedesktop.org/attachment.cgi?id=121287&action=edit
external picture showing corruption

Testing both release and git wayland/weston on R9285.

Using weston-launch from fbcon so it uses weston-drm.

Apart from https://bugs.freedesktop.org/show_bug.cgi?id=93740 which can be
worked around, rendering is good when compositing.

If I run something that allows weston to enable direct scanout there is slight
corruption. kodi and mpv are the only ways I know to do this.

If I do something that changes back yo compositing the corruption goes, taking
a screen shot/recording or zooming in will all "fix" the corruption.

I am inferring direct scan out is happening as I can't change transparency +
the man page for weston-drm says it will be used where possible.

Tried going back in time with mesa to see if it ever worked, but I started
hitting places where either weston wouldn't start or I always got compositing
so no corruption but I could change transparency.

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

[-- Attachment #1.2: Type: text/html, Size: 3130 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-01-25 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 23:00 bugzilla-daemon [this message]
2016-01-25 23:01 ` [Bug 93866] Tonga: Weston-drm direct scan out corruption bugzilla-daemon
2017-11-02 17:52 ` 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-93866-502@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