Re: scrollmode, accel_flags, fbcon.c ...

On Tue, 2004-03-30 at 03:50, James Simmons wrote:

Why do we need a var for ever VC. The card is on one hardware state at 
all times. The only times we nned to be concern with changes is for 
setfont, resize and VC switching. These are not common occurs. If the 
fbcon layer can't get the data it needs from struct vc_data then the upper
console layer is broken.

I don't agree. If I set a special mode with fbset in one console I
wnat this mode to say in that console and only that console unless
I use -a. The vc_data doesn't carry enough informations to set a
mode. It would also make things a lot simpler for fbdev apps that
use a different mode. 

Anyway, for the current mecanism to work, we need picking a mode
properly when resized or mode switched, which isn't the case right
now. The "var" that fbcon_resize pass to the fbdev is at best bogus
currently. The FB_ACTIVATE_FIND thing I did helps if the fbdev can
properly lookup for a mode (though there are still some issues in
radeonfb implementation of this as you have noticed).

Ben.




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click