| /openbmc/qemu/include/crypto/ |
| H A D | afsplit.h | 32 * The core idea is to take a short piece of data (key material)
33 * and process it to expand it to a much larger piece of data.
100 * size, to form a larger piece of data @out, which is
122 * bytes in size, to form the original small piece of
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc_message_registry.readmefirst.md | 9 1. Messages should not be specific to a piece or type of hardware. Generally
11 message strings, unless that behavior is specific to that particular piece of
|
| /openbmc/bmcweb/redfish-core/include/ |
| H A D | sub_route_trie.hpp | 190 std::string piece(&c, 1); in add()
191 if (!this->nodes[idx].children.contains(piece)) in add()
194 this->nodes[idx].children.emplace(piece, newNodeIdx); in add()
196 idx = this->nodes[idx].children[piece]; in add()
183 std::string piece(&c, 1); add() local
|
| /openbmc/entity-manager/ |
| H A D | CONFIG_FORMAT.md | 6 configuration required to describe a given piece of hardware. As such, they are
21 reactors on a single piece of hardware, and will generally have less
24 2. Configuration files should trend toward one config file per physical piece of
26 given piece of hardware in a single file, even at the risk of duplicating
30 changes will be submitted. Having each individual piece of hardware in its
37 - Having one config file per piece of hardware makes it much easier and clear
38 for a user to determine if a piece of hardware is supported.
|
| /openbmc/bmcweb/http/routing/ |
| H A D | trie.hpp | 271 std::string piece(&c, 1); in add()
272 if (!nodes[idx].children.contains(piece)) in add()
275 nodes[idx].children.emplace(piece, newNodeIdx); in add()
277 idx = nodes[idx].children[piece]; in add()
264 std::string piece(&c, 1); add() local
|
| /openbmc/linux/Documentation/ABI/testing/ |
| D | sysfs-platform-dell-wmi-ddv | |
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/debian/ |
| H A D | throw-exception-on-unknown-os.patch | 5 guarauntee its functionality regarding that piece of code.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/debian/system/core/ |
| H A D | throw-exception-on-unknown-os.patch | 5 guarauntee its functionality regarding that piece of code.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Hardware.interface.yaml | 21 This ID could be used to identify the specific piece of hardware
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | linaro,optee-tz.txt | 3 OP-TEE is a piece of software using hardware features to provide a Trusted
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| D | index.rst | |
| /openbmc/linux/arch/sparc/include/uapi/asm/ |
| D | posix_types.h | |
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| D | mediatek,mt8186-fhctl.yaml | |
| /openbmc/linux/drivers/target/ |
| D | target_core_rd.h | |
| /openbmc/google-misc/subprojects/libcr51sign/ |
| H A D | README.md | 14 implement each piece of platform-specific functionality will be passed to the
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.yaml | |
| /openbmc/linux/arch/powerpc/platforms/85xx/ |
| D | qemu_e500.c | |
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | UPL-1.0 | 9 (b) any piece of software and/or hardware listed in the lrgrwrks.txt file if one is included with t…
|
| /openbmc/linux/arch/mips/pci/ |
| D | fixup-ip32.c | |
| /openbmc/u-boot/doc/driver-model/ |
| H A D | serial-howto.txt | 21 - Add the U_BOOT_DRIVER piece at the end (e.g. copy serial_s5p.c for example)
|
| H A D | i2c-howto.txt | 31 - Add the U_BOOT_DRIVER piece at the end (e.g. copy tegra_i2c.c for example)
|
| /openbmc/linux/arch/arm/mach-mvebu/ |
| D | pmsu_ll.S | |
| /openbmc/qemu/target/arm/ |
| H A D | idau.h | 20 * In the v8M architecture, the IDAU is a small piece of hardware
|
| /openbmc/ipmi-fru-parser/ |
| H A D | fru_area.hpp | 15 * IPMIFruArea represents a piece of a FRU that is accessible over IPMI.
|
| /openbmc/docs/designs/ |
| H A D | redfish-pcie.md | 67 piece that implements hardware scanning should use mechanisms, such as caching
|