From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: add intel gallium driver support
Date: Fri, 11 Mar 2016 08:47:07 -0300 [thread overview]
Message-ID: <56E2B03B.9000701@zacarias.com.ar> (raw)
In-Reply-To: <87wpp9i6se.fsf@dell.be.48ers.dk>
On 11/03/16 08:38, Peter Korsgaard wrote:
> I actually think the comment is wrong. Googling around for wayland /
> mesa / intel seems to show a bunch of references to people using dri
> drivers and not gallium:
>
> https://wayland.freedesktop.org/building.html
> https://lists.freedesktop.org/archives/wayland-devel/2011-February/000702.html
> https://lists.freedesktop.org/archives/wayland-devel/2012-August/004832.html
> https://gist.github.com/tmpvar/6218568
Many people use xwayland hence care (or don't, depending on perspective)
about lingering x11 stuff around.
The end reason is libgtk3 with the wayland and/or broadway backend,
newer gtk3 versions require some form of *GL support provided by the
libepoxy wrapper.
libepoxy in turn needs a real GLX and/or EGL provider, GLX is a
no-brainer, it requires X11. EGL on the other hand does not.
With some patching (sent) libepoxy can be built X11-less to only handle
EGL, after all who wants a gtk3 with wayland carrying x11 luggage? (when
building libgtk3 with only the wayland and/or broadway backends)
Now, since newer libgtk3 versions mandate some form of GL support, which
is wrapped by libepoxy and provided by mesa, doesn't it make sense that
said GL support is accelerated?
Regards.
next prev parent reply other threads:[~2016-03-11 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 18:01 [Buildroot] [PATCH] mesa3d: add intel gallium driver support Gustavo Zacarias
2016-03-10 19:59 ` Peter Korsgaard
2016-03-10 20:08 ` Gustavo Zacarias
2016-03-10 21:58 ` Bernd Kuhls
2016-03-11 11:09 ` Peter Korsgaard
2016-03-11 11:16 ` Gustavo Zacarias
2016-03-11 11:38 ` Peter Korsgaard
2016-03-11 11:47 ` Gustavo Zacarias [this message]
2016-03-11 14:19 ` Peter Korsgaard
2016-03-11 14:23 ` Gustavo Zacarias
2016-03-31 2:00 ` Thomas Petazzoni
2016-03-31 10:28 ` Gustavo Zacarias
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=56E2B03B.9000701@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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