| /openbmc/phosphor-objmgr/src/ |
| H A D | processing.hpp | 28 /** @brief Get well known name of input unique name
30 * If user passes in well known name then that will be returned.
34 * @param[out] wellKnown - The well known name if found
36 * @return True if well known name is found, false otherwise
56 * @param[in,out] nameOwners - Map of unique name to well known name
57 * @param[in] wellKnown - Well known name that has new owner
77 * @param[in] wellKnown - Well known name that has new owner
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | project.html | 63 <div class="well well-transparent" id="machine-section">
80 <div class="well well-transparent" id="distro-section">
97 <div class="well well-transparent">
111 <div class="well well-transparent">
131 <div class="well well-transparent" id="layer-container">
|
| H A D | project_specific.html | 63 <div class="well well-transparent" id="machine-section">
80 <div class="well well-transparent" id="distro-section">
96 <div class="well well-transparent">
109 <div class="well well-transparent">
129 <div class="well well-transparent" id="layer-container">
|
| H A D | builddashboard.html | 83 …<div class="well well-transparent dashboard-section" data-artifacts-for-target="{{target.target.pk…
185 <div class="well well-transparent dashboard-section">
210 <div class="well well-transparent">
220 <div class="well well-transparent">
270 <div class="well well-transparent">
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 12 that while some layers were popular and worked well, others developed a
14 interoperate well with others and tended to assume they controlled all
43 to operate well together. "anti-patterns" were also found, preventing layers
44 from working well together.
47 compatibility tests, it is considered "well behaved" and should operate
48 and cooperate well with other compatible layers.
|
| /openbmc/qemu/tests/keys/ |
| H A D | README | 1 This folder contains a well-known ssh key pair used in QEMU tests.
5 run. Because the private key is well-known, care must be taken to use the key
|
| /openbmc/qemu/tests/multiboot/ |
| H A D | aout_kludge.S | 46 /* Well-behaved kernel file with explicit bss_end */
53 /* Well-behaved kernel file with default bss_end */
60 /* Well-behaved kernel file with default load_end */
67 /* Well-behaved kernel file with load_end < data_end and bss > data_end */
|
| /openbmc/webui-vue/docs/guide/components/ |
| H A D | readme.md | 4 Boostrap-Vue components, as well as custom components. Using these components
9 other sections of the application can use as well.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-geomet_1.1.0.bb | 1 SUMMARY = "Convert GeoJSON to WKT/WKB (Well-Known Text/Binary), and vice versa."
2 DESCRIPTION = "Convert GeoJSON to WKT/WKB (Well-Known Text/Binary), and vice versa."
|
| /openbmc/u-boot/board/toradex/apalis_t30/ |
| H A D | Kconfig | 31 Bring up the Apalis type specific 4 lane PCIe port as well as the
34 disabled in the device tree which needs changing as well for this to
|
| /openbmc/openbmc/poky/meta/recipes-support/libdisplay-info/ |
| H A D | libdisplay-info_0.2.0.bb | 3 easy-to-use, and opinionated functions, as well as low-level functions for \
5 performance and resource usage, while being well-tested and fuzzed."
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/openssl-tpm-engine/files/ |
| H A D | 0001-create-tpm-key-support-well-known-key-option.patch | 7 support well-known password in openssl-tpm-engine.
9 Add "-z" option to select well known password in create_tpm_key tool.
21 +#define TPM_WELL_KNOWN_KEY_LEN 20 /*well know key length is 20 bytes zero*/
30 + "\t\t-z|--zerokey use well known 20 bytes zero as SRK password.\n"
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 28 of the feature, as well as the design doc should explicitly state one of the
42 well as all processor classes.
62 feature is disabled. Company or feature specific functions, as well as the
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | rm_work_and_downloads.bbclass | 18 # Where it works well is in well-connected build environments with limited
|
| /openbmc/docs/designs/ |
| H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 27 decode IPMI-FRU storage formatted blobs, as well as the Tyan data format.
87 '/serial-number,' which both have well-known paths in the device tree
111 potentially for other hardware as well).
166 1. Has no well-known handles for common properties like /model or /serial-number
168 'well-known' properties
172 'model' instead of the well known device-tree /model handle would add
174 3. Since /model is well described in device-tree documentation, there is
183 1. Is a well-established device-tree node
316 well-defined location? Inventory.Decorator.[Asset] = Model
|
| /openbmc/u-boot/drivers/firmware/ |
| H A D | ti_sci.c | 126 * return corresponding error, else if all goes well,
286 * Return: 0 if all went well, else returns appropriate error value.
336 * Return: 0 if all went well, else returns appropriate error value.
353 * Return: 0 if all went well, else returns appropriate error value.
371 * Return: 0 if all went well, else returns appropriate error value.
389 * Return: 0 if all went well, else returns appropriate error value.
406 * Return: 0 if all went well, else returns appropriate error value.
787 * Return: 0 if all went well, else returns appropriate error value.
842 * Return: 0 if all went well, else returns appropriate error value.
905 * Return: 0 if all went well, else returns appropriate error value.
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Imlib2 | 5 …a) as well as making an offer to supply the source on request. This Copyright notice serves as an …
|
| H A D | FTL | 35 …using' is a generic term including compiling the project's source code as well as linking it to fo…
69 …Discusses general use and applications of FreeType, as well as future and wanted additions to the …
73 Discusses bugs, as well as engine internals, design issues, specific licenses, porting, etc.
|
| /openbmc/u-boot/drivers/tpm/ |
| H A D | Kconfig | 101 The functionality is available via the 'tpm' command as well.
109 The functionality is available via the 'tpm' command as well.
116 The functionality is available via the 'tpm' command as well.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 45 well, is being used in more and more drivers, the same problem of altering the
46 device tree starts cropping up in U-Boot itself as well.
111 detected components are added to the device tree, as well as a "subtractive"
113 as well as a combination of both approaches should work.
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 13 important information learned from other users. You're well prepared. But
53 well. Each layer has a ``README`` document that you can look at for this type of
101 well as the package feed and possibly the update solution. You would create
113 #. **Congratulations! You're well on your way.**
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0040-fix-runtime-capsule-update-flags-checks.patch | 33 + * header as well.*/
43 + * header as well.*/
|
| /openbmc/openbmc/poky/meta/recipes-extended/shadow/files/pam.d/ |
| H A D | su | 28 # as well as /etc/porttime)
53 # NIS (man nsswitch) as well as normal /etc/passwd and
|
| /openbmc/ipmitool/ |
| H A D | README | 38 well as those debugging or developing their own BMC implementations.
57 enough to allow a single well-designed driver to support them all.
108 security with encryption as well as support for Serial over LAN.
110 There are different types of LAN interfaces as well. Some systems have
126 enabling the LAN interface as well.
198 Its been working well with IPMITOOL on the LAN interface with:
243 interfaces and which is default as well as a list of top level commands in
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 25 well as information on how to identify the maintainer for each area of
35 Implementations of Bugzilla work well for group development because they
60 There are multiple mailing lists maintained by the Yocto Project as well
152 how to work with Linux Yocto kernels as well as provides a bit of
|