Searched +full:free +full:- +full:standing (Results 1 – 12 of 12) sorted by relevance
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
H A D | Chassis.interface.yaml | 5 - name: Type 12 - name: ChassisType 16 - name: Blade 18 An enclosed or semi-enclosed, typically vertically-oriented, 19 system chassis that must be plugged into a multi-system chassis 21 - name: Component 25 - name: Enclosure 29 - name: Module 33 - name: RackMount 35 A single-system chassis designed specifically for mounting in an [all …]
|
/openbmc/entity-manager/scripts/ |
H A D | autojson.py | 11 # Trying to parse JSON comments and then being able to re-insert them into 12 # the correct location on a re-emitted and sorted JSON would be very difficult. 15 # - Single-line style comments (//) can be on a new line or at the end of 18 # - Multi-line style comments (/* */) use the must be free-standing. 20 # - Comments will get inserted back into the file in the line they came 24 # - No attempts to re-indent multi-line comments will be made. 27 # prettier before using this script and planning to move multi-line comments 37 def __init__(self) -> None: 40 # Extract out the comments from a JSON-like string and save them away. 41 def extract_comments(self, contents: str) -> str: [all …]
|
/openbmc/qemu/hw/watchdog/ |
H A D | spapr_watchdog.c | 2 * This library is free software; you can redistribute it and/or 4 * License as published by the Free Software Foundation; either 25 FIELD(reg, field, 64 - (start + len), len) 30 * 0 - stop out-standing watchdogs on timeout, 31 * 1 - leave outstanding watchdogs running on timeout 35 /* Bits 48-55: "operation" */ 42 /* Bits 56-63: "timeoutAction" */ 56 * Bits 0-15: The minimum supported timeout in milliseconds 57 * Bits 16-31: The number of watchdogs supported 58 * Bits 32-63: Reserved [all …]
|
/openbmc/openbmc/poky/meta/recipes-support/boost/ |
H A D | boost.inc | 1 SUMMARY = "Free peer-reviewed portable C++ source libraries" 2 DESCRIPTION = "Provides free peer-reviewed portable C++ source libraries. The emphasis is on libra… 7 DEPENDS = "boost-build-native zlib bzip2" 55 PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich" 59 inherit python3-dir 62 # Make a package for each library, plus -dev 63 PACKAGES = "${PN}-dbg ${BOOST_PACKAGES}" 70 extras.append("--with-%s" % lib) 71 pkg = "%s-%s" % (d.getVar("BPN"), lib.replace("_", "-")) 72 if "-native" in pn: [all …]
|
/openbmc/entity-manager/ |
H A D | CONFIG_FORMAT.md | 12 - Configuration files will get replicated and built to support hundreds of 18 - Reactor writers tend to be domain experts on their subsystem, and 28 - Hardware constraints, bugs, and oddities are generally found over time. The 33 - Having separate config files reduces the number of platforms that need to 37 - Having one config file per piece of hardware makes it much easier and clear 39 - Note: This is a "guideline" not a "rule". There are many cases of hardware 42 - Example: SAS modules and cards made by the same company, on the same 44 - Non-Example: Power supplies. While all pmbus power supplies appear 49 3. Configuration files are not a long-term stable ABI. Why? 50 - Configuration files occasionally need to modify their schema in pursuit of [all …]
|
/openbmc/libmctp/docs/bindings/ |
H A D | vendor-ibm-astlpc.md | 18 …<https://www.intel.com/content/dam/www/program/design/us/en/documents/low-pin-count-interface-spec… 29 MCTP-compliant endpoints must accept. 33 A hardware-defined flag bit in a KCS device's Status Register (STR). The IBF 42 ### KCS: Keyboard-Controller-Style 48 systems. This interface is available built-in to several commercially available 49 microcontrollers. Data is transferred across the KCS interface using a per-byte 68 values larger than the BTU may improve throughput for data-intensive transfers. 72 A hardware-defined flag bit in a KCS device's Status Register (STR). The OBF 84 BMC-controlled, eight-bit register exposed to both the BMC and the host for 86 Bits that are not defined by hardware can be software-controlled in a manner [all …]
|
/openbmc/qemu/docs/devel/ |
H A D | style.rst | 1 .. _coding-style: 39 * Tabs are rendered badly in patches, causing off-by-one errors in almost 46 ---------------- 62 .. code-block:: c 77 .. code-block:: c 100 as a guard against obviously-overlength lines, not a target.) 109 * The four-space indentation makes the most common excuse ("But look 117 type names are in CamelCase; harder to type but standing out. Enum type 124 --------------------------- 135 --------------------------- [all …]
|
/openbmc/openbmc/poky/documentation/overview-manual/ |
H A D | yp-intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK 11 developers create custom Linux-based systems that are designed for 26 .. image:: figures/key-dev-elements.png 31 …ticle <https://www.embedded.com/electronics-blogs/say-what-/4458600/Why-the-Yocto-Project-for-my-I… 39 -------- 43 - *Widely Adopted Across the Industry:* Many semiconductor, operating 50 - *Architecture Agnostic:* Yocto Project supports Intel, ARM, MIPS, 59 - *Images and Code Transfer Easily:* Yocto Project output can easily 68 - *Flexibility:* Corporations use the Yocto Project many different 75 - *Ideal for Constrained Embedded and IoT devices:* Unlike a full Linux [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Chassis.v1_27_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json", 5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or… 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 31 "description": "The available OEM-specific actions for this resource.", 32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour… 39 …nts the physical components of a system. This resource represents the sheet-metal confined spaces… 42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context" 60 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag" 63 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id" [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | Chassis.v1_27_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json", 5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or… 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 31 "description": "The available OEM-specific actions for this resource.", 32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour… 39 …nts the physical components of a system. This resource represents the sheet-metal confined spaces… 42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context" 60 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag" 63 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id" [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | Chassis_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ --> 4 <!--# Redfish Schema: Chassis v1.27.0 --> 5 <!--# --> 6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, --> 7 <!--# available at http://www.dmtf.org/standards/redfish --> 8 <!--# Copyright 2014-2025 DMTF. --> 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright --> 10 <!--################################################################################ --> [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Chassis_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ --> 4 <!--# Redfish Schema: Chassis v1.27.0 --> 5 <!--# --> 6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, --> 7 <!--# available at http://www.dmtf.org/standards/redfish --> 8 <!--# Copyright 2014-2025 DMTF. --> 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright --> 10 <!--################################################################################ --> [all …]
|