Hi Brian,
On 3/19/13, Brian Paul <bri...@vmware.com> wrote:
> I'm not familiar with glxspheres. But the xlib/swrast driver was
> optimized for simple things like glxgears. llvm might be slower on
> that kind of thing, but it should be much, much faster with modern
> apps that uses shaders and texturing.
>
>
>> It is fair to say, if running llvm driver in my local machine (a
>> 32-bit CentOS 6.2 without VNC connection), it was indeed faster than
>> the xlib driver.
>>
>> Seems to me that the llvm driver broken the xlib VNC connection which
>> could be caused by either I haven't configure the llvm correctly, or
>> mesa llvm compile process may have bugs.
>
> I don't understand what you mean by "llvm driver broken the xlib VNC
> connection".
Cannot run GL application using llvm driver via VNC. I'll change to a
faster network and test it again, will let you know tomorrow.
>
>
>> For your further examination, please see following configurations for
>> building each drivers:
>>
>> (1) Compile xlib driver
>>
>> ${SOURCE}/${CONFIGURE} --prefix=${INSTALL} --enable-xlib-glx
>> --disable-dri --with-gallium-drivers=swrast
>>
>>
>> (2) Compile llvm driver
>>
>> LLVM="/usr/local/libllvm/3.2"
>>
>> ${SOURCE}/${CONFIGURE} --prefix=${INSTALL} --enable-xlib-glx
>> --disable-dri --enable-gallium-llvm --with-gallium-drivers=swrast
>> --with-llvm-shared-libs=${LLVM}/lib --with-llvm-prefix=${LLVM}
>>
>> Manually change libGL.so and libGL.so.1 to link
>> lib/gallium/libGL.so.1.5.0.
>
> Looks OK to me.
Thanks for the confirmation.
Kind regards.
Jupiter
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
