dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98146] DRI_PRIME=1 and fullscreen issues
Date: Fri, 07 Oct 2016 18:27:30 +0000	[thread overview]
Message-ID: <bug-98146-502-7VSYg1H5HR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98146-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1608 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98146

--- Comment #5 from Darek Deoniziak <darekdeoniziak@gmail.com> ---
"Also are you using DRI2 or DRI3?"
Not sure how to check it. The `cat /var/log/Xorg.0.log | grep -i DRI3` command
gives me: `[ 40491.158] (==) RADEON(G0): DRI3 enabled` so looks like it is only
enabled, but not probably not used, when I look for DRI2 the outpout looks like
this: http://pastebin.com/Nevad1GD

Also in xorg.conf.d I have file `10-amdgpu.conf` with content:
Section "OutputClass"
        Identifier "AMDgpu"
        MatchDriver "amdgpu"
        Driver "amdgpu"
EndSection

but in `10-monitor.conf` I have setup at the end of file (which works fine,
except for issues I've mention earlier):
...
Section "Device"
    Identifier "Device0"
    Driver "intel"
EndSection

Section "Device"
    Identifier "Device1"
    Driver "radeon"
EndSection

Not sure what's the difference between radeon and amdgpu driver in this case,
can 10-amdgpu.conf be related to amdgpu-pro? I've tried amdgpu-pro few weeks
ago but that didn't work out at all so I decided to stick with opensource one.

Asking because I would like to try to enable DRI3 and recently it got kind of
harder to understand what drivers for radeon are in use (recently I think it
was only mesa and fglrx). To use DRI3 should file look like `20-radeon.conf` as
filename and inside:
Section "Device"
   Identifier "Radeon"
   Driver "radeon"
   Option "SwapBufferWait" "0"
   Option "DRI" "3"
EndSection

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2588 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-07 18:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:02 [Bug 98146] DRI_PRIME=1 and fullscreen issues bugzilla-daemon
2016-10-07 15:29 ` bugzilla-daemon
2016-10-07 16:33 ` bugzilla-daemon
2016-10-07 16:34 ` bugzilla-daemon
2016-10-07 16:55 ` bugzilla-daemon
2016-10-07 18:27 ` bugzilla-daemon [this message]
2016-10-07 18:46 ` bugzilla-daemon
2016-10-07 19:51 ` bugzilla-daemon
2016-10-07 19:53 ` bugzilla-daemon
2016-10-10  9:12 ` bugzilla-daemon
2016-10-11  7:21 ` bugzilla-daemon
2016-10-11  7:32 ` bugzilla-daemon
2016-10-11  7:41 ` bugzilla-daemon
2016-10-20 19:51 ` bugzilla-daemon
2016-10-20 20:27 ` bugzilla-daemon
2016-10-21  5:33 ` bugzilla-daemon
2016-10-22 16:24 ` bugzilla-daemon
2016-10-22 17:40 ` bugzilla-daemon
2016-10-22 20:52 ` bugzilla-daemon
2016-10-25  6:35 ` bugzilla-daemon
2017-06-25  6:42 ` bugzilla-daemon
2017-06-25 13:35 ` bugzilla-daemon
2017-07-25 12:33 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98146-502-7VSYg1H5HR@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox