Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
api/ | 12-May-2024 | - | 7,446 | 3,236 | ||
extensions/KHR/ | 12-May-2024 | - | ||||
specs/ | 12-May-2024 | - | ||||
CODE_OF_CONDUCT.md | D | 12-May-2024 | 280 | 2 | 1 | |
LICENSE | D | 12-May-2024 | 1.1 KiB | 22 | 22 | |
OAT.xml | D | 12-May-2024 | 5.4 KiB | 87 | 31 | |
README.OpenSource | D | 12-May-2024 | 544 | 12 | 11 | |
README.md | D | 12-May-2024 | 1.7 KiB | 43 | 31 | |
index.php | D | 12-May-2024 | 3.4 KiB | 87 | 69 | |
registry.tcl | D | 12-May-2024 | 1.3 KiB | 37 | 26 |
README.OpenSource
1[ 2 { 3 "Name": "Khronos Group - OpenMAX IL", 4 "License": "MIT license", 5 "License File": "", 6 "Version Number": "1.1.2", 7 "Owner": "liufeihu@huawei.com", 8 "Upstream URL": "https://github.com/KhronosGroup/OpenMAX-IL-Registry/tree/main/api/1.1.2", 9 "Description": "The OpenMAX IL (Integration Layer) API defines a standardized media component interface to enable developers and platform providers to integrate and communicate with multimedia codecs implemented in hardware or software." 10 } 11] 12
README.md
1# OpenMAX-IL-Registry 2 3The OpenMAX-IL-Registry repository contains the OpenMAX IL API and Extension 4Registry, including specifications. 5 6It is also used as a backing store for the web view of the registry at 7https://www.khronos.org/registry/omxil/ ; commits to the main branch of 8this repository will be reflected there. 9 10**NOTE**: as of 2021-07-21, the default branch of this repository has 11been renamed from 'master' to 'main'. 12 13In the past, the OpenMAX IL registry was maintained in a public Subversion 14repository. The history in that repository has not been imported to github, 15but it is still available at 16https://cvs.khronos.org/svn/repos/registry/trunk/public/omxil/ . 17 18Interesting files in this repository include: 19 20* index.php - toplevel index page for the web view. This relies on PHP 21 include files found elsewhere on www.khronos.org and so is not very useful 22 in isolation. 23* api/ - OpenMAX IL header files 24* extensions/ - OpenMAX IL extension specifications, grouped into 25 vendor-specific subdirectories. 26* specs/ - OpenMAX IL specification documents. 27 28 29## Adding Extension Specifications 30 31Extension specification documents can be added by proposing a pull request 32adding the specification PDF (and related source markup, if 33available) files under extensions/<vendor>/ . You must also: 34 35* Allocate an extension number in registry.tcl (follow the existing 36 extension examples, search for "Next free extension number", and use the 37 lowest available extension number. 38* Include that extension number in the extension specification document. 39* Add a link from the extensions section of index.php to the extension 40 document, using the specified extension number, so it shows up in the web 41 view. 42 43