That's what I was trying to say ;-) I am. Sounds like a plan. Where can I find a list of the branches in the 4.0.1 meta data? I'm using the following to select one at the

Alright, sounds like a bigger project to get it out of the layer.conf and probably something we need to get into the documentation somewhere. This series looks fine to me otherwise. -- Darren

I did try that first, but puting it in the layer.conf was the only thing that worked. I think the same thing could be said for the other recipes in the COMMERCIAL_LICENSE list in default-distrovars,

The model is that you must explicitly chose values to modify them, otherwise, they flow through. Last through the gate wins. If you don't speak, others parts speak for the configuration. In this

That's what I've done. I used 'make xconfig' to modify the .config file (resulting from bitbake -c compile virtual/kernel). However, turning off CONFIG_USB_SERIAL and saving the result as a

I've tossed this onto the pile. Once some testing completes, I'll push this out with my 3.0.2 update. Bruce

Can't this be done in the common emgd driver recipe? Seems wrong to have to specify commercial license for recipe in a machine config... A different machine could just omit it and the user would not

Acked-by: Darren Hart <dvhart@...> -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

Acked-by: Darren Hart <dvhart@...> -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

From: Tom Zanussi <tom.zanussi@...> Document an alternative mechanism for users to deal with COMMERCIAL_LICENSE in the crownbay and fri2 BSPs. Signed-off-by: Tom Zanussi

From: Tom Zanussi <tom.zanussi@...> Update the meta-fri2 README to reflect the addtion of the EMGD capabilities and new machine. Changes were also made to reflect the new image names and a

From: Tom Zanussi <tom.zanussi@...> The emgd-driver-bin recipe now automatically downloads and installs EMGD using the new click-through-free tarball, but since the binaries still fall under a

From: Tom Zanussi <tom.zanussi@...> Add common/recipes-graphics so fri2 can pick up the EMGD bits in emgd-driver-bin. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---

From: Tom Zanussi <tom.zanussi@...> emgd-driver-bin will be shared by multiple BSPs, crownbay and fri2 to start with, so move them into /common. Signed-off-by: Tom Zanussi

From: Tom Zanussi <tom.zanussi@...> This patch essentially adds a new EMGD-capable 'fri2' machine to meta-fri2. The current version with vesa graphics will become fri2-noemgd; fri2 will become

From: Tom Zanussi <tom.zanussi@...> With the new emgd-driver-bin recipe, the extensive instructions on how to manually download and set up EMGD for the build are no longer necessary. Those

From: Tom Zanussi <tom.zanussi@...> This patchset switches crownbay to the 3.0 kernel and upgrades emgd to 1.8. Both crownbay and crownbay-noemgd were successfully built and boot tested into

From: Tom Zanussi <tom.zanussi@...> Update to the ced-generated xorg.conf for 1.8. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- .../xserver-xf86-config/crownbay/xorg.conf |

From: Tom Zanussi <tom.zanussi@...> The emgd-driver-bin recipe now automatically downloads and installs EMGD using the new click-through-free tarball, but since the binaries still fall under a

From: Tom Zanussi <tom.zanussi@...> Change preferred version of emgd binaries to 1.8. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- meta-crownbay/conf/machine/crownbay.conf | 2