Re: [Mesa3d-dev] gallium: let drivers fallback on framebuffer clearing

2009-12-10 Thread Keith Whitwell
On Thu, 2009-12-10 at 01:52 -0800, Marek Olšák wrote: > Keith, > > I've taken your comment into consideration and started laying out a > new simple driver module which I call Blitter. The idea is to provide > acceleration for operations like clear, surface_copy, and > surface_fill. The module does

Re: [Mesa3d-dev] gallium: let drivers fallback on framebuffer clearing

2009-12-10 Thread Marek Olšák
Keith, I've taken your comment into consideration and started laying out a new simple driver module which I call Blitter. The idea is to provide acceleration for operations like clear, surface_copy, and surface_fill. The module doesn't depend on a CSO context, instead, a driver must call appropria

Re: [Mesa3d-dev] gallium: let drivers fallback on framebuffer clearing

2009-12-08 Thread Keith Whitwell
On Mon, 2009-12-07 at 05:01 -0800, Marek Olšák wrote: > Hi, > > Because some hardware under some circumstances (e.g. disabled tiling) > may not be able to use a hardware-specific clear path, it would be > nice to let a state tracker do the clearing by drawing a > screen-aligned quad. I am proposin

[Mesa3d-dev] gallium: let drivers fallback on framebuffer clearing

2009-12-07 Thread Marek Olšák
Hi, Because some hardware under some circumstances (e.g. disabled tiling) may not be able to use a hardware-specific clear path, it would be nice to let a state tracker do the clearing by drawing a screen-aligned quad. I am proposing to change the pipe_context->clear function to return TRUE if buf