[Mesa-dev] separate depth and stencil buffers in gallium

Dave Airlie airlied at gmail.com
Wed Sep 22 03:40:07 PDT 2010

On Wed, Sep 22, 2010 at 8:20 PM, Keith Whitwell
<keith.whitwell at gmail.com> wrote:
> On Wed, Sep 22, 2010 at 11:15 AM, Dave Airlie <airlied at gmail.com> wrote:
>>>> I'm mainly posting just wondering if anyone else has considered this
>>>> or any other hardware this might be useful for exists, or if anyone
>>>> can speak to the pitfalls I'll face.
>>>> I've got some initial done in 30 mins hacks
>>>> http://cgit.freedesktop.org/~airlied/mesa/log/?h=sep-zs
>> So I'm guessing I've taken the wrong approach here from reading this,
>> I should probably not expose this to gallium, and just make sure the DDX
>> allocates a large enough buffer for two planes.
> This sounds good, especially if sampling needs yet more logic.
> Presumably things like Hyper-Z require their own, additional storage?

the HiZ/HiS on r600 needs VRAM allocated, thinking about it now I
wonder if we need to group that allocation with the depth alloc, esp
for the whole GLX context sharing stuff.

I suppose r300g has similar issues, though the HiZ/Zmask on those GPUs
is internal.


More information about the mesa-dev mailing list