| /openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
| H A D | fix_missing_use_directives.patch | 14 use Bastille::API;
15 +use Bastille::API::AccountPermission;
16 use Bastille::API::FileContent;
17 use Bastille::API::ServiceAdmin;
26 use Bastille::API;
27 +use Bastille::API::AccountPermission;
28 use Bastille::API::HPSpecific;
29 use Bastille::API::ServiceAdmin;
30 use Bastille::API::FileContent;
38 use Bastille::API;
[all …]
|
| H A D | Miscellaneous.pm | 1 package Bastille::API::Miscellaneous;
5 use Bastille::API;
6 use Bastille::API::HPSpecific;
7 use Bastille::API::FileContent;
|
| H A D | fixed_defined_warnings.patch | 12 in API.pm.
21 Bastille/API.pm | 12 ++++++------
24 Index: Bastille/Bastille/API.pm
26 --- Bastille.orig/Bastille/API.pm 2008-09-14 19:56:53.000000000 -0400
27 +++ Bastille/Bastille/API.pm 2013-08-21 08:55:26.715950001 -0400
|
| H A D | simplify_B_place.patch | 7 Index: Bastille/Bastille/API.pm
9 --- Bastille.orig/Bastille/API.pm 2013-08-21 08:59:17.939950001 -0400
10 +++ Bastille/Bastille/API.pm 2013-08-21 08:59:30.983950001 -0400
|
| H A D | edit_usage_message.patch | 20 Index: Bastille/Bastille/API.pm
22 --- Bastille.orig/Bastille/API.pm 2013-08-25 08:15:40.266779002 -0400
23 +++ Bastille/Bastille/API.pm 2013-08-25 14:18:22.750778811 -0400
|
| /openbmc/u-boot/api/ |
| H A D | Kconfig | 1 menu "API" menu
3 config API config
4 bool "Enable U-Boot API"
7 This option enables the U-Boot API. See api/README for more information.
|
| H A D | README | 1 U-Boot machine/arch independent API for external apps
6 - there is a single entry point (syscall) to the API
18 - consumer application will recognize the API is available by searching
22 - the U-Boot integral part of the API is meant to be thin and non-intrusive,
43 - core API, integral part of U-Boot, mandatory
|
| /openbmc/openbmc/poky/meta/recipes-graphics/libva/ |
| H A D | libva.inc | 1 SUMMARY = "Video Acceleration (VA) API for Linux"
2 DESCRIPTION = "Video Acceleration API (VA API) is a library (libVA) \
3 and API specification which enables and provides access to graphics \
8 Media Accelerator) series of GPU hardware, the API is however not \
10 manufacturers can also freely use this API for hardware accelerated \
|
| H A D | libva-utils_2.22.0.bb | 4 and examples to exercise VA-API in accordance with the libva \
5 project.VA-API is an open-source library and API specification, \
|
| /openbmc/openbmc/poky/meta/recipes-devtools/log4cplus/ |
| H A D | log4cplus_2.1.2.bb | 1 SUMMARY = "log4cplus provides a simple C++ logging API for log management"
4 …g API providing thread-safe, flexible, and arbitrarily granular control over log management and co…
|
| /openbmc/qemu/docs/devel/ |
| H A D | qom-api.rst | 4 QEMU Object Model (QOM) API Reference
7 This is the complete API documentation for :ref:`qom`.
|
| H A D | tcg-plugins.rst | 15 API versioning
21 API should it need to do so. The best way to avoid this is to submit
22 your plugin upstream so they can be updated if/when the API changes.
24 All plugins need to declare a symbol which exports the plugin API
31 supported range of API versions.
35 current API versions supported by QEMU. The API version will be
36 incremented if new APIs are added. The minimum API version will be
165 Plugin API
168 The following API is generated from the inline documentation in
169 ``include/qemu/qemu-plugin.h``. Please ensure any updates to the API
|
| /openbmc/u-boot/doc/ |
| H A D | README.LED_display | 1 LED display internal API
4 This README describes the LED display API.
6 The API is defined by the include file include/led-display.h
|
| H A D | README.VSC3316-3308 | 1 This file contains API information of the initialization code written for
18 API Overview:
23 …This API programs VSC to interface with either two-wire or four-wire interface. In our case the in…
30 …This API configures the VSC3316 device for required connections. Connection through the VSC device…
41 …ed, 01.h value need to be written in 75.h (core configuration register), which is done by this API.
|
| /openbmc/pldm/docs/ |
| H A D | code_flows.md | 12 message. It can make use of a decode_foo_req() API, and doesn't have to perform
19 encode_foo_resp() API, and doesn't have to perform the serialization of the
30 use of an encode_foo_req() API.
39 a decode_foo_resp() API to deserialize the response message.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/opencl/ |
| H A D | opencl-headers_2024.10.24.bb | 1 SUMMARY = "OpenCL API Headers"
2 DESCRIPTION = "OpenCL compute API headers from Khronos Group"
|
| H A D | opencl-clhpp_2024.10.24.bb | 1 SUMMARY = "OpenCL API C++ bindings"
2 DESCRIPTION = "OpenCL API C++ bindings from Khronos"
|
| /openbmc/libpldm/docs/checklists/ |
| H A D | changes.md | 97 - **Public API**: Any definitions and declarations under `include/libpldm`.
112 - Incorrect use of public API functions is always an error condition, and is
163 Adding APIs to a library is a difficult task. Generally, once an API is exposed
164 in the library's ABI, any changes to the API risk breaking applications already
165 making use of it. To make sure we have more than one shot at getting an API
218 use in context _before_ preventing us from making changes to the API.
247 ## Adding a new API
272 - [ ] The API must abstract over the platform-specific types, and there are no
283 ### API design
293 requiring heap allocation in the implementation or splitting the API t
236 Naming macros, functions and typesChecklist for making changes to `libpldm`""Adding a new API global() argument
253 API designChecklist for making changes to `libpldm`""Adding a new API global() argument
310 ABI controlChecklist for making changes to `libpldm`""Adding a new API global() argument
319 Error handling and invariantsChecklist for making changes to `libpldm`""Adding a new API global() argument
336 ImplementationChecklist for making changes to `libpldm`""Adding a new API global() argument
357 TestingChecklist for making changes to `libpldm`""Adding a new API global() argument
362 MaintenanceChecklist for making changes to `libpldm`""Adding a new API global() argument
373 OEM/vendor-specific APIsChecklist for making changes to `libpldm`""Adding a new API global() argument
[all...] |
| /openbmc/u-boot/doc/driver-model/ |
| H A D | pmic-framework.txt | 63 the PMIC devices should also support this. By the pmic and regulator API's,
69 - Common I/O API - UCLASS_PMIC
73 - Common regulator API - UCLASS_REGULATOR
91 For detailed API description, please refer to the header file.
99 The 'pmic; command also supports the new API. So the pmic command can be enabled
127 For detailed API description, please refer to the header file.
135 The 'regulator' command also supports the new API. The command allow:
|
| /openbmc/libpldm/ |
| H A D | CONTRIBUTING.md | 97 - **Public API**: Any definitions and declarations under `include/libpldm`.
112 - Incorrect use of public API functions is always an error condition, and is
163 Adding APIs to a library is a difficult task. Generally, once an API is exposed
164 in the library's ABI, any changes to the API risk breaking applications already
165 making use of it. To make sure we have more than one shot at getting an API
218 use in context _before_ preventing us from making changes to the API.
247 ## Adding a new API
272 - [ ] The API must abstract over the platform-specific types, and there are no
283 ### API design argument
293 requiring heap allocation in the implementation or splitting the API t
249 Naming macros, functions and typesChecklist for making changes to `libpldm`""Adding a new API global() argument
340 ABI controlChecklist for making changes to `libpldm`""Adding a new API global() argument
349 Error handling and invariantsChecklist for making changes to `libpldm`""Adding a new API global() argument
366 ImplementationChecklist for making changes to `libpldm`""Adding a new API global() argument
387 TestingChecklist for making changes to `libpldm`""Adding a new API global() argument
392 MaintenanceChecklist for making changes to `libpldm`""Adding a new API global() argument
403 OEM/vendor-specific APIsChecklist for making changes to `libpldm`""Adding a new API global() argument
[all...] |
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm2/tpm2-pytss/ |
| H A D | python3-tpm2-pytss_2.3.0.bb | 1 DESCRIPTION = "TPM2 TSS Python bindings for Enhanced System API (ESYS), Feature API (FAPI), Marshal…
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | qtest.rst | 22 The QTest library is implemented by ``tests/qtest/libqtest.c`` and the API is
33 Libqos also offers the Qgraph API to increase each test coverage and
35 Refer to :ref:`qgraph` for Qgraph explanation and API.
42 2. Write the test code with the glib and libqtest/libqos API. See also existing
90 libqtest API reference
|
| /openbmc/bmcweb/docs/ |
| H A D | OEM_SCHEMAS.md | 4 implemented by OEMs. bmcweb does not expose a stable API for adding OEM
5 properties in a backward API compatible way for code that has not been merged to
20 OpenBMC's external Redfish API aims to be as compatible between systems as
32 a breaking change to an external API, given that clients are likely to be
36 have to break an API boundary to move to the standard implementation. Given the
37 effort it takes to break an API, it is much simpler to wait for the standard to
44 to positive API design changes up front, which increases the usefulness of the
49 show up in the public facing API as it exports a level of support that doesn't
81 validator and should follow redfish API design practices. We require OEM to have
|
| /openbmc/u-boot/Documentation/media/ |
| H A D | Makefile | 5 API = $(srctree)/include macro
20 $(BUILDDIR)/linker_lists.h.rst: ${API}/linker_lists.h ${PARSER} $(SRC_DIR)/linker_lists.h.rst.excep…
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/mrw/ |
| H A D | mrw-api-native.bb | 1 SUMMARY = "Phosphor OpenBMC machine readable workbook API modules"
2 DESCRIPTION = "The API for the MRW XML generated by the Serverwiz tool"
|