All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] gles2 on raspi3
Date: Sat, 15 Apr 2017 12:35:37 -0400	[thread overview]
Message-ID: <20170415163537.GA23175@linux-uys3> (raw)
In-Reply-To: <CALbNGRQy1Lf1=hV47Lf+u7rQUgubXjdiQWhjNJN4a3sDwr419A@mail.gmail.com>

On Sat 2017-04-15 @ 04:46:14 PM, Andreas Müller wrote:
> > Does anyone have any of these (or something else?) working?
> >
> Ehm userland gles2 on X11? I would not expect that to work. Experts
> correct me but userland acceleration works for fullscreen apps only.

I have made this work before (which, as you'll see later in this email,
doesn't imply that's how it's supposed to work!):
https://twoerner.blogspot.ca/2015/09/oe-build-of-glmark2-running-on.html

Oh, and I did try both with and without "--fullscreen".

> Why not using FOSS VC4+mesa?

Now's probably a good time to point out I only have a vague idea of what I'm
doing ;-)

I didn't try vc4 because the raspi recipes implied (to me) it was for aarch64
only. The "vc4graphics" MACHINE_FEATURES is only added for raspberrypi3-64.
I'll give this a try though.

Here's another question that only shows my inexperience in this area... does
using mesa always imply software-only rendering? mali (for example) would be
hardware rendering (though through a binary blob) and mesa is the software
fallback?

By the way, with my current setup I have been able to run openGL apps (e.g.
glmark2 by itself) albeit most definitely non-accelerated!

A lot of google searches talk about setting environment variables. Are there
any that might apply?

Best regards,
	Trevor


  reply	other threads:[~2017-04-15 16:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 13:39 [meta-raspberrypi] gles2 on raspi3 Trevor Woerner
2017-04-15 14:46 ` Andreas Müller
2017-04-15 16:35   ` Trevor Woerner [this message]
2017-04-15 18:09     ` Andreas Müller
2017-04-15 23:16       ` Trevor Woerner
2017-04-16 23:23         ` Andreas Müller
2017-04-17  0:30           ` Trevor Woerner
2017-04-17  0:49             ` Andreas Müller
2017-04-17  0:45           ` Trevor Woerner
2017-04-16 23:52         ` Andreas Müller
2017-04-17  0:27           ` Trevor Woerner
2017-04-17  1:11             ` Andreas Müller
2017-04-18  4:16               ` Changhyeok Bae
2017-04-16 22:54       ` Trevor Woerner
2017-04-20  3:41       ` ***SPAM*** " Herve Jourdain
2017-04-20  7:13         ` Trevor Woerner
2017-04-20 11:56           ` Herve Jourdain
2017-04-20 12:58             ` Andreas Müller
2017-04-20 16:55           ` Khem Raj
2017-04-21  3:19             ` Gary Thomas

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=20170415163537.GA23175@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=schnitzeltony@googlemail.com \
    --cc=yocto@yoctoproject.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.