From: Brian Paul <brian.paul@tungstengraphics.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Xserver development <xorg@freedesktop.org>,
DRI-EGL <dri-egl@lists.freedesktop.org>
Subject: Re: EGL_MESA_screen_surface proposal
Date: Wed, 16 Mar 2005 08:04:38 -0700 [thread overview]
Message-ID: <42384B06.1010901@tungstengraphics.com> (raw)
In-Reply-To: <9e47339105031520304154e567@mail.gmail.com>
Jon Smirl wrote:
> On Tue, 15 Mar 2005 11:36:53 -0500, Michel Danzer <mdanzer@ati.com> wrote:
>
>>On Tue, 2005-03-15 at 11:28 -0500, Jon Smirl wrote:
>>
>>>On Tue, 15 Mar 2005 08:17:13 -0700, Brian Paul
>>><brian.paul@tungstengraphics.com> wrote:
>>>
>>>>Perhaps the eglShowSurface() and eglScreenMode() functions should be
>>>>combined so the new surface and new display mode can be validated
>>>>together. That way, the undefined state between setting the new
>>>>surface and new mode can be avoided.
>>
>>Makes sense to me.
>
>
> What if I just want to show another surface without changing the mode?
> I could still use a combined version and since the mode matches the
> mode won't actually get changed?
Right. The combined function can just as well be used to change the
screen's current mode _or_ current surface. You don't have to change
both.
-Brian
prev parent reply other threads:[~2005-03-16 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4236F0A8.4000004@tungstengraphics.com>
[not found] ` <9e47339105031507064a68630f@mail.gmail.com>
[not found] ` <4236FC79.5000909@tungstengraphics.com>
2005-03-15 16:28 ` EGL_MESA_screen_surface proposal Jon Smirl
2005-03-15 16:36 ` Michel Danzer
2005-03-16 4:30 ` Jon Smirl
2005-03-16 4:44 ` Vladimir Dergachev
2005-03-16 15:04 ` Brian Paul [this message]
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=42384B06.1010901@tungstengraphics.com \
--to=brian.paul@tungstengraphics.com \
--cc=dri-egl@lists.freedesktop.org \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@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;
as well as URLs for NNTP newsgroup(s).