They're not maintained and gets in the way when loading EGL drivers.
The doc string even says it's disabled by default.
---
I think it makes sense to disable the intel gallium drivers as they're not
maintained and not in use anywhere. If nothing else, they're certainly
experimental, and as such it makes sense to require an opt-in before
compiling them.
Jakob didn't like the wholesale disabling of gallium for intel, but preferred
a per-state tracker option (to disable gallium egl from loading intel
gallium drivers, for example). I just don't think it makes sense to build
the gallium intel drivers by default if they're not supposed to be
used anywhere.
Kristian
configure.ac | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 46d3516..4a3f06e 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1705,7 +1705,7 @@ AC_ARG_ENABLE([gallium-i915],
[AS_HELP_STRING([--enable-gallium-i915],
[build gallium i915 @<:@default=disabled@:>@])],
[enable_gallium_i915="$enableval"],
- [enable_gallium_i915=auto])
+ [enable_gallium_i915=no])
if test "x$enable_gallium_i915" = xyes; then
GALLIUM_WINSYS_DIRS="$GALLIUM_WINSYS_DIRS i915/sw"
GALLIUM_DRIVERS_DIRS="$GALLIUM_DRIVERS_DIRS i915"
@@ -1722,7 +1722,7 @@ AC_ARG_ENABLE([gallium-i965],
[AS_HELP_STRING([--enable-gallium-i965],
[build gallium i965 @<:@default=disabled@:>@])],
[enable_gallium_i965="$enableval"],
- [enable_gallium_i965=auto])
+ [enable_gallium_i965=no])
if test "x$enable_gallium_i965" = xyes; then
GALLIUM_DRIVERS_DIRS="$GALLIUM_DRIVERS_DIRS i965"
gallium_check_st "i965/drm" "dri-i965" "xorg-i965"
--
1.7.4
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
