Home
last modified time | relevance | path

Searched refs:layers (Results 176 – 200 of 426) sorted by relevance

12345678910>>...18

/openbmc/linux/Documentation/filesystems/
H A Dindex.rst44 Filesystem support layers
/openbmc/openbmc/poky/meta/recipes-graphics/spir/
H A Dspirv-tools_1.3.280.0.bb15 # vulkan-validation-layers, vulkan-utility-libraries.
/openbmc/linux/Documentation/userspace-api/media/dvb/
H A Dfe_property_parameters.rst291 is consisting of one segment and layer or three segments and two layers.
382 .. _isdb-hierq-layers:
390 ISDB-T hierarchical layers can be decoded simultaneously. For that
393 ISDB-T has 3 hierarchical layers which each can use a part of the
394 available segments. The total number of segments over all layers has to
408 layers in the decoding process. Setting all bits of
409 ``DTV_ISDBT_LAYER_ENABLED`` to '1' forces all layers (if applicable) to
/openbmc/linux/drivers/edac/
H A Ddebugfs.c65 edac_layer_name[mci->layers[i].type]); in edac_create_debugfs_nodes()
/openbmc/openbmc/meta-openpower/
H A DREADME.md12 layers: meta
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/networkmanager/
H A Dnetworkmanager-fortisslvpn_1.4.0.bb21 # meta-gnome in layers is required using gnome:
/openbmc/openbmc/poky/meta/recipes-multimedia/gstreamer/
H A Dgstreamer1.0-vaapi_1.22.11.bb32 # and BSP layers to pick either glx, egl, or no GL. By default,
/openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/css/
H A Ddefault.css136 /* Style the form links in the project page (all machines, all layers, etc) */
147 /* Style the layers section in the project page and the layer dependencies in the import layer form…
154 #layers-in-project-list .tooltip-inner { max-width: 600px; }
155 #no-layers-in-project { margin-top: 20px; }
156 #no-layers-in-project ul { margin-top: 10px; }
/openbmc/linux/Documentation/admin-guide/
H A Dsyscall-user-dispatch.rst10 Compatibility layers like Wine need a way to efficiently emulate system
83 Syscall User Dispatch provides functionality for compatibility layers to
/openbmc/linux/Documentation/devicetree/bindings/firmware/
H A Dintel,stratix10-svc.txt12 exception layers must channel through the EL3 software whenever it needs
/openbmc/openbmc/meta-google/
H A DREADME40 other layers needed. e.g.:
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Didentify-component.rst6 The Yocto Project and OpenEmbedded ecosystem is built of :term:`layers <Layer>`
/openbmc/openbmc/meta-raspberrypi/.github/workflows/
H A Dyocto-builds.yml56 dynamic-layers/**
/openbmc/openbmc/meta-openembedded/meta-python/conf/include/
H A Dptest-packagelists-meta-python.inc6 # meta_python_ptest_recipes=$(bitbake-layers show-recipes --recipes-only --layer meta-python --inhe…
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dlicenses.rst323 and layers sources for the time being), but this output also includes
457 By releasing the version of the OpenEmbedded build system and the layers
463 those layers are used to patch, compile, package, or modify (in any way)
465 required to release those layers under section 3 of GPLv2 or section 1
467 of the Yocto Project and layers used during your build. Here is an
475 # We built using the release_branch for our layers
485 development organization's layers are included in the ``bblayers.conf`` file
504 layers (recipes, configuration files, and so forth) enables you to meet
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-ref-variables.rst133 condition often occurs when layers get out of sync (e.g. ``oe-core``
773 layers. The precedence established through this variable stands
789 You can use the command bitbake-layers show-layers to list all
790 configured layers along with their priorities.
803 identify the layers by the collections that the layers define.
808 dependency on those other layers.
812 dependency on those other layers.
871 in conjunction with ``bitbake-layers layerindex-fetch`` and tells
872 ``bitbake-layers`` where to place the fetched layers.
991 layers that contain different versions of the same recipe.
[all …]
/openbmc/linux/fs/overlayfs/
H A Dnamei.c401 layer = &ofs->layers[ofs->numlayer - ofs->numdatalayer]; in ovl_lookup_data_layers()
426 if (ofs->layers[i].fsid && in ovl_check_origin_fh()
427 ofs->layers[i].fs->bad_uuid) in ovl_check_origin_fh()
430 origin = ovl_decode_real_fh(ofs, fh, ofs->layers[i].mnt, in ovl_check_origin_fh()
453 .layer = &ofs->layers[i] in ovl_check_origin_fh()
H A Dparams.c768 iput(ofs->layers[i].trap); in ovl_free_fs()
770 mounts[i] = ofs->layers[i].mnt; in ovl_free_fs()
773 kfree(ofs->layers); in ovl_free_fs()
/openbmc/openbmc/poky/bitbake/lib/bb/tests/
H A Dutils.py667layers = [{"SRC_URI"}, {"QT_GIT", "QT_MODULE", "QT_MODULE_BRANCH_PARAM", "QT_GIT_PROTOCOL"}, {"QT_…
668 self.check_referenced("${SRC_URI}", layers)
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/tracker/
H A Dtracker-miners_3.7.1.bb70 # your layers and 'libseccomp' to PACKAGECONFIG".
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dpopulate_sdk_ext.bbclass196 # Copy in all metadata layers + bitbake (as repositories)
204 …corebase, sdkbblayers = buildsystem.copy_bitbake_and_layers(baseoutpath + '/layers', workspace_nam…
205 conf_bbpath = os.path.join('layers', corebase, 'bitbake')
207 for path in os.listdir(baseoutpath + '/layers'):
208 relpath = os.path.join('layers', path, oe_init_env_script)
212 relpath = os.path.join('layers', path, 'scripts', 'esdk-tools', 'devtool')
216 relpath = os.path.join('layers', path, 'meta')
272 f.write(' $' + '{SDKBASEMETAPATH}/layers/%s \\\n' % layerrelpath)
850 # sdk(since the layers are put in the sdk) set the task to nostamp so it
/openbmc/openbmc/poky/meta/lib/oeqa/utils/
H A Dcommands.py291 layers = bblayers.split()
293 for l in layers:
/openbmc/openbmc/poky/meta/classes/
H A Dtoaster.bbclass27 # Find and dump layer info when we got the layers parsed
45 """ Some layers have a different name on openembedded.org site,
72 layer_url = 'http://layers.openembedded.org/layerindex/layer/{layer}/'
/openbmc/linux/Documentation/gpu/
H A Dkomeda-kms.rst40 Compositor blends multiple layers or pixel data flows into one single display
328 achieve this, split the komeda device into two layers: CORE and CHIP.
385 parts and handles it by two layers and two scalers individually. But it
394 only can be used for bottom layers composition. The komeda driver wants to
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/atop/
H A Datop_2.4.0.bb7 memory, swap, disks (including LVM) and network layers, and for every process \

12345678910>>...18