renumber ARB_shader_objects and ARB_vertex_shader offsets

[mesa.git] / docs / README.DJ

diff --git a/docs/README.DJ b/docs/README.DJ
index 2e663d2ee70427e5b49d8489a1b8a1a884d52777..4b086cc4e5a36cb9bce951d29bc980230dbfbc6d 100644 (file)
--- a/docs/README.DJ
+++ b/docs/README.DJ
@@ -1,4 +1,4 @@
-                       Mesa 6.1 DOS/DJGPP Port v1.6
+                       Mesa 6.3 DOS/DJGPP Port v1.7
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 
@@ -6,7 +6,7 @@
 Description:
 ~~~~~~~~~~~~
 
-Well, guess what... this is the DOS port of Mesa 6.1, for DJGPP fans... Whoa!
+Well, guess what... this is the DOS port of Mesa 6.3, for DJGPP fans... Whoa!
 The driver has its origins in ddsample.c, written by Brian Paul and found by me
 in Mesa 3.4.2.
 
@@ -42,15 +42,7 @@ Available options:
                        As a consequence, you'll need the DJGPP Glide3
                        library to build any application.
                        default = no
-       HAVE_X86=1      optimize for i386.
-                       default = no
-       HAVE_MMX=1      allow MMX specializations, provided your assembler
-                       supports MMX instruction set. However, the true CPU
-                       capabilities are checked at run-time to avoid lockups.
-                       default = no
-       HAVE_SSE=1      (see HAVE_MMX)
-                       default = no
-       HAVE_3DNOW=1    (see HAVE_MMX)
+       X86=1           optimize for x86 (if possible, use MMX, SSE, 3DNow).
                        default = no
 
      Targets:
@@ -100,7 +92,7 @@ FAQ:
 2. Using Mesa for DJGPP
 
    Q) DMesa is so SLOOOW! The Win32 OpenGL performs so much better...
-   A) Is that a question? If you have a 3dfx Voodoo^2 or higher card, you're
+   A) Is that a question? If you have a 3dfx Voodoo (any model), you're
       lucky (check http://sourceforge.net/projects/glide for the DJGPP port).
       If you haven't, sorry; everything is done in software. Suggestions?
 
@@ -128,8 +120,8 @@ FAQ:
 
    Q) What is NUL driver good for, if I don't get any output at all?
    A) For debugging. The NUL driver is very much like OSMesa. Everything is
-      done just the same as VESA/VGA drivers, only it doesn't touches your
-      video hardware. You can query the actual buffer by issuing:
+      done just the same as VESA/VGA drivers, only it doesn't touch your video
+      hardware. You can query the actual buffer by issuing:
        DMesaGetIntegerv(DMESA_GET_BUFFER_ADDR, &buffer);
       and dump it to a file.
 
@@ -142,7 +134,7 @@ FAQ:
        struct {
                int xres, yres;
                int bpp;
-       } **l = malloc(n * sizeof(void **));
+       } **l = malloc(n * sizeof(void *));
       Now pass the newly allocated buffer to fill in:
        DMesaGetIntegerv(DMESA_GET_VIDEO_MODES, (GLint *)l);
       And collect the info:
@@ -258,17 +250,22 @@ v1.5 (jan-2004)
        - removed Matrox Millennium MGA2064W driver
        x more changes to the 3dfx driver
 
-v1.6 (???-2004)
+v1.6 (aug-2004)
        + implemented NUL driver
        + added DMesaGetProcAddress and glutGetProcAddress
        * reorganized fxMesa wrapper to handle multiple contexts
        ! fixed a horrible bug in VGA initialization routine
+       ! fixed partial clears
+
+v1.7 (???-2004)
+       + enabled OpenGL 2.0 support
+       + added support for sw texture compression
 
 
 
 Contact:
 ~~~~~~~~
 
-Name:   Borca Daniel
+Name:   Daniel Borca
 E-mail: dborca@users.sourceforge.net
 WWW:    http://www.geocities.com/dborca/