<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - DRM backend does not search for i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94476#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - DRM backend does not search for i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94476">bug 94476</a>
from <span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span></b>
<pre>(In reply to gobogowoli from <a href="show_bug.cgi?id=94476#c6">comment #6</a>)
<span class="quote">> In the context of the mesa package, USE="bindist" means "Disable
> patent-encumbered ARB_texture_float, EXT_texture_shared_exponent, and
> EXT_packed_float extensions."[1] I had automatically assumed it meant
> proprietary code would be **enabled**, so that was my mistake. So bindist
> was disabled, which enabled proprietary code, which caused the drivers to
> end up in /usr/lib64/mesa instead of /usr/lib64/dri. Do I need any of those
> proprietary functions/drivers (does Intel even provide any proprietary
> drivers?), or should I set USE="-bindist"?</span >
For all I know, saying "bindist" affects installation location is totally
incorrect.
It's also not proprietary code. It is all FOSS code, but some algorithms are
patented in some countries, and in some countries those patents might even be
valid, so if you were not building Mesa only for yourself, you might maybe
perhaps one day get into trouble if you have enough money to be stolen.
Whatever, I don't really understand the legal matters, but I believe it depends
on your country a lot.
I repeat: it is not proprietary. Patent-encumbered is a different thing.
Whether you have "bindist" or not makes no difference to Weston. If you have
"bindist" and see some applications not working, then you could consider
disabling it. It only affects some GL extensions whether they work or not.
Weston uses none of that.
"bindist" is a short for "it is safe to redistribute the binaries built from
this package in all countries".
<span class="quote">> "eselect opengl" is and was set to xorg-x11 (the only option available).
>
> As you suggested, I added VIDEO_CARDS="intel i965" and reinstalled mesa.
> After symlinking /usr/lib64/dri/i965_dri.so to the real file in
> /usr/lib64/mesa, I started Weston, and it worked properly without the
> slowness. So, confusing as it sounds, i965_dri.so is the correct driver even
> when the kernel driver is i915, as you said.</span >
No, you should not need to do any symlinking manually. 'eselect' should do all
that, and reinstalling Mesa should trigger it automatically.
<span class="quote">> Finally, my keyboard works under Weston, but do you think it would benefit
> other users if I report that bug anyway?</span >
weston-keyboard is an on-screen keyboard program intended primarily for
touchscreens when you don't have a real keyboard.
If it's really missing, it's an issue in the Gentoo packaging or the Weston USE
flags you used.
<span class="quote">> Thanks everyone for the help! Weston appears to be working for me now.</span >
Cool, no worries.
<span class="quote">> [1] <a href="https://packages.gentoo.org/packages/media-libs/mesa">https://packages.gentoo.org/packages/media-libs/mesa</a></span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>