2268 2012-04-09 20:40:35 +0000 Specify emgd feature in recipe-space 2013-03-14 10:59:01 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 1.3 x86 Multiple VERIFIED FIXED Low minor 1.4 M3 1 dvhart nitin.a.kamble alexandrux.palalau bruce.ashfield dvhart sgw tom.zanussi --- --- --- oldest_to_newest 20085 0 dvhart 2012-04-09 20:40:35 +0000 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. 23175 1 dvhart 2012-07-17 20:18:40 +0000 Moving to 1.3. 23353 2 dvhart 2012-07-20 21:08:09 +0000 This is a cleanup, prioritizing accordingly. 28685 3 nitin.a.kamble 2013-01-09 20:53:20 +0000 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 28688 4 dvhart 2013-01-09 21:29:41 +0000 Nitin, that was basically my thinking, yes. Rather than patches, this could just merge the EMGD branch. 29273 5 nitin.a.kamble 2013-01-29 06:03:19 +0000 This is completed with multiple commits in the meta-intel & kernel repos. 30694 6 alexandrux.palalau 2013-03-14 10:59:01 +0000 Verified on master branch. Commit ID: 4da406cd50cf02a63ed76810a670aba1eb561c79 used emgd-1.16 on crownbay-noemgd Switching to verified.