Comment # 4
on bug 75453
from Emil Velikov
(In reply to comment #3)
> Ah, that's interesting. Actually, the "DRI driver" I meant was the
> 'i915_dri.so' file, which got created from these components:
>
Classic mesa can produce only DRI drivers, whereas gallium can do alot more -
dri, vdpau, xvmc, omx, opencl...
> - libdricommon.a
> - libmesagallium.a
> - libgallium.a
> - libdridrm.a
> - libi915drm.a
> - libwsw.a
> - libsoftpipe.a
> - libgalahad.a
> - libtrace.a
> - librbug.a
> - libi915.a
>
> The Makefile for this library is located in src/gallium/targets/dri-i915.
>
> But you're right, there also apppeared a 'mesa_dri_drivers.so' in the build
> log, which doesn't appear anymore with your four patches applied. I also
> remember having seen an 'i915_dri.so' file linked to 'mesa_dri_drivers.so'
> with another configuration.
>
Currently only classic dri drivers build into megadriver (mesa_dri_drivers.so)
> So, there appear to be two ways to get this 'i915_dri.so' file built and one
> of them is actually a Gallium driver? I'm confused now.
Same hardware, different drivers developed via different infrastructure by
different teams. Is it that confusing :P
Named in the same way so that people can simply make install, and things just
work(tm). If you're building both, then you need to keep an eye open to install
the one you want. Simples :-)
FWIW the build should be fine now, thanks for the report.
commit 4687b0a1a7280a7f19e349aa6b00ee1c0f634b21
Author: Emil Velikov <emil.l.velikov@gmail.com>
Date: Mon Feb 24 22:58:13 2014 +0000
configure: enable the drm pipe-loader for non swrast drivers
All hardware drivers including the virtual vmwgfx require
the drm pipe-loader in order to be properly loaded by xa,
gbm and opencl.
Note this does _not_ add support for the above three it only
allows the pipe driver to be loaded by the library.
Eg. GBM will now properly open the pipe-i915 driver, should
one be working on the such hardware.