Forums » Software Development »
DCEVA/CVP API stack
Added by David Cuccia 7 days ago
Can CL enable the EVA/CVP stack in a MitySOM build — kernel driver (msm-eva/cvp), firmware ( cvpss/evass .mbn), and the SV SDK ( StereoDisparity engine that Qualcomm's open-source QcNode wraps)? We'd like to use this for stereo disparity-based profilometry.
We noted that CL's QLI 2.0 prelim build (https://support.criticallink.com/redmine/boards/78/topics/7410?r=7428#message-7428) already ships proprietary Qualcomm multimedia bits (gst-plugins-imsdk-prop , camx, qwes) — CL presumably has redistribution rights for vendor blobs, so the SV SDK plausibly arrives the same way?
Or is there direct Qualcomm engagement needed on our side?
Thanks!
David
Replies (2)
GG RE: EVA/CVP API stack - Added by Gregory Gluszek about 19 hours ago
Hi David,
Typically when it comes to modifying Qualcomm's proprietary code, unless it's in relation to our development board or a specific contract we have with a customer we would recommend becoming a Qualcomm "Licensed developers with authorized access" to get access to the necessary source to modify and build for your project's needs. The Building and Customizing firmware wiki page provides some direction on this (with the purpose of the page being on customizing and rebuilding the firmware for the QCS6490). If we've had experience with making changes to Qualcomm's proprietary code we like to make a wiki page that outlines what we've done to assist anyone who has access to the source and needs to make similar mods for their project. However, we do not have experience with the EVA/CVP stack or SV SDK. I've looked into this and QcNode a bit, but it seems this is all centered around Qualcomm's Advanced Driver Assistance Systems (ADAS), which I have not heard of being supported for the QCS6490. Could you provide some links relating to the EVA/CVP stack and SV SDK you're referring to so we can be sure it will be supported on the QCS6490?
Thanks,
Greg
DC RE: EVA/CVP API stack - Added by David Cuccia about 15 hours ago
Thanks! We'll validate with a CPU solution first and return with evidence if needed