/openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
H A D | 0008-Define-glibc-compatible-basename-for-non-glibc-syste.patch | 7 using non-posix basename implementation, we have a way out 16 diff --git a/src/basic/string-util.h b/src/basic/string-util.h 18 --- a/src/basic/string-util.h
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/ |
H A D | fiptool-native_2.11.0.bb | 2 # It is a packaging format used by TF-A to package the 3 # firmware images in a single binary. 8 SRC_URI_TRUSTED_FIRMWARE_A ?= "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=h…
|
H A D | fiptool-native_2.10.4.bb | 2 # It is a packaging format used by TF-A to package the 3 # firmware images in a single binary. 8 SRC_URI_TRUSTED_FIRMWARE_A ?= "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=h…
|
/openbmc/openbmc/poky/meta/recipes-kernel/systemtap/systemtap/ |
H A D | 0001-elaborate.cxx-gcc-version-compatibility-hack-redux.patch | 8 Upstream-Status: Backport [https://sourceware.org/git/?p=systemtap.git;a=commit;h=91caf37e4dfe862f9… 14 diff --git a/elaborate.cxx b/elaborate.cxx 16 --- a/elaborate.cxx
|
/openbmc/linux/arch/xtensa/ |
H A D | Kconfig | 63 a home page at <http://www.linux-xtensa.org/>. 139 You will be prompted for a processor variant CORENAME. 146 Provide the name of a custom Xtensa processor variant. 163 Build a Conventional Kernel with full MMU support, 164 ie: it supports a TLB with auto-loading, page protection. 522 Attach a first simdisk to a host file. Conventionally, this file 523 contains a root file system. 530 Another simulated disk in a host file for a buildroot-independent 577 work for using KEXEC to have a hot kernel ready for doing a 697 This is a safe choice for most configurations. [all …]
|
/openbmc/linux/arch/arm/include/asm/ |
H A D | sections.h | 22 void *a = (void *)addr; in in_idmap_text() local 23 return memory_contains(__idmap_text_start, __idmap_text_end, a, 1); in in_idmap_text()
|
/openbmc/qemu/tests/qapi-schema/ |
H A D | doc-bad-enum-member.json | 5 # @a: a
|
H A D | event-nest-struct.err | 2 event-nest-struct.json:1: 'data' member 'a' should be a type name or array
|
H A D | nested-struct-data.err | 2 nested-struct-data.json:2: 'data' member 'a' should be a type name or array
|
H A D | struct-member-invalid.err | 2 struct-member-invalid.json:1: 'data' member 'a' should be a type name or array
|
/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | as3711.txt | 2 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/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | riscv,cpu-intc.txt | 7 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/linux/Documentation/w1/masters/ |
H A D | omap-hdq.rst | 17 Semiconductor 1-Wire protocols. These protocols use a single wire for 28 using an initialization pulse (also referred to as a break pulse).The slave 29 does not respond with a presence pulse as it does in the 1-Wire protocol. 35 spec(family:id:crc), a module parameter can be passed to the driver which will 41 Please note to load both the modules with a different ID if required, but note
|
/openbmc/linux/tools/testing/selftests/ftrace/ |
H A D | README | 3 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/linux/Documentation/ABI/testing/ |
H A D | sysfs-firmware-ofw | 5 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.
|
/openbmc/linux/Documentation/security/tpm/ |
H A D | tpm_event_log.rst | 24 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/openbmc/poky/meta/files/common-licenses/ |
H A D | PSF-2.0 | 11 hereby grants Licensee a nonexclusive, royalty-free, world-wide 20 3. In the event Licensee prepares a derivative work that is based on 23 Licensee hereby agrees to include in any such work a brief summary of 38 6. This License Agreement will automatically terminate upon a material 44 trademarks or trade name in a trademark sense to endorse or promote
|
/openbmc/linux/drivers/eisa/ |
H A D | Kconfig | 21 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/u-boot/scripts/coccinelle/iterators/ |
H A D | use_after_iter.cocci | 1 /// 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/u-boot/doc/ |
H A D | README.arm64 | 7 These days U-Boot runs on a variety of 64-bit capable ARM hardware, from 14 recommened to enter it in EL3 if U-Boot takes some responsibilities of a 17 that of a boot loader. It can drop to lower exception levels before 21 use rela relocation format, a tool(tools/relocate-rela) by Scott Wood 25 3. Earlier Linux kernel versions required the FDT to be placed at a
|
/openbmc/qemu/docs/ |
H A D | qemupciserial.inf | 5 ; emulated by qemu has, and to apply a name tag to it which windows 8 ; Installing the driver: Go to device manager. You should find a "pci 9 ; serial card" tagged with a yellow question mark. Open properties. 11 ; (Com+Lpt)" from the list. Click "Have a disk". Select this file. 12 ; Procedure may vary a bit depending on the windows version.
|
/openbmc/linux/Documentation/ABI/stable/ |
H A D | sysfs-firmware-opal-elog | 8 Each error log is identified by a unique ID and will 11 Each log entry has a directory in /sys/firmware/opal/elog. 20 the only remaining copy of a log message may be in 23 Typically, a user space daemon will monitor for new 31 The raw log format is a binary format. We currently
|
/openbmc/linux/Documentation/hwmon/ |
H A D | abituguru3.rst | 14 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/openbmc/poky/documentation/dev-manual/ |
H A D | intro.rst | 20 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/linux/Documentation/userspace-api/media/rc/ |
H A D | lirc-write.rst | 13 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
|