dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106271] Switch between AMD hybrid graphics (HD 8650G / HD 8970M) makes hardware reset.
Date: Tue, 20 Oct 2015 19:01:30 +0000	[thread overview]
Message-ID: <bug-106271-2300-gouhWUK5fT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106271-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=106271

Lukas Wunner <lukas@wunner.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lukas@wunner.de

--- Comment #3 from Lukas Wunner <lukas@wunner.de> ---
The pitcairn GPU says "No connectors reported connected with modes". I suppose
that's the discrete GPU?

Does this machine have a hardware mux at all? If not, the discrete GPU can only
be used to offload rendering and switching won't work. I guess the only thing
that can be improved in this case is to make radeon_atpx_switchto() a no-op on
muxless machines.

If on the other hand the machine *does* have a mux, the question is why the
pitcairn GPU didn't find any modes. Are there none in VBT? If so, the issue can
probably be solved by temporarily switching DDC to the discrete GPU on probe.
I'm working on patches to do that with apple-gmux on the MacBook Pro.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-10-20 19:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 17:40 [Bug 106271] New: Switch between AMD hybrid graphics (HD 8650G / HD 8970M) makes hardware reset bugzilla-daemon
2015-10-19 17:41 ` [Bug 106271] " bugzilla-daemon
2015-10-19 17:42 ` bugzilla-daemon
2015-10-20 19:01 ` bugzilla-daemon [this message]
2015-10-20 19:08 ` bugzilla-daemon
2015-10-27 15:27 ` bugzilla-daemon
2015-10-27 15:47 ` bugzilla-daemon
2015-10-30 14:33 ` bugzilla-daemon
2015-10-30 14:35 ` bugzilla-daemon
2015-10-30 14:36 ` bugzilla-daemon
2015-11-01  6:06 ` bugzilla-daemon
2015-11-12 14:44 ` bugzilla-daemon
2015-11-12 15:34 ` bugzilla-daemon
2015-11-15  8:39 ` bugzilla-daemon
2015-11-15 20:08 ` 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-106271-2300-gouhWUK5fT@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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