From: Boszormenyi Zoltan <zboszor@pr.hu>
To: Alex Deucher <alexdeucher@gmail.com>, Dave Airlie <airlied@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>
Subject: Re: AMD/AMD hybrid graphics
Date: Fri, 21 Feb 2014 15:32:09 +0100 [thread overview]
Message-ID: <53076369.9050006@pr.hu> (raw)
In-Reply-To: <CADnq5_N6x_vt3TSF8Vkg0j9Gj1UQ5W3V96sX9EESOfTmrY+9mQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
2014-02-21 14:37 keltezéssel, Alex Deucher írta:
>
> Does the attached patch help?
>
> Alex
Yes, it helped, thank you very much.
The compressed Xorg.0.log is attached as proof.
To others: the patch is against xf86-video-ati.
Two notes, though:
1. Is it normal that "xrandr --listproviders" lists 3 providers?
[zozo@localhost ~]$ cat xrandr-providers
Providers: number : 3
Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload
crtcs: 4 outputs: 3 associated providers: 2 name:radeon
Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload
crtcs: 0 outputs: 0 associated providers: 2 name:radeon
Provider 2: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload
crtcs: 0 outputs: 0 associated providers: 2 name:radeon
2. I tried glxgears with and without DRI_PRIME=1 as below:
[zozo@localhost ~]$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
299 frames in 5.0 seconds = 59.558 FPS
[zozo@localhost ~]$ DRI_PRIME=1 glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5589 frames in 5.0 seconds = 1117.730 FPS
5369 frames in 5.0 seconds = 1073.715 FPS
5699 frames in 5.0 seconds = 1139.670 FPS
Obviously, it doesn't sync to the framerate with PRIME.
On the other hand, nothing is displayed in the glxgears window.
I have llvm 3.4-4 and Mesa 10.1-rc1 from Fedora 21 rawhide.
I will go back to plain Fedora 20 (Xorg 1.14, llvm 3.3 and Mesa 9.2.5)
and try the same patch to see if there's any difference.
Best regards,
Zoltán Böszörményi
[-- Attachment #2: Xorg.0.log.fixed.gz --]
[-- Type: application/x-tar, Size: 9901 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-02-21 14:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 8:11 AMD/AMD hybrid graphics Boszormenyi Zoltan
2014-02-19 9:59 ` Michel Dänzer
2014-02-19 10:56 ` Boszormenyi Zoltan
2014-02-20 3:20 ` Michel Dänzer
2014-02-20 5:09 ` Boszormenyi Zoltan
2014-02-20 5:47 ` Michel Dänzer
2014-02-20 7:44 ` Boszormenyi Zoltan
2014-02-20 8:17 ` Boszormenyi Zoltan
2014-02-21 2:25 ` Michel Dänzer
2014-02-21 2:37 ` Dave Airlie
2014-02-21 13:37 ` Alex Deucher
2014-02-21 14:32 ` Boszormenyi Zoltan [this message]
2014-02-21 14:58 ` Boszormenyi Zoltan
2014-02-21 15:12 ` Alex Deucher
2014-02-21 19:05 ` Boszormenyi Zoltan
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=53076369.9050006@pr.hu \
--to=zboszor@pr.hu \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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