1. 26 11月, 2010 2 次提交
  2. 09 11月, 2010 1 次提交
  3. 05 8月, 2010 1 次提交
  4. 04 8月, 2010 1 次提交
  5. 24 5月, 2010 1 次提交
  6. 14 3月, 2010 1 次提交
  7. 13 3月, 2010 1 次提交
  8. 16 12月, 2009 1 次提交
  9. 09 12月, 2009 1 次提交
    • T
      OMAP: Add VRAM manager · afedec18
      Tomi Valkeinen 提交于
      Add a Video RAM manager for OMAP 2 and 3 platforms. VRAM manager is used
      to allocate large continuous blocks of SDRAM or SRAM. The features VRAM
      manager has that are missing from dma_alloc_* functions are:
      
      - Support for OMAP2's SRAM
      - Allocate without ioremapping
      - Allocate at defined physical addresses
      - Allows larger VRAM area and larger allocations
      
      The upcoming DSS2 uses VRAM manager.
      
      VRAM area size can be defined in kernel config, board file or with
      kernel boot parameters. Board file definition overrides kernel config,
      and boot parameter overrides kernel config and board file.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
      afedec18
  10. 23 9月, 2009 3 次提交
  11. 13 6月, 2009 1 次提交
  12. 07 5月, 2009 1 次提交
  13. 01 4月, 2009 2 次提交
  14. 27 2月, 2009 2 次提交
  15. 10 2月, 2009 1 次提交
  16. 22 1月, 2009 1 次提交
  17. 13 1月, 2009 2 次提交
  18. 07 11月, 2008 1 次提交
  19. 17 10月, 2008 3 次提交
  20. 27 8月, 2008 1 次提交
  21. 29 7月, 2008 1 次提交
  22. 25 7月, 2008 4 次提交
  23. 28 4月, 2008 2 次提交
    • J
      fbdev: platforming metronomefb and am200epd · 03c33a4f
      Jaya Kumar 提交于
      This patch splits metronomefb into the platform independent metronomefb and
      the platform dependent am200epd.
      Signed-off-by: NJaya Kumar <jayakumar.lkml@gmail.com>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      03c33a4f
    • Y
      fbdev: powerpc: driver for Freescale 8610 and 5121 DIU · 9b53a9e2
      York Sun 提交于
      The following features are supported:
      plane 0 works as a regular frame buffer, can be accessed by /dev/fb0
      plane 1 has two AOIs (area of interest), can be accessed by /dev/fb1 and /dev/fb2
      plane 2 has two AOIs, can be accessed by /dev/fb3 and /dev/fb4
      Special ioctls support AOIs
      
      All /dev/fb* can be used as regular frame buffer devices, except hardware
      change can only be made through /dev/fb0.  Changing pixel clock has no effect
      on other fbs.
      
      Limitation of usage of AOIs:
      AOIs on the same plane can not be horizonally overlapped
      AOIs have horizonal order, i.e. AOI0 should be always on top of AOI1
      AOIs can not beyond phisical display area. Application should check AOI geometry
      before changing physical resolution on /dev/fb0
      
      required command line parameters to preallocate memory for frame buffer diufb.
      
      optional command line parameters to set modes and monitor
      video=fslfb:[resolution][,bpp][,monitor]
      Syntax:
      
      Resolution
      xres x yres-bpp@refresh_rate, the -bpp and @refresh_rate are optional
      eg, 1024x768, 1280x1024, 1280x1024-32, 1280x1024@60, 1280x1024-32@60, 1280x480-32@60
      
      Bpp
      bpp=32, bpp=24, or bpp=16
      
      Monitor
      monitor=0, monitor=1, monitor=2
      0 is DVI
      1 is Single link LVDS
      2 is Double link LVDS
      
      Note: switching monitor is a board feather, not DIU feather. MPC8610HPCD has three
      monitor ports to swtich to. MPC5121ADS doesn't have additional monitor port. So switching
      monirot port for MPC5121ADS has no effect.
      
      If compiled as a module, it takes pamameters mode, bpp, monitor with the same syntax above.
      Signed-off-by: NYork Sun <yorksun@freescale.com>
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9b53a9e2
  24. 25 4月, 2008 1 次提交
  25. 20 3月, 2008 1 次提交
  26. 11 3月, 2008 1 次提交
  27. 30 11月, 2007 1 次提交
    • H
      x86_64 EFI boot support: EFI frame buffer driver · 7c83172b
      Huang, Ying 提交于
      This patch adds Graphics Output Protocol support to the kernel.  UEFI2.0 spec
      deprecates Universal Graphics Adapter (UGA) protocol and only Graphics Output
      Protocol (GOP) is produced.  Therefore, the boot loader needs to query the
      UEFI firmware with appropriate Output Protocol and pass the video information
      to the kernel.  As a result of GOP protocol, an EFI framebuffer driver is
      needed for displaying console messages.  The patch adds a EFI framebuffer
      driver.  The EFI frame buffer driver in this patch is based on the Intel Mac
      framebuffer driver.
      
      The ELILO bootloader takes care of passing the video information as
      appropriate for EFI firmware.
      
      The framebuffer driver has been tested in i386 kernel and x86_64 kernel on EFI
      platform.
      Signed-off-by: NChandramouli Narayanan <mouli@linux.intel.com>
      Signed-off-by: NHuang Ying <ying.huang@intel.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Andi Kleen <ak@suse.de>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7c83172b
  28. 17 10月, 2007 1 次提交