Perhaps the layer need additional maintainers? I'm happy to volunteer, I have multiple RaspberryPi(s) (model B) as well as a RaspberryPi-2 available for testing. --

Hi Khem, Because of running into same issues I've tried your branch and get errors as attached with current oe-core. Off-topic note: I think this layer is totally under-maintained. There were many

Building userland source with gcc 5.x causes multiple issues such as: vcos_thread.h:186:15: warning: inline function 'vcos_thread_get_affinity' declared but never defined | VCOS_UNSIGNED

That adds some rules to /etc/udev/rules.d, including automounting. I had that in there for a day or so, because I also need to access an external flash drive sometimes, but it had some insoluble

are you installing udev-extraconf into image? IIRC that was doing it in my cases some time ago.

My x86 system, built with Yocto Fido, boots from /dev/sda2 on a USB flash drive. There's another partition on /dev/sda1 which I wish to mount with a systemd mount unit, or with a line in /etc/fstab.

I've been trying to build an image that boots from a USB flash drive that has no persistence, and I've found that the .iso image serves this purpose reasonably well, if processed by isohybrid (part of

It isn't. You asked how to add custom components to a core-image, that's one way to do it, append every image involved. Whether that works for you depends on your requirements, and wasn't part of the

You need to use whatever kernel the accelerated drivers were written against. Sometimes that can be fairly recent, other times: not so much. For ARM SoCs/boards that have mali (which isn't your case,

What's the argument against requires picking up any .bbappends? I agree with the original poster - this seems only natural and would be extremely useful, not necessitating jumping through hoops like

All,

How is bbappend a core image different from bbappend foo-hwbringup-image? If you follow the original post one more generation, foo-hwbringup-image.bb "inherit core-image"

You could always define custom features for use in IMAGE_FEATURES and add them to your images via EXTRA_IMAGE_FEATURES in local.conf, or bbappend one of the core images. -- Christopher Larson clarson

I'm sorry, I posted this to the wrong list. Meant to post to u-boot list.

This is unfortunate since foo-hwbringup-image.bb is also a valid recipe. It just doesn't contain the graphics support. Is there a better way to add your custom components to "core-image" I

I have been using u-boot with CONFIG_SPI_FLASH_MTD. This has allowed me to use MTD/UBI/UBIFS with SPI flash. I now want to use CONFIG_ENV_IS_IN_UBI, but after enabling this, u-boot can't read

All, I almost have a full working setup with GDB in Eclipse for debugging remotely on my target hardware, but it's not quite there. Here's what I've done and where I'm at so far: 1. I have a custom

bbappends do not append arbitrary files, only recipes (and in this case, the inclusion treats them as an arbitrary file). They do not apply to anything included or required, only the recipe itself. So

Current Dev Position: YP 2.0 Final Next Deadline: 2.0 Cut off: Sept. 28, 2015 noon GMT SWAT team rotation: Paul -> Ross https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key

Why not printf? [geckos@csi24 ~]$ echo 1.0 | awk '{ printf("%d\n", $1); }' 1 Cheers, - dhs 2015-09-25 11:12 GMT-03:00 Dave Wolaver <davewolaver@...>: -- "Do or do not. There is no try" Yoda Master