Need to understand how Codec Engine (CE) on Linux for DM3730 is ported on QNX and what all components needs to be ported. This is needed for a split video decoder to run on QNX on DM3730. The application on ARM will access the decoder libraries running on ARM and DSP through Codec Engine.
Since it is a split decoder, the application uses VIDDEC2_FRONT calls for accessing ARM side decoder library and VIDDEC2_BACK calls for accessing DSP side library.
Split decoder that runs on DM3730 uses CMEM memory allocations, DMA channels on DSP side, instruction caches and data caches.
I am listing below the components which I think needs to be ported from TI’s DVSDK (ti-dvsdk_dm3730-evm_4_03_00_06) on Linux for DM3730:
- Codec Engine (codec-engine_2_26_02_11),
- DSPLink,
- DMAN3,
- DSKT2,
- CMEM,
- OSAL
I have some questions. Can I get the answers for these questions?
- Is the above list complete?
- Are there any other relevant components from framework-components_2_26_00_01 and other folders of DVSDK (ti-dvsdk_dm3730-evm_4_03_00_06) that also need to be ported?
- Are the version numbers I have mentioned in the above list latest?
- How can the ported Codec Engine be tested? Is there any test suite from TI?
- TI's Codec Engine for Linux comes with several example applications. Is testing the ported Codec Engine with these example applications especially the ones related to video decoder (viddec2 split and viddec2 interfaces) sufficient?
