Mesa 3.5 release notes
- Month ??, 2001
+ June 21, 2001
PLEASE READ!!!!
------------
Mesa uses an even/odd version number scheme like the Linux kernel.
-Odd numbered versions (such as 3.3) designate new developmental releases.
+Odd numbered versions (such as 3.5) designate new developmental releases.
Even numbered versions (such as 3.4) designate stable releases.
-The internal structure of Mesa 3.5 is (will be) changed so that it
-is more modular. The motivation is better support of 3D hardware
-such as T&L hardware in which much of core Mesa isn't needed.
+The biggest change in Mesa 3.5 is a complete overhaul of the source
+code in order to make it more modular. This was driven by the DRI
+hardware drivers. It simplifies the DRI drivers and opens the door
+to hardware transform/clip/lighting (TCL). Keith Whitwell can take
+the credit for that.
+
+
+
+Driver Support
+--------------
+
+The device driver interface in Mesa 3.5 has changed a lot since Mesa 3.4
+Not all of the older Mesa drivers have been updated. Here's the status:
+
+Driver Status
+---------------------- -----------
+XMesa (Xlib) updated
+OSMesa (off-screen) updated
+FX (3dfx Voodoo1/2) updated
+SVGA updated
+GGI not updated
+Windows/Win32 not updated
+DOS/DJGPP not updated
+BeOS not updated
+Allegro not updated
+D3D not updated
+DOS not updated
+
+We're looking for volunteers to update the remaining drivers. Please
+post to the Mesa3d-dev mailing list if you can help.
-Details to come...
GLU 1.3
GL_SGIX_depth_texture, GL_SGIX_shadow and GL_SGIX_shadow_ambient
Implements a shadow casting algorithm based on depth map textures
+GL_SGIS_generate_mipmap
+ Automatically generate lower mipmap images whenever the base mipmap
+ image is changed with glTexImage, glCopyTexImage, etc.
+
libOSMesa.so
Multitexture
------------
-Three texture units are now supported by default. We'll allow more
-than three texture units when we fix some bitfield issues. In at least
-one place we have a 32-bit bitfield which is fully allocated, leaving
-no space for texture unit #3 or higher.
-
-The TEXTURE1_1D, TEXTURE1_2D, etc constants may go away in the future.
-Currently, they're only used in the ctx->Texture.ReallyEnabled field.
-This bitfield is just a conglomerate of ctx->Texture.Unit[i].ReallyEnabled
-for all <i> texture units. ctx->Texture.ReallyEnabled may become a
-GLboolean. Then, drivers will have to loop over the texture units to
-examine ctx->Texture.Unit[i].ReallyEnabled.
-
-
-
+Eight texture units are now supported by default.
-Internal color values
+16-bit color channels
---------------------
-Previously, Mesa treated color channel values as GLubytes in [0,255].
-Mesa 3.5 uses the GLchan datatype for color channel values. In the
-future it will be possible to define GLchan to be larger than a byte
-in order to support high-precision colors.
-
-Many, many occurances of GLubyte have been replaced with GLchan
-and many occurances of the number 255 have been replaced with CHAN_MAX.
+There's experimental support for 16-bit color channels (64-bit pixels)
+in Mesa 3.5. Only the OSMesa interface can be used for 16-bit rendering.
+Type "make linux-osmesa16" in the top-level directory to build the
+special libOSMesa16.so library.
-Support for CHAN_BITS > 8 is not ready yet but will be eventually.
+This hasn't been tested very thoroughly yet so please file bug reports
+if you have trouble.
+In the future I hope to implement support for 32-bit, floating point
+color channels.
----------------------------------------------------------------------
-$Id: RELNOTES-3.5,v 1.11 2001/04/20 02:34:12 brianp Exp $
+$Id: RELNOTES-3.5,v 1.14 2001/06/20 19:02:48 brianp Exp $