From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: add intel gallium driver support
Date: Fri, 11 Mar 2016 12:38:09 +0100 [thread overview]
Message-ID: <87wpp9i6se.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56E2A91A.1030509@zacarias.com.ar> (Gustavo Zacarias's message of "Fri, 11 Mar 2016 08:16:42 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> On 11/03/16 08:09, Peter Korsgaard wrote:
>> Hi,
>>
>> > To sum up: Yes, it is possible to build a i915 gallium driver in mesa3d,
>> > but who needs it? That's the reason I never implemented a Config.in
>> > option for it, but it will not hurt having one ;)
>>
>> Ok, that was more of less also my understanding. Gustavoz, what do you
>> need the gallium driver for?
> "DRI drivers need X.org" -> wayland, plus libgtk3 with it as backend.
> All that libepoxy effort would go to /dev/null otherwise.
> Regards.
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
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-03-11 11:38 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 [this message]
2016-03-11 11:47 ` Gustavo Zacarias
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=87wpp9i6se.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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