From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109345] drm-next-2018-12-14 -Linux PPC
Date: Mon, 13 May 2019 09:37:48 +0000 [thread overview]
Message-ID: <bug-109345-502-oeZ3km3YmY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109345-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1064 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109345
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #45 from Michel Dänzer <michel@daenzer.net> ---
Reviewing the information, I'm afraid it's not clear that there's a bug here.
The description says the FirePro is the secondary card in a PCIe 1x slot,
whereas the R7 is in the PCIe 16x slot. Thus it seems pretty clear that without
explicit configuration, Xorg should be expected to come up on the R7. Arguably
it was actually the previous behaviour that was buggy.
Something like this in /etc/X11/xorg.conf should be enough to make Xorg use the
FirePro card:
Section "Device"
Identifier "whatever"
BusID "PCI:5@4096:0:0"
EndSection
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2550 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-13 9:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 7:34 [Bug 109345] drm-next-2018-12-14 -Linux PPC bugzilla-daemon
2019-01-14 10:49 ` bugzilla-daemon
2019-01-15 7:55 ` bugzilla-daemon
2019-03-24 8:38 ` bugzilla-daemon
2019-03-25 14:25 ` bugzilla-daemon
2019-03-30 7:21 ` bugzilla-daemon
2019-04-01 16:05 ` bugzilla-daemon
2019-04-02 7:44 ` bugzilla-daemon
2019-04-02 8:35 ` bugzilla-daemon
2019-04-02 14:03 ` bugzilla-daemon
2019-04-11 7:24 ` bugzilla-daemon
2019-04-11 7:27 ` bugzilla-daemon
2019-04-29 14:04 ` bugzilla-daemon
2019-04-29 14:19 ` bugzilla-daemon
2019-04-30 7:19 ` bugzilla-daemon
2019-04-30 7:29 ` bugzilla-daemon
2019-04-30 16:00 ` bugzilla-daemon
2019-05-01 14:44 ` bugzilla-daemon
2019-05-01 14:54 ` bugzilla-daemon
2019-05-01 15:00 ` bugzilla-daemon
2019-05-01 16:06 ` bugzilla-daemon
2019-05-01 17:00 ` bugzilla-daemon
2019-05-01 17:04 ` bugzilla-daemon
2019-05-01 18:47 ` bugzilla-daemon
2019-05-02 3:44 ` bugzilla-daemon
2019-05-02 7:56 ` bugzilla-daemon
2019-05-02 21:47 ` bugzilla-daemon
2019-05-03 11:00 ` bugzilla-daemon
2019-05-03 16:37 ` bugzilla-daemon
2019-05-04 21:23 ` bugzilla-daemon
2019-05-05 10:14 ` bugzilla-daemon
2019-05-05 14:17 ` bugzilla-daemon
2019-05-06 8:09 ` bugzilla-daemon
2019-05-06 10:52 ` bugzilla-daemon
2019-05-07 21:08 ` bugzilla-daemon
2019-05-07 21:18 ` bugzilla-daemon
2019-05-08 7:08 ` bugzilla-daemon
2019-05-08 11:13 ` bugzilla-daemon
2019-05-09 10:04 ` bugzilla-daemon
2019-05-09 11:52 ` bugzilla-daemon
2019-05-10 3:45 ` bugzilla-daemon
2019-05-10 14:15 ` bugzilla-daemon
2019-05-10 15:39 ` bugzilla-daemon
2019-05-11 4:47 ` bugzilla-daemon
2019-05-11 4:51 ` bugzilla-daemon
2019-05-13 9:37 ` bugzilla-daemon [this message]
2019-05-13 14:20 ` bugzilla-daemon
2019-05-27 1:54 ` bugzilla-daemon
2019-06-03 8:42 ` bugzilla-daemon
2019-08-06 2:23 ` 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-109345-502-oeZ3km3YmY@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;
as well as URLs for NNTP newsgroup(s).