/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | cython.bbclass | 5 # 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 D | toolchain-scripts-base.bbclass | 14 echo 'Metadata Revision: ${METADATA_REVISION}' >> $versionfile
|
/openbmc/openbmc/poky/documentation/kernel-dev/ |
H A D | advanced.rst | 4 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 D | intro.rst | 14 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 D | maint-appx.rst | 19 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/phosphor-fan-presence/control/json/utils/ |
H A D | pcie_card_metadata.hpp | 94 struct Metadata struct in phosphor::fan::control::json::PCIeCardMetadata 103 bool operator==(const Metadata& other) in operator ==() argument 142 std::vector<Metadata> _cards;
|
/openbmc/linux/tools/testing/kunit/ |
H A D | kunit_json.py | 16 class Metadata: class 50 def get_json_result(test: Test, metadata: Metadata) -> str: argument
|
H A D | kunit.py | 180 …metadata = kunit_json.Metadata(arch=linux.arch(), build_dir=request.build_dir, def_config='kunit_d… 219 def parse_tests(request: KunitParseRequest, metadata: kunit_json.Metadata, input_data: Iterable[str… argument 521 metadata = kunit_json.Metadata()
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | metafmt-vivid.rst | 9 VIVID Metadata Format 22 .. flat-table:: VIVID Metadata
|
H A D | pixfmt-compressed.rst | 121 Metadata associated with the frame to decode is required to be passed 165 Metadata associated with the frame to decode is required to be passed 187 Metadata associated with the frame to decode is required to be passed 215 Metadata associated with the frame to decode is required to be passed 237 Metadata associated with the frame to decode is required to be passed 267 pipeline with the :ref:`stateless_decoder`. Metadata associated with the
|
H A D | meta-formats.rst | 6 Metadata Formats
|
H A D | dev-meta.rst | 6 Metadata Interface 9 Metadata refers to any non-image data that supplements video frames with
|
H A D | metafmt-uvc.rst | 31 .. flat-table:: UVC Metadata Block
|
/openbmc/pldm/tools/fw-update/ |
H A D | README.md | 33 ## 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/types/ |
H A D | sensor_types.hpp | 15 utils::tstring::Metadata>;
|
H A D | report_types.cpp | 19 sensorParameters.at_label<ts::Metadata>()); in toReadingParameters()
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-2.0.rst | 91 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/tools/phosphor-logging/templates/ |
H A D | elog-process-metadata.mako.cpp | 16 extern const std::map<metadata::Metadata,
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/wic/ |
H A D | corstone1000-flash-firmware.wks.in | 12 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/telemetry/src/utils/ |
H A D | tstring.hpp | 27 struct Metadata struct
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | custom-distribution.rst | 7 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/phosphor-logging/ |
H A D | elog_meta.hpp | 24 using Metadata = std::string; typedef
|
/openbmc/linux/Documentation/admin-guide/nfs/ |
H A D | pnfs-scsi-server.rst | 7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/ |
H A D | 0007-Plaform-Corstone1000-Switch-to-metadata-v2.patch | 33 + * Metadata version 2 data structures defined by PSA_FW update specification 68 /* Metadata CRC value */
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | terms.rst | 210 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
|