/openbmc/openbmc/poky/meta/recipes-devtools/rpm/files/ |
H A D | 0002-rpmio-rpmglob.c-avoid-using-GLOB_BRACE-if-undefined-.patch | 7 This addresses musl failures; if there is code out there relying on
|
/openbmc/bmcweb/include/ |
H A D | str_utility.hpp | 32 // Converts a character to lower case without relying on std::locale in asciiToLower()
|
/openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/files/ |
H A D | README.md | 20 relying solely on compile/link tests and pre-defined hints.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
H A D | Entry.interface.yaml | 37 of file in their own context, without relying on additional API calls.
|
/openbmc/qemu/docs/specs/ |
H A D | acpi_hw_reduced_hotplug.rst | 15 single interrupt for the GED device, relying on an IO memory region
|
/openbmc/qemu/hw/s390x/ |
H A D | s390-skeys.c | 247 * actually relying on this data. in qemu_s390_enable_skeys() 248 * 2) Relying on ram_size and allocating a big array is ugly. We should in qemu_s390_enable_skeys() 251 * 3) We only ever have a single S390SKeysState, so relying on in qemu_s390_enable_skeys()
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/usbip-tools/ |
H A D | usbip-tools.bb | 53 # Use local scripts before relying on inherited autotools
|
/openbmc/qemu/include/hw/ppc/ |
H A D | spapr_ovec.h | 23 * bits using only the documented values. This is done mainly by relying
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libmad/libmad/ |
H A D | add-pkgconfig.patch | 7 developers) have started relying on this support being present, causing
|
/openbmc/bmcweb/docs/ |
H A D | HEADERS.md | 13 Boost::beast at the time we ported took the same opinion, relying on header
|
/openbmc/docs/designs/ |
H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 33 HPE hardware uses different channels and data formats from the above, relying on 175 potential for non-HPE platform to make easy use of it. Relying on 'model' as 265 suggested relying on xyz.openbmc_project.Inventory.Decorator.Asset (for
|
/openbmc/qemu/docs/system/devices/ |
H A D | usb-u2f.rst | 4 U2F is an open authentication standard that enables relying parties
|
/openbmc/qemu/include/hw/acpi/ |
H A D | generic_event_device.h | 17 * method. Here, we use a single interrupt for the GED device, relying
|
/openbmc/u-boot/doc/ |
H A D | README.bcm7xxx | 17 - support for FIT-provided DTBs instead of relying on the
|
H A D | README.chromium | 227 a SPI driver with an empty probe() method, relying on whatever was set up
|
H A D | README.fdt-control | 211 which runs on your AT91 and OMAP boards, relying on an fdt to configure
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_efi_loader.py | 35 # static IP. If solely relying on DHCP, this variable may be omitted or set to
|
H A D | test_net.py | 33 # static IP. If solely relying on DHCP, this variable may be omitted or set to
|
/openbmc/phosphor-webui/app/common/styles/base/ |
H A D | forms.scss | 83 // TODO: Create state rulesets rather than relying on one off solutions
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-2.7.rst | 121 likely to be needed on modern systems. If you are relying on these
|
/openbmc/qemu/docs/system/ |
H A D | igvm.rst | 7 Guests to be calculated when the IGVM file is built, allowing a relying party to
|
/openbmc/qemu/docs/devel/ |
H A D | vfio-iommufd.rst | 10 the new iommufd interface is device-centric, relying on device fd and iommufd.
|
/openbmc/qemu/accel/tcg/ |
H A D | tcg-accel-ops-rr.c | 176 * This is done explicitly rather than relying on side-effects
|
/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | error_logging.cpp | 246 // Explicitly remove FFDC files rather than relying on FFDCFile destructor. in removeFFDCFiles()
|
/openbmc/qemu/docs/ |
H A D | glossary.rst | 152 virtual addresses by adding a specific offset, and relying on host MMU/OS
|