On Mon, 3 Aug 2009, Sascha Hauer wrote: > On Fri, Jul 31, 2009 at 01:42:35PM -0500, Bill Gatliff wrote: > > Could your bootloader pre-initialize the graphics hardware to the same > > mode that the Linux driver will ultimately select, and then throw up a > > static graphic? That would give you some output until the driver itself > > comes online. > > I implemented exactly this for the i.MX framebuffer last week. It works > by looking at the controllers physical screen start address, ioremapping > this address and copying the content to the newly allocated framebuffer. > Currently the driver still reinitilializes the controller with exactly > the same values. We could skip this initialization step depending on a > imxfb.preinitialized=1 command line parameter and read back > resolution/depth from the device in order to fill the fb_info struct. > > This approach works good, I just wonder how acceptable it is for > mainline. If the actual frame buffer driver doesn't do much after initialization, we already have (at least) two similar drivers in the kernel: vesafb and offb. Both rely on firmware (PC BIOS vs. Open Firmware) to initialize the graphics mode. Feel free to unify all of this into `staticfb.c'... With kind regards, Geert Uytterhoeven Software Architect Techsoft Centre Technology and Software Centre Europe The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium Phone: +32 (0)2 700 8453 Fax: +32 (0)2 700 8622 E-mail: Geert.Uytterhoeven@xxxxxxxxxxx Internet: http://www.sony-europe.com/ A division of Sony Europe (Belgium) N.V. VAT BE 0413.825.160 · RPR Brussels Fortis · BIC GEBABEBB · IBAN BE41293037680010 -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
