summaryrefslogtreecommitdiffstats
path: root/recipes-bsp/imx-vpu/imx-vpu_3.10.17-1.0.0.bb
Commit message (Collapse)AuthorAgeFilesLines
* imx-vpu: Upgrade to 3.10.31-1.1.0 Beta versionLauren Post2014-11-101-15/+0
| | | | | | | | | | | | | | | Upgrade to v5.4.26 version - Fixes to support multiple thread robustness - SOF stuffing new command added used for MJPEG - VPU performance fixes with multiple instances - IOGetVirtMem - return checking - Remove patch from recipe - SOI search performance fixes - Comment unused registers for mx6 chips as dummy - Add new registers used on mx6 chips only. Signed-off-by: Lauren Post <lauren.post@freescale.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-{lib,vpu}: obey CFLAGS, LDFLAGSChristopher Larson2014-09-041-1/+4
| | | | | | | This quiets GNU_HASH warnings when building with an external toolchain. Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-vpu: fix checks of IOGetVirtMem() return valueEric Nelson2014-06-251-0/+2
| | | | | | | | | | | | | | | | | The IOGetVirtMem() routine returns the address of a memory block or -1 (MAP_FAILED) to indicate an error. Many callers of this routine tested the return value for <= 0 to detect failure, and at least with a 3G/1G memory split configured in the kernel, a negative number (!= -1) is a valid (successful) return value. Without this patch, the IOSystemInit() will often detect failure incorrectly. Change-Id: I8b20ae5f74608307cbb810168024e8863599dbdb Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-vpu: Update to 3.10.17-1.0.0 GA versionLauren Post2014-04-301-6/+2
| | | | | | Change-Id: I2cffa52aec15bce9efb09e4ef186f541f0b3afc0 Signed-off-by: Lauren Post <lauren.post@freescale.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* imx-vpu: Upgrade to 3.10.17-1.0.0_betaLauren Post2014-02-201-0/+14
Signed-off-by: Lauren Post <lauren.post@freescale.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>