Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 17 1月, 2014 9 次提交
  3. 18 12月, 2013 1 次提交
  5. 05 12月, 2013 1 次提交
    • T
      drm/vmwgfx: Fix dma buffer memory size accounting · 308d17ef
      由 Thomas Hellstrom 提交于 
      Also request kernel ttm_buffer objects for buffer objects that obviously
aren't visible to user-space, and save some device address space.

The accounting was broken in a couple of ways:
1) We did not differentiate between user dma buffers and kernel dma buffers.
2) The ttm_bo_acc_size function is broken in that it
a) Doesn't take into account the size of the optional dma address array,
b) Doesn't take into account the fact that drivers typically embed the
ttm_tt structure.

This needs to be fixed in ttm, but meanwhile provide a vmwgfx-specific
function to do the job.
Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: NJakob Bornecrantz <jakob@vmware.com>
      308d17ef
  7. 18 11月, 2013 1 次提交
  9. 06 11月, 2013 1 次提交
  11. 19 8月, 2013 1 次提交
    • D
      drm/vmwgfx: remove ->firstopen callback · 0faa4a87
      由 Daniel Vetter 提交于 
      So if we survey kms drivers there's a bunch of things they commonly do
in ->lastclose
- delayed processing of vga switcheroo requests (i915, nouveau,
  radeon)
- force-restoring the fbcon (most)
- resetting a bunch properties to make fbcon work better (omap)
- disabling all outputs (vmwgfx)

In short besides the semantically important vga switcheroo stuff they
all try very hard to keep fbcon working in case X dies.

But none of them try to not do this at driver unload time safe for
vmwgfx, and digging through logs I couldn't find any reason for why
vmwgfx is special.

Since ->firstopen has lots of potential for abuse with kms drivers
(like delaying driver setup to pamper over races in the load sequence)
it's imo very much worth it to remove this logic so that we can
stop using the ->firstopen callback for kms drivers.

Also module unloading is rather a debug feature and developers should
know how to restore the display to a sane configuration.

Cc: Jakob Bornecrantz <jakob@vmware.com>
Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: NDave Airlie <airlied@redhat.com>
      0faa4a87
  13. 28 11月, 2012 1 次提交
  15. 21 11月, 2012 1 次提交
  17. 20 11月, 2012 1 次提交
  19. 03 10月, 2012 1 次提交
  21. 13 9月, 2012 1 次提交
  23. 13 2月, 2012 6 次提交
  25. 19 12月, 2011 1 次提交
  27. 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
  29. 18 10月, 2011 1 次提交
  31. 10 10月, 2011 2 次提交
  33. 05 10月, 2011 9 次提交
  35. 06 9月, 2011 1 次提交