All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Remove ancient I915_GEM_EXECBUFFER (v1) support
Date: Wed, 06 Dec 2017 14:04:20 +0000	[thread overview]
Message-ID: <151256906034.3497.15506520313363569466@mail.alporthouse.com> (raw)
In-Reply-To: <20171206115641.14558-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2017-12-06 11:56:41)
> We transitioned to I915_GEM_EXECBUFFER2 in
> 
> commit 76446cac68568fc7f5168a27deaf803ed22a4360 [v2.6.33]
> Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> Date:   Thu Dec 17 22:05:42 2009 -0500
> 
>     drm/i915: execbuf2 support
> 
> and
> 
> libdrm commit b50964027bef249a0cc3d511de05c2464e0a1e22 [v2.4.19]
> Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> Date:   Tue Sep 15 11:02:58 2009 -0700
> 
>     libdrm/intel: execbuf2 support

For more perspective, this was required by

xf86-video-intel commit 8899cd03e2e7ee673e8b3b2a9d2873839cdc1bf8 [v2.11.901]
Author: Carl Worth <cworth@cworth.org>
Date:   Thu Jun 10 15:38:54 2010 -0700

    Fix to require libdrm 2.4.19 or newer.

and

mesa commit 179d2c0e0bcf96fc40107882ccab909af8c89853 [v7.8]
Author: Eric Anholt <eric@anholt.net>
Date:   Tue Mar 2 15:34:17 2010 -0800

    intel: Use drm_intel_bo_alloc_tiled for region allocs.

-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-12-06 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 11:56 [PATCH] drm/i915: Remove ancient I915_GEM_EXECBUFFER (v1) support Chris Wilson
2017-12-06 12:20 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-06 13:35 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-06 14:04 ` Chris Wilson [this message]

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=151256906034.3497.15506520313363569466@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@linux.ie \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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.