qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Elie Tournier <tournier.elie@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC 0/2] Use SDL to create an OpenGL ES context for virglrenderer.
Date: Mon, 29 Jan 2018 19:08:30 +0100	[thread overview]
Message-ID: <20180129180830.tinzwowiarfolyfr@sirius.home.kraxel.org> (raw)
In-Reply-To: <20180129161155.GA25994@Nikki.localdomain>

  Hi,

> > In order to use this feature, we need to create a gles context.
> > This series add an option (`-display sdl,gles=on`) in the SDL display to create that context.
> 
> Humble ping.
> I didn't get any comment on this series.

Well, display configuration is going to be rewritten, and while that is
in flight adding new config options isn't a good idea b/c things will
conflict ...

Beside that:  Is a new config option actually needed in the first place?

Ideally qemu (or sdl) would figure on its own that a full core context
isn't available and try fallback to gles then.

cheers,
  Gerd

  reply	other threads:[~2018-01-29 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 14:50 [Qemu-devel] [RFC 0/2] Use SDL to create an OpenGL ES context for virglrenderer Elie Tournier
2018-01-17 14:50 ` [Qemu-devel] [RFC 1/2] sdl2: Add gles options Elie Tournier
2018-01-17 14:50 ` [Qemu-devel] [RFC 2/2] sdl2: gles option will create a gles context Elie Tournier
2018-01-17 15:04 ` [Qemu-devel] [RFC 0/2] Use SDL to create an OpenGL ES context for virglrenderer no-reply
2018-01-29 16:11 ` Elie Tournier
2018-01-29 18:08   ` Gerd Hoffmann [this message]
2018-01-30 14:43     ` Elie Tournier
2018-01-30 15:22       ` Gerd Hoffmann
2018-01-30 17:08         ` Elie Tournier

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=20180129180830.tinzwowiarfolyfr@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tournier.elie@gmail.com \
    /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).