] [PATCH v3 1/2] configure.ac: Enable GLX_USE_TLS
if possible.
Even if the system supports tls, the x server may not have been
built with it. As i recall, there is an issue with mismatching tls
between x and drivers... Can a non-tls server load a tls driver?
>
AFAIK, a mesa built without TLS
On 02/15/2012 05:15 PM, Matt Turner wrote:
On Wed, Feb 15, 2012 at 7:52 AM, tf (mobile) wrote:
Even if the system supports tls, the x server may not have been built with it.
As i recall, there is an issue with mismatching tls between x and drivers...
Can a non-tls server load a tls driver?
> -Original Message-
> From: tf (mobile) [mailto:tfo...@sci.utah.edu]
> Sent: Wednesday, February 15, 2012 8:53 PM
> To: zhigang.g...@linux.intel.com
> Cc: dbn.li...@gmail.com; nob...@dreamwidth.org;
> mesa-dev@lists.freedesktop.org
> Subject: Re: [Mesa-dev] [PATCH
On Wed, Feb 15, 2012 at 7:52 AM, tf (mobile) wrote:
> Even if the system supports tls, the x server may not have been built with
> it. As i recall, there is an issue with mismatching tls between x and
> drivers... Can a non-tls server load a tls driver?
I don't think mismatching TLS/non-TLS Me
Even if the system supports tls, the x server may not have been built with it.
As i recall, there is an issue with mismatching tls between x and drivers...
Can a non-tls server load a tls driver?
Anyway, if there's an issue there, this check must be more complicated -- it
can't be just, "does
From: Zhigang Gong
If the system support tls, we prefer to enable it by default
just as xserver does. Actually, the checking code is copied
from xserver/configure.ac.
According to nobled's suggestion, move the checking before
enable_asm. As if tls_model is not supported, then asm may
can't work c
