Re: [Mesa3d-dev] 3.5 todo list

[Keith W. <ke...@va...>]

Gareth Hughes wrote:
> 
> Keith Whitwell wrote:
> >
> > Brian, Gareth, and others,
> >
> > I'm trying to nail down what's left to do for 3.5.  I've got a list of crucial
> > and 'nice' items, maybe you can add your own items to the list & we can get
> > some idea how close we are to nailing this down.
> >
> > Crucial:
> >
> >         - Floating point color support in 'tnl' module.  (in progress)
> >         - Restore driver ability to swap in alternate tnl modules.
> >
> > Nice:
> >         - Finish the 't_dd_' templates.
> >         - Port the remaining DRI drivers to 3.5. (tdfx in progress, trying
> >           to use the templates)
> >
> >
> > I think 3.5 is such a big step forward in terms of maintainability and
> > cleanliness that it's sensible to see it released as soon as seamliness
> > permits...
> 
> I'm doing a fairly comprehensive reworking of driver texture state and
> texture image handling that will touch core Mesa a bit, as well as
> change/add utility functions.  This will go into 3.5 and would be under
> the "Nice" category.

OK.

> 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...  

> 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'...

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

> 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.

Keith