All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: Chris Wilson
	<chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>,
	airlied-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: xorg-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] Fallback to std DRI2CopyRegion when DRI2UpdatePrime fails
Date: Mon, 06 Oct 2014 11:04:51 +0900	[thread overview]
Message-ID: <5431F8C3.2040000@daenzer.net> (raw)
In-Reply-To: <1412492791-4121-1-git-send-email-chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>

On 05.10.2014 16:06, Chris Wilson wrote:
> I was looking at a bug report today of intel/ati prime and noticed a
> number of sna_share_pixmap_backing() failures (called from
> DRI2UpdatePrime). These were failing as the request was for the scanout
> buffer (which is tiled and so we refuse to share it, and since it is
> already on the scanout we refuse to change tiling).
>
> But looking at radeon_dri2_copy_region2(), if DRI2UpdatePrime() fails,
> the copy is aborted and the update lost. If the copy is made to the
> normal window drawable is that enough for it to be propagated back
> through damage tracking?

Have you asked the reporter of that bug to test your patch?


-- 
Earthling Michel Dänzer            |                  http://www.amd.com
Libre software enthusiast          |                Mesa and X developer
_______________________________________________
xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

  parent reply	other threads:[~2014-10-06  2:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  7:06 [PATCH] Fallback to std DRI2CopyRegion when DRI2UpdatePrime fails Chris Wilson
     [not found] ` <1412492791-4121-1-git-send-email-chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
2014-10-06  2:04   ` Michel Dänzer [this message]
2014-10-06  6:39     ` Chris Wilson
     [not found]       ` <20141006063907.GB31284-aII6DKEyn0pWYbfKqPwjAkR8Iwp7RQ6xAL8bYrjMMd8@public.gmane.org>
2014-10-06  7:37         ` Mike Lothian

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=5431F8C3.2040000@daenzer.net \
    --to=michel-otuistvhuppr7s880joybq@public.gmane.org \
    --cc=airlied-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=xorg-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 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.