I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa bug
went to dri-devel. Is this intended, why don't use mesa-dev for all mesa
related bug instead and use dri-devel for libdrm/kernel modules only?
___
mesa-dev mailing list
mesa
https://bugs.freedesktop.org/show_bug.cgi?id=52347
--- Comment #2 from Phr33d0m 2012-09-03 05:14:41 UTC ---
Created attachment 66525
--> https://bugs.freedesktop.org/attachment.cgi?id=66525
mesa-9_pre20120831.log.gz (full build log)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs
https://bugs.freedesktop.org/show_bug.cgi?id=52347
--- Comment #1 from Phr33d0m 2012-09-03 05:13:49 UTC ---
Hello, I'm hitting this same issue on mesa-9_pre20120831.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
Y
https://bugs.freedesktop.org/show_bug.cgi?id=52347
Phr33d0m changed:
What|Removed |Added
CC||g...@politeia.in
--
Configure bugmail: https
Greetings, Mesa hackers,
I've hacked together a small (~500 sloc) preloadable library that
implements OpenGL offloading by means of GLX forking, similar to
VirtualGL. The basic idea is to track contexts and drawables and
create shadow contexts and pbuffers on the secondary X server,
redirecting al
Signed-off-by: Vinson Lee
---
src/gallium/auxiliary/util/u_cpu_detect.c |4 ++--
src/gallium/include/pipe/p_config.h |4
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/gallium/auxiliary/util/u_cpu_detect.c
b/src/gallium/auxiliary/util/u_cpu_detect.c
index e
