Summary: | Request: Control Center for AMD GPU | ||
---|---|---|---|
Product: | Mesa | Reporter: | Ahmed Elsayed <ahmed.com> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Ahmed Elsayed
2018-10-13 15:12:34 UTC
You can use the drirc configuration file to force applications to automatically use the AMD card. udevadm info /dev/dri/card0 | grep ID_PATH_TAG udevadm info /dev/dri/card1 | grep ID_PATH_TAG This will give you the ID_PATH_TAG of your Intel and your AMD card. Then in $HOME/drirc you can set the device_id parameter for a given application to the value of the ID_PATH_TAG to use this card automatically. You can find an example here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/opengl-vulkan-mesa-gallium3d/920292-nvidia-developer-posts-auto-prime-detection-mesa-usb-loader-support Also this (uncomplete) app has a section to configure your drirc automatically for prime. It detects running apps using the gpu (thus you don't need to guess the app exe name) and you can set the card to use for them: https://github.com/axeldavy/driCenter The tricky part is making something that works across different desktop environments. Each desktop environment stores it's display settings in a different way. Additionally, since most of the infrastructure and APIs on Linux are common across GPUs, it would probably be better to make a generic control center that each desktop environment could get on board with for the common areas, and then we can add vendor/device specific knobs on top of that. That way we'd have a common interface across GPUs and it would work consistently across desktops. I hope that will be done one day. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/929. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.