from:"piotr.lewicki"

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

2016-11-02 Thread 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-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -54,16 +54,3 @@ do_deploy_append() {
 fi
 echo "${CMDLINE}${PITFT_PARAMS}" > 
${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
 }
-
-do_bundle_initramfs_append() {
-if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
-if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
-if test -n "${KERNEL_DEVICETREE}"; then
-# Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
-for type in ${KERNEL_IMAGETYPES} ; do
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
-done
-fi
-fi
-fi
-}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-11-02 Thread piotr.lewicki

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/linux-raspberrypi.inc | 13 -
 1 file changed, 13 deletions(-)

-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-26 Thread piotr.lewicki


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 Sundar Gayen wrote:


Hi,


I am trying to build Yocto for my custom FPGA board. I added the 
meta-bsp layer. But after successful building of Yocto I am getting 
"Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00". Kernel log mentioned below.



I am using Yocto version dizzy and the same rfs is working fine with 
phycore Vybrid board because both (Vybrid & my custom FPGA) are using 
cortex-A5. I am compiling my Linux kernel externally using poky 
toolchain because I need to make it initramfs. Phycore Vybrid board is 
using Linux kernel version 3.0.15 and for my custom FPGA board it is 
4.6. It seems to be noticed that 4.6 Linux kernel with openWRT is 
perfectly running whenever I am creating that also as initramfs for my 
custom FPGA.



So, please let me know how to resolve it.


*LOG:~*


[   10.16] console [ttyS0] enabled
[   10.16] console [ttyS0] enabled
[   10.17] bootconsole [earlycon0] disabled
[   10.17] bootconsole [earlycon0] disabled
[   10.38] Warning: unable to open an initial console.
[   10.39] devtmpfs: mounted
[   12.13] Freeing unused kernel memory: 4648K (2022e000 - 206b8000)
[   12.14] This architecture does not have kernel memory protection.
[   12.32] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00

[   12.32]
[   12.32] Rebooting in 5 seconds..Reboot failed -- System halted


*Thanks & regards,
Anindya Sundar Gayen
Contact | 7842753740*




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-25 Thread piotr.lewicki

Thank you. I will try this, but I wonder what is the right way of 
dealing with that when I want to change the ownership of let's say 2 
files from different packages to a user that I create?


Is using "useradd" possible in 2 separate recipes (to create the same user)?



Thanks,

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 las 07:22 AM, piotr.lewicki escribió:

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/testuser" inside do_install 
task makes those files being owned by "nobody".


How can I manage ownership of those files properly?



The recipe is like so:

DESCRIPTION = "Files installed in testuser user home directory"
LICENSE = "CLOSED"

SRC_URI += " \
   file://authorized_keys \
   file://bash_profile \
   file://bashrc \
   "

do_install(){
install -d ${D}/home/testuser/
install -m 0644 ${WORKDIR}/bash_profile 
${D}/home/testuser/.bash_profile

install -m 0644 ${WORKDIR}/bashrc ${D}/home/testuser/.bashrc

install -d ${D}/home/testuser/.ssh
install -m 0644 ${WORKDIR}/authorized_keys ${D}/home/testuser/.ssh/
}

FILES_${PN} = "/home/testuser"


Thanks,

Piotr





--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] changing ownership of a file in a package

2016-07-25 Thread piotr.lewicki


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/testuser" inside do_install 
task makes those files being owned by "nobody".


How can I manage ownership of those files properly?



The recipe is like so:

DESCRIPTION = "Files installed in testuser user home directory"
LICENSE = "CLOSED"

SRC_URI += " \
   file://authorized_keys \
   file://bash_profile \
   file://bashrc \
   "

do_install(){
install -d ${D}/home/testuser/
install -m 0644 ${WORKDIR}/bash_profile 
${D}/home/testuser/.bash_profile

install -m 0644 ${WORKDIR}/bashrc ${D}/home/testuser/.bashrc

install -d ${D}/home/testuser/.ssh
install -m 0644 ${WORKDIR}/authorized_keys ${D}/home/testuser/.ssh/
}

