| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | AOM-Patent-License-1.0 | 10 for sale, import or distribute any Implementation.
15 sell, offer for sale, import or distribute an Implementation under
17 this License, and must reproduce this License with any Implementation
21 root directory of the source code with its Implementation.
27 Implementation.
37 that any Implementation infringes Necessary Claims, any patent licenses
40 was in response to a corresponding suit regarding an Implementation first
45 1.4. Disclaimers. The Reference Implementation and Specification are provided
47 otherwise using the Reference Implementation or Specification is assumed
77 2.6. Implementation. "Implementation" means any implementation, including the
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | README.msl.md | 10 If an OpenBMC implementation provides MinimumShipLevelRequired, it must be on
21 namespace. Again, there are no requirements on what an implementation does when
24 ## Implementation Notes
30 Phosphor OpenBMC provides a basic implementation of MinimumShipLevelRequired. It
32 implementation is suitable for the hypothetical platform implementation
36 implementation would need to write an application that implements
40 contributing it to Phosphor OpenBMC. A possible implementation for the
|
| H A D | MinimumShipLevel.interface.yaml | 2 'An implementation may provide a single instance of MinimumShipLevelRequired
5 The definition of enforcement of this setting is implementation defined.'
11 'A user has requested that the implementation specific requirements
|
| H A D | VoltageRegulatorMode.interface.yaml | 3 Control.VoltageRegulatorProfile.Supported is read only. Implementation of
7 and sets the implementation specific mode for the voltage regulator to run
8 in. The definitions of said enum are implementation defined, as systems
27 An implementation specific list of supported modes that the voltage
|
| H A D | ThermalMode.interface.yaml | 6 Implementation of this interface populates the list of supported modes.
8 Implementation specific mode for the thermal control application
17 An implementation specific list of supported modes that the thermal
|
| H A D | Failover.interface.yaml | 3 implementation, this may reside on the 'from' or 'to' object (or both). The
4 'Options' method argument provides a mechanism to provide implementation
49 not be available. The checks it bypasses are implementation
|
| /openbmc/u-boot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 18 this is a simple implementation, only parses the 'fsl,pins'
32 this is a simple implementation, only parses the 'fsl,pins'
46 this is a simple implementation, only parses the 'fsl,pins'
59 is different from the linux one, this is a simple implementation,
74 is different from the linux one, this is a simple implementation,
88 is different from the linux one, this is a simple implementation,
103 this is a simple implementation, only parses the 'fsl,pins'
|
| /openbmc/u-boot/drivers/power/regulator/ |
| H A D | Kconfig | 50 This config enables implementation of driver-model regulator uclass
68 This config enables implementation of driver-model regulator uclass
75 This config enables implementation of driver-model regulator uclass
83 This config enables implementation of driver-model regulator
99 This config enables implementation of driver-model regulator uclass
107 This config enables implementation of driver-model regulator uclass
114 This config enables implementation of driver-model regulator uclass
122 This config enables implementation of driver-model regulator uclass
138 This enables implementation of driver-model regulator uclass
195 This enables implementation of driver-model regulator uclass
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 8 This document describes a userspace implementation of MCTP infrastructure,
35 The proposed implementation here is to produce an MCTP "library" which provides
48 implementation does not make sense to include in the platform-agnostic library.
50 The reason for a library is to allow the same MCTP implementation to be used in
61 implementation for running on a Linux environment may be implemented through
78 MCTP implementation without requiring major structural changes to handler
124 implementation contained within a single process, using the libmctp API directly
129 implementation of those application-level handlers (programming language,
148 For the OpenBMC MCTP daemon implementation, testing models would depend on the
|
| H A D | mctp.md | 27 attempted, but not in a cross-implementation manner so far. This does not
45 stack needing to be aware of the hardware implementation. These higher levels
61 packets by the transmit implementation, and reassembled at the receive
62 implementation.
99 There have been two main alternatives to an MCTP implementation in OpenBMC:
119 users of the MCTP messaging (eg, a PLDM implementation). These would somewhat
|
| /openbmc/service-config-manager/ |
| H A D | README.md | 9 implementation][bmcweb-implementation] of the Redfish NetworkProtocol schema.
13 [bmcweb-implementation]:
18 Implementation details are described in the [D-Bus interface README].
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pyjwt_2.10.1.bb | 1 SUMMARY = "JSON Web Token implementation in Python"
2 DESCRIPTION = "A Python implementation of JSON Web Token draft 32.\
3 Original implementation was written by https://github.com/progrium"
|
| /openbmc/gpioplus/src/gpioplus/internal/ |
| H A D | fd.hpp | 22 * @param[in] sys - Optional underlying syscall implementation
31 * @param[in] sys - Optional underlying syscall implementation
41 * @param[in] sys - Optional underlying syscall implementation
57 /** @brief Gets the syscall interface implementation
59 * @return The syscall implementation
|
| /openbmc/u-boot/arch/arm/lib/ |
| H A D | cache.c | 22 * Default implementation:
31 * Default implementation of enable_caches()
32 * Real implementation should be in platform code
41 /* An empty stub, real implementation should be in platform code */ in invalidate_dcache_range()
45 /* An empty stub, real implementation should be in platform code */ in flush_dcache_range()
|
| /openbmc/u-boot/drivers/usb/ulpi/ |
| H A D | Kconfig | 7 Select ULPI viewport (SoC-side interface to ULPI) implementation
14 Support generic ULPI Viewport implementation that is used on
20 Support ULPI Viewport implementation that is used on OMAP devices.
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | mock_services.hpp | 38 * Implementation of the Services interface using mock system services.
156 * Mock implementation of the ErrorLogging interface.
161 * Mock implementation of the Journal interface.
166 * Mock implementation of the PresenceService interface.
171 * Mock implementation of the Sensors interface.
176 * Mock implementation of the VPD interface.
|
| /openbmc/u-boot/doc/ |
| H A D | README.omap-ulpi-viewport | 12 implementation of "drivers/usb/ulpi/ulpi.c"
20 omap-ulpi-viewport implementation.
26 implementation which will do ulpi reset using the
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Community-Spec-1.0 | 41 Licensee’s Implementation of the Draft Specification, except for those
48 that are within Scope for Licensee’s Implementation of the Approved
55 license to its Necessary Claims for its Implementation, except for those
64 the Implementation;
69 provided with the Implementation; or
78 Implementation, any licenses granted under this License to the Licensee
80 to a claim against Licensee regarding an Implementation, or 2) that claim
86 an Implementation of the Specification or are enforceable or (ii) that
87 an Implementation of the Specification would not infringe intellectual
248 of the specific part(s) of the Draft Specification whose implementation
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | services.hpp | 96 * Implementation of the Services interface using standard BMC system services.
162 * Implementation of the ErrorLogging interface using D-Bus method calls.
167 * Implementation of the Journal interface that writes to the systemd
173 * Implementation of the PresenceService interface using D-Bus method calls.
178 * Implementation of the Sensors interface using D-Bus.
183 * Implementation of the VPD interface using D-Bus method calls.
|
| /openbmc/qemu/docs/devel/ |
| H A D | codebase.rst | 62 Block devices and `image formats<disk images>` implementation.
100 `User mode <user-mode>` implementation. Contains one folder per target
117 `Monitor <QEMU monitor>` implementation (HMP & QMP).
126 :ref:`TCG plugins <tcg-plugins>` core implementation. Plugins can be found in
135 `QAPI <qapi>` implementation.
137 QEMU Object implementation.
139 QEMU `Guest agent <qemu-ga>` implementation.
141 QEMU :ref:`Object model <qom>` implementation, with monitor associated commands.
143 QEMU :ref:`Record/replay <replay>` implementation.
156 QEMU `Semihosting <Semihosting>` implementation.
[all …]
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | propertywatch.hpp | 50 * Watch start interface implementation for PropertyWatch.
56 * Watch callback interface implementation for PropertyWatch.
140 /** @brief PropertyMatch implementation for PropertyWatchOfType.
149 /** @brief PropertyMatch implementation for PropertyWatchOfType.
159 /** @brief DBus agnostic implementation of interfacesAdded.
170 /** @brief PropertyMatch implementation for PropertyWatchOfType.
177 /** @brief DBus agnostic implementation of interfacesAdded.
|
| /openbmc/x86-power-control/ |
| H A D | README.md | 3 This repository contains an OpenBMC compliant implementation of power control
9 2. The implementation should either give the requested power control result, or
58 Caveats: This implementation does not currently implement the common targets
79 See <https://github.com/Intel-BMC/host-misc-comm-manager> for implementation
|
| /openbmc/pldm/pldmd/ |
| H A D | dbus_impl_pdr.hpp | 22 * @brief OpenBMC PLDM.PDR Implementation
23 * @details A concrete implementation for the
44 /** @brief Implementation for PdrIntf.FindStateEffecterPDR
52 /** @brief Implementation for PdrIntf.FindStateSensorPDR
|
| /openbmc/docs/designs/ |
| H A D | bmc-service-failure-debug-and-recovery.md | 71 cannot be detected by service state alone. Implementation of resiliency by way
89 covers implementation-specific data transports such as D-Bus, which requires a
160 implementation. Where available the options for external consumer tend to be, in
185 implementation should capture any appropriate data needed to debug the need to
196 or PLDM. In order to avoid these in the implementation of mechanism 2, the host
221 The implementation of recovery mechanism 1 is already accounted for in the
233 #### Analysis of Implementation Methods on Power10 Platforms
235 The implementation of recovery mechanism 2 is limited to using existing
286 external signal. The implementation should have no IPC dependencies or
290 A trivial implementation of the daemon is
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | Khronos | 16 If the binary is used as part of an OpenCL(TM) implementation, whether binary
17 is distributed together with or separately to that implementation, then
19 conformance process for that implementation, details at:
|