Brian Paul wrote:
>
> Keith Whitwell wrote:
> >
> > The real problem with this is that changing to flat shade & back again
> > means a buffer flush per rectangle. This is masked by the fact that in
> > the current model we have to do a buffer flush inside the
> > ASSERT_OUTSIDE_BEGIN_END() command, although this hopefully won't always
> > be the case. The real problem that you are addressing is the large
> > performance differential between smooth and flat shaded primitives in
> > the X driver. It shouldn't be too great an effort to attack the problem
> > at its heart & it would certainly be a bigger win.
>
> Naturally, smooth shading is a bit slower than flat shading. However,
> I think the current code is fairly efficient. You'd probably have to
> resort to assembly language to make it substantially faster.
>
Actually I had a look at this. I think I am sitting in the worst
performing graphic mode, because it looks like the truecolor modes are
the only ones which use XPutPixel. I think we can get a good speedup
for at least the most common 16-bit XImage formats by writing directly
into the XImage memory.
Keith
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
