Home
last modified time | relevance | path

Searched +full:build +full:- +full:system1 (Results 1 – 7 of 7) sorted by relevance

/openbmc/openbmc/meta-ibm/meta-system1/conf/templates/default/
H A Dbblayers.conf.sample1 # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
10 ##OEROOT##/meta-openembedded/meta-oe \
11 ##OEROOT##/meta-openembedded/meta-networking \
12 ##OEROOT##/meta-openembedded/meta-python \
13 ##OEROOT##/meta-security/meta-tpm \
14 ##OEROOT##/meta-phosphor \
15 ##OEROOT##/meta-aspeed \
16 ##OEROOT##/meta-ibm \
17 ##OEROOT##/meta-ibm/meta-system1 \
H A Dlocal.conf.sample17 MACHINE ??= "system1"
22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
[all …]
/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
96 "System": "system1",
105 The above example shows that on system 'system1' the severity will be recovered,
132 applicable" for non-informational logs, and "misc_information_only" for
[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 …]
/openbmc/
Dopengrok1.0.log1 2025-11-09 03:01:12.083-0600 FINE t1 Executor.registerErrorHandler: Installing default uncaught exception handler
2 2025-11-09 03:01:12.139-0600 INFO t1 Indexer.parseOptions: Indexer options: [-c, /usr/local/bin/ctags, -T, 12, -s, /opengrok/src, -
[all...]
Dopengrok2.0.log1 2025-11-08 03:01:19.154-0600 FINE t1 Executor.registerErrorHandler: Installing default uncaught exception handler
2 2025-11-08 03:01:19.229-0600 INFO t1 Indexer.parseOptions: Indexer options: [-c, /usr/local/bin/ctags, -T, 12, -s, /opengrok/src, -
[all...]