diff options
Diffstat (limited to 'mesalib/docs')
| -rw-r--r-- | mesalib/docs/GL3.txt | 58 | ||||
| -rw-r--r-- | mesalib/docs/autoconf.html | 54 | ||||
| -rw-r--r-- | mesalib/docs/devinfo.html | 300 | ||||
| -rw-r--r-- | mesalib/docs/index.html | 6 | ||||
| -rw-r--r-- | mesalib/docs/relnotes.html | 1 | ||||
| -rw-r--r-- | mesalib/docs/relnotes/10.2.6.html | 118 | ||||
| -rw-r--r-- | mesalib/docs/relnotes/10.3.html | 17 |
7 files changed, 486 insertions, 68 deletions
diff --git a/mesalib/docs/GL3.txt b/mesalib/docs/GL3.txt index 3d610f6e1..76412c3dc 100644 --- a/mesalib/docs/GL3.txt +++ b/mesalib/docs/GL3.txt @@ -94,18 +94,18 @@ GL 4.0, GLSL 4.00: GL_ARB_draw_buffers_blend DONE (i965, nv50, nvc0, r600, radeonsi, softpipe) GL_ARB_draw_indirect DONE (i965, nvc0, radeonsi, softpipe, llvmpipe) - GL_ARB_gpu_shader5 started + GL_ARB_gpu_shader5 DONE (i965, nvc0) - 'precise' qualifier DONE - - Dynamically uniform sampler array indices started (Chris) - - Dynamically uniform UBO array indices started (Chris) + - Dynamically uniform sampler array indices DONE () + - Dynamically uniform UBO array indices DONE () - Implicit signed -> unsigned conversions DONE - - Fused multiply-add DONE (i965, nvc0) - - Packing/bitfield/conversion functions DONE (i965, nvc0, r600) - - Enhanced textureGather DONE (i965, nvc0, r600, radeonsi) - - Geometry shader instancing DONE (i965, nvc0) - - Geometry shader multiple streams DONE (i965, nvc0) - - Enhanced per-sample shading DONE (i965, r600) - - Interpolation functions DONE (i965) + - Fused multiply-add DONE () + - Packing/bitfield/conversion functions DONE (r600) + - Enhanced textureGather DONE (r600, radeonsi) + - Geometry shader instancing DONE () + - Geometry shader multiple streams DONE () + - Enhanced per-sample shading DONE (r600) + - Interpolation functions DONE () - New overload resolution rules DONE GL_ARB_gpu_shader_fp64 started (Dave) GL_ARB_sample_shading DONE (i965, nv50, nvc0, radeonsi) @@ -125,13 +125,13 @@ GL 4.1, GLSL 4.10: GL_ARB_get_program_binary DONE (0 binary formats) GL_ARB_separate_shader_objects DONE (all drivers) GL_ARB_shader_precision started (Micah) - GL_ARB_vertex_attrib_64bit not started + GL_ARB_vertex_attrib_64bit started (Dave) GL_ARB_viewport_array DONE (i965, nv50, nvc0, r600) GL 4.2, GLSL 4.20: - GL_ARB_texture_compression_bptc not started + GL_ARB_texture_compression_bptc DONE (i965, nvc0, r600, radeonsi) GL_ARB_compressed_texture_pixel_storage DONE (all drivers) GL_ARB_shader_atomic_counters DONE (i965) GL_ARB_texture_storage DONE (all drivers) @@ -147,7 +147,7 @@ GL 4.2, GLSL 4.20: GL 4.3, GLSL 4.30: GL_ARB_arrays_of_arrays started (Timothy) - GL_ARB_ES3_compatibility DONE (i965) + GL_ARB_ES3_compatibility DONE (all drivers that support GLSL 3.30) GL_ARB_clear_buffer_object DONE (all drivers) GL_ARB_compute_shader started (currently stalled) GL_ARB_copy_image DONE (i965) @@ -182,6 +182,38 @@ GL 4.4, GLSL 4.40: GL_ARB_texture_stencil8 not started GL_ARB_vertex_type_10f_11f_11f_rev DONE (i965, nv50, nvc0, r600, radeonsi) +GL 4.5, GLSL 4.50: + + GL_ARB_ES3_1_compatibility not started + GL_ARB_clip_control not started + GL_ARB_conditional_render_inverted DONE (i965, nvc0, softpipe, llvmpipe) + GL_ARB_cull_distance not started + GL_ARB_derivative_control DONE (i965, nv50, nvc0, r600) + GL_ARB_direct_state_access not started + GL_ARB_get_texture_sub_image started (Brian Paul) + GL_ARB_shader_texture_image_samples not started + GL_ARB_texture_barrier DONE (nv50, nvc0, r300, r600, radeonsi) + GL_KHR_context_flush_control not started + GL_KHR_robust_buffer_access_behavior not started + GL_KHR_robustness 90% done (the ARB variant) + +These are the extensions cherry-picked to make GLES 3.1 +GLES3.1, GLSL ES 3.1 + GL_ARB_arrays_of_arrays started (Timothy) + GL_ARB_compute_shader started (currently stalled) + GL_ARB_explicit_uniform_location DONE (all drivers that support GLSL) + GL_ARB_framebuffer_no_attachments not started + GL_ARB_program_interface_query not started + GL_ARB_shader_atomic_counters DONE (i965) + GL_ARB_shader_image_load_store in progress (curro) + GL_ARB_shader_storage_buffer_object not started + GL_ARB_separate_shader_objects DONE (all drivers) + GL_ARB_stencil_texturing DONE (i965/gen8+, nv50, nvc0, r600, radeonsi) + GL_ARB_vertex_attrib_binding DONE (all drivers) + GS5 Enhanced textureGather DONE (i965, nvc0, r600, radeonsi) + GS5 Packing/bitfield/conversion functions DONE (i965, nvc0, r600) + GL_EXT_shader_integer_mix DONE (all drivers that support GLSL) + More info about these features and the work involved can be found at http://dri.freedesktop.org/wiki/MissingFunctionality diff --git a/mesalib/docs/autoconf.html b/mesalib/docs/autoconf.html index d4e8a35d8..2ef8c63db 100644 --- a/mesalib/docs/autoconf.html +++ b/mesalib/docs/autoconf.html @@ -97,20 +97,22 @@ shared libraries in a single pass.</p> <dt><code>CC, CFLAGS, CXX, CXXFLAGS</code></dt> <dd><p>These environment variables control the C and C++ compilers used during the build. By default, -<code>gcc</code> and <code>g++</code> are used with the options -<code>"-g -O2"</code>.</p> +<code>gcc</code> and <code>g++</code> are used and the debug/optimisation +level is left unchanged.</p> </dd> <dt><code>LDFLAGS</code></dt> <dd><p>An environment variable specifying flags to -pass when linking programs. These are normally empty, but can be used -to direct the linker to use libraries in nonstandard directories. For -example, <code>LDFLAGS="-L/usr/X11R6/lib"</code>.</p> +pass when linking programs. These should be empty and +<code>PKG_CONFIG_PATH</code> is recommended to be used instead. If needed +it can be used to direct the linker to use libraries in nonstandard +directories. For example, <code>LDFLAGS="-L/usr/X11R6/lib"</code>.</p> </dd> <dt><code>PKG_CONFIG_PATH</code></dt> -<dd><p>When available, the -<code>pkg-config</code> utility is used to search for external libraries +<dd><p>The +<code>pkg-config</code> utility is a hard requirement for cofiguring and +building mesa. It is used to search for external libraries on the system. This environment variable is used to control the search path for <code>pkg-config</code>. For instance, setting <code>PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig</code> will search for @@ -135,14 +137,32 @@ one of these architectures is detected. This option ensures that assembly will not be used.</p> </dd> -<dt><code>--enable-32-bit</code></dt> -<dt><code>--enable-64-bit</code></dt> -<dd><p>By default, the build will compile code as directed by the environment -variables -<code>CC</code>, <code>CFLAGS</code>, etc. If the compiler is -<code>gcc</code>, these options offer a helper to add the compiler flags -to force 32- or 64-bit code generation as used on the x86 and x86_64 -architectures. Note that these options are mutually exclusive.</p> +<dt><code>--build=</code></dt> +<dt><code>--host=</code></dt> +<dd><p>By default, the build will compile code for the architecture that +it's running on. In order to build cross-compile Mesa on a x86-64 machine +that is to run on a i686, one would need to set the options to:</p> + +<p><code>--build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu</code></p> + +Note that these can vary from distribution to distribution. For more +information check with the +<a href="https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html"> +autoconf manual</a>. +Note that you will need to correctly set <code>PKG_CONFIG_PATH</code> as well. + + +<p>In some cases a single compiler is capable of handling both architectures +(multilib) in that case one would need to set the <code>CC,CXX</code> variables +appending the correct machine options. Seek your compiler documentation for +further information - +<a href="https://gcc.gnu.org/onlinedocs/gcc/Submodel-Options.html"> gcc +machine dependent options</a></p> + +<p>In addition to specifying correct <code>PKG_CONFIG_PATH</code> for the target +architecture, the following should be sufficient to configure multilib Mesa</p> + +<code>./configure CC="gcc -m32" CXX="g++ -m32" --build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu ...</code> </dd> </dl> @@ -194,7 +214,9 @@ kernel DRM modules are not available. <dt><code>--enable-glx-tls</code> <dd><p> Enable Thread Local Storage (TLS) in GLX. -<dt><code>--with-expat=DIR</code> <dd> The DRI-enabled libGL uses expat to +<dt><code>--with-expat=DIR</code> +<dd><p><strong>DEPRECATED</strong>, use <code>PKG_CONFIG_PATH</code> instead.</p> +<p>The DRI-enabled libGL uses expat to parse the DRI configuration files in <code>/etc/drirc</code> and <code>~/.drirc</code>. This option allows a specific expat installation to be used. For example, <code>--with-expat=/usr/local</code> will diff --git a/mesalib/docs/devinfo.html b/mesalib/docs/devinfo.html index a947b0d39..8d20eea3c 100644 --- a/mesalib/docs/devinfo.html +++ b/mesalib/docs/devinfo.html @@ -218,15 +218,93 @@ commit ID of the commit of interest (as it appears in the mesa master branch). The latest set of patches that have been nominated, accepted, or rejected for the upcoming stable release can always be seen on the -<a href=http://cworth.org/~cworth/mesa-stable-queue/">Mesa Stable Queue</a> +<a href="http://cworth.org/~cworth/mesa-stable-queue/">Mesa Stable Queue</a> page. -<h2>Cherry-picking candidates for a stable branch</h2> +<h2>Criteria for accepting patches to the stable branch</h2> -<p> -Please use <code>git cherry-pick -x <commit></code> for cherry-picking a commit -from master to a stable branch. -</p> +Mesa has a designated release manager for each stable branch, and the release +manager is the only developer that should be pushing changes to these +branches. Everyone else should simply nominate patches using the mechanism +described above. + +The stable-release manager will work with the list of nominated patches, and +for each patch that meets the crtieria below will cherry-pick the patch with: +<code>git cherry-pick -x <commit></code>. The <code>-x</code> option is +important so that the picked patch references the comit ID of the original +patch. + +The stable-release manager may at times need to force-push changes to the +stable branches, for example, to drop a previously-picked patch that was later +identified as causing a regression). These force-pushes may cause changes to +be lost from the stable branch if developers push things directly. Consider +yourself warned. + +The stable-release manager is also given broad discretion in rejecting patches +that have been nominated for the stable branch. The most basic rule is that +the stable branch is for bug fixes only, (no new features, no +regressions). Here is a non-exhaustive list of some reasons that a patch may +be rejected: + +<ul> + <li>Patch introduces a regression. Any reported build breakage or other + regression caused by a particular patch, (game no longer work, piglit test + changes from PASS to FAIL), is justification for rejecting a patch.</li> + + <li>Patch is too large, (say, larger than 100 lines)</li> + + <li>Patch is not a fix. For example, a commit that moves code around with no + functional change should be rejected.</li> + + <li>Patch fix is not clearly described. For example, a commit message + of only a single line, no description of the bug, no mention of bugzilla, + etc.</li> + + <li>Patch has not obviously been reviewed, For example, the commit message + has no Reviewed-by, Signed-off-by, nor Tested-by tags from anyone but the + author.</li> + + <li>Patch has not already been merged to the master branch. As a rule, bug + fixes should never be applied first to a stable branch. Patches should land + first on the master branch and then be cherry-picked to a stable + branch. (This is to avoid future releases causing regressions if the patch + is not also applied to master.) The only things that might look like + exceptions would be backports of patches from master that happen to look + significantly different.</li> + + <li>Patch depends on too many other patches. Ideally, all stable-branch + patches should be self-contained. It sometimes occurs that a single, logical + bug-fix occurs as two separate patches on master, (such as an original + patch, then a subsequent fix-up to that patch). In such a case, these two + patches should be squashed into a single, self-contained patch for the + stable branch. (Of course, if the squashing makes the patch too large, then + that could be a reason to reject the patch.)</li> + + <li>Patch includes new feature development, not bug fixes. New OpenGL + features, extensions, etc. should be applied to Mesa master and included in + the next major release. Stable releases are intended only for bug fixes. + + Note: As an exception to this rule, the stable-release manager may accept + hardware-enabling "features". For example, backports of new code to support + a newly-developed hardware product can be accepted if they can be reasonably + determined to not have effects on other hardware.</li> + + <li>Patch is a performance optimization. As a rule, performance patches are + not candidates for the stable branch. The only exception might be a case + where an application's performance was recently severely impacted so as to + become unusable. The fix for this performance regression could then be + considered for a stable branch. The optimization must also be + non-controversial and the patches still need to meet the other criteria of + being simple and self-contained</li> + + <li>Patch introduces a new failure mode (such as an assert). While the new + assert might technically be correct, for example to make Mesa more + conformant, this is not the kind of "bug fix" we want in a stable + release. The potential problem here is that an OpenGL program that was + previously working, (even if technically non-compliant with the + specification), could stop working after this patch. So that would be a + regression that is unaacceptable for the stable branch.</li> +</ul> <h2>Making a New Mesa Release</h2> @@ -237,64 +315,205 @@ These are the instructions for making a new Mesa release. <h3>Get latest source files</h3> <p> Use git to get the latest Mesa files from the git repository, from whatever -branch is relevant. +branch is relevant. This document uses the convention X.Y.Z for the release +being created, which should be created from a branch named X.Y. +</p> + +<h3>Perform basic testing</h3> +<p> +The release manager should, at the very least, test the code by compiling it, +installing it, and running the latest piglit to ensure that no piglit tests +have regressed since the previous release. +</p> + +<p> +The release manager should do this testing with at least one hardware driver, +(say, whatever is contained in the local development machine), as well as on +both Gallium and non-Gallium software drivers. The software testing can be +performed by running piglit with the following environment-variable set: +</p> + +<pre> +LIBGL_ALWAYS_SOFTWARE=1 +</pre> + +And Gallium vs. non-Gallium software drivers can be obtained by using the +following configure flags on separate builds: + +<pre> +--with-dri-drivers=swrast +--with-gallium-drivers=swrast +</pre> + +<p> +Note: If both options are given in one build, both swrast_dri.so drivers will +be compiled, but only one will be installed. The following command can be used +to ensure the correct driver is being tested: </p> +<pre> +LIBGL_ALWAYS_SOFTWARE=1 glxinfo | grep "renderer string" +</pre> + +If any regressions are found in this testing with piglit, stop here, and do +not perform a release until regressions are fixed. -<h3>Verify and update version info in VERSION</h3> +<h3>Update version in file VERSION</h3> <p> -Create a docs/relnotes/x.y.z.html file. -The bin/bugzilla_mesa.sh and bin/shortlog_mesa.sh scripts can be used to -create the HTML-formatted lists of bugfixes and changes to include in the file. -Link the new docs/relnotes/x.y.z.html file into the main <a href="relnotes.html">relnotes.html</a> file. +Increment the version contained in the file VERSION at Mesa's top-level, then +commit this change. </p> +<h3>Create release notes for the new release</h3> + <p> -Update <a href="index.html">docs/index.html</a>. +Create a new file docs/relnotes/X.Y.Z.html, (follow the style of the previous +release notes). Note that the sha256sums section of the release notes should +be empty at this point. </p> <p> -Tag the files with the release name (in the form <b>mesa-x.y</b>) -with: <code>git tag -s mesa-x.y -m "Mesa x.y Release"</code> -Then: <code>git push origin mesa-x.y</code> +Two scripts are available to help generate portions of the release notes: + +<pre> + ./bin/bugzilla_mesa.sh + ./bin/shortlog_mesa.sh +</pre> + +<p> +The first script identifies commits that reference bugzilla bugs and obtains +the descriptions of those bugs from bugzilla. The second script generates a +log of all commits. In both cases, HTML-formatted lists are printed to stdout +to be included in the release notes. </p> +<p> +Commit these changes +</p> -<h3>Make the tarballs</h3> +<h3>Make the release archives, signatures, and the release tag</h3> <p> -Make the distribution files. From inside the Mesa directory: +From inside the Mesa directory: <pre> ./autogen.sh - make tarballs + make -j1 tarballs </pre> <p> -After the tarballs are created, the md5 checksums for the files will -be computed. -Add them to the docs/relnotes/x.y.html file. +After the tarballs are created, the sha256 checksums for the files will +be computed and printed. These will be used in a step below. </p> <p> -Copy the distribution files to a temporary directory, unpack them, -compile everything, and run some demos to be sure everything works. +It's important at this point to also verify that the constructed tar file +actually builds: </p> -<h3>Update the website and announce the release</h3> +<pre> + tar xjf MesaLib-X.Y.Z.tar.bz2 + cd Mesa-X.Y.Z + ./configure --enable-gallium-llvm + make -j6 + make install +</pre> + <p> -Make a new directory for the release on annarchy.freedesktop.org with: -<br> -<code> -mkdir /srv/ftp.freedesktop.org/pub/mesa/x.y -</code> +Some touch testing should also be performed at this point, (run glxgears or +more involved OpenGL programs against the installed Mesa). </p> <p> -Basically, to upload the tarball files with: -<br> -<code> -rsync -avP -e ssh MesaLib-x.y.* USERNAME@annarchy.freedesktop.org:/srv/ftp.freedesktop.org/pub/mesa/x.y/ -</code> +Create detached GPG signatures for each of the archive files created above: +</p> + +<pre> + gpg --sign --detach MesaLib-X.Y.Z.tar.gz + gpg --sign --detach MesaLib-X.Y.Z.tar.bz2 + gpg --sign --detach MesaLib-X.Y.Z.zip +</pre> + +<p> +Tag the commit used for the build: +</p> + +<pre> + git tag -s mesa-X.Y.X -m "Mesa X.Y.Z release" +</pre> + +<p> +Note: It would be nice to investigate and fix the issue that causes the +tarballs target to fail with multiple build process, such as with "-j4". It +would also be nice to incorporate all of the above commands into a single +makefile target. And instead of a custom "tarballs" target, we should +incorporate things into the standard "make dist" and "make distcheck" targets. +</p> + +<h3>Add the sha256sums to the release notes</h3> + +<p> +Edit docs/relnotes/X.Y.Z.html to add the sha256sums printed as part of "make +tarballs" in the previous step. Commit this change. +</p> + +<h3>Push all commits and the tag creates above</h3> + +<p> +This is the first step that cannot easily be undone. The release is going +forward from this point: +</p> + +<pre> + git push origin X.Y --tags +</pre> + +<h3>Install the release files and signatures on the distribution server</h3> + +<p> +The following commands can be used to copy the release archive files and +signatures to the freedesktop.org server: +</p> + +<pre> + scp MesaLib-X.Y.Z* people.freedesktop.org: + ssh people.freedesktop.org + cd /srv/ftp.freedesktop.org/pub/mesa + mkdir X.Y.Z + cd X.Y.Z + mv ~/MesaLib-X.Y.Z* . +</pre> + +<h3>Back on mesa master, andd the new release notes into the tree</h3> + +<p> +Something like the following steps will do the trick: +</p> + +<pre> + cp docs/relnotes/X.Y.Z.html /tmp + git checkout master + cp /tmp/X.Y.Z.html docs/relnotes + git add docs/relnotes/X.Y.Z.html +</pre> + +<p> +Also, edit docs/relnotes.html to add a link to the new release notes, and edit +docs/index.html to add a news entry. Then commit and push: +</p> + +<pre> + git commit -a -m "docs: Import X.Y.Z release notes, add news item." + git push origin +</pre> + +<h3>Update the mesa3d.org website</h3> + +<p> +NOTE: The recent release managers have not been performing this step +themselves, but leaving this to Brian Paul, (who has access to the +sourceforge.net hosting for mesa3d.org). Brian is more than willing to grant +the permission necessary to future release managers to do this step on their +own. </p> <p> @@ -306,13 +525,22 @@ sftp USERNAME,mesa3d@web.sourceforge.net </code> </p> + +<h3>Announce the release</h3> <p> Make an announcement on the mailing lists: <em>mesa-dev@lists.freedesktop.org</em>, -<em>mesa-users@lists.freedesktop.org</em> and <em>mesa-announce@lists.freedesktop.org</em> + +Follow the template of previously-sent release announcements. The following +command can be used to generate the log of changes to be included in the +release announcement: + +<pre> + git shortlog mesa-X.Y.Z-1..mesa-X.Y.Z +</pre> </p> </div> diff --git a/mesalib/docs/index.html b/mesalib/docs/index.html index 584bc4ec7..5fb55670e 100644 --- a/mesalib/docs/index.html +++ b/mesalib/docs/index.html @@ -16,6 +16,12 @@ <h1>News</h1> +<h2>August 19, 2014</h2> +<p> +<a href="relnotes/10.2.6.html">Mesa 10.2.6</a> is released. +This is a bug-fix release. +</p> + <h2>August 2, 2014</h2> <p> <a href="relnotes/10.2.5.html">Mesa 10.2.5</a> is released. diff --git a/mesalib/docs/relnotes.html b/mesalib/docs/relnotes.html index c7e0983a8..b84f498ca 100644 --- a/mesalib/docs/relnotes.html +++ b/mesalib/docs/relnotes.html @@ -21,6 +21,7 @@ The release notes summarize what's new or changed in each Mesa release. </p> <ul> +<li><a href="relnotes/10.2.6.html">10.2.6 release notes</a> <li><a href="relnotes/10.2.5.html">10.2.5 release notes</a> <li><a href="relnotes/10.2.4.html">10.2.4 release notes</a> <li><a href="relnotes/10.2.3.html">10.2.3 release notes</a> diff --git a/mesalib/docs/relnotes/10.2.6.html b/mesalib/docs/relnotes/10.2.6.html new file mode 100644 index 000000000..73c14164b --- /dev/null +++ b/mesalib/docs/relnotes/10.2.6.html @@ -0,0 +1,118 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> +<html lang="en"> +<head> + <meta http-equiv="content-type" content="text/html; charset=utf-8"> + <title>Mesa Release Notes</title> + <link rel="stylesheet" type="text/css" href="../mesa.css"> +</head> +<body> + +<div class="header"> + <h1>The Mesa 3D Graphics Library</h1> +</div> + +<iframe src="../contents.html"></iframe> +<div class="content"> + +<h1>Mesa 10.2.6 Release Notes / August 19, 2014</h1> + +<p> +Mesa 10.2.6 is a bug fix release which fixes bugs found since the 10.2.5 release. +</p> +<p> +Mesa 10.2.6 implements the OpenGL 3.3 API, but the version reported by +glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) / +glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being used. +Some drivers don't support all the features required in OpenGL 3.3. OpenGL +3.3 is <strong>only</strong> available if requested at context creation +because compatibility contexts are not supported. +</p> + +<h2>SHA256 checksums</h2> +<pre> +193314d2adba98e43697d726739ac46b4299aae324fa1821aa226890c28ac806 MesaLib-10.2.6.tar.bz2 +f7a45a5977b485eb95ac024205c584a0c112fe3951c2313c797579bb16a7a448 MesaLib-10.2.6.tar.gz +6d086d6fcda8f317adfaaae40011decf2f2e2dc80819c4a7a77c76f73512e8d8 MesaLib-10.2.6.zip +</pre> + +<h2>New features</h2> +<p>None</p> + +<h2>Bug fixes</h2> + +<p>This list is likely incomplete.</p> + +<ul> + +<li><a href="https://bugs.freedesktop.org/show_bug.cgi?id=81450">Bug 81450</a> - [BDW]Piglit spec_glsl-1.30_execution_tex-miplevel-selection_textureGrad_1DArray cases intel_do_flush_locked failed</li> + +</ul> + +<h2>Changes</h2> + +<p>Anuj Phogat (15):</p> +<ul> + <li>mesa: Fix error condition for valid texture targets in glTexStorage* functions</li> + <li>mesa: Turn target_can_be_compressed() in to a utility function</li> + <li>mesa: Add error condition for using compressed internalformat in glTexStorage3D()</li> + <li>mesa: Fix condition for using compressed internalformat in glCompressedTexImage3D()</li> + <li>mesa: Add utility function _mesa_is_enum_format_snorm()</li> + <li>mesa: Don't allow snorm internal formats in glCopyTexImage*() in GLES3</li> + <li>mesa: Add a helper function _mesa_is_enum_format_unsized()</li> + <li>mesa: Add a gles3 error condition for sized internalformat in glCopyTexImage*()</li> + <li>mesa: Add gles3 error condition for GL_RGBA10_A2 buffer format in glCopyTexImage*()</li> + <li>mesa: Add utility function _mesa_is_enum_format_unorm()</li> + <li>mesa: Add gles3 condition for normalized internal formats in glCopyTexImage*()</li> + <li>mesa: Allow GL_TEXTURE_CUBE_MAP target with compressed internal formats</li> + <li>meta: Use _mesa_get_format_bits() to get the GL_RED_BITS</li> + <li>egl: Fix OpenGL ES version checks in _eglParseContextAttribList()</li> + <li>meta: Fix datatype computation in get_temp_image_type()</li> +</ul> + +<p>Brian Paul (1):</p> +<ul> + <li>mesa: fix assertion in _mesa_drawbuffers()</li> +</ul> + +<p>Carl Worth (2):</p> +<ul> + <li>docs: Add sha256 sums to the 10.2.5 release notes</li> + <li>Update VERSION to 10.2.6</li> +</ul> + +<p>Ilia Mirkin (1):</p> +<ul> + <li>mesa/st: only convert AND(a, NOT(b)) into MAD when not using native integers</li> +</ul> + +<p>Jordan Justen (1):</p> +<ul> + <li>i965/miptree: Layout 1D Array as 2D Array with height of 1</li> +</ul> + +<p>Maarten Lankhorst (1):</p> +<ul> + <li>configure.ac: Do not require llvm on x32</li> +</ul> + +<p>Marek Olšák (4):</p> +<ul> + <li>st/mesa: fix blit-based partial TexSubImage for 1D arrays</li> + <li>radeon,r200: fix buffer validation after CS flush</li> + <li>radeonsi: fix a hang with instancing in Unigine Heaven/Valley on Hawaii</li> + <li>radeonsi: fix CMASK and HTILE allocation on Tahiti</li> +</ul> + +<p>Pali Rohár (1):</p> +<ul> + <li>configure: check for dladdr via AC_CHECK_FUNC/AC_CHECK_LIB</li> +</ul> + +<p>Roland Scheidegger (1):</p> +<ul> + <li>gallivm: fix up out-of-bounds level when using conformant out-of-bound behavior</li> +</ul> + +</div> +</body> +</html> diff --git a/mesalib/docs/relnotes/10.3.html b/mesalib/docs/relnotes/10.3.html index f023ca6dc..fa4ea234f 100644 --- a/mesalib/docs/relnotes/10.3.html +++ b/mesalib/docs/relnotes/10.3.html @@ -44,23 +44,32 @@ Note: some of the new features are only available with certain drivers. </p> <ul> +<li>GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe</li> +<li>GL_ARB_clear_texture on i965</li> <li>GL_ARB_compressed_texture_pixel_storage on all drivers</li> +<li>GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe</li> +<li>GL_ARB_derivative_control on i965, nv50, nvc0, r600</li> <li>GL_ARB_draw_indirect on nvc0, radeonsi</li> <li>GL_ARB_explicit_uniform_location (all drivers that support GLSL)</li> +<li>GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600</li> +<li>GL_ARB_gpu_shader5 on i965/gen7, nvc0</li> <li>GL_ARB_multi_draw_indirect on nvc0, radeonsi</li> <li>GL_ARB_sample_shading on radeonsi</li> +<li>GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe</li> <li>GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi</li> +<li>GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi</li> +<li>GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi</li> <li>GL_ARB_texture_cube_map_array on radeonsi</li> <li>GL_ARB_texture_gather on r600, radeonsi</li> <li>GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe</li> <li>GL_ARB_texture_query_lod on r600, radeonsi</li> <li>GL_ARB_viewport_array on nvc0</li> -<li>GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe</li> -<li>GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600</li> <li>GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600</li> -<li>GL_ARB_clear_texture on i965</li> +<li>GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe</li> +<li>GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe</li> <li>A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm)</li> +<li>Distribute the Khronos GL/glcorearb.h header file.</li> </ul> @@ -72,6 +81,8 @@ TBD. <ul> <li>Removed support for the GL_ATI_envmap_bumpmap extension</li> +<li>The hacky --enable-32/64-bit is no longer available in configure. To build +32/64 bit mesa refer to the default method recommended by your distribution</li> </ul> </div> |