Age | Commit message (Collapse) | Author | Files |
|
Signed-off-by: Brijesh Singh <bksingh@ti.com>
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
Signed-off-by: Roger Monk <r-monk@ti.com>
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
* ti-xdctools: consistent recipe cleanup + add versions
* ti-dspbios: recipe cleanup + add versions
* ti-cgt6x: consistent recipe cleanup + add versions
* ti-biosutils: consistent recipe cleanup
* ti-xdais: consistent recipe cleanup + add versions
* ti-edma3lld: consistent recipe cleanup + remove broken version
* ti-framework-components: consistent recipe cleanup
* ti-dspbios: remove non-public versions
* ti-lpm-module/ti-local-power-manager: recipe cleanup, breakout and rename
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
low level driver 1.11.00.02 ti-bios-utils: Add BIOSUTILS package 1.02.02 ti-codec-engine : 2.25.00.05 using lite-CE, i.e. without cetools dependency
- improve installer to put dsp server executables next to arm apps
- add runtime depends on cmem, dsplink modules
- small tweaks for OMAPL138
ti-multimedia-common: Adding new paths for subcomponents
ti-dsplink-module: Adding suffix to track kernel version changes
angstrom: add infrastructure to set preferred versions for the codec-engine dependency chain
- the DEFAULT_PREFERENCE approach didn't scale
- add codec-engine 2.25.01 preferred versions and set as default
ti-xdais : adding recipe for v6.25.01.08
ti-codec-engine: remove 2.25.01, add 2.25.01.06
ti-framework-components: Add recipe for v2.25.01.05
ti-lpm: Renaming recipe to reflect component version instead of parent version
ti-multimedia-common: change path for separately staged lpm
ti recipes: remove bogus autotools defines
- autotools.bbclass isn't used or needed here
ti-lpm-module: switch to TSPA release and fix versioning
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
* New codec recipes from Arago team in Germantown
* Updated dm6446 and dm355 from Brijesh Singh
* cmem, gst-ti and dmai fixes from Brijesh Singh
angstrom: introduce SOC_FAMILY and start using it TI recipes as a testing ground
* SOC_FAMILY tells you which system on chip is used in the MACHINE, e.g. omap3, dm355, pxa25x, s3c24xx.
This avoids having to duplicate lots of overrides in machine specific recipes. This is *NOT*
intended to be used as a package arch.
|