Home
last modified time | relevance | path

Searched full:protecting (Results 1 – 25 of 88) sorted by relevance

1234

/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/
H A DTrustedComponent.interface.yaml24 - name: protecting
26 Objects that implement TrustedComponent can implement the "protecting"
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/
H A DIntrusion.interface.yaml39 Any mechanism protecting the chassis's internal hardwares from
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DBlueOak-1.0.08 this software as possible, while protecting contributors
H A DCC0-1.018 rights protecting against unfair competition in regards to a Work, subject to the limitations in pa…
19 rights protecting the extraction, dissemination, use and reuse of data in a Work;
H A DBSD-Protection15 … a wide variety of settings, both non-commercial and commercial, while protecting the work from ha…
H A DHippocratic-2.15 …patent rights, if any, in the Software, while ensuring attribution and protecting the Licensor fro…
H A DLGPL-2.0-or-later44 Our method of protecting your rights has two steps: (1) copyright the library,
340 this section has the sole purpose of protecting the integrity of the free
H A DLGPL-2.0-only47 Our method of protecting your rights has two steps: (1) copyright the library, and (2) offer you th…
235 …test validity of any such claims; this section has the sole purpose of protecting the integrity of…
/openbmc/qemu/hw/misc/
H A Dstm32l4x5_syscfg.c184 "%s: Write protecting SRAM2 isn't supported\n", in stm32l4x5_syscfg_write()
197 "%s: Write protecting SRAM2 isn't supported\n", in stm32l4x5_syscfg_write()
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/
H A DItem.interface.yaml113 reverse_name: protecting
/openbmc/u-boot/board/hisilicon/hikey/
H A DREADME136 INFO: BL2: TrustZone: protecting 16777216 bytes of memory at 0x3f000000
137 INFO: BL2: TrustZone: protecting 4194304 bytes of memory at 0x3e800000
/openbmc/qemu/hw/display/
H A Dqxl.h163 * protecting the pointer, such as a reference to the region that includes
/openbmc/qemu/include/system/
H A Dconfidential-guest-support.h4 * schemes for protecting guest memory or other state against a
/openbmc/qemu/docs/system/
H A Dsecrets.rst162 The only item that needs strongly protecting is the master key file.
/openbmc/qemu/replay/
H A Dreplay-internal.h123 /* Mutex functions for protecting replay log file and ensuring
/openbmc/docs/designs/
H A Dredfish-spdm-attestation.md71 protecting. Note, the "trusted component" in this doc refers to a trusted
98 which it is protecting. It should also be associated with the component
H A Dredfish-resource-supplement-for-pfr.md31 resiliency by protecting, detecting and recovering platform assets. Management
/openbmc/u-boot/test/py/tests/
H A Dtest_tpm2.py208 No authentication mechanism is used here, not protecting against packet
/openbmc/qemu/include/exec/
H A Dcpu-common.h77 * does not hold the BQL, it must have other means of protecting the
/openbmc/qemu/docs/devel/
H A Dlockcnt.rst104 This could be implemented simply by protecting the counter with the
/openbmc/qemu/include/block/
H A Dgraph-lock.h80 * the pointer. In most cases this is equivalent to actually protecting the
/openbmc/u-boot/Licenses/
H A Dlgpl-2.0.txt44 Our method of protecting your rights has two steps: (1) copyright
372 such claims; this section has the sole purpose of protecting the
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/
H A DFLTK93 Our method of protecting your rights has two steps: (1) copyright
421 such claims; this section has the sole purpose of protecting the
H A DMini-XML-License70 Our method of protecting your rights has two steps: (1) copyright
398 such claims; this section has the sole purpose of protecting the
/openbmc/qemu/include/qemu/
H A Djob.h337 * Take the mutex protecting the list of jobs and their status.
348 * Release the mutex protecting the list of jobs and their status.

1234