Home
last modified time | relevance | path

Searched refs:Metadata (Results 1 – 25 of 62) sorted by relevance

123

/openbmc/openbmc/poky/meta/classes-recipe/
H A Dcython.bbclass5 # Remove the Cython Metadata headers that we don't need after the build, and
7 …rint0 | xargs --no-run-if-empty --null sed -i -e "/BEGIN: Cython Metadata/,/END: Cython Metadata/d"
H A Dtoolchain-scripts-base.bbclass14 echo 'Metadata Revision: ${METADATA_REVISION}' >> $versionfile
/openbmc/phosphor-fan-presence/control/json/utils/
H A Dpcie_card_metadata.hpp94 struct Metadata struct in phosphor::fan::control::json::PCIeCardMetadata
103 bool operator==(const Metadata& other) in operator ==() argument
142 std::vector<Metadata> _cards;
H A Dpcie_card_metadata.cpp108 Metadata data; in load()
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dadvanced.rst4 Working with Advanced Metadata (``yocto-kernel-cache``)
12 :term:`Metadata` that you can use to define
14 the Metadata and the tools that manage it is to help you manage the
18 Kernel Metadata exists in many places. One area in the
31 Using Kernel Metadata in a Recipe
35 Metadata, which is located in the ``yocto-kernel-cache`` Git repository.
36 This Metadata defines Board Support Packages (BSPs) that correspond to
44 A Linux kernel recipe that contains kernel Metadata (e.g. inherits
86 within the kernel Metadata with which to build out the sources and
119 within the kernel Metadata itself. The examples here are taken from the
[all …]
H A Dintro.rst14 Linux kernel :term:`Metadata`, describes
16 use the kernel Metadata needed to work with the kernel inside the Yocto
18 and maintains Yocto Linux kernel Git repositories and Metadata.
34 upstream Yocto Linux kernel development and kernel Metadata development.
177 used during kernel development, advanced Metadata usage, and Yocto Linux
H A Dmaint-appx.rst19 kernel repository (or tree) and accompanying Metadata in the
31 ``yocto-kernel-cache``, which contains stores of kernel Metadata::
42 Once you have cloned the kernel Git repository and the cache of Metadata
92 provide the Metadata and create the tree that includes the new feature,
184 - A BSP build branch with Metadata exists in the ``yocto-kernel-cache``
/openbmc/telemetry/src/types/
H A Dsensor_types.hpp15 utils::tstring::Metadata>;
H A Dreport_types.cpp19 sensorParameters.at_label<ts::Metadata>()); in toReadingParameters()
/openbmc/pldm/tools/fw-update/
H A DREADME.md33 ## Metadata JSON file
55 Metadata JSON must have a key called "PackageHeaderInformation", which is of
74 Metadata JSON must have a key called "FirmwareDeviceIdentificationArea", which
94 - RecordDescriptors: Metadata JSON must have a key called "Descriptors", which
127 Metadata JSON must have a key called "ComponentImageInformationArea", which is
/openbmc/telemetry/src/utils/
H A Dtstring.hpp27 struct Metadata struct
H A Dconversion_trigger.cpp77 val.at_label<ts::Metadata>()); in fromLabeledSensorsInfo()
/openbmc/phosphor-logging/tools/phosphor-logging/templates/
H A Delog-process-metadata.cpp.mako16 extern const std::map<metadata::Metadata,
/openbmc/openbmc/meta-arm/meta-arm-bsp/wic/
H A Dcorstone1000-flash-firmware.wks.in12 part --source empty --size 4k --align 4 --offset 20k --part-name="FWU-Metadata" --uuid 3FDFFEE1-322…
13 part --source empty --size 4k --align 4 --offset 24k --part-name="Bkup-FWU-Metadata" --uuid B306831…
/openbmc/openbmc/poky/documentation/migration-guides/
H A Dmigration-2.0.rst91 unlikely to require any changes to Metadata. However, these minor
209 ``linux-yocto`` Kernel Metadata Repository Now Split from Source
216 to manipulate the Metadata as compared to the source.
218 Metadata processing has now been removed from the
220 Metadata repository ``yocto-kernel-cache``, which has always been used
/openbmc/phosphor-logging/
H A Delog_meta.hpp24 using Metadata = std::string; typedef
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dcustom-distribution.rst7 distribution :term:`Metadata`, you are using the Poky distribution.
20 configuration file, and then adding any needed code and Metadata to the
24 so that you can keep your Metadata and code for the distribution
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/
H A D0007-Plaform-Corstone1000-Switch-to-metadata-v2.patch33 + * Metadata version 2 data structures defined by PSA_FW update specification
68 /* Metadata CRC value */
/openbmc/openbmc/poky/documentation/ref-manual/
H A Dterms.rst210 recipes and related Metadata. Images are the binary output that run on
282 :term:`Metadata`
283 A key element of the Yocto Project is the Metadata that
286 parses when building an image. In general, Metadata includes recipes,
289 things get built and the effects of the build. Metadata also includes
296 In the context of the kernel ("kernel Metadata"), the term refers to
317 You can see the Metadata in the ``meta`` directory of the Yocto
439 The Source Directory contains BitBake, Documentation, Metadata and
/openbmc/openbmc/poky/meta/lib/patchtest/tests/
H A Dtest_metadata.py17 class TestMetadata(base.Metadata):
H A Dbase.py135 class Metadata(Base): class
/openbmc/qemu/docs/interop/
H A Dnbd.rst15 Metadata namespaces
/openbmc/telemetry/src/
H A Dreport_factory.cpp107 sensorPath.at_label<Metadata>(), bus->get_io_context(), bus); in getSensors()
/openbmc/openbmc/poky/documentation/overview-manual/
H A Dyp-intro.rst213 your Metadata, the easier it is to cope with future changes.
239 and Metadata that support a new GUI environment, for example. This
635 :term:`Metadata` to get you started building your own distro. In other
713 Metadata is loosely grouped into configuration files or package recipes.
805 - *Metadata:* A key element of the Yocto Project is the Metadata that
808 image. In general, Metadata includes recipes, configuration files,
811 and the effects of the build. Metadata also includes commands and
843 You can see the Metadata in the ``meta`` directory of the Yocto
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Dreport-defect.rst25 ``meta-intel`` layer, you would choose "Build System, Metadata &

123