Skip to content

Navigation Menu

Sign inAppearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Sign upAppearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Uh oh!

There was an error while loading. Please reload this page.

rdkcentral / ut-core Public

Notifications You must be signed in to change notification settings
Fork 3
Star 5

Code
Issues 23
Pull requests 1
Discussions
Actions
Projects
Wiki
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security and quality
Insights

vDevice: Overview

Jump to bottom

Ulrond edited this page Oct 22, 2024 · 6 revisions

Moved to https://github.com/rdkcentral/ut-core/wiki/5.0:-Standards:-vDevice-Overview

Wiki pages Pages 57

Home
1. Standards & Development Process Flow
1.0. Standards: Tier 1 Operator Guide: Branching for Direct Contributions
1.0.1 Standards: Tier 2 Operator Guide: Forking for External Contributions
1.1. Standards: Principles from Code Complete
1.2. Standards: Issue Description Guideline
1.3. Standards: Milestone Description Guideline
1.4. Standards: Commit Message: The 50‐72 Rule: A Simple Guide
1.5. Standards: Semantic Versioning and Testing Suite Alignment
2. Standards: Single Source of Truth ‐ HAL Interfaces and Testing Suites
2.1. Standards: Doxygen: Crafting Excellent Documentation
2.2. Standards: Forking And Branching
2.3. Standards: Performing Changes to an interface
2.4. Standards: Repository Access and Branch Protection Policy
2.5. Standards: Feature Branch Workflow
3. Standards: Levels of Test for Vendor Layer
3.0.1 Standards: Testing Feedback Loops
3.1. Standards: Overview of Test‐Driven Development
3.2. Standards: Requirements for building testing suites
3.2.1: Standards: Phased Delivery with Checkpoints
3.3. Standards: L4 ‐ System Interface Testing
3.4. Standards: L4: Vendor Full Stack ‐ Video ‐ Smoke Regression Test
4. Standards: Dynamic Library Loading for Vendor Abstraction
4.0.1: Standards: Dynamic Library Search Order
4.1. Standards: Dynamically Installable Plugins In C
5.0.1: Standards: vDevice Architecture Overview
5.0: Standards: vDevice Overview
5.1.0: Standards: vDevice Controller
5.1.1: Standards: vDevice Control Plane
autogenerate.sh: Running the Framework Generation Script
FAQ: QEMU vs Vagrant
FAQ: Video and Audio Playback Performance Metrics
FAQ: Black‐Box Testing and Code Coverage Metrics
FAQ: Buildroot vs. Yocto Project vs. Bob the Builder
FAQ: C Macro that prints structure fields
FAQ: C macro that prints the function name, parameter names with values
FAQ: Choosing GHEC‐ORG or RDKCentral
FAQ: Comparing Python Development Platforms
FAQ: Git Flow Support for Multiple mainlines
FAQ: Git‐Flow: Developers Branching Model
FAQ: Migrating Binaries to `Git LFS`
FAQ: RDK Docker Toolchain
FAQ: Release Engineers: Performing a release with git flow
FAQ: Sign up for RDK Central ‐ Tier 1 Registration
FAQ: Software Post Release Development Cycle
FAQ: UT Core Framework Overview
FAQ: Vagrant: Setting Up and Managing Your Vagrant VM
How to use UT‐Core to write a simple app in C or CPP using the ut‐core subsystem
T1: Training: CODEOWNERS: Ensuring Code Quality and Governance
UT Core Building using Docker or Vagrant
ut_kvp: A Flexible Key‐Value Pair Framework
ut_kvp_profile: Key‐Value Pair Assertions for Unit Testing
UTCore: Test Group Support
UT‐Core: Concept Overview: UT‐Core and Engineering Suites Integration
UT‐Core: How to Build and Run a HAL Testing Suite
vDevice: Overview
Vendor Test Suites

Clone this wiki locally

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.