From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: add intel gallium driver support
Date: Thu, 10 Mar 2016 22:58:27 +0100 [thread overview]
Message-ID: <3979rcxl7o.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 56E1D44F.70807@zacarias.com.ar
Am Thu, 10 Mar 2016 17:08:47 -0300 schrieb Gustavo Zacarias:
> On 10/03/16 16:59, Peter Korsgaard wrote:
>
>> I don't know much about mesa, but I thought the Intel driver didn't use
>> galium? Is this some kind of alternative to the dri driver?
>
> You've got both, from mesa configure:
>
> --with-gallium-drivers[=DIRS...]
> comma delimited Gallium drivers list, e.g.
>
"i915,ilo,nouveau,r300,r600,radeonsi,freedreno,svga,swrast,vc4,virgl"
> [default=r300,r600,svga,swrast]
>
> Enabling it builds /usr/lib/dri/i915_dri.so besides others you may have
> selected (in my case kms_swrast_dri.so and swrast_dri.so).
> Otherwise we can ask Bernd, but i get that additional driver with this
> option, and it's documented.
> Regards.
Hi,
I am using the DRI driver for my Kodi system and never tried the Gallium
one because my personal Kodi package follows the OpenElec development,
and they use DRI, too ;)
https://github.com/OpenELEC/OpenELEC.tv/blob/master/config/graphic#L26
Some quotes I found during a quick research:
http://www.mesa3d.org/relnotes/8.0.html (February 9, 2012)
"Removed the dead Gallium i965, cell and failover drivers, which were
either broken and with nobody in sight to fix the situation or
deprecated."
https://blogs.igalia.com/itoral/2014/08/08/diving-into-mesa/
"Although there were some efforts to port the Intel driver to Gallium in
the past, development of the Intel Gallium drivers (i915g and i965g) is
stalled now as far as I know. Intel is focusing in the classic version of
the drivers instead."
These days Intel is busy in coding a Vulkan driver for mesa3d:
https://cgit.freedesktop.org/mesa/mesa/tree/README.intel-vulkan.txt?
h=vulkan
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 ;)
Regards, Bernd
next prev parent reply other threads:[~2016-03-10 21:58 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 [this message]
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
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=3979rcxl7o.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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