dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27502] modeset=1 causes fallback to software rendering on RV350 (PowerBook G4)
Date: Tue,  6 Apr 2010 18:03:42 -0700 (PDT)	[thread overview]
Message-ID: <20100407010342.D7AFD13005D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27502-502@http.bugs.freedesktop.org/>

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

Jeremy Huddleston <jeremyhu@freedesktop.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michel@daenzer.net

--- Comment #6 from Jeremy Huddleston <jeremyhu@freedesktop.org> 2010-04-06 18:03:42 PDT ---
Based on Michael's comments, it looks like radeonfb and radeon can live
side-by-side, and radeonfb is needed for console access:

http://lists.x.org/archives/xorg-devel/2009-May/000814.html

I'd rather not blacklist radeonfb and loose console.

Does the KMS support in 2.6.32's radeon driver allow console access without
radeonfb, and if so, is there anything special I need to do to use it?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  parent reply	other threads:[~2010-04-07  1:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  0:30 [Bug 27502] New: modeset=1 causes fallback to software rendering on RV350 (PowerBook G4) bugzilla-daemon
2010-04-07  0:30 ` [Bug 27502] " bugzilla-daemon
2010-04-07  0:31 ` bugzilla-daemon
2010-04-07  0:31 ` bugzilla-daemon
2010-04-07  0:32 ` bugzilla-daemon
2010-04-07  0:34 ` bugzilla-daemon
2010-04-07  0:36 ` bugzilla-daemon
2010-04-07  1:03 ` bugzilla-daemon [this message]
2010-04-07  1:10 ` bugzilla-daemon
2010-04-07  1:12 ` bugzilla-daemon
2010-04-07  1:14 ` bugzilla-daemon
2010-04-07  1:32 ` bugzilla-daemon
2010-04-07  1:33 ` bugzilla-daemon
2010-04-07  1:46 ` bugzilla-daemon
2010-04-07  2:27 ` bugzilla-daemon
2010-04-07  2:29 ` bugzilla-daemon
2010-04-07  2:29 ` bugzilla-daemon
2010-04-07  2:31 ` bugzilla-daemon
2010-04-07  2:33 ` bugzilla-daemon
2010-04-07  6:54 ` bugzilla-daemon
2010-04-07 22:13 ` 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=20100407010342.D7AFD13005D@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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