Other Parts Discussed in Thread: DM3730, OMAP3530
Hi,
I am currently working on video acceleration in Android ICS on DM3730. My project is based on the rowboat release: http://code.google.com/p/rowboat/wiki/ICSonBeagleboard_WithSGX
I am trying two different approaches and would like some insight from the TI community.
My first approach has been to integrate the DVSDK as it was in gingerbread. I've made few changes to build the following packages:
* dsplink_arm
* dsplink_dsp
* dsplink_gpp_genpackage
* dsplink_dsp_genpackage
* lpm
* cmem
* sdma
* ce
* codecs
As the DMAI codecs part is made only for OpenCore and the PV framework, it has to be re-designed for Stagefright.
The second approach is to look at the omap4 way of accelerating video, especially the binding with stagefright (not a lot more as the architecture is obviously a lot different). From what I understood the hw part is added in the hardware/ti/omap4 folder in the omx and libstagefrighthw sub-directories. As I found the same directories in the hardware/ti/omap3/ folder of the rowboat release I built them even though I know they must not work as-is (otherwise it would have been activated). So far I haven't been able to bind them with the openmax layer.
Doing this work I noticed that even some software codecs do not work ([OMX.google.h264.decoder] ERROR(0x80001001, -1007)). The result I expected was that the video would be really slow but I do not understand why the software codec fails.
So here are my questions about this subject:
- What do these packages (hardware/ti/omap3/libstagefright and omx) provide?
- What is the work to be done on them to have an accelerated video (if possible this way)? How to bind them with SF?
- Which approach should I focus on (which one is the best)?
- Why doesnt the h264 sw codec work?
Thanks,
Gary