From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
Subject: Re: [RFC PATCH 2/2] sna: Support running nested in Mir
Date: Mon, 22 Jul 2013 08:20:49 +0010
Message-ID: <51ece914.4688440a.5f0d.77db@mx.google.com>
References: <1374475480-7255-1-git-send-email-christopher.halse.rogers@canonical.com>
	<1374475480-7255-2-git-send-email-christopher.halse.rogers@canonical.com>
	<20130722075306.GA16732@cantiga.alporthouse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com
	[209.85.160.48])
	by gabe.freedesktop.org (Postfix) with ESMTP id 389D5E5CFE
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 22 Jul 2013 01:11:02 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so6708180pbc.7
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 22 Jul 2013 01:11:01 -0700 (PDT)
In-Reply-To: <20130722075306.GA16732@cantiga.alporthouse.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Mon, 22 Jul, 2013 at 5:53 PM, Chris Wilson 
<chris@chris-wilson.co.uk> wrote:
> With xorgMir this is not going to fly. Make sure the compatibility
> cruft, first of all, exists and is out of line in a header.
> 

Do you mean remove the various #ifdef XMIR bits, or *all* the bits 
gated on xorgMir? Some of that's not going to be trivial to hide away 
in a header.

>  And expose the driving heartbeat of when to refresh the screen 
> pixmap from Xmir.
> 
I'm not sure what you mean here - Xmir exposes the on-buffer-available 
callback, which gets triggered when swap_buffers has returned the next 
buffer to render to. This is what I'd think of as the refresh 
heartbeat. Is this not what you mean?

If you're rendering as fast as possible, this will be a 
once-per-compositor-vblank event.