[yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi: remove not needed bundle_initramfs_append()

--- recipes-kernel/linux/linux-raspberrypi.inc | 13 - 1 file changed, 13 deletions(-) diff --git a/recipes-kernel/linux/linux-raspberrypi.inc b/recipes-kernel/linux/linux-raspberrypi.inc index 6184402..98229d9 100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++ b/recipes-ker

[yocto] [meta-raspberrypi][PATCH 0/1] linux-raspberrypi: remove not needed bundle_initramfs_append()

This append is not needed anymore and it breaks the build for the people that use initramfs, because the path to mkknlimg is wrong. Resending again because it did not make into the master. piotr.lewicki (1): linux-raspberrypi: remove not needed bundle_initramfs_append() recipes-kernel/linux

Re: [yocto] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

This error is probably caused by exiting /init script inside initramfs. Are you sure that your init script is mounting and switching root properly? You can share your init script, but I'm not sure that it's the proper list to fix that for you. BR, Piotr On 26.07.2016 12:23, Anindya Sund

Re: [yocto] changing ownership of a file in a package

s, Piotr On 25.07.2016 15:58, Leonardo Sandoval wrote: As a workaround, have you tried using the other class to include users (useradd)? Look at the 'note' of this section http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#ref-classes-extrausers Leo El 07/25/2016 a la

[yocto] changing ownership of a file in a package

Hi, I have a package where I want to install some files into a home directory of a user "testuser". I create a user in my image bb file using "extrausers". My problem is that I'm unable to change ownership of those files from root to the testuser. Simple "chown testuser:testuser -R /home/t

Re: [yocto] [meta-raspberrypi] linux-raspberrypi versions

Hi all, I also think that's a good idea. In my opinion we should at least make latest LTS (4.4) the default kernel and try to add latest mainline. Probably the "proper way" of dealing with the issue is using branches. This way (as it is in oe-core): jethro would have kernel 3.18 and 4.1, kro

Re: [yocto] customizing system configuration files in my image

It's always helpful to first check here: http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html and here: https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html But find an answer attached.. On 20.07.2016 13:41, Jörg Wittenberger wrote: Hi all, yet an

[yocto] [meta-raspberrypi] problem with building gstreamer1.0-omx

, | from ../../gst-omx-1.2.0/omx/gstomx.c:30: | /home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/sysroots/raspberrypi3/usr/include/IL/OMX_Core.h:45:4: warning: #warning OMX_SKIP64BIT is not defined - this will be incompatible with the VC GPU code. [-Wcpp] |#warning OMX_SKIP64BIT is

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: remove unbuildable task

Resending with fixed Subject. This patch removes append from do_bundle_initramfs task in linux-raspberrypi which made building kernel fail with error: | /home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.13+gitAUTOINC+680be5e27a

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: remove unbuildable task

After removing rpi-mkimage we don't have the tool mkknlimg and task do_bundle_initramfs fails with the error: | /home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.13+gitAUTOINC+680be5e27a-r0/temp/run.do_bundle_initramfs.

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: remove unbuildable task

Signed-off-by: piotr.lewicki --- recipes-kernel/linux/linux-raspberrypi.inc | 13 - 1 file changed, 13 deletions(-) diff --git a/recipes-kernel/linux/linux-raspberrypi.inc b/recipes-kernel/linux/linux-raspberrypi.inc index 6184402..98229d9 100644 --- a/recipes-kernel/linux/linux

[yocto] [meta-raspberrypi][PATCH 00/01] Fix bundling initramfs to kernel

Fixes error: | /home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.13+gitAUTOINC+680be5e27a-r0/temp/run.do_bundle_initramfs.19144: 152: /home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux

Re: [yocto] NTP

I am new to Yocto, so please explain a bit more. Not all of the recipes can be found in poky layers. You can use multiple layers together to be able to access more recipes (and features like bbclasses, etc.). You will find more info in the manual. All I have done is: git clone -b krogoth gi

Re: [yocto] NTP

On 17.06.2016 08:33, Anicic Damir (PSI) wrote: Hi! I just realised that ntpd + ntpdate is not part of Yocto 2.1 What do you mean by "not part of Yocto"? I found http://layers.openembedded.org/layerindex/recipe/2299/ but how to get

Re: [yocto] Script being installed under /etc/init.d instead of /usr/lib/systemd folder

Take a look at example from my some-recipe.bb : inherit systemd SYSTEMD_SERVICE_${PN} = "some-recipe.service" do_install_append () { install -d ${D}${systemd_unitdir}/system install -m 0644 ${S}/configs/some-recipe.service ${D}${systemd_unitdir}/system } First in your recipe inherit

Re: [yocto] Customization for nginx

This is not an answer to your question but it can be helpful: You can use a wildcard for version in your bbappend file. If you rename it to: nginx_1.9.%.bbappend this will work for both 1.9.5 and 1.9.14. For debugging I can give you a hint: try using "-v" switch for bitbake when baking your ngi

Re: [yocto] DISTRO_FEATURES modification from image recipe?

On 7 June 2016 at 13:10, piotr.lewicki <mailto:piotr.lewi...@elfin.de>> wrote: Is it possible to manipulate DISTRO_FEATURES from my image recipe file? No. You should control distro features in your distro configuration or if they're for local tweaking in your local.conf.

[yocto] DISTRO_FEATURES modification from image recipe?

Hi, Is it possible to manipulate DISTRO_FEATURES from my image recipe file? In my case I added line: DISTRO_FEATURES += " systemd" to local.conf and it worked (added systemd), but when I moved this line to my image.bb recipe I got build errors: ERROR: Required build target 'my-image' has no b

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

Burton has modified the original one to use oe.path.join() when committing it] To be more specific, I will most likely start by fixing gst-omx (which currently wants to use userland on RPI), then go for omxplayer. Herve -Original Message- From: piotr.lewicki [mailto:piotr.lewi...@elfin.de

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

pi][PATCH 0/8] Support for vc4 graphics driver"? Patch for mesa is part of those patches above? I'll take a look at the omxplayer issue as soon as I can, in the meanwhile I recommend to not use it... This would be great. Thank you. Herve -Original Message- From: piotr.lewicki

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

1 | make: *** [OMXPlayerVideo.o] Error 1 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /home/piotr.lewicki/yocto-raspberry/pi3-16.05.19/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_compile.6167) ERROR: Task 928 (/hom

Re: [yocto] [meta-raspberrypi][Question] How to build an hwup image for raspberrypi3

On 19.05.2016 16:39, Andrei Gherzan wrote: On Thu, May 19, 2016 at 02:15:22PM +0200, piotr.lewicki wrote: Hello, I'm trying to build a Yocto image for raspberrypi3. I'm using only two layers: - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842) - meta-raspberrypi (m

[yocto] [meta-raspberrypi][Question] How to build an hwup image for raspberrypi3

Hello, I'm trying to build a Yocto image for raspberrypi3. I'm using only two layers: - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842) - meta-raspberrypi (master: rev 9912d38e97671704822d1aa05312a0439cb650d3) I have built it by cloning both layers from git (and changing poky branch

Re: [yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9

atch to OE-Core mailing list. and also add Upstream-Status: to patch I don't see a "why" anywhere. Something wrong with libav, something better with ffmpeg, etc? libav was replaced in OE-core by ffmpeg On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki

[yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9

--- .../omxplayer/explicitly_link_with_vchostif_library.patch | 13 + recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++-- 2 files changed, 16 insertions(+), 2 deletions(-) create mode 100644 recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_li