!!! RDKM Confluence(wiki) Now Migrated from LDAP to SSO Authentication !!!
For more information, including FAQs and resources, please visit the link below:
RDKM-SSO
Any questions or comments please feel free to contact RDK Support team support@rdkcentral.com .
Thank you. ***
Generated core minimal image using the recipe rdk-geneirc-camera-img.bb
Analysis on RDK-C manifest and listed out the recipes need to be written and available ones
Planned to have validation using userland utilities like raspistil, raspivid etc
Also would like to valid the streaming use cases with gst-launch utilities with v4l2 src and glimage sinks etc
RDK-C Team :
Working on the Yocto recipes for the SoC SDK with minimal boot core image with external toolchains
Suggesting for the streaming use cases for first validation along with basic features such as Webpa
RDK-M Team :
Need to work along with Revathy on the meta layers for proposing the changes on recipes
Raj to come up with road-map plan for covering the features
As of now comcast JIRA is used for epic story ticket and in RDK wiki we shall have restricted page within the RDK-M and Comcast-RDK-C team
Platform Team :
Able to perform a media playback using the captured camera content in the RDK-V media client image through an R-Pi -3B Target board
Used gstreamer launch command : gst-launch-1.0 v4l2src ! glimagesink
Currently trying to bring up the camera in the R-Pi0 and comparing the driver differences between the R-Pi3B and R-Pi0
Trying for the media playback using gst command in a week in R-pi0
Will be syncing up with Revathy post this call
RDK-M Team :
Platform team need to discuss on the RDK-C components and its features for R-Pi0 port and come with a road-map plan on the same
Need to target the release for Q-3
Platform Team :
Able to bring up the camera in the Ri-Pi 0 Target
Able to perform a media playback using the captured camera content in the core minimal image through an R-Pi -0 Target board
Used gstreamer launch command : gst-launch-1.0 v4l2src ! glimagesink
Explained comprehensive the list of available and non available yocto recipes for the components in the RDK-C Stack
Will be syncing up with Revathy post this call
RDK-M Team :
Please prepare the yocto skeleton design approach for hosting the camera and soc specific recipes and get it approved by RDK-C team and Khem
Building from the comcast yocto repo for the core minimal image and deploying in the R-Pi Target
Shall target for Media streaming and Thumbnail features
Also follow up with Sundar on the open-sourcing of the RDK-C components
Platform team need to discuss on the RDK-C components and its features for R-Pi0 port and come with a road-map plan on the same
Need to target the release for Q-3
Platform Team :
Created separate configuration file for R-Pi Zero Target, which includes kernel configuration Pushed the changes with respect to Configuration and Gstreamer plugins in the Comcast Jira https://ccp.sys.comcast.net/browse/RDKC-5173
Build the core minimal image from Comcast gerrit repo along with the gstreamer components
Mapped RDK-C components with respect to features
Able to capture video using camera and displayed to the display panel
Explained with an analysis deck on the below items
Analysis on Yocto Recipes Availability and Non - Availability
RDK-Components vs feature mapping
RDK camera meta layers and recipes
RDK-M Team :
Need to get confirmation from Vijay regarding the open sourcing of the EMS component and taking that as the media streaming use case
Please ask Vijay to join the next call
Platform Team :
Started working on the recipe creation for the ems component
Finding the dependencies like sysapp which in turn has dependencies like ledmgr, buttonmgr. Would like to know still those are needed for r-pi port ?
RDK-C Team :
Vijay : Those are with respect to xcam only we can exclude the syspp dependencies for R-Pi
Also we shall exclude the sdk dependencies by using the macro -DSDK_DISABLED
For R-Pi, you need to do an customization in the following two files for streaming to work
sources/thelib/include/api3rdparty/apiprotocol.h
sources/thelib/src/api3rdparty/apiprotocol.cpp
W can still use ems for mediastreaming for R-Pi as we shall be opensourcing shortly
Also it uses the light webrtc for streaming
Hope there shouldn't be any dependencies on soc/sdk side
Once the reference platform team creates the recipe for ems we shall be supporting further on the use case validation
Platform Team :
Started working on the recipe creation for the ems component
Compiled the below modules of EMS component using cmake