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 81476] three monitors on two radeon cards works with some layouts not others
Date: Mon, 21 Jul 2014 16:28:37 +0000	[thread overview]
Message-ID: <bug-81476-502-GZRK1ItfCZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81476-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #17)
> 
> Phoronix suggests they don't all work well with open source drivers, those
> that do work often don't do well multi-monitor, and most don't do triple DVI
> output unless one buys one or more active adapters.

Displays should generally work fine.  Note that Evergreen, NI, and SI parts
only have two non-DP PLLs so they are limited to two independent non-DP clocks.
 So what this means is that you can only use two non-DP monitors with
independent timings.  If you want to use more than two non-DP monitors, you
have to use the exact same pixel clocks on several of the monitors so you don't
use more then two different clocks.  E.g., if all three of your monitors are
identical use the same modeline and pixel clock, you'd only need one PLL so you
should be fine.

> 
> I don't want to pick a card that becomes obsolete and where the driver
> writers have moved on and aren't interested in fixing the old bugs (e.g. the
> above bug in the radeon driver).

TBH, I think it's a hw limitation on r5xx hardware that's not properly handled.
 Unfortunately, X didn't support multi-card xrandr support when r5xx was still
actively being developed.  At that time, the only way to support multi-card
multi-head was zaphod mode which uses separate buffers for each display so you
never hit the hw limits.

> 
> Are the open source drivers for the evergreen cards (and newer) under active
> development?

Yes.

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

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

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

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

  parent reply	other threads:[~2014-07-21 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-81476-502@http.bugs.freedesktop.org/>
2014-07-18 21:53 ` [Bug 81476] three monitors on two radeon cards works with some layouts not others bugzilla-daemon
2014-07-18 22:46 ` bugzilla-daemon
2014-07-19  4:35 ` bugzilla-daemon
2014-07-19 10:45 ` bugzilla-daemon
2014-07-19 13:50 ` bugzilla-daemon
2014-07-21 14:48 ` bugzilla-daemon
2014-07-21 16:06 ` bugzilla-daemon
2014-07-21 16:28 ` bugzilla-daemon [this message]
2014-07-21 23:17 ` bugzilla-daemon
2014-07-22  0:04 ` bugzilla-daemon
2019-11-19  8:53 ` 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-81476-502-GZRK1ItfCZ@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