1. 13 4月, 2011 4 次提交
  2. 09 4月, 2011 4 次提交
  3. 04 4月, 2011 2 次提交
  4. 01 4月, 2011 1 次提交
  5. 31 3月, 2011 1 次提交
  6. 24 3月, 2011 2 次提交
    • T
      drm radeon: Return -EINVAL on wrong pm sysfs access · 1783e4bf
      Thomas Renninger 提交于
      Throw an error if someone tries to fill this with
      wrong data, instead of simply ignoring the input.
      Now you get:
      
      echo hello >/sys/../power_method
      -bash: echo: write error: Invalid argument
      Signed-off-by: NThomas Renninger <trenn@suse.de>
      CC: Alexander.Deucher@amd.com
      CC: dri-devel@lists.freedesktop.org
      Reviewed-by: NAlex Deucher <alexdeucher@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      1783e4bf
    • 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
  7. 23 3月, 2011 2 次提交
  8. 22 3月, 2011 1 次提交
  9. 17 3月, 2011 3 次提交
  10. 16 3月, 2011 1 次提交
  11. 14 3月, 2011 1 次提交
    • D
      drm/radeon: fix problem with changing active VRAM size. (v2) · 53595338
      Dave Airlie 提交于
      So we used to use lpfn directly to restrict VRAM when we couldn't
      access the unmappable area, however this was removed in
      93225b0d as it also restricted
      the gtt placements. However it was only later noticed that this
      broke on some hw.
      
      This removes the active_vram_size, and just explicitly sets it
      when it changes, TTM/drm_mm will always use the real_vram_size,
      and the active vram size will change the TTM size used for lpfn
      setting.
      
      We should re-work the fpfn/lpfn to per-placement at some point
      I suspect, but that is too late for this kernel.
      
      Hopefully this addresses:
      https://bugs.freedesktop.org/show_bug.cgi?id=35254
      
      v2: fix reported useful VRAM size to userspace to be correct.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      53595338
  12. 13 3月, 2011 1 次提交
  13. 11 3月, 2011 1 次提交
  14. 03 3月, 2011 15 次提交
  15. 01 3月, 2011 1 次提交