> >>It is possible to get the vesafb on boottime. Because, there is no >>longer a bootsplash :( > > > >>Stefan means, I need an CLE266 fb kerneldriver and it should work, but >>via offered a kernel modul, only > > > Where can that module be found?
The sources for CLE266 Unichrome integrated graphics Kernel 2.4.x and 2.6.x http://www.viaarena.com/Driver/linux-fbdev-kernel-src_20050726.tgz There are some other sources available for different chipsets. You won't easily be able to use the vesa > framebuffer, because linuxbios always sets a text mode instead of a > graphics mode (and the vesafb driver does bios calls in some > circumstances, at least on x86, but that can easily be patched) > > LinuxBIOS should offer a way of getting the machine right into graphics > mode and provide the framebuffer address and depth in the linuxbios > table. ;) I say, drop text mode (as an option) and go framebuffer. This > allows using two graphics cards on the bios level since we don't need to > cope with concurrent mapping of legacy bios areas anymore. Great idea :D > > Stefan > > -- LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
