1. 28 4月, 2008 1 次提交
    • H
      atmel_lcdfb: don't initialize a pre-allocated framebuffer · 01d3a5e7
      Haavard Skinnemoen 提交于
      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: NHaavard 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: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      01d3a5e7
  2. 07 2月, 2008 2 次提交
  3. 26 1月, 2008 1 次提交
  4. 15 1月, 2008 1 次提交
  5. 30 11月, 2007 1 次提交
  6. 22 7月, 2007 2 次提交
  7. 11 5月, 2007 1 次提交