All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sinclair Yeh <syeh@vmware.com>
Cc: airlied@redhat.com, linux-graphics-maintainer@vmware.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [git pull] vmwgfx-next
Date: Sun, 2 Apr 2017 20:11:12 +0200	[thread overview]
Message-ID: <20170402181112.iwogxvqhw5aefniy@phenom.ffwll.local> (raw)
In-Reply-To: <20170331233255.GA38850@syeh-m02>

On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote:
> Hi Dave,
> 
> This series enables atomic mode set for vmwgfx.  A number of features and
> larger fixes are also included.
> 
> The following changes since commit 8cd3ac52963f2e99f4c21d1c9ce89531ce66c2d6:
> 
>   Merge branch 'drm-next-4.12' of git://people.freedesktop.org/~agd5f/linux into drm-next (2017-03-31 11:47:18 +1000)
> 
> are available in the git repository at:
> 
>   git://people.freedesktop.org/~syeh/repos_linux drm-vmwgfx-next
> 
> for you to fetch changes up to 28c954299cd2b5cb5411816c9eeaf3f51ed4638e:
> 
>   drm/vmwgfx: Properly check display/scanout surface size (2017-03-31 15:21:20 -0700)
> 
> ----------------------------------------------------------------
> Sinclair Yeh (18):
>       drm/vmwgfx: Removed unused snooper.crtc field
>       drm/vmwgfx: Add universal plane support
>       drm/vmwgfx: CRTC atomic state
>       drm/vmwgfx: Plane atomic state
>       drm/vmwgfx: Connector atomic state
>       drm/vmwgfx: Add and connect CRTC helper functions
>       drm/vmwgfx: Add and connect plane helper functions
>       drm/vmwgfx: Add and connect connector helper function
>       drm/vmwgfx: Add and connect atomic state object check/commit
>       drm/vmwgfx: Fixes to vmwgfx_fb
>       drm/vmwgfx: Switch over to internal atomic API for STDU
>       drm/vmwgfx: Switch over to internal atomic API for SOU and LDU
>       drm/vmwgfx: Turn on DRIVER_ATOMIC flag
>       drm/vmwgfx: Explicityly track screen target width and height
>       drm/vmwgfx: Skipping fbdev fb pinning for ldu
>       drm/vmwgfx: Fix LDU X blank screen until mode change issue
>       drm/vmwgfx: Support topology greater than texture size
>       drm/vmwgfx: Properly check display/scanout surface size
> 
> Thomas Hellstrom (3):
>       drm/vmwgfx: Introduce a simple resource type
>       drm/vmwgfx: Re-implement the stream resource as a simple resource.
>       drm/vmwgfx: Define an overlaid handle_close ioctl.
> 
> Øyvind A. Holm (1):
>       drm/vmwgfx: Revert "drm/vmwgfx: Replace numeric parameter like 0444 with macro"

Quite a pile of conflicts of this against the drm-misc-next pull. Nothing
too hairy, but just more reasons to remove all the vmwgfx special cases
again :-)

Also noticed that you've forgotten to garabge collect the legacy cursor
functions. Probably a good reason for having vfunc implementations in the
same file as the vtable so that they can all be static and the compiler
will tell you when you forget to remove stuff. vmwgfx and radeon/amdgpu
are anti-pattern drivers in this regard imo. On top it's annoying when you
always have to change a prototype in 2 places when doing a subsystem-wide
change :-)

Cheers, Daniel

>  drivers/gpu/drm/vmwgfx/Makefile                 |    3 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.c             |   13 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.h             |    2 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_fb.c              |   27 ++-
>  drivers/gpu/drm/vmwgfx/vmwgfx_kms.c             | 1111 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------
>  drivers/gpu/drm/vmwgfx/vmwgfx_kms.h             |  143 ++++++++++++--
>  drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c             |  373 ++++++++++++++++++++++++-----------
>  drivers/gpu/drm/vmwgfx/vmwgfx_resource.c        |  254 ------------------------
>  drivers/gpu/drm/vmwgfx/vmwgfx_resource_priv.h   |   40 ++++
>  drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c            |  510 +++++++++++++++++++++++++++++++-----------------
>  drivers/gpu/drm/vmwgfx/vmwgfx_simple_resource.c |  256 ++++++++++++++++++++++++
>  drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c            |  937 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------
>  drivers/gpu/drm/vmwgfx/vmwgfx_surface.c         |   15 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_va.c              |  168 ++++++++++++++++
>  include/uapi/drm/vmwgfx_drm.h                   |   24 +++
>  15 files changed, 2856 insertions(+), 1020 deletions(-)
>  create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_simple_resource.c
>  create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_va.c
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-04-02 18:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 23:32 [git pull] vmwgfx-next Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter [this message]
2017-04-03 19:00   ` Sinclair Yeh
  -- strict thread matches above, loose matches on Subject: below --
2020-01-16  9:29 Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42   ` Thomas Hellström (VMware)
2020-01-21  9:49   ` Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15  7:15 Thomas Hellström (VMware)
     [not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2019-06-19  7:25 Thomas Hellström (VMware)
2018-12-05 10:35 Thomas Hellstrom
2018-09-28 13:11 Thomas Hellstrom
2017-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39   ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02  8:23 Thomas Hellstrom
2015-08-06 12:54 Thomas Hellstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170402181112.iwogxvqhw5aefniy@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=syeh@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.