From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff McGee <jeff.mcgee@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: Slice/Subslice/EU info via
 GETPARAM
Date: Wed, 6 Aug 2014 09:43:44 -0500
Message-ID: <20140806144344.GF4660@jeffdesk>
References: <1406771987-1127-1-git-send-email-jeff.mcgee@intel.com>
 <20140804082037.GP8727@phenom.ffwll.local>
 <20140805140333.GD4660@jeffdesk>
 <CAKMK7uEtX8JEW4G_5sRJXFWrMsgVpwtEfBX5KaYTH9v6vTo=0w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21])
 by gabe.freedesktop.org (Postfix) with ESMTP id B2B9A6E275
 for <intel-gfx@lists.freedesktop.org>; Wed,  6 Aug 2014 07:33:15 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <CAKMK7uEtX8JEW4G_5sRJXFWrMsgVpwtEfBX5KaYTH9v6vTo=0w@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On Tue, Aug 05, 2014 at 04:50:16PM +0200, Daniel Vetter wrote:
> On Tue, Aug 5, 2014 at 4:03 PM, Jeff McGee <jeff.mcgee@intel.com> wrote:
> >> Also, usual broken record request: I need open-source userspace using
> >> this (mesa, ddx, libva).
> >> -Daniel
> >>
> >
> > This is kind of chicken-and-egg problem that I haven't been through. I
> > assume that we build new interfaces up the stack (kernel->libdrm->usermode).
> > Any tips or docs on how to proceed?
> 
> You need to have the full thing ready with kernel, igt, libdrm, and
> umd driver patches (and maybe even testcases for the new umd feature,
> e.g. for some of the arb robustness stuff we've done). Then you post
> them all to relevant mailing lists and go through the review process
> for all parts. Once that's done and _all_ parts are reviewed, merging
> starts with kernel+igt, then libdrm + libdrm release, then umd.
> -Daniel

Thanks Daniel. Is it acceptable to get the kernel part merged with only
an igt test (technically an open-source userspace component)? I think
probably not, but have to ask.
-Jeff