Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

[Sven Luther <sven.luther@wanadoo.fr>]

On Mon, Oct 31, 2005 at 01:34:49AM +0100, Erik van Konijnenburg wrote:
> Just a quick note that there's nothing in yaird 0.0.11 tarball
> to support vga=...
> 
> This will probably require an extra module in the config file, vesafb or
> so, plus an equivalence to a kernel define (I seem to remember modular framebuffers
> are broken on some architectures, so it may be compiled in on some machines).
> 
> Perhaps also an 'optional' variant of the MODULE keyword, that will not complain
> if the module is not compiled in and not a module.

Well, vesafb is now builtin (don't know how you can detect builtin vs
modules), the missing one was fbcon, which could either be builtin in the
kernel, or added always for x86/amd64 machines. On powerpc it is builtin.

Now i have a question concerning fbdevs is the following. On powerpc, since
there is no vga text mode in most cases, we have most framebuffer devices
builtin, which is a waste of space, since only one of them is usually used.

One of the interests of initramfs is that it allows to load modules much
earlier than what was possible previously, and altough this may not be as
early as when the modules are builtin, it would be interesting to make them
modular, and have yaird load them as the first step in the modules to be
loaded.

What do you think about this plan ? This would allow also for real fbdev's to
be used in the x86 world, instead of vesafb and co.

It would be wonderful if you could comment on this ? 

Friendly,

Sven Luther