linux/meta-freescale.git/recipes-bsp/libimxdmabuffer/libimxdmabuffer_1.2.0.bb, branch master

global: Use single space around variable assignments

2026-07-12T18:55:50+00:00

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

global: Indent multi-line variable continuations

2026-07-12T08:14:32+00:00

Align the continuation lines of multi-line variable assignments, as suggested by oelint-adv's auto-fix for a single rule (oelint.vars.multilineident), isolated to one commit. The auto-fix strips the leading space from a value's first line, which for a ':append' is a required separator; those five recipes had their leading space restored by hand, so ':append'/':prepend' concatenation is unchanged. A few multi-line values (e.g. DESCRIPTION) gain internal whitespace, which is cosmetic and collapses on display. Build-tested: parsing all 2948 recipes for an i.MX machine reports 0 errors. A residual set (the restored ':append' recipes, whose separator space oelint cannot reconcile with its indent preference, plus opencv/dpdk where oelint's own fix does not satisfy its checker) is left for per-recipe handling. Signed-off-by: Otavio Salvador

global: Drop needless whitespace in assignments

2026-07-12T07:54:14+00:00

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

libimxdmabuffer: Upgrade to version 1.2.0

2026-04-07T18:28:49+00:00

* waf: update to 2.1.9 * ion: Cache detected ion heaps mask * kernel: Set linux-imx 4.14.34 as the minimum required version * dma-buf: Add imx_dma_buffer_get_physical_address_from_dmabuf_fd() imx_dma_buffer_dma_heap_get_physical_address_from_dmabuf_fd() and imx_dma_buffer_ion_get_physical_address_from_dmabuf_fd() are deprecated, since starting with linux-imx 4.14.34, the DMA_BUF_IOCTL_PHYS ioctl can be used, which is independent of any particular allocator. Instead, imx_dma_buffer_get_physical_address_from_dmabuf_fd() is the recommended way to get physical address out of DMA-BUF FDs now. Signed-off-by: Carlos Rafael Giani