| /openbmc/docs/designs/ |
| H A D | state-management-and-external-interfaces.md | 17 instance: `redfish/v1/Systems/system/Actions/ComputerSystem.Reset`
25 and Host within an OpenBMC managed system. The README within the repository can
32 looking to support the capability to reboot an operating system on a system
63 the system.",
64 "GracefulRestart": "Shut down gracefully and restart the system.",
68 typically, halt the system.",
85 …system into soft off (S4/S45) state. This is for ‘emergency’ management power down actions. The co…
87 … the deassertion of the system’s POWERGOOD status from the main power subsystem. It is recommended…
88 …know whether a reset will cause any particular effect and will pulse the system reset signal regar…
89 …ectly to the processor(s). This is typically used to cause the operating system to do a diagnostic…
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | video-interface-devices.yaml | 34 A camera sensor has a 2-dimensional reference system 'Rc' defined by its
52 The external world scene reference system 'Rs' is a 2-dimensional
53 reference system on the focal plane of the camera module. The origin is
76 with the reference system 'Rs' placed on the camera focal plane:
89 reference system 'Rs' are typically (but not always) inverted, due to the
93 inversion projects the scene and its reference system onto the sensor
112 The resulting projected reference system is named 'Rp'.
115 the counter-clockwise direction between the camera reference system 'Rc'
349 'Rc' reference system.
390 system where the device is installed on.
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-genesis3/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bbappend | 22 ${PN}-system \
27 virtual/obmc-system-mgmt \
30 RPROVIDES:${PN}-system += "virtual-obmc-system-mgmt"
|
| /openbmc/linux/fs/hpfs/ |
| H A D | Kconfig | 3 tristate "OS/2 HPFS file system support"
8 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
9 is the file system used for organizing files on OS/2 hard disk
16 To compile this file system support as a module, choose M here: the
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Hardware.interface.yaml | 5 registers, and it is used for debugging system checkstop. checkstop is the
6 descriptive term for entire system termination by the hardware due to a
14 This ID is a reference to an error log entry in the logging system.
22 within the system. The value should be a 32-bit unsigned integer.
|
| /openbmc/linux/Documentation/power/ |
| H A D | userland-swsusp.rst | 13 utilities that will read/write the system memory snapshot from/to the
45 create a snapshot of the system memory; the
49 from it (0) (after resume the system finds itself finishing the
55 restore the system memory state from the
57 the system memory snapshot back to the kernel using the write()
104 make the kernel transition the system to the hibernation
151 resumed system may be totally unpredictable.
168 created and the system is ready for saving it):
175 system MUST be powered off or rebooted after the snapshot
178 file system operations (including reads) on the file systems
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | README.md | 19 on voltage regulators in the system:
46 - [Name Based on System Type](#name-based-on-system-type)
57 required if the BMC firmware image supports multiple system types, and those
58 system types do not share a common config file.
60 A config file is normally system-specific. Each system type usually has a
63 The system type is obtained from a D-Bus Chassis object created by the
69 system types. The types are ordered from most specific to least specific.
84 - The complete compatible system type plus a '.json' suffix
85 - The last node of the compatible system type plus a '.json' suffix
92 If a config file is not found based on system type, `phosphor-regulators`
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.sata | 6 * ext2load to read a file from ext2 file system
17 1.1 How to raw write the kernel, file system, dtb to a SATA hard disk?
34 1.2 How to raw read the kernel, file system, dtb from a SATA hard disk?
48 1.3 How to load an image from an ext2 file system in U-Boot?
50 U-Boot doesn't support writing to an ext2 file system, so the
|
| /openbmc/linux/Documentation/admin-guide/nfs/ |
| H A D | pnfs-scsi-server.rst | 13 system needs to support the pNFS SCSI layouts (currently just XFS), and the
14 file system must sit on a SCSI LUN that is accessible to the clients in
15 addition to the MDS. As of now the file system needs to sit directly on the
20 automatically enabled if the file system is exported using the "pnfs"
23 enabled, and the file system is mounted using the NFSv4.1 protocol
|
| H A D | pnfs-block-server.rst | 12 system needs to support the pNFS block layouts (currently just XFS), and the
13 file system must sit on shared storage (typically iSCSI) that is accessible
14 to the clients in addition to the MDS. As of now the file system needs to
18 On the server, pNFS block volume support is automatically if the file system
21 file system is mounted using the NFSv4.1 protocol version (mount -o vers=4.1).
26 prefix for the file system to be fenced. Below is an example file that shows
|
| /openbmc/qemu/docs/system/ |
| H A D | target-avr.rst | 6 Use the executable ``qemu-system-avr`` to emulate a AVR 8 bit based machine.
22 qemu-system-avr -machine mega2560 -bios demo.elf
26 qemu-system-avr -M mega2560 -bios demo.elf -nographic \
35 qemu-system-avr -machine mega2560 -bios demo.elf -s -S
48 qemu-system-avr -machine mega2560 -bios demo.elf -d in_asm
|
| /openbmc/bmcweb/test/redfish-core/include/utils/ |
| H A D | dbus_utils.cpp | 27 boost::system::error_code ec; in TEST()
40 boost::system::error_code ec; in TEST()
66 boost::system::error_code ec = in TEST()
67 boost::system::errc::make_error_code(boost::system::errc::timed_out); in TEST()
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-presence-config/swift/ |
| H A D | config.yaml | 2 path: /system/chassis/motherboard/fan0
15 path: /system/chassis/motherboard/fan1
28 path: /system/chassis/motherboard/fan2
41 path: /system/chassis/motherboard/fan3
55 path: /system/chassis/motherboard/fan4
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | gfs2.rst | 7 GFS2 is a cluster file system. It allows a cluster of computers to
10 file system, but also uses a lock module to allow the computers coordinate
11 their I/O so file system consistency is maintained. One of the nifty
12 features of GFS2 is perfect consistency -- changes made to the file system
19 - allows GFS2 to be used as a local file system
28 To use GFS2 as a local file system, no external clustering systems are
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/ |
| H A D | adbd.mk | 44 SOURCES := $(foreach source, $(SOURCES), system/core/$(source))
50 CPPFLAGS += -Isystem/coreinclude -Isystem/core/adb -Isystem/core/base/include -Idebian/out/system/…
54 …-lpthread -Ldebian/out/system/core -Ldebian/out/external/boringssl -lbase -lcrypto_utils -l:libcry…
83 mkdir --parents debian/out/system/core
84 $(CXX) $^ -o debian/out/system/core/adbd $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS)
87 $(RM) debian/out/system/core/adbd
|
| /openbmc/linux/Documentation/devicetree/bindings/cache/ |
| H A D | socionext,uniphier-system-cache.yaml | 4 $id: http://devicetree.org/schemas/cache/socionext,uniphier-system-cache.yaml#
11 controller system. All of them have a level 2 cache controller, and some
19 const: socionext,uniphier-system-cache
68 compatible = "socionext,uniphier-system-cache";
81 compatible = "socionext,uniphier-system-cache";
93 compatible = "socionext,uniphier-system-cache";
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/netcf/ |
| H A D | netcf_0.2.8.bb | 54 install -d ${D}${systemd_unitdir}/system
55 if [ -d "${D}${libdir}/systemd/system" ]; then
57 mv ${D}${libdir}/systemd/system/* ${D}${systemd_unitdir}/system/
61 mv ${D}${nonarch_libdir}/systemd/system/* ${D}${systemd_unitdir}/system/
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-mce | 1 What: /sys/devices/system/machinecheck/machinecheckX/
21 What: /sys/devices/system/machinecheck/machinecheckX/bank<Y>
38 What: /sys/devices/system/machinecheck/machinecheckX/check_interval
56 What: /sys/devices/system/machinecheck/machinecheckX/trigger
67 What: /sys/devices/system/machinecheck/machinecheckX/monarch_timeout
76 What: /sys/devices/system/machinecheck/machinecheckX/ignore_ce
83 What: /sys/devices/system/machinecheck/machinecheckX/dont_log_ce
93 What: /sys/devices/system/machinecheck/machinecheckX/cmci_disabled
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | read-only-rootfs.rst | 8 filesystem). Or, perhaps you are running the device's operating system
14 Supporting a read-only root filesystem requires that the system and
16 configure all parts of the target system to write elsewhere, or to
48 the build on the host system. These scripts cannot attempt to run during
50 enabled, the build system makes sure that all post-installation scripts
51 succeed at file system creation time. If any of these scripts
58 system for the out-of-the-box Yocto Project are engineered so that they
61 need to be sure they can be run during this file system creation.
66 - *Not using $D in front of absolute paths:* The build system defines
76 native tools, which run on the host system, to accomplish the same
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | asymmetric-32bit.rst | 17 a system, Linux by default treats the asymmetry as a "mismatch" and
38 allowing 32-bit tasks to run on an asymmetric 32-bit system requires an
43 system* to mean an asymmetric 32-bit SoC running Linux with this kernel
49 32-bit tasks running on an asymmetric system behave in mostly the same
50 way as on a homogeneous system, with a few key differences relating to
57 ``/sys/devices/system/cpu/aarch32_el0`` and is documented further in
58 ``Documentation/ABI/testing/sysfs-devices-system-cpu``.
69 ``execve(2)``. This is not always possible on an asymmetric system,
107 32-bit system unless admission control is disabled by writing -1 to
119 32-bit tasks on an asymmetric system. Failure to do so is likely to
[all …]
|
| /openbmc/phosphor-fan-presence/docs/control/ |
| H A D | README.md | 7 - [System Config Location](#system-config-location)
63 and those system types can not share any one common config file.
65 A system type sub-directory can be obtained from the
67 property holds a list of one or more compatible system types.
121 system.
166 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan0",
167 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan1",
168 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan2",
169 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan3",
170 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan4",
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/logging/files/ |
| H A D | callouts.yaml | 2 …m/ahb/1e780000.apb/1e780000.apb:bus@1e78a000/1e78a100.i2c/i2c-3/3-0052: /system/chassis/motherboard
3 /sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw: /system/chassis/motherboard/cpu0
4 /sys/devices/platform/gpio-fsi/fsi0/slave@00:00/00:00:00:0a/fsi1/slave@01:00/raw: /system/chassis/m…
|
| /openbmc/bmcweb/redfish-core/lib/ |
| H A D | chassis.hpp | 63 [asyncResp](const boost::system::error_code& ec, in getStorageLink()
111 if (ec == boost::system::errc::host_unreachable) in getChassisState()
149 const boost::system::error_code& ec, in handlePhysicalSecurityGetSubTree()
336 [asyncResp](const boost::system::error_code& ec, in getChassisLocationCode()
358 [asyncResp](const boost::system::error_code& ec, in getChassisUUID()
449 nlohmann::json::object_t system; in handleDecoratorAssetProperties() local
450 system["@odata.id"] = in handleDecoratorAssetProperties()
452 computerSystems.emplace_back(std::move(system)); in handleDecoratorAssetProperties()
613 path](const boost::system::error_code&, in handleChassisGetSubTree()
709 indicatorLed](const boost::system::error_code& ec, in handleChassisPatch()
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/websocketpp/websocketpp-0.8.2/ |
| H A D | 1024.patch | 58 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
84 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
123 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
162 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
175 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
188 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
214 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
253 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
266 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
279 ALL_LIBS = boostlibs(['system'],env_cpp11) + [platform_libs] + [polyfill_libs]
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/configuration/romulus-yaml-config/ |
| H A D | romulus-ipmi-fru-bmc.yaml | 2 /system/chassis/motherboard/fan0:
11 /system/chassis/motherboard/fan1:
20 /system/chassis/motherboard/fan2:
|