/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
H A D | RedundancyPriority.interface.yaml | 9 represented as a value between 0 (High) and 127 (Low). Any value 16 A dual-sided redundancy model could be represented by two
|
/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | README.md | 25 The I2C bus(es) that the power supply is on will be represented by the `I2CBus` 31 The I2C address(es) that the power supply is at will be represented by the
|
/openbmc/u-boot/doc/device-tree-bindings/reset/ |
H A D | reset.txt | 5 standalone chips are most likely better represented as GPIOs, although there 14 A reset signal is represented by the phandle of the provider, plus a reset 24 may be reset. Instead, reset signals should be represented in the DT node
|
/openbmc/qemu/include/io/ |
H A D | channel-file.h | 54 * Create a new IO channel object for a file represented 76 * Create a new IO channel object for a file represented by the @fd 96 * Create a new IO channel object for a file represented
|
/openbmc/openbmc/poky/meta/recipes-extended/iputils/iputils/ |
H A D | CVE-2025-47268.patch | 25 … error: signed integer overflow: -2513732689199106 * 1000000 cannot be represented in type 'long i… 26 …nteger overflow: -4975495174606980224 + -6510615555425289427 cannot be represented in type 'long i… 27 … integer overflow: 6960633343677281965 * 6960633343677281965 cannot be represented in type 'long i… 32 …time error: signed integer overflow: 6960633343677281965 * 2 cannot be represented in type 'long i… 37 … integer overflow: 1740158335919320832 * 1740158335919320832 cannot be represented in type 'long i…
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
H A D | Drive.interface.yaml | 26 Time when the Drive last rebooted represented in EpochTime. The time 28 be represented as maxint.
|
/openbmc/qemu/docs/ |
H A D | xbzrle.txt | 27 The page data delta is represented by zero and non zero runs. 28 A zero run is represented by its length (in bytes). 29 A non zero run is represented by its length (in bytes) and the new data.
|
/openbmc/qemu/docs/system/s390x/ |
H A D | protvirt.rst | 7 encrypted and can only be decrypted by the firmware, represented by an 29 ``Unpack facility`` (stfle bit 161 represented by the feature
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-bitstruct_8.21.0.bb | 1 …ule performs conversions between Python values and C bit field structs represented as Python byte …
|
/openbmc/qemu/ui/ |
H A D | vnc-enc-tight.h | 69 * Data size is compactly represented in one, two or three bytes, according 79 * should be represented as two bytes: binary 10010000 01001110, or 136 * Data size is compactly represented in one, two or three bytes, just like 140 * 8-bit wide, then one pixel in Tight encoding is always represented by
|
/openbmc/google-misc/subprojects/nemora-postd/src/ |
H A D | default_addresses.h | 23 // NOTE: All the IPv4 addresses used in this file will be represented in the 30 // 32-bit number is represented in memory as:
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/python3-hypothesis/ |
H A D | test_rle.py | 20 consecutive equal elements is represented as a single element plus a count. So 23 [1, 1, 1, 1, 2, 1] is represented as [[1, 4], [2, 1], [1, 1]]
|
/openbmc/openbmc/poky/meta/recipes-devtools/distcc/files/ |
H A D | default | 15 # Hosts are represented by a single IP Adress
|
/openbmc/phosphor-fan-presence/docs/monitor/ |
H A D | deviation.md | 18 Deviation is represented as a percentage, so only 0 to 100 are valid values.
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | NASA-1.3 | 4 …TES GOVERNMENT AS REPRESENTED BY THE GOVERNMENT AGENCY LISTED BELOW ("GOVERNMENT AGENCY"). THE UNI… 40 …keted language.] Copyright � {YEAR} United States Government as represented by ___ ____. Al… 42 …keted language.] Copyright � {YEAR} United States Government as represented by ____ ____. N…
|
H A D | CFITSIO | 1 …ved under the copyright laws of the United States), U.S. Government as represented by the Administ…
|
H A D | Adobe-Glyph | 8 …to permit others to do the same, provided that the derived work is not represented as being a copy…
|
/openbmc/docs/architecture/ |
H A D | redfish-logging-in-bmcweb.md | 6 Redfish Message Objects can be represented in different ways. In bmcweb, we have 42 A Redfish MessageId is represented in this format:
|
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
H A D | README.md | 17 belong to that record are represented as properties under that interface. The
|
/openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
H A D | pinctrl-bindings.txt | 5 controllers. Each pin controller must be represented as a node in device tree, 9 designated client devices. Again, each client device must be represented as a 161 Many data items that are represented in a pin configuration node are common
|
/openbmc/u-boot/lib/libavb/ |
H A D | avb_crypto.h | 113 * e) where |n| is the modulus (which can be represented in 119 * represented in |key_num_bits|.
|
/openbmc/boost-dbus/include/dbus/ |
H A D | match.hpp | 21 * Each rule will be represented by an instance of match. To remove that rule,
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/ippool/ippool/ |
H A D | 0001-Use-unsigned-int-type-for-1-bit-integer-bitfield.patch | 6 In C++, signed integers are represented in two's complement. This also applies to signed bitfields.
|
/openbmc/u-boot/doc/device-tree-bindings/leds/ |
H A D | leds-gpio.txt | 6 Each LED is represented as a sub-node of the gpio-leds device. Each
|
/openbmc/u-boot/drivers/pinctrl/nxp/ |
H A D | pinctrl-imx.h | 37 * Each pin represented in fsl,pins consists of 5 u32 PIN_FUNC_ID and
|