FILES_${PN} = "/home/testuser"


Thanks,

Piotr

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-22 Thread piotr.lewicki


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, 
krogoth would have 4.4 and 4.1 and master would only have 4.4 and latest 
mainline.


Don't you think that it would be a good idea to create some "quasi" 
krogoth branch out of what is on master and then cleaning the master 
(e.g. removing kernel 3.18 and 4.1) ?



BR,

Piotr


On 21.07.2016 17:39, Herve Jourdain wrote:

Hi Paul,

I had the same line of thoughts...
I believe 3.18 should be dropped, maybe even 4.1, default to 4.4, and maybe
add 4.7 to the mix, since 4.7 seems to be where the bulk of the work is done
now.

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Paul Barker
Sent: jeudi 21 juillet 2016 09:03
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi] linux-raspberrypi versions

Hi all,

I'm planning to look at the linux-raspberypi recipes once I've had time to
send V2 of my u-boot patches. I'd like to know people's thoughts on the
available kernel versions in the meta-raspberrypi layer:

Is anyone still using the linux-raspberrypi 3.18 recipe? The commit
referenced in SRCREV is from June 2015. I think it's probably time to retire
this unless anyone has a reason to keep it around.

Is there any reason to keep linux-raspberrypi 4.1 as the default recipe? The
last commit to the 4.1 branch was in April and the default branch on the
linux-raspberrypi GitHub repository has been
4.4 since then. I think we should change the default version to 4.4 unless
there's a good reason not to.

If there's no objections I'll send a couple of patches to drop 3.18 and
change the default to 4.4.

Thanks,
Paul Barker
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-20 Thread piotr.lewicki

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 another newbie here stumbling around…

I’m not trying to find „any way“ to do what I need.  I’m trying to 
learn how these thing sould be done in yocto.  Looks to mea s if I’m 
missing something basic.

Zhenhua Lu wrote:

> Usually I do it by adding bbappend of corresponding packages to 
override original files, the interfaces is provided by init-ifupdown, 
the inittab is provided by sysvinit-inittab.

>

> An example: 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/recipes-core/init-ifupdown

I failed trying to follow this example.

I  have this samba_4.%.bbappend :

FILESEXTRAPATHS_prepend := "${THISDIR}/iris:"

You should add a line
SRC_URI += "file://smb.conf"
that will copy a file from your "${THISDIR}/iris:" to ${WORKDIR}
and then..

do_install_append() {

install -m644 iris/smb.conf ${D}${sysconfdir}/samba/smb.conf

}

..install this with "install -m 0644 ${WORKDIR}/smb.conf 
${D}${sysconfdir}/samba/smb.conf"

Also make sure that you have a directory ${D}${sysconfdir}/samba by 
adding the line:

install -d ${D}${sysconfdir}/samba

And in the same directory a subdirectory „iris“ which contrains the 
„smb.conf“ I want to install.

Does not work.  Using `bitbake -c devshell samba` I found no copy of 
my „iris“ directory.

Thanks so much.

/Jörg

BR,
Piotr

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-20 Thread piotr.lewicki


Hi,

After recent update of meta-raspberrypi I have a problem with building 
gstreamer1.0-omx package.


I have one strange warning and one error due to missing gstglmemoryegl.h 
file (marked with pluses below):


| In file included from ../../gst-omx-1.2.0/omx/gstomx.h:48:0,
|  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 not defined - this will be 
incompatible with the VC GPU code.

| ^
| ../../gst-omx-1.2.0/omx/gstomxvideodec.c:41:39: fatal error: 
gst/gl/egl/gstglmemoryegl.h: No such file or directory

| compilation terminated.
| make[2]: *** [libgstomx_la-gstomxvideodec.lo] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory 
`/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/build/omx'

| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory 
`/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/build'

