On 10/08/2013 04:27 PM, Ben Widawsky wrote:
The HiZ buffer's allocation requirements were relaxed on Ivybridge.
Following a "simple" formula in the bspec was all you needed to satisfy
the requirement.
To prepare the code for this, extract all places where the miptree was
used, when we really onl
The HiZ buffer's allocation requirements were relaxed on Ivybridge.
Following a "simple" formula in the bspec was all you needed to satisfy
the requirement.
To prepare the code for this, extract all places where the miptree was
used, when we really only needed the region. This allows an upcoming
p
On Thu, Sep 26, 2013 at 11:16:52AM -0700, Chad Versace wrote:
> On 09/26/2013 10:37 AM, Chad Versace wrote:
> >On 09/22/2013 10:37 AM, Ben Widawsky wrote:
> >>Starting with Ivybridge, the hierarchical had relaxed requirements for
> >^^^
> >"the hierarchical"
On 09/26/2013 10:37 AM, Chad Versace wrote:
On 09/22/2013 10:37 AM, Ben Widawsky wrote:
Starting with Ivybridge, the hierarchical had relaxed requirements for
^^^
"the hierarchical" doesn't make sense. Just call it "the HiZ buffer" or
"the hiz buffer".
On 09/22/2013 10:37 AM, Ben Widawsky wrote:
Starting with Ivybridge, the hierarchical had relaxed requirements for
^^^
"the hierarchical" doesn't make sense. Just call it "the HiZ buffer" or
"the hiz buffer".
its allocation. Following a "simple" formula i
Starting with Ivybridge, the hierarchical had relaxed requirements for
its allocation. Following a "simple" formula in the bspec was all you
needed to satisfy the requirement.
To prepare the code for this, extract all places where the miptree was
used, when we really only needed the region. This a
