From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: add intel gallium driver support
Date: Thu, 31 Mar 2016 07:28:44 -0300 [thread overview]
Message-ID: <56FCFBDC.8010903@zacarias.com.ar> (raw)
In-Reply-To: <20160331040040.0083ba81@free-electrons.com>
On 30/03/16 23:00, Thomas Petazzoni wrote:
> "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
Hi Thomas.
The gallium intel driver wasn't cutting it like Bernd said so i
tried/investigated the DRI route and it worked out.
So yes, even though it might be academically interesting to have the
option to build the intel gallium driver it's pretty much useless so no
argument from me since i got what was really interesting from the other
patchset.
Regards.
prev parent reply other threads:[~2016-03-31 10:28 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
2016-03-31 10:28 ` Gustavo Zacarias [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=56FCFBDC.8010903@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