From: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC PATCH 2/2] sna: Support running nested in Mir
Date: Mon, 22 Jul 2013 08:20:49 +0010 [thread overview]
Message-ID: <51ece914.4688440a.5f0d.77db@mx.google.com> (raw)
In-Reply-To: <20130722075306.GA16732@cantiga.alporthouse.com>
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.
next prev parent reply other threads:[~2013-07-22 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:44 [PATCH 1/2] sna: Call EnterVT from sna_screen_init christopher.halse.rogers
2013-07-22 6:44 ` [RFC PATCH 2/2] sna: Support running nested in Mir christopher.halse.rogers
2013-07-22 7:53 ` Chris Wilson
2013-07-22 8:10 ` Christopher James Halse Rogers [this message]
2013-07-22 8:33 ` Chris Wilson
2013-07-22 8:41 ` Chris Wilson
2013-07-22 9:27 ` Christopher James Halse Rogers
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=51ece914.4688440a.5f0d.77db@mx.google.com \
--to=christopher.halse.rogers@canonical.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 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.