RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
Release No. | Date | Revision Description |
1.0 | 02 Mar 2020 | Updated Release Information , Release Identification for 2020 M2 Release Updated Features supported for this sprint and Community tickets addressed
|
1.1 | 31 Mar 2020 | Updated Release Information , Release Identification for 2020 M3 Release Updated Features supported for this sprint and Community tickets addressed Updated Known Issues and Limitations for
|
1.2 | 30 April 2020 | Updated Release Information , Release Identification for 2020 M4 Release Updated Features supported for this sprint and Community tickets addressed
|
1.3 | 29 May 2020 | Updated Release Information, Release Identification for 2020 M5 Release Updated Features supported for this sprint and Community tickets addressed
|
1.4 | 30 Jun 2020 | Updated Release Information, Release Identification for 2020 M6 Release Updated Features supported for this sprint and Community tickets addressed
|
1.5 | 31 July 2020 | Updated Release Information, Release Identification for 2020 M7 Release Updated Features supported for this sprint and Community tickets addressed
|
Contents Table of Contents style none
...
S.No | Feature | Device | Profile | Remarks | Tickets |
---|---|---|---|---|---|
1 | Turris Omnia | RDKB | |||
2 | Yocto 3.1 Image Stabilization and Validation | Turris Omnia | RDKB | ||
3 | RDKB Emulator hal re-factoring | Emu | RDKB | Currently, we are hosting the Emulator hal source code in generic hal repo( i,e rdkb/components/opensource/ccsp/hal under the source-pc folder. So, it doesn't cause any impact on other targets). Getting the changes at rdk-next branch takes around 2 to 3 weeks after round tripping the comcast sprint, stable2 branches (Which is not ideally needed because the changes are in emulator HAL specific in source-pc)
| Sub Tasks: |
4 | Integrated SNMP module support in rpi platform | R-PI | RDKB |
| Related tickets |
5 | Online / Offline status of connected devices on RDKB | R-Pi | RDK-B | In WebUI, connected Device > Devices > Connected clients status need to be updated properly. If any new associated clients connected with our Gateway Device,that client information should be properly updated in WebUI under online status. If any connected clients disconnects from our Gateway Device, that clients information's should be properly updated in WebUI under Offline status For that, we have implemented the below api's, update_wifi_inactive_AssociatedDeviceInfo() wifi_getApInactiveAssociatedDeviceDiagnosticResult() CosaDMLWiFi_Send_FullHostDetails_To_LMLite() | REFPLTB-622 |
6 | R-Pi | RDKV | |||
7 | R-Pi | RDKC | |||
8 | Community Tickets | R-Pi, Turris Omnia and Emulator | RDKB | ||
9 | Community Tickets | R-Pi | RDKV |
...