RE: My experience with the r300 driver
It's not. The driver limits it to 128 MB because the CPU can't access more than that. Thanks for the information! By the way, if i do the override that won't do nothing, in terms of amount of memory visible to GPU, right? --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: My experience with the r300 driver
On Wed, 2005-10-12 at 11:01 +0100, pedro.lixo wrote: By the way, if i do the override that won't do nothing, in terms of amount of memory visible to GPU, right? No, it will only affect what the driver thinks, and if that doesn't correspond with what's actually there and/or the hardware can handle, bad things will happen, which is why the override is usually bad and the patch you encountered which disables it is generally a good idea. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: confirming broken EXT_texture_rectangle.
Dave Airlie wrote:
Hi Roland,
Just to reconfirm what I said on IRC, I put my M7 back into my
machine and my internal application is defintely broken with the latest
radeon texrect changes...
I'll leave the M7 in for a few days and I'll have a look at the code if I
get a chance..
Does this patch help? It's somehwat overkill I guess always updating the
texture matrix when the _NEW_TEXTURE flag is set (though the r200 driver
does exactly that, not quite sure yet why), but I think currently the
update_texturematrix function may not get triggered if a texrect texture
changes and since the texture matrix is needed to get correct coords for
texture rectangles it may not work correctly.
Roland
Index: radeon_state.c
===
RCS file: /cvs/mesa/Mesa/src/mesa/drivers/dri/radeon/radeon_state.c,v
retrieving revision 1.36
diff -u -r1.36 radeon_state.c
--- radeon_state.c 8 Oct 2005 23:36:35 - 1.36
+++ radeon_state.c 12 Oct 2005 12:38:58 -
@@ -2281,7 +2280,7 @@
/* Does this need to be triggered on eg. modelview for
* texgen-derived objplane/eyeplane matrices?
*/
- if (new_state _NEW_TEXTURE_MATRIX) {
+ if (new_state (_NEW_TEXTURE|_NEW_TEXTURE_MATRIX) {
update_texturematrix( ctx );
}
Re: My experience with the r300 driver
Michel Dänzer wrote: On Wed, 2005-10-12 at 11:01 +0100, pedro.lixo wrote: By the way, if i do the override that won't do nothing, in terms of amount of memory visible to GPU, right? No, it will only affect what the driver thinks, and if that doesn't correspond with what's actually there and/or the hardware can handle, bad things will happen, which is why the override is usually bad and the patch you encountered which disables it is generally a good idea. Maybe the driver should be changed so it can output a more precise message, so people don't think that the ram is misdetected (e.g. something like detected 256MB, using 128MB). Also, the 128MB limit should just not be overridable, since we KNOW the driver can't cope with it (imho, otherwise allowing override is a nice idea, you can for instance simulate performance with cards which have less memory, though you could argue only smaller than detected values are useful, as long as the driver always detects the memory amount correctly). And, the driver also limits texture memory to only be useable up to 128MB, and I think this is not necessary (as textures are always blitted using the gpu and the memory used by them never touched directly by the cpu) or is it? Roland --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4087] indirect GLX crashs Xserver / in libGLcore.so ?
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 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |dri- ||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:16 --- (In reply to comment #4) Similar crash here. My scenario is maximizing a glxgears window with DRI completely disabled; the server SIGSEGVs after about one to four tries. Can you explain what you mean by one to four tries? Does that mean starting and stoping glxgears one to four time, or does it mean something else? Backtracing pinpoints the crash in flat_8R8G8B_z_triangle()---in a nutshell, pRow is pointing to invalid memory. I think that xmesa_alloc_storage() was previously called with bogus args. Here's an excerpt from my GDB session: That seems like a fair assessment, but I'm not sure how that could happen. Oh, and all this is with the Mesa code in the xorg CVS tree. Mesa CVS has some newer material, but to judge from my [very] cursory glance at it, they haven't come across this issue yet. Are you able to reproduce this when building X.org with the Mesa 6.4 branch? That branch is going to be merged into X.org soon, so I don't want to spend a lot of time digging into a bug that's already fixed. :) Thanks for retesting this issue after my 9/28 commits, BTW. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3982] glxinfo disagrees xorg.log / too old libgl
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=3982 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO Summary|glxinfo disagrees |glxinfo disagrees xorg.log / |xorg.log/to old libgl |too old libgl --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:20 --- Is anyone still able to reproduce this problem? If so, what does 'ldd $(which glxinfo)' show? Also, the attachments seem to be wrong. #3259 is incomplete, and #3260 is just wrong. It looks like a patch, not a glxinfo log. The output of 'LIBGL_DEBUG_VERBOSE=y glxinfo' would be useful. Thanks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4327] texture mapping bug on unichrome
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=4327 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:28 --- Is this bug still reproducable? I seem to recall keithw making some changes related to this since August. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4351] Howto Get direct rendering working for i915 under xorg 6.8.2 or 6.8.99
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=4351 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||NOTABUG --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:29 --- Since this appears to be an installation problem, closing as NOTABUG. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4508] Problem with DRM on Alpha arch.
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=4508 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:33 --- The interesting thing is that the Xorg.0.log claims that DRI is disabled because DMA could not be bootstrapped. If that's the case, then how are *any* of those DRM calls happening? I'm also curious about why the DMA bootstrap fails. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 715] MGA (CVS snapshot + XF86 4.x): Hard lockups ([dri] Idle timed out) during heavy texture use, requiring system reset.
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=715 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:45 --- Closing as a duplicate of bug #473. After reading the comments and looking at all the attached log files, I strongly suspect that both bugs have the same root cause. *** This bug has been marked as a duplicate of 473 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4508] Problem with DRM on Alpha arch.
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=4508 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 10:59 --- Hmmm, I don't know what happened, but I cannot build the code that I pulled out of cvs a few hours ago... ... XF86VMode.c:1180: error: `info' undeclared (first use in this function) XF86VMode.c:1184: error: `size' undeclared (first use in this function) XF86VMode.c:1186: error: `False' undeclared (first use in this function) XF86VMode.c:1193: error: `xReply' undeclared (first use in this function) XF86VMode.c:1193: error: syntax error before ')' token XF86VMode.c:1193: error: `xTrue' undeclared (first use in this function) XF86VMode.c:1201: error: `True' undeclared (first use in this function) XF86VMode.c: At top level: XF86VMode.c:1204: error: syntax error before XF86VidModeGetPermissions XF86VMode.c:1205: error: syntax error before '*' token XF86VMode.c:1209: warning: return type defaults to `int' XF86VMode.c:1209: warning: function declaration isn't a prototype XF86VMode.c: In function `XF86VidModeGetPermissions': XF86VMode.c:1210: error: `info' undeclared (first use in this function) XF86VMode.c:1214: error: `permissions' undeclared (first use in this function) XF86VMode.c:1216: error: `False' undeclared (first use in this function) XF86VMode.c:1223: error: `xReply' undeclared (first use in this function) XF86VMode.c:1223: error: syntax error before ')' token XF86VMode.c:1223: error: `xTrue' undeclared (first use in this function) XF86VMode.c:1231: error: `True' undeclared (first use in this function) make[4]: *** [XF86VMode.o] Error 1 make[4]: Leaving directory `/home/laurensv/xorg_cvs.orig/xc/lib/Xxf86vm' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/laurensv/xorg_cvs.orig/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/laurensv/xorg_cvs.orig/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/home/laurensv/xorg_cvs.orig/xc' make: *** [World] Error 2 Any ideas what happened? ;) Thanks in advance, Laurens -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4327] texture mapping bug on unichrome
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=4327 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 16:59 --- I just did a cvs update to my xorg, drm, and mesa trees and rebuilt everything. The problem still occurs. Is there anything else I should've updated? You can still test it the program I pasted into the bug report. As I mentioned earlier, you can change tiledim to 256 or 64 to see the problem a little more clearly. hope that helps. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: confirming broken EXT_texture_rectangle.
Does this patch help? It's somehwat overkill I guess always updating the texture matrix when the _NEW_TEXTURE flag is set (though the r200 driver does exactly that, not quite sure yet why), but I think currently the update_texturematrix function may not get triggered if a texrect texture changes and since the texture matrix is needed to get correct coords for texture rectangles it may not work correctly. Yes that makes by textures works again.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4508] Problem with DRM on Alpha arch.
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=4508 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 22:56 --- Created an attachment (id=3551) -- (https://bugs.freedesktop.org/attachment.cgi?id=3551action=view) Complete logfile of the failed build from the cvs sources. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
