On Wed, Jun 03, 2015 at 12:20:09AM -0700, Kenneth Graunke wrote:
> On Tuesday, June 02, 2015 11:41:56 PM Ben Widawsky wrote:
> > On Tue, 02 Jun 2015 20:32:13 -0700
> > Kenneth Graunke wrote:
> >
> > > On Tuesday, June 02, 2015 08:07:50 PM Ben Widawsky wrote:
> > > > I'm very confused here. It see
On Tuesday, June 02, 2015 11:41:56 PM Ben Widawsky wrote:
> On Tue, 02 Jun 2015 20:32:13 -0700
> Kenneth Graunke wrote:
>
> > On Tuesday, June 02, 2015 08:07:50 PM Ben Widawsky wrote:
> > > I'm very confused here. It seems pretty clear that since the
> > > command has been introduced with support
On Tue, 02 Jun 2015 20:32:13 -0700
Kenneth Graunke wrote:
> On Tuesday, June 02, 2015 08:07:50 PM Ben Widawsky wrote:
> > I'm very confused here. It seems pretty clear that since the
> > command has been introduced with support for MOCS, MOCS lives at
> > bit 8 of dword 0 for all constant buffers
On Tuesday, June 02, 2015 08:07:50 PM Ben Widawsky wrote:
> I'm very confused here. It seems pretty clear that since the command has been
> introduced with support for MOCS, MOCS lives at bit 8 of dword 0 for all
> constant buffers. The error has existed since forever AFAICT.
>
> No piglit regress
I'm very confused here. It seems pretty clear that since the command has been
introduced with support for MOCS, MOCS lives at bit 8 of dword 0 for all
constant buffers. The error has existed since forever AFAICT.
No piglit regressions or fixes:
http://otc-mesa-ci.jf.intel.com/view/dev/job/bwidawsk
