Page History

The roadmap is always available to the Preferred and Preferred Plus members of RDK at https://wiki.rdkcentral.com/display/ASP/Roadmap . To become a preferred member as well as to know the benefits, please visit https://rdkcentral.com/memberships/  . For the non preferred members, you can get answers to specific queries on Roadmap items by contacting support@rdkcentral.com or asking at https://wiki.rdkcentral.com/display/FORUMS/FORUMS+Home .

Please refer Breakpad steps

On 15 August 2013 Comcast Cable and Time Warner Cable jointly announced the formation of RDK Management, LLC to fulfill the role of the "RDK Entity".

We will maintain compatibility with the previous RDK version as described by the guidelines in the agreement. Additional details will be posted on the RDK Wiki as they become available.

Licensee are not required to take a new baseline.

RDKM does not assess run-time royalties for the Generic RDK.

The infrastructure to support DVB exists today; but additional components may need to be developed to support the particular network type. Typical enhancements include converting a URI to a network-specific identifier in the SI handling, and enhancing the security processor to implement CA that doesn't use the cable card.

RDK supports CEA-708 and EIA-608.

The font-type used for Closed Captioning belongs to an opensource family called Droid with specific glyphs for closed captions. Incase operators are using licensed fonts they have to meet the exclusive license requirements for those fonts.

OEM vendors will need to work with font vendors to provide fonts that comply with FCC standards. RDK Support is looking into whether FCC-compliant open-source fonts are available, and will provide that information in a future update.

To add VOD support for a different system, the VOD client would be rewritten to talk to the appropriate backend to provide content. This is an independent implementation and not coupled to any specific MSO configuration. The client is responsible for tuning to the content, connecting it to a sink, and starting streaming. It comes into play only after a VOD request is received by the receiver, the purchase is completed, and the connection is created (i.e., broadcast has started from servers side). Because time shift buffers are not allowed for VOD content, trickplay commands are merely forwarded to the content source, which is responsible for taking the appropriate actions.

Yes, RDK supports these tags in the current version.

Device Settings is integrated with IARM, which invokes the HAL API to effect changes requested by the application. Interface specifications are available for application developers.

The IP client provided by RDK works with the RDK Server, not the general DMS. This is the direction for now. CVP-1 and CVP-2 certification are planned for RDK Servers.

Separate RDK release packages will be available for IP and Hybrid versions. The requirements will draw a clear distinction between IP and Hybrid components

Control of front-panel brightness and other front-panel controls such as LED displays, power-button and similar controls will be specified as part of the Comcast Manufacturer Interface Specification.

The answer can be "extsrc is used to faciliate easy development work. If it is preferred otherwise, there is a XXX-nosrc.xml manifest file which will be retained after the first build and hence saving time 

Many developments  & improvements happening in RDK .Few are listed below.

• Doxygen : Video & Broadband documentations are available in the following locations.
  • For Broadband: https://wiki.rdkcentral.com/doxygen/rdkb/index.html
  • For Video: https://wiki.rdkcentral.com/doxygen/rdkv-opensourced/index.html
• Github : https://github.com/rdkcentral/
• Systemd

For latest updates see Announcements at https://wiki.rdkcentral.com/ page and  " What is the Roadmap for the RDK?" question in this page to know about the Roadmap of RDK.

1. git commit your changes in both the local repos
2. Create a branch and check it out in both repos make sure it has the SAME NAME (i.e. git checkout -b my_special_changes)
3. Then finally do a git review in both repos (or more specifically git review master or git review stable2)

What this does:

In gerrit the changes will be put up for review in the branch you specified in your git review command (master or stable2). At the same time it will set the Topic field to the name of your local branch (i.e. my_special_changes). When gerrit sees topic fields with identical names it binds them together. So it forces project maintainers to press the "Submit Together" button so they go in at the same time once given +2.

Install SDK if it is not already installed by following the steps under the previous heading. Install Groovy version 2.0.7 / 2.0.6 (until M75)using the below command 

• sdk install groovy 2.0.6

Check groovy version :

• groovy -version

From M76 release onwards, the supported groovy version is groovy 2.3.0. Install SDK if it is not already installed by following the steps under the previous heading. Install Groovy version 2.3.0 using the below command –

• sdk install groovy 2.3.0

Check groovy version :

• groovy –version

Follow are the commands to install MySQL

• sudo apt-get install mysql-server      

mysql installation will ask for the password during installation. (give the root password)

If validate_password plugin is present for Mysql, set the password policy as LOW using the below command

• set GLOBAL validate_password_policy=LOW; flush privileges";

Login to mysql prompt

• sudo mysql -u root -p

It will ask for password, give the root password given during installation.

There is no size restrictions imposed by RDK as such, the limits depends on SoC and OEM factors including Flash size. The firmware image will be compressed using SquashFS with LZMA compression.

No advanced options are currently supported by the IARM.  It is mainly an event bus with a pub/sub metaphor.  A lot of what is available is driven by the need.  If some of the features are needed we should see a feature request.  We are open to discussion of improvement as long as there is a case for it. No metrics have been captured at this time outside of the overall cloud metrics where IARM is part of the overall latency.

The various components in RDK have dependencies on other components, and some of these have similar functions. As long as the claims on memory and other system resources is small (e.g., Mongoose is a single file) it may be expedient to retain these redundant components.

It is optional and some devices is known to have HDMI 2.0 such as accelerator.

 Checkout relevant code repos based on your requirements from https://code.rdkcentral.com/r/admin/repos

1. For Open sourced components, search for required component in the filter option to get the relevant code repo.
2. For Licensed components, sign in to https://code.rdkcentral.com/r/admin/repos using username and password,and search for required component in the filter option to get the relevant code repo.