| /openbmc/openpower-debug-collector/watchdog/ |
| H A D | watchdog_logging.cpp | 19 * @param additional - Additional PEL data
22 void event(std::map<std::string, std::string>& additional, in event() argument
30 // Create PEL with additional data. in event()
31 auto pelId = createPel(eventName, additional, emptyFfdc); in event()
46 // Additional data to be added to PEL object in eventWatchdogTimeout()
|
| H A D | watchdog_dbus.hpp | 42 * The additional data provided in the map will be placed in a user data
46 * @param additional - map of additional data
51 std::map<std::string, std::string>& additional,
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | attn_dbus.cpp | 70 // Additional data for log in createPelRaw()
71 std::map<std::string, std::string> additional; in createPelRaw() local
72 additional.emplace("RAWPEL", filePath.string()); in createPelRaw()
73 additional.emplace("_PID", std::to_string(getpid())); in createPelRaw()
85 // append additional dbus call parameters in createPelRaw()
86 method.append(eventPelTerminate, levelPelError, additional); in createPelRaw()
116 // additional dbus call parameters in getPel()
|
| H A D | attn_logging.cpp | 98 * to the backend logging code as a raw PEL. Note that additional data map
103 * @param i_additional - additional data to be added to the new PEL
111 // The additional data contains the TI info as well as the value for the in createPelCustom()
112 // subystem that provided the TI info. Get the subystem from additional in createPelCustom()
126 // The entry with key "Subsystem" does not exist in the additional map. in createPelCustom()
175 // The entry with key "Subsystem" does not exist in the additional in createPelCustom()
207 // data (additional data "0x10 HB Word") is reflected in the PEL as in createPelCustom()
234 // The entry with key "Subsystem" does not exist in the additional in createPelCustom()
311 * @param i_additional - Additional PEL data
358 // Create PEL with additional data and FFDC data. The newly created in event()
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | BUSL-1.1 | 10 Licensor may make an Additional Use Grant, above, permitting limited
62 later version. Licensor may specify additional Change Licenses without
65 2. To either: (a) specify an additional grant of rights to use that does not
66 impose any additional restriction on the right granted in this License, as
67 the Additional Use Grant; or (b) insert the text “None”.
|
| H A D | LPPL-1.2 | 65 1. You must meet any additional conditions borne by the file on the
67 in the subsection `Additional Conditions on Individual Files of
71 applicable additional conditions on the distribution of a modified
73 `Additional Conditions on LaTeX Software Files`.
153 Additional Conditions on Individual Files of The Program
156 An individual file of The Program may bear additional conditions that
158 if, such additional conditions exclusively concern modification of the
166 Additional Conditions on LaTeX Software Files
170 if it is a LaTeX software file), then the following additional
301 If The Program contains any files bearing additional conditions on
[all …]
|
| H A D | LPPL-1.1 | 65 1. You must meet any additional conditions borne by the file on the
67 in the subsection `Additional Conditions on Individual Files of
71 applicable additional conditions on the distribution of a modified
73 `Additional Conditions on LaTeX Software Files`.
152 Additional Conditions on Individual Files of The Program
155 An individual file of The Program may bear additional conditions that
157 if, such additional conditions exclusively concern modification of the
165 Additional Conditions on LaTeX Software Files
169 if it is a LaTeX software file), then the following additional
300 If The Program contains any files bearing additional conditions on
[all …]
|
| H A D | SGI-B-1.0 | 6 …1.1 "Additional Notice Provisions" means such additional provisions as appear in the Notice in Ori…
42 …Modifications are fully compliant with any API as may be identified in Additional Notice Provision…
46 …ere the Recipient’s rights relating to Covered Code are described. Any Additional Notice Provision…
82 Additional Notice Provisions: [such additional provisions, if any, as appear in the Notice in the O…
|
| /openbmc/bmcweb/ |
| H A D | meson.options | 370 # Additional ports
379 'additional-ports',
382 description: '''Additional ports to listen to. Allows bmcweb to listen to
387 'additional-protocol',
391 additional-ports index. Allows setting http, https, or both
393 additional-ports index, assumes https.''',
397 'additional-bind-to-device',
401 directive for each additional socket file. If not provided
402 for a given additional-ports index, assumes bind to all
407 'additional
[all...] |
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | platform_message_registry.hpp | 50 "Check additional diagnostic data if available.",
60 "Check additional diagnostic data if available.",
72 "Check additional diagnostic data if available.",
82 "Check additional diagnostic data if available.",
|
| /openbmc/u-boot/fs/ubifs/ |
| H A D | debug.h | 200 /* Additional journal messages */
204 /* Additional TNC messages */
208 /* Additional lprops messages */
210 /* Additional LEB find messages */
212 /* Additional mount messages */
216 /* Additional I/O messages */
218 /* Additional commit messages */
220 /* Additional budgeting messages */
222 /* Additional log messages */
224 /* Additional gc messages */
[all …]
|
| /openbmc/u-boot/Documentation/sphinx/ |
| H A D | load_config.py | 12 u"""Load an additional configuration file into *namespace*.
25 sys.stdout.write("load additional sphinx-config: %s\n" % config_file)
32 sys.stderr.write("WARNING: additional sphinx-config not found: %s\n" % config_file)
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | create-spdx-3.0.bbclass | 25 SPDX_PACKAGE_ADDITIONAL_PURPOSE[doc] = "The list of additional purposes to assign to \
27 Packages overrides are allowed to override the additional purposes for \
32 The first listed item will be the Primary Purpose and all additional items will \
33 be added as additional purposes"
37 The first listed item will be the Primary Purpose and all additional items will \
38 be added as additional purposes"
|
| /openbmc/qemu/qapi/ |
| H A D | introspect.json | 116 # Additional `SchemaInfo` members for meta-type 'builtin'.
157 # Additional `SchemaInfo` members for meta-type 'enum'.
197 # Additional `SchemaInfo` members for meta-type 'array'.
211 # Additional `SchemaInfo` members for meta-type 'object'.
219 # @variants: variant members, i.e. additional members that depend on
276 # Additional `SchemaInfo` members for meta-type 'alternate'.
304 # Additional `SchemaInfo` members for meta-type 'command'.
326 # Additional `SchemaInfo` members for meta-type 'event'.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/ |
| H A D | LICENSE-OASIS | 10 referencing additional sets of general entities and declaring
11 additional notations, label your DTD as a variant of DocBook. See
|
| /openbmc/phosphor-power/tools/power-utils/ |
| H A D | updater.hpp | 160 * and additional data. It interacts with the OpenBMC logging service to
165 * @param[in] additionalData Additional key-value pairs containing details
173 * @brief Retrieves additional data related to I2C communication.
187 * It collects additional data about the I2C communication and logs the
190 * @param[in] extraAdditionalData Additional key-value pairs specific to
203 * This method logs a failure related to PSU firmware updates and additional
206 * @param[in] extraAdditionalData Additional key-value pairs specific to
216 * software-related errors. It merges any additional error-specific data
219 * @param[in] extraAdditionalData Additional key-value pairs specific to
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | Device.errors.yaml | 6 # for additional information.
14 # additional information.
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 67 - If your SDK configuration inherits additional classes using the
83 - If you have classes or recipes that add additional tasks to the
102 the SDK can add additional items to the SDK after installation
104 ":ref:`sdk-manual/appendix-customizing:providing additional installable extensible sdk content`"
171 perform additional steps. These steps make it possible for anyone using
240 Providing Additional Installable Extensible SDK Content
247 #. Ensure the additional items you want the user to be able to install
257 variable for additional information.
328 See the :term:`SDK_INCLUDE_PKGDATA` variable for additional information.
338 the "world" target if you want to provide additional items to the SDK.
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/.github/ |
| H A D | ISSUE_TEMPLATE.md | 25 **Additional information you deem important (e.g. issue happens only occasionally):**
27 **Additional details (revisions used, host distro, etc.):**
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | standard_device.hpp | 123 * @param additionalData Additional data to include in the error log if
133 * Store pgood fault debug data in the specified additional data map.
146 * @param additionalData Additional data to include in an error log
153 * Store GPIO values in the specified additional data map.
164 * @param additionalData Additional data to include in an error log
|
| /openbmc/phosphor-logging/lib/ |
| H A D | lg2_commit.hpp | 14 /** Extract the message, level, and additional data from agenerated event.
17 * @return A tuple containing the message, level, and additional data.
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | 3270.rst | 22 ``CONFIG_TN3270`` and at least one of ``CONFIG_TN3270_TTY`` (for additional
42 This should get you an additional tty for logging into the guest.
45 an additional tty, you can also append ``conmode=3270 condev=000a`` to
|
| /openbmc/qemu/tcg/tci/ |
| H A D | README | 26 The additional file tcg/tci.c adds the interpreter and disassembler.
41 additional code in configure which must be fixed when new native TCG
55 qemu.log files. This is also useful to see the effects of additional
56 registers or additional opcodes (it is easy to modify the virtual machine).
|
| /openbmc/phosphor-power/phosphor-regulators/src/actions/ |
| H A D | action_environment.hpp | 48 * - additional error data captured by actions (if any)
79 * Adds the specified key/value pair to the map of additional error data
120 * Returns the additional error data that has been captured (if any).
122 * @return additional error data
279 * Additional error data that has been captured.
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.md | 35 - Any additional patches or changes:
37 **Additional context**
|