1. 09 11月, 2012 1 次提交
  2. 03 10月, 2012 1 次提交
  3. 13 9月, 2012 2 次提交
  4. 07 9月, 2012 2 次提交
  5. 25 7月, 2012 1 次提交
    • I
      drm: track dev_mapping in more robust and flexible way · 949c4a34
      Ilija Hadzic 提交于
      Setting dev_mapping (pointer to the address_space structure
      used for memory mappings) to the address_space of the first
      opener's inode and then failing if other openers come in
      through a different inode has a few restrictions that are
      eliminated by this patch.
      
      If we already have valid dev_mapping and we spot an opener
      with different i_node, we force its i_mapping pointer to the
      already established address_space structure (first opener's
      inode). This will make all mappings from drm device hang off
      the same address_space object.
      
      Some benefits (things that now work and didn't work
      before) of this patch are:
      
       * user space can mknod and use any number of device
         nodes and they will all work fine as long as the major
         device number is that of the drm module.
       * user space can even remove the first opener's device
         nodes and mknod the new one and the applications and
         windowing system will still work.
       * GPU drivers can safely assume that dev->dev_mapping is
         correct address_space and just blindly copy it
         into their (private) bdev.dev_mapping
      
      For reference, some discussion that lead to this patch can
      be found here:
      
      http://lists.freedesktop.org/archives/dri-devel/2012-April/022283.htmlSigned-off-by: NIlija Hadzic <ihadzic@research.bell-labs.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      949c4a34
  6. 20 7月, 2012 1 次提交
  7. 17 2月, 2012 1 次提交
    • D
      drm: move pci bus master enable into driver. · 466e69b8
      Dave Airlie 提交于
      The current enabling of bus mastering in the drm midlayer allows a large
      race condition under kexec. When a kexec'ed kernel re-enables bus mastering
      for the GPU, previously setup dma blocks may cause writes to random pieces
      of memory. On radeon the writeback mechanism can cause these sorts of issues.
      
      This patch doesn't fix the problem, but it moves the bus master enable under
      the individual drivers control so they can move enabling it until later in
      their load cycle and close the race.
      
      Fix for radeon kms driver will be in a follow-up patch.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      466e69b8
  8. 13 2月, 2012 3 次提交
  9. 06 2月, 2012 1 次提交
  10. 11 11月, 2011 1 次提交
    • A
      drm: Make the per-driver file_operations struct const · e08e96de
      Arjan van de Ven 提交于
      From fdf1fdebaa00f81de18c227f32f8074c8b352d50 Mon Sep 17 00:00:00 2001
      From: Arjan van de Ven <arjan@linux.intel.com>
      Date: Sun, 30 Oct 2011 19:06:07 -0700
      Subject: [PATCH] drm: Make the per-driver file_operations struct const
      
      The DRM layer keeps a copy of struct file_operations inside its
      big driver struct... which prevents it from being consistent and static.
      For consistency (and the general security objective of having such things
      static), it's desirable to get this fixed.
      
      This patch splits out the file_operations field to its own struct,
      which is then "static const", and just stick a pointer to this into
      the driver struct, making it more consistent with how the rest of the
      kernel does this.
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      e08e96de
  11. 02 11月, 2011 1 次提交
    • T
      vmwgfx: Reinstate the update_layout ioctl · cd2b89e7
      Thomas Hellstrom 提交于
      We need to redefine a connector as "connected" if it matches a window
      in the host preferred GUI layout.
      Otherwise "smart" window managers would turn on Xorg outputs that we don't
      want to be on.
      
      This reinstates the update_layout and adds the following information to
      the modesetting system.
      a) Connection status <-> Equivalent to real hardware connection status
      b) Preferred mode <-> Equivalent to real hardware reading EDID
      c) Host window position <-> Equivalent to a real hardware scanout address
      dynamic register.
      
      It should be noted that there is no assumption here about what should be
      displayed and where. Only how to access the host windows.
      
      This also bumps minor to signal availability of the new IOCTL.
      
      Based on code originally written by Jakob Bornecrantz
      Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      cd2b89e7
  12. 01 11月, 2011 1 次提交
  13. 28 10月, 2011 1 次提交
  14. 18 10月, 2011 1 次提交
  15. 10 10月, 2011 2 次提交
  16. 05 10月, 2011 6 次提交
  17. 06 9月, 2011 6 次提交
  18. 01 9月, 2011 4 次提交
  19. 23 2月, 2011 2 次提交
  20. 07 2月, 2011 1 次提交
  21. 27 10月, 2010 1 次提交