qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Elie Tournier <tournier.elie@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.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: Tue, 30 Jan 2018 17:08:24 +0000	[thread overview]
Message-ID: <20180130170824.GA7376@Nikki.localdomain> (raw)
In-Reply-To: <20180130152233.kg2qpibe4zxrtytx@sirius.home.kraxel.org>

On Tue, Jan 30, 2018 at 04:22:33PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > 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 ...
> > I'm wondering how extensive this rewrite is going to be. Did you plan to modify the qemu interface?
> > If someone already start working on this task, can you send me the link to the repository?
> > I will be happy to help if needed.
> 
> https://www.kraxel.org/cgit/qemu/log/?h=sirius/display-cmdline
Awesome, thanks. I will definitely have a look to it.
> 
> > > 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.
> > I'm fine with this idea.
> > However, I think we still need to add a way to the user to choose the backend he want.
> 
> Changing gl from bool to multiple choice looks more useful to me then,
> i.e. have "gl={on,core,gles,off}", where "on" automatically picks "core"
> or "gles" depending on what is available.
I like that solution. ;). I will implement it on top of your work.
> 
> What is the status of the virglrenderer patches btw?
We keep upstreaming no invasive patches.
But with upstream virglrenderer, you will not be able to use a gles backend.
If you want to know more about the current status of the project, you can have a look to our repo [1].

Currently, we are working through bugs, cleaning up the remaing patches.
Our short term goal is to pass the GLES2 CTS [2] in the guest side.

Regards,
Elie

[1] https://gitlab.collabora.com/jakob/virglrenderer-gles/tree/hacks
[2] https://github.com/KhronosGroup/VK-GL-CTS
> 
> cheers,
>   Gerd
> 

      reply	other threads:[~2018-01-30 17:10 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
2018-01-30 14:43     ` Elie Tournier
2018-01-30 15:22       ` Gerd Hoffmann
2018-01-30 17:08         ` Elie Tournier [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=20180130170824.GA7376@Nikki.localdomain \
    --to=tournier.elie@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).