|author||Daniel Stone <email@example.com>||Tue Mar 12 16:56:19 2019 +0000|
|committer||Daniel Stone <firstname.lastname@example.org>||Mon Apr 01 18:07:19 2019 +0100|
EXT_image_dma_buf_import_modifiers: Correct no-modifier-token behaviour Zero is a valid and explicit modifier token, meaning that the image is pitch-linear, i.e. no tiling or compression is applied. When no modifier is passed for dmabuf import, the implementation may assume the image is linear, but is not required to do so. Many drivers which supported tiling formats before modifiers (or which do not yet support modifiers) will determine the layout via other mechanisms, e.g. metadata held by the kernel. Fix the wording for the case where the user does not explicitly pass modifiers to state that the layout will be determined by the implementation, rather than stating the layout must be linear. Reported by @olvaffe
The EGL-Registry repository contains the EGL API and Extension Registry, including specifications, reference pages and reference cards, and the enumerant registry. It is also used as a backing store for the web view of the registry at https://www.khronos.org/registry/egl/ ; commits to the master branch of this repository will be reflected there.
In the past, the EGL registry was maintained in a public Subversion repository. The history in that repository has not been imported to github, but it is still available at https://cvs.khronos.org/svn/repos/registry/trunk/public/egl/ .
Interesting files in this repository include:
EGL enumerants are documented in api/egl.xml . New ranges can be allocated by proposing a pull request to master modifying this file, following the existing examples. Allocate ranges starting at the lowest free values available (search for “Reservable for future use”). Ranges are not officially allocated until your pull request is accepted into master. At that point you can use values from your assigned range for API extensions.
Extension specification documents can be added by proposing a pull request to master, adding the specification .txt file and related changes under extensions/<vendor>/filename.txt. Your pull request must also:
<extension>examples, search for “Next free extension number”, and use the lowest available extension number).
# Validate XML changes make validate # Verify headers build and are legal C make clobber make make tests
Sometimes extension text files contain inappropriate UTF-8 characters. They should be restricted to the ASCII subset of UTF-8 at present. They can be removed using the iconv Linux command-line tool via
iconv -c -f utf-8 -t ascii filename.txt
(see internal Bugzilla issue 16141 for more).
We may transition to an asciidoc-based extension specification format at some point.