| /openbmc/openbmc/poky/meta/recipes-extended/shadow/files/ |
| H A D | shadow-update-pam-conf.patch | 6 The system-auth in the configure files is from Fedora which put all the 4 pam type rules
37 -password include system-auth
47 -password include system-auth
57 -password include system-auth
67 -password include system-auth
77 -password include system-auth
87 -password include system-auth
97 -password include system-auth
107 -password include system-auth
117 -password include system-auth
|
| /openbmc/linux/drivers/media/dvb-frontends/ |
| H A D | ascot2e.c | 276 system = ASCOT2E_DTV_DVBT_5; in ascot2e_get_tv_system()
278 system = ASCOT2E_DTV_DVBT_6; in ascot2e_get_tv_system()
280 system = ASCOT2E_DTV_DVBT_7; in ascot2e_get_tv_system()
282 system = ASCOT2E_DTV_DVBT_8; in ascot2e_get_tv_system()
284 system = ASCOT2E_DTV_DVBT_8; in ascot2e_get_tv_system()
289 system = ASCOT2E_DTV_DVBT2_5; in ascot2e_get_tv_system()
291 system = ASCOT2E_DTV_DVBT2_6; in ascot2e_get_tv_system()
293 system = ASCOT2E_DTV_DVBT2_7; in ascot2e_get_tv_system()
302 system = ASCOT2E_DTV_DVBC_6; in ascot2e_get_tv_system()
304 system = ASCOT2E_DTV_DVBC_8; in ascot2e_get_tv_system()
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 6 virtiofs: virtio-fs host<->guest shared file system
13 The virtiofs file system for Linux implements a driver for the paravirtualized
14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a
19 booting from a root file system located on the host, persistent storage for
25 solve these problems by providing file system access without networking.
33 Mount file system with tag ``myfs`` on ``/mnt``:
58 Since the virtio-fs device uses the FUSE protocol for file system requests, the
59 virtiofs file system for Linux is integrated closely with the FUSE file system
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/recipes-phosphor/configuration/palmetto-yaml-config/ |
| H A D | palmetto-ipmi-fru.yaml | 2 /system/chassis/motherboard/cpu0:
29 /system/chassis:
40 /system/chassis/motherboard/membuf:
62 /system/chassis/motherboard/dimm0:
90 /system/chassis/motherboard/dimm1:
118 /system/chassis/motherboard/dimm2:
146 /system/chassis/motherboard/dimm3:
174 /system/chassis/motherboard:
196 /system:
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/keystone/ |
| H A D | ti,sci.yaml | 15 management of the System on Chip (SoC) system. These include various system
18 An example of such an SoC is K2G, which contains the system control hardware
33 pattern: "^system-controller@[0-9a-f]+$"
64 ti,system-reboot-controller:
65 description: Determines If system reboot can be triggered by SoC reboot
95 pmmc: system-controller@2921800 {
97 ti,system-reboot-controller;
106 dmsc: system-controller@44083000 {
|
| /openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/configuration/s6q-yaml-config/ |
| H A D | ipmi-fru-properties.yaml | 1 /system:
9 /system/chassis:
17 /system/chassis/bmc:
25 /system/chassis/mainboard:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/OperatingSystem/ |
| H A D | Status.interface.yaml | 2 Implement to set the operating system status.
9 Current state of the operating system.
14 The operaing system statuses.
39 Operating system is ready to be booted.
|
| /openbmc/openpower-hw-diags/ |
| H A D | README.md | 3 In the event of a system fatal error reported by the internal system hardware
4 (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems
6 service action needed to avoid repeated system failures.
|
| /openbmc/qemu/docs/devel/ |
| H A D | ci-definitions.rst.inc | 53 functionality and performance are achieved [4]_. Some or all system components
54 are integrated to create a complete system to be tested as a whole. System
56 transfer the right data at the right time across their interfaces. As system
58 to system testing [5]_. Note that, in some cases, system testing may require
62 On QEMU, system testing is represented by the 'check-avocado' target from
90 the unit, functional, system, and other tests.
94 1. System tests may depend on external software (operating system images,
97 the system being developed several times per day.
99 not be possible to run system tests in the developer’s private workspace.
100 There may be differences in hardware, operating system, or installed
[all …]
|
| /openbmc/linux/include/trace/ |
| H A D | define_trace.h | 84 # define __TRACE_INCLUDE(system) <trace/events/system.h> argument
87 # define __TRACE_INCLUDE(system) __stringify(TRACE_INCLUDE_PATH/system.h) argument
90 # define TRACE_INCLUDE(system) __TRACE_INCLUDE(system) argument
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | cpu-load.rst | 7 the average time system spent in a particular state, for example::
12 avg-cpu: %user %nice %system %iowait %steal %idle
17 Here the system thinks that over the default sampling period the
18 system spent 10.01% of the time doing work in user space, 2.92% in the
28 kind/state. The problem with this is that the system could have
36 If we imagine the system with one task that periodically burns cycles
46 In the above situation the system will be 0% loaded according to the
48 system is executing the idle handler), but in reality the load is
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-networking/cyrus-sasl/ |
| H A D | cyrus-sasl_2.1.28.bb | 60 install -d ${D}${systemd_unitdir}/system
61 install -m 0644 ${WORKDIR}/saslauthd.service ${D}${systemd_unitdir}/system
63 sed -i -e 's#@SBINDIR@#${sbindir}#g' ${D}${systemd_unitdir}/system/saslauthd.service
64 … sed -i -e 's#@LOCALSTATEDIR@#${localstatedir}#g' ${D}${systemd_unitdir}/system/saslauthd.service
65 sed -i -e 's#@SYSCONFDIR@#${sysconfdir}#g' ${D}${systemd_unitdir}/system/saslauthd.service
77 GROUPADD_PARAM:${PN}-bin = "--system mail"
78 USERADD_PARAM:${PN}-bin = "--system --home=/var/spool/mail -g mail cyrus"
92 ${systemd_unitdir}/system/saslauthd.service \
|
| /openbmc/qemu/docs/system/ |
| H A D | target-arm.rst | 7 ``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
10 work for ``qemu-system-arm`` will behave the same when used with
11 ``qemu-system-aarch64``.
16 are generally built into "system-on-chip" (SoC) designs created by
35 For QEMU's Arm system emulation, you must specify which board
40 operating system or firmware images intended to run on one machine
42 users who are used to the x86 world where every system looks like a
46 If you already have a system image or a kernel that works on hardware
52 boots on a system that QEMU does emulate.)
[all …]
|
| H A D | target-riscv.rst | 7 ``qemu-system-riscv64`` executable to simulate a 64-bit RISC-V machine,
8 ``qemu-system-riscv32`` executable to simulate a 32-bit RISC-V machine.
13 CPUs are generally built into "system-on-chip" (SoC) designs created by
25 For QEMU's RISC-V system emulation, you must specify which board
30 operating system or firmware images intended to run on one machine
32 users who are used to the x86 world where every system looks like a
36 If you already have a system image or a kernel that works on hardware
41 extract the file system and use that with a different kernel which
42 boots on a system that QEMU does emulate.)
58 ``qemu-system-riscv64 --machine help``, or
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | sensor_monitoring_tests.cpp | 113 std::unique_ptr<System> system = in createParentObjects() local
116 return std::make_tuple(std::move(system), chassisPtr, devicePtr, in createParentObjects()
146 auto [system, chassis, device, i2cInterface, rail] = in TEST()
183 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
198 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
222 auto [system, chassis, device, i2cInterface, rail] = in TEST()
244 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
264 auto [system, chassis, device, i2cInterface, rail] = in TEST()
318 monitoring->execute(services, *system, *chassis, *device, in TEST()
330 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
[all …]
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_timed_power_on.robot | 3 ... and verify the power status of the system.
39 # Shut down the system and schedule it to restart in 1 hour.
48 ... the system to boot on scheduled time.
63 # Check if the system BootProgress state changed. If changed, it implies the
64 # system is powering on. Though we have set system to power on in 100 seconds
65 # since, the system boot sometime to change.
73 ... and expect the system to boot on scheduled time.
93 # Check if the system BootProgress state changed. If changed, it implies the
94 # system is powering on after user timer set and delta time to update BootProgress
99 Log To Console Waiting for system to power on.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libcereal/files/ |
| H A D | 0001-cmake-Use-idirafter-instead-of-isystem.patch | 6 isystem dirs are searched before the regular system dirs
11 from libc++ as well, which is then eventually including system stdlib.h
14 if cstlib ends up including system stdlib.h before libc++ provided
23 directory via -system and some of these directories point to sysroot
25 <sysroot>/usr/include and causes the system stdlib.h to included before
28 A fix is to use -idirafter which preserved the effects of system headers
29 but instead of prepending, it will append to system headers and the
|
| /openbmc/telemetry/tests/src/ |
| H A D | dbus_environment.hpp | 106 [&propertyPromise](const boost::system::error_code& ec, T t) { in getProperty()
118 static boost::system::error_code
122 auto promise = std::promise<boost::system::error_code>(); in setProperty()
128 boost::system::error_code ec) mutable { in setProperty()
135 static boost::system::error_code
139 auto promise = std::promise<boost::system::error_code>(); in callMethod()
143 boost::system::error_code ec) mutable { in callMethod()
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 14 information about the power sequencer device within a system. This device is
31 The config file name is based on the system type that it supports.
33 A config file is normally system-specific. Each system type usually has a
36 The system type is obtained from a D-Bus Chassis object created by the
42 system types. The types are ordered from most specific to least specific.
49 The `phosphor-power-sequencer` application converts each compatible system type
|
| /openbmc/linux/tools/testing/selftests/memory-hotplug/ |
| H A D | mem-on-off-test.sh | 25 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then
30 if ! grep -q 1 $SYSFS/devices/system/memory/memory*/removable; then
43 for memory in $SYSFS/devices/system/memory/memory*; do
63 grep -q online $SYSFS/devices/system/memory/memory$1/state
68 grep -q offline $SYSFS/devices/system/memory/memory$1/state
73 echo online > $SYSFS/devices/system/memory/memory$1/state
78 echo offline > $SYSFS/devices/system/memory/memory$1/state
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | design.rst | 12 for the system, potentially including lasting hardware damage.
14 of the system - software-equivalent variants of the same chip may
22 particular system.
27 - The overwhelming majority of devices in a system will have no
31 - Many of the power supplies in the system will be shared between many
|
| /openbmc/boost-dbus/include/dbus/ |
| H A D | connection_service.hpp | 22 static const int system = DBUS_BUS_SYSTEM; variable
52 inline void open(implementation_type& impl, const int bus = bus::system) { in open()
78 void(boost::system::error_code, message)) in BOOST_ASIO_INITFN_RESULT_TYPE()
85 MessageHandler, void(boost::system::error_code, message)> in BOOST_ASIO_INITFN_RESULT_TYPE()
88 MessageHandler, void(boost::system::error_code, message)>::type>( in BOOST_ASIO_INITFN_RESULT_TYPE()
|
| /openbmc/linux/tools/testing/selftests/timers/ |
| H A D | set-2038.c | 66 ret = system("date"); in do_tests()
67 ret = system("./inconsistency-check -c 0 -t 20"); in do_tests()
68 ret |= system("./nanosleep"); in do_tests()
69 ret |= system("./nsleep-lat"); in do_tests()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/debian/ |
| H A D | fix-gettid-exception-declaration.patch | 5 --- a/system/core/libcutils/include/cutils/threads.h
6 +++ b/system/core/libcutils/include/cutils/threads.h
16 --- a/system/core/libcutils/threads.cpp
17 +++ b/system/core/libcutils/threads.cpp
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/debian/system/core/ |
| H A D | fix-gettid-exception-declaration.patch | 5 --- a/system/core/libcutils/include/cutils/threads.h
6 +++ b/system/core/libcutils/include/cutils/threads.h
16 --- a/system/core/libcutils/threads.cpp
17 +++ b/system/core/libcutils/threads.cpp
|