Thread (27 messages) 27 messages, 5 authors, 2003-10-17

Re: ioremap problem on highmem

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2003-10-16 10:10:28

On Thu, 2003-10-16 at 01:17, James Simmons wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help