meta-intel currently defines emgd and non-emgd machines for all emgd-enabled BSPs. The linux-yocto kernel machine scc files are shared between the machines, but they merge in the emgd feature. This means the non-emgd machines still run a kernel patches with the emgd sources. Avoid this by moving the "merge emgd-1.10" to the emgd.scc feature and specifying the feature explicitly in the emgd version of the machine linux-yocto bbappend.
Moving to 1.3.
This is a cleanup, prioritizing accordingly.
Darren, Tom, Bruce, Does this get implemented by this kind of recipe configuration? KERNEL_FEATURES_append = " features/emgd-1.14" If yes, then we will need to create emgd-1.14 feature in the kernel repo. And that feature will just add couple of patches to the kernel tree. Is this is the best way to do this, or it can be done in any better way? Thanks, Nitin
Nitin, that was basically my thinking, yes. Rather than patches, this could just merge the EMGD branch.
This is completed with multiple commits in the meta-intel & kernel repos.
Verified on master branch. Commit ID: 4da406cd50cf02a63ed76810a670aba1eb561c79 used emgd-1.16 on crownbay-noemgd Switching to verified.