From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: add intel gallium driver support
Date: Thu, 31 Mar 2016 04:00:40 +0200 [thread overview]
Message-ID: <20160331040040.0083ba81@free-electrons.com> (raw)
In-Reply-To: <56E2A91A.1030509@zacarias.com.ar>
Hello,
On Fri, 11 Mar 2016 08:16:42 -0300, Gustavo Zacarias wrote:
> 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.
"DRI drivers need X.org" ? This seems wrong, since you precisely sent a
patch recently to all DRI drivers to be built without X.org.
So I guess this specific patch, allowing to build the unmaintained
Intel Gallium driver is no longer needed?
I've marked it as Rejected on patchwork for now. Let me know if you
disagree for some reason.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-31 2:00 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
2016-03-11 14:19 ` Peter Korsgaard
2016-03-11 14:23 ` Gustavo Zacarias
2016-03-31 2:00 ` Thomas Petazzoni [this message]
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=20160331040040.0083ba81@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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