[meta-ti] [master PATCH v2 0/1] Updating IPUMM recipes to the latest

[Karthik Ramanan]

Here is the link to the latest IPUMM recipe on meta-ti : http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/ipumm-fw/ipumm-fw_3.00.04.02.bb
Here is the link to the patchworks for version v1 of new recipe: http://dflvsu0004.dal.design.ti.com/patch/10880/

* The recipe today supports both dra7xx and omap5.
* But GLSDK has dropped the support for omap5, starting from the 6.10.00.01 release. 
* Am assuming that the ipumm-fw recipe should continue to provide atleast the last supported firmware binary for OMAP5 which is why the older OMAP5 firmware binary is still referenced in the recipe.
* The firmware binaries have always been different. So we had this earlier approach of having two different recipes and then we decided to have a single recipe supporting both.
Link to the older recipe approach: http://arago-project.org/git/projects/meta-ti-glsdk.git?p=projects/meta-ti-glsdk.git;a=tree;f=recipes-ti/ipumm-fw;h=bcba55d8ac71890c5e53cda25c1d2b2eebe675b7;hb=6b80942da01d63a46567f3fe7b50bb1e945de1ba

Things to do:

* Add am57xx as compatible machine at a later time.
* Discuss about the python function that checks for the MMIP being defined in the MACHINE_FEATURES. Doesn’t this make it a two level indirection to support ipumm-fw?
What is the reason for introducing this? I would like to understand this further.


Karthik Ramanan (1):
  ipumm-fw: Updated ipumm firmware for latest IPC version

 ...umm-fw_3.00.04.02.bb => ipumm-fw_3.00.06.00.bb} |   25 ++++++++++----------
 1 file changed, 12 insertions(+), 13 deletions(-)
 rename recipes-bsp/ipumm-fw/{ipumm-fw_3.00.04.02.bb => ipumm-fw_3.00.06.00.bb} (53%)

-- 
1.7.9.5