| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | Thermal.events.yaml | 18 A event signaling that a device is operating over a set operating
22 message: Device {Device} is over safe operating temperature.
40 due to it operating significantly in excess of the set operating
44 Device {Device} is significantly over safe operating temperature
57 A event signaling that a device is operating over a set operating
59 message: Device {Device} is operating in normal temperature.
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | rk3399-op1-opp.dtsi | 8 compatible = "operating-points-v2";
43 compatible = "operating-points-v2";
86 compatible = "operating-points-v2";
116 operating-points-v2 = <&cluster0_opp>;
120 operating-points-v2 = <&cluster0_opp>;
124 operating-points-v2 = <&cluster0_opp>;
128 operating-points-v2 = <&cluster0_opp>;
132 operating-points-v2 = <&cluster1_opp>;
136 operating-points-v2 = <&cluster1_opp>;
140 operating-points-v2 = <&gpu_opp_table>;
|
| H A D | sun8i-h3.dtsi | 47 compatible = "operating-points-v2";
79 operating-points-v2 = <&cpu0_opp_table>;
89 operating-points-v2 = <&cpu0_opp_table>;
99 operating-points-v2 = <&cpu0_opp_table>;
109 operating-points-v2 = <&cpu0_opp_table>;
|
| H A D | imx6q.dtsi | 24 operating-points = <
32 fsl,soc-operating-points = <
59 operating-points = <
67 fsl,soc-operating-points = <
93 operating-points = <
101 fsl,soc-operating-points = <
127 operating-points = <
135 fsl,soc-operating-points = <
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | OperatingSystem.v1_0_2.json | 36 "description": "A container engine running in an operating system.",
37 … "longDescription": "This type shall contain a container engine running in an operating system.",
127 "description": "The kernel information for an operating system.",
128 … "longDescription": "This type shall contain the kernel information for an operating system.",
146 …hall contain the machine hardware name of the kernel. For strict POSIX operating systems, the val…
155 … "This property shall contain the name of the kernel. For strict POSIX operating systems, the val…
164 …his property shall contain the release of the kernel. For strict POSIX operating systems, the val…
173 …his property shall contain the version of the kernel. For strict POSIX operating systems, the val…
209 "description": "The link to the software image for this operating system.",
210 …ype `SoftwareInventory` that represents the software image from which this operating system runs.",
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | s390-dasd-ipl.rst | 32 IPL2 is to find and load either the operating system or a small program that
33 loads the operating system from disk. At the end of this step all or some of
34 the real operating system is loaded into memory and we are ready to hand
35 control over to the guest operating system. At this point the guest
36 operating system is entirely responsible for loading any more data it might
42 address points to the guest operating system code to execute at the end of
47 4. Start executing the guest operating system.
49 should contain the needed flags for the operating system we have loaded. The
51 to start executing the operating system. This psw is loaded (via LPSW
52 instruction) causing control to be passed to the operating system code.
[all …]
|
| H A D | s390-cpu-topology.rst | 41 "cpu-state": "operating",
56 "cpu-state": "operating",
71 "cpu-state": "operating",
86 "cpu-state": "operating",
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | OperatingSystem_v1.xml | 54 …"OData.Description" String="The `OperatingSystem` schema represents the operating system and softw…
55 … Term="OData.LongDescription" String="This resource shall represent the operating system and softw…
92 <Annotation Term="OData.Description" String="The type of operating system."/>
93 …="OData.LongDescription" String="This property shall contain the type for this operating system."/>
97 …<Annotation Term="OData.Description" String="The wall-clock time this operating system has been ru…
98 …scription" String="This property shall contain the wall-clock time this operating system has been …
101 … <Annotation Term="OData.Description" String="The kernel information for this operating system."/>
102 …scription" String="This property shall contain the kernel information for this operating system."/>
105 …n Term="OData.Description" String="The virtual machine engines running in this operating system."/>
106 …tring="This property shall contain the virtual machine engines running in this operating system."/>
[all …]
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | environmental_message_registry.hpp | 70 "Fan group '%1' is operating normally.",
177 …g is no longer below the lower critical threshold but is still outside of normal operating range.",
191 …ding is no longer below the lower fatal threshold but is still outside of normal operating range.",
289 …g is no longer above the upper critical threshold but is still outside of normal operating range.",
303 …ding is no longer above the upper fatal threshold but is still outside of normal operating range.",
369 "Indicates that a flow rate reading is now within normal operating range.",
370 "Flow rate '%1' reading of %2 L/min is within normal operating range.",
395 …g is no longer below the lower critical threshold but is still outside of normal operating range.",
409 …ding is no longer below the lower fatal threshold but is still outside of normal operating range.",
507 …g is no longer above the upper critical threshold but is still outside of normal operating range.",
[all …]
|
| H A D | power_message_registry.hpp | 105 …g is no longer below the lower critical threshold but is still outside of normal operating range.",
119 …ding is no longer below the lower fatal threshold but is still outside of normal operating range.",
217 …g is no longer above the upper critical threshold but is still outside of normal operating range.",
231 …ding is no longer above the upper fatal threshold but is still outside of normal operating range.",
271 "Indicates that a current reading is now within normal operating range.",
272 "Current '%1' reading of %2 amperes is within normal operating range.",
297 …g is no longer below the lower critical threshold but is still outside of normal operating range.",
367 …g is no longer above the upper critical threshold but is still outside of normal operating range.",
407 "Indicates that a frequency reading is now within normal operating range.",
408 "Frequency '%1' reading of %2 hertz is within normal operating range.",
[all …]
|
| H A D | sensor_event_message_registry.hpp | 57 …g is no longer below the lower critical threshold but is still outside of normal operating range.",
72 …ding is no longer below the lower fatal threshold but is still outside of normal operating range.",
177 …g is no longer above the upper critical threshold but is still outside of normal operating range.",
192 …ding is no longer above the upper fatal threshold but is still outside of normal operating range.",
261 "Indicates that a sensor reading is now within normal operating range.",
262 "Sensor '%1' reading of %2 (%3) is within normal operating range.",
|
| H A D | telemetry_message_registry.hpp | 59 …onger below the lower critical trigger threshold, but is still outside of normal operating range.",
134 …onger above the upper critical trigger threshold, but is still outside of normal operating range.",
149 "Indicates that a numeric metric reading is now within normal operating range.",
150 "Metric '%1' value of %2 is within normal operating range of trigger '%3'",
|
| /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.
39 Operating system is ready to be booted.
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap5/ |
| H A D | Kconfig | 77 Select the Operating Performance Point(OPP) for the MPU voltage
91 Select the Operating Performance Point(OPP) for the DSPEVE voltage
115 Select the Operating Performance Point(OPP) for the IVA voltage
139 Select the Operating Performance Point(OPP) for the GPU voltage
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Caldera | 1 …Operating Systems that operate on the 16-Bit PDP-11 CPU and early versions of the 32-Bit UNIX Oper…
|
| H A D | Multics | 13 Inc. to the development of this operating system. Multics development
19 for executing programs. Many subsequent operating systems incorporated
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Leak/ |
| H A D | DetectorGroup.events.yaml | 39 The detector group has returned to its normal operating state.
40 message: Detector group {DetectorName} is operating normally.
|
| /openbmc/u-boot/doc/usage/ |
| H A D | measured_boot.rst | 8 component's measurement in memory for the operating system to consume.
21 * The operating system must also be configured to use the memory regions
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Boot/ |
| H A D | Progress.interface.yaml | 49 Starting Operating System.
52 Operating System up and running
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | custom-runners.yml | 2 # registered on machines that match their operating system names,
8 # jobs should be capable of running on operating systems with no
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/gnulib/ |
| H A D | gnulib_202401.bb | 3 be usable on many operating systems. The goal of the project \
5 software run on many operating systems. Since source is designed \
|
| /openbmc/u-boot/arch/arm/cpu/armv7/ |
| H A D | exception_level.c | 8 * secure mode before booting an operating system.
38 * Operating systems may expect to run in non-secure mode. Here we check if
|
| /openbmc/u-boot/arch/arm/cpu/armv8/ |
| H A D | exception_level.c | 8 * level before booting an operating system.
37 * trusted firmware being one embodiment). The operating system shall be
|
| /openbmc/u-boot/doc/ |
| H A D | README.iscsi | 11 operating system kernel and the initial file system (initrd).
17 Furthermore the services providing the operating system loader or kernel are
18 not the ones that the operating system typically will use. Especially in a SAN
19 environment this makes updating the operating system a hassle. After installing
32 same target where the operating system is installed.
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | acpi-bits.rst | 13 operating system getting involved in between. Bios-bits has python integration
18 operating system (the OS). Operating systems tend to bypass bios problems and
21 complicated software component such as an operating system coming in between.
25 land software resides in unprivileged ring 3, operating system must be modified
|