| /openbmc/u-boot/doc/device-tree-bindings/gpu/ |
| H A D | nvidia,tegra20-host1x.txt | 12 - clocks: Must contain one entry, for the module clock.
14 - resets: Must contain an entry for each entry in reset-names.
16 - reset-names: Must include the following entries:
28 - clocks: Must contain one entry, for the module clock.
30 - resets: Must contain an entry for each entry in reset-names.
32 - reset-names: Must include the following entries:
41 - clocks: Must contain one entry, for the module clock.
43 - resets: Must contain an entry for each entry in reset-names.
45 - reset-names: Must include the following entries:
54 - clocks: Must contain one entry, for the module clock.
[all …]
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_x86_cpu_model_versions.py | 35 # all aliases must point to a valid CPU model name:
38 # aliases must not point to aliases
42 # aliases must not be static
87 'unversioned Cascadelake-Server CPU model must not be static')
90 'Cascadelake-Server must be an alias of Cascadelake-Server-v1')
92 'Cascadelake-Server-v1 must not be an alias')
95 'unversioned qemu64 CPU model must not be static')
97 'qemu64 must be an alias of qemu64-v1')
99 'qemu64-v1 must not be an alias')
106 "Haswell must be an alias")
[all …]
|
| /openbmc/pldm/tools/fw-update/ |
| H A D | README.md | 27 - Providing the metadata JSON file is a must
28 - The file path of at least one image file must be provided
35 Some fields corresponding to the PLDM firmware update package must be specified
55 Metadata JSON must have a key called "PackageHeaderInformation", which is of
58 - PackageHeaderIdentifier: Supported, must be specified in metadata file
59 - PackageHeaderFormatRevision: Supported, must be specified in metadata file
70 - PackageVersionString: Supported, must be specified in metadata file
74 Metadata JSON must have a key called "FirmwareDeviceIdentificationArea", which
83 - DeviceUpdateOptionFlags: Supported, must be specified in metadata file
89 - ApplicableComponents: Supported, must be specified in metadata file
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/ |
| H A D | Value.interface.yaml | 3 must be instantiated in the correct hierarchy within the sensors
20 Any service implementing Sensor.Value on one or more objects must implement
46 in the airflow namespace, Unit must be "CFM" For objects in the
47 altitude namespace, Unit must be "Meters". For objects in the current
48 namespace, Unit must be "Amperes". For objects in the energy
49 namespace, Unit must be "Joules". For objects in the fan_tach
50 namespace, Unit must be "RPMS". For objects in the humidity namespace,
51 Unit must be "PercentRH" For objects in the power namespace, Unit must
52 be "Watts". For objects in the pressure namespace, Unit must be
53 "Pascals" For objects in the temperature namespace, Unit must be
[all …]
|
| /openbmc/qemu/include/qapi/ |
| H A D | visitor-impl.h | 23 * otherwise. In the comments below, some callbacks are marked "must
50 /* Must be set to visit structs */
57 /* Must be set to visit structs */
60 /* Must be set; implementations may require @list to be non-null,
61 * but must document it. */
65 /* Must be set */
71 /* Must be set */
74 /* Must be set by input and clone visitors to visit alternates */
82 /* Must be set */
86 /* Must be set */
[all …]
|
| /openbmc/phosphor-mboxd/Documentation/ |
| H A D | mbox_protocol.md | 27 2 specific funtionality). All version specific functionality must also be
144 above), the "Response Code" (Register 13) must be the last register written to.
147 prior to completing the response may lead to a data race, and must, therefore,
166 To initiate a request the host must set a command code (see Commands) into
169 command-specific data should be written (see Layout). The host must then
178 responding the BMC must ensure that the sequence number is the same as
179 the one in the request from the host. The BMC must also ensure that
192 defined as being able to be acknowledged by the host must be with a
223 response argument to `MBOX_GET_INFO`. Thus the host must always call
227 When invoking `MBOX_GET_INFO` the host must provide the BMC its highest
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 092.out | 5 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
6 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
7 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
8 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
12 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
13 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
14 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
15 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
|
| H A D | 039 | 61 # The dirty bit must not be set
75 # The dirty bit must be set
80 echo "== Read-only access must still work =="
84 # The dirty bit must be set
88 echo "== Repairing the image file must succeed =="
92 # The dirty bit must not be set
110 # The dirty bit must be set
115 # The dirty bit must not be set
128 # The dirty bit must not be set since lazy_refcounts=off
143 # The dirty bit must not be set
[all …]
|
| /openbmc/google-misc/subprojects/ncsid/src/platforms/nemora/portable/ |
| H A D | ncsi_server.h | 41 * response_buf: buffer, where to put the response. Must be big enough to fit
43 * response_code: Response Code. Must be zero for ACK.
44 * reason_code: Reason Code. Must be zero for ACK.
57 * response_buf: buffer, where to put the response. Must be big enough to fit
71 * response_buf: buffer, where to put the response. Must be big enough to fit
84 * received command, which in this case must be NCSI_GET_VERSION_ID command.
88 * response_buf: buffer, where to put the response. Must be big enough to fit
100 * received OEM command, which in this case must be
105 * response_buf: buffer, where to put the response. Must be big enough to fit
121 * response_buf: buffer, where to put the response. Must be big enough to fit
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Sensor/Aggregation/History/ |
| H A D | Average.interface.yaml | 17 in the temperature namespace, Unit must be "DegreesC". For objects in
18 the fan_tach namespace, Unit must be "RPMS". For objects in the
19 voltage namespace, Unit must be "Volts". For objects in the altitude
20 namespace, Unit must be "Meters". For objects in the current
21 namespace, Unit must be "Amperes". For objects in the power namespace,
22 Unit must be "Watts". For objects in the energy namespace, Unit must
|
| H A D | Maximum.interface.yaml | 17 in the temperature namespace, Unit must be "DegreesC". For objects in
18 the fan_tach namespace, Unit must be "RPMS". For objects in the
19 voltage namespace, Unit must be "Volts". For objects in the altitude
20 namespace, Unit must be "Meters". For objects in the current
21 namespace, Unit must be "Amperes". For objects in the power namespace,
22 Unit must be "Watts". For objects in the energy namespace, Unit must
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Vim | 3 …ept that they must include this license text. You can also distribute unmodified parts of Vim, lik…
7 1) This license text must be included unmodified.
9 2) The modified Vim must be distributed in one of the following five ways:
11 …must clearly describe in the distribution how to contact you. When the maintainer asks you (in any…
15 …e what license to use for new code you add. The changes and their license must not restrict others…
19 …fied Vim to asks you (in any way) for the changes within this period, you must make them available…
20 …describe in the distribution how to contact you. This contact information must remain valid for at…
24 …3) A message must be added, at least in the output of the ":version" command and in the intro scre…
26 …4) The contact information as required under 2)a) and 2)d) must not be removed or changed, except …
|
| H A D | Eurosym | 8 …1. The origin of this software must not be misrepresented; you must not claim that you wrote the o…
10 …2. Altered source versions must be plainly marked as such, and must not be misrepresented as being…
12 …3. You must not use any of the names of the authors or copyright holders of the original software …
14 …4. If you change this software and redistribute parts or all of it in any form, you must make the …
|
| H A D | Spencer-94 | 8 … of this software must not be misrepresented, either by explicit claim or by omission. Since few …
10 …ions must be plainly marked as such, and must not be misrepresented as being the original software…
|
| H A D | QPL-1.0-INRIA-2004 | 34 a. Modifications must not alter or remove any copyright notices
48 a. You must include this license document in the distribution.
50 b. You must ensure that all recipients of the machine-executable
57 c. You must ensure that all modifications included in the
70 a. You must ensure that all recipients of machine-executable
75 b. You must explicitly license all recipients of your items to
78 recipients must be able to do so without any charges whatsoever,
79 and they must be able to re-distribute to anyone they choose.
83 then you must supply one.
|
| H A D | ZPL-1.1 | 10 Redistributions in source code must retain the above copyright notice, this list of conditions, and…
11 Redistributions in binary form must reproduce the above copyright notice, this list of conditions, …
12 …nd documentation mentioning features derived from or use of this software must display the followi…
17 Names associated with Zope or Zope Corporation must not be used to endorse or promote products deri…
18 Modified redistributions of any form whatsoever must retain the following acknowledgment:
23 …t must be packaged separately as patches to official Zope releases. Distributions that do not clea…
|
| H A D | QPL-1.0 | 18 a. Modifications must not alter or remove any copyright notices in the Software.
23 a. You must include this license document in the distribution.
24 b. You must ensure that all recipients of the machine-executable forms are also able to receive the…
26 c. You must ensure that all modifications included in the machine-executable forms are available un…
32 a. You must ensure that all recipients of machine-executable forms of these items are also able to …
33 …must explicitly license all recipients of your items to use and re-distribute original and modifie…
35 …, and the initial developer of the Software requests a copy of the items, then you must supply one.
|
| /openbmc/qemu/docs/interop/ |
| H A D | qcow2.rst | 34 Length of the backing file name in bytes. Must not be
41 Must not be less than 9 (i.e. 512 byte clusters).
48 must be at least 14 (i.e. 16384 byte clusters).
74 starts. Must be aligned to a cluster boundary.
78 starts. Must be aligned to a cluster boundary.
88 starts. Must be aligned to a cluster boundary.
96 Bitmask of incompatible features. An implementation must
105 structure may be corrupt and the image must not
114 Standard Cluster Descriptor must match the
123 clusters. The compression_type field must be
[all …]
|
| H A D | parallels.rst | 45 Must contain "WithoutFreeSpace" or "WithouFreSpacExt".
48 Must be 2.
66 Only the lowest 4 bytes are used. The highest 4 bytes must be
94 data_off must be non-zero and aligned to cluster size.
108 ext_off must meet the same requirements as cluster offsets
125 Cluster offsets specified by BAT entries must meet the following requirements:
127 - the value must not be lower than data offset (provided by ``header.data_off``
129 - the value must be lower than the desired file size
130 - the value must be unique among all BAT entries
131 - the result of ``(cluster offset - data offset)`` must be aligned to
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/dynamic-layers/meta-arm-systemready/recipes-test/arm-systemready-acs/files/fvp-base/ |
| H A D | 0001-check-sr-results-Change-the-expected-SR-result-confi.patch | 14 a. must-have-esp: EFI partition/variable persistence not supported due to
17 c. must-contain "efi: ESRT=0x" and "'esrt: Reserving ESRT space from 0x'":
23 a. must-contain "Failure: |0|": Capsule and EFI partition failures make
27 b. must-contain "'EFI_SYSTEM_RESOURCE_TABLE:'" and
30 c. must-contain "FwClass": Capsule updates are not supported.
35 This patch also adds must-contain for the specific totals of the test
46 a. must-contain "EFISystemPartition": EFI partition/variable persistence
48 b. must-contain "FirmwareManagement": Capsule updates are not supported.
75 - must-have-esp:
76 must-contain:
[all …]
|
| /openbmc/qemu/include/hw/ |
| H A D | resettable.h | 50 * reset. This whole API must only be used when holding the iothread mutex.
52 * All objects which can be reset must implement this interface;
54 * Every Resettable object must maintain some state tracking the
80 * should reset local state of the object, but it must not do anything that
92 * @get_state: Mandatory method which must return a pointer to a
99 * additional opaque and ResetType arguments which must be passed unmodified to
160 * Trigger a reset on an object @obj of type @type. @obj must implement
170 * Put an object @obj into reset. @obj must implement Resettable interface.
172 * @resettable_release_reset() must eventually be called after this call.
173 * There must be one call to @resettable_release_reset() per call of
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/bldcontrol/ |
| H A D | bbcontroller.py | 63 The return object MUST always be a BuildEnvironmentController.
76 """ BuildEnvironmentController (BEC) is the abstract class that defines the operations that MUST
77 … or SHOULD be supported by a Build Environment. It is used to establish the framework, and must
84 You must derive this class to teach Toaster how to operate in your own infrastructure.
103 bitbake must be a single BRBitbake instance
104 The layer paths must be in a list of BRLayer object
108 raise NotImplementedError("FIXME: Must override setLayers")
112 … up to the implementing BEC. The return MUST be a REST URL where a GET will actually return
115 raise NotImplementedError("Must return the REST URL of the artifact")
118 raise NotImplementedError("Must override BE release")
|
| /openbmc/openbmc/poky/meta/lib/oeqa/runtime/decorator/ |
| H A D | package.py | 14 The argument must be a string, set, or list of packages that must be
17 The way to tell a package must not be in an image is using an
27 If test depends on pkg1 but pkg2 must not be present use:
72 The argument must be a string, set, or list of packages that must be
75 The way to tell a package must not be in an image is using an
85 If test depends on pkg1 but pkg2 must not be present use:
|
| /openbmc/u-boot/lib/lzma/ |
| H A D | LzmaDec.h | 73 1) Stream without end mark. You must know exact uncompressed size to decompress such stream. */
78 LZMA_FINISH_END /* block must be finished at the end */
83 You must use LZMA_FINISH_END, when you know that current output buffer
84 covers last bytes of block. In other cases you must use LZMA_FINISH_ANY.
94 You must use correct finish mode in that case. */
101 LZMA_STATUS_NEEDS_MORE_INPUT, /* you must provide more input bytes */
122 For Buffer Interface you must always use variant 1.
140 You must work with CLzmaDec variables directly in this interface.
160 You must manually update CLzmaDec::dicPos, if it reaches CLzmaDec::dicBufSize !!!
165 LZMA_FINISH_END - Stream must be finished after dicLimit.
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | secure-coding-practices.rst | 4 This document covers topics that both developers and security researchers must
41 trusted and may be invalid. Inputs must be checked before using them in a way
46 accesses and data read from guest memory must be validated. A typical example
68 place when ``unit`` is dereferenced. The code must check that ``val`` is 0 or
74 moments. Device emulation code must not assume that the guest follows the
79 A related issue is that device emulation code must be prepared for unexpected
82 certain device registers. Device emulation code must handle the case where the
84 request completes. Unexpected accesses must not cause memory corruption or
94 Live migration code must validate inputs when loading device state so an
102 running. Device emulation code must copy in descriptors and other guest RAM
[all …]
|