On 2014-07-24 22:20:55, Kenneth Graunke wrote:
Emil,
[snip]
For what it's worth, I'm fine with your suggestion of reading
GBM_DRIVERS_PATH first, then LIBGL_DRIVERS_PATH. It's the sensible
way to do things - it adds the new useful behavior the 6 of us want,
while preserving the existing
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
Generally this split leads to confusion as to why gbm doesn't work.
This patch makes
On Thu, Jul 24, 2014 at 1:32 PM, Emil Velikov emil.l.veli...@gmail.com wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
Generally this
On Thu, Jul 24, 2014 at 1:43 PM, Kristian Høgsberg k...@bitplanet.net wrote:
On Thu, Jul 24, 2014 at 1:32 PM, Emil Velikov emil.l.veli...@gmail.com
wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
Generally this split leads to
On 24/07/14 22:08, Dylan Baker wrote:
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
On Thu, Jul 24, 2014 at 5:17 PM, Emil Velikov emil.l.veli...@gmail.com wrote:
On 24/07/14 22:08, Dylan Baker wrote:
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm
On 25/07/14 03:14, Matt Turner wrote:
On Thu, Jul 24, 2014 at 5:17 PM, Emil Velikov emil.l.veli...@gmail.com
wrote:
On 24/07/14 22:08, Dylan Baker wrote:
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On 22/07/14 19:43, Dylan Baker wrote:
GBM_DRIVERS_PATH is not documented, and
On Thu, Jul 24, 2014 at 8:02 PM, Emil Velikov emil.l.veli...@gmail.com wrote:
On 25/07/14 03:14, Matt Turner wrote:
On Thu, Jul 24, 2014 at 5:17 PM, Emil Velikov emil.l.veli...@gmail.com
wrote:
On 24/07/14 22:08, Dylan Baker wrote:
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On Friday, July 25, 2014 04:02:48 AM Emil Velikov wrote:
On 25/07/14 03:14, Matt Turner wrote:
On Thu, Jul 24, 2014 at 5:17 PM, Emil Velikov emil.l.veli...@gmail.com
wrote:
On 24/07/14 22:08, Dylan Baker wrote:
On Thursday, July 24, 2014 09:32:38 PM Emil Velikov wrote:
On 22/07/14
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
Generally this split leads to confusion as to why gbm doesn't work.
This patch makes LIBGL_DRIVERS_PATH the main variable, but uses
Reviewed-by: Jordan Justen jordan.l.jus...@intel.com
On Tue, Jul 22, 2014 at 11:43 AM, Dylan Baker baker.dyla...@gmail.com wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
On Tue, Jul 22, 2014 at 11:43 AM, Dylan Baker baker.dyla...@gmail.com wrote:
GBM_DRIVERS_PATH is not documented, and only used to set the location of
gbm drivers, while LIBGL_DRIVERS_PATH is used for everything else, and
is documented.
Generally this split leads to confusion as to why gbm
13 matches
Mail list logo
