Announcement

Collapse
No announcement yet.

Mesa's DRIRC Options To Become More Driver-Agnostic

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mesa's DRIRC Options To Become More Driver-Agnostic

    Phoronix: Mesa's DRIRC Options To Become More Driver-Agnostic

    There's good news for both Mesa users and developers when needing to workaround OpenGL bugs / buggy applications and games...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I haven't looked deeply at driconf, but from what I have seen, the dri3 offloading section doesn't really "fit" into the model of setting driconf settings "for" a specific driver. I wasn't sure how it could be implemented except maybe a completely different tab:
    http://lists.freedesktop.org/archive...ay/060131.html
    The problem is that "loader" is treated as a separate driver, but driconf would be loaded with the currently used driver instead:
    Code:
    <driconf>
        <device driver="loader">
            <application name="Glmark2" executable="glmark2-wayland">
                <option name="device_id" value="pci-0000_01_00_0" />
            </application>
        </device>
    </driconf>
    Is this going to improve?

    Comment

    Working...
    X