summaryrefslogtreecommitdiffstats
path: root/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
Commit message (Collapse)AuthorAgeFilesLines
* imx-vpu: Upgrade to 5.4.39.1Cristinel Panfir2019-12-161-31/+0
| | | | | | | - Bring imx6/7 soc on q-preview (LOCAL_MODULE_TAGS) - Add ION_FLAG_CACHED when buffer need CPU access Signed-off-by: Cristinel Panfir <cristinel.panfir@nxp.com>
* layer: replace ${PN} with ${BPN} in SRC_URIMax Krummenacher2019-09-141-1/+1
| | | | | | | This prevents a number warnings like the following: | imx-sc-firmware-1.2-r0 do_package_qa: QA Issue: imx-sc-firmware: SRC_URI uses PN not BPN [src-uri-bad] Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* classes/use-imx-headers: Easy linux-imx-headers useOtavio Salvador2018-10-261-5/+2
| | | | | | | | | | | | | | | | | | | | | This allow to easy reuse of binary packages among similar SoCs. The usual use for this is to share SoC specific packages among different boards independently of the kernel version it is using, as far it is ABI compatible with the official version it will just work. Following recipes has been reworked to make use of the class: - imx-lib - imx-test - imx-vpu-hantro - imx-vpu - imx-alsa-plugins - gstreamer1.0-plugins-base - gstreamer1.0-plugins-imx - imx-gst1.0-plugin Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-vpu: Use linux-imx-headersOtavio Salvador2018-10-261-4/+3
| | | | | | | This reworks make use of linux-imx-headers and set it as SoC arch compatible. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-vpu: Clarify compatibility for Chips&Media VPUTom Hochstein2018-08-301-3/+3
| | | | | Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-vpu: Update to version 5.4.38Fabio Berton2018-06-261-0/+35
- Update license checksum to match EULA v22 April 2018. - Remove .inc file to use only one .bb file - Update O.S. Systems Software Copyright Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>