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

quoted

But an fbdev that implements an accelerated copyarea ?

I don't want such heuristics in fbcon, they are just asking for trouble,
I think we should redraw on non-accelerated and copy on accelerated,

You mean, if ywrap/ypan is not available/not possible (e.g. partial screen
scrolls)? Yes, that makes sense.

Sounds like we need to update update_scrollmode. So what do we have so 
far. 

1. test for ywrap/ypan. This test should see if the screen is more than 
   two whole screens in size. 

2. Test if xxxfb_copyarea is accelerated. If it is set to YMOVE.

3. If xxxfb_copyare is not accelerated then redraw the screen.

If I'm missing anything let me know.

Which means additional flags to fb_fix_screeninfo...

:-( I'm hoping we can develope some kind of nice logic. Often I seen 
a driver writer use the wrong flag.

quoted

One thing I don't like in the new fbcon is the way it deals with the
var structure anyway. I think it should have one var per VC.

I agree.

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.




-------------------------------------------------------
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