After an exchange of messages with Richard, Saul and John Willis (he already started a layer for oe and did a good job in it) i want to announce that i started start a fork from his layer and with Flo

There are issues that cannot be solved with just one layer. A distro is a workaround but still. More about this, rpi layer will be included in yocto project repos as Richard plans so it makes sense to

For example parsing libav and rpi-zram-service will fail. We don't have libav and we don't have systemd yet in poky. @g

Or we can set up a distro file so that we can use it out of the box and in case ppl want to use custom distros use BBMASK. A pull request was sent with some other stuff as well.

Give some more output please.

Strange. I just built the kernel and worked ok for me. I will give it a try tonight.

Yes it is. Forget that. We decided to use a single layer for both distros.

https://github.com/djwillis/meta-raspberrypi Cheers! @g

Why not using branches? For example meta-ivi maintains two branches: denzil and master.

That would be a good idea in my opinion too as i tried to make doc last week and i ended up dropping this task as i didn't have the time to search for those xml deps. @g

Try to use myconfig.cfg. @g

I have Version: 2.21.53.20110810-0ubuntu5.1 and everything seems to be ok. @g

I tried now to fetch it and it works ok... @g

Cheers John, No worries about this. I will modify readme to advise the user to checkout a specific commit known as working. Good hint! Fixed and merged Definitely you are. All you need now is a git pu

It works for me. @g

Today bugzilla was realy slow. Anybody experiencing this issue? This webpage is not available Chromium could not load the webpage because bugzilla.yoctoproject.org took too long to respond. The websit

Both should work now. Denzil and master. @g

Yes. I switched to Image and things work as expected. It seems like after updating the bootloader we introduced a bug which makes a compressed kernel not boot-able. As soon as upstream will solve this

Not all images create .sdcard files. What image are you talking about? sd images are used for machines like imx / rpi where rootfs and/or kernel and/or boot-loader are used from sd. In qemu ext3 image

Anybody faced this error before and can save me from searching the roots of the problem? | 53135360 bytes (53 MB) copied, 1.21693 s, 43.7 MB/s | rm: cannot remove `<img-name>.sdimg': Value too large f