dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>
Subject: [GIT PULL] drm-vc4-next-2016-11-16
Date: Wed, 16 Nov 2016 13:29:19 -0800	[thread overview]
Message-ID: <20161116212919.11239-1-eric@anholt.net> (raw)

  Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)

are available in the git repository at:

  https://github.com/anholt/linux tags/drm-vc4-next-2016-11-16

for you to fetch changes up to c778cc5df944291dcdb1ca7a6bb781fbc22550c5:

  drm/vc4: Add fragment shader threading support (2016-11-16 13:25:26 -0800)

----------------------------------------------------------------
This pull request brings in fragment shader threading and ETC1 support
for vc4.

----------------------------------------------------------------
Dan Carpenter (1):
      drm/vc4: Fix a couple error codes in vc4_cl_lookup_bos()

Eric Anholt (3):
      drm/vc4: Fix termination of the initial scan for branch targets.
      drm/vc4: Add support for rendering with ETC1 textures.
      drm/vc4: Use runtime autosuspend to avoid thrashing V3D power state.

Jonas Pfeil (1):
      drm/vc4: Add fragment shader threading support

 drivers/gpu/drm/vc4/vc4_drv.c              | 11 ++--
 drivers/gpu/drm/vc4/vc4_drv.h              |  2 +
 drivers/gpu/drm/vc4/vc4_gem.c              | 15 +++---
 drivers/gpu/drm/vc4/vc4_v3d.c              |  2 +
 drivers/gpu/drm/vc4/vc4_validate.c         | 24 +++++++--
 drivers/gpu/drm/vc4/vc4_validate_shaders.c | 82 ++++++++++++++++++++++++++----
 include/uapi/drm/vc4_drm.h                 |  2 +
 7 files changed, 113 insertions(+), 25 deletions(-)

                 reply	other threads:[~2016-11-16 21:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161116212919.11239-1-eric@anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).