Home
last modified time | relevance | path

Searched full:involves (Results 1 – 25 of 347) sorted by relevance

12345678910>>...14

/openbmc/bmcweb/redfish-core/include/registries/
H A Dopenbmc_message_registry.readmefirst.md10 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 Dadding-syscalls.rst26 - 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 Dphosphor-watchdog_%.bbappend4 # Ampere Mt. Jade power control involves different action during
/openbmc/linux/drivers/hwmon/pmbus/
H A Dltc4286.c41 * 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 Dpi-futex.rst7 - 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 Dhlwd-pic.c27 * 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 Dsysfs-bus-nfit11 involves determining the ARS capabilities of a given address
/openbmc/linux/Documentation/userspace-api/media/drivers/
H A Dst-vgxy61.rst22 - This involves subtracting the short exposure frame from the long
/openbmc/openpower-hw-diags/analyzer/
H A Dutil.hpp5 * stuff that involves libhei).
/openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/
H A D0001-docs-Disable-manual-validation.patch6 validating manual and manpages, this task involves calling xmllint which
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dcmake-qemu.bbclass7 # involves a certain risk, which is also the reason why this feature
/openbmc/linux/drivers/staging/media/deprecated/atmel/
H A DTODO4 The move to media controller involves several changes which are
/openbmc/qemu/python/
H A DPACKAGE.rst24 <https://wiki.qemu.org/Contribute/SubmitAPatch>`_, which involves
/openbmc/u-boot/doc/driver-model/
H A Dserial-howto.txt36 this involves these steps:
H A Di2c-howto.txt46 this involves these steps:
/openbmc/linux/arch/hexagon/mm/
H A Dcopy_to_user.S8 /* The right way to do this involves valignb
H A Dcopy_from_user.S9 * The right way to do this involves valignb
/openbmc/qemu/tests/tcg/x86_64/
H A Dcross-modifying-code.c8 * involves patching the first byte with int3.
/openbmc/linux/Documentation/devicetree/bindings/mailbox/
H A Dqcom-ipcc.yaml14 to route interrupts across various subsystems. It involves a three-level
/openbmc/linux/drivers/infiniband/hw/hfi1/
H A Dopfn.h19 * OPFN involves the communication between two QPs on the HFI
/openbmc/u-boot/doc/
H A DREADME.i2c15 minimal overhead and involves very little code. The scheme can survive
/openbmc/u-boot/arch/arm/include/asm/arch-mx7/
H A Dmx7_plugin.S91 * "image_copy_start", which involves FLASH_OFFSET, plus the first
/openbmc/linux/Documentation/networking/device_drivers/fddi/
H A Ddefza.rst30 The board only supports DMA on the receive side. Transmission involves
/openbmc/linux/Documentation/infiniband/
H A Dopa_vnic.rst12 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 Dsol_manager.hpp197 * Starting a payload instance involves creating the context object,
209 * Stopping a payload instance involves stopping and removing the

12345678910>>...14