Home
last modified time | relevance | path

Searched refs:a (Results 6126 – 6150 of 20302) sorted by relevance

1...<<241242243244245246247248249250>>...813

/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Ddm-flakey.rst28 Full pathname to the underlying block-device, or a
71 During <down interval>, replace random byte in a read bio
72 with a random value. probability is an integer between
76 During <down interval>, replace random byte in a write bio
77 with a random value. probability is an integer between
/openbmc/pldm/oem/ampere/event/
H A Dcper.cpp21 int guid_equal(EFI_GUID* a, EFI_GUID* b) in guid_equal() argument
24 if (a->Data1 != b->Data1 || a->Data2 != b->Data2 || a->Data3 != b->Data3) in guid_equal()
32 if (a->Data4[i] != b->Data4[i]) in guid_equal()
/openbmc/linux/Documentation/hwmon/
H A Dabituguru3.rst14 The uGuru is a microcontroller with onboard firmware which programs
15 it to behave as a hwmon IC. There are many different revisions of the
59 The 3rd revision of the uGuru chip in reality is a Winbond W83L951G.
60 Unfortunately this doesn't help since the W83L951G is a generic microcontroller
61 with a custom Abit application running on it.
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-rtrs-server5 Description: When a user of RTRS API creates a new session on a client side, a
13 a directory entry named as <source address>@<destination address> is created
H A Dsysfs-firmware-ofw5 When using OpenFirmware or a Flattened Device Tree to enumerate
10 Some device drivers use a separate detached device tree which
11 have no attachment to the system tree and will appear in a
23 The contents of /sys/firmware/devicetree/ is a
51 time. Otherwise, a warning is printed.
H A Dsysfs-class-rnbd-server11 Description: When a client maps a device, a directory entry with the name of the
18 Description: Is a symlink to the sysfs entry of the exported device.
27 Description: For each client a particular device is exported to, following directory will be
/openbmc/linux/Documentation/filesystems/ext4/
H A Dmmp.rst6 Multiple mount protection (MMP) is a feature that protects the
8 simultaneously. When a filesystem is opened (for mounting, or fsck,
9 etc.), the MMP code running on the node (call it node A) checks a
16 code passes all of those checks, a new MMP sequence number is generated
19 While the filesystem is live, the kernel sets up a timer to re-check the
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/tbb/
H A Dtbb_2021.13.0.bb2 TBB is a library that helps you leverage multi-core processor \
3 performance without having to be a threading expert. It represents a \
32 # Hard-float 'd' ABI can't be used for a target that doesn't support the D instruction set extensio…
39 # | arm-oe-linux-gnueabi-g++ -march=armv7-a -mthumb -mthumb-interwork -mfloat-abi=softfp -mfpu=neo…
/openbmc/linux/Documentation/security/tpm/
H A Dtpm_event_log.rst24 to a challenger. However, PCR contents are difficult to interpret;
26 are accompanied by a measurement log. While not trusted on their own,
27 the measurement log contains a richer set of information than do the PCR
34 UEFI provided event log has a few somewhat weird quirks.
37 a custom configuration table defined by the stub itself. Unfortunately,
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Das3711.txt2 supplies, a battery charger and an RTC. So far only bindings for the two stepup
4 standard regulator properties, they must belong to a sub-node, called
6 configuration should be placed in a subnode, called "backlight."
12 To use the SU1 converter as a backlight source the following two properties must
17 To use the SU2 converter as a backlight source the following two properties must
/openbmc/openbmc/meta-security/meta-hardening/
H A DREADME.md9 a framework from which a user can build from and can possible contribute to.
19 Yocto Project compatible guideline that indicate that simply including a
25 If one wants the a more complete example of a hardened image, one must also build the image:
/openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Draideng.txt4 Engine should have a separate node.
30 There must be a sub-node for each job queue present in RAID Engine
31 This node must be a sub-node of the main RAID Engine node
48 There must be a sub-node for each job ring present in RAID Engine
49 This node must be a sub-node of job queue node
/openbmc/linux/tools/testing/selftests/ftrace/
H A DREADME3 This is a collection of testcases for ftrace tracing feature in the Linux
33 * The tests should not run for a long period of time (more than 1 min.)
36 * You can add a directory for your testcases under test.d/ if needed.
60 or the test depends on a previous test, which failed.
64 * UNTESTED: The test was not run, currently just a placeholder.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/usbip-tools/
H A Dusbip-tools.bb15 client over the network. Server is a machine which provides (shares) a \
16 USB device. Client is a machine which uses USB device provided by server \
18 to a server or software entity created on a server using USB gadget subsystem."
/openbmc/linux/arch/x86/include/asm/
H A Dfloppy.h23 #define _CROSS_64KB(a, s, vdma) \ argument
25 ((unsigned long)(a)/K_64 != ((unsigned long)(a) + (s) - 1) / K_64))
27 #define CROSS_64KB(a, s) _CROSS_64KB(a, s, use_virtual_dma & 1) argument
/openbmc/openbmc/poky/meta/recipes-extended/cpio/
H A Dcpio_2.15.bb1 SUMMARY = "GNU cpio is a program to manage archives of files"
2 DESCRIPTION = "GNU cpio is a tool for creating and extracting archives, or copying files from one p…
3 another. It handles a number of cpio formats as well as reading and writing tar files."
59 # change permission after that has happened so the ptest user can write a
66 # The tests need to run as a non-root user, so pull in the ptest user
/openbmc/u-boot/scripts/coccinelle/iterators/
H A Duse_after_iter.cocci1 /// If list_for_each_entry, etc complete a traversal of the list, the iterator
3 /// and not a meaningful structure. Thus this value should not be used after
5 //#False positives arise when there is a goto in the iterator and the
7 //#may also cause a report to be a false positive.
/openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-devtools/python/python3-pyinotify/
H A D0001-Make-asyncore-support-optional-for-Python-3.patch16 diff --git a/python3/pyinotify.py b/python3/pyinotify.py
18 --- a/python3/pyinotify.py
64 - events. This method can be overridden for handling a notification
77 + events. This method can be overridden for handling a notification
84 + # asyncore was removed in Python 3.12, but try the import instead of a
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Driscv,cpu-intc.txt7 Every interrupt is ultimately routed through a hart's HLIC before it
19 required to have a HLIC with these three interrupt sources present. Since the
23 a PLIC interrupt property will typically list the HLICs for all present HARTs
34 SBI calls and implements a one-shot timer.
42 An example device tree entry for a HLIC is show below.
/openbmc/openbmc/poky/meta/recipes-extended/tar/tar/
H A D0003-Exclude-VCS-directory-with-writing-from-an-archive.patch17 diff --git a/tests/exclude18.at b/tests/exclude18.at
40 +# You should have received a copy of the GNU General Public License
63 +# Make a VCS directory with a file:
67 +# Make a VCS file:
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/fuse/
H A Dfuse3_3.16.2.bb1 SUMMARY = "Implementation of a fully functional filesystem in a userspace program"
2 DESCRIPTION = "FUSE (Filesystem in Userspace) is a simple interface for userspace \
3 programs to export a virtual filesystem to the Linux kernel. FUSE \
4 also aims to provide a secure method for non privileged users to \
/openbmc/linux/drivers/eisa/
H A DKconfig21 Say Y here if you are building a kernel for an EISA-based machine.
30 Activate this option if your system contains a Vesa Local
41 Activate this option if your system contains a PCI to EISA
57 a system.
66 By default, the kernel contains a database of all known EISA
/openbmc/linux/Documentation/userspace-api/media/rc/
H A Dlirc-write.rst13 lirc-write - Write to a LIRC device
43 The exact format of the data depends on what mode a driver is in, use
48 the chardev is a pulse/space sequence of integer values. Pulses and spaces
50 with a pulse, therefore, the data must always include an uneven number of
56 ``struct lirc_scancode`` must be written to the chardev at a time, else
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dintro.rst20 example, procedures that show you how to set up a build host and work
28 creating a new layer, customizing an image, writing a new recipe,
54 knowledge of Yocto Project as a way of quickly testing it out, see the
57 For a comprehensive list of links and other documentation, see the
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/freeradius/files/
H A D0004-Fix-libtool-detection.patch22 diff --git a/configure.ac b/configure.ac
24 --- a/configure.ac
38 +dnl Unfortunately, even up to libtool 2.2.6a there is no way to know
40 +dnl just assume that it's a working version as long as we have the
47 +dnl Check the header files first since the system may have a

1...<<241242243244245246247248249250>>...813