summaryrefslogtreecommitdiff
path: root/recipes/ti/ti-linuxutils.inc
AgeCommit message (Collapse)AuthorFiles
2010-04-25change INHIBIT_PACKAGE_STRIP to PACKAGE_STRIP with more optionsRoman Khimov1
Originally approached with "package.bbclass: introduce KEEP_GNU_DEBUGLINK": http://patchwork.openembedded.org/patch/886/ Redone with a change from INHIBIT_PACKAGE_STRIP to PACKAGE_STRIP which allows more options. By default it does exactly the same thing as is done today, strips the binary, but keeps the gnu.debuglink section. When set to "no", stripping is not done at all, when set to "full" the gnu.debuglink section is not re-added to the binary. Signed-off-by: Roman I Khimov <khimov@altell.ru> Acked-by: Chris Larson <chris_larson@mentor.com>
2010-04-12ti-recipes: Shoot ti-multimedia-common.inc, move inside ti-paths.incRoger Monk1
* Following cleanup, ti-paths is empty and simply includes ti-multimedia-common * Move ti-multimedia-common into ti-paths and shoot ti-multimedia-common * Fix recipe references that directly reference ti-multimedia-common Signed-off-by: Roger Monk <r-monk@ti.com> Signed-off-by: Koen Kooi <k-kooi@ti.com>
2010-04-12ti-linuxutils.inc: build irq module on dm365 platformBrijesh Singh1
Signed-off-by: Brijesh Singh <bksingh@ti.com> Signed-off-by: Koen Kooi <k-kooi@ti.com>
2010-04-12ti recipes: add license sectionBrijesh Singh1
Signed-off-by: Brijesh Singh <bksingh@ti.com> Signed-off-by: Koen Kooi <k-kooi@ti.com>
2010-04-12ti-recipes: Add SECTION qualifiers to recipesRoger Monk1
Signed-off-by: Roger Monk <r-monk@ti.com> Signed-off-by: Koen Kooi <k-kooi@ti.com>
2010-04-12ti-dmai: convert to new style staging ti-linux-utils: dittoKoen Kooi1
Signed-off-by: Koen Kooi <k-kooi@ti.com>
2010-04-12ti recipes: start moving from -native to machine specificKoen Kooi1
Signed-off-by: Koen Kooi <k-kooi@ti.com>
2009-12-04recipes/ti: merge in updatesKoen Kooi1
* 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.