1. 24 1月, 2013 2 次提交
  2. 10 12月, 2012 1 次提交
  3. 29 9月, 2012 1 次提交
  4. 23 9月, 2012 1 次提交
  5. 30 4月, 2012 3 次提交
  6. 15 2月, 2012 1 次提交
  7. 13 2月, 2012 1 次提交
  8. 12 11月, 2011 1 次提交
  9. 06 9月, 2011 1 次提交
  10. 13 7月, 2011 1 次提交
  11. 23 5月, 2011 1 次提交
  12. 17 3月, 2011 1 次提交
  13. 08 3月, 2011 1 次提交
    • S
      video: Add i.MX23/28 framebuffer driver · f0a523b5
      Sascha Hauer 提交于
      changes since v2:
      
      - use v3 and v4 for specifying the ip version instead of i.MX23/28.
        This is a better namespace when future versions are added.
      - rename mach/fb.h to mach/mxsfb.h
      
      changes since v1:
      - Add a LCDC_ prefix to the register names.
      - use set/clear registers where appropriate
      - protect call to mxsfb_disable_controller() in mxsfb_remove()
        with a (host->enabled) as suggested by Lothar Wassmann
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      Acked-by: NShawn Guo <shawn.guo@freescale.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: linux-fbdev@vger.kernel.org
      f0a523b5
  14. 16 12月, 2010 1 次提交
    • D
      video: add driver for PXA3xx 2D graphics accelerator · 364dbdf3
      Daniel Mack 提交于
      This adds a driver for the the 2D graphics accelerator found on PXA3xx
      processors. Only resource mapping, interrupt handling and a simple ioctl
      handler is done by the kernel part, the rest of the logic is implemented
      in DirectFB userspace.
      
      Graphic applications greatly benefit for line drawing, blend, and
      rectangle and triangle filling operations.
      
      Benchmarks done on a PXA303 using the df_dok benchmarking tool follow,
      where the value in square brackets show the CPU usage during that test.
      
      Without accelerator (benchmarking 256x252 on 480x262 RGB16 (16bit)):
      
        Anti-aliased Text                              3.016 secs (   65.649 KChars/sec) [ 99.6%]
        Fill Rectangle                                 3.021 secs (  175.107 MPixel/sec) [ 98.0%]
        Fill Rectangle (blend)                         3.582 secs (    3.602 MPixel/sec) [ 99.7%]
        Fill Rectangles [10]                           3.177 secs (  182.753 MPixel/sec) [ 98.1%]
        Fill Rectangles [10] (blend)                  18.020 secs (    3.580 MPixel/sec) [ 98.7%]
        Fill Spans                                     3.019 secs (  145.306 MPixel/sec) [ 98.0%]
        Fill Spans (blend)                             3.616 secs (    3.568 MPixel/sec) [ 99.4%]
        Blit                                           3.074 secs (   39.874 MPixel/sec) [ 98.0%]
        Blit 180                                       3.020 secs (   32.042 MPixel/sec) [ 98.0%]
        Blit with format conversion                    3.005 secs (   19.321 MPixel/sec) [ 99.6%]
        Blit from 32bit (blend)                        4.792 secs (    2.692 MPixel/sec) [ 98.7%]
      
      With accelerator:
      
        Anti-aliased Text                              3.056 secs (*  36.518 KChars/sec) [ 21.3%]
        Fill Rectangle                                 3.015 secs (* 115.543 MPixel/sec) [  8.9%]
        Fill Rectangle (blend)                         3.180 secs (*  20.286 MPixel/sec) [  1.8%]
        Fill Rectangles [10]                           3.251 secs (* 119.062 MPixel/sec) [  1.2%]
        Fill Rectangles [10] (blend)                   6.293 secs (*  20.502 MPixel/sec) [  0.3%]
        Fill Spans                                     3.051 secs (*  97.264 MPixel/sec) [ 35.7%]
        Fill Spans (blend)                             3.377 secs (*  15.282 MPixel/sec) [ 17.8%]
        Blit                                           3.046 secs (*  27.533 MPixel/sec) [  2.6%]
        Blit 180                                       3.098 secs (*  27.070 MPixel/sec) [  2.2%]
        Blit with format conversion                    3.131 secs (*  39.148 MPixel/sec) [  2.8%]
        Blit from 32bit (blend)                        3.346 secs (*  11.568 MPixel/sec) [  0.8%]
      Signed-off-by: NDaniel Mack <daniel@caiaq.de>
      Tested-by: NSven Neumann <s.neumann@raumfeld.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Denis Oliver Kropp <dok@directfb.org>
      Cc: Sven Neumann <s.neumann@raumfeld.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Signed-off-by: NEric Miao <eric.y.miao@gmail.com>
      364dbdf3
  15. 26 11月, 2010 2 次提交
  16. 16 11月, 2010 1 次提交
  17. 09 11月, 2010 1 次提交
  18. 05 8月, 2010 1 次提交
  19. 04 8月, 2010 1 次提交
  20. 24 5月, 2010 1 次提交
  21. 14 3月, 2010 1 次提交
  22. 13 3月, 2010 1 次提交
  23. 16 12月, 2009 1 次提交
  24. 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
  25. 23 9月, 2009 3 次提交
  26. 13 6月, 2009 1 次提交
  27. 07 5月, 2009 1 次提交
  28. 01 4月, 2009 2 次提交
  29. 27 2月, 2009 2 次提交
  30. 10 2月, 2009 1 次提交
  31. 22 1月, 2009 1 次提交
  32. 13 1月, 2009 1 次提交