linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Jon Smirl <jonsmirl@yahoo.com>, Otto Solares <solca@guug.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: ioremap problem on highmem
Date: Thu, 16 Oct 2003 12:09:30 +0200	[thread overview]
Message-ID: <1066298970.646.123.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0310160012230.13660-100000@phoenix.infradead.org>

On Thu, 2003-10-16 at 01:17, James Simmons wrote:
> > My main motivation for this is to have a single driver controlling the 
> > graphics hardware on DRI supported systems. This will eliminate the problem 
> > with saving hardware state between VT's. 
> 
> Unless you disable the VT console system you still have to to deal with 
> switching from KDTEXT to KDGRAPHICS and back again. Its also userlands 
> responiblity to save the console state and restore it.

Which is a bit hellish... I would love a callback "restore" (or maybe
just a set_par with a "force" attribute bypassing check of old par !=
new par that most drivers have that gets called on switch back from
KDGRAPHICS to KDTEXT. In my experience, this is the only way to get
things back properly after XFree with radeons.

XFree _could_ probably be fixed, but it's a bit difficult, especially
saving & restoring the entire 2D accel state, and you know how long it
would take for an xfree fix to get in, while it's so easy for radeonfb
to just put back its own settings...




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  parent reply	other threads:[~2003-10-16 10:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 19:18 ioremap problem on highmem Otto Solares
2003-10-13 20:30 ` Jon Smirl
2003-10-14  0:14   ` Otto Solares
2003-10-14  0:46     ` Jon Smirl
2003-10-14  1:56       ` Otto Solares
2003-10-14  4:51         ` Jon Smirl
2003-10-15  1:13           ` Otto Solares
2003-10-15  1:37             ` Jon Smirl
2003-10-15 23:11             ` James Simmons
2003-10-16 10:15               ` Benjamin Herrenschmidt
2003-10-16 16:56                 ` Otto Solares
2003-10-17 16:58                   ` James Simmons
2003-10-14  8:30         ` Geert Uytterhoeven
2003-10-14  8:34       ` Geert Uytterhoeven
2003-10-14 14:42         ` Jon Smirl
2003-10-14 17:25           ` James Simmons
2003-10-14 17:23         ` James Simmons
2003-10-14 16:49       ` James Simmons
2003-10-14 17:59         ` Jon Smirl
2003-10-15 23:17           ` James Simmons
2003-10-16  0:34             ` Jon Smirl
2003-10-16 10:12               ` Benjamin Herrenschmidt
2003-10-16  0:43             ` I2C standalone vs integrated? Jon Smirl
2003-10-16 10:14               ` Benjamin Herrenschmidt
2003-10-17 16:43                 ` James Simmons
2003-10-16 10:09             ` Benjamin Herrenschmidt [this message]
2003-10-15 16:46       ` ioremap problem on highmem Benjamin Herrenschmidt

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=1066298970.646.123.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=solca@guug.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;
as well as URLs for NNTP newsgroup(s).