On 06/02/2012 23:14, Carl Worth wrote:
> On 2012-02-04, Jon TURNEY wrote:
>> It looks like these error messages will always be emitted when
>> software-direct
>> and indirect are the only paths available (e.g. when ./configured with
>> --with-dri-drivers=swrast or --disable-driglx-direct).
>
> Th
On 2012-02-04, Jon TURNEY wrote:
> It looks like these error messages will always be emitted when software-direct
> and indirect are the only paths available (e.g. when ./configured with
> --with-dri-drivers=swrast or --disable-driglx-direct).
Thanks for sharing your concern, Jon. I certainly don'
On 04/02/2012 01:14, Carl Worth wrote:
> I recently had a problem with a dri driver failing to load, (it turned
> out to be a case of the driver being built for 64-bit, but running a
> 32-bit application).
>
> At the time, mesa switched over to indirect rendering without me
> realizing it at all.
I recently had a problem with a dri driver failing to load, (it turned
out to be a case of the driver being built for 64-bit, but running a
32-bit application).
At the time, mesa switched over to indirect rendering without me
realizing it at all. This left me quite confused. Finally, a kind
friend
