Messages in this thread | | | Date | Sat, 16 Oct 2004 14:21:57 +0200 | From | Gerd Knorr <> | Subject | Re: Generic VESA framebuffer driver and Video card BOOT? |
| |
On Sat, Oct 16, 2004 at 02:55:44AM +0200, Andi Kleen wrote: > On Fri, Oct 15, 2004 at 05:37:09PM +0200, Gerd Knorr wrote: > > Andi Kleen <ak@muc.de> writes: > > > > > The problem is that this would imply that the console would only > > > work after user space is running. Even with initrd that's quite late. > > > > klibc + initramfs + early userspace? > > That's still quite late in my book (by my perspective may be skewed > a bit from low level architecture hacking)
Framebuffer console _is_ quite late compared vgacon or even early_printk, all the basic stuff is already up+running at that point.
I think initialization in early userspace can be done in a way that it wouldn't delay the initial console display compared to todays vesafb (or any other framebuffer). Of course you need some way to turn it off and use vgacon instead ...
Gerd
-- return -ENOSIG; - 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/
| |