[Bug 3380] Dynamically generate GL dispatch functions for PowerPC

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=3380 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 17:29 --- Creat

DRM/Mesa Patches

Posting my latest DRM and Mesa patches in case they should prove useful to anyone else. They are to head as of early Saturday. I moved the CP idle outside the while loop in radeon_state.c. I think it may apply to the R300 as well as there is an "if R300 idle command" in the Xserver RADEONEnte

Re: R300 seems to be broken.

> > No ctx->FragmentProgram._Current!! > drmRadeonCmdBuffer: -22 (exiting) > > dmesg shows: > > [drm] Loading R300 Microcode > [drm:r300_emit_carefully_checked_packet0] *ERROR* Register 4500 failed check > as flag=00 > [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet0 failed > My bad, texrect nee

Re: Missing some Mesa Defines in xorg-6.9 build, final patch

On Sun, 2005-12-04 at 03:09 +0100, Roland Scheidegger wrote: > Otherwise, I'm unsure what the -DPTHREADS and -DHAVE_ALIAS switches > actually do. Maybe they conflict with other options (some xthreads > stuff maybe?) which are used in the xorg build. Yes , remove -DPTHREADS and -DHAVE_ALIAS switch

R300 seems to be broken.

Since yesterday afternoon, starting many (though not all) GL apps results in: No ctx->FragmentProgram._Current!! drmRadeonCmdBuffer: -22 (exiting) dmesg shows: [drm] Loading R300 Microcode [drm:r300_emit_carefully_checked_packet0] *ERROR* Register 4500 failed check as flag=00 [drm:r300_do_

[Bug 5245] New: After loading a Xserver with the glx module the network stops working

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=5245 Summary: After loading a Xserver with the glx module the network

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 04:21 --- I alm

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 [EMAIL PROTECTED] changed: What|Removed |Added --

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 04:16 --- Creat

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 04:14 --- Creat

[Bug 5244] glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 04:13 --- Creat

[Bug 5244] New: glxinfo reports no Direct Rendering although X logs say the opposite

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=5244 Summary: glxinfo reports no Direct Rendering although X logs say

Re: RADEON Scratch Register Usage

On Monday 28 November 2005 02:55 pm, Benjamin Herrenschmidt wrote: > The DRM lock should protect that ... note that I just spotted a DRM fix > "drm: fix quiescent locking" going into the linux kernel that may > explain races with the DRM lock. > > Also, there has been historical issues with the scr