James Simmons wrote:

If this is true then it would be better if we have the below logic.

struct vc_data --> native driver layer --> fbdev.

instead of save/restore the var for each VC.
 

I don't mean save as in record the current hardware state.  I mean save 
as in remember the last mode the user had active on the console before a 
graphics app starts.  This only has to be done 1) on boot and 2) after 
running fbset or calling VT_RESIZE.

Once we get the users mode db into the kernel then we only need to 
remember the generic stuff (x, y, Hz, bpp) per vt as the user will have 
the ability to map:

(x, y, Hz, bpp) -> (exact timing options)

Either way, regardless if we remember a per vt var or (x, y, Hz, bpp), I 
still would like the vt/fbcon to reset the the last mode on switch from 
KD_GRAPHICS to KD_TEXT.

John




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click