Re: [Mesa3d-dev] 3.5 todo list

[Gareth H. <ga...@va...>]

Keith Whitwell wrote:
> 
> > I'd pretty much like to work on any of the above.  I might be
> > particularly useful on the templates, having working copies for 3.4
> > myself.  I'd also like to port at least one driver to 3.5 (r128 and mga
> > are good candidates here).
> 
> You can have either or both of them...

I'll take both.

> > Here's my Nice list:
> >
> >         - General work on driver begin/end objects.
> >         - Code generation for begin/end objects.
> >         - Asm-optimized clipping, lighting code.
> >
> > And after that (Really Nice?  Not As Nice?):
> >
> >         - General work (like the old fastpath) to accelerate driver
> >           rendering paths.
> 
> All this is good stuff but I think we can finalize 3.5 and do this afterwards
> as seperate work.  (I'm not trying to push this back, just pull forwards the
> 3.5 release).  Using my list, I think a 3.5 release could occur after the
> 'crucial' and before the 'nice'...

Sorry, I should have made that clearer.  This is what I meant, I just
wanted to let you guys know what I will be working on in the future. 
After 3.5 goes out, that is...

> The current code matches or beats the old fastpath, but for different
> reasons.  So yes, path improvements are possible.

Exactly.  I'd like to profile the new code and work out nifty ways to
make it run faster.  No matter what, it will be a good chance to really
learn the new code.

> > If you haven't started the tnl module swapping stuff, that might be a
> > good thing for me to work on in the short term.
> 
> I haven't.  I've got a basic design I'll try and detail in a followup email.

Okay, cool.

-- Gareth