Messages in this thread |  | | Date | Tue, 20 Jun 2006 10:04:06 -0400 | | From | "Jon Smirl" <> | | Subject | Re: [PATCH 3/9] VT binding: Make VT binding a Kconfig option |
| |
On 6/20/06, Antonino A. Daplas <adaplas@gmail.com> wrote: > All fbdev drivers have a startup mode that should always be valid. All > fbcon does is enable that mode. > > You can load nvidiafb like this instead: > > modprobe nvidiafb mode_option=1024x768@60
Good idea, it didn't occur to me to use the module parameters. Doing it that way I can see what I am doing instead of typing blind.
> > How does vbetool save state? > > vbetool basically calls an int10 function that saves the state. This > function is unique per video BIOS, ie you cannot use the state file in > another machine even if the graphics chipset is the same. > > > Could VGAcon do whatever vbetool is doing? > > No it can't. Once the card is in graphics mode, vgacon cannot go to > text mode on its own. It has to know how to write to other VGA > registers which are unique per hardware.
Might be a good place for a little call_usermodehelper example. VGAcon could try calling vbetool to save it's state and restore it. GregKH told me that the class firmware loader code was the place to start.
-- Jon Smirl jonsmirl@gmail.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |