Haavard Skinnemoen 01d3a5e7fa atmel_lcdfb: don't initialize a pre-allocated framebuffer ... If the user specified a fixed framebuffer address on the command line, it may have been initialized already with a splash image or something, so we shouldn't clear it. Therefore, we should only initialize the framebuffer if we allocated it ourselves. This patch also updates the AVR32 setup code to clear the framebuffer if it allocated it itself, i.e. the user didn't provide a fixed address or the reservation failed. I've updated the at91 platform code as well so that it initializes the framebuffer if it is located in SRAM, but I haven't tested that it actually works. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com> Cc: "Antonino A. Daplas" <adaplas@pol.net> Cc: Nicolas FERRE <nicolas.ferre@rfo.atmel.com> Cc: Andrew Victor <andrew@sanpeople.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2008-04-28 08:58:38 -07:00
..
boards	avr32: Use correct config symbol in atstk1004 board code	2008-02-13 14:44:06 +01:00
boot	…
configs	…
kernel	atmel_lcdfb: don't initialize a pre-allocated framebuffer	2008-04-28 08:58:38 -07:00
lib	…
mach-at32ap	avr32: Implement set_rate(), set_parent() and mode() for pll1	2008-04-19 20:40:08 -04:00
mm	avr32: Remove two unused #defines from mm/init.c	2008-04-19 20:40:08 -04:00
oprofile	avr32: Delete mostly unused header asm/intc.h	2008-04-19 20:40:07 -04:00
Kconfig	avr32: Generic clockevents support	2008-04-19 20:40:08 -04:00
Kconfig.debug	…
Makefile	…