/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | openbmc_message_registry.readmefirst.md | 10 this involves not using terms like "CPU", "Drive", "Backplane", etc in the 20 This generally involves placing the substitution parameters in the
|
/openbmc/linux/Documentation/process/ |
H A D | adding-syscalls.rst | 26 - If the new functionality involves operations where the kernel notifies 130 If your new :manpage:`xyzzy(2)` system call involves a filename argument:: 150 If your new :manpage:`xyzzy(2)` system call involves a parameter describing an 154 If your new :manpage:`xyzzy(2)` system call involves privileged functionality, 256 way (see below), this involves a "common" entry (for x86_64 and x32) in 314 If the system call involves a structure that is laid out differently on 32-bit 407 This is arch-specific, but typically involves defining assembly entry points 467 involves a new userspace-visible structure, the corresponding header will need
|
/openbmc/openbmc/meta-ampere/meta-common/recipes-phosphor/watchdog/ |
H A D | phosphor-watchdog_%.bbappend | 4 # Ampere Mt. Jade power control involves different action during
|
/openbmc/linux/drivers/hwmon/pmbus/ |
H A D | ltc4286.c | 41 * Thus, the MBR setting which involves rsense should be shifted by 6 digits. 49 * Thus, the MBR setting which involves rsense should be shifted by 6 digits.
|
/openbmc/linux/Documentation/locking/ |
H A D | pi-futex.rst | 7 - in the user-space fastpath a PI-enabled futex involves no kernel work 79 mutexes involves no kernel work at all - they behave quite similarly to
|
/openbmc/linux/arch/powerpc/platforms/embedded6xx/ |
H A D | hlwd-pic.c | 27 * Enabling/disabling an interrupt line involves asserting/clearing 28 * the corresponding bit in IMR. ACK'ing a request simply involves
|
/openbmc/linux/Documentation/ABI/removed/ |
H A D | sysfs-bus-nfit | 11 involves determining the ARS capabilities of a given address
|
/openbmc/linux/Documentation/userspace-api/media/drivers/ |
H A D | st-vgxy61.rst | 22 - This involves subtracting the short exposure frame from the long
|
/openbmc/openpower-hw-diags/analyzer/ |
H A D | util.hpp | 5 * stuff that involves libhei).
|
/openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/ |
H A D | 0001-docs-Disable-manual-validation.patch | 6 validating manual and manpages, this task involves calling xmllint which
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | cmake-qemu.bbclass | 7 # involves a certain risk, which is also the reason why this feature
|
/openbmc/linux/drivers/staging/media/deprecated/atmel/ |
H A D | TODO | 4 The move to media controller involves several changes which are
|
/openbmc/qemu/python/ |
H A D | PACKAGE.rst | 24 <https://wiki.qemu.org/Contribute/SubmitAPatch>`_, which involves
|
/openbmc/u-boot/doc/driver-model/ |
H A D | serial-howto.txt | 36 this involves these steps:
|
H A D | i2c-howto.txt | 46 this involves these steps:
|
/openbmc/linux/arch/hexagon/mm/ |
H A D | copy_to_user.S | 8 /* The right way to do this involves valignb
|
H A D | copy_from_user.S | 9 * The right way to do this involves valignb
|
/openbmc/qemu/tests/tcg/x86_64/ |
H A D | cross-modifying-code.c | 8 * involves patching the first byte with int3.
|
/openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | qcom-ipcc.yaml | 14 to route interrupts across various subsystems. It involves a three-level
|
/openbmc/linux/drivers/infiniband/hw/hfi1/ |
H A D | opfn.h | 19 * OPFN involves the communication between two QPs on the HFI
|
/openbmc/u-boot/doc/ |
H A D | README.i2c | 15 minimal overhead and involves very little code. The scheme can survive
|
/openbmc/u-boot/arch/arm/include/asm/arch-mx7/ |
H A D | mx7_plugin.S | 91 * "image_copy_start", which involves FLASH_OFFSET, plus the first
|
/openbmc/linux/Documentation/networking/device_drivers/fddi/ |
H A D | defza.rst | 30 The board only supports DMA on the receive side. Transmission involves
|
/openbmc/linux/Documentation/infiniband/ |
H A D | opa_vnic.rst | 12 involves one or more virtual Ethernet switches overlaid on the Omni-Path 114 It involves HW resource allocation/management for VNIC functionality.
|
/openbmc/phosphor-net-ipmid/sol/ |
H A D | sol_manager.hpp | 197 * Starting a payload instance involves creating the context object, 209 * Stopping a payload instance involves stopping and removing the
|