...
| Expand |
|---|
| title | Click here to see set of sample manifests for developing OEM specific manifests |
|---|
|
| # | File | Remarks |
|---|
| 1 | Device Specific Manifest | This is the starting point of the build and is specific to a device. Usually it contains references to other manifest files which will be having specific set of repos | 6 | Third party apps | This manifest can contain meta layers related to Premium streaming applications which are chosen by OEM | 5 | RDK-V manifest | This manifest can contain meta layers specific to RDK & RDK-V and , for EXTERNALSRC cases, the RDK & RDK-V component repo details too. It might be supplemented with a conf file too | 3| 2 | OEM manifest | This manifest contains meta layer details of OEM( which might or might not be generic across OEMs multiple devices ) and , optionally, some OEM specific repos | 2 | SoC | 3 | SoC manifest | This manifest contains meta layer details of SoC and , optionally, some SoC specific repos | | 4 | RDK-B manifest | This manifest | contains meta layer details of SoC and , optionally, some SoC specific repos4can contain meta layers specific to RDK & RDK-V and , for EXTERNALSRC cases, the RDK & RDK-V component repo details too. It might be supplemented with a conf file too | | 5 | OE layers manifest | This manifest has details of the basic Yocto Open Embedded layers | | 6 | Third party apps | This manifest can contain meta layers related to their applications which are chosen by OEM |
|
For more details on getting RDK-B ported to an OEM device, please refer the links RDK-B OEM Specific Porting and Guideline for SoC and OEM Vendors
...
