Re: [yocto] [PATCH 1/2] packagegroup-rpi-test: Poky moved the license so fix LIC_FILES_CHKSUM
On Wed, Jun 15, 2016 at 12:50:19AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan
> ---
> recipes-core/packagegroups/packagegroup-rpi-test.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb
> b/recipes-core/packagegroups/packagegroup-rpi-test.bb
> index ae16cec..a47aeb2 100644
> --- a/recipes-core/packagegroups/packagegroup-rpi-test.bb
> +++ b/recipes-core/packagegroups/packagegroup-rpi-test.bb
> @@ -1,6 +1,6 @@
> DESCRIPTION = "RaspberryPi Test Packagegroup"
> LICENSE = "MIT"
> -LIC_FILES_CHKSUM =
> "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58"
> +LIC_FILES_CHKSUM =
> "file://${COREBASE}/meta/COPYING.MIT;md5=3f40d7994397109285ec7b81fdeb3b58"
>
> inherit packagegroup
>
> --
> 2.8.2
>
Merged to master.
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/2] linux-raspberrypi: Fix v4.1 with GCC6
On Wed, Jun 15, 2016 at 12:50:20AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan
> ---
> ...ove-unused-sm_cache_map_vector-definition.patch | 31 +
> .../linux-raspberrypi-4.1/0003-fix-gcc6.patch | 78
> ++
> recipes-kernel/linux/linux-raspberrypi_4.1.bb | 2 +
> 3 files changed, 111 insertions(+)
> create mode 100644
> recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> create mode 100644
> recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
>
> diff --git
> a/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
>
> b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> new file mode 100644
> index 000..8d4a900
> --- /dev/null
> +++
> b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> @@ -0,0 +1,31 @@
> +The code using it also ifdef'ed with 0, anyyd gcc 6
> +complains
> +
> +error: 'sm_cache_map_vector' defined but not used
> +
> +The code using it also ifdef'ed out
> +
> +Upstream-status: Denied [https://github.com/raspberrypi/linux/pull/1528]
> +
> +Signed-off-by: Khem Raj
> +---
> + drivers/char/broadcom/vc_sm/vmcs_sm.c | 2 ++
> + 1 file changed, 2 insertions(+)
> +
> +--- a/drivers/char/broadcom/vc_sm/vmcs_sm.c
> b/drivers/char/broadcom/vc_sm/vmcs_sm.c
> +@@ -197,12 +197,14 @@ struct SM_STATE_T {
> + static struct SM_STATE_T *sm_state;
> + static int sm_inited;
> +
> ++#if 0
> + static const char *const sm_cache_map_vector[] = {
> + "(null)",
> + "host",
> + "videocore",
> + "host+videocore",
> + };
> ++#endif
> +
> + /* Private Function Prototypes --
> */
> +
> diff --git a/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> b/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> new file mode 100644
> index 000..61ec2fb
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> @@ -0,0 +1,78 @@
> +Fix compile with GCC6
> +
> +Upstream-status: Denied [https://github.com/raspberrypi/linux/pull/1528]
> +
> +Signed-off-by: Andrei Gherzan
> +
> +Index: source/include/linux/compiler-gcc6.h
> +===
> +--- /dev/null
> source/include/linux/compiler-gcc6.h
> +@@ -0,0 +1,67 @@
> ++#ifndef __LINUX_COMPILER_H
> ++#error "Please don't include directly, include
> instead."
> ++#endif
> ++
> ++#define __used __attribute__((__used__))
> ++#define __must_check
> __attribute__((warn_unused_result))
> ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b)
> ++
> ++/* Mark functions as cold. gcc will assume any path leading to a call
> ++ to them will be unlikely. This means a lot of manual unlikely()s
> ++ are unnecessary now for any paths leading to the usual suspects
> ++ like BUG(), printk(), panic() etc. [but let's keep them for now for
> ++ older compilers]
> ++
> ++ Early snapshots of gcc 4.3 don't support this and we can't detect this
> ++ in the preprocessor, but we can live with this because they're
> unreleased.
> ++ Maketime probing would be overkill here.
> ++
> ++ gcc also has a __attribute__((__hot__)) to move hot functions into
> ++ a special section, but I don't see any sense in this right now in
> ++ the kernel context */
> ++#define __cold __attribute__((__cold__))
> ++
> ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix),
> __COUNTER__)
> ++
> ++#ifndef __CHECKER__
> ++# define __compiletime_warning(message) __attribute__((warning(message)))
> ++# define __compiletime_error(message) __attribute__((error(message)))
> ++#endif /* __CHECKER__ */
> ++
> ++/*
> ++ * Mark a position in code as unreachable. This can be used to
> ++ * suppress control flow warnings after asm blocks that transfer
> ++ * control elsewhere.
> ++ *
> ++ * Early snapshots of gcc 4.5 don't support this and we can't detect
> ++ * this in the preprocessor, but we can live with this because they're
> ++ * unreleased. Really, we need to have autoconf for the kernel.
> ++ */
> ++#define unreachable() __builtin_unreachable()
> ++
> ++/* Mark a function definition as prohibited from being cloned. */
> ++#define __noclone __attribute__((__noclone__))
> ++
> ++/*
> ++ * Tell the optimizer that something else uses this function or variable.
> ++ */
> ++#define __visible __attribute__((externally_visible))
> ++
> ++/*
> ++ * GCC 'asm goto' miscompiles certain code sequences:
> ++ *
> ++ * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670
> ++ *
> ++ * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
> ++ *
> ++ * (asm goto is automatically volatile - the naming reflects this.)
> ++ */
> ++#define asm_volatile_got
Re: [yocto] [meta-raspberrypi][PATCH V3 0/4] Drop rpi-mkimage and use upstream u-boot
On Sat, Jun 18, 2016 at 12:07:02PM +0100, Paul Barker wrote: > Following discussion on the Raspberry Pi tools bug tracker it was found that > rpi-mkimage is no longer needed with recent firmware. It can therefore be > dropped from the layer completely. > > Whilst looking into this I also found that the u-boot-rpi recipe in > meta-raspberrypi can now be replaced by direct use of the mainline u-boot > recipe > from oe-core. The 2016.03 release of u-boot supports the original Raspberry Pi > and the Raspberry Pi 2. Configuration of the u-boot environment to directly > boot > the uImage file on the SD card must still be done manually - I'm going to look > into making this work by default in the near future. > > Changes for V2: > * Don't remove linux-raspberrypi 3.18 just yet > * Drop move of PV setting out of linux-raspberrypi.inc > > Changes for V3: > * Rebase onto latest master > > Paul Barker (4): > linux-raspberrypi: rpi-mkimage is no longer needed > u-boot: Use mainline u-boot recipe from oe-core > rpi-mkimage: Remove unused recipe > sdcard_image-rpi: Always install dtb files > > classes/sdcard_image-rpi.bbclass | 42 > +++--- > conf/machine/include/rpi-default-providers.inc | 1 - > conf/machine/raspberrypi.conf | 2 ++ > conf/machine/raspberrypi2.conf | 2 ++ > recipes-bsp/rpi-mkimage/rpi-mkimage/License| 25 - > .../open-files-relative-to-script.patch| 17 - > recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 22 > recipes-bsp/u-boot/u-boot-rpi_git.bb | 29 --- > recipes-kernel/linux/linux-raspberrypi.inc | 20 --- > 9 files changed, 25 insertions(+), 135 deletions(-) > delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage/License > delete mode 100644 > recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch > delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb > delete mode 100644 recipes-bsp/u-boot/u-boot-rpi_git.bb > Merged to master. Thank you. -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Toaster build fails on Master branch Yocto
Hi Sambaran, On 07/07/2016 10:43, "yocto-boun...@yoctoproject.org on behalf of Sambaran Ghosh" wrote: >While creating a toaster project with the Master Yocto branch, build >always fails. But if I select Krogoth or Jethro branch then builds >succeeds. The major problem with sub-branches like Krogoth is that there >few layers supported. Is everyone having > similar problem? If you are using the Krogoth release of Yocto Project, Toaster will no longer build the master branch. The project as a whole has migrated to python3, and that has broken compatibility between Krogoth and master. So with the Toaster from Krogoth you will only be able to build krogoth and jethro. >And do you have any solution? There is, although it is a bit clunky. You will need to manually import any layers you want to build into your krogoth Toaster project. In the project page, select the "import layer" tab, and fill the git repository information, which you can get from https://layers.yoctoproject.org. As the revision, enter "master". That will add the layer to the list of compatible layers for the project, and add it to the project configuration, so that you can build recipes from it. I hope this helps. Cheers Belén > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error building python-imaging_1.1.7.bb
On Thu, Jun 02, 2016 at 12:55:17PM -0400, Michael Dangler wrote: > Hello > > Am new to yocto and am trying to build an image for a Gumstix Pepper board > and use ROS. However always get to the point with python-imaging_1.1.7.bb > failing do_package_qa. HAve tried just doing the following - > > bitbake python-imaging > > But still have the same failure - > > Build Configuration: > BB_VERSION= "1.26.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-14.04" > TARGET_SYS= "arm-poky-linux-gnueabi" > MACHINE = "pepper" > DISTRO= "poky" > DISTRO_VERSION= "1.8" > TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8" > TARGET_FPU= "vfp-neon" > meta > meta-yocto= "(nobranch):83aa565d93aacae484976562ef1ae8dbbb6b2bc0" > meta-gnome > meta-oe > meta-xfce > meta-systemd > meta-networking > meta-multimedia > meta-python = "(nobranch):10d3c8f85280a0bf867a8e4f84bcda81c290d28e" > meta-gumstix = "(nobranch):8ea631d8ef26cb13102dac0910be52674cb7b395" > meta-gumstix-extras = "(nobranch):15cfa9fcff75d3d95f66cfa190e1b604ff5ea4f6" > meta-ros = "(nobranch):d465a23c0a96e651419d46b29ab7c0c3663da314" > meta-ti = "(nobranch):03cb3ff15f3b8535ca409ce682f44ec1b81da0c3" > meta-java = "(nobranch):66c97ae7461f4c1a13917131787bb76dc34e6b6f" > > NOTE: Preparing RunQueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > ERROR: QA Issue: python-imaging: The compile log indicates that host > include and/or library paths were used. > Please check the log > '/home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_compile' > for more information. [compile-host-path] > ERROR: QA run found fatal errors. Please consider fixing them. > ERROR: Function failed: do_package_qa > ERROR: Logfile of failure stored in: > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_package_qa.11102 > ERROR: Task 9 (/home/michael/yocto/poky/meta/recipes-devtools/python/ > python-imaging_1.1.7.bb, do_package_qa) failed with exit code '1' > NOTE: Tasks Summary: Attempted 695 tasks of which 0 didn't need to be rerun > and 1 failed. > Waiting for 0 running tasks to finish: > > Summary: 1 task failed: > /home/michael/yocto/poky/meta/recipes-devtools/python/ > python-imaging_1.1.7.bb, do_package_qa > Summary: There were 3 ERROR messages shown, returning a non-zero exit code. > > > DEBUG: Executing python function sstate_task_prefunc > DEBUG: Python function sstate_task_prefunc finished > DEBUG: Executing python function do_package_qa > NOTE: DO PACKAGE QA > DEBUG: Executing python function read_subpackage_metadata > DEBUG: Python function read_subpackage_metadata finished > ERROR: QA Issue: python-imaging: The compile log indicates that host > include and/or library paths were used. > Please check the log > '/home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_compile' > for more information. [compile-host-path] > NOTE: Checking Package: python-imaging-staticdev > NOTE: Checking Package: python-imaging-dev > NOTE: Checking Package: python-imaging-dbg > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imaging.so > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imagingmath.so > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imagingft.so > NOTE: Checking Package: python-imaging-doc > NOTE: Checking Package: python-imaging > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imaging.so > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imagingmath.so > NOTE: arm-poky-linux-gnueabi-objdump -p > /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imagingft.so > ERROR: QA run found fatal errors. Please consider fixing them. > DEBUG: Python function do_package_qa finished > ERROR: Function failed: do_package_qa > > Any help would be much grateful and please let me know if I should post > somewhere else. Thank you all. > > Cheers, Micha
Re: [yocto] [meta-raspberry] Raspberry Pi 3
On Fri, Mar 18, 2016 at 10:15:39AM +0100, David Weisgerber wrote: > Hi, > did anyone succeed in building an image that runs on Raspberry Pi 3? I set my > conf/local.conf to > > MACHINE ??= "raspberrypi3" > GPU_MEM = "128" > DISABLE_OVERSCAN = "1" > > and built rpi-basic-image but when booting the Pi 3 up I only see 4 > raspberries in the top right but nothing else happens. The image works > perfectly on a Pi 2 though. > > Thanks for help, > David > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto How do you check that the image is running or not? PS: Please us the correct subject tag: meta-raspberrypi. -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/2] linux-raspberrypi: Fix v4.1 with GCC6
On Wed, Jun 15, 2016 at 01:43:23PM -0700, Khem Raj wrote:
>
>
> On Tue, Jun 14, 2016 at 4:50 PM, Andrei Gherzan wrote:
> > Signed-off-by: Andrei Gherzan
> > ---
> > ...ove-unused-sm_cache_map_vector-definition.patch | 31 +
> > .../linux-raspberrypi-4.1/0003-fix-gcc6.patch | 78
> > ++
> > recipes-kernel/linux/linux-raspberrypi_4.1.bb | 2 +
> > 3 files changed, 111 insertions(+)
> > create mode 100644
> > recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> > create mode 100644
> > recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> >
> > diff --git
> > a/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> >
> > b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> > new file mode 100644
> > index 000..8d4a900
> > --- /dev/null
> > +++
> > b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
> > @@ -0,0 +1,31 @@
> > +The code using it also ifdef'ed with 0, anyyd gcc 6
> > +complains
> > +
> > +error: 'sm_cache_map_vector' defined but not used
> > +
> > +The code using it also ifdef'ed out
> > +
> > +Upstream-status: Denied [https://github.com/raspberrypi/linux/pull/1528]
> > +
> > +Signed-off-by: Khem Raj
> > +---
> > + drivers/char/broadcom/vc_sm/vmcs_sm.c | 2 ++
> > + 1 file changed, 2 insertions(+)
> > +
> > +--- a/drivers/char/broadcom/vc_sm/vmcs_sm.c
> > b/drivers/char/broadcom/vc_sm/vmcs_sm.c
> > +@@ -197,12 +197,14 @@ struct SM_STATE_T {
> > + static struct SM_STATE_T *sm_state;
> > + static int sm_inited;
> > +
> > ++#if 0
> > + static const char *const sm_cache_map_vector[] = {
> > + "(null)",
> > + "host",
> > + "videocore",
> > + "host+videocore",
> > + };
> > ++#endif
> > +
> > + /* Private Function Prototypes
> > -- */
> > +
> > diff --git a/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> > b/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> > new file mode 100644
> > index 000..61ec2fb
> > --- /dev/null
> > +++ b/recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
> > @@ -0,0 +1,78 @@
> > +Fix compile with GCC6
> > +
> > +Upstream-status: Denied [https://github.com/raspberrypi/linux/pull/1528]
> > +
> > +Signed-off-by: Andrei Gherzan
> > +
> > +Index: source/include/linux/compiler-gcc6.h
> > +===
> > +--- /dev/null
> > source/include/linux/compiler-gcc6.h
> > +@@ -0,0 +1,67 @@
> > ++#ifndef __LINUX_COMPILER_H
> > ++#error "Please don't include directly, include
> > instead."
> > ++#endif
> > ++
> > ++#define __used__attribute__((__used__))
> > ++#define __must_check __attribute__((warn_unused_result))
> > ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b)
> > ++
> > ++/* Mark functions as cold. gcc will assume any path leading to a call
> > ++ to them will be unlikely. This means a lot of manual unlikely()s
> > ++ are unnecessary now for any paths leading to the usual suspects
> > ++ like BUG(), printk(), panic() etc. [but let's keep them for now for
> > ++ older compilers]
> > ++
> > ++ Early snapshots of gcc 4.3 don't support this and we can't detect this
> > ++ in the preprocessor, but we can live with this because they're
> > unreleased.
> > ++ Maketime probing would be overkill here.
> > ++
> > ++ gcc also has a __attribute__((__hot__)) to move hot functions into
> > ++ a special section, but I don't see any sense in this right now in
> > ++ the kernel context */
> > ++#define __cold__attribute__((__cold__))
> > ++
> > ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix),
> > __COUNTER__)
> > ++
> > ++#ifndef __CHECKER__
> > ++# define __compiletime_warning(message) __attribute__((warning(message)))
> > ++# define __compiletime_error(message) __attribute__((error(message)))
> > ++#endif /* __CHECKER__ */
> > ++
> > ++/*
> > ++ * Mark a position in code as unreachable. This can be used to
> > ++ * suppress control flow warnings after asm blocks that transfer
> > ++ * control elsewhere.
> > ++ *
> > ++ * Early snapshots of gcc 4.5 don't support this and we can't detect
> > ++ * this in the preprocessor, but we can live with this because they're
> > ++ * unreleased. Really, we need to have autoconf for the kernel.
> > ++ */
> > ++#define unreachable() __builtin_unreachable()
> > ++
> > ++/* Mark a function definition as prohibited from being cloned. */
> > ++#define __noclone __attribute__((__noclone__))
> > ++
> > ++/*
> > ++ * Tell the optimizer that something else uses this function or variable.
> > ++ */
> > ++#define __visible __attribute__((externally_visible))
> > ++
> > ++/*
> > ++ * GCC 'asm
Re: [yocto] [meta-raspberrypi][PATCH 1/4] userland: Upgrade to latest tip
On Thu, Jun 23, 2016 at 02:34:28PM -0700, Khem Raj wrote:
> Drop upstream applied patches
>
> Signed-off-by: Khem Raj
> ---
> ...applications-to-set-next-resource-handle.patch} | 6 +-
> ...make-generate-and-install-pkgconfig-files.patch | 114
> -
> ...yland-Add-support-for-the-Wayland-winsys.patch} | 10 +-
> ...atch => 0003-wayland-Add-Wayland-example.patch} | 6 +-
> ...wayland-egl-Add-bcm_host-to-dependencies.patch} | 6 +-
> ...move-faulty-assert-to-make-weston-happy-.patch} | 8 +-
> ...-zero-out-wl-buffers-in-egl_surface_free.patch} | 6 +-
> ...07-initialize-front-back-wayland-buffers.patch} | 6 +-
> ...RPC_FLUSH.patch => 0008-Remove-RPC_FLUSH.patch} | 6 +-
> patch => 0009-fix-cmake-dependency-race.patch} | 6 +-
> ...tch => 0010-Fix-enum-conversion-warnings.patch} | 6 +-
> ...ix-for-framerate-with-nested-composition.patch} | 6 +-
> ...> 0012-build-shared-library-for-vchostif.patch} | 6 +-
> ...t-buffer-wrapping-interface-for-dispmanx.patch} | 14 ++-
> recipes-graphics/userland/userland_git.bb | 29 +++---
> 15 files changed, 66 insertions(+), 169 deletions(-)
> rename
> recipes-graphics/userland/userland/{0003-Allow-applications-to-set-next-resource-handle.patch
> => 0001-Allow-applications-to-set-next-resource-handle.patch} (98%)
> delete mode 100644
> recipes-graphics/userland/userland/0002-cmake-generate-and-install-pkgconfig-files.patch
> rename
> recipes-graphics/userland/userland/{0004-wayland-Add-support-for-the-Wayland-winsys.patch
> => 0002-wayland-Add-support-for-the-Wayland-winsys.patch} (99%)
> rename
> recipes-graphics/userland/userland/{0005-wayland-Add-Wayland-example.patch =>
> 0003-wayland-Add-Wayland-example.patch} (99%)
> rename
> recipes-graphics/userland/userland/{0006-wayland-egl-Add-bcm_host-to-dependencies.patch
> => 0004-wayland-egl-Add-bcm_host-to-dependencies.patch} (86%)
> rename
> recipes-graphics/userland/userland/{0007-interface-remove-faulty-assert-to-make-weston-happy-.patch
> => 0005-interface-remove-faulty-assert-to-make-weston-happy-.patch} (86%)
> rename
> recipes-graphics/userland/userland/{0008-zero-out-wl-buffers-in-egl_surface_free.patch
> => 0006-zero-out-wl-buffers-in-egl_surface_free.patch} (87%)
> rename
> recipes-graphics/userland/userland/{0009-initialize-front-back-wayland-buffers.patch
> => 0007-initialize-front-back-wayland-buffers.patch} (88%)
> rename recipes-graphics/userland/userland/{0010-Remove-RPC_FLUSH.patch =>
> 0008-Remove-RPC_FLUSH.patch} (87%)
> rename
> recipes-graphics/userland/userland/{0011-fix-cmake-dependency-race.patch =>
> 0009-fix-cmake-dependency-race.patch} (95%)
> rename
> recipes-graphics/userland/userland/{0012-Fix-enum-conversion-warnings.patch
> => 0010-Fix-enum-conversion-warnings.patch} (97%)
> rename
> recipes-graphics/userland/userland/{0013-Fix-for-framerate-with-nested-composition.patch
> => 0011-Fix-for-framerate-with-nested-composition.patch} (94%)
> rename
> recipes-graphics/userland/userland/{0014-build-shared-library-for-vchostif.patch
> => 0012-build-shared-library-for-vchostif.patch} (84%)
> rename
> recipes-graphics/userland/userland/{0015-wl-dispmanx-buffer-wrapping.patch =>
> 0013-implement-buffer-wrapping-interface-for-dispmanx.patch} (85%)
>
> diff --git
> a/recipes-graphics/userland/userland/0003-Allow-applications-to-set-next-resource-handle.patch
>
> b/recipes-graphics/userland/userland/0001-Allow-applications-to-set-next-resource-handle.patch
> similarity index 98%
> rename from
> recipes-graphics/userland/userland/0003-Allow-applications-to-set-next-resource-handle.patch
> rename to
> recipes-graphics/userland/userland/0001-Allow-applications-to-set-next-resource-handle.patch
> index 4a8b16d..4d026bd 100644
> ---
> a/recipes-graphics/userland/userland/0003-Allow-applications-to-set-next-resource-handle.patch
> +++
> b/recipes-graphics/userland/userland/0001-Allow-applications-to-set-next-resource-handle.patch
> @@ -1,7 +1,7 @@
> -From 1d750c8922cbb4276e4337d2af2776676c0bd224 Mon Sep 17 00:00:00 2001
> +From 83c5ac5892d0cd29caa8922ff8b639b9a373c3cb Mon Sep 17 00:00:00 2001
> From: Dom Cobley
> Date: Tue, 9 Jul 2013 09:26:26 -0400
> -Subject: [PATCH 03/13] Allow applications to set next resource handle
> +Subject: [PATCH 01/13] Allow applications to set next resource handle
>
> This patch adds provisions in userland to
> let apps callers set the next rendereing dispmanx resource.
> @@ -204,5 +204,5 @@ index 8a5734c..51b3580 100644
>
> FN(void, eglIntGetColorData_impl, (EGL_SURFACE_ID_T s, KHRN_IMAGE_FORMAT_T
> format, uint32_t width, uint32_t height, int32_t stride, uint32_t y_offset,
> void *data))
> --
> -2.7.4
> +2.9.0
>
> diff --git
> a/recipes-graphics/userland/userland/0002-cmake-generate-and-install-pkgconfig-files.patch
>
> b/recipes-graphics/userland/userland/0002-cmake-generate-and-install-pkgconfig-files.patch
> deleted file mode 100644
> index 50ebaa6..000
>
Re: [yocto] [meta-raspberrypi] PL2303 instability on RPi 3 but not on RPi 2
On Mon, Jun 13, 2016 at 11:24:08PM +0200, Martin Bergek wrote: > Hi, > > I am testing an image on a system including a PL2303 (USB to serial bridge) > and have noticed an issue on the Raspberry Pi 3. The system will run fine for > an hour or two but then the kernel logs the following error: > > pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 > > After this there is no more data coming from the USB device and I have to > either reboot or disconnect/connect the USB device - neither of which is > acceptable in my application. > > This is on kernel 4.4.9 and it happens only on the Raspberry Pi 3. On > Raspberry Pi 2 the exact same firmware runs flawlessly. > > Has anyone else come across this or have some suggestions on how to solve it? > Or how to pinpoint the cause? > > Thanks, > Martin Bergek > I'm usign exactly the same chipset and never saw this problem before. There might be something related to https://github.com/raspberrypi/firmware/issues/553 which you can test with a core_freq=250 As well it might be connected to the USB power supply if you use the 5V pin from PL2303 to power up your board. I do and I experience no issue but it might be something there. -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to install 2 or more initscrips out form one recipe?
Hej
I run into a problem when I tried to install 3 initscrips out of one
recipe. My recipe looks like:
#
SUMMARY = "demo cfg"
SECTION = "demo"
LICENSE = "CLOSED"
inherit update-rc.d
RDEPENDS_${PN} = "bash initscripts"
SRC_URI = "file://startA \
file://startB \
file://startC \
"
S = "${WORKDIR}"
do_install () {
install -d ${D}${sysconfdir}/
install -d ${D}${sysconfdir}/init.d/
install -m 0644 ${S}/startA ${D}${sysconfdir}/init.d/startA
install -m 0644 ${S}/startB ${D}${sysconfdir}/init.d/startB
install -m 0644 ${S}/startC ${D}${sysconfdir}/init.d/startC
chmod a+x ${D}${sysconfdir}/init.d/startA
chmod a+x ${D}${sysconfdir}/init.d/startB
chmod a+x ${D}${sysconfdir}/init.d/startC
}
INITSCRIPT_PACKAGES = "${PN} ${PN}_B ${PN}_C"
INITSCRIPT_NAME_${PN} = "startA"
INITSCRIPT_PARAMS_${PN} = "start 90 10"
INITSCRIPT_NAME_${PN}_B = "startB"
INITSCRIPT_PARAMS_${PN}_B = "start 90 10"
INITSCRIPT_NAME_${PN}_C = "startC"
INITSCRIPT_PARAMS_${PN}_C = "start 90 10"
CONFFILES_${PN} += "${sysconfdir}/init.d/startA"
CONFFILES_${PN} += "${sysconfdir}/init.d/startB"
CONFFILES_${PN} += "${sysconfdir}/init.d/startC"
FILES_${PN} += "${sysconfdir}/*"
#
The do_install works but initscript does not generates the link. I build
that after this document
http://docs.openembedded.ru/update-rc-d_class.html.
Any ideas?
Regards!
Stefan Jaritz
ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de
Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker
Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten
haben, informieren Sie bitte sofort den Absender und löschen Sie diese
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail
ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you
are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is
strictly
forbidden.--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberry] Raspberry Pi 3
On Fri, Jul 8, 2016 at 6:12 AM, Andrei Gherzan wrote: >> MACHINE ??= "raspberrypi3" can you change it to MACHINE = "raspberrypi3" and retry -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 1/2] sdcard_image-rpi.bbclass: Add the vardepexcludes
The problem reappears because we need to add to the variable
and not assign
Signed-off-by: Khem Raj
---
classes/sdcard_image-rpi.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 6960aca..57cefea 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -72,8 +72,8 @@ SDIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
FATPAYLOAD ?= ""
IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
-IMAGE_CMD_rpi-sdimg[vardepsexclude] = "IMAGEDATESTAMP"
-IMAGE_CMD_rpi-sdimg[vardepsexclude] = "DATETIME"
+IMAGE_CMD_rpi-sdimg[vardepsexclude] += "IMAGEDATESTAMP"
+IMAGE_CMD_rpi-sdimg[vardepsexclude] += "DATETIME"
IMAGE_CMD_rpi-sdimg () {
--
2.9.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 2/2] gstreamer1.0-omx-1.2.0: Add patches and bbappend for 1.2.0 separately
Signed-off-by: Khem Raj
---
...o-acquire-buffer-when-src-pad-isn-t-activ.patch | 48
.../0001-config-files-path.patch | 137 +
.../0002-fix-decoder-flushing.patch| 16 +++
.../0003-no-timeout-on-get-state.patch | 16 +++
...erly-handle-drain-requests-while-flushing.patch | 69 +++
...-gst_omx_video_dec_set_format-if-there-s-.patch | 30 +
...-unref-allocator-after-getting-it-from-al.patch | 48
...mxvideodec-Use-gstglmemoryegl-for-the-RPi.patch | 115 +
..._%.bbappend => gstreamer1.0-omx_1.2.0.bbappend} | 8 +-
...mx_%.bbappend => gstreamer1.0-omx_git.bbappend} | 0
10 files changed, 484 insertions(+), 3 deletions(-)
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-config-files-path.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0002-fix-decoder-flushing.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0003-no-timeout-on-get-state.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0004-Properly-handle-drain-requests-while-flushing.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0005-Don-t-abort-gst_omx_video_dec_set_format-if-there-s-.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0006-omxvideodec-unref-allocator-after-getting-it-from-al.patch
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0007-omxvideodec-Use-gstglmemoryegl-for-the-RPi.patch
copy recipes-multimedia/gstreamer/{gstreamer1.0-omx_%.bbappend =>
gstreamer1.0-omx_1.2.0.bbappend} (70%)
rename recipes-multimedia/gstreamer/{gstreamer1.0-omx_%.bbappend =>
gstreamer1.0-omx_git.bbappend} (100%)
diff --git
a/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch
b/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch
new file mode 100644
index 000..815a7c2
--- /dev/null
+++
b/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch
@@ -0,0 +1,48 @@
+From 2e111e52f96f0b942abda120c30a876629bd73fc Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Enrique=20Oca=C3=B1a=20Gonz=C3=A1lez?=
+Date: Mon, 25 May 2015 14:53:35 +0200
+Subject: [PATCH] Don't try to acquire buffer when src pad isn't active
+
+This solves a race condition when setting the pipeline from PAUSE to
+NULL while the decoder loop is still running. Without this patch, the
+thread which interacts with the decode sink pad gets blocked here:
+
+ gst_element_change_state()
+ gst_element_change_state_func()
+ gst_element_pads_activate() --> Deactivating pads
+ activate_pads()
+ gst_pad_set_active()
+ gst_pad_activate_mode()
+ post_activate()
+ GST_PAD_STREAM_LOCK()
+
+while gst_omx_port_acquire_buffer() gets stalled forever in
+gst_omx_component_wait_message() waiting for a message that will never
+arrive:
+
+ gst_omx_video_dec_loop()
+ gst_omx_port_acquire_buffer()
+ gst_omx_component_wait_message()
+---
+ omx/gstomxvideodec.c | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/omx/gstomxvideodec.c b/omx/gstomxvideodec.c
+index cd24944..57a61dd 100644
+--- a/omx/gstomxvideodec.c
b/omx/gstomxvideodec.c
+@@ -1247,6 +1247,11 @@ gst_omx_video_dec_loop (GstOMXVideoDec * self)
+ GstClockTimeDiff deadline;
+ OMX_ERRORTYPE err;
+
++ if (!gst_pad_is_active(GST_VIDEO_DECODER_SRC_PAD (self))) {
++GST_DEBUG_OBJECT (self, "Src pad not active, not acquiring buffer and
flushing instead");
++ goto flushing;
++ }
++
+ #if defined (USE_OMX_TARGET_RPI) && defined (HAVE_GST_GL)
+ port = self->eglimage ? self->egl_out_port : self->dec_out_port;
+ #else
+--
+1.8.3.2
+
diff --git
a/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-config-files-path.patch
b/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-config-files-path.patch
new file mode 100644
index 000..a7da922
--- /dev/null
+++
b/recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-config-files-path.patch
@@ -0,0 +1,137 @@
+--- a/config/bellagio/gstomx.conf
b/config/bellagio/gstomx.conf
+@@ -1,6 +1,6 @@
+ [omxmpeg4videodec]
+ type-name=GstOMXMPEG4VideoDec
+-core-name=/usr/local/lib/libomxil-bellagio.so.0
++core-name=/usr/lib/libomxil-bellagio.so.0
+ component-name=OMX.st.video_decoder.mpeg4
+ rank=256
+ in-port-index=0
+@@ -9,7 +9,7 @@
+
+ [omxh264dec]
+ type-name=GstOMXH264Dec
+-core-name=/usr/local/lib/libomxil-bellagio.so.0
++core-name=/usr/lib/libomxil-bellagio.so.0
+ component-name=OMX.st.video_decoder.avc
+ rank=256
+ in-port-index=0
+@@ -18,7 +18,7 @@
+
+ [omxmpeg4videoenc]
+ type-name=GstOMXMPEG4VideoEnc
+-core-name=/usr/local/lib/lib
[yocto] Yocto Project Status WW28
Current Dev Position: YP 2.2 M2 Next Deadline: YP 2.2 M2 cut off would be: 7/18/16 SWAT team rotation: Bill -> Paul https://wiki.yoctoproject.org/wiki/Yoct o_Build_Failure_Swat_Team Key Status/Updates: * M1 QA report is out however there are concerns about performanceregressions which have not been root caused. M1 will continue to bedelayed until we figure out those issues and the fact that medium+ bugsand high bugs are still assigned to M1. * M2 patch merging is held up due to the shear volume of regressionswe’re seeing which are basically being left to Ross/RP to triage andfind the patches responsible. * We did upgrade pseudo after various issues which brings in severalxattr fixes and resolves the init problems we were seeing in pseudotowards the end of the last release properly, rather than theworkarounds we put in place. * We’ve merged the progress patches from Paul so we get better feedbackduring the build for how various tasks are progressing. * We’re looking likely to remove directfb from OE-Core since the projectappears to have died. * 2.1.1 is in QA having had a successful build. We are working with areduced capacity QA team due to various changes at Intel/WindRiver sowe will have more limited QA testing of this unfortunately. Key YP 2.2 Dates: * YP 2.2 M1 release would be: 6/24/16 * YP 2.2 M2 cut off would be: 7/18/16 * YP 2.2 M2 release would be: 7/29/16 * YP 2.2 M3 cut off would be: 8/29/16 * YP 2.2 M3 release would be: 9/9/16 * YP 2.2 M4 cut off would be: 10/3/16 * YP 2.2 M4 release would be: 10/28/16 Tracking Metrics: WDD 2747 (last week 2718) (https://wiki.yoctoproject.org/charts/combo.html) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to install a service generated by update-rc.d?
Yes - The installation of the can_if into /etc/init.d was missing.
By adding:
do_install () {
install -d ${D}${sysconfdir}/init.d
cat ${WORKDIR}/can_if | \
sed -e 's,/etc,${sysconfdir},g' \
-e 's,/usr/sbin,${sbindir},g' \
-e 's,/var,${localstatedir},g' \
-e 's,/usr/bin,${bindir},g' \
-e 's,/usr,${prefix},g' > ${D}${sysconfdir}/init.d/can_if
chmod a+x ${D}${sysconfdir}/init.d/can_if
}
It was solved!
Merci & Regards!
Stefan Jaritz
ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de
Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker
Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten
haben, informieren Sie bitte sofort den Absender und löschen Sie diese
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail
ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you
are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is
strictly
forbidden.
Von:Anders Darander
An: yocto@yoctoproject.org
Datum: 06.07.2016 11:40
Betreff:Re: [yocto] How to install a service generated by
update-rc.d?
Gesendet von: yocto-boun...@yoctoproject.org
* s.jar...@esa-grimma.de [160706 11:22]:
> I want to start a service that generates Sockets for the CAN Modules.
> Manually configuring the system is no problem, but I like to have it
done
> by yocto. Below I give the code of my recipe (socketcan.bb):
> SUMMARY = "the config for the can socket interface"
> SECTION = "CAN"
> LICENSE = "CLOSED"
> inherit update-rc.d
> RDEPENDS_${PN} = "initscripts"
> DEPENDS = "iproute2"
> SRC_URI = "file://can_if"
> INITSCRIPT_PARAMS = "start 02 2 3 4 5 . stop 01 0 1 6 ."
> INITSCRIPT_NAME = "can_if"
> CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
If this is the complete recipe, you never install can_if...
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
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] Toaster build fails on Master branch Yocto
Very helpful. Thanks a lot On Fri, Jul 8, 2016, 5:06 PM Barros Pena, Belen wrote: > Hi Sambaran, > > On 07/07/2016 10:43, "yocto-boun...@yoctoproject.org on behalf of Sambaran > Ghosh" sambaran.m...@gmail.com> wrote: > > >While creating a toaster project with the Master Yocto branch, build > >always fails. But if I select Krogoth or Jethro branch then builds > >succeeds. The major problem with sub-branches like Krogoth is that there > >few layers supported. Is everyone having > > similar problem? > > If you are using the Krogoth release of Yocto Project, Toaster will no > longer build the master branch. The project as a whole has migrated to > python3, and that has broken compatibility between Krogoth and master. So > with the Toaster from Krogoth you will only be able to build krogoth and > jethro. > > >And do you have any solution? > > There is, although it is a bit clunky. You will need to manually import > any layers you want to build into your krogoth Toaster project. In the > project page, select the "import layer" tab, and fill the git repository > information, which you can get from https://layers.yoctoproject.org. As > the revision, enter "master". > > That will add the layer to the list of compatible layers for the project, > and add it to the project configuration, so that you can build recipes > from it. > > I hope this helps. > > Cheers > > Belén > > > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] PublishLayerTarballs.py: don't change directories for Eclipse builds
When publishing eclipse tarballs, we are already in the correct directory, so skip the change direction operation (which will generate an error). Signed-off-by: Bill Randle --- .../site-packages/autobuilder/buildsteps/PublishLayerTarballs.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishLayerTarballs.py b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishLayerTarballs.py index c140725..7c1ce4a 100644 --- a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishLayerTarballs.py +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishLayerTarballs.py @@ -38,7 +38,8 @@ class PublishLayerTarballs(ShellCommand): snapshot = "" self.basedir=os.path.join(os.path.join(os.path.join( self.workerdir, buildername), self.workdir)) -if self.layername is not "poky": +if self.layername is not "poky" + and "eclipse" is not in self.layername: command = "cd " + self.layername + ";" else: command = "" -- 2.5.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to install 2 or more initscrips out form one recipe?
On 8 July 2016 at 16:57, wrote:
> Hej
>
> I run into a problem when I tried to install 3 initscrips out of one
> recipe. My recipe looks like:
> #
> SUMMARY = "demo cfg"
> SECTION = "demo"
> LICENSE = "CLOSED"
>
> inherit update-rc.d
>
> RDEPENDS_${PN} = "bash initscripts"
>
> SRC_URI = "file://startA \
> file://startB \
> file://startC \
> "
>
> S = "${WORKDIR}"
>
> do_install () {
> install -d ${D}${sysconfdir}/
> install -d ${D}${sysconfdir}/init.d/
> install -m 0644 ${S}/startA ${D}${sysconfdir}/init.d/startA
> install -m 0644 ${S}/startB ${D}${sysconfdir}/init.d/startB
> install -m 0644 ${S}/startC ${D}${sysconfdir}/init.d/startC
>
> chmod a+x ${D}${sysconfdir}/init.d/startA
> chmod a+x ${D}${sysconfdir}/init.d/startB
> chmod a+x ${D}${sysconfdir}/init.d/startC
> }
>
> INITSCRIPT_PACKAGES = "${PN} ${PN}_B ${PN}_C"
INITSCRIPT_NAME_${PN} = "startA"
> INITSCRIPT_PARAMS_${PN} = "start 90 10"
> INITSCRIPT_NAME_${PN}_B = "startB"
> INITSCRIPT_PARAMS_${PN}_B = "start 90 10"
> INITSCRIPT_NAME_${PN}_C = "startC"
> INITSCRIPT_PARAMS_${PN}_C = "start 90 10"
>
> CONFFILES_${PN} += "${sysconfdir}/init.d/startA"
> CONFFILES_${PN} += "${sysconfdir}/init.d/startB"
> CONFFILES_${PN} += "${sysconfdir}/init.d/startC"
>
> FILES_${PN} += "${sysconfdir}/*"
>
This puts all the init scripts in ${PN} when each should go into their own
package. You'll also probably need to make sure the extra packages are
created:
PACKAGES =+ "${PN}_B ${PN}_C"
Check packages-split/-directory in WORKDIR to make sure all the files went
to the right place.
As a style comment: Underscore probably works in a package name but hyphen
("${PN}-B") is the common choice.
Jussi
#
>
> The do_install works but initscript does not generates the link. I build
> that after this document
> http://docs.openembedded.ru/update-rc-d_class.html.
>
> Any ideas?
>
> Regards!
>
> Stefan Jaritz
>
>
>
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are
> not the intended recipient (or have received this e-mail in error) please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> --
> ___
> 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] How to install 2 or more initscrips out form one recipe?
Take a look at "initscripts_1.0.bb". A lot of init scripts are created in
that single recipe.
Thanks,
Paul Knopf
Software Engineer
Med X Change, Inc
pkn...@medxchange.com
On Fri, Jul 8, 2016 at 9:57 AM, wrote:
> Hej
>
> I run into a problem when I tried to install 3 initscrips out of one
> recipe. My recipe looks like:
> #
> SUMMARY = "demo cfg"
> SECTION = "demo"
> LICENSE = "CLOSED"
>
> inherit update-rc.d
>
> RDEPENDS_${PN} = "bash initscripts"
>
> SRC_URI = "file://startA \
> file://startB \
> file://startC \
> "
>
> S = "${WORKDIR}"
>
> do_install () {
> install -d ${D}${sysconfdir}/
> install -d ${D}${sysconfdir}/init.d/
> install -m 0644 ${S}/startA ${D}${sysconfdir}/init.d/startA
> install -m 0644 ${S}/startB ${D}${sysconfdir}/init.d/startB
> install -m 0644 ${S}/startC ${D}${sysconfdir}/init.d/startC
>
> chmod a+x ${D}${sysconfdir}/init.d/startA
> chmod a+x ${D}${sysconfdir}/init.d/startB
> chmod a+x ${D}${sysconfdir}/init.d/startC
> }
>
> INITSCRIPT_PACKAGES = "${PN} ${PN}_B ${PN}_C"
> INITSCRIPT_NAME_${PN} = "startA"
> INITSCRIPT_PARAMS_${PN} = "start 90 10"
> INITSCRIPT_NAME_${PN}_B = "startB"
> INITSCRIPT_PARAMS_${PN}_B = "start 90 10"
> INITSCRIPT_NAME_${PN}_C = "startC"
> INITSCRIPT_PARAMS_${PN}_C = "start 90 10"
>
> CONFFILES_${PN} += "${sysconfdir}/init.d/startA"
> CONFFILES_${PN} += "${sysconfdir}/init.d/startB"
> CONFFILES_${PN} += "${sysconfdir}/init.d/startC"
>
> FILES_${PN} += "${sysconfdir}/*"
> #
>
> The do_install works but initscript does not generates the link. I build
> that after this document
> http://docs.openembedded.ru/update-rc-d_class.html.
>
> Any ideas?
>
> Regards!
>
> Stefan Jaritz
>
>
>
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are
> not the intended recipient (or have received this e-mail in error) please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> --
> ___
> 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] [meta-raspberrypi] u-boot doesnt boot kernel
Hi,
I wanted to boot with u-boot so I added:
KERNEL_IMAGETYPE = "uImage"
u-boot builds fine but when I boot up my raspberrypi, u-boot doesnt start
the kernel.
U-Boot 2013.01-rc1 (Jul 08 2016 - 19:01:50)
DRAM: 448 MiB
WARNING: Caches not enabled
MMC: bcm2835_sdhci: 0
Using default environment
In:serial
Out: lcd
Err: lcd
mbox: Timeout waiting for response
bcm2835: Could not set USB power state
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
reading uEnv.txt
** Unable to read file uEnv.txt **
reading boot.scr
** Unable to read file boot.scr **
U-Boot>
Heres is a printenv
U-Boot> printenv
arch=arm
baudrate=115200
board=rpi_b
board_name=rpi_b
bootargs=dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416
bcm2708.boardrev=0xe bcm2708.serial=0x4ef0ddfa
smsc95xx.macaddr=B8:27:EB:F0:DD:FA sdhci-bcm2708.emmc_clock_freq=25000
vc_memg
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootenv; then run
importbootenv; fi; if run loadbootscript; then run bootscript; fi; fi
bootdelay=3
bootenv=uEnv.txt
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
cpu=arm1176
importbootenv=echo Importing environment from mmc ...; env import -t
$loadaddr $filesize
loadaddr=0x0020
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
mmcdev=0
soc=bcm2835
stderr=serial,lcd
stdin=serial
stdout=serial,lcd
usbethaddr=B8:27:EB:F0:DD:FA
vendor=raspberrypi
Environment size: 1064/16380 bytes
Any help would be great. Thanks.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
