From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 00/18] Introduce the Haswell VECS
Date: Tue, 7 May 2013 23:13:39 -0700
Message-ID: <20130508061338.GC3582@bwidawsk.net>
References: <1367110769-1306-1-git-send-email-ben@bwidawsk.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from shiva.localdomain (unknown [209.20.75.48])
	by gabe.freedesktop.org (Postfix) with ESMTP id 277A9E5C20
	for <intel-gfx@lists.freedesktop.org>;
	Tue,  7 May 2013 23:11:02 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <1367110769-1306-1-git-send-email-ben@bwidawsk.net>
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>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Intel-GFX <intel-gfx@lists.freedesktop.org>, Damien Lespiau <damien.lespiau@intel.com>
Cc: Jocelyn Li <jocelyn.li@intel.com>
List-Id: intel-gfx@lists.freedesktop.org

I've pushed a branch with everything I got from Damien's review so far.

http://cgit.freedesktop.org/~bwidawsk/drm-intel/log/?h=vecs-rebase

Since it appears Damien hasn't finished yet, I won't send the updated
patches in case someone else comes along with more comments on those
patches.

Also, since Damien found a pretty significant functional bug with the
semaphore registers, it would be good if we could get some more testing
on the branch. Jocelyn, would it be possible to have someone from your
team run a test with libva. If I recall correctly, Haihao found the same
bug previously, but we seemed to have missed it this time around when I
rebased on the wrong branch.

[snip]

-- 
Ben Widawsky, Intel Open Source Technology Center