Great, the best thing would be to submit a pull request against the edison branch with a suitable subject. Congratulations! I appreciate your effort in sharing this work. Joshua

Merged into psplash upstream, if you would like to send a patch to Openembedded-Core updating the psplash recipe that would be welcome also. Thanks Sau!

Thanks Scott, I'm closing up on the edison branch changes and testing and I will be adding more to the denzil branch soon. -M

Cool, this is a fairly convenient way for me to merge in these commits. Like Joshua has pointed out, as long as they are bugfixes and don't introduce significant feature additions or create backward

I'm fine to have some of them rejected, such is how things work ;) I know what you mean ;) Yep, I've made my best effort to only backport commits already upstream. I understand. I'm fine with

Indeed, that's likely the sum of it but the changes in isolation don't offer any context as to why they're required for PPC so my gut reaction is to reject them as they violate the suggested

OK. Yes. I see very little of this, the valgrind series and/or the a few other image generation bits. So is poky edison dead now? How do I support folks that still want to use it? I understand that

I don't know how much work will be done on Edison after the 1.1.2 release. I personally will no longer be working on it and I don't think the team here as enough resources to maintain it

From: Nitin A Kamble <nitin.a.kamble@...> Add emgd config option (DRM_EGD) and modify Makefiles for in-tree builds. rebased to v3.4 code Fix build errors caused by changes to kernel

From: Nitin A Kamble <nitin.a.kamble@...> These commits add emgd 1.14 driver support for linux kernel v3.4 These commits need to go in a new branch named "emgd-1.14", so that it can be merged

Thanks Khem,I successfully found g++ compiler path which is: /opt/poky/1.2.1/sysroots/i686-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ now I was able to

Aloha all, I have successfully managed to build a custom kernel, thanks to the help on IRC. Unfortunately this is only step one of my travels with Yocto. I now need to be able to build the kernel

Hello, With a recent poky tree (updated on 16.07.2012) I'm unable to make a multilib build. I added these lines to my conf/local.conf: require conf/multilib.conf MULTILIBS =

Hmmm. And here I was just thinking that things had been quiet on this front and it was time to get supported move to the 3.4 kernel tree. Which exact beagleboard (model/revision) is this ? Was the

Hi, I found the solution, I had to ensure that the KERNEL_DEVICE tree variable evaluate to the following KERNEL_DEVICETREE = "${S}/arch/powerpc/boot/dts/virtex440-ml507.dts" i.e. it was missing

Hi Khem, I tried various combinations, but all of them did not yield a dtb file. KERNEL_DEVICETREE = "virtex440-ml507.dtb" (as you suggested in your original email, but I guess it might have been a

I did the mentioned modification and it worked.. Thanks a lot..

This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in

This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can