mesa3d-dev

[Mesa3d-dev] 3.5 todo list

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

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

Keith

Re: [Mesa3d-dev] 3.5 todo list

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

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.

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

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.

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.

-- Gareth

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

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

Re: [Mesa3d-dev] 3.5 todo list

[Brian P. <br...@va...>]

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

A few things I'd like to do:

1. clean-up the function namespace.  I.e. replace gl_*() functions with
   _mesa_*().

2. clean-up the INTERP_Z and fog code in the line and triangle template
   code.

3. I've still got some corner cases to fix in the new teximage code.
   glGetTexImage(GL_COLOR_INDEX), for example, doesn't work right.

4. Integrate the SGI SI GLU.

Otherwise, I think I've fixed the last of the conformance bugs.
All color index mode tests now pass (at 8pp) and all RGB tests work
at 24, 16 and 8bpp.  The only exception is a convolution border
mode test at 8bpp.  A comment in the code for that test says that
the test may not work correctly at shallow depths so i'm not too concerned.

-Brian

BTW: I'm trying to upload 3.4.1 to sourceforge but the upload facility
still seems to be broken.

Re: [Mesa3d-dev] 3.5 todo list

[emanuel s. <em...@ec...>]

Keith Whitwell wrote:
> 
> Brian, Gareth, and others,
> 
> I'm trying to nail down what's left to do for 3.5.  

Win32 Makefiles ?
;-)

cheers

Re: [Mesa3d-dev] 3.5 todo list

[Brian P. <br...@va...>]

emanuel stiebler wrote:
> 
> Keith Whitwell wrote:
> >
> > Brian, Gareth, and others,
> >
> > I'm trying to nail down what's left to do for 3.5.
> 
> Win32 Makefiles ?
> ;-)

The Mesa/Windows driver code will need a number of updates in order
to work at all with Mesa 3.5.

As of now, nobody's taking an active role in maintaining the
Windows code.  I'm not likely to postpone the 3.5 release
waiting for anyone to do that.

-Brian