Re: [Linux-fbdev-devel] 2 pm3fb questions/problesm ...

[James S. <jsi...@tr...>]

> Look at matroxfb's use of currcon = -1 && currcon = -2 ;-) If you set
> currcon to -1 and invoke set_var with currcon == -2, then, if your _set_var
> is correct, disp structure will get initialized, but you'll not touch
> hardware, as background VT resolution just changed. Of course if you
> are in ruby tree, you are lost...

Well the design goals are a bit different for 2.5.X. First you can run
fbdev with fbcon. This makes for a very different handling. Another thing
I have done is when you insmod a fbdev driver it doesn't change the video.
It leaves the hardware as is. Its when you open /dev/fb and do a
FBIOPUT_VSCREENINFO the video mode really changes. So if your hardware is
a vga state then you could save the state in fb_open. This is actually
very nice since not all video cards have a vga state so fb_open being a
optional function is perfect for this. Then for fb_close you can set the
state back to vga text mode.  

> No, vc_resize has completely different symptoms. vgacon problem
> symptoms are either completely white screen (if driver disabled
> VGA apperture), or complete garbage (if driver changed VGA layout).

Hum. I guess the tdfx driver handles this correctly already.