1. 21 9月, 2012 2 次提交
  2. 13 8月, 2012 1 次提交
  3. 20 7月, 2012 1 次提交
  4. 17 5月, 2012 2 次提交
  5. 03 5月, 2012 1 次提交
  6. 01 5月, 2012 2 次提交
  7. 24 4月, 2012 1 次提交
  8. 21 3月, 2012 1 次提交
  9. 07 3月, 2012 1 次提交
  10. 25 1月, 2012 3 次提交
  11. 16 11月, 2011 1 次提交
  12. 02 11月, 2011 4 次提交
  13. 10 10月, 2011 1 次提交
  14. 15 8月, 2011 1 次提交
  15. 04 8月, 2011 1 次提交
    • T
      drm/radeon: Extended DDC Probing for Connectors with Improperly Wired DDC... · e384fab8
      Thomas Reim 提交于
      drm/radeon: Extended DDC Probing for Connectors with Improperly Wired DDC Lines (here: Asus M2A-VM HDMI)
      
          Some integrated ATI Radeon chipset implementations with add-on HDMI card
          (e. g. Asus M2A-VM HDMI) indicate the availability of a DDC even
          when the add-on card is not plugged in or HDMI is disabled in BIOS setup.
          In this case, drm_get_edid() and drm_edid_block_valid() periodically
          dump data and kernel errors into system log files and onto terminals.
          For these connectors DDC probing is extended by a check for a correct
          EDID header. Only in case a valid EDID header is also found, the
          (HDMI or DVI) connector will be used by the Radeon driver. This prevents
          the kernel driver from useless flooding of logs and terminal sessions with
          EDID dumps and error messages.
          This patch adds a flag 'requires_extended_probe' to the radeon_connector
          structure. In function radeon_connector_needs_extended_probe() this flag
          can be set on a chipset family/vendor/connector type specific basis.
          In addition, function radeon_ddc_probe() has been adapted to perform
          extended DDC probing if required by the connector's flag.
          Requires function drm_edid_header_is_valid() in DRM module provided by
          [PATCH] drm: Separate EDID Header Check from EDID Block Check.
      
          Tested for kernel 2.6.35, 2.6.38 and 3.0 on Asus M2A-VM HDMI board
      
          BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=668196
          BugLink: http://bugs.launchpad.net/bugs/7228066
      
      Cc: <stable@kernel.org>
      Signed-off-by: NThomas Reim <reimth@gmail.com>
      Reviewed-by: NAlex Deucher <alexdeucher@gmail.com>
      Acked-by: NStephen Michaels <Stephen.Micheals@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      e384fab8
  16. 17 6月, 2011 2 次提交
  17. 24 5月, 2011 1 次提交
  18. 20 5月, 2011 6 次提交
  19. 24 3月, 2011 1 次提交
    • A
      drm/radeon/kms: fix hardcoded EDID handling · fafcf94e
      Alex Deucher 提交于
      On some servers there is a hardcoded EDID provided
      in the vbios so that the driver will always see a
      display connected even if something like a KVM
      prevents traditional means like DDC or load
      detection from working properly.  Also most
      server boards with DVI are not actually DVI, but
      DVO connected to a virtual KVM service processor.
      If we fail to detect a monitor via DDC or load
      detection and a hardcoded EDID is available, use
      it.
      
      Additionally, when using the hardcoded EDID, use
      a copy of it rather than the actual one stored
      in the driver as the detect() and get_modes()
      functions may free it if DDC is successful.
      
      This fixes the virtual KVM on several internal
      servers.
      Signed-off-by: NAlex Deucher <alexdeucher@gmail.com>
      Cc: stable@kernel.org
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      fafcf94e
  20. 23 3月, 2011 1 次提交
  21. 14 2月, 2011 1 次提交
  22. 07 2月, 2011 1 次提交
    • D
      drm: dumb scanout create/mmap for intel/radeon (v3) · ff72145b
      Dave Airlie 提交于
      This is just an idea that might or might not be a good idea,
      it basically adds two ioctls to create a dumb and map a dumb buffer
      suitable for scanout. The handle can be passed to the KMS ioctls to create
      a framebuffer.
      
      It looks to me like it would be useful in the following cases:
      a) in development drivers - we can always provide a shadowfb fallback.
      b) libkms users - we can clean up libkms a lot and avoid linking
      to libdrm_*.
      c) plymouth via libkms is a lot easier.
      
      Userspace bits would be just calls + mmaps. We could probably
      mark these handles somehow as not being suitable for acceleartion
      so as top stop people who are dumber than dumb.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      ff72145b
  23. 02 2月, 2011 1 次提交
  24. 07 1月, 2011 1 次提交
  25. 21 12月, 2010 1 次提交
  26. 22 11月, 2010 1 次提交