| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | ipmi-network-format.md | 13 Specify 'chassis bootdev', field 96, data1 0x00 0x08 0x61 0x80
24 Specify 'chassis bootdev', field 96, data1 0x00 0x08 0x61 0x80
28 Specify the version (only 1 at the moment) 0x00 0x01
30 Specify the size of the MAC address and IP address. This is used to
37 Specify 'ignore' or 'static/dynamic' flags. The second byte specifies to use
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | UpdateServiceCapabilities.v1_0_0.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
40 "description": "This property shall specify a valid odata or Redfish property.",
61 "description": "This property shall specify a valid odata or Redfish property.",
92 …"description": "The allowable URIs that a client can specify in the `Targets` parameter for update…
96 … property shall contain an array of the allowable URIs that a client can specify in the `Targets` …
101 …"description": "The allowable URIs that a client can specify in the `Targets` parameter for update…
105 … property shall contain an array of the allowable URIs that a client can specify in the `Targets` …
|
| H A D | MetricReportDefinition.v1_4_7.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
54 …"longDescription": "This type shall specify the function to apply to the list of metric properties…
70 …alue in the metric report shall specify the end of the time interval and the `CollectionDuration` …
71 …lue instances, the `Timestamp` property value in the metric report shall specify the point in time…
72 …ue in the metric report shall specify the end of the time interval. The `CollectionDuration` prop…
74 … "longDescription": "This type shall specify the time scope of the corresponding metric values.",
83 "description": "This property shall specify a valid odata or Redfish property.",
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
123 "description": "This property shall specify a valid odata or Redfish property.",
138 …"longDescription": "This property shall specify the duration over which the function is computed.",
[all …]
|
| H A D | OperatingConfig.v1_0_4.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
37 "longDescription": "This type shall specify the clock speed for a set of cores.",
40 "description": "This property shall specify a valid odata or Redfish property.",
95 "description": "This property shall specify a valid odata or Redfish property.",
116 "description": "This property shall specify a valid odata or Redfish property.",
169 …"longDescription": "This property shall contain an array of objects that specify the clock speed f…
250 …"longDescription": "The property shall contain an array of objects that specify the turbo profile …
265 … "longDescription": "This type shall specify the turbo profile for a set of active cores.",
268 "description": "This property shall specify a valid odata or Redfish property.",
|
| H A D | MetricDefinition.v1_3_5.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
79 "description": "This property shall specify a valid odata or Redfish property.",
155 "description": "This property shall specify a valid odata or Redfish property.",
204 … "longDescription": "This property shall specify whether the metric can be used in a calculation.",
237 …"longDescription": "This property shall specify the time interval over the metric calculation is p…
273 …"longDescription": "The values of the property shall specify the possible values of the discrete m…
291 … "longDescription": "This property shall specify the implementation of the metric.",
332 "longDescription": "This property shall specify the data-type of the metric.",
358 "longDescription": "This property shall specify the type of metric.",
404 …"longDescription": "This property shall specify the number of significant digits in the metric rea…
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | qemu-option-trace.rst.inc | 2 Specify tracing options.
9 or ``ftrace`` tracing backend. To specify multiple events or patterns,
10 specify the :option:`-trace` option multiple times.
|
| /openbmc/openbmc/poky/meta/conf/machine/include/mips/ |
| H A D | README | 45 MIPSPKGSFX_ABI - This is used to specify an alternative ABI when the previous
49 MIPSPKGSFX_R6 - This is used to specify the presence of release 6.
52 MIPSPKGSFX_64R6 - This is used to specify "isa" in the tuple.
55 MIPSPKGSFX_32R6 - This is used to specify "isa32" in the tuple.
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-bsp/kexecboot/ |
| H A D | kexecboot-cfg_0.2.bb | 20 # Specify full kernel path on target.
23 # Specify which device tree blob to use
32 # Specify optional initrd/initramfs.
35 # Specify full path for a custom icon for the menu-item.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | MetricReportDefinition.v1_4_7.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
54 …"longDescription": "This type shall specify the function to apply to the list of metric properties…
70 …alue in the metric report shall specify the end of the time interval and the `CollectionDuration` …
71 …lue instances, the `Timestamp` property value in the metric report shall specify the point in time…
72 …ue in the metric report shall specify the end of the time interval. The `CollectionDuration` prop…
74 … "longDescription": "This type shall specify the time scope of the corresponding metric values.",
83 "description": "This property shall specify a valid odata or Redfish property.",
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
123 "description": "This property shall specify a valid odata or Redfish property.",
138 …"longDescription": "This property shall specify the duration over which the function is computed.",
[all …]
|
| H A D | OperatingConfig.v1_0_4.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
37 "longDescription": "This type shall specify the clock speed for a set of cores.",
40 "description": "This property shall specify a valid odata or Redfish property.",
95 "description": "This property shall specify a valid odata or Redfish property.",
116 "description": "This property shall specify a valid odata or Redfish property.",
169 …"longDescription": "This property shall contain an array of objects that specify the clock speed f…
250 …"longDescription": "The property shall contain an array of objects that specify the turbo profile …
265 … "longDescription": "This type shall specify the turbo profile for a set of active cores.",
268 "description": "This property shall specify a valid odata or Redfish property.",
|
| H A D | MetricDefinition.v1_3_5.json | 13 "description": "This property shall specify a valid odata or Redfish property.",
79 "description": "This property shall specify a valid odata or Redfish property.",
155 "description": "This property shall specify a valid odata or Redfish property.",
204 … "longDescription": "This property shall specify whether the metric can be used in a calculation.",
237 …"longDescription": "This property shall specify the time interval over the metric calculation is p…
273 …"longDescription": "The values of the property shall specify the possible values of the discrete m…
291 … "longDescription": "This property shall specify the implementation of the metric.",
332 "longDescription": "This property shall specify the data-type of the metric.",
358 "longDescription": "This property shall specify the type of metric.",
404 …"longDescription": "This property shall specify the number of significant digits in the metric rea…
[all …]
|
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
37 "description": "The term shall be applied to a property in order to specify when the property was deprecated. The value of the string should contain the resource version where the property was deprecated."
41 "description": "The term shall be applied to a property in order to specify when the property was added. The value of the string should contain the resource version where the property was added."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
57 "description": "The term shall be applied to a value in order to specify when the value was deprecated. The value of the string should contain the resource version where the value was deprecated."
61 "description": "The term shall be applied to a value in order to specify when the value was added. The value of the string should contain the resource version where the value was added."
139 "description": "The term is applied to Redfish schema or registry in order to specify licensing information."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sblim-sfcb/sblim-sfcb/ |
| H A D | sblim-sfcb-1.3.9-sfcbrepos-schema-location.patch | 29 echo -e "\t-s specify staging directory [@localstatedir@/lib/sfcb/stage]"
30 echo -e "\t-r specify repository directory [@localstatedir@/lib/sfcb/registration]"
31 - echo -e "\t-c specify directory containing CIM Schema MOFs [@datadir@/sfcb/CIM]"
32 + echo -e "\t-c specify directory containing CIM Schema MOFs [@datadir@/mof/cim-current]"
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 8 have to explicitly specify the disk where you want to boot from (or "IPL" from,
24 information in order to be bootable), it is recommended to specify a ``scsi-cd``
41 not specify a boot device with the ``bootindex`` property, there is still a
45 It is really recommended to always specify the boot device with the
50 specify the ``bootindex`` with these commands. Note that the convenience
55 recommended to specify a CD-ROM device via ``-device scsi-cd`` (as mentioned
112 important for booting via the network. If you don't specify the ``bootindex``
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | BUSL-1.1 | 58 1. To specify as the Change License the GPL Version 2.0 or any later version,
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
69 3. To specify a Change Date.
|
| /openbmc/qemu/include/exec/ |
| H A D | memattrs.h | 61 * Bus masters which don't specify any attributes will get this
64 * "didn't specify" if necessary. "debug" can be set alongside
75 /* Bus masters which don't specify any attributes will get this,
78 * from "didn't specify" if necessary).
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | sensor_monitoring.md | 18 - Use the "rule_id" property to specify a standard rule to run.
19 - Use the "actions" property to specify an array of actions that are unique to
32 - You must specify either "rule_id" or "actions".
|
| H A D | phase_fault_detection.md | 38 - Use the "rule_id" property to specify a standard rule to run.
39 - Use the "actions" property to specify an array of actions that are unique to
42 The default device for the actions is the voltage regulator. You can specify a
57 - You must specify either "rule_id" or "actions".
|
| H A D | compare_vpd.md | 49 …he VPD. Specify the relative D-Bus inventory path of the FRU. Full inventory paths begin with the …
50 | keyword | yes | string | VPD keyword. Specify one of the following:…
56 - You must specify either "value" or "byte_values".
|
| H A D | configuration.md | 18 - Use the "rule_id" property to specify a standard rule to run.
19 - Use the "actions" property to specify an array of actions that are unique to
33 - You must specify either "rule_id" or "actions".
|
| H A D | presence_detection.md | 24 - Use the "rule_id" property to specify a standard rule to run.
25 - Use the "actions" property to specify an array of actions that are unique to
48 - You must specify either "rule_id" or "actions".
|
| /openbmc/openbmc/poky/meta/recipes-devtools/clang/clang/ |
| H A D | 0001-libcxxabi-Find-libunwind-headers-when-LIBCXXABI_LIBU.patch | 25 "Specify path to libunwind source." FORCE)
54 + "Specify path to libunwind includes." FORCE)
56 + "Specify path to libunwind source." FORCE)
|
| /openbmc/phosphor-mrw-tools/ |
| H A D | patchxml.py | 7 and uses XML attributes to specify if the elements in the file should replace
8 existing elements or add new ones. An XPath attribute is used to specify
10 patch file to specify the base name of the XML file the patches should be
14 used to specify the patch placement the target XML cannot use those at a
57 Use a type attribute of 'add-child' and specify the target parent with
78 as described above, and also use the key attribute to specify which
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | kickstart.rst | 69 - ``--size``: The minimum partition size. Specify as an integer value
74 - ``--fixed-size``: The exact partition size. Specify as an integer
77 given is "M". Cannot be specify together with ``--size``. An error
106 option to specify the size of the empty partition.
147 will fail. Specify as an integer value optionally followed by one of
164 option. The default value is 10M. Specify as an integer value
184 identifier is used in the bootloader configuration to specify the
|
| /openbmc/entity-manager/ |
| H A D | Doxyfile | 49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
96 # The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
169 # Note that you can specify absolute paths here, but also relative paths, which
179 # specify the list of include paths that are normally passed to the compiler
249 # This tag can be used to specify a number of aliases that act as commands in
717 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
727 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
731 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
[all …]
|