docs: add release notes for 17.0.1

[mesa.git] / docs / egl.html

diff --git a/docs/egl.html b/docs/egl.html
index bc21c6c4894fc9fcc2537e9561f97209f805f701..17823c2b0fa9fcd0b680160af2949bad626fd5a1 100644 (file)
--- a/docs/egl.html
+++ b/docs/egl.html
@@ -18,8 +18,8 @@
 
 <p>The current version of EGL in Mesa implements EGL 1.4.  More information
 about EGL can be found at
-<a href="http://www.khronos.org/egl/">
-http://www.khronos.org/egl/</a>.</p>
+<a href="https://www.khronos.org/egl/">
+https://www.khronos.org/egl/</a>.</p>
 
 <p>The Mesa's implementation of EGL uses a driver architecture.  The main
 library (<code>libEGL</code>) is window system neutral.  It provides the EGL
@@ -44,7 +44,7 @@ the driver for your hardware.  For example</p>
 
 <p>The main library and OpenGL is enabled by default.  The first two options
 above enables <a href="opengles.html">OpenGL ES 1.x and 2.x</a>.  The last two
-options enables the listed classic and and Gallium drivers respectively.</p>
+options enables the listed classic and Gallium drivers respectively.</p>
 
 </li>
 
@@ -83,15 +83,17 @@ drivers will be installed to <code>${libdir}/egl</code>.</p>
 <p>List the platforms (window systems) to support.  Its argument is a comma
 separated string such as <code>--with-egl-platforms=x11,drm</code>.  It decides
 the platforms a driver may support.  The first listed platform is also used by
-the main library to decide the native platform: the platform the EGL native
+the main library to decide the native platform: this defines EGL native
 types such as <code>EGLNativeDisplayType</code> or
-<code>EGLNativeWindowType</code> defined for.</p>
+<code>EGLNativeWindowType</code>.</p>
 
 <p>The available platforms are <code>x11</code>, <code>drm</code>,
 <code>wayland</code>, <code>surfaceless</code>, <code>android</code>,
-and <code>haiku</code>.  The <code>android</code> platform
-can only be built as a system component, part of AOSP, while the
-<code>haiku</code> platform can only be built with SCons.
+and <code>haiku</code>.
+The <code>android</code> platform can either be built as a system
+component, part of AOSP, using <code>Android.mk</code> files, or
+cross-compiled using appropriate <code>configure</code> options.
+The <code>haiku</code> platform can only be built with SCons.
 Unless for special needs, the build system should
 select the right platforms automatically.</p>