| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | IEC-Code-Components-EULA | 9 - The software license extends to modifications permitted under the relevant IEC standard.
13 relevant IEC standard may be referenced when claiming compliance with the relevant IEC
18 relevant IEC standard. Please reproduce this note if possible.”), may be placed in the code itself
|
| H A D | PDDL-1.0 | 14 …roperty law, this document first relinquishes the rights and waives the relevant rights and claims…
32 …ouring rights and similarly related sets of rights under the law of the relevant jurisdiction unde…
38 …) and any future updates as well as any similar rights available in the relevant jurisdiction unde…
90 …on inapplicable. If the dedication in Section 3.1 does not apply in the relevant jurisdiction unde…
96 To the extent possible in the relevant jurisdiction, the above waiver of rights and claims applies …
98 …the dedication and waiver in Sections 3.1 and 3.2 does not apply in the relevant jurisdiction unde…
100 …nd do not exclude any field of endeavour. To the extent possible in the relevant jurisdiction, the…
104 …r may have in the Work to the fullest extent possible by the law of the relevant jurisdiction unde…
106 …relevant jurisdiction is not possible, Licensor agrees not to assert any moral rights over the Wor…
136 …the relevant jurisdiction in which the Document terms are sought to be enforced. If the rights wai…
|
| H A D | ODC-By-1.0 | 33 …al part of the Contents, as well as any similar rights available in the relevant jurisdiction unde…
89 …nd do not exclude any field of endeavour. To the extent possible in the relevant jurisdiction, the…
121 … Database, including both in the Database or Derivative Database and in any relevant documentation;
125 …s structure, then You must include the notices in a location (such as a relevant directory) where …
141 …y have in the Database to the fullest extent possible by the law of the relevant jurisdiction unde…
143 …relevant jurisdiction is not possible, Licensor agrees not to assert any moral rights over the Dat…
195 …relevant jurisdiction in which the License terms are sought to be enforced. If the standard suite …
|
| H A D | ODbL-1.0 | 72 rights available in the relevant jurisdiction under Section 10.4.
188 the extent possible in the relevant jurisdiction, these rights may be
253 Database or Derivative Database and in any relevant documentation; and
260 location (such as a relevant directory) where users would be likely to
404 extent possible by the law of the relevant jurisdiction under Section
407 b. If waiver of moral rights under Section 5.1 a in the relevant
410 fullest extent possible by the law of the relevant jurisdiction under
536 the laws of the relevant jurisdiction in which the License terms are
538 applicable copyright law and Database Rights in the relevant
|
| H A D | SSH-OpenSSH | 14 * source code is used in accordance with the relevant license agreements
18 [However, none of that term is relevant at this point in time. All of
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | manifest.hpp | 14 Relevant, enumerator
31 {Expand::Relevant, "Relevant"},
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Manifest.v1_1_2.json | 10 "Relevant"
15 …"Relevant": "Expand relevant subordinate references. Relevant references are those that are tied … string
20 …"Relevant": "This value shall indicate that relevant subordinate references in the manifest respon… string
|
| H A D | PrivilegeRegistry.v1_1_5.json | 37 …"description": "The mapping between a resource type and the relevant privileges that accesses the …
38 …n": "This type shall describe a mapping between a resource type and the relevant privileges that a…
258 …"description": "The mappings between entities and the relevant privileges that access those entiti…
262 …n": "This property shall describe the mappings between entities and the relevant privileges that a…
|
| /openbmc/openbmc/meta-raspberrypi/.github/actions/docker-build/ |
| H A D | action.yml | 21 # relevant docker files because there is a chance that another PR (or
23 # version of the PR included change for the relevant docker image but a
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | layer-contents.md | 34 all the relevant boards.
40 all the relevant boards.
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 5 … layers. Companies, like Arm, may not wish to release a snapshot of the relevant “master” branches…
8 …sion, the best solution for us is to allow new hardware enablement (and relevant software features…
22 …eptions to this can be made, but must be sized appropriately and agreed to by the relevant parties.
42 # **Relevant Links**
|
| /openbmc/u-boot/doc/ |
| H A D | README.multi-dtb-fit | 12 The relevant DTBs are packed into a FIT (list provided by CONFIG__OF_LIST). The
27 The relevant DTBs are packed into a FIT. This FIT is automatically generated
30 CONFIG_SPL__OF_LIST is used to list the relevant DTBs.
|
| H A D | README.fsl-esdhc | 5 operating Qixis FPGA relevant registers. The STAT_PRES1 register has SDHC
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/images/ |
| H A D | corstone1000-recovery-image.bb | 6 # be disabled as it is not relevant for the Corstone1000.
|
| /openbmc/u-boot/drivers/ddr/marvell/axp/ |
| H A D | ddr3_axp_config.h | 92 * U_BOOT_START_ADDR, U_BOOT_SCRUB_SIZE - relevant when using ECC and need
141 * AUTO_DETECTION_SUPPORT - relevant ONLY for Marvell DB boards.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/cmake/cmake/ |
| H A D | 0001-CMakeDetermineCompilerABI-Strip-pipe-from-compile-fl.patch | 46 + # Avoid failing ABI detection caused by non-functionally relevant
59 + # contains the relevant compiler internals) becomes interweaved.
|
| /openbmc/docs/designs/ |
| H A D | nmi-dbus-interface.md | 11 Currently, servers that use OpenBMC cannot have the ability to capture relevant
21 has to recover the system with no relevant debug data captured.
|
| /openbmc/openpower-hw-diags/util/ |
| H A D | ffdc.hpp | 11 * Create FDDC files from journal messages of relevant executables
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/libiec61883/ |
| H A D | libiec61883_1.2.0.bb | 1 DESCRIPTION = "An implementation of the most relevant parts of IEC 61883 over \
|
| /openbmc/openbmc/meta-google/recipes-google/networking/gbmc-bridge/ |
| H A D | 50-gbmc-br.rules | 6 # those packets over the entire bridge. They are only relevant P2P.
|
| /openbmc/u-boot/arch/arm/mach-mvebu/serdes/a38x/ |
| H A D | ctrl_pex.c | 39 /* for PEX by4 - relevant for the first port only */ in hws_pex_config()
58 /* for PEX by4 - relevant for the first port only */ in hws_pex_config()
107 /* for PEX by4 - relevant for the first port only */ in hws_pex_config()
210 /* for PEX by4 - relevant for the first port only */ in hws_pex_config()
|
| /openbmc/qemu/qapi/ |
| H A D | rocker.json | 144 # depending if they're relevant to the flow key.
174 # depending if they're relevant to the flow mask.
201 # depending if they're relevant to the flow action.
294 # depending if they're relevant to the group type.
|
| /openbmc/u-boot/scripts/ |
| H A D | Makefile.extrawarn | 6 # W=1 - warnings that may be relevant and does not occur too often
7 # W=2 - warnings that occur quite often but may still be relevant
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | CMU-Tex | 10 paragraph (this paragraph not being relevant to the printed manual).
|
| /openbmc/u-boot/include/fsl-mc/ |
| H A D | fsl_dpio.h | 95 * destination in the relevant interface to this DPIO
106 * relevant only if 'channel_mode = DPIO_LOCAL_CHANNEL'
201 * relevant only if 'channel_mode = DPIO_LOCAL_CHANNEL'
|