RADEON Scratch Register Usage

2005-11-28 Thread vehemens
I've been looking at my remaining lockups, and find that I keep coming back to the use of scratch registers in the driver for one of them. If I'm reading the code correctly, the scratch registers are per device, not per client. This would mean that you can't run more then one client without t

Re: drm_handle_t vs. unsigned long

2005-11-28 Thread Adam Jackson
On Friday 25 November 2005 17:51, Brian Paul wrote: > I've been poking around in the DRM code a bit. One thing I've noticed > is that the xf86drm.h file in the DRI/drm tree is a bit out of sync > with the xf86drm.h file in the X.org tree. In particular, the use of > unsigned long vs. drm_handle_t

[Bug 5171] Memleak in xf86drmHash.c::HashHash()

2005-11-28 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5171 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 4087] indirect GLX crashs Xserver / in libGLcore.so ?

2005-11-28 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4087 --- Additional Comments From [EMAIL PROTECTED] 2005-11-29 04:31 --- I pla

Re: RADEON Scratch Register Usage

2005-11-28 Thread Benjamin Herrenschmidt
On Mon, 2005-11-28 at 02:18 -0800, vehemens wrote: > I've been looking at my remaining lockups, and find that I keep coming back > to > the use of scratch registers in the driver for one of them. > > If I'm reading the code correctly, the scratch registers are per device, not > per client. Th