From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75453] New: i915/DRM Gallium driver apparently not usable without DRM pipe loader
Date: Mon, 24 Feb 2014 16:25:38 +0000 [thread overview]
Message-ID: <bug-75453-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3014 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75453
Priority: medium
Bug ID: 75453
Assignee: dri-devel@lists.freedesktop.org
Summary: i915/DRM Gallium driver apparently not usable without
DRM pipe loader
Severity: normal
Classification: Unclassified
OS: All
Reporter: christian.prochaska@genode-labs.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/i915g
Product: Mesa
(git master 73b46136b0ba20f7f84abdadad895111a4c37166)
I've built Mesa with the following configuration:
./autogen.sh --enable-gles2 --disable-glx --with-dri-drivers=
--enable-gallium-egl --with-egl-platforms=drm --with-gallium-drivers=i915
With this configuration, both a DRI driver and a Gallium driver get built,
despite the --with-dri-drivers= configure option (bug or intended?).
Then I've built the 'es2gears' demo as follows:
gcc -g -O0 -DMESA_EGL_NO_X11_HEADERS -o es2gears es2gears.c
../eglut/eglut_screen.c ../eglut/eglut.c -I../eglut -lGLESv2 -lEGL -lm
When I tried to run it on an IBM T60 notebook (Debian testing), at first bug
75335 triggered. Now that this bug has been resolved, the following error
occured:
-----
EGL_VERSION = 1.4 (DRI2)
EGLUT: failed to choose a config
-----
When I deleted the DRI driver, the following error occured:
-----
gbm: failed to open any driver (search paths /usr/local/lib/dri)failed to load
driver: i915
gbm: failed to open any driver (search paths /usr/local/lib/dri)failed to load
driver: i915
gbm: failed to open any driver (search paths /usr/local/lib/dri)failed to load
driver: i915
EGLUT: failed to initialize EGL display
-----
Apparently, the Gallium driver was not usable, too. Since bug 75335 got
triggered by the missing DRM pipe loader, I tried to enable it with the
following modification of configure.ac:
-----
index ba158e8..feb025f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1748,6 +1748,7 @@ if test "x$with_gallium_drivers" != x; then
xi915)
HAVE_GALLIUM_I915=yes
PKG_CHECK_MODULES([INTEL], [libdrm_intel >=
$LIBDRM_INTEL_REQUIRED])
+ gallium_require_drm_loader
GALLIUM_DRIVERS_DIRS="$GALLIUM_DRIVERS_DIRS i915 softpipe"
if test "x$MESA_LLVM" = x1; then
GALLIUM_DRIVERS_DIRS="$GALLIUM_DRIVERS_DIRS llvmpipe"
-----
With that, the demo finally worked:
-----
EGL_VERSION = 1.4 (Gallium)
Found 6 modes:
0: 1400 x 1050
1: 1400 x 1050
2: 1280 x 1024
3: 1024 x 768
4: 800 x 600
5: 640 x 480
Will use screen size: 1400 x 1050
vertex shader info:
fragment shader info:
info:
724 frames in 5.0 seconds = 144.713 FPS
-----
So it seems that the DRM pipe loader should get enabled by default for the
i915/DRM Gallium configuration, but I'm not sure if the modification I made
would break some other configuration.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4750 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-02-24 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 16:25 bugzilla-daemon [this message]
2014-02-24 19:06 ` [Bug 75453] i915/DRM Gallium driver apparently not usable without DRM pipe loader bugzilla-daemon
2014-02-24 19:22 ` bugzilla-daemon
2014-02-25 16:12 ` bugzilla-daemon
2014-02-28 23:08 ` bugzilla-daemon
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=bug-75453-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.