/openbmc/qemu/subprojects/ |
H A D | either-1-rs.wrap | 2 directory = either-1.12.0 3 source_url = https://crates.io/api/v1/crates/either/1.12.0/download 4 source_filename = either-1.12.0.tar.gz 7 patch_directory = either-1-rs
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-platform-msi-laptop | 13 Enable automatic brightness control: contains either 0 or 1. If 22 WLAN subsystem enabled: contains either 0 or 1. 29 Bluetooth subsystem enabled: contains either 0 or 1. Please 38 Contains either 0 or 1 and indicates if touchpad is turned on. 46 Contains either 0 or 1 and indicates if turbo mode is turned 59 Contains either 0 or 1 and indicates if ECO mode is turned on. 80 Contains either 0 or 1 and indicates if fan speed is controlled
|
H A D | sysfs-bus-iio-frequency-ad9523 | 10 Reading returns either '1' or '0'. 20 Reading returns either '1' or '0'. '1' means that the
|
/openbmc/qemu/subprojects/packagefiles/either-1-rs/ |
H A D | meson.build | 1 project('either-1-rs', 'rust', 8 'either', 25 meson.override_dependency('either-1-rs', either_dep, native: true)
|
/openbmc/linux/lib/crypto/ |
H A D | Kconfig | 28 either builtin or as a module. 44 either builtin or as a module. 62 by either the generic implementation or an arch-specific one, if one 70 either builtin or as a module. 88 fulfilled by either the generic implementation or an arch-specific 106 either builtin or as a module. 123 by either the generic implementation or an arch-specific one, if one
|
/openbmc/telemetry/tests/src/ |
H A D | test_numeric_threshold.cpp | 308 .Direction(numeric::Direction::either) 314 .Direction(numeric::Direction::either) 320 .Direction(numeric::Direction::either) 338 .Direction(numeric::Direction::either) 356 .Direction(numeric::Direction::either) 444 .Direction(numeric::Direction::either) 451 .Direction(numeric::Direction::either) 458 .Direction(numeric::Direction::either) 525 .Direction(numeric::Direction::either) 532 .Direction(numeric::Direction::either) [all …]
|
/openbmc/qemu/subprojects/packagefiles/itertools-0.11-rs/ |
H A D | meson.build | 7 subproject('either-1-rs', required: true) 9 either_dep = dependency('either-1-rs', native: true)
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | UPL-1.0 | 5 …nt rights owned or freely licensable by each licensor hereunder covering either (i) the unmodified… 11 …ftware and the Larger Work(s), and to sublicense the foregoing rights on either these or other ter… 15 The above copyright notice and either this complete permission notice or at a minimum a reference t…
|
/openbmc/openbmc/poky/meta/recipes-graphics/wayland/ |
H A D | wayland-protocols_1.39.bb | 3 available in the Wayland core protocol. Such protocols either add \ 5 protocol either in Wayland core, or some other protocol in \
|
/openbmc/linux/drivers/clk/baikal-t1/ |
H A D | Kconfig | 26 signals, which are either directly wired to the consumers (like 37 SoC. CCU dividers can be either configurable or with fixed divider, 38 either gateable or ungateable. Some of the CCU dividers can be as well
|
/openbmc/linux/Documentation/virt/kvm/s390/ |
H A D | s390-diag.rst | 19 all supported DIAGNOSE calls need to be handled by either KVM or its 46 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3). 49 the function's return code, which is either a return code or a subcode 62 Handled by either userspace or KVM (ioeventfd case).
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 226.out | 15 qemu-io: can't open: 'host_device' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or … 22 qemu-io: can't open: 'host_cdrom' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or b…
|
/openbmc/openbmc/poky/meta/recipes-extended/at/at/ |
H A D | file_replacement_with_gplv2.patch | 24 - the Free Software Foundation; either version 3 of the License, or 26 + the Free Software Foundation; either version 2, or (at your option)
|
/openbmc/linux/Documentation/scsi/ |
H A D | LICENSE.FlashPoint | 8 the terms of either: 11 Foundation; either version 2, or (at your option) any later version, 19 or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public
|
/openbmc/u-boot/doc/device-tree-bindings/gpio/ |
H A D | intel,x86-broadwell-pinctrl.txt | 16 - direction - sets the direction of the gpio, either PIN_INPUT (default) 19 - trigger - sets the trigger type, either TRIGGER_EDGE (default) or 22 - owner 0 sets the owner of the pin, either OWNER_ACPI (default) or 24 - route - sets whether the pin is routed, either PIRQ_APIC_MASK or
|
/openbmc/linux/arch/mips/sgi-ip27/ |
H A D | Kconfig | 11 in either N-Modes which allows for more nodes or M-Mode which allows 19 in either N-Modes which allows for more nodes or M-Mode which allows
|
/openbmc/linux/Documentation/arch/xtensa/ |
H A D | booting.rst | 18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a 19 virtual or physical address. In either case it must be within the default
|
/openbmc/openbmc/poky/scripts/pybootchartgui/ |
H A D | README.pybootchart | 7 http://www.bootchart.org/) to either the screen or files of various 29 single image to either the screen or in PNG, PDF or SVG format.
|
/openbmc/linux/Documentation/hwmon/ |
H A D | gsc-hwmon.rst | 21 The voltage inputs are scaled either internally or by the driver depending 33 either internally or by the driver depending on the GSC version and firmware.
|
/openbmc/linux/Documentation/usb/ |
H A D | misc_usbsevseg.rst | 26 The device can accept "text" either in raw, hex, or ascii textmode. 46 The device has either 6 or 8 decimal points.
|
/openbmc/linux/Documentation/admin-guide/gpio/ |
H A D | gpio-aggregator.rst | 15 system permissions, on an all-or-nothing basis: either a GPIO controller is 80 Binding a device to the GPIO Aggregator is performed either by modifying the 94 it can be bound to the GPIO Aggregator by either:
|
H A D | sysfs.rst | 75 reads as either "in" or "out". This value may 87 reads as either 0 (low) or 1 (high). If the GPIO 97 poll(2) returns, either lseek(2) to the beginning of the sysfs 102 reads as either "none", "rising", "falling", or 110 reads as either 0 (false) or 1 (true). Write
|
/openbmc/linux/Documentation/devicetree/bindings/mtd/ |
H A D | nxp-spifi.txt | 5 mode 0 or 3. The controller operates in either command or memory 25 - spi-cpol : Controller only supports mode 0 and 3 so either
|
/openbmc/linux/Documentation/power/ |
H A D | apm-acpi.rst | 6 odds are it supports either Advanced Power Management (APM) or 12 The best way to determine which, if either, your system supports is to
|
/openbmc/telemetry/src/ |
H A D | numeric_threshold.cpp | 79 (direction == numeric::Direction::either && in sensorUpdated() 87 : numeric::Direction::either; in sensorUpdated()
|