[Bug 943] Patch to add support for 32bit DRI clients on 64bit machines
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=943 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 02:37 --- Created an attachment (id=2024) -- (https://bugs.freedesktop.org/attachment.cgi?id=2024action=view) dmesg from 64-bit kernel and Xserver and 32-bit glxinfo This is my dmesg output from an X86-64 kernel and Xserver and an ia32 chrooted glxinfo. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 943] Patch to add support for 32bit DRI clients on 64bit machines
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=943 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 02:40 --- Created an attachment (id=2025) -- (https://bugs.freedesktop.org/attachment.cgi?id=2025action=view) strace from 32-bit glxinfo on 64-bit kernel and Xserver This is the strace from an chrooted ia32 glxinfo on an X86-64 Kernel and Xserver. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Vladimir Dergachev wrote: I just tagged gliding_penguin snapshot of r300_driver. We have not had snapshot in a long time and it seemed appropriate to make one. You can get the code by checking out r300_driver module with tag gliding_penguin from CVS at http://r300.sf.net/ . Use a command like this: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 \ co -P -z3 -r gliding_penguin r300_driver Both Quake and PPRacer (Open Source continuation of TuxRacer) work, with many Quake levels rendering very well (and I have not played PPRacer long enough to tell whether there is one that is broken). Big thanks to everyone who contributed to the release and, in particular, to many people who test CVS code :) Also, I updated the author list in the r300_driver/README file, but omitted e-mails of people that were added. If you would like your e-mail to appear please edit the file to your liking. If you have committed code to r300_driver and do not appear in the author list, I apologize - please add yourself ! I made the list by looking through CVS logs, I might have missed someone. Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. Adam --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Savage Command DMA
Hi Savage Users, Last night I committed support for command DMA for Savage4-based chips to DRM, Xorg and Mesa CVS. Unfortunately the upgrade may not be completely smooth, because the DRM and DDX changes exposed some bugs in the Mesa driver that have been fixed now. So if you upgrade, you need to upgrade all three components to get command DMA and to avoid strange failures of the 3D driver. On the bright side, this improves performance slightly and will hopefully bring a big performance boost to SuperSavages. These chips used to lock up in vertex DMA mode. I hope that command DMA works better with them. If it doesn't please let me know, then I'll have to disable command DMA too, on these chips. There is a new option for xorg.conf now: (from the manual page) Option DmaMode string This option influences in which way DMA (direct memory access) is used by the kernel and 3D drivers. Any -- Try command DMA first, then vertex DMA (default) Command -- Only use command DMA or dont use DMA at all Vertex -- Only use vertex DMA or dont use DMA at all None -- Disable DMA Command and vertex DMA cannot be enabled at the same time. Which DMA mode is actually used in the end also depends on the DRM version (only = 2.4.0 supports command DMA) and the hardware (Savage3D/MX/IX doesnt support command DMA). If you have trouble (lockups) with command DMA, please let me know (include information about your hardware, lspci output at least). As a workaround try setting DmaMode to Vertex, which should result in the old behavior. Best regards, Felix P.S.: Binary snapshot users will have to be patient. Hardware problems on the build machine prevent the builds at the moment. -- | Felix Khling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 06:08 --- Reopening this, because it says we should probably apply to xorg CVS also but no indication of wether that ever happened or not. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #402||approval_X11R6.8.x? Flag|| --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 06:11 --- (From update of attachment 402) Adding to 6.8.x approval request queue. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
On Sunday 06 March 2005 14:15, Adam K Kirchhoff wrote: Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. cu, Nicolai Adam pgpo4Bo89wFuG.pgp Description: PGP signature
Re: [R300] gliding_penguin snapshot
Nicolai Haehnle wrote: On Sunday 06 March 2005 14:15, Adam K Kirchhoff wrote: Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. cu, Nicolai Well, I've never build solo before, but I gave it a whirl. I edited the config file so it'd only build the r300 driver, but it errors out during the build process: CC=gcc CXX=g++ ../../../bin/mklib -o GL -major 1 -minor 2 \ -install ../../../lib -lm -lpthread -ldl ../../../src/mesa/main/dispatch.o ../../../src/mesa/glapi/glapi.o ../../../src/mesa/glapi/glthread.o ../../../src/mesa/drivers/dri/common/glcontextmodes.o ../../../../drm/libdrm/xf86drm.o ../../../../drm/libdrm/xf86drmHash.o ../../../../drm/libdrm/xf86drmRandom.o miniglx.o miniglx_events.o ../../../src/mesa/x86/glapi_x86.o mklib: Making Linux shared library: libGL.so.1.2 ../../../src/mesa/x86/glapi_x86.o(.text+0x20): In function `glNewList': ../../../src/mesa/x86/glapi_x86.S:128: multiple definition of `glNewList' ../../../src/mesa/main/dispatch.o(.text+0x0):../../src/mesa/glapi/glapitemp.h:74: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x40): In function `glEndList': ../../../src/mesa/x86/glapi_x86.S:129: multiple definition of `glEndList' ../../../src/mesa/main/dispatch.o(.text+0x46):../../src/mesa/glapi/glapitemp.h:79: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x60): In function `glCallList': ../../../src/mesa/x86/glapi_x86.S:130: multiple definition of `glCallList' ../../../src/mesa/main/dispatch.o(.text+0x7e):../../src/mesa/glapi/glapitemp.h:84: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x80): In function `glCallLists': ../../../src/mesa/x86/glapi_x86.S:131: multiple definition of `glCallLists' ../../../src/mesa/main/dispatch.o(.text+0xbe):../../src/mesa/glapi/glapitemp.h:89: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0xa0): In function `glDeleteLists': ../../../src/mesa/x86/glapi_x86.S:132: multiple definition of `glDeleteLists' ../../../src/mesa/main/dispatch.o(.text+0x10c):../../src/mesa/glapi/glapitemp.h:94: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0xc0): In function `glGenLists': ../../../src/mesa/x86/glapi_x86.S:133: multiple definition of `glGenLists' And so on and so forth :-) Are there any instructions on building linux-solo-x86 that I should be aware of? Adam --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #402|approval_X11R6.8.x? | Flag|| --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 08:25 --- (From update of attachment 402) DRI CVS was merged into X.org CVS a long time ago... this fix is on the 6.8 branch, as a little investigation would have shown. However, it looks like this case might have been overlooked when support for colour tiling was added on HEAD, Roland? -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 08:51 --- (In reply to comment #7) However, it looks like this case might have been overlooked when support for colour tiling was added on HEAD, Roland? Oops, this might be ambiguous... I mean Roland Scheidegger. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 14:30 --- I removed that since for color tiling displayWidth must be a multiple of 256 bytes (i.e. 64 pixels minimum at 32bpp, 128 pixels for 16bpp). Then I discovered even without color tiling the requested pitchInc for mode validation is 64 * pScrn-bitsPerPixel, i.e. 64 pixels too, so the additional check for z tiling alignment is unnecessary. At least I think that is what this code does... -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
Hi Adam, Could you remind me what video card you have ? And also any other details that might be relevant (like resolution, refresh rate, motherboard chipset, AGP mode, etc). thank you ! Vladimir Dergachev On Sun, 6 Mar 2005, Adam K Kirchhoff wrote: Vladimir Dergachev wrote: I just tagged gliding_penguin snapshot of r300_driver. We have not had snapshot in a long time and it seemed appropriate to make one. You can get the code by checking out r300_driver module with tag gliding_penguin from CVS at http://r300.sf.net/ . Use a command like this: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 \ co -P -z3 -r gliding_penguin r300_driver Both Quake and PPRacer (Open Source continuation of TuxRacer) work, with many Quake levels rendering very well (and I have not played PPRacer long enough to tell whether there is one that is broken). Big thanks to everyone who contributed to the release and, in particular, to many people who test CVS code :) Also, I updated the author list in the r300_driver/README file, but omitted e-mails of people that were added. If you would like your e-mail to appear please edit the file to your liking. If you have committed code to r300_driver and do not appear in the author list, I apologize - please add yourself ! I made the list by looking through CVS logs, I might have missed someone. Unfortunately, I'm still getting pretty constant lockups that seem to be related to high framerates. From ppcracer with RADEON_DEBUG set to all: http://68.44.156.246/ppracer.txt.gz On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. Adam --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] gliding_penguin snapshot
On the plus side, the texture problem that I had seen with neverputt/neverball seems to be resolved. This is probably the same lockup that I have seen. Unfortunately, I can't test anything for another two weeks or so. It may be worth it to test whether the lockup is due to some (race?) interaction between the 3D client and the X server. In particular, test if the lockup also happens with Solo. If the lockup happens with Solo as well, we at least know that it's not caused by the X server doing something. A less rigourous, but easier way is to launch bare X - put a single xterm line in your .xinitrc (or .xsession) and login. Then start the game from xterm window. If it does not lock up immediately, you can be reasonably sure that X does not mess with the hardware while the game is playing. best Vladimir Dergachev cu, Nicolai Adam --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 788] Display Artifacts at 1680x1050
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=788 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 18:37 --- (In reply to comment #9) Then I discovered even without color tiling the requested pitchInc for mode validation is 64 * pScrn-bitsPerPixel, i.e. 64 pixels too, so the additional check for z tiling alignment is unnecessary. That's only true for the cases when xf86ValidateModes() is used AFAICT. -- 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. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
