On Fri, Oct 25, 2013 at 09:56:51AM +0200, Andre Heider wrote: > On Thu, Oct 24, 2013 at 10:23:40PM +0200, Andre Heider wrote: > > This set adds a common simple framebuffer driver for platforms which choose > > to support it. RPi support is part of this set. > > > > The driver serves two functions: > > * a framebuffer driver for barebox > > * pass an active framebuffer configuration to a loaded kernel > > Pondering over this again, this is probably the wrong approach. There's > no need for a distinct simplefb driver for barebox, bcm2835 can have its own > fb driver like everyone else, Right, > and the simplefb configuration for the > kernel can be done independent of the fb barebox driver in use... Yes. I think we should have an option whether a framebuffer should be kept enabled when starting a kernel. If yes, then we have to resever the memory for the framebuffer and create the simplefb node. If not, we have to disable the framebuffer. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
