Home
last modified time | relevance | path

Searched +full:build +full:- +full:system2 (Results 1 – 3 of 3) sorted by relevance

/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DREADME.md4 phosphor-logging using a message registry that provides the PEL related fields.
9 - [Component IDs](#component-ids)
10 - [Message Registry](#message-registry-fields)
11 - [Modifying and Testing](#modifying-and-testing)
30 Component IDs will be unique on a per-repository basis for errors unique to that
41 validated either during a bitbake build or during CI, or eventually possibly
69 This field is used by scripts that build documentation from the message registry
132 applicable" for non-informational logs, and "misc_information_only" for
150 [OpenPower PELs README](../README.md#action-flags-and-event-type-rules).
185 - BD = SRC type
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Dregistry.cpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright 2019 IBM Corporation
9 #include <phosphor-logging/lg2.hpp>
24 constexpr auto debugFilePath = "/etc/phosphor-logging/";
194 // Build the map of which AdditionalData fields to use for which SRC words in getSRCHexwordFields()
249 auto srcWordNum = field.substr(field.size() - 1); in getSRCSymptomIDFields()
307 * @param[in] json - The highest level callout JSON
309 * @return bool - If it is the AdditionalData format or not
324 * System key - Value of the key will be the system name as a string. The
327 * Systems key - Value of the key will be an array of system names in the form
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/
H A Dschema.json3 …"$id": "http://github.com/openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/schem…
89 "pattern": "^0x[0-9A-F]{2}00$"
161 "pattern": "^0x[0-9A-F]{4}$",
262 …to pass in the subsystem. Used by scripts that generate documentation to build all possible SRC A…
410 …holders for numeric values using %1, %2, etc, that come from the SRC words 6-9 as defined by the M…
419 …"description": "The SRC word 6-9 to use as the source of the numeric arguments that will be substi…
451 …"description": "This details what the user defined SRC hex words (6-9) mean, and which AdditionalD…
454 "^[6-9]$": {
493 "description": "A location code - the segment after the 'UTMS-' prefix. (e.g. P1-C2)",
538 …allout. List of available procedures is at https://github.com/ibm-openbmc/openpower-pel-parsers/bl…
[all …]