| make: *** [all] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-poky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/temp/log.do_compile.4424)
ERROR: Task 
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/../layers/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bb:do_compile 
(/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/../layers/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bb:do_compile) 
failed with exit code '1'



Do you have any idea why I have those messages?

I use gstreamer1.0 1.8.2 and corresponding plugin versions.

I have noticed that after removing 
file://0007-omxvideodec-Use-gstglmemoryegl-for-the-RPi.patch from 
gstreamer1.0-omx_1.2.0.bbappend - the package builds..


Any hint why I don't have this gstglmemoryegl.h header?


Thanks,

Piotr

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-20 Thread piotr.lewicki

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.19144: 
152: 
/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: 
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/sysroots/x86_64-linux/usr/bin/mkknlimg: 
not found

| WARNING: exit code 127 from a shell command.
| ERROR: Function failed: do_bundle_initramfs (log file is located at 
/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/log.do_bundle_initramfs.19144)


Removing this append fixes this behaviour.

I have tested that with kernel 4.4.13.


Unfortunately I don't know how this behaves with older kernels (3.18 and 
4.1)



BR,

Piotr


On 20.07.2016 11:31, piotr.lewicki wrote:

Signed-off-by: piotr.lewicki <piotr.lewi...@elfin.de>
---
  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-kernel/linux/linux-raspberrypi.inc
@@ -54,16 +54,3 @@ do_deploy_append() {
  fi
  echo "${CMDLINE}${PITFT_PARAMS}" > 
${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
  }
-
-do_bundle_initramfs_append() {
-if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
-if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
-if test -n "${KERNEL_DEVICETREE}"; then
-# Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
-for type in ${KERNEL_IMAGETYPES} ; do
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
-done
-fi
-fi
-fi
-}


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-20 Thread piotr.lewicki

Signed-off-by: piotr.lewicki <piotr.lewi...@elfin.de>
---
 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-kernel/linux/linux-raspberrypi.inc
@@ -54,16 +54,3 @@ do_deploy_append() {
 fi
 echo "${CMDLINE}${PITFT_PARAMS}" > 
${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
 }
-
-do_bundle_initramfs_append() {
-if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
-if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
-if test -n "${KERNEL_DEVICETREE}"; then
-# Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
-for type in ${KERNEL_IMAGETYPES} ; do
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
-done
-fi
-fi
-fi
-}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-07-20 Thread piotr.lewicki


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-gnueabi/linux-raspberrypi/1_4.4.13+gitAUTOINC+680be5e27a-r0/temp/run.do_bundle_initramfs.19144:
 
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/sysroots/x86_64-linux/usr/bin/mkknlimg:
 not found
| WARNING: exit code 127 from a shell command.
| ERROR: Function failed: do_bundle_initramfs (log file is located at 
/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/log.do_bundle_initramfs.19144)

After removing rpi-mkimage from the layer tool mkknlimg is not available (and 
not needed with kernels 4.4+).
To fix execution of do_bundle_initramfs task I have removed lines appended to 
this task in linux-raspberrypi.inc.

Tested with kernel 4.4.13.

Unfortunately I don't know how this works with older kernels (3.18 and 4.1) but 
since we don't have mkknlimg anymore-
bundling initramfs should also fail there.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] NTP

2016-06-17 Thread piotr.lewicki


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 git://git.yoctoproject.org/poky.git

How do I now add layers ?

http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#enabling-your-layer
You will find the whole manual quite useful.


Or can I somehow clone Yocto 2.1 with all layers ?

I don't think that's possible.


Damir



Best regards,
Piotr Lewicki
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] NTP

2016-06-17 Thread piotr.lewicki




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 it?
You need to add a layer "meta-networking" which is a part of 
"meta-openembedded" and the recipe is there at 
meta-openembedded/meta-networking/recipes-support/ntp

Link: http://cgit.openembedded.org/meta-openembedded/

