Ben Skeggs wrote:
> Am Freitag, den 21.09.2007, 08:45 +0100 schrieb Keith Whitwell:
>> Brian Paul wrote:
>>> Ben Skeggs wrote:
>>>> I've been playing gallium on NV40 hardware a bit this week, so far it
>>>> seems very nice.  However... :)
>>>>
>>>> The hardware supports selective clearing of each channel of the primary
>>>> render target, depth, and stencil buffers in a single operation.  The
>>>> current buffer clear interface is called with separate pipe_surface
>>>> structs for each GL_x_BUFFER_BIT, which makes it difficult to use this
>>>> functionality (which is somewhat faster when clearing both colour and
>>>> depth/stencil buffers at the same time).
>>>>
>>>> Is there any plan for a pipe->fb_clear() (for example) interface, which
>>>> would pass in a bit mask saying "clear these buffers that are currently
>>>> bound to the framebuffer", similar to the interface in the "old" driver
>>>> model?
>>> If you can also specify the channel mask for clearing each buffer, you'd 
>>> probably want something like:
>>>
>>> clear(uint numSurfaces, pipe_surface **surfaces, const uint *masks)
>> I see reasonable uses for clearing fullscreen color, depth and stencil 
>> independently.  There's also a case that we should be able to pass down 
>> a list of fullscreen clears so that the driver can process them as 
>> efficiently as possible.
> Yes, this is what I was after.  The ability to clear some combination of
> colour/depth/stencil buffers in one operation, I don't care for the
> ability to clear R/G/B/A individually, was just mentioning that's how
> the hw implements clears :)

OK.

If you want to change clear() to take a list of surfaces, go ahead.

-Brian

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to