public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Mihai Dontu <mihai.dontu@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.6.23-rc7 + radeonfb/s2ram
Date: Mon, 24 Sep 2007 10:07:58 +1000	[thread overview]
Message-ID: <1190592478.6886.9.camel@localhost.localdomain> (raw)
In-Reply-To: <E1IZZ37-0001OI-8g@flower>


On Sun, 2007-09-23 at 23:31 +0200, Oleg Verych wrote:
> * Sun, 23 Sep 2007 22:22:28 +0300
> * Organization: Home
> 
> []
> >> > 
> >> >   So there, if one wants "ATI Radeon display support" on Radeon XPRESS 200M with
> >> >   X using radeon_drv.so, *should* put "Framebuffer Console support" to N (if it's
> >> >   not already).
> []
> >   Bottom line: no radeonfb for me :( at least, not now; but I have to be honest with
> >   you: I don't see what commit dd1447134454b169d5ae353aceb93f2368db8547 brought new
> >   into the picture. The previous radeonfb worked just great, but then, again, maybe I'm
> >   not using the console at it's full power :)
> 
> In fact, it's known statement, that there must only one hardware driver
> for graphic adapter. Be it framebuffer with X fb driver on it or legacy
> VGA text and X with its driver.so and 3D stuff.
> 
> (i choose legacy text without X for the most of my time, though :)

Not quite ... on PowerMacs, we've been routinely using radeonfb and X
together. However, for that to work, in general, one has to be careful
to switch back to console mode before suspending and back to X after
resume, which seems to have been broken by many distro lately, probably
because somebody made it optional in the kernel...

Ben.



  reply	other threads:[~2007-09-24  0:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22  5:27 2.6.23-rc7 + radeonfb/s2ram Mihai Donțu
2007-09-22 14:46 ` Mihai Donțu
2007-09-23 10:20   ` Benjamin Herrenschmidt
2007-09-23 16:37     ` Mihai Donțu
2007-09-23 17:51       ` Mihai Donțu
2007-09-23 18:31         ` Mihai Donțu
2007-09-23 19:18           ` Rafael J. Wysocki
2007-09-23 19:22             ` Mihai Donțu
2007-09-23 21:31               ` Oleg Verych
2007-09-24  0:07                 ` Benjamin Herrenschmidt [this message]
2007-09-24  0:06               ` Benjamin Herrenschmidt
2007-09-24 14:43 ` Andreas Herrmann
2007-09-25  7:09   ` Mihai Donțu
2007-09-25 15:48     ` Randy Dunlap

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=1190592478.6886.9.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.dontu@gmail.com \
    --cc=olecom@flower.upol.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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