All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 117131] vga_switcheroo does not switch IGP -> DIS ( IGP == i915 , DIS == radeon )
Date: Tue, 26 Apr 2016 15:26:25 +0000	[thread overview]
Message-ID: <bug-117131-2300-oHwe65FfAD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-117131-2300@https.bugzilla.kernel.org/>

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

--- Comment #18 from Jason Vas Dias <jason.vas.dias@gmail.com> ---
I think FGLRX is evidently able to run my laptop's display in 
dual-driver mode whereby the Intel IGP card runs the LCD in some sort of
"slave" mode under the control of the fglrx Radeon 8970M controller module,
to display frames produced by the Radeon card.

It would be nice if Linux would either 
A) fully support this configuration 
OR
B) detect that this configuration is not supported and refuse
   to attempt to go into graphics mode at all on the radeon card.
  - this would include things like vga_switcheroo complaining 
    / returning an error when asked to switch without a MUX .

Linux is evidently not doing either yet .

I'm not convinced the intel driver can "go it alone" either in this
scenario -
see: https://bugs.freedesktop.org/show_bug.cgi?id=95078

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

  parent reply	other threads:[~2016-04-26 15:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 19:17 [Bug 117131] New: vga_switcheroo does not switch IGP -> DIS ( IGP == i915 , DIS == radeon ) bugzilla-daemon
2016-04-24 19:28 ` [Bug 117131] " bugzilla-daemon
2016-04-24 19:46 ` bugzilla-daemon
2016-04-24 20:30 ` bugzilla-daemon
2016-04-24 20:44 ` bugzilla-daemon
2016-04-24 23:21 ` bugzilla-daemon
2016-04-25 13:58 ` bugzilla-daemon
2016-04-25 17:43 ` bugzilla-daemon
2016-04-25 17:49 ` bugzilla-daemon
2016-04-25 17:59 ` bugzilla-daemon
2016-04-25 18:49 ` bugzilla-daemon
2016-04-25 19:02 ` bugzilla-daemon
2016-04-25 19:25 ` bugzilla-daemon
2016-04-25 19:39 ` bugzilla-daemon
2016-04-25 20:19 ` bugzilla-daemon
2016-04-25 20:48 ` bugzilla-daemon
2016-04-25 20:51 ` bugzilla-daemon
2016-04-26  0:43 ` bugzilla-daemon
2016-04-26 15:26 ` bugzilla-daemon [this message]
2016-04-26 15:52 ` bugzilla-daemon
2016-04-26 16:55 ` bugzilla-daemon
2016-04-26 18:37 ` bugzilla-daemon
2016-04-26 18:38 ` bugzilla-daemon
2016-04-26 18:50 ` bugzilla-daemon
2016-04-26 22:11 ` bugzilla-daemon
2016-04-26 22:16 ` bugzilla-daemon
2016-04-26 22:20 ` 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-117131-2300-oHwe65FfAD@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.