On 03/19/13 09:25 PM, Pat Somerville wrote:
Question 2c: I get the impression that at least some versions of X.org X
Server
are general, kernel-version-number-specific, for example, version 2.4, 2.6, et
cetera? Is that true of all of them?
Nope - the Xorg server itself runs on BSD, Solaris,
And so may be why I do not find similar issue on my Ubuntu platform.
From: Zhigang Gong [mailto:zhigang.g...@linux.intel.com]
Sent: Tuesday, March 19, 2013 7:18 PM
To: He, Junyan; 'Michel Dänzer'
Cc: 'Alex B'; xorg-devel@lists.x.org; gla...@lists.freedesktop.org
Subject: RE: [Glamor] glamor with
Hey,
Op 19-03-13 22:13, Chris Wilson schreef:
On Tue, Mar 19, 2013 at 11:50:47AM +0100, Maarten Lankhorst wrote:
The drmSetMaster call is needed, but the spinning is really just waiting for
the workqueue to run.
bryce's patch never worked, it just caused it to try drmsetinterfaceversion
Op 20-03-13 09:40, Maarten Lankhorst schreef:
Hey,
Op 19-03-13 22:13, Chris Wilson schreef:
On Tue, Mar 19, 2013 at 11:50:47AM +0100, Maarten Lankhorst wrote:
The drmSetMaster call is needed, but the spinning is really just waiting
for the workqueue to run.
bryce's patch never worked, it
It seems ODEV_ATTRIB_BUSID is only used in xf86platformProbe for pci devices,
and there's no need to open the drm device to find out the pci id. It
can be determined from the sysfs path.
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0 will become
pci::01:00.0 here.
Op 20-03-13 14:03, Maarten Lankhorst schreef:
It seems ODEV_ATTRIB_BUSID is only used in xf86platformProbe for pci devices,
and there's no need to open the drm device to find out the pci id. It
can be determined from the sysfs path.
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
https://bugs.freedesktop.org/show_bug.cgi?id=61822
--- Comment #6 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #5)
Has anyone ever run valgrind for Xorg?
Lots of people have. Basically the same story as running Xorg in gdb.
(In reply to comment #3)
Also, my stack trace
