1. 06 8月, 2010 1 次提交
  2. 05 8月, 2010 1 次提交
  3. 02 8月, 2010 1 次提交
  4. 05 6月, 2010 1 次提交
  5. 08 5月, 2010 2 次提交
    • F
      viafb: make procfs entries optional · 2b78a963
      Florian Tobias Schandinat 提交于
      viafb: make procfs entries optional
      
      This patch adds a config option to enable procfs entries for direct
      hardware access. This was the old behaviour but the option defaults
      to no as this is really ugly and should not be needed if the driver
      works correct (and if it doesn't, it needs to be fixed).
      That stuff is really something that should
      - not be needed at all (the driver should be capable of doing it)
      - not be there (debugfs would be better for such things)
      So add this option just for backwards compatiblity.
      Signed-off-by: NFlorian Tobias Schandinat <FlorianSchandinat@gmx.de>
      2b78a963
    • J
      viafb: add a driver for GPIO lines · 7e0de022
      Jonathan Corbet 提交于
      This is a simple gpiolib driver giving access to the GPIO lines in the
      VIA framebuffer system.  A simple mechanism exists for switching lines
      between GPIO and I2C, but it's only compile-time for now.
      
      Cc: ScottFang@viatech.com.cn
      Cc: JosephChan@via.com.tw
      Cc: Harald Welte <laforge@gnumonks.org>
      Acked-by: NFlorian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      7e0de022
  6. 23 4月, 2010 1 次提交
  7. 17 3月, 2010 1 次提交
  8. 15 3月, 2010 1 次提交
  9. 14 3月, 2010 1 次提交
  10. 13 3月, 2010 2 次提交
  11. 18 2月, 2010 1 次提交
  12. 16 12月, 2009 1 次提交
  13. 11 12月, 2009 1 次提交
  14. 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
  15. 16 11月, 2009 1 次提交
  16. 12 11月, 2009 1 次提交
  17. 09 10月, 2009 1 次提交
  18. 23 9月, 2009 4 次提交
  19. 10 9月, 2009 1 次提交
    • B
      PCI/GPU: implement VGA arbitration on Linux · deb2d2ec
      Benjamin Herrenschmidt 提交于
      Background:
      Graphic devices are accessed through ranges in I/O or memory space. While most
      modern devices allow relocation of such ranges, some "Legacy" VGA devices
      implemented on PCI will typically have the same "hard-decoded" addresses as
      they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994
      Standard for Boot (Initialization Configuration) Firmware Revision 2.1"
      Section 7, Legacy Devices.
      
      The Resource Access Control (RAC) module inside the X server currently does
      the task of arbitration when more than one legacy device co-exists on the same
      machine. But the problem happens when these devices are trying to be accessed
      by different userspace clients (e.g. two server in parallel). Their address
      assignments conflict. Therefore an arbitration scheme _outside_ of the X
      server is needed to control the sharing of these resources. This document
      introduces the operation of the VGA arbiter implemented for Linux kernel.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NTiago Vignatti <tiago.vignatti@nokia.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      deb2d2ec
  20. 23 7月, 2009 1 次提交
  21. 15 7月, 2009 1 次提交
  22. 07 7月, 2009 1 次提交
    • P
      video: sh_mobile_lcdcfb: depends on HAVE_CLK. · 727dc3fd
      Paul Mundt 提交于
      This deifdefs the driver and adds an explicit HAVE_CLK dependency. Given
      that all SH platforms provide it, there is no reason to keep this as an
      ifdef. Other architectures that implement support for this driver will
      already have to provide clock framework support for timers and so on
      already, so adding this as an additional dependency is not terribly
      probematic.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      727dc3fd
  23. 03 7月, 2009 1 次提交
  24. 27 6月, 2009 1 次提交
  25. 20 6月, 2009 1 次提交
  26. 17 6月, 2009 1 次提交
    • J
      mb862xxfb: restrict compliation of platform driver to PPC · 336e747e
      Julian Calaby 提交于
      The OpenFirmware part of this driver is uncompilable on SPARC due to it's
      dependance on several PPC specific functions.
      
      Restricting this to PPC to prevent these build errors:
        CC      drivers/video/mb862xx/mb862xxfb.o
      drivers/video/mb862xx/mb862xxfb.c: In function 'of_platform_mb862xx_probe':
      drivers/video/mb862xx/mb862xxfb.c:559: error: implicit declaration of function 'of_address_to_resource'
      drivers/video/mb862xx/mb862xxfb.c:575: error: 'NO_IRQ' undeclared (first use in this function)
      drivers/video/mb862xx/mb862xxfb.c:575: error: (Each undeclared identifier is reported only once
      drivers/video/mb862xx/mb862xxfb.c:575: error: for each function it appears in.)
      
      This was found using randconfig builds.
      Signed-off-by: NJulian Calaby <julian.calaby@gmail.com>
      Signed-off-by: NAnatolij Gustschin <agust@denx.de>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Anatolij Gustschin <agust@denx.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Michal Simek <monstr@monstr.eu>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      336e747e
  27. 13 6月, 2009 1 次提交
  28. 21 5月, 2009 1 次提交
  29. 13 5月, 2009 1 次提交
  30. 07 5月, 2009 1 次提交
  31. 07 4月, 2009 1 次提交
  32. 01 4月, 2009 3 次提交
  33. 13 3月, 2009 1 次提交