| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Add the missing mandatory SUMMARY and set SECTION.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
| |
Add the missing mandatory SUMMARY.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
meta-freescale used columnar alignment (multiple spaces padding the
variable name out to a common column) for tables of assignments such as
the fsl-eula-unpack MD5 sums and PACKAGECONFIG[...] entries. The Yocto
Recipe Style Guide and oelint-adv (oelint.vars.spacesassignment) call for
a single space around the assignment operator.
Collapse the padding to a single space on every flagged assignment. The
change is purely whitespace around the operator: variable names, operators
and values (including whitespace inside quoted values) are untouched, as
confirmed by an empty 'git diff -w'.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
| |
Add the mandatory HOMEPAGE to recipes whose upstream repository was not a
plain github/gitlab URL in SRC_URI: those using a source variable or an
included .inc (resolved to the real NXP/Freescale repo), and those hosted
elsewhere (denx, SourceForge, dpdk.org, freedesktop, jhauser). Clears the
oelint-adv oelint.var.mandatoryvar.HOMEPAGE error for these recipes.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the stray space between an assignment's opening quote and its
line-continuation backslash, and the space before '%' in inline
${@...} expressions. Generated mechanically by oelint-adv's auto-fix
for a single rule (oelint.vars.notneededspace), isolated to one commit.
The affected values are whitespace-separated lists (leading space is
insignificant) and Python format expressions ("%s"% p is equivalent),
so there is no functional change; a re-run of oelint-adv reports the
rule clean.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
| |
vulkan-wsi-layer depends on Vulkan being part of the distro configuration.
Inherit features_check and require the vulkan distro feature so non-Vulkan builds skip the recipe cleanly.
Tested as part of the series with bitbake -p and yocto-check-layer.
Signed-off-by: Luciano Dittgen <luciano.dittgen@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
'__STDC_VERSION__' is predefined by the compiler in C++ mode. Redefining
it triggers '-Wbuiltin-macro-redefined', which with '-Werror' fails the
build with GCC 16.
error: '__STDC_VERSION__' defined [-Werror]
As suggested in the Vulkan WSI Layer issue tracker, add a C++ guard
before the __STDC_VERSION__ define.
Signed-off-by: Franz Schnyder <franz.schnyder@toradex.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Make Vulkan-loader bbappend version-agnostic.
Previously, recipe parsing failed whenever Vulkan-loader was updated in
openembedded-core because the bbappend targeted a fixed version.
The Vulkan-loader code referenced in the patch was modified in
commit: ecd88b5c6b1e4c07 ("Define _FILE_OFFSET_BITS=64 for 32 bit linux builds")
(introduced in version 1.3.296). Since then, two different patches are now required.
Add a conditional in vulkan-loader_%.bbappend to apply the correct patch based
on the Vulkan-loader version.
Signed-off-by: Benjamin Missey <benjamin.missey@non.se.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The patch still applies cleanly. Follow the version bump, otherwise
- vulkan-loader_1.4.328.1.bbappend doesn't have a matching recipe
- vulkan-loader_%.bbappend adds the patch, however it is nowhere found
Both points results in meta data parsing errors.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The patch still applies cleanly. Follow the version bump, otherwise
- vulkan-loader_1.4.321.0.bbappend doesn't have a matching recipe
- vulkan-loader_%.bbappend adds the patch, however it is nowhere found
Both points results in meta data parsing errors.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
| |
Use the new virtual runtime provider to configure the ICD for i.MX GPU.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The build fails because it cannot find the patch files in the version-
specific folder. The problem is the bbappend uses `PN`. However, it
turns out that `BP` doesn't work either:
```
ERROR: /.../poky/meta/recipes-graphics/vulkan/vulkan-loader_1.4.321.0.bb: Unable to get checksum for vulkan-loader SRC_URI entry 0001-LF-11869-change-mali-wsi-layer-activating-order.patch: file could not be found
The following paths were searched:
/.../meta-freescale/recipes-graphics/vulkan/defaultpkgname-1.0/fsl/0001-LF-11869-change-mali-wsi-layer-activating-order.patch
[ %< SNIP %< ]
```
When `FILESEXTRAPATHS` is prepended, `BP` is not ready since the
immediate expansion operator `:=` is used, hence the folder name
`defaultpkgname-1.0` shown in the error log.
Fix the problem with hard-coded values.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Building for i.MX 8 without GPU results in a patching error:
```
ERROR: vulkan-loader-1.4.321.0-r0 do_patch: QA Issue: Fuzz detected:
Applying patch 0001-LF-11869-change-mali-wsi-layer-activating-order.patch
patching file loader/loader.c
Hunk #1 succeeded at 3034 with fuzz 1 (offset 128 lines).
Hunk #2 succeeded at 3101 (offset 135 lines).
Hunk #3 succeeded at 3115 (offset 135 lines).
The context lines in the patches can be updated with devtool:
devtool modify vulkan-loader
devtool finish --force-patch-refresh vulkan-loader <layer_path>
Don't forget to review changes done by devtool!
Patch log indicates that patches do not apply cleanly. [patch-fuzz]
```
The problem is i.MX 8 without GPU uses the latest Vulkan 1.4.321.0 and
needs that version of the patch, but the recipe provides the older
version of the patch for Vulkan 1.3.275.0.imx.
Use version-specific folders to resolve the mismatch.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
| |
Vivante is limited to older Vulkan, but Mali is not. Adapt the bbappend
so i.MX 9 can use the latest Vulkan while i.MX 8 continues to be
limited to 1.3.275.0.imx.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
| |
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
| |
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
spir: Update downgrade spir: 1.3.261.1.imx -> 1.3.275.0.imx
vulkan: Update downgrade vulkan: 1.3.261.1.imx -> 1.3.275.0.imx
vulkan-loader_1.3.261.1.imx.bbappend: Upgrade vulkan-loader: 1.3.261.1.imx -> 1.3.275.0.imx
Add patch for wsi layer
imx-base.inc: Update `PREFFERED_VERSION` for vulkan and spir
Signed-off-by: Valentin Jec <valentin.jec@nxp.com>
|
| |
|
|
|
|
| |
Align with NXP BSP 6.6.3-1.0.0.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
| |
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
|
|
| |
Rename from <recipe name>_<version>.bb to
<recipe name>_<version>.imx.bb
Hopefully making it more obvious that recipes
are forks/older version of what's in OE-core.
Signed-off-by: Vincent Davis Jr <vince@underview.tech>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The logic to move the .so into the main package is incorrect and results
in all libraries being moved to the dev package, causing a QA error like
the following:
```
ERROR: imx-gpu-sdk-5.7.1-r0 do_package_qa: QA Issue: imx-gpu-sdk rdepends on vulkan-loader-dev [dev-deps]
```
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
| |
The library libvulkan.so is loaded dynamically and so is needed in the
main package.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
| |
When i.MX GPU-based vulkan is used, the mesa drivers are not needed.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
| |
i.MX GPU drivers work with an older version of vulkan, so add the older
recipes.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
| |
With this the libvulkan-imx is recommends only when the machine
supports Vulkan.
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
The i.MX GPU package libvulkan-imx is missing at runtime because it is
dynamically loaded and has no implicit mechanism for inclusion in the
rootfs. Add the package explicitly.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|