Best Regards
Piotr Lewicki
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-06-14 Thread piotr.lewicki


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 from "systemd".
Then install your systemd service file in 
"${D}${systemd_unitdir}/system" (there is also a variable for this 
directory, I think it's ${systemd_system_unitdir} or something similar).

Remember to create a directory before placing a file there.

In the last step use "SYSTEMD_SERVICE_${PN}" where you specify systemd 
services that should be run.


I hope that helps..

Best regards,
Piotr Lewicki


On 09.06.2016 03:11, Dey, Megha wrote:


Hi,

I am trying to use the systemd init system from the existing system. I 
have added the following to my conf file:


DISTRO_FEATURES_append = " systemd"

VIRTUAL-RUNTIME_init_manager = "systemd"

VIRTUAL-RUNTIME_initscripts = ""

DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"

I have also added the ‘systemd’ binary to the INSTALL_APPEND.

When I boot the resulting image, I do see systemd up and running and I 
am able to start and stop services.


However, I do have a script recipe which is currently placed as a 
bbappend to initscripts 
(meta/recipes-core/initscripts/initscript_..bb) in my custom meta layer.


This script even after shifting to systemd, is being placed in the 
/etc/init.d/ folder, and hence doesn’t run on boot. I want this to be 
placed in the /usr/lib/system.d/ folder instead. How would I be able 
to do this?


Is it because this script is an append to initscripts, it by default 
gets installed under /etc/init.d? If so, where should I place the recipe?


Thanks,

Megha





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Customization for nginx

2016-06-14 Thread piotr.lewicki


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 nginx recipe- this 
stands for "verbose".


Best regards,
Piotr Lewicki

On 14.06.2016 09:15, Elias Diem wrote:

Hi

With jethro, I used to use the following .bbappend to use
my config for nginx:


FILESEXTRAPATHS_prepend := "${THISDIR}/files:"



My nginx.conf was inside the corresponding files directory.

Since krogoth, which uses nginx 1.9.14, this does not seem to work any 
more. My config file is not used any more. The .bbappend file how has 
the name nginx_1.9.14.bbappend of course.


What could be the reason for this?

Or, alternatively: where can I debug this?




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] DISTRO_FEATURES modification from image recipe?

2016-06-08 Thread piotr.lewicki


Thanks.
I actually want to enable systemd in all packages, but my current DISTRO 
is "poky".
Can you point me some documentation where I can get information on how 
to create a distro file based on poky and add systemd there?


Thanks,
Piotr

On 07.06.2016 15:53, Burton, Ross wrote:


On 7 June 2016 at 13:10, piotr.lewicki <piotr.lewi...@elfin.de 
<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.  Would it be 
helpful if you explained why you want to enable systemd in some images 
but not others?  In this case the systemd feature isn't exclusive with 
sysvinit, you can enable both and pick on a per-image basis what init 
system is used.


Ross


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] DISTRO_FEATURES modification from image recipe?

2016-06-07 Thread piotr.lewicki


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 buildable providers.
Missing or unbuildable dependency chain was: ['my-image', 'my-app', 
'systemd']


I already have in my image recipe line:
DISTRO_FEATURES_append = " gles2"
so I tried to add systemd to it like so:
DISTRO_FEATURES_append = " gles2 systemd"
but it didn't help.

Can you help a me?
What should I put and where to enable distro-feature: systemd without 
manipulating with local.conf? Is that possible?



Thanks
Piotr Lewicki
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-05-24 Thread piotr.lewicki

So I understand that 1 and 2 should be applied and 3rd is already merged 
into master (of poky).

I cannot wait to for your fixes for gst-omx and later omxplayer.

Thanks,
Piotr

On 24.05.2016 14:06, Herve Jourdain wrote:

Hi Piotr,

Please make sure you have the latest series, the 02 was modified actually,
and is different from what you have.
If meta-raspberrypi was changed since I sent the patch, then there might be
some need to rebase it. Dear list, do you need me to send a v3 taking into
account the latest modifications of the meta-raspberrypi master, if any?
The other patch threads, that are needed, are:
1. [yocto][meta-raspberrypi][PATCH v3 0/5] Support for .dtbo files for dtb
overlays, required by kernels 4.4.6+
2. [yocto][PATCH v2 0/1] Support for .dtbo files for dtb overlays
3. [OE-core][mesa][PATCH v2 0/1] Fix mesa_populate_packages() when dri is
disabled [I believe Ross 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]
Sent: mardi 24 mai 2016 13:08
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4
graphics driver

On 24.05.2016 12:42, Herve Jourdain wrote:

Hi Piotr,

Hi,
There were issues with patches 02, 07 and 12.
02- due to different overlay naming (overlays/vc4-kms-v3d-overlay.dtb
instead of overlays/vc4-kms-v3d.dtbo) and 07 and 12 due to bump of
linux-raspberrypi from 4.4.8 to 4.4.9 (on master).

I know that the omxplayer would not build at this time, because VC4
and userland will conflict, and currently omxplayer depends on userland.
I will check if it can be supported with VC4 driver enabled, but for
the moment it's true I disabled it in my build.

Regarding your patches:
1. Are you using linux kernel 4.4? You should set
PREFERRED_VERSION_linux-raspberrypi = "4.4.%" somewhere, either in
your distro configuration file, or your local.conf.
  If you do so, it should get kernel 4.4.10, which requires .dtbo
files for overlay. As mentioned in the patch, support for VC4 in 4.1
is not stable, and therefore not supported.

I did that :-)

2. I've seen only one TODO, did you make only one modification?

There were issues with patches 02, 07 and 12.
02- due to different overlay naming (overlays/vc4-kms-v3d-overlay.dtb
instead of overlays/vc4-kms-v3d.dtbo) and 07 and 12 due to bump of
linux-raspberrypi from 4.4.8 to 4.4.9 (on master).

Now I see that 02 whas not necessary- I just missed the patch you provided
earlier.

3. There are other patches that are needed to be applied, before this
patch series is applied: 2 for .dtbo support (1 in meta-raspberrypi, 1
in meta), 1 for mesa (to allow packaging with empty DRI).

Ok. I didn't know. Can you confirm that I have the right patches?
Patch for meta is from thread "[yocto] [PATCH v2 0/1] Support for .dtbo
files for dtb overlays"?
Patch for meta-raspberrypi is "[yocto] [meta-raspberrypi][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 [mailto:piotr.lewi...@elfin.de]
Sent: mardi 24 mai 2016 11:59
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for
VC4 graphics driver

I have tried these patches, but there were some hunks and errors
during applying to current master revision
(69840c0bbe03c2e61601e2377c8e2adc264e0478).
Building 'rpi-hwup-image' passed, but while building 'rpi-test-image'
(omxplayer recipe) I have noticed some errors due to missing files:
- IL/OMX_Core.h
- VG/openvg.h
- bcm_host.h

I'm attaching omxplayer_build_errors.txt with build log and my patch
with changes created by Herve (adapted to current master revision) -
Support_for_VC4_graphics_driver.patch (Herve- if you decide to use
that and resend v3 of patches - please remove my TODO from
"conf/machine/include/rpi-base.inc"

Could you take a look at that and help me resolve those issues?


I currently have a problem that I'm forced to use Raspbian because
playing FHD/1080p videos with omxplayer from Yocto runs choppy (I'm
not sure if that's the right word, but playback is not smooth) while
with Raspbian it works perfect.
Do you think that enabling VC4 graphics driver can solve my issue?
Did any of you experienced similar problems? Do you have some other
solution or do you know what's the cause of this?


Thanks,
Piotr Lewicki


On 20.05.2016 13:51, Herve Jourdain wrote:

This v2 series addresses the following issues with the first series:
a. Fix the 4.4.10 kernel revision
b. Effecti

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

2016-05-24 Thread piotr.lewicki


On 24.05.2016 12:42, Herve Jourdain wrote:

Hi Piotr,

Hi,
There were issues with patches 02, 07 and 12.
02- due to different overlay naming (overlays/vc4-kms-v3d-overlay.dtb 
instead of overlays/vc4-kms-v3d.dtbo) and 07 and 12 due to bump of 
linux-raspberrypi from 4.4.8 to 4.4.9 (on master).

I know that the omxplayer would not build at this time, because VC4 and
userland will conflict, and currently omxplayer depends on userland.
I will check if it can be supported with VC4 driver enabled, but for the
moment it's true I disabled it in my build.

Regarding your patches:
1. Are you using linux kernel 4.4? You should set
PREFERRED_VERSION_linux-raspberrypi = "4.4.%" somewhere, either in your
distro configuration file, or your local.conf.
 If you do so, it should get kernel 4.4.10, which requires .dtbo files
for overlay. As mentioned in the patch, support for VC4 in 4.1 is not
stable, and therefore not supported.

I did that :-)

2. I've seen only one TODO, did you make only one modification?

There were issues with patches 02, 07 and 12.
02- due to different overlay naming (overlays/vc4-kms-v3d-overlay.dtb 
instead of overlays/vc4-kms-v3d.dtbo) and 07 and 12 due to bump of 
linux-raspberrypi from 4.4.8 to 4.4.9 (on master).


Now I see that 02 whas not necessary- I just missed the patch you 
provided earlier.

3. There are other patches that are needed to be applied, before this patch
series is applied: 2 for .dtbo support (1 in meta-raspberrypi, 1 in meta), 1
for mesa (to allow packaging with empty DRI).

Ok. I didn't know. Can you confirm that I have the right patches?
Patch for meta is from thread "[yocto] [PATCH v2 0/1] Support for .dtbo 
files for dtb overlays"?
Patch for meta-raspberrypi is "[yocto] [meta-raspberrypi][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 [mailto:piotr.lewi...@elfin.de]
Sent: mardi 24 mai 2016 11:59
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4
graphics driver

I have tried these patches, but there were some hunks and errors during
applying to current master revision
(69840c0bbe03c2e61601e2377c8e2adc264e0478).
Building 'rpi-hwup-image' passed, but while building 'rpi-test-image'
(omxplayer recipe) I have noticed some errors due to missing files:
- IL/OMX_Core.h
- VG/openvg.h
- bcm_host.h

I'm attaching omxplayer_build_errors.txt with build log and my patch with
changes created by Herve (adapted to current master revision) -
Support_for_VC4_graphics_driver.patch (Herve- if you decide to use that and
resend v3 of patches - please remove my TODO from
"conf/machine/include/rpi-base.inc"

Could you take a look at that and help me resolve those issues?


I currently have a problem that I'm forced to use Raspbian because playing
FHD/1080p videos with omxplayer from Yocto runs choppy (I'm not sure if
that's the right word, but playback is not smooth) while with Raspbian it
works perfect.
Do you think that enabling VC4 graphics driver can solve my issue?
Did any of you experienced similar problems? Do you have some other solution
or do you know what's the cause of this?


Thanks,
Piotr Lewicki


On 20.05.2016 13:51, Herve Jourdain wrote:

This v2 series addresses the following issues with the first series:
a. Fix the 4.4.10 kernel revision
b. Effectively add vc4-kms-v3d overlay to the list of overlays to
build (forgotten previously) c. Make the parameter to the v4c-kms-v3d
overlay configurable d. Add default values for the cma parameter to
the v4c-kms-v3d overlay, depending on the board (and the memory it
has)

This patch series enables the support for the VC4 graphics driver from

Eric Anholt.

There was a previous patch series by Javier Martinez Canillas, but it

required use of a different kernel.

VC4 is now supported in the raspberrypi official kernel, at least for

4.4.9+.

The support in 4.1 exists, but it is NOT STABLE, so it has been deemed

unreasonable to support VC4 with 4.1 kernels.

THEREFORE, VC4 graphics is supported ONLY for kernel versions 4.4.9 and

later.

This patch series proposes to support VC4 by only adding 'vc4graphics' to

MACHINE_FEATURES, for raspberrypi. If this is set, it will trigger all the
necessary configuration/changes to use the VC4 driver, including
mesa/wayland/weston currently, and adding the overlay required.

In order for this series to work, some previous patches are needed

(support for .dtbo, and fix of the mesa packaging when there is no DRI
driver).

The memory reserved for the VC4 driver has default values depending on the

version of the board used, but it can be configured by setting VC4_CMA_SIZE
to a value supported by the overlay ('cma-256', 'cma-1

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

2016-05-24 Thread piotr.lewicki

es changed, 49 insertions(+), 19 deletions(-)
  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend



| In file included from linux/RBP.h:45:0,
|  from linux/RBP.cpp:22:
| ./DllBCM.h:34:22: fatal error: bcm_host.h: No such file or directory
| compilation terminated.
| make: *** [linux/RBP.o] Error 1
| make: *** Waiting for unfinished jobs
| In file included from SubtitleRenderer.cpp:27:0:
| SubtitleRenderer.h:30:23: fatal error: VG/openvg.h: No such file or directory
| compilation terminated.
| make: *** [SubtitleRenderer.o] Error 1
| In file included from OMXCore.h:32:0,
|  from OMXVideo.h:25,
|  from OMXVideo.cpp:28:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| make: *** [OMXVideo.o] Error 1
| In file included from OMXCore.h:32:0,
|  from OMXCore.cpp:31:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| make: *** [OMXCore.o] Error 1
| In file included from OMXCore.h:32:0,
|  from OMXAudio.h:34,
|  from OMXAudio.cpp:27:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| make: *** [OMXAudio.o] Error 1
| In file included from OMXCore.h:32:0,
|  from OMXClock.h:27,
|  from OMXReader.cpp:29:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| In file included from OMXCore.h:32:0,
|  from OMXClock.h:27,
|  from OMXPlayerAudio.h:32,
|  from OMXPlayerAudio.cpp:28:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| In file included from OMXCore.h:32:0,
|  from OMXClock.h:27,
|  from OMXClock.cpp:32:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| In file included from OMXCore.h:32:0,
|  from OMXClock.h:27,
|  from OMXPlayerSubtitles.h:23,
|  from OMXPlayerSubtitles.cpp:19:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| In file included from OMXCore.h:32:0,
|  from OMXClock.h:27,
|  from OMXPlayerVideo.h:30,
|  from OMXPlayerVideo.cpp:28:
| DllOMX.h:36:25: fatal error: IL/OMX_Core.h: No such file or directory
| compilation terminated.
| make: *** [OMXReader.o] Error 1
| make: *** [OMXPlayerAudio.o] Error 1
| make: *** [OMXClock.o] Error 1
| make: *** [OMXPlayerSubtitles.o] Error 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 
(/home/piotr.lewicki/yocto-raspberry/pi3-16.05.19/layers/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer_git.bb,
 do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3680 tasks of which 3639 didn't need to be rerun 
and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  
/home/piotr.lewicki/yocto-raspberry/pi3-16.05.19/layers/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer_git.bb,
 do_compile
  Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
index 56ca83e..21bf9c0 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,7 +37,9 @@ KERNEL_DEVICETREE ?= " \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
 overlays/pi3-miniuart-bt-overlay.dtb \
+overlays/vc4-kms-v3d-overlay.dtb \
 "
+# TODO line with overlays/vc4-kms-v3d.dtbo : decide whether it is .dtb or .dtbo
 KERNEL_IMAGETYPE ?= "Image"
 
 MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen alsa bluetooth wifi sdio"
diff --git a/conf/machine/include/rpi-default-providers.inc b/conf/machine/include/rpi-default-providers.inc
index cabbd43..0bc8838 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -3,8 +3,8 @@
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
 PREFERRED_PROVIDER_u-boot ?= "u-boot-rpi"
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
-PREFERRED_PROVIDER_virtual/egl ?= "userland"
-PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
-PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
+PREFERRED_PROVIDER_virtual/egl ?= "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "userland", d)}&q

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

2016-05-19 Thread piotr.lewicki


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), then I sourced poky (source poky/oe-init-build-env), added 
meta-raspberrypi layer in conf/bblayers.conf and in conf/local.conf 
changed MACHINE to raspberrypi3.


Then I have built "rpi-hwup-image" using bitbake and dd'd it to an SD card.

Unfortunately rpi-hwup-image does not work on raspberry pi 3.
Boot screen halts when 4 raspberry logos show up and that's it.

On the other hand I have tried the same SD card with raspberry pi 2 and 
it booted up (!?).


Can you tell me if there is still support for meta-raspberrypi layer?
I found that this layer does not follow Yocto project naming convention 
for branches (I think that the latest is "jethro", but nothing newer 
besides "master").
Does this mean that there is no stable and up-to-date branch apart from 
master?


Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?


Thanks,
Piotr Lewicki
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-04-22 Thread piotr.lewicki


Hello.
I'm new here and I didn't know how to prepare patch correctly- I just 
used instructions from meta-raspberrypi README.


I can resend it if you want. Especially now when the patch is not 
necessary anymore, because Andrei Gherzan has merged latest revision of 
omxplayer to master (patch with explicit linking vchostif lib was taken 
from there).


Please provide me with instruction on how to create a patch properly.

Thank you,
Piotr Lewicki

On 22.04.2016 05:01, Gary Thomas wrote:

On 2016-04-22 02:44, Mark Hatle wrote:

On 4/21/16 6:31 PM, Khem Raj wrote:

resend this patch 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 
<piotr.lewi...@elfin.de> wrote:

---
.../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_library.patch


diff --git 
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch 
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch 


new file mode 100644
index 000..642f63a
--- /dev/null
+++ 
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch

@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
 b/Makefile
+@@ -51,7 +51,7 @@ version:
+   bash gen_version.sh > version.h
+
+ omxplayer.bin: version $(OBJS)
+-  $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm 
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat 
-lswscale -lswresample -lpcre
++  $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm 
-lvchostif -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec 
-lavformat -lswscale -lswresample -lpcre

+   $(STRIP) omxplayer.bin
+
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb

index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
  LICENSE = "GPLv2"
  LIC_FILES_CHKSUM = 
"file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"


-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl 
samba libssh"

-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl 
samba libssh"

+PR = "r5"

  SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
  SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master 
\
@@ -19,6 +19,7 @@ SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master

 file://fix-tar-command-with-DIST.patch \
 file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+ file://explicitly_link_with_vchostif_library.patch \
 "
  S = "${WORKDIR}/git"

--
2.5.0

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto







--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2016-04-21 Thread piotr.lewicki

---
 .../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_library.patch

diff --git 
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
 
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
new file mode 100644
index 000..642f63a
--- /dev/null
+++ 
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
 b/Makefile
+@@ -51,7 +51,7 @@ version:
+   bash gen_version.sh > version.h 
+ 
+ omxplayer.bin: version $(OBJS)
+-  $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos -ldbus-1 
-lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample -lpcre
++  $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif 
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale 
-lswresample -lpcre
+   $(STRIP) omxplayer.bin
+ 
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh"
-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba libssh"
+PR = "r5"
 
 SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
 SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
@@ -19,6 +19,7 @@ SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+   file://explicitly_link_with_vchostif_library.patch \
"
 S = "${WORKDIR}/git"
 
-- 
2.5.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

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

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

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

[yocto] changing ownership of a file in a package

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

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

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

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

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

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

Re: [yocto] NTP

Re: [yocto] NTP

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

Re: [yocto] Customization for nginx

Re: [yocto] DISTRO_FEATURES modification from image recipe?

[yocto] DISTRO_FEATURES modification from image recipe?

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

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

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

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

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

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

23 matches

Site Navigation

Mail list logo

Footer information