Home
last modified time | relevance | path

Searched +full:implementation +full:- +full:defined (Results 1 – 25 of 839) sorted by relevance

12345678910>>...34

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/abseil-cpp/abseil-cpp/
H A D0004-abseil-ppc-fixes.patch6 An all-in-one patch that fixes several issues:
8 1) UnscaledCycleClock not fully implemented for ppc*-musl (disabled on musl)
9 2) powerpc stacktrace implementation only works on glibc (disabled on musl)
10 3) powerpc stacktrace implementation has ppc64 assumptions (fixed)
15 Upstream-Status: Pending
17 Signed-off-by: Khem Raj <raj.khem@gmail.com>
18 ---
19 absl/base/internal/unscaledcycleclock.cc | 4 ++--
20 absl/base/internal/unscaledcycleclock_config.h | 3 ++-
21 absl/debugging/internal/examine_stack.cc | 8 +++++++-
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/
H A DVoltageRegulatorMode.interface.yaml3 Control.VoltageRegulatorProfile.Supported is read only. Implementation of
5 where the VR has a well defined default, implementations should place the
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
22 - name: Supported
25 - readonly
27 An implementation specific list of supported modes that the voltage
30 - name: Selected
H A DMinimumShipLevel.interface.yaml2 'An implementation may provide a single instance of MinimumShipLevelRequired
5 The definition of enforcement of this setting is implementation defined.'
8 - name: MinimumShipLevelRequired
11 'A user has requested that the implementation specific requirements
/openbmc/phosphor-gpio-monitor/
H A DREADME.md5 ### `phosphor-gpio-monitor`
8 take action if requested. This implementation uses GPIO keys and only supports
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
16 defined in config based on gpio state change. It uses libgpiod library.
20 New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line
21 monitoring in single instance of phosphor-multi-gpio-monitor running. It is very
23 line by name defined in kernel.
27 There is a phosphor-multi-gpio-monitor.json file that defines details of GPIOs
34 2. LineName: this is the line name defined in device tree for specific gpio
[all …]
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-grpcio/
H A Dabseil-ppc-fixes.patch3 Date: Sat, 13 Mar 2021 10:26:25 -0800
4 Subject: [PATCH] An all-in-one patch that fixes several issues:
6 1) UnscaledCycleClock not fully implemented for ppc*-musl (disabled on musl)
7 2) powerpc stacktrace implementation only works on glibc (disabled on musl)
8 3) powerpc stacktrace implementation has ppc64 assumptions (fixed)
13 Upstream-Status: Pending
14 Signed-off-by: Khem Raj <raj.khem@gmail.com>
15 Signed-off-by: Xu Huan <xuhuan.fnst@fujitsu.com>
16 Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
17 ---
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/
H A DMeetsMinimumShipLevel.interface.yaml4 meet an implementation defined minimum level for shipment requirement.
11 - name: MeetsMinimumShipLevel
14 'The inventory item meets the implementation defined minimum ship
/openbmc/docs/designs/mctp/
H A Dmctp.md8 BMC. This is primarily IPMI-based, but also includes a few hardware-specific
9 side-channels, like hiomap. On OpenPOWER hardware at least, we've definitely
23 these; we currently have BT and KCS (both defined as part of the IPMI 2.0
27 attempted, but not in a cross-implementation manner so far. This does not
31 layer bindings for the actual transport of MCTP packets. These are defined by
40 ![MCTP Diagram](mctp-standards.svg)
45 stack needing to be aware of the hardware implementation. These higher levels
46 only need to be aware that they are communicating with a certain entity, defined
48 that communicates over MCTP - for example, the host device, the BMC, or any
49 other system peripheral - static or hot-pluggable.
[all …]
/openbmc/u-boot/arch/m68k/lib/
H A Dcache.c1 // SPDX-License-Identifier: GPL-2.0+
16 /* Must be implemented for all M68k processors with copy-back data cache */ in flush_cache()
35 #if defined(CONFIG_CF_V4) || defined(CONFIG_CF_V4E) in icache_enable()
38 #if defined(CONFIG_CF_V4E) in icache_enable()
57 #if defined(CONFIG_CF_V4) || defined(CONFIG_CF_V4E) in icache_disable()
60 #if defined(CONFIG_CF_V4E) in icache_disable()
90 #if defined(CONFIG_CF_V4) || defined(CONFIG_CF_V4E) in dcache_enable()
93 #if defined(CONFIG_CF_V4E) in dcache_enable()
111 #if defined(CONFIG_CF_V4) || defined(CONFIG_CF_V4E) in dcache_disable()
114 #if defined(CONFIG_CF_V4E) in dcache_disable()
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/
H A DCreate.interface.yaml5 Any OpenBMC implementation should provide one implementation of
7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
16 - name: AdditionalData
20 this case should be an implementation specific enum defined for
23 enum-format string is required to come from a parallel class
34 - name: Path
41 - xyz.openbmc_project.Common.File.Error.Open
42 - xyz.openbmc_project.Common.File.Error.Write
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-dbs/mongodb/mongodb/
H A D0001-Mark-one-of-strerror_r-implementation-glibc-specific.patch3 Date: Mon, 23 Sep 2019 12:31:31 -0700
4 Subject: [PATCH] Mark one of strerror_r implementation glibc specific
9 Upstream-Status: Pending
11 Signed-off-by: Khem Raj <raj.khem@gmail.com>
12 ---
13 src/mongo/util/errno_util.cpp | 2 +-
14 1 file changed, 1 insertion(+), 1 deletion(-)
16 diff --git a/src/mongo/util/errno_util.cpp b/src/mongo/util/errno_util.cpp
18 --- a/src/mongo/util/errno_util.cpp
20 @@ -61,7 +61,7 @@ std::string errnoWithDescription(int errNumber) {
[all …]
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md16 - A class of failure exists where a BMC service has entered a failed state but
18 - A class of failure exists under which we can attempt debug data collection
21 This proposal argues for and proposes a software-driven debug data capture and
26 By necessity, BMCs are not self-contained systems. BMCs exist to service the
27 needs of both the host system by providing in-band platform services such as
29 out-of-band system management interfaces such as error reporting, platform
35 are usually a domain-specific Linux distributions with complex or highly coupled
40 recovery in the face of well-defined error conditions, but the need to mitigate
41 ill-defined error conditions or entering unintended software states remains.
60 As the state transformations to enter the ill-defined or unintended software
[all …]
H A Devent-logging.md3 Author: [Patrick Williams][patrick-email] `<stwcx>`
5 [patrick-email]: mailto:patrick@stwcx.xyz
13 There is currently not a consistent end-to-end error and event reporting design
15 primarily using phosphor-logging and one using rsyslog, both of which have gaps
17 end-to-end design handling both errors and tracing events which facilitate
30 be "DIMM-A0 encountered an uncorrectable ECC error" or "System boot successful".
36 temperature threshold exceeded: ["temperature threshold exceeded"][HPE-Example]
37 and ["Temperature #0x30 Upper Critical going high"][Oracle-Example]. There is
45 reference][Registry-Example] from the DMTF gives this example:
84 Within OpenBMC, there is currently a [limited design][existing-design] for this
[all …]
/openbmc/u-boot/arch/arm/cpu/armv8/
H A DKconfig15 bool "Enable multiple CPUs to enter into U-Boot"
21 CPUECTLR_EL1.SMPEN bit before U-Boot.
33 or when CPU implementation doesn't include that register.
36 bool "Support spin-table enable method"
39 Say Y here to support "spin-table" enable method for booting Linux.
42 - Specify enable-method = "spin-table" in each CPU node in the
44 - Bring secondary CPUs into U-Boot proper in a board specific
49 U-Boot automatically does:
50 - Set "cpu-release-addr" property of each CPU node
52 - Reserve the code for the spin-table and the release address
[all …]
/openbmc/qemu/docs/specs/
H A Dvirt-ctlr.rst4 The ``virt-ctrl`` device is a simple interface defined for the pure
5 virtual machine with no hardware reference implementation to allow the
8 The specification can evolve, the current state is defined as below.
12 Two 32bit registers are defined:
14 the features register (read-only, address 0x00)
19 the command register (write-only, address 0x04)
23 A basic command, no-op (0), is always present and can be used to test the
/openbmc/qemu/docs/devel/
H A Dwriting-monitor-commands.rst4 This document is a step-by-step guide on how to write new QMP commands using
8 into the QAPI framework implementation.
10 For an in-depth introduction to the QAPI framework, please refer to
11 :doc:`qapi-code-gen`. For the QMP protocol, see the
12 :doc:`/interop/qmp-spec`.
24 --------
34 added to the monitor/qmp-cmds.c file
47 -------
54 # qemu-system-TARGET [...] \
55 -chardev socket,id=qmp,port=4444,host=localhost,server=on \
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DMessage.v1_3_0.json3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
11 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
26 "description": "The human-readable message.",
27 "longDescription": "This property shall contain a human-readable message.",
42 …"longDescription": "This property shall contain a `MessageId`, as defined in the 'MessageId format…
49 …e. Services can replace the value defined in the message registry with a value more applicable to…
56 …operties contained in this object shall conform to the Redfish Specification-described requirement…
63 …"longDescription": "This property shall contain an array of RFC6901-defined JSON pointers indicati…
69 …tain the resolution of the message. Services can replace the resolution defined in the message re…
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DMessage.v1_3_0.json3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
11 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
26 "description": "The human-readable message.",
27 "longDescription": "This property shall contain a human-readable message.",
42 …"longDescription": "This property shall contain a `MessageId`, as defined in the 'MessageId format…
49 …e. Services can replace the value defined in the message registry with a value more applicable to…
56 …operties contained in this object shall conform to the Redfish Specification-described requirement…
63 …"longDescription": "This property shall contain an array of RFC6901-defined JSON pointers indicati…
69 …tain the resolution of the message. Services can replace the resolution defined in the message re…
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/
H A D0001-memory.h-Always-define-strlcpy-for-glibc-based-syste.patch3 Date: Wed, 7 Sep 2022 13:20:22 -0700
6 android-config.h file includes on compiler cmdline sets HAVE_STRLCPY
8 and also no problem when using musl since implementation exists for musl
10 the implementation provided by android-tools here. We are currently
11 using the in tree implementation for systems which do not provide it
13 Upstream-Status: Pending
15 Signed-off-by: Khem Raj <raj.khem@gmail.com>
16 ---
17 include/cutils/memory.h | 2 +-
18 1 file changed, 1 insertion(+), 1 deletion(-)
[all …]
/openbmc/u-boot/arch/arm/include/asm/
H A Dsetjmp.h1 /* SPDX-License-Identifier: GPL-2.0+ */
11 * This really should be opaque, but the EFI implementation wrongly
12 * assumes that a 'struct jmp_buf_data' is defined.
15 #if defined(__aarch64__)
18 u32 regs[10]; /* r4-r9, sl, fp, sp, lr */
/openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/
H A DAOM-Patent-License-1.07 grants Licensee a non-sublicensable, perpetual, worldwide, non-exclusive,
8 no-charge, royalty-free, irrevocable (except as expressly stated in this
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
42 enforce the terms of this License (including intervention in a third-party
[all …]
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-devtools/swagger-ui/
H A Dswagger-ui_5.18.2.bb1 SUMMARY = "Visually render documentation for an API defined with the OpenAPI"
4 interact with the API’s resources without having any of the implementation logic in place. \
6 …with the visual documentation making it easy for back end implementation and client side consumpti…
8 HOMEPAGE = "https://github.com/swagger-api/swagger-ui"
10 LICENSE = "Apache-2.0"
13 SRC_URI = "git://github.com/swagger-api/swagger-ui;branch=master;protocol=https"
17 CVE_STATUS[CVE-2016-1000229] = "fixed-version: fixed since 2.2.1"
22 install -d ${D}${localstatedir}/www/openapi/static
23 cp -r ${S}/dist/* ${D}${localstatedir}/www/openapi/static
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/augeas/augeas/
H A D0001-src-internal-Use-__GLIBC__-to-check-for-GNU-extentio.patch3 Date: Sat, 3 Sep 2022 01:23:28 -0700
5 implementation
7 __USE_GNU is defined by _GNU_SOURCE and configure explicitly sets this
10 have to check for libc implementation for this to be sure.
12 Upstream-Status: Pending
14 Signed-off-by: Khem Raj <raj.khem@gmail.com>
15 ---
16 src/internal.c | 2 +-
17 1 file changed, 1 insertion(+), 1 deletion(-)
19 diff --git a/src/internal.c b/src/internal.c
[all …]
/openbmc/u-boot/doc/
H A DREADME.ext41 U-Boot supports access of both ext2 and ext4 filesystems, either in read-only
2 mode or in read-write mode.
7 CONFIG_FS_EXT4 (for read-only)
8 CONFIG_EXT4_WRITE (for read-write)
10 Next, to select the ext2-related commands:
15 or ext4-related commands:
33 which automatically selects CONFIG_EXT4_WRITE if it wasn't defined
45 1. Check that the commands can be seen in the output of U-Boot help:
49 ext4load- load binary file from a Ext4 file system
50 ext4ls - list files in a directory (default /)
[all …]
/openbmc/libpldm/docs/checklists/
H A Dchanges.md5 - [Good Practices in Library Design, Implementation, and Maintenance - Ulrich
10 - [How Do I Make This Hard to Misuse? - Rusty Russell][rusty-api-scale-good]
12 [rusty-api-scal
336 ### Implementation global() subsection
[all...]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/cabextract/cabextract/
H A Dfix-fnmatch.patch1 From - Mon Jun 11 00:00:00 2024
7 because Autoconf didn't detect the working implementation and enabled fnmatch.c
16 Upstream-Status: Submitted [https://github.com/kyz/libmspack/pull/51]
17 Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
19 Index: cabextract-1.11/fnmatch.c
21 --- cabextract-1.11.orig/fnmatch.c
22 +++ cabextract-1.11/fnmatch.c
23 @@ -49,11 +49,6 @@ static const char rcsid[] =
27 -#if defined (_LIBC) || !defined (__GNU_LIBRARY__)
28 -
[all …]

12345678910>>...34