From: Thomas Hellstrom <thellstrom@vmware.com>
To: dri-devel@lists.freedesktop.org, airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com
Subject: [git pull] vmwgfx-next
Date: Thu, 6 Aug 2015 05:54:58 -0700 [thread overview]
Message-ID: <1438865698-3911-1-git-send-email-thellstrom@vmware.com> (raw)
Dave,
Take 2 implementing screen targets, this time with the fbdev code adjusted
accordingly.
Also there is an implementation of register-driven command buffers, that
overrides the FIFO ring for command processing. It's needed for our upcoming
hardware revision.
The following changes since commit dcd14dd957f02ef679c61325a2221a0574bdcab3:
Merge tag 'topic/connector-locking-2015-07-23' of git://anongit.freedesktop.org/drm-intel into drm-next (2015-07-24 14:30:29 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux vmwgfx-next
for you to fetch changes up to 6a5278ee34e7fd4b051fd107a94a099778458d8c:
drm/vmwgfx: Fix an uninitialized value (2015-08-05 14:01:12 +0200)
----------------------------------------------------------------
Sinclair Yeh (5):
drm/vmwgfx: SVGA device definition update
drm/vmwgfx: Refactor vmw_gb_surface_define_ioctl()
vmwgfx: Major KMS refactoring / cleanup in preparation of screen targets
drm/vmwgfx: Implement screen targets
drm/vmwgfx: Replace SurfaceDMA usage with SurfaceCopy in 2D VMs
Thomas Hellstrom (20):
drm/vmwgfx: Fix an fb unlocking bug
vmwgfx: Rework device initialization
drm/vmwgfx: Fix OTABLE takedown
vmwgfx: Update device headers for command buffers.
drm/vmwgfx: Add command buffer support v3
drm/vmwgfx: Fix an overlay lockdep error
drm/vmwgfx: Add an interface to pin a resource v3
drm/vmwgfx: Add "quirk" to handling command verification exceptions
drm/vmwgfx: Introduce a pin count to allow for recursive pinning v2
drm/vmwgfx: Add kms helpers for dirty- and readback functions
drm/vmwgfx: Convert screen objects to the new helpers
drm/vmwgfx: Convert screen targets to new helpers v3
drm/vmwgfx: Avoid cmdbuf alloc sleeping if !TASK_RUNNING
drm/vmwgfx: Add a kernel interface to create a framebuffer v2
drm/vmwgfx: Implement fbdev on kms v2
drm/vmwgfx: Reinstate the legacy display system dirty callback
drm/vmwgfx: Fix kms preferred mode sorting
drm/vmwgfx: Kill a bunch of sparse warnings
drm/vmwgfx: Fix compiler warning with 32-bit dma_addr_t
drm/vmwgfx: Fix an uninitialized value
drivers/gpu/drm/vmwgfx/Makefile | 2 +-
drivers/gpu/drm/vmwgfx/svga3d_reg.h | 60 +-
drivers/gpu/drm/vmwgfx/svga3d_surfacedefs.h | 67 +-
drivers/gpu/drm/vmwgfx/svga_reg.h | 187 ++++
drivers/gpu/drm/vmwgfx/svga_types.h | 3 +
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 13 +
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 1304 ++++++++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 20 +-
drivers/gpu/drm/vmwgfx/vmwgfx_dmabuf.c | 182 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 440 ++++----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 162 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 292 +++--
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 558 ++++++----
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 8 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 122 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c | 12 +-
drivers/gpu/drm/vmwgfx/vmwgfx_irq.c | 45 +-
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 1593 +++++++++++++--------------
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 192 +++-
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 47 +-
drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 43 +-
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 10 +-
drivers/gpu/drm/vmwgfx/vmwgfx_reg.h | 6 +-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 130 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 556 +++++++++-
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 14 +-
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 1265 +++++++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 215 ++--
include/uapi/drm/vmwgfx_drm.h | 1 +
29 files changed, 5892 insertions(+), 1657 deletions(-)
create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c
create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-08-06 12:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 12:54 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-02 8:23 [git pull] vmwgfx-next Thomas Hellstrom
2015-11-06 15:29 Thomas Hellstrom
2017-01-30 19:46 Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00 ` Sinclair Yeh
2017-04-21 17:18 Sinclair Yeh
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
2018-09-28 13:11 [git pull] vmwgfx-next Thomas Hellstrom
2018-12-05 10:35 Thomas Hellstrom
2019-06-19 7:25 Thomas Hellström (VMware)
[not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2019-08-15 7:15 Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
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)
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=1438865698-3911-1-git-send-email-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox