Bug 2268

Summary: Specify emgd feature in recipe-space
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Darren Hart <dvhart>
Component: kernelAssignee: Nitin Kamble <nitin.a.kamble>
Status: VERIFIED FIXED QA Contact:
Severity: minor    
Priority: Low CC: alexandrux.palalau, bruce.ashfield, dvhart, sgw, tom.zanussi
Version: 1.3   
Target Milestone: 1.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Darren Hart 2012-04-09 20:40:35 UTC 
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.
Comment 1 Darren Hart 2012-07-17 20:18:40 UTC 
Moving to 1.3.
Comment 2 Darren Hart 2012-07-20 21:08:09 UTC 
This is a cleanup, prioritizing accordingly.
Comment 3 Nitin Kamble 2013-01-09 20:53:20 UTC 
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
Comment 4 Darren Hart 2013-01-09 21:29:41 UTC 
Nitin, that was basically my thinking, yes. Rather than patches, this could just merge the EMGD branch.
Comment 5 Nitin Kamble 2013-01-29 06:03:19 UTC 
This is completed with multiple commits in the meta-intel & kernel repos.
Comment 6 Alexandru Palalau 2013-03-14 10:59:01 UTC 
Verified on master branch.
Commit ID: 4da406cd50cf02a63ed76810a670aba1eb561c79
used emgd-1.16 on crownbay-noemgd
Switching to verified.