From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-next
Date: Mon, 2 Nov 2015 00:23:50 -0800 [thread overview]
Message-ID: <1446452630-4378-1-git-send-email-thellstrom@vmware.com> (raw)
Dave,
Changes for vmwgfx for 4.4. If there is time, I'll follow up with a series
to move to threaded irqs.
The following changes since commit a76edb8cec0cc864c8b72fa7e84a72336e033e23:
Merge tag 'topic/drm-misc-2015-10-22' of git://anongit.freedesktop.org/drm-intel into drm-next (2015-10-30 09:49:06 +1000)
are available in the git repository at:
git://people.freedesktop.org/git/~thomash/linux vmwgfx-next
for you to fetch changes up to b76ff5ea1cf6fe648e7ce2b84e636f8a95849a0b:
drm/vmwgfx: Replace iowrite/ioread with volatile memory accesses (2015-11-02 00:16:05 -0800)
----------------------------------------------------------------
Dan Williams (1):
drm/vmwgfx: switch from ioremap_cache to memremap
Thomas Hellstrom (2):
drm/vmwgfx: Turn off support for multisample count != 0 v2
drm/vmwgfx: Replace iowrite/ioread with volatile memory accesses
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 8 +--
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 28 +++++++-
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 24 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 109 +++++++++++++++-----------------
drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c | 38 ++++++++---
drivers/gpu/drm/vmwgfx/vmwgfx_irq.c | 9 +--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 23 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 2 +
8 files changed, 140 insertions(+), 101 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-11-02 8:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 8:23 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-16 9:29 [git pull] vmwgfx-next 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-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00 ` Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 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=1446452630-4378-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