dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Boszormenyi Zoltan <zboszor@pr.hu>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: AMD/AMD hybrid graphics
Date: Wed, 19 Feb 2014 18:59:25 +0900	[thread overview]
Message-ID: <1392803965.770.8.camel@thor.local> (raw)
In-Reply-To: <5304674C.6060604@pr.hu>

On Mit, 2014-02-19 at 09:11 +0100, Boszormenyi Zoltan wrote:
> 
> On second thought, the usage of VESA for installation and then
> switching to KMS might have caused the mixed behaviour, i.e. that
> the kernel recognized and initialized both chips but X used only the
> integrated one. But I don't want to reinstall the system to test
> this theory.

I doubt it would make any difference.


> Now, with the "Switchable" state, RADEON(0) lines (for ARUBA) and
> RADEON(G0) lines (for HAINAN) are present.
[...]
> I would like to have PRIME functional so I will need to set "Switchable
> Graphics" in the BIOS. What xorg.conf magic should I add to make it
> use the ARUBA chip for display but still keep HAINAN active for PRIME?

According to the screen enumeration above, that's already the case.

https://bugs.freedesktop.org/show_bug.cgi?id=69694 may be helpful for
troubleshooting the crash.


> Can Mesa/Xorg use both r600g and radeonsi at the same time?

Yes, that seems to work fine for others. You may need Mesa 10.1 or newer
though.


-- 
Earthling Michel Dänzer            |                  http://www.amd.com
Libre software enthusiast          |                Mesa and X developer

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

  reply	other threads:[~2014-02-19  9:59 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 [this message]
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
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=1392803965.770.8.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zboszor@pr.hu \
    /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