Home
last modified time | relevance | path

Searched refs:handle (Results 4051 – 4075 of 4091) sorted by relevance

1...<<161162163164

/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-ufs472 the device to handle system data by the tagging mechanism.
/openbmc/linux/Documentation/admin-guide/media/
H A Dvivid.rst621 allow you to check if your application can handle such things correctly.
/openbmc/linux/drivers/scsi/
H A DKconfig842 allows them to act as expansion buses that can handle up to 64
/openbmc/linux/Documentation/networking/
H A Dbonding.rst1440 sysconfig network initialization scripts handle this automatically; if
1747 # tc qdisc add dev bond0 handle 1 root multiq
/openbmc/qemu/target/ppc/translate/
H A Dvsx-impl.c.inc1845 * uim > 12 handle as per hardware in helper
/openbmc/linux/Documentation/networking/dsa/
H A Ddsa.rst457 "phy-handle" property, if found, this PHY device is created and registered
/openbmc/linux/arch/arm/
H A DKconfig1091 transparently handle transition between a cluster of A15's
/openbmc/linux/drivers/scsi/aic7xxx/
H A Daic79xx.reg4241 * way we handle our scatter gather lists. The driver implements
/openbmc/linux/arch/x86/crypto/
H A Daesni-intel_avx-x86_64.S395 # handle the last <16 Byte block separately
/openbmc/qemu/tests/functional/acpi-bits/bits-tests/
H A Dsmbios.py2148 self.add_field('handle', self.u.unpack_one("<H"))
/openbmc/qemu/docs/interop/
H A Dvhost-user.rst1407 Backends that negotiated this feature should handle both
/openbmc/qemu/tcg/aarch64/
H A Dtcg-target.c.inc813 we can handle both register sets with one function. */
/openbmc/linux/drivers/rtc/
H A DKconfig254 should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
/openbmc/openbmc/poky/meta/recipes-bsp/lrzsz/lrzsz-0.12.20/
H A Dautotools-update.patch618 - cannot handle mpty for list. Reported by Jim Meyering.
4316 - some systems libc cannot handle nonalpha characters. */
/openbmc/linux/security/selinux/
H A Dhooks.c1613 #error Fix SELinux to handle capabilities > 63.
/openbmc/openbmc/poky/documentation/sdk-manual/
H A Dextensible.rst1331 or other path variables is usually the way to handle this situation.
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dcommon.rst1598 your target system is capable and powerful enough to handle the
/openbmc/openbmc/meta-raspberrypi/recipes-multimedia/rpidistro-ffmpeg/files/
H A D0001-ffmpeg-5.1.4-rpi_24.patch3665 - * handle resolution change event and end of stream event
3920 + * handle resolution change event and end of stream event
3945 - /* 0. handle errors */
3965 - /* 1. handle resolution changes */
12872 + struct drm_gem_close gem_close = {.handle = da->bo_handles[i]};
18001 + // handle the last block at the end of each row
18116 + // handle incomplete block at the end of every row
/openbmc/linux/Documentation/sound/
H A Dalsa-configuration.rst340 Note: Some ALSA mixer applications don't handle the SPDIF sample rate
/openbmc/u-boot/common/
H A Ddlmalloc.src298 at the expense of not being able to handle requests greater than
/openbmc/linux/Documentation/admin-guide/
H A Dspkguide.txt1111 ~/.bash_profile file). If there are several languages to handle, the
/openbmc/linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/
H A Dmain.c5546 int (*d_fn)(void *handle)) in brcms_c_module_register() argument
/openbmc/linux/drivers/net/ethernet/broadcom/bnxt/
H A Dbnxt_hsi.h8976 __le16 handle; member
/openbmc/qemu/target/i386/tcg/
H A Demit.c.inc2362 /* load the segment here to handle exceptions properly */
/openbmc/linux/Documentation/
H A Dmemory-barriers.txt2922 To handle this case optimally, low-level virt_mb() etc macros are available.

1...<<161162163164