On Sat, 25 Sep 2010 10:05:10 -0400, Gaetan Nadon mems...@videotron.ca wrote:
The trusted location of the dri driver directory can be obtained
from the mesa dri.pc pkg-config file.
Merged.
5532687..c36ca7b master - master
--
keith.pack...@intel.com
pgph5UPG0G3q1.pgp
Description: PGP
On Fri, Sep 24, 2010 at 5:19 PM, Rémi Cardona r...@gentoo.org wrote:
Le 24/09/2010 15:56, Jon TURNEY a écrit :
On 23/09/2010 23:43, Keith Packard wrote:
What's the state of this patch? Seems like it should default to
whatever the old default was in the absence of a dri.pc file? Or is
Le 25/09/2010 06:38, Matt Turner a écrit :
On Fri, Sep 24, 2010 at 6:19 PM, Rémi Cardona r...@gentoo.org wrote:
I'll pipe in to add that this bit us (Gentoo) in the past as well.
For some unknown reason, DRI support was disabled in our packages for
HPPA and alpha. When swrast's build was
Le 26/09/2010 22:34, Dan Nicholson a écrit :
Hmm, I don't really get it. If you can't build a DRI-enabled Mesa, you
won't have dri.pc and your server won't have DRI support. What part is
painful?
Well that's what bit us: you need a DRI-enabled mesa even if you're only
building swrast.
So
On Sun, Sep 26, 2010 at 5:30 PM, Rémi Cardona r...@gentoo.org wrote:
Well that's what bit us: you need a DRI-enabled mesa even if you're only
building swrast.
So we've had to turn on DRI (even though it doesn't have any DRM
drivers) just to get swrast, whereas older versions of
Le 26/09/2010 23:39, Matt Turner a écrit :
On Sun, Sep 26, 2010 at 5:30 PM, Rémi Cardona r...@gentoo.org wrote:
Well that's what bit us: you need a DRI-enabled mesa even if you're only
building swrast.
So we've had to turn on DRI (even though it doesn't have any DRM
drivers) just to get
The trusted location of the dri driver directory can be obtained
from the mesa dri.pc pkg-config file.
Reviewed-by: Jon TURNEY jon.tur...@dronecode.org.uk
Acked-by: Matt Turner matts...@gmail.com
Reviewed-by: Dan Nicholson dbn.li...@gmail.com
Signed-off-by: Gaetan Nadon mems...@videotron.ca
---
On Thu, 2010-09-23 at 15:43 -0700, Keith Packard wrote:
What's the state of this patch? Seems like it should default to
whatever the old default was in the absence of a dri.pc file? Or is
everyone happy with the patch as-is?
The only use of the driver path is within a formatted string.
On 23/09/2010 23:43, Keith Packard wrote:
What's the state of this patch? Seems like it should default to
whatever the old default was in the absence of a dri.pc file? Or is
everyone happy with the patch as-is?
I am affected by this, as currently cygwin has no dri.pc file, as mesa can't
be
Le 24/09/2010 15:56, Jon TURNEY a écrit :
On 23/09/2010 23:43, Keith Packard wrote:
What's the state of this patch? Seems like it should default to
whatever the old default was in the absence of a dri.pc file? Or is
everyone happy with the patch as-is?
I am affected by this, as currently
On Fri, Sep 24, 2010 at 6:19 PM, Rémi Cardona r...@gentoo.org wrote:
I'll pipe in to add that this bit us (Gentoo) in the past as well.
For some unknown reason, DRI support was disabled in our packages for
HPPA and alpha. When swrast's build was moved from the server back into
mesa, the
What's the state of this patch? Seems like it should default to
whatever the old default was in the absence of a dri.pc file? Or is
everyone happy with the patch as-is?
--
keith.pack...@intel.com
pgp9bnR1sIuNK.pgp
Description: PGP signature
___
Just to be 100% complete here... This has the effect that DRI_DRIVER_PATH=
rather than ${libdir}/dri on systems without dri.pc
Is that situation ok? Should you check for existence of dri.pc first and set
it to the old fallback if not present?
On Sep 21, 2010, at 14:44, Gaetan Nadon wrote:
On Wed, Sep 22, 2010 at 9:16 AM, Jeremy Huddleston
jerem...@freedesktop.org wrote:
Just to be 100% complete here... This has the effect that DRI_DRIVER_PATH=
rather than ${libdir}/dri on systems without dri.pc
Is that situation ok? Should you check for existence of dri.pc first and set
it
On Wed, 2010-09-22 at 09:16 -0700, Jeremy Huddleston wrote:
Just to be 100% complete here... This has the effect that
DRI_DRIVER_PATH= rather than ${libdir}/dri on systems without dri.pc
Is that situation ok? Should you check for existence of dri.pc first
and set it to the old fallback if
On Tue, 2010-08-24 at 17:35 -0700, Dan Nicholson wrote:
To me, the only reason is that since you can't override the path at
runtime either, there's no way to set a custom path to the modules.
Maybe that's more of a runtime concern, though.
A custom path for dri would be a path that is
On Wed, Aug 25, 2010 at 6:12 AM, Gaetan Nadon mems...@videotron.ca wrote:
On Tue, 2010-08-24 at 17:35 -0700, Dan Nicholson wrote:
To me, the only reason is that since you can't override the path at
runtime either, there's no way to set a custom path to the modules.
Maybe that's more of a
On Wed, 2010-08-25 at 07:24 -0700, Dan Nicholson wrote:
Not so much a system builder, but a developer or someone debugging a
problem that wants to point at an alternate set of drivers. I don't
think the configure option helps as much as a xorg.conf option,
though.
I think we are all in
On Mon, 2010-08-23 at 10:53 -0400, Gaetan Nadon wrote:
The trusted location of the dri driver directory can be obtained
from the mesa dri.pc pkg-config file.
Could just use dri.pc for the default value of the option, rather than
removing it altogether?
--
Earthling Michel Dänzer |
On Tue, 2010-08-24 at 12:56 +0200, Michel Dänzer wrote:
Could just use dri.pc for the default value of the option, rather than
removing it altogether?
Yes. I think the author of the bug report wishes to also remove the
option as it is no longer useful.
This is an opportunity for me to get
2010/8/24 Gaetan Nadon mems...@videotron.ca:
On Tue, 2010-08-24 at 12:56 +0200, Michel Dänzer wrote:
Could just use dri.pc for the default value of the option, rather than
removing it altogether?
Yes. I think the author of the bug report wishes to also remove the option
as it is no longer
On Tue, Aug 24, 2010 at 2:12 PM, Kristian Høgsberg k...@bitplanet.net wrote:
2010/8/24 Gaetan Nadon mems...@videotron.ca:
On Tue, 2010-08-24 at 12:56 +0200, Michel Dänzer wrote:
Could just use dri.pc for the default value of the option, rather than
removing it altogether?
Yes. I think the
The trusted location of the dri driver directory can be obtained
from the mesa dri.pc pkg-config file.
Signed-off-by: Gaetan Nadon mems...@videotron.ca
---
configure.ac |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/configure.ac b/configure.ac
index
23 matches
Mail list logo
