/openbmc/qemu/tests/qapi-schema/ |
H A D | doc-bad-event-arg.json | 5 # @a: a
|
H A D | doc-bad-feature.json | 7 # @a: a
|
/openbmc/qemu/tests/decode/ |
H A D | succ_ident1.decode | 5 &3arg a b c 6 @3arg ........ ........ ........ ........ &3arg a=%1f b=%2f c=%3f
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | tips.txt | 1 For a higher level overview, try: perf report --sort comm,dso 6 Generate a script for your data: perf script -g <lang> 9 Search options using a keyword: perf report -h <keyword> 14 To see callchains in a more compact form: perf report -g folded 26 To record every process run by a user: perf record -u <user> 33 System-wide collection from all CPUs: perf record -a
|
/openbmc/linux/Documentation/security/ |
H A D | sak.rst | 8 An operating system's Secure Attention Key is a security tool which is 19 The proper way of generating a SAK is to define the key sequence using 24 once defined, SAK will kill a running X server. If the system is in 41 1. Linux SAK is said to be not a "true SAK" as is required by 49 Unfortunately this includes a number of things which you don't 65 So ``gpm`` will be killed by SAK. This is a bug in gpm. It should
|
/openbmc/u-boot/board/freescale/mpc8544ds/ |
H A D | README | 15 board, a runtime reset through the FPGA can also affect a swap 35 For example, to place a new image in the alternate flash bank 93 use a command similar to this: 102 you can download that dtb file using a command like: 112 Place a linux uImage in the TFTP disk area too.
|
/openbmc/linux/Documentation/userspace-api/media/dvb/ |
H A D | frontend_f_open.rst | 13 fe-open - Open a frontend device 48 This system call opens a named frontend device 50 thing to do after a successful open is to find out the frontend type 57 In a system with multiple front-ends, it is usually the case that 59 long as a front-end device is opened in read/write mode, other open() 63 versa) using the F_SETFL command of the fcntl system call. This is a
|
/openbmc/openbmc/poky/meta/recipes-kernel/linux-libc-headers/ |
H A D | linux-libc-headers.inc | 18 # and have a machine specific libc. 23 # better than having a machine specific C library. This does mean your 24 # recipe needs a 28 # There can also be a case where your kernel extremely old and you want 30 # recipe should still be a standard mainline kernel, not your own custom 37 RECIPE_NO_UPDATE_REASON = "Recipe is updated through a separate process"
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/emlog/emlog/ |
H A D | Drop-use-of-error-h.patch | 18 diff --git a/mkemlog.c b/mkemlog.c 20 --- a/mkemlog.c 62 - error(1, 0, "Invalid size provided must be a value between 1 and %d\n" USAGE, emlog_ma… 63 + fprintf(stderr, "Invalid size provided must be a value between 1 and %d\n" USAGE, emlo… 98 - error(1, 0, EMLOG_DEVICE " is not a valid emlog device\n"); 99 + fprintf(stderr, EMLOG_DEVICE " is not a valid emlog device\n");
|
/openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc/ |
H A D | 0014-add-if_nameindex-from-musl.patch | 35 diff --git a/kexec/Makefile b/kexec/Makefile 37 --- a/kexec/Makefile 48 diff --git a/kexec/if_nameindex.c b/kexec/if_nameindex.c 118 diff --git a/kexec/if_nameindex.h b/kexec/if_nameindex.h 139 diff --git a/kexec/ifdown.c b/kexec/ifdown.c 141 --- a/kexec/ifdown.c
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/postfix/files/ |
H A D | 0001-Fix-makedefs.patch | 21 diff --git a/makedefs b/makedefs 23 --- a/makedefs 50 # On a properly installed system, Postfix builds 64 test -e $lib/lib$name.a -o -e $lib/lib$name.so && { 98 # On a properly installed system, Postfix builds 113 test -e $lib/lib$name.a -o -e $lib/lib$name.so && {
|
/openbmc/openbmc/poky/meta-poky/ |
H A D | README.poky.md | 4 Poky is an integration of various components to form a pre-packaged 5 build system and development environment which is used as a development and 10 application development using QEMU emulation and a standalone toolchain and 15 in the form of BSP layers which extend the systems capabilities in a modular way. 27 The Yocto Project has extensive documentation about the system including a 43 As Poky is an integration repository (built using a tool called combo-layer),
|
/openbmc/openbmc/poky/ |
H A D | README.md | 4 Poky is an integration of various components to form a pre-packaged 5 build system and development environment which is used as a development and 10 application development using QEMU emulation and a standalone toolchain and 15 in the form of BSP layers which extend the systems capabilities in a modular way. 27 The Yocto Project has extensive documentation about the system including a 43 As Poky is an integration repository (built using a tool called combo-layer),
|
H A D | README.poky.md | 4 Poky is an integration of various components to form a pre-packaged 5 build system and development environment which is used as a development and 10 application development using QEMU emulation and a standalone toolchain and 15 in the form of BSP layers which extend the systems capabilities in a modular way. 27 The Yocto Project has extensive documentation about the system including a 43 As Poky is an integration repository (built using a tool called combo-layer),
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/samba/samba/ |
H A D | 0004-Add-options-to-configure-the-use-of-libbsd.patch | 18 diff --git a/buildtools/wafsamba/wscript b/buildtools/wafsamba/wscript 20 --- a/buildtools/wafsamba/wscript 36 diff --git a/lib/replace/wscript b/lib/replace/wscript 38 --- a/lib/replace/wscript 76 diff --git a/lib/texpect/wscript b/lib/texpect/wscript 78 --- a/lib/texpect/wscript
|
/openbmc/linux/Documentation/devicetree/bindings/clock/ |
H A D | arm,syscon-icst.yaml | 19 an ICST clock request after a write to the 32 bit register at an offset 22 writing a special token to another offset in the system controller. 30 In the core modules and logic tiles, the ICST is a configurable clock fed 31 from a 24 MHz clock on the motherboard (usually the main crystal) used for 33 only one of these. This clock node must be a subnode of the core module. 52 The ICST oscillator must be provided inside a system controller node.
|
/openbmc/linux/Documentation/devicetree/bindings/ata/ |
H A D | ahci-common.yaml | 14 This document defines device tree properties for a common AHCI SATA 18 document doesn't constitute a DT-node binding by itself but merely 19 defines a set of common properties for the AHCI-compatible devices. 39 Generic AHCI state change interrupt. Can be implemented either as a 40 single line attached to the controller or as a set of the signals 76 "^sata-port@[0-9a-f]+$":
|
/openbmc/linux/Documentation/tools/rtla/ |
H A D | rtla-hwnoise.rst | 22 of threads as a consequence, only non-maskable interrupts and hardware-related 39 on a system with 8 cores/16 threads with hyper-threading enabled. 42 to run for *ten minutes*, displaying a summary of the report at the 64 The *Max Noise* column is the maximum hardware noise the tool detected in a 74 noise, as the *Max Single* noise was of *3 us*. The CPU has *HW noise,* at a 75 rate of *six occurrences*/*ten minutes*. The CPU also has *NMIs*, at a higher
|
/openbmc/linux/Documentation/arch/arm/keystone/ |
H A D | knav-qmss.rst | 14 The Queue Manager is a hardware module that is responsible for accelerating 16 reading descriptor address to a particular memory mapped location. The PDSPs 24 knav qmss driver provides a set of APIs to drivers to open/close qmss queues, 33 The QMSS PDSP firmware support accumulator channel that can monitor a single 49 ubifs file system and provide a sym link to k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin 58 PDSP is not running in the SoC. The API call fails if there is a queue open
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-kernel-iommu_groups | 5 Description: /sys/kernel/iommu_groups/ contains a number of sub- 11 The group directory also optionally contains a "name" 12 file if the IOMMU driver has chosen to register a more 24 region is described on a single line: the 1st field is 54 The default domain type of a group may be modified only when 60 Unbinding a device driver will take away the driver's control
|
/openbmc/linux/drivers/acpi/acpica/ |
H A D | exfield.c | 52 #define GENERIC_SUBSPACE_COMMAND(a) (4 == a || a == 5) argument 53 #define MASTER_SUBSPACE_COMMAND(a) (12 <= a && a <= 15) argument
|
/openbmc/linux/drivers/iio/ |
H A D | Kconfig | 9 The industrial I/O subsystem provides a unified framework for 10 drivers for many different types of embedded sensors using a 41 buffers. The triggers are effectively a 'capture 49 This value controls the maximum number of consumers that a 57 device can be created via configfs or directly by a driver 65 trigger can be created via configfs or directly by a driver
|
/openbmc/phosphor-ipmi-flash/ |
H A D | ipmi_flash.md | 5 To avoid excessive complications, there is a restriction that only one blob 6 within the firmware handler can be open at a time. 10 At each state, each method has a specific effect, depending on a variety of 22 You can only open one file at a time, and some of the states exist only when a
|
/openbmc/linux/include/linux/ |
H A D | compiler_types.h | 74 #define ___PASTE(a,b) a##b argument 75 #define __PASTE(a,b) ___PASTE(a,b) argument 403 #define __same_type(a, b) __builtin_types_compatible_p(typeof(a), typeof(b)) argument
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | CPOL-1.02 | 24 …a. "Articles" means, collectively, all articles written by Author which describes how the Source C… 28 …c. "Derivative Work" means a work based upon the Work or upon the Work and other pre-existing work… 36 …g. "Standard Version" refers to such a Work if it has not been modified, or has been modified in a… 46 …a. You may use the standard version of the Source Code or Executable Files in Your own application… 48 …obtained from the Public Domain or from the Author. A Work modified in such a way shall still be c… 50 …is Work (excluding the Articles) in any way to create a Derivative Work, provided that You insert … 52 …tive Work in aggregate with other (possibly commercial) programs as part of a larger (possibly com… 62 …a. You agree not to remove any of the original copyright, patent, trademark, and attribution notic… 64 b. You agree not to advertise or in any way imply that this Work is a product of Your own. 84 …b. If You bring a copyright, trademark, patent or any other infringement claim against any contrib… [all …]
|