/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/edid-decode/ |
H A D | edid-decode_git.bb | 1 SUMMARY = "Decode EDID data in human-readable format" 2 DESCRIPTION = "edid-decode decodes EDID monitor description data in human-readable format."
|
/openbmc/qemu/python/qemu/qmp/ |
H A D | error.py | 45 :param error_message: Human-readable string describing the error. 49 #: Human-readable error message, without any prefix.
|
/openbmc/qemu/include/standard-headers/linux/ |
H A D | virtio_crypto.h | 273 /* Device-readable part */ 289 /* Device-readable part */ 400 /* Device-readable part */ 406 /* Device-readable part */ 412 /* Device-readable part */ 439 /* Device-readable part */ 456 /* Device-readable part */
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_net.py | 44 'fn': 'ubtest-readable.bin', 53 'fn': 'ubtest-readable.bin', 145 pytest.skip('No TFTP readable file to read') 186 pytest.skip('No NFS readable file to read')
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvstreams/ |
H A D | gcc-6.patch | 16 - si.wants.readable = readcb; 19 + si.wants.readable = static_cast<bool>(readcb);
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | redfish-error.v1_0_2.json | 35 …"description": "A human-readable error message corresponding to the message in a message registry.… 36 …"longDescription": "This property shall contain a human-readable error message corresponding to th…
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | redfish-error.v1_0_2.json | 35 …"description": "A human-readable error message corresponding to the message in a message registry.… 36 …"longDescription": "This property shall contain a human-readable error message corresponding to th…
|
/openbmc/intel-ipmi-oem/docs/ |
H A D | Intel_IPMI_Platform_Events.md | 6 IPMI Platform Events in a human readable form by defining a generic framework 30 human-readable format. IPMI Platform Events is one type of these messages, used 50 Generic OEM-agnostic algorithm is proposed to achieve human-readable output for 104 as-is or formatted in certain way, to be introduced in human-readable `Message`. 116 - `Message` - human-readable message, possibly with predefined placeholders for 151 contains human-readable information for each `EventId`: 182 - Human-readable message lookup (`[2], [8]`) 297 human-readable form
|
/openbmc/libcper/sections/ |
H A D | cper-section-generic.c | 45 //Processor type, with human readable name if possible. in cper_section_generic_to_ir() 56 //Processor ISA, with human readable name if possible. in cper_section_generic_to_ir() 67 //Processor error type, with human readable name if possible. in cper_section_generic_to_ir() 78 //The operation performed, with a human readable name if possible. in cper_section_generic_to_ir()
|
/openbmc/libcper/specification/document/ |
H A D | cper-json-specification.tex | 47 in a human-readable JSON format, intended to be interoperable with standard CPER binary. 122 name & string & The human readable name of this error severity, if known. \\ 146 type & string & A human readable name, if available, of the notification type for the given GUID.\\ 154 name & string & A human readable name, if available, of this flag.\\ 178 sectionType.type & string & The human readable name, if possible, for the type of section body. GUI… 183 severity.name & string & If available, the human readable name for the severity of the described se… 230 errorType.name & string & The human readable name, if available, of the error type.\\ 231 errorType.description & string & A human readable description, if available, of the error type.\\ 260 processorType.name & string & If available, the human readable name of the processor type.\\ 263 processorISA.name & string & If available, the human readable name of the processor ISA.\\ [all …]
|
/openbmc/openbmc/poky/meta/recipes-core/glibc/glibc/ |
H A D | makedbs.sh | 130 echo "has been set to be readable only by root. You may want" 131 echo "to make it readable by the \`shadow' group depending" 153 echo "has been set to be readable only by root. You may want" 154 echo "to make it readable by the \`shadow' group depending"
|
/openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-devtools/python/ |
H A D | python3-json2html_1.3.0.bb | 1 DESCRIPTION="Python wrapper to convert JSON into a human readable HTML Table representation."
|
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
H A D | xcb-util-errors_1.0.1.bb | 3 SUMMARY = "xcb-util-errors gives human readable names to error codes and event codes"
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-hexbytes_1.3.1.bb | 1 SUMMARY = "Python bytes subclass that decodes hex, with a readable console output."
|
/openbmc/qemu/include/qapi/ |
H A D | error.h | 168 * ERRP_GUARD() commonly results in more readable code. 291 * Get @err's human-readable error message. 310 * human-readable error message is made from printf-style @fmt, ... 328 * the human-readable error message. 345 * is appended to the human-readable error message. 389 * Prepend some text to @errp's human-readable error message. 396 * Prepend some text to @errp's human-readable error message. 403 * Append a printf-style human-readable explanation to an existing error.
|
/openbmc/u-boot/drivers/cpu/ |
H A D | mpc83xx_cpu.h | 26 /* Array mapping the e300 core types to their human-readable names */ 103 /* Array mapping the MCP83xx CPUs to their human-readable names */
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | OFL-1.0-no-RFN | 35 …included either as stand-alone text files, human-readable headers or in the appropriate machine-re…
|
H A D | OFL-1.0 | 35 …included either as stand-alone text files, human-readable headers or in the appropriate machine-re…
|
H A D | OFL-1.0-RFN | 35 …included either as stand-alone text files, human-readable headers or in the appropriate machine-re…
|
H A D | OFL-1.1 | 53 included either as stand-alone text files, human-readable headers or 54 in the appropriate machine-readable metadata fields within text or
|
H A D | OFL-1.1-RFN | 29 …included either as stand-alone text files, human-readable headers or in the appropriate machine-re…
|
H A D | OFL-1.1-no-RFN | 29 …included either as stand-alone text files, human-readable headers or in the appropriate machine-re…
|
H A D | QPL-1.0-INRIA-2004 | 51 forms are also able to receive the complete machine-readable 72 complete machine-readable source code to the items without any
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/mrw/ |
H A D | mrw-perl-tools-native_git.bb | 2 DESCRIPTION = "OpenBMC Perl tools for the machine readable workbook"
|
/openbmc/openbmc-test-automation/docs/ |
H A D | openbmc_test_tools.md | 23 ## Converting SELs to readable format: 51 - To generate a readable error log from binary SEL data: 68 The output file `SEL_data.txt` contains the readable error log (SEL) data.
|