Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
d3d9_dri3 [2014/10/11 19:02]
okias [How to verify that DRI3 is running?] 		d3d9_dri3 [2015/08/29 03:28] (current)
sarnex
Line 1: Line 1:
 ==== Vendor specific ==== ==== Vendor specific ====
-=== Radeon with GLAMOR support === +=== Radeons with EXA support (9700 - HD6000) === 
-  * only Radeon cards with GLAMOR support are supported at this time **>=** HD **6000** +  * Set ''Option "DRI" "3"'' in Xorg.conf 
-  * for the HD **6000** series you must enable '' Option          "AccelMethod" "glamor" '' in your xorg.conf files! +  * you can check DRI3 in Xorg.log 
-  * **don't expect any messages about DRI3 in Xorg.0.log!** XServer is mostly silent about it.+=== Radeon with GLAMOR support (HD6000 - latest) === 
 +  * Set ''Option "DRI" "3"'' in Xorg.conf 
 +  * for the HD **6000** series you may want enable '' Option          "AccelMethod" "glamor" '' in your xorg.conf files for getting better performance 
 +  * Look for ''DRI3 enabled'' in Xorg.log 
 +  * The Radeon DDX was recently updated with vsync support with DRI3, so you should have no issues now.
 === nVidia === === nVidia ===
-  * it should just work at this time+  * DRI3 is enabled by default when using glamor as of nouveau DDX version 1.0.11, but it is buggy currently (imirkin)
 ==== How to verify that DRI3 is running? ==== ==== How to verify that DRI3 is running? ====
-  * this will work only for Mesa-3D with **[[d3d9_debugging|debug]]** enabled or libgl1-mesa-glx-dbg package on Ubuntu!+  * this will work only for Mesa-3D with **[[d3d9_debugging|debug]]** enabled OR libgl1-mesa-glx-dbg package on Ubuntu!
   * run glxgears or any simple application with ''**gdb app_name**''   * run glxgears or any simple application with ''**gdb app_name**''
   * ''**break dri3_swap_buffers**'' will set a breakpoint in dri3_swap_buffers   * ''**break dri3_swap_buffers**'' will set a breakpoint in dri3_swap_buffers
   * Answer **y** to //Function "dri3_swap_buffers" not defined.//   * Answer **y** to //Function "dri3_swap_buffers" not defined.//
-  * ''**run**'' and it **should stop** at this function. If it doesn't, you're **not** using DRI3+  * ''**run**'' and it **should stop** at this function. If it doesn't, you're **not** using DRI3 OR you compiled with --disable-dri3 for VSync. If it's the latter, this is expected and everything should still work.