On 6/19/06, Antonino A. Daplas <[email protected]> wrote:
Jon Smirl wrote:
> I gave this patch a try and it seems to work. I say seems because I
> could not get the nvidiafb driver to set a usable mode after it was
> bound/unbound.
What do you mean by this? You mean that you cannot restore vgacon?
If that's the case, then yes, that is perfectly understandable as
nvidiafb does not restore VGA to text mode.
modprobe fbcon
modprobe nvidiafb
Display is messed up.
I used to fix this by switching to X and back but the nvidia X driver
won't build on the mm kernel. I can try again and write a script to
echo a mode into sysfs after the modprobe.
When fbcon first gets a new fbdev driver registered with it, should it
pick one of the modes is supports and set it automatically?
or would it be better for each driver to set in a
> default mode that it understands when it gets control? The fbdev
> driver should not set a mode when it loads, but that doesn't mean
> fbcon can't set one when it is activated. Similarly VGAcon would set
> the mode (and load its fonts) when it regains control.
The problem with vgacon setting its own mode is that it does not know
anything about the hardware. So VGA text mode will need to rely on
a secondary program to set the mode (whether it's vbetool, another
fb driver, or X does not matter).
How does vbetool save state? Could VGAcon do whatever vbetool is doing?
--
Jon Smirl
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
