]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
atmel_lcdfb: don't initialize a pre-allocated framebuffer
authorHaavard Skinnemoen <hskinnemoen@atmel.com>
Mon, 28 Apr 2008 09:15:19 +0000 (02:15 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Mon, 28 Apr 2008 15:58:38 +0000 (08:58 -0700)
commit01d3a5e7fab7732cfc5d5d4533e9378ea435295a
tree3bf547f6eaeec9c69f78e1b70cb66f67399d1abd
parent20e061fb750d36ec0ffcb2e44ed7dafa9018223b
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>
arch/arm/mach-at91/at91sam9261_devices.c
arch/arm/mach-at91/at91sam9rl_devices.c
arch/avr32/kernel/setup.c
drivers/video/atmel_lcdfb.c