Re: [yocto] Error building python-imaging_1.1.7.bb

[Andrei Gherzan]

/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, Michael

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

I've sent a patch lately that might fix your issue:
http://lists.openembedded.org/pipermail/openembedded-devel/2016-July/108073.html

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH V3 0/4] Drop rpi-mkimage and use upstream u-boot

[Andrei Gherzan]

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] [PATCH 2/2] linux-raspberrypi: Fix v4.1 with GCC6

[Andrei Gherzan]

On Wed, Jun 15, 2016 at 12:50:20AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  ...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 <raj.k...@gmail.com>
> +---
> + 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 <and...@gherzan.ro>
> +
> +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__))
&g

Re: [yocto] [PATCH 1/2] packagegroup-rpi-test: Poky moved the license so fix LIC_FILES_CHKSUM

[Andrei Gherzan]

On Wed, Jun 15, 2016 at 12:50:19AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  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] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

[Andrei Gherzan]

On Fri, Jun 03, 2016 at 08:47:45PM +0100, Paul Barker wrote:
> On Fri, 3 Jun 2016 09:07:37 +0300
> Ionel Badisor <ionelbadi...@gmail.com> wrote:
>
> > On 06/03/2016 12:25 AM, Paul Barker wrote:
> > > On Thu, 2 Jun 2016 10:59:37 +0300
> > > Ionel Badisor <ionelbadi...@gmail.com> wrote:
> > >
> > >> On 06/01/2016 08:55 PM, Paul Barker wrote:
> > >>> On Tue, 31 May 2016 10:39:03 +0300
> > >>> Khem Raj <raj.k...@gmail.com> wrote:
> > >>>
> > >>>> On May 30, 2016 3:15 PM, "Paul Barker" <p...@paulbarker.me.uk>
> > >>>> wrote:
> > >>>>>
> > >>>>>
> > >>>>> I'm trying to build from a source archive instead of a git
> > >>>>> repository (to avoid a ~1.3GB git clone operation) so the use of
> > >>>>> ${SRCPV} is causing me trouble.
> > >>>>>
> > >>>>
> > >>>> Can you override the whole PV
> > >>>
> > >>> I've given this another look and I can get the recipe to parse if
> > >>> I require linux-raspberrypi.inc before setting PV instead of
> > >>> afterwards. However do_kernel_configme then gets confused looking
> > >>> for a "standard/raspberrypi" configuration. It only works if I
> > >>> modify linux-raspberrypi.inc as per my patch and set PV before
> > >>> requiring that include file.
> > >>>
> > >>> I'm starting to think that I might be doing something wrong here -
> > >>> is there a supported way to build a kernel from an archive instead
> > >>> of a git repository within OE?
> > >>>
> > >>> Thanks,
> > >>> Paul Barker
> > >>>
> > >> Are you trying to avoid repeated cloning operation to save bandwith
> > >> and time or you are trying to save disk space?
> > >
> > > I'm trying to reduce "time to first build" on a new build machine as
> > > well as the amount of space/bandwidth needed to mirror downloaded
> > > files.
> > >
> > > Instead of setting PV in each recipe I could just duplicate
> > > linux-raspberrypi.inc into my own layer with the change I need.
> > > That's probably the simplest approach for now, I'll just have to
> > > keep my eye on meta-raspberrypi going forward for any changes to
> > > linux-raspberrypi.inc which I'd need to incorporate.
> > >
> > Maybe you can use the `DL_DIR ?= "/path/to/downloads/"` in your
> > conf/local.conf file for multiple build directories and if you want
> > you can copy downloads directory to new machine and point to it the
> > new local.conf  then all do_fetch operations are already performed,
> > except new changes in which case the git fetch operation is performed
> > when git is used and takes less time then when fetching entire
> > archive.
> >
> > note: multiple builds on same machine can use same downloads
> > directory.
>
> I'm planning to release this as part of a distro layer in the future.
> Not all build machines will be under my control if others use the
> layer.
>
> I'm going to drop this patch for now as I can maintain my own copy of
> linux-raspberrypi.inc. I think it'd be good to get the other changes
> into master.
>
> V2 incoming.

I managed to follow the discussion. Sorry for my last reply on this.

I don't think the solution would be to manage a custom inc file. We need
to find a solution with this. Can I see and try your changes for the
arhive?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

[Andrei Gherzan]

On Sun, May 29, 2016 at 04:59:08PM +0100, Paul Barker wrote:
> PV is now set in each version of the linux-raspberrypi recipe instead of in
> linux-raspberrypi.inc. This allows linux-raspberrypi.inc to be used in custom
> kernel recipes in another layer which require a different PV value.
>
> Signed-off-by: Paul Barker <p...@paulbarker.me.uk>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc | 1 -
>  recipes-kernel/linux/linux-raspberrypi_3.18.bb | 1 +
>  recipes-kernel/linux/linux-raspberrypi_4.1.bb  | 1 +
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb  | 1 +
>  4 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 4799c74..dd477cd 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -13,7 +13,6 @@ SRC_URI += " \
>  COMPATIBLE_MACHINE = "raspberrypi"
>
>  PE = "1"
> -PV = "${LINUX_VERSION}+git${SRCPV}"
>
>  # NOTE: For now we pull in the default config from the RPi kernel GIT tree.
>  KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
> diff --git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb 
> b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> index 1110b71..b16a1d7 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> @@ -1,6 +1,7 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
>  LINUX_VERSION ?= "3.18.16"
> +PV = "${LINUX_VERSION}+git${SRCPV}"
>
>  SRCREV = "1bb18c8f721ef674a447f3622273f2e2de7a205c"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y \
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> index 79fac66..9e1572e 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> @@ -1,6 +1,7 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
>  LINUX_VERSION ?= "4.1.21"
> +PV = "${LINUX_VERSION}+git${SRCPV}"
>
>  SRCREV = "ff45bc0e8917c77461b2901e2743e6339bb70413"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y \
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index ba47b22..12bb43a 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,6 +1,7 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
>  LINUX_VERSION ?= "4.4.9"
> +PV = "${LINUX_VERSION}+git${SRCPV}"
>
>  SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \

I'm not really happy in duplicating PV. Wouldn't a weak assignment work
for you? PV ?= "${LINUX_VERSION}+git${SRCPV}" . So you can overwrite it
as you want.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support for .dtbo files for dtb overlays

[Andrei Gherzan]

On Tue, May 31, 2016 at 04:46:33AM +0800, Herve Jourdain wrote:
> Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of 
> .dtb.
> Add support for both variants of overlays ("-overlay.dtb" and ".dtbo") for 
> the default KERNEL_DEVICETREE variable
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  conf/machine/include/rpi-base.inc | 36 +++-
>  1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 56ca83e..2c9d8e0 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -16,7 +16,7 @@ XSERVER = " \
>  "
>
>  # Really supported starting from linux-raspberrypi 3.18.y only
> -KERNEL_DEVICETREE ?= " \
> +KERNEL_DEVICETREE_OVERLAYS_DTB = " \
>  bcm2708-rpi-b.dtb \
>  bcm2708-rpi-b-plus.dtb \
>  bcm2709-rpi-2-b.dtb \
> @@ -38,6 +38,40 @@ KERNEL_DEVICETREE ?= " \
>  overlays/w1-gpio-pullup-overlay.dtb \
>  overlays/pi3-miniuart-bt-overlay.dtb \
>  "
> +KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
> +bcm2708-rpi-b.dtb \
> +bcm2708-rpi-b-plus.dtb \
> +bcm2709-rpi-2-b.dtb \
> +bcm2710-rpi-3-b.dtb \
> +\
> +overlays/hifiberry-amp.dtbo \
> +overlays/hifiberry-dac.dtbo \
> +overlays/hifiberry-dacplus.dtbo \
> +overlays/hifiberry-digi.dtbo \
> +overlays/i2c-rtc.dtbo \
> +overlays/iqaudio-dac.dtbo \
> +overlays/iqaudio-dacplus.dtbo \
> +overlays/lirc-rpi.dtbo \
> +overlays/pitft22.dtbo \
> +overlays/pitft28-resistive.dtbo \
> +overlays/pps-gpio.dtbo \
> +overlays/rpi-ft5406.dtbo \
> +overlays/w1-gpio.dtbo \
> +overlays/w1-gpio-pullup.dtbo \
> +overlays/pi3-miniuart-bt.dtbo \
> +"
> +
> +def cmpver_strings(ver1, ver2, truevalue, falsevalue):
> +from distutils.version import LooseVersion
> +ver1 = ''.join(ch for ch in ver1 if ch in '0123456789.')
> +ver2 = ''.join(ch for ch in ver2 if ch in '0123456789.')
> +if LooseVersion(ver1) >= LooseVersion(ver2):
> +return truevalue
> +else:
> +return falsevalue
> +
> +KERNEL_DEVICETREE ?= 
> "${@cmpver_strings("${PREFERRED_VERSION_linux-raspberrypi}", "4.4", 
> "${KERNEL_DEVICETREE_OVERLAYS_DTBO}", "${KERNEL_DEVICETREE_OVERLAYS_DTB}")}"
> +
>  KERNEL_IMAGETYPE ?= "Image"
>

Can we avoid this duplication by translating dtbo->dtb for kernels
before 4.4? And I would suggest doing this in
linux-raspberrypi-base.bbclass . What do you think? We should reuse code
there for version too.

>  MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen alsa 
> bluetooth wifi sdio"
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Andrei Gherzan]

On Tue, May 31, 2016 at 04:46:34AM +0800, Herve Jourdain wrote:
> Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of 
> .dtb.
> Patch the kernel, which has faulty rules to generate .dtbo the way yocto does
>

You need an Upstream status here:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
I think this would be interesting to send upstream too.

> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  .../0001-fix-dtbo-rules.patch  | 27 
> ++
>  1 file changed, 27 insertions(+)
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
>
> diff --git 
> a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch 
> b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> new file mode 100644
> index 000..ef04a72
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> @@ -0,0 +1,27 @@
> +diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> +index a2e7cf7..673c1cb 100644
> +--- a/arch/arm/Makefile
>  b/arch/arm/Makefile
> +@@ -333,6 +333,8 @@ $(INSTALL_TARGETS):
> +
> + %.dtb: | scripts
> + $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
> ++%.dtbo: | scripts
x> ++   $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
> +
> + PHONY += dtbs dtbs_install
> +
> +diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> +index 3079c4f..6cc3766 100644
> +--- a/scripts/Makefile.lib
>  b/scripts/Makefile.lib
> +@@ -293,7 +293,8 @@ $(obj)/%.dtb: $(src)/%.dts FORCE
> + $(call if_changed_dep,dtc)
> +
> + quiet_cmd_dtco = DTCO$@
> +-cmd_dtco = $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; 
> \
> ++cmd_dtco = mkdir -p $(dir ${dtc-tmp}) ; \
> ++$(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
> + $(objtree)/scripts/dtc/dtc -@ -H epapr -O dtb -o $@ -b 0 \
> + -i $(dir $<) $(DTC_FLAGS) \
> + -d $(depfile).dtc.tmp $(dtc-tmp) ; \
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v4 5/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Andrei Gherzan]

On Tue, May 31, 2016 at 04:46:35AM +0800, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index ba47b22..789fef1 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -4,5 +4,6 @@ LINUX_VERSION ?= "4.4.9"
>
>  SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
> +   file://0001-fix-dtbo-rules.patch \
>  "
>  require linux-raspberrypi.inc
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Can we merge this patch in the 4th one? Only if you decide to push
another version based on other comments.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v4 0/5] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

[Andrei Gherzan]

On Tue, May 31, 2016 at 04:46:30AM +0800, Herve Jourdain wrote:
> v4: rebased
> For kernels 4.4.9+, the behavior for the device tree overlays loading has 
> been modified on RaspberryPi.
> For overlays, it loads .dtbo files, not .dtb anymore.
> Also, it does not check for -overlay extension, so the name of the overlay 
> that is placed in the "overlays" directory must be .dtbo, 
> instead of -overlay.dtb.
>
> This patch addresses the issue for kernels 4.4+, while keeping the same 
> behavior for older kernels.
> This patch must be used in conjunction with another patch to 
> meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo 
> files for overlays, instead of only .dtb like before.
>

Is the poky patch merged? It doesn't seem it was.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi.inc: KERNEL_OUTPUT has been removed in kernel.bbclass

[Andrei Gherzan]

Hi,

On Tue, May 31, 2016 at 07:58:59PM +0800, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc | 8 ++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 4799c74..6133b02 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -66,7 +66,9 @@ do_rpiboot_mkimage() {
>  if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
>  if test -n "${KERNEL_DEVICETREE}"; then
>  # Add RPi bootloader trailer to kernel image to enable 
> DeviceTree support
> -${STAGING_BINDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT} 
> ${KERNEL_OUTPUT}
> +for type in ${KERNEL_IMAGETYPES} ; do
> +${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
> ${KERNEL_OUTPUT_DIR}/$type ${KERNEL_OUTPUT_DIR}/$type
> +done
>  fi
>  fi
>  }
> @@ -76,7 +78,9 @@ do_bundle_initramfs_append() {
>  if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
>  if test -n "${KERNEL_DEVICETREE}"; then
>  # Add RPi bootloader trailer to kernel image to enable 
> DeviceTree support
> -${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
> ${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
> +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

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/2] linux-raspberrypi: Fix v4.1 with GCC6

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 ...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 <raj.k...@gmail.com>
+---
+ 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 <and...@gherzan.ro>
+
+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_goto(x...)   do { asm goto(x); asm (""); } while (0)
++
++#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP
++#define __HAVE_BUILTIN_BSWAP32__
++#define __HAVE_BUILTIN_BSWAP64__
++#define __HA

[yocto] [PATCH 1/2] packagegroup-rpi-test: Poky moved the license so fix LIC_FILES_CHKSUM

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 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

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

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi: Prevent taskhash mismatch

[Andrei Gherzan]

Hi Paul,

On Wed, Jun 08, 2016 at 02:02:29PM +0100, Paul Barker wrote:
> As recently discussed on the mailing list, bitbake now issues an error when 
> the
> task hash computed by the bitbake master differs from the task hash computed 
> by
> the bitbake worker. This usually happens when the task hash depends on the 
> date
> and time for some reason.
>
> This affects IMAGE_CMD_rpi-sdimg and is fixed by excluding the dependency on 
> the
> current date and time from the command.
>
> Signed-off-by: Paul Barker <p...@paulbarker.me.uk>
> ---
>  classes/sdcard_image-rpi.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/classes/sdcard_image-rpi.bbclass 
> b/classes/sdcard_image-rpi.bbclass
> index 3b4f13f..a8d83a3 100644
> --- a/classes/sdcard_image-rpi.bbclass
> +++ b/classes/sdcard_image-rpi.bbclass
> @@ -72,7 +72,7 @@ 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 () {

I can't seem to replicate this issue with currrent poky master. Any idea
why? Maybe this got fixed in poky?



--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] omxplayer: fix compilation with GCC 6

[Andrei Gherzan]

Hi,

On Wed, Jun 08, 2016 at 12:57:13AM +1000, Jonathan Liu wrote:
> Specifying -isystem${STAGING_DIR_HOST}/usr/include in INCLUDES gives:
>
> In file included from utils/PCMRemap.cpp:26:0:
> .../build/tmp/sysroots/raspberrypi2/usr/include/c++/6.1.1/cstdlib:75:25: 
> fatal error: stdlib.h: No such file or directory
>  #include_next 
>  ^
> compilation terminated.
> Makefile:44: recipe for target 'utils/PCMRemap.o' failed
>
> To resolve this, /usr/include shouldn't be specified as it is already a
> default include path relative to the sysroot.
>
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129.
>
> Signed-off-by: Jonathan Liu <net...@gmail.com>

Pushed to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-rpi: ensure config file is closed

[Andrei Gherzan]

Hello,

On Sun, Jun 05, 2016 at 01:38:52AM +1000, Jonathan Liu wrote:
> Avoids warnings like this with python3:
>
> WARNING: 
> .../meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_3.18.bb: 
> :16: ResourceWarning: unclosed file <_io.TextIOWrapper 
> name='.../meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig' 
> mode='r' encoding='UTF-8'>
>
> Signed-off-by: Jonathan Liu <net...@gmail.com>
> ---
>  recipes-kernel/linux/linux-rpi.inc | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/recipes-kernel/linux/linux-rpi.inc 
> b/recipes-kernel/linux/linux-rpi.inc
> index 1755685..4b65fc2 100644
> --- a/recipes-kernel/linux/linux-rpi.inc
> +++ b/recipes-kernel/linux/linux-rpi.inc
> @@ -133,4 +133,6 @@ python () {
>  if 'CONFIG_KERNEL_LZO=y\n' in configfile.readlines():
>  depends = d.getVar('DEPENDS', False)
>  d.setVar('DEPENDS', depends + ' lzop-native')
> +
> +configfile.close()
>  }
> https://lists.yoctoproject.org/listinfo/yocto

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] ***SPAM*** Re: [meta-raspberrypi][PATCH 5/8] Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10

[Andrei Gherzan]

On Fri, May 20, 2016 at 12:47:40PM +0200, Herve Jourdain wrote:
> Hi Andrei, Khem,
>
> That's what I implemented in the upcoming v2 - except for the python
> checking function part.
> One thing, shall I call the variable CMA_SIZE, or VC4_CMA_SIZE?
> I know CMA is kind of common, but we're using this only to trigger a
> parameter to the v4c overlay.
> Any opinion? (in the current implementation, I went with CMA_SIZE, but I
> have doubts...)
>

Hint: Try to reply in line if possible. It is easier to follow the
discussion in this way.

I would vote for VC4_CMA_SIZE. It sounds safer.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 5/8] Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10

[Andrei Gherzan]

On Thu, May 19, 2016 at 09:02:04AM -0700, Khem Raj wrote:
> On Thu, May 19, 2016 at 8:11 AM, Andrei Gherzan <and...@gherzan.ro> wrote:
> > On Wed, May 18, 2016 at 11:46:39PM +0200, Andreas Müller wrote:
> >> On Wed, May 18, 2016 at 7:32 PM, Herve Jourdain <herve.jourd...@neuf.fr> 
> >> wrote:
> >> > One thing I didn't make configurable, but that maybe could be, is the 
> >> > parameter passed to the overlay.
> >> > I selected cma-256, based on experience from other people, and because 
> >> > my configuration is RPI2/3 with 1G of memory.
> >> > I realize it might not work well with RPI0/1, which have less memory 
> >> > available...
> >> > So even if I believe cma-256 is a good default value, it might be made 
> >> > selectable by the user, if we want to consider vc4 on RPI0/1.
> >> I played around with vc4 to but did not manage to get it work for an
> >> elder version 4.1 of kernel.
> >>
> >> I did in rpi-config:
> >>
> >> CMA_SIZE = "cma-256"
> >> CMA_SIZE_raspberrypi = "cma-64"
>
>
> >
> > I sent reply about this too. This is definitely one solution would I
> > would rather have a CMA_SIZE default value and a python function to
> > check its match with board variant. Cause in this way a user might be
> > able to use cma-96 on rapsberrypi.
> >
> >> CMA_SIZE_raspberrypi0 = "cma-128"
>
>
> setting CMA_SIZE should be moved into machine.conf file IMO
>

That's actually a good idea. I would say to have it in machine as a
default value for that specific machine. And then be able to overwrite
it as user needs. Optionally have a python function to check that what
user requested makes sense for the selected board.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Andrei Gherzan]

On Thu, May 19, 2016 at 09:40:13AM -0700, Khem Raj wrote:
>
> > On May 19, 2016, at 8:27 AM, Andrei Gherzan <and...@gherzan.ro> wrote:
> >
> > On Thu, May 19, 2016 at 05:26:15PM +0200, piotr.lewicki wrote:
> >> On 19.05.2016 16:39, Andrei Gherzan wrote:
> >>> On Thu, May 19, 2016 at 02:15:22PM +0200, piotr.lewicki wrote:
> >>>> Hello,
> >>>> I'm trying to build a Yocto image for raspberrypi3.
> >>>> I'm using only two layers:
> >>>> - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842)
> >>>> - meta-raspberrypi (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.
> >>>>
> >>> I just tested the same revisions as you mentioned and the board boot for
> >>> me. How do you test the board? Over serial?
> >>>
> >>> If you are using serial I suspecte you are not setting the serial
> >>> console. if you are using tty1 (hdmi) you need to add the specific
> >>> console argument to cmdline.
> >> I'm using hdmi. Where can I find those console arguments?
> >
> > Boot partition, cmdline.txt.
> >
> >>>
> >>>> 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?
> >>>>
> >>> What do you mean rpi is not following the yocto project naming
> >>> convention? It does miss a branch for the last yocto release but there
> >>> are already for the old ones.
> >> Maybe I explained that wrong, but I've noticed that it's missing krogoth
> >> branch.
> >> I think that if something like this occurs users are a little bit confused
> >> and have to choose between old branch (potentially outdated) and a master
> >> branch (potentially unstable).
> >
> > Correct. I'll release krogoth too soon. Thanks.
>
>
> I would suggest to delay branching until we really diverge from krogoth in 
> incompatible ways
> just makes it easier to maintain.

Indeed. Sounds like a good idea.


--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-rpi: Enable kconf options to enable initramfs support

[Andrei Gherzan]

On Thu, May 12, 2016 at 10:43:03PM -0700, Khem Raj wrote:
> Additionally add few few file systems e.g. squashfs, overlayfs
> to support booting with initramfs
>
> Drop checking for target triplet to set EABI, rpi probaly should
> not have any legacy into OABI world.
>

Merged both to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Andrei Gherzan]

On Thu, May 19, 2016 at 05:26:15PM +0200, piotr.lewicki wrote:
> On 19.05.2016 16:39, Andrei Gherzan wrote:
> > On Thu, May 19, 2016 at 02:15:22PM +0200, piotr.lewicki wrote:
> > > Hello,
> > > I'm trying to build a Yocto image for raspberrypi3.
> > > I'm using only two layers:
> > > - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842)
> > > - meta-raspberrypi (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.
> > >
> > I just tested the same revisions as you mentioned and the board boot for
> > me. How do you test the board? Over serial?
> >
> > If you are using serial I suspecte you are not setting the serial
> > console. if you are using tty1 (hdmi) you need to add the specific
> > console argument to cmdline.
> I'm using hdmi. Where can I find those console arguments?

Boot partition, cmdline.txt.

> >
> > > 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?
> > >
> > What do you mean rpi is not following the yocto project naming
> > convention? It does miss a branch for the last yocto release but there
> > are already for the old ones.
> Maybe I explained that wrong, but I've noticed that it's missing krogoth
> branch.
> I think that if something like this occurs users are a little bit confused
> and have to choose between old branch (potentially outdated) and a master
> branch (potentially unstable).

Correct. I'll release krogoth too soon. Thanks.

> >
> > > 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
> > --
> > Andrei Gherzan
> __
>
> BR,
> Piotr Lewicki

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] userland: Update to tip of tree

[Andrei Gherzan]

On Fri, May 13, 2016 at 09:32:32AM -0700, Khem Raj wrote:
> Drop the patch which is upstreamed slightly differently
> use VMCS_INSTALL_PREFIX to /usr via EXTRA_OECMAKE
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>

Merged to master. Thanks.
--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 5/8] Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10

[Andrei Gherzan]

On Wed, May 18, 2016 at 11:46:39PM +0200, Andreas Müller wrote:
> On Wed, May 18, 2016 at 7:32 PM, Herve Jourdain <herve.jourd...@neuf.fr> 
> wrote:
> > One thing I didn't make configurable, but that maybe could be, is the 
> > parameter passed to the overlay.
> > I selected cma-256, based on experience from other people, and because my 
> > configuration is RPI2/3 with 1G of memory.
> > I realize it might not work well with RPI0/1, which have less memory 
> > available...
> > So even if I believe cma-256 is a good default value, it might be made 
> > selectable by the user, if we want to consider vc4 on RPI0/1.
> I played around with vc4 to but did not manage to get it work for an
> elder version 4.1 of kernel.
>
> I did in rpi-config:
>
> CMA_SIZE = "cma-256"
> CMA_SIZE_raspberrypi = "cma-64"

I sent reply about this too. This is definitely one solution would I
would rather have a CMA_SIZE default value and a python function to
check its match with board variant. Cause in this way a user might be
able to use cma-96 on rapsberrypi.

> CMA_SIZE_raspberrypi0 = "cma-128"
> ...
> echo "dtoverlay=vc4-kms-v3d-overlay,${CMA_SIZE}"
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>
> This is nothing but an untested suggestion.
>
> Without testing your series I would be very happy to see this or very
> similar applied in master: Since vc4 works, RaspberryPi turned into my
> reference test board - e.g. have not seen kde5 running that nice on
> another board..
>
> Andreas
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 5/8] Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10

[Andrei Gherzan]

On Thu, May 19, 2016 at 08:28:00AM +0200, Andreas Müller wrote:
> On Thu, May 19, 2016 at 7:21 AM, Herve Jourdain <herve.jourd...@neuf.fr> 
> wrote:
> > Hi Andreas,
> >
> > I've been able to do some testing with the latest 4.1 kernel.
> > So it can actually "work" in a way, but both the device tree overlay and 
> > the driver in the kernel are "old".
> > This has an impact on stability: I can definitely start wayland/weston, and 
> > it's "responsive", BUT after I started playing out with the demo 
> > applications, it quickly crashed...
> > So we could either try to backport the newer driver / dt overlay to the 
> > 4.1, which could be possible, or we could just support vc4graphics only for 
> > 4.4.10+...
> >
> > Since 4.1 is not heavily maintained anymore on github, since 4.4 is now the 
> > default revision on github, and since development branches for 4.5 and 4.6 
> > are already there on github, I would personally be inclined to support 
> > vc4graphics only for 4.4.10+...
> > And I would also be in favor of moving the default version of the kernel to 
> > the 4.4 series...
> >
> > What do you think is the best option there?
> >
> No need to backport to 4.1. 4.4 is fine. One question: are you able to
> change screen resolution for HDMI monitor (elder sdl fullscreen games
> need that)? This was not possible for kernel 4.1.
>
> Just to avoid misunderstandings: I like this patch series very much
> and would be happy to see it applied.
>

Santa heard you.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/8] Support for vc4 graphics driver: add vc4-kms-v3d to the overlays

[Andrei Gherzan]

On Wed, May 18, 2016 at 08:21:16PM +0800, Herve Jourdain wrote:
> This patch series enables the support for the VC4 graphics driver from Eric 
> Anholt.
> Add vc4-kms-v3d overlay if 'vc4graphics' is in MACHINE_FEATURES.
> (This patch has a dependency on the patch that enables the support of .dtbo 
> overlay files)
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-bsp/bootfiles/rpi-config_git.bb | 8 
>  1 file changed, 8 insertions(+)
>
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index 4bc8eb7..79e436d 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -19,6 +19,8 @@ PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", 
> "1", "0", d)}"
>  PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
>  PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
>
> +VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
> "0", d)}"
> +
>  inherit deploy
>
>  do_deploy() {
> @@ -102,6 +104,12 @@ do_deploy() {
>  echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +
> +# VC4 Graphics support
> +if [ "${VC4GRAPHICS}" = "1" ]; then
> +echo "# Enable VC4 Graphics" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtoverlay=vc4-kms-v3d,cma-256" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt

This is definitely not a good idea on rpi0/1. Let's select this based
on RPI version:
CMA_USAGE_raspberrypi = "cma-128"

Or we can set a default variable on this configurable by user. But I
would like to have a warning mechanism. Maybe a python function that
will check if we want to build rpi1 and cma-256 was selected issue a
warning.

> +fi
>  }
>
>  addtask deploy before do_package after do_install
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/8] Support for vc4 graphics driver: add vc4-kms-v3d to the overlays

[Andrei Gherzan]

On Thu, May 19, 2016 at 01:25:34AM +0800, Herve Jourdain wrote:
> Hi Khem,
>
> Well, it seems to be the way it will be activated in the future as well, 
> through a device tree overlay.
> The rationale being that people may not want/need the VC4 driver, because 
> they prefer to use userland or other reasons, and that only the persons who 
> want to activate it will load the overlay.
> One thing to remember is that vc4 has the potential to conflict with other 
> pieces, and it might not be for everybody (the firmware patch helps in that 
> regards, but before it, weston/drm was conflicting with the splash screen for 
> instance on my test setup, creating very disturbing images).
>
> If your question is, will userland disappear one day and vc4 graphics 
> becoming the only graphics driver, the overlay could be included in the base 
> device tree itself, in like a few years from now, then I clearly don't have 
> an answer to that...
>
> But I believe the overlay will stick some time around.
>

I'm not sure if this is what Raj asked about. Needs some clarification.

> Herve
>
> > Le 19 mai 2016 à 00:53, Khem Raj <raj.k...@gmail.com> a écrit :
> >
> >
> >> On May 18, 2016, at 5:21 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote:
> >>
> >> This patch series enables the support for the VC4 graphics driver from 
> >> Eric Anholt.
> >> Add vc4-kms-v3d overlay if 'vc4graphics' is in MACHINE_FEATURES.
> >> (This patch has a dependency on the patch that enables the support of 
> >> .dtbo overlay files)
> >>
> >> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> >> ---
> >> recipes-bsp/bootfiles/rpi-config_git.bb | 8 
> >> 1 file changed, 8 insertions(+)
> >>
> >> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> >> b/recipes-bsp/bootfiles/rpi-config_git.bb
> >> index 4bc8eb7..79e436d 100644
> >> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> >> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> >> @@ -19,6 +19,8 @@ PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", 
> >> "1", "0", d)}"
> >> PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
> >> PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", 
> >> d)}"
> >>
> >> +VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
> >> "0", d)}"
> >> +
> >> inherit deploy
> >>
> >> do_deploy() {
> >> @@ -102,6 +104,12 @@ do_deploy() {
> >>echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> >>echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> >>fi
> >> +
> >> +# VC4 Graphics support
> >> +if [ "${VC4GRAPHICS}" = "1" ]; then
> >> +echo "# Enable VC4 Graphics" 
> >> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> >> +echo "dtoverlay=vc4-kms-v3d,cma-256" 
> >> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> >> +fi
> >
> >
> > will this keep appending overtime ?
> >
> >> }
> >>
> >> addtask deploy before do_package after do_install
> >> --
> >> 2.7.4
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/8] Support for vc4 graphics driver: add vc4-kms-v3d to the overlays

[Andrei Gherzan]

On Wed, May 18, 2016 at 08:21:16PM +0800, Herve Jourdain wrote:
> This patch series enables the support for the VC4 graphics driver from Eric 
> Anholt.
> Add vc4-kms-v3d overlay if 'vc4graphics' is in MACHINE_FEATURES.
> (This patch has a dependency on the patch that enables the support of .dtbo 
> overlay files)
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-bsp/bootfiles/rpi-config_git.bb | 8 
>  1 file changed, 8 insertions(+)
>
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index 4bc8eb7..79e436d 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -19,6 +19,8 @@ PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", 
> "1", "0", d)}"
>  PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
>  PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
>
> +VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
> "0", d)}"
> +
>  inherit deploy
>
>  do_deploy() {
> @@ -102,6 +104,12 @@ do_deploy() {
>  echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +
> +# VC4 Graphics support
> +if [ "${VC4GRAPHICS}" = "1" ]; then
> +echo "# Enable VC4 Graphics" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtoverlay=vc4-kms-v3d,cma-256" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt

NIT: space after >>

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/8] Support for vc4 graphics driver: modify the wayland configuration for vc4

[Andrei Gherzan]

On Wed, May 18, 2016 at 08:21:20PM +0800, Herve Jourdain wrote:
> This patch series enables the support for the VC4 graphics driver from Eric 
> Anholt.
> Configure the configuration options for Wayland, depending on whether 
> 'vc4graphics' is in MACHINE_FEATURES or not.
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-graphics/wayland/weston_%.bbappend | 7 +++
>  1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/recipes-graphics/wayland/weston_%.bbappend 
> b/recipes-graphics/wayland/weston_%.bbappend
> index c3a7421..76bab9f 100644
> --- a/recipes-graphics/wayland/weston_%.bbappend
> +++ b/recipes-graphics/wayland/weston_%.bbappend
> @@ -1,4 +1,3 @@
> -EXTRA_OECONF_append_rpi = "\
> ---enable-rpi-compositor \
> -WESTON_NATIVE_BACKEND=rpi-backend.so \
> -   "
> +EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
> 'vc4graphics', '', ' --enable-rpi-compositor', d)}"
> +EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
> 'vc4graphics', '', ' WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"

Wondering if having this in one line would be better.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/8] Support for vc4 graphics driver: change the default providers

[Andrei Gherzan]

Hello,

Try to keep the commit log format as we currently have the layer.
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

On Wed, May 18, 2016 at 08:21:15PM +0800, Herve Jourdain wrote:
> This patch series enables the support for the VC4 graphics driver from Eric 
> Anholt.
> Configure the default providers, depending on whether 'vc4graphics' is in 
> MACHINE_FEATURES or not.
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  conf/machine/include/rpi-default-providers.inc | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> 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)}"
> +PREFERRED_PROVIDER_virtual/libgles2 ?= 
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "userland", 
> d)}"
> +PREFERRED_PROVIDER_virtual/libgl ?= 
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "mesa-gl", 
> d)}"
> +PREFERRED_PROVIDER_virtual/mesa ?= "${@bb.utils.contains("MACHINE_FEATURES", 
> "vc4graphics", "mesa", "mesa-gl", d)}"
>  PREFERRED_PROVIDER_jpeg ?= "jpeg"
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 0/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12

[Andrei Gherzan]

On Thu, May 19, 2016 at 09:43:47AM +0200, Herve Jourdain wrote:
> Hi,
>
> Sorry, it seems there has been some mismatch in my test setup...
> So while .dtbo are required for 4.4.9+, there NOT to be used for 4.1.21 it
> seems...
> I will therefore send soon a v3 patchset, that will work fine for 4.4
> (what's laid out here is needed for 4.4) without breaking overlay support
> for 4.1.
>

I was just about to send you an email about this. It's fine. Let's fix
it in v3.
--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Andrei Gherzan]

On Thu, May 19, 2016 at 02:15:22PM +0200, piotr.lewicki wrote:
> Hello,
> I'm trying to build a Yocto image for raspberrypi3.
> I'm using only two layers:
> - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842)
> - meta-raspberrypi (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.
>

I just tested the same revisions as you mentioned and the board boot for
me. How do you test the board? Over serial?

If you are using serial I suspecte you are not setting the serial
console. if you are using tty1 (hdmi) you need to add the specific
console argument to cmdline.

> 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?
>

What do you mean rpi is not following the yocto project naming
convention? It does miss a branch for the last yocto release but there
are already for the old ones.

> 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

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] replace base_contains by bb.utils.contains

[Andrei Gherzan]

On Sat, Apr 30, 2016 at 02:09:24PM +0200, Andreas Müller wrote:
> Signed-off-by: Andreas Müller <schnitzelt...@googlemail.com>
> ---
>  recipes-connectivity/bluez5/bluez5_%.bbappend | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend 
> b/recipes-connectivity/bluez5/bluez5_%.bbappend
> index eec52e0..89798a4 100644
> --- a/recipes-connectivity/bluez5/bluez5_%.bbappend
> +++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
> @@ -13,7 +13,7 @@ do_install_append_raspberrypi3() {
>  install -d ${D}/lib/firmware/brcm/
>  install -m 0644 ${WORKDIR}/BCM43430A1.hcd 
> ${D}/lib/firmware/brcm/BCM43430A1.hcd
>
> -if ${@base_contains('DISTRO_FEATURES', 'systemd', 'true', 'false', d)}; 
> then
> +if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', 
> d)}; then
>  install -d ${D}${systemd_unitdir}/system
>  install -m 0644 ${WORKDIR}/brcm43438.service 
> ${D}${systemd_unitdir}/system
>  fi

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix do_image_rpi_sdimg tashhash mismatch

[Andrei Gherzan]

On Fri, Apr 29, 2016 at 11:57:43AM +1000, Jonathan Liu wrote:
> IMAGE_CMD_rpi-sdimg() uses the IMAGEDATESTAMP variable, so the taskhash
> of the function keeps changing. This results in a taskhash mismatch
> error.
>
> Fix this by excluding the IMAGEDATESTAMP variable from the checksum.
>
> Change-Id: Ie6f30ad29e279d5312ec655ac4a3bf246c8a04de
> Signed-off-by: Jonathan Liu <net...@gmail.com>
> ---
>  classes/sdcard_image-rpi.bbclass | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/classes/sdcard_image-rpi.bbclass 
> b/classes/sdcard_image-rpi.bbclass
> index 1b055bd..989d77a 100644
> --- a/classes/sdcard_image-rpi.bbclass
> +++ b/classes/sdcard_image-rpi.bbclass
> @@ -67,6 +67,7 @@ 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 () {
>

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] README: Switch from redmine to github issues

[Andrei Gherzan]

On Mon, Apr 25, 2016 at 10:10:40AM +0200, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  README | 15 ++-
>  1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/README b/README
> index 5a6a0d9..c39f9ed 100644
> --- a/README
> +++ b/README
> @@ -332,18 +332,15 @@ When sending patches to mailing list, please use 
> something like:
>
>  git send-email --to yocto@yoctoproject.org 
>
> -7.B. Redmine
> -
> -In order to manage and trace the meta-raspberrypi issues, we use redmine:
> -http://redmine.gherzan.ro/projects/meta-raspberrypi
> -
> -Here we report, trace and develop bugs, features or support tickets for this
> -yocto BSP later.
> +7.B. Github issues
> +==
> +In order to manage and trace the meta-raspberrypi issues, we use github 
> issues:
> +https://github.com/agherzan/meta-raspberrypi/issues
>
> -If you push patches which have a redmine issue associated, please provide the
> +If you push patches which have a github issue associated, please provide the
>  issue number in the commit log just before "Signed-off-by" line(s). Example 
> line
>  for a bug:
> -[Bug #13]
> +[Issue #13]
>
>
>  8. Maintainers
> --
> 2.8.0
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] u-boot-rpi2: use the upstreamed U-Boot

[Andrei Gherzan]

Hi Steve,

On Mon, Jan 25, 2016 at 04:32:27PM -0800, Steve Rae wrote:
>
>
> On 16-01-25 01:32 PM, Khem Raj wrote:
> > Hi Steve
> >
> > > On Jan 25, 2016, at 1:00 PM, Steve Rae <s...@broadcom.com> wrote:
> > >
> > > For Raspberry Pi 2, use the U-Boot from "den".
> >
> >
> > Can this be done by using/extending OE-Core recipe please ?
> >
> >
>
> I modelled it after the existing RPi recipe:
> diff recipes-bsp/u-boot/u-boot-rpi_git.bb
> recipes-bsp/u-boot/u-boot-rpi2_git.bb
> sorry -- I don't know enough about this to answer your question...
> Which recipe should I "extend"? Could you please provide more details?
> Thanks in advance, Steve

Khem Raj is proposing to use a uboot recipe from oe-core
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot
and extend it with a bbappend to include rpi support. Is that possible?

P.S.: Sorry for this late reply. I'm trying to catch up with some old
threads.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] README: Switch from redmine to github issues

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 README | 15 ++-
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/README b/README
index 5a6a0d9..c39f9ed 100644
--- a/README
+++ b/README
@@ -332,18 +332,15 @@ When sending patches to mailing list, please use 
something like:
 
 git send-email --to yocto@yoctoproject.org 
 
-7.B. Redmine
-
-In order to manage and trace the meta-raspberrypi issues, we use redmine:
-http://redmine.gherzan.ro/projects/meta-raspberrypi
-
-Here we report, trace and develop bugs, features or support tickets for this
-yocto BSP later.
+7.B. Github issues
+==
+In order to manage and trace the meta-raspberrypi issues, we use github issues:
+https://github.com/agherzan/meta-raspberrypi/issues
 
-If you push patches which have a redmine issue associated, please provide the
+If you push patches which have a github issue associated, please provide the
 issue number in the commit log just before "Signed-off-by" line(s). Example 
line
 for a bug:
-[Bug #13]
+[Issue #13]
 
 
 8. Maintainers
-- 
2.8.0

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

Re: [yocto] [meta-raspberrypi][PATCH] Change serial console for Raspberry Pi 3

[Andrei Gherzan]

Hi Martin,

On Tue, Apr 05, 2016 at 09:08:54AM +0200, Martin Bergek wrote:
> With the Raspberry Pi 3 the serial ports ttyS0 and ttyAMA0 have been switched 
> around. This causes an issue with the serial console that has previously been 
> set to ttyAMA0, causing the boot process to halt. I have a 100% failure rate 
> when booting a Raspberry Pi 3 image built using the master branch of 
> meta-raspberrypi. After a lot of testing it appears that the system fails to 
> boot whenever the kernel command line specifies a console - regardless of 
> whether it is ttyAMA0 or ttyS0.
>
> This patch changes the serial console and kernel command line to use default 
> values, allowing the raspberrypi3 machine configuration to assign different 
> values and to remove the kernel console. Now I get the console output to the 
> screen but at least it boots. Not sure if this is an acceptable way of doing 
> it but it fixed my problem.
>
> This patch has been verified on both the 4.1 and 4.4 kernel. It has also been 
> tested with the raspberrypi2 machine configuration.
>
> Signed-off-by: Martin Bergek 
> ---
> conf/machine/include/rpi-base.inc  | 2 +-
> conf/machine/raspberrypi3.conf | 4 
> recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
> 3 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 792150e..5d6280b 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -7,7 +7,7 @@ include conf/machine/include/soc-family.inc
>
> IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"
>
> -SERIAL_CONSOLE = "115200 ttyAMA0"
> +SERIAL_CONSOLE ?= "115200 ttyAMA0"
>
> XSERVER = " \
> xserver-xorg \
> diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> index 1b73f2f..2c76dc2 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -6,4 +6,8 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
>
> MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
>
> +# Change serial console due to swapped ttyAMA0 and ttyS0 on the Raspberry Pi 
> 3
> +SERIAL_CONSOLE = "115200 ttyS0"
> +CMDLINE = "dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
> +
> include conf/machine/raspberrypi2.conf
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 24e7fe2..a3fe61a 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
> KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
>
> # CMDLINE for raspberrypi
> -CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
> rootfstype=ext4 rootwait"
> +CMDLINE ?= "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
> rootfstype=ext4 rootwait"
>
> # Add the kernel debugger over console kernel command line option if enabled
> CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
> "kgdboc=ttyAMA0,115200", "", d)}'

This issue was fixed in master using serial0 magic string and the new
firmware. This will unlock your serial console. Be aware that you will
need to use enable_uart to force core_freq.

Cheers!

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] userland: fix wayland PACKAGECONFIG

[Andrei Gherzan]

Hi Jonathan,

On Wed, Apr 13, 2016 at 06:09:55PM +1000, Jonathan Liu wrote:
> The wayland-native dependency was not added correctly.
>
> Signed-off-by: Jonathan Liu <net...@gmail.com>
> ---
>  recipes-graphics/userland/userland_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index ef06b12..2fdfeed 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
> -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
>
>  PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
> 'wayland', '', d)}"
>
> -PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
> +PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland
>  wayland-native"
>
>  CFLAGS_append = " -fPIC"

Master has a similar commit merged. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

[Andrei Gherzan]

Hi Trevor,

On Wed, Apr 13, 2016 at 06:04:28PM -0400, Trevor Woerner wrote:
> On Wed 2016-03-30 @ 04:35:47 PM, Petter Mabäcker wrote:
> > rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
> > touchscreen support.
>
> I have an official raspberry pi 7" touchscreen and it's not obvious to me how
> I would go about enabling it in my config. If I had one of the others I would
> simply add:
>
>   MACHINE_FEATURES += "pitft pitft22"
>
> or
>
>   MACHINE_FEATURES += "pitft pitft28r"
>
> to my conf/local.conf, but what do I do for the official touchscreen?
>
> Also, by trial and error I've discovered that my touchscreen comes up as
> /dev/fb0 and not /dev/fb1. But the xorg config for touchscreen support assumes
> /dev/fb1. Am I doing something wrong in my build or can anyone think of a
> reason why my screen would be /dev/fb0 instead of /dev/fb1?
>
> By the way
>
>   MACHINE_FEATURES += "pitft pitft22"
>
> seems to work for me if I use /dev/fb0, but I'm not sure if that's a fluke?
>

Sorry for not being able to follow this thread. Did you manage to make
it work?


Regards,
--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Bump to v4.4.7

[Andrei Gherzan]

On Fri, Apr 22, 2016 at 04:46:11PM +0200, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index 8e4530f..9cb8aae 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.4.6"
> +LINUX_VERSION ?= "4.4.7"
>
> -SRCREV = "2faaa2ccef9e4c595bd26f14285c225ceea6097e"
> +SRCREV = "3de232825c9ba5989522b8691eb6ac5df6619458"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
>     file://0001-dts-add-overlay-for-pitft22.patch \
>  "
> --
> 2.8.0
>

Merged this series to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] rpi-base.inc: Include pi3-miniuart-bt-overlay.dtb

[Andrei Gherzan]

This is used to switch BT from ttyUSB0 to ttyS0 (miniUART).

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index f64bc9d..56ca83e 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -36,6 +36,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/rpi-ft5406-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
+overlays/pi3-miniuart-bt-overlay.dtb \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 4/5] bluez5: Add bluez5 support for brcm43438 on raspberrypi3.

[Andrei Gherzan]

From: toolmmy <tool...@gmail.com>

This patch adds the bluetooth support for the brcm43438 module on the 
raspberrypi3 by
deploying the modules firmware and changing the targeting firmware path. In 
addition
the brcm43438.service adds the automatically attaching (hciattach) for systemd 
environments.
The following steps can be used to manually configure the brcm43438:

root@raspberrypi3:~# hciattach /dev/ttyAMA0 bcm43xx-3wire
bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set Controller UART speed to 300 bit/s
Device setup complete
root@raspberrypi3:~# hciconfig
hci0:   Type: BR/EDR  Bus: UART
BD Address: B8:27:EB:6C:85:BE  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN
RX bytes:983 acl:0 sco:0 events:33 errors:0
TX bytes:887 acl:0 sco:0 commands:33 errors:0

root@raspberrypi3:~# /usr/lib/bluez5/bluetooth/bluetoothd -e -n -E
root@raspberrypi3:~# bluetoothctl
[NEW] Controller B8:27:EB:6C:85:BE raspberrypi3 [default]
[bluetooth]# power on
[CHG] Controller B8:27:EB:6C:85:BE Class: 0x40
Changing power on succeeded
[CHG] Controller B8:27:EB:6C:85:BE Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:6C:85:BE Discovering: yes
[NEW] Device 00:1C:05:FF:F9:F8 Nonin3230_501585326

NOTE: SERIAL_CONSOLE must configured to ttyS0 instead of ttyAMA0 (used by the 
brcm43438). See pending patch from Martin Bergek

Signed-off-by: Tom Doehring <tool...@gmail.com>
Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 .../0001-bcm43xx-Add-bcm43xx-3wire-variant.patch   |  26 +++
 ...-UART-speed-must-be-reset-after-the-firmw.patch |  37 +
 ...003-Increase-firmware-load-timeout-to-30s.patch |  25 ++
 ...-Move-the-43xx-firmware-into-lib-firmware.patch |  25 ++
 recipes-connectivity/bluez5/bluez5/BCM43430A1.hcd  | Bin 0 -> 35976 bytes
 .../bluez5/bluez5/brcm43438.service|  12 +++
 recipes-connectivity/bluez5/bluez5_%.bbappend  |  26 +++
 7 files changed, 151 insertions(+)
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0003-Increase-firmware-load-timeout-to-30s.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0004-Move-the-43xx-firmware-into-lib-firmware.patch
 create mode 100644 recipes-connectivity/bluez5/bluez5/BCM43430A1.hcd
 create mode 100644 recipes-connectivity/bluez5/bluez5/brcm43438.service
 create mode 100644 recipes-connectivity/bluez5/bluez5_%.bbappend

diff --git 
a/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
 
b/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
new file mode 100644
index 000..3bc02c4
--- /dev/null
+++ 
b/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
@@ -0,0 +1,26 @@
+From b4f2b77472aeb967d3a7595e8a965785c7a37c87 Mon Sep 17 00:00:00 2001
+From: Phil Elwell <p...@raspberrypi.org>
+Date: Tue, 16 Feb 2016 16:40:46 +
+Subject: [PATCH 1/4] bcm43xx: Add bcm43xx-3wire variant
+
+---
+ tools/hciattach.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/tools/hciattach.c b/tools/hciattach.c
+index 59a76a7..5861d33 100644
+--- a/tools/hciattach.c
 b/tools/hciattach.c
+@@ -1144,6 +1144,9 @@ struct uart_t uart[] = {
+   { "bcm43xx",0x, 0x, HCI_UART_H4,   115200, 300,
+   FLOW_CTL, DISABLE_PM, NULL, bcm43xx, NULL  },
+ 
++  { "bcm43xx-3wire",0x, 0x, HCI_UART_3WIRE, 115200, 300,
++  0, DISABLE_PM, NULL, bcm43xx, NULL  },
++
+   { "ath3k",0x, 0x, HCI_UART_ATH3K, 115200, 115200,
+   FLOW_CTL, DISABLE_PM, NULL, ath3k_ps, ath3k_pm  },
+ 
+-- 
+1.9.1
+
diff --git 
a/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
 
b/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
new file mode 100644
index 000..5a0a434
--- /dev/null
+++ 
b/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
@@ -0,0 +1,37 @@
+From e145c9621f976063e5c573db1f2053d906f63427 Mon Sep 17 00:00:00 2001
+From: Phil Elwell <p...@raspberrypi.org>
+Date: Tue, 16 Feb 2016 16:39:09 +
+Subject: [PATCH 2/4] bcm43xx: The UART speed must be reset after the firmware 
download
+
+---
+ tools/hciattach_bcm43xx.c | 6 ++
+ 1 file changed, 2 insertions(+), 4 deletions(-)
+
+diff --git a/tools/hciattach_bcm43xx.c b/tools/hciattach_bcm43xx.c
+index 81f38cb..0b792e0 100644
+--- a/tools/hciattach_bcm43xx.c
 b/tools/hciattach_bcm43xx.c
+@@ -366,11 +366,8 @@ int bcm43xx_init(int fd, int def_s

[yocto] [meta-raspberrypi][PATCH 3/5] packagegroup-rpi-test: Add packages to be able to test WiFi/Bluetooth

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 recipes-core/packagegroups/packagegroup-rpi-test.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb 
b/recipes-core/packagegroups/packagegroup-rpi-test.bb
index f33c05d..ae16cec 100644
--- a/recipes-core/packagegroups/packagegroup-rpi-test.bb
+++ b/recipes-core/packagegroups/packagegroup-rpi-test.bb
@@ -13,10 +13,15 @@ RDEPENDS_${PN} = "\
 pi-blaster \
 python-rtimu \
 python-sense-hat \
+connman \
+connman-client \
+crda \
+bluez5 \
 "
 
 RRECOMMENDS_${PN} = "\
 bigbuckbunny-1080p \
 bigbuckbunny-480p \
 bigbuckbunny-720p \
+${MACHINE_EXTRA_RRECOMMENDS} \
 "
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 2/5] linux-raspberrypi: Set baudrate and use serial0 for kgdboc

[Andrei Gherzan]

The driver for 8250 defaults to 9600. We setup it on 115200 to be consistent
with getty configuration.

The firmware can do its magic with kgdboc too as it searches and replaces
=serial0 and =serial1. So, use serial0 for kgdboc too.

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 recipes-kernel/linux/linux-raspberrypi.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index eccbbc6..4799c74 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,10 +20,10 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
 KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
 
 # CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=serial0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"
+CMDLINE = "dwc_otg.lpm_enable=0 console=serial0,115200 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"
 
 # Add the kernel debugger over console kernel command line option if enabled
-CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
"kgdboc=ttyAMA0,115200", "", d)}'
+CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
"kgdboc=serial0,115200", "", d)}'
 
 UDEV_GE_141 ?= "1"
 
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Bump to v4.4.7

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 8e4530f..9cb8aae 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.4.6"
+LINUX_VERSION ?= "4.4.7"
 
-SRCREV = "2faaa2ccef9e4c595bd26f14285c225ceea6097e"
+SRCREV = "3de232825c9ba5989522b8691eb6ac5df6619458"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-dts-add-overlay-for-pitft22.patch \
 "
-- 
2.8.0

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

Re: [yocto] [meta-raspberrypi][PATCH V2 1/4] firmware.inc: Update firmware to include various serial fixes

[Andrei Gherzan]

On Thu, Apr 21, 2016 at 08:42:36PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan <theo...@resin.io>
>
> Signed-off-by: Theodor Gherzan <theo...@resin.io>
> ---
>  recipes-bsp/common/firmware.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index c1117d6..abc7d06 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,5 +1,5 @@
> -RPIFW_SRCREV ?= "046effa13ebc4cc7601df4f06f4834bd0eebb0f8"
> -RPIFW_DATE ?= "20160326"
> +RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
> +RPIFW_DATE ?= "20160303"
>  RPIFW_SRC_URI ?= 
> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>  RPIFW_S ?= "${WORKDIR}/git"

Merged to master (along with the other patches in the series). Thanks.
Some minor modifications added (README).

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/5] firmware.inc: Update firmware to include various serial fixes

[Andrei Gherzan]

On Thu, Apr 21, 2016 at 06:32:10PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan <theo...@resin.io>
>
> Signed-off-by: Theodor Gherzan <theo...@resin.io>

Doesn't apply over over current master. Can you send a v2 without
Trevor's patch and with the updated one for README?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] serial console definition split

[Andrei Gherzan]

Hi Trevor,

On Wed, Apr 13, 2016 at 01:06:21PM -0400, Trevor Woerner wrote:
> The latest raspberrypi3 puts its console on ttyS0 instead of ttyAMA0 (like all
> the preceding boards). Therefore pull this definition out of the common
> include file and add it separately for each MACHINE.
>
> Signed-off-by: Trevor Woerner <twoer...@gmail.com>

Merged this to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] omxplayer: Bump revision

[Andrei Gherzan]

On Sat, Apr 16, 2016 at 11:20:51AM +1000, Jonathan Liu wrote:
> Fixes linking error due to missing vchostif library dependency.
> Rebased patches and removed patches already merged upstream.
>
> Signed-off-by: Jonathan Liu <net...@gmail.com>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 5/5] README: Document new variable configuration

[Andrei Gherzan]

On Thu, Apr 21, 2016 at 06:32:13PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan <theo...@resin.io>
>
> Signed-off-by: Theodor Gherzan <theo...@resin.io>
> ---
>  README | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/README b/README
> index 536926b..cbc7a92 100644
> --- a/README
> +++ b/README
> @@ -233,6 +233,10 @@ the modelname should be added as a MACHINE_FEATURES in 
> local.conf like below:
>  List of currently supported models:
>  - pitft22
>
> +3.O. Enable UART
> +===
> +Set this variable to enable UART:
> +ENABLE_UART = "1"

Based on the explaination about enable_uart this is not quite right.
Cause on rpi1, rpi2 and cm it will get enabled without this variable by
default. So this needs a little additional information.

>
>  4. Extra apps
>  =
> --
> 2.1.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler

[Andrei Gherzan]

On Thu, Apr 21, 2016 at 06:47:29PM +0100, Theodor Gherzan wrote:
> A new config.txt setting has been introduced - enable_uart - the
> purpose of which is to control the initialisation of the UART(*). The
> default value varies according to the primary UART on the platform -
> if the PL011 is the primary UART (that used for the console and boot
> messages) then enable_uart defaults to 1, and if the mini-UART is the
> primary then it defaults to 0.
>

Got it now. So people with rpi3 will need to set this to get serial
enabled but rpi1-2 will get it by default. Can you please add a summary
in README too?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler

[Andrei Gherzan]

Hi,

On Thu, Apr 21, 2016 at 06:32:11PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan <theo...@resin.io>
>
> Signed-off-by: Theodor Gherzan <theo...@resin.io>
> ---
>  recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
>  1 file changed, 6 insertions(+)
>
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index 4d41723..6ddf843 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -90,6 +90,12 @@ do_deploy() {
>  echo "# Enable PITFT22 display" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +
> +# UART support
> +if [ "${ENABLE_UART}" = "1" ]; then
> +echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
What is the default value of enable_uart?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] userland: Make vchostif as shared library

[Andrei Gherzan]

On Sat, Apr 16, 2016 at 11:24:01AM +1000, Jonathan Liu wrote:
> Hi Khem,
>
> On 14 April 2016 at 02:36, Khem Raj <raj.k...@gmail.com> wrote:
> > Thats interesting, I will try to reproduce it
>
> I have submitted a patch to the mailing list to bump the omxplayer
> revision which fixes the issue.
>

Cool. I'll take a look on it, test it and merge today.
--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++

[Andrei Gherzan]

Hi Julien,

On Thu, Apr 21, 2016 at 10:15:23AM +0200, Julien Gueytat wrote:
> Just to keep you informed that a bug report has been opened to Qt:
> https://bugreports.qt.io/browse/QTBUG-52739
>
> We might save some patches in layers by solving this,
> Thanks for helping,
>

Great Julien. Here is a hint - would this help your problem?
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028277.html

> Le 20/04/2016 01:46, Julien Gueytat a écrit :
> > Hi again guys,
> >
> > after more investigations:
> >
> > I found out that the default value -lEGL comes from
> > ./mkspecs/common/linux.conf which is included in
> > ./mkspecs/linux-oe-g++/qmake.conf
> >
> > linux-oe-g++ being the only generic mkspecs that should be used in Yocto
> >
> > So! At the time the configuration enters egl.pro the content of the
> > variables LIBS and QMAKE_EGL_LIBS are still a bit weird for me :
> >
> > 1- LIBS already has the content of the QMAKE_EGL_LIBS content from the
> > result of the pkg-config command.
> > 2- QMAKE_EGL_LIBS has the content of the default value found in
> > ./mkspecs/common/linux.conf
> >
> > There are two options to have it properly working:
> > - First and easy option : remove the QMAKE_EGL_LIBS default variable in
> > ./mkspecs/linux-oe-g++/qmake.conf since the good libs seems to already
> > been present in the LIBS variable.
> > - Second option : understand why the LIBS variable is already properly
> > set and why the QMAKE_EGL_LIBS properly computed in the configure and
> > present .qmake.vars is not used. (I would say that the device spec
> > overrides the one from qmake spec... I did not dig further yet.)
> >
> > Anyway I'm pretty sure the trouble comes from meta-qt5 side now. I'm
> > pretty sure meta-raspberrypi maintainers can confirm that their master
> > branch handles pkg-config stuff now.
> >
> > Thanks advance for having a look on this guys,
> > Best Regards
> >
> >
> > Le 19/04/2016 10:46, Julien Gueytat a écrit :
> > > Hi,
> > >
> > > I still can't figure out the patch to apply in meta-qt5 to get EGL
> > > support with the Raspberry.
> > >
> > > The test to check EGL does not pass and fails with the following command:
> > >
> > > arm-poky-linux-gnueabi-g++  -march=armv7-a -marm -mthumb-interwork
> > > -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 
> > > --sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
> > > -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o
> > > -lGLESv2 -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> > >
> > >
> > > Here is the content of the file egl.pro:
> > >
> > > $ cat egl.pro
> > > SOURCES = egl.cpp
> > >
> > > for(p, QMAKE_LIBDIR_EGL) {
> > > exists($$p):LIBS += -L$$p
> > > }
> > >
> > > message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > > message("In egl.pro - 1: LIBS = $$LIBS")
> > >
> > > !isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
> > > !isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL
> > >
> > > message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > > message("In egl.pro - 2: LIBS = $$LIBS")
> > >
> > > CONFIG -= qt
> > >
> > > In the main ./configure file of qtbase:
> > >
> > > | In configure #1: QMAKE_LIBS_EGL =
> > > | In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lbcm_host -lvcos -lvchiq_arm -pthread
> > >
> > > The variable QMAKE_LIBS_EGL is set properly.
> > >
> > >
> > > In the ./config.tests/qpa/egl/egl.pro file:
> > >
> > > | Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
> > > | Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lvcos -lvchiq_arm -pthread
> > > | Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
> > > | Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> > >
> > >
> > > *What I see is that:*
> > > In the configure file the variable QMAKE_LIBS_EGL is properly set
> > > through pkg-config.
> > > In the egl.pro file... The variable LIBS gets the content of
> > > QMAKE_LIBS_EGL and the variable QMAKE_LIBS_EGL gets back to its
> > > default -lEGL.
> > >
> > > In the 

Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++

[Andrei Gherzan]

On Wed, Apr 20, 2016 at 11:05:01PM +0200, Andrei Gherzan wrote:
> On Tue, Apr 19, 2016 at 10:46:11AM +0200, Julien Gueytat wrote:
> > Hi,
> >
> > I still can't figure out the patch to apply in meta-qt5 to get EGL support
> > with the Raspberry.
> >
> > The test to check EGL does not pass and fails with the following command:
> >
> > arm-poky-linux-gnueabi-g++  -march=armv7-a -marm  -mthumb-interwork
> > -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 
> > --sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
> > -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o -lGLESv2
> > -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> >
> >
> > Here is the content of the file egl.pro:
> >
> > $ cat egl.pro
> > SOURCES = egl.cpp
> >
> > for(p, QMAKE_LIBDIR_EGL) {
> > exists($$p):LIBS += -L$$p
> > }
> >
> > message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > message("In egl.pro - 1: LIBS = $$LIBS")
> >
> > !isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
> > !isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL
> >
> > message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > message("In egl.pro - 2: LIBS = $$LIBS")
> >
> > CONFIG -= qt
> >
> > In the main ./configure file of qtbase:
> >
> > | In configure #1: QMAKE_LIBS_EGL =
> > | In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif
> > -lbcm_host -lvcos -lvchiq_arm -pthread
> >
> > The variable QMAKE_LIBS_EGL is set properly.
> >
> >
> > In the ./config.tests/qpa/egl/egl.pro file:
> >
> > | Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
> > | Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
> > -lvchostif -lvcos -lvchiq_arm -pthread
> > | Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
> > | Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
> > -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> >
> >
> > *What I see is that:*
> > In the configure file the variable QMAKE_LIBS_EGL is properly set through
> > pkg-config.
> > In the egl.pro file... The variable LIBS gets the content of QMAKE_LIBS_EGL
> > and the variable QMAKE_LIBS_EGL gets back to its default -lEGL.
> >
> > In the end with have -lGLESv2 before -lEGL and this does not link.
> >
> > I checked also the content of .qmake.vars:
> > grep QMAKE_LIBS_EGL .qmake.vars
> > QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif -lbcm_host -lvcos
> > -lvchiq_arm -pthread
> >
> >
> > The command QMakeVar set QMAKE_LIBS_EGL "$QMAKE_LIBS_EGL" seems to have his
> > job done too late...
> >
> > If someone has an idea to get the proper correction done...
> >
> > Best Regards,
> > Julien
> >
>
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> Merged to master. Thanks.
>

Ignore this message. Sorry for the noise but I replied to the wrong
email.

> --
> Andrei Gherzan



--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] userland: Fix passing of wayland-native to cmake while configuring

[Andrei Gherzan]

On Sat, Apr 16, 2016 at 03:31:25PM +0200, toolmmy wrote:
> From: Tom Doehring <tool...@gmail.com>
>
> While having 'wayland' set DISTRO_FEATURES 'wayland-native' is handled as a 
> cmake parameter which breaks the do_configure:
>
> $ cat /data/builds/rpi3-sandbox/tmp/work/raspberrypi2-poky-linux-gnueab 
> i/userland/git-r5/temp/run.do_configure
>  cmake \
>   ${OECMAKE_SITEFILE} \
>   [...]
>   -DCMAKE_BUILD_TYPE=Release 
> -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-as-needed'  wayland-native 
> \
>   -Wno-dev
>
> $ CMake Error: The source directory 
> "/data/builds/rpi3-sandbox/tmp/work/raspberrypi2-poky-linux-gnueabi/userland/git-r5/build/wayland-native"
>  does not exist.
> | Specify --help for usage, or press the help button on the CMake GUI.
>
> Assuming that wayland-native should only be defined as a DEPENDS package this 
> patch moves it to the correct PACKAGECONFIG position.
>
> Signed-off-by: Tom Doehring <tool...@gmail.com>
> Signed-off-by: toolmmy <tool...@gmail.com>
> ---

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++

[Andrei Gherzan]

On Tue, Apr 19, 2016 at 10:46:11AM +0200, Julien Gueytat wrote:
> Hi,
>
> I still can't figure out the patch to apply in meta-qt5 to get EGL support
> with the Raspberry.
>
> The test to check EGL does not pass and fails with the following command:
>
> arm-poky-linux-gnueabi-g++  -march=armv7-a -marm  -mthumb-interwork
> -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 
> --sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
> -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o -lGLESv2
> -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
>
>
> Here is the content of the file egl.pro:
>
> $ cat egl.pro
> SOURCES = egl.cpp
>
> for(p, QMAKE_LIBDIR_EGL) {
> exists($$p):LIBS += -L$$p
> }
>
> message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> message("In egl.pro - 1: LIBS = $$LIBS")
>
> !isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
> !isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL
>
> message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> message("In egl.pro - 2: LIBS = $$LIBS")
>
> CONFIG -= qt
>
> In the main ./configure file of qtbase:
>
> | In configure #1: QMAKE_LIBS_EGL =
> | In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif
> -lbcm_host -lvcos -lvchiq_arm -pthread
>
> The variable QMAKE_LIBS_EGL is set properly.
>
>
> In the ./config.tests/qpa/egl/egl.pro file:
>
> | Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
> | Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
> -lvchostif -lvcos -lvchiq_arm -pthread
> | Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
> | Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
> -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
>
>
> *What I see is that:*
> In the configure file the variable QMAKE_LIBS_EGL is properly set through
> pkg-config.
> In the egl.pro file... The variable LIBS gets the content of QMAKE_LIBS_EGL
> and the variable QMAKE_LIBS_EGL gets back to its default -lEGL.
>
> In the end with have -lGLESv2 before -lEGL and this does not link.
>
> I checked also the content of .qmake.vars:
> grep QMAKE_LIBS_EGL .qmake.vars
> QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif -lbcm_host -lvcos
> -lvchiq_arm -pthread
>
>
> The command QMakeVar set QMAKE_LIBS_EGL "$QMAKE_LIBS_EGL" seems to have his
> job done too late...
>
> If someone has an idea to get the proper correction done...
>
> Best Regards,
> Julien
>

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

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] userland: Fix a build regression in builds not using wayland

[Andrei Gherzan]

gt; - host_applications/linux/apps/dtoverlay/dtoverlay_main.c | 6 --
> - 1 file changed, 4 insertions(+), 2 deletions(-)
> -
> -diff --git a/host_applications/linux/apps/dtoverlay/dtoverlay_main.c 
> b/host_applications/linux/apps/dtoverlay/dtoverlay_main.c
> -index 4b33809..fa8324f 100755
>  a/host_applications/linux/apps/dtoverlay/dtoverlay_main.c
> -+++ b/host_applications/linux/apps/dtoverlay/dtoverlay_main.c
> -@@ -353,7 +353,8 @@ static int dtoverlay_remove(STATE_T *state, const char 
> *overlay)
> - int rmpos;
> - int i;
> -
> --chdir(work_dir);
> -+if (chdir(work_dir) != 0)
> -+return error("chdir to %s failed", work_dir);
> -
> - overlay_dir = sprintf_dup("%s/%s", dt_overlays_dir, overlay);
> - if (!dir_exists(overlay_dir))
> -@@ -633,7 +634,8 @@ static int overlay_applied(const char *overlay_dir)
> - FILE *fp = fopen(status_path, "r");
> - if (fp)
> - {
> --fread(status, sizeof(status), 1, fp);
> -+int bytes __attribute__((unused));
> -+bytes = fread(status, sizeof(status), 1, fp);
> - fclose(fp);
> - }
> - free_string(status_path);
> ---
> -2.7.4
> -
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index ca9123e..efa2128 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -16,7 +16,7 @@ COMPATIBLE_MACHINE = "raspberrypi"
>
>  SRCBRANCH = "master"
>  SRCFORK = "raspberrypi"
> -SRCREV = "2f56a2943a9eb8420df52ccf91f5a1c5a70e8713"
> +SRCREV = "703a2c4b35e23ee44ad84db6b9c3f89c0a627143"
>
>  SRC_URI = "\
>  
> git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
> @@ -33,7 +33,6 @@ SRC_URI = "\
>  file://0011-fix-cmake-dependency-race.patch \
>  file://0012-Fix-enum-conversion-warnings.patch \
>  file://0013-Fix-for-framerate-with-nested-composition.patch \
> -file://0014-Fix-errors-due-to-ignored-return-code.patch \
>  file://0015-wl-dispmanx-buffer-wrapping.patch \
>  "
>  S = "${WORKDIR}/git"
> --
> 2.8.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged both patches. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 4/6] linux-firmware: Add brcmfmac43430 firmware

[Andrei Gherzan]

On Wed, Apr 06, 2016 at 02:30:41AM +0100, Theodor Gherzan wrote:
> I will have a look.
>

No need to take a look on this anymore Theodor. It was fixed in master.

> Theodor Gherzan
>
> On Tue, Mar 29, 2016 at 11:06 PM, Andrei Gherzan <and...@gherzan.ro> wrote:
> > On Fri, Mar 25, 2016 at 11:34:21AM +1100, Jonathan Liu wrote:
> >> Hi Theodor,
> >>
> >> On 10 March 2016 at 01:15, Theodor Gherzan <theo...@gherzan.ro> wrote:
> >> > From: Theodor Gherzan <theo...@resin.io>
> >> >
> >> > Signed-off-by: Theodor Gherzan <theo...@resin.io>
> >> > ---
> >> >  .../linux-firmware/LICENSE.broadcom_brcm80211  | 205 
> >> > +
> >> >  .../linux-firmware/brcmfmac43430-sdio.bin  | Bin 0 -> 368957 
> >> > bytes
> >> >  .../linux-firmware/brcmfmac43430-sdio.txt  |  66 +++
> >> >  .../linux-firmware/linux-firmware_git.bbappend |  29 +++
> >> >  4 files changed, 300 insertions(+)
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.bin
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.txt
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> >>
> >> I get the following warning when building an image that installs
> >> linux-firmware-ralink package (but not any of the other firmware
> >> packages):
> >> [log_check] WARNING: The license listed Firmware-broadcom_brcm80211
> >> was not in the licenses collected for recipe linux-firmware
> >>
> >> It seems the license is not being packaged correctly.
> >>
> >> Could you please have a look?
> >
> > Theodor,
> >
> > Any chance you can take a look on this?
> >
> > Cheers!
> >
> > --
> > Andrei Gherzan

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/1] userland: In case of wayland configuration build needs wayland-native

[Andrei Gherzan]

On Fri, Apr 01, 2016 at 01:37:11PM +0200, Andrei Gherzan wrote:
> Building wayland support requires availability of wayland-scanner to avoid
> build errors like:
>
> | /bin/sh:
> | 
> /home/andrei/work/yocto/build-rpi-master/tmp/sysroots/x86_64-linux/usr/bin/wayland-scanner:
> | No such file or directory
>
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  recipes-graphics/userland/userland_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index ca9123e..536c3ec 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
> -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
>
>  PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
> 'wayland', '', d)}"
>
> -PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland"
> +PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
>
>  CFLAGS_append = " -fPIC"
>
> --
> 2.7.4
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 1/1] README: Mention all the supported machines

[Andrei Gherzan]

On Mon, Apr 04, 2016 at 09:31:01PM +0200, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  README | 6 +-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/README b/README
> index 536926b..cfd83b3 100644
> --- a/README
> +++ b/README
> @@ -73,7 +73,11 @@ revision: HEAD
>  a. source poky/oe-init-build-env rpi-build
>  b. Add needed layer to bblayers.conf:
>  - meta-raspberrypi
> -c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
> +c. Set MACHINE in local.conf to one of the supported boards:
> +- raspberrypi
> +- raspberrypi0
> +- raspberrypi2
> +- raspberrypi3
>  d. bitbake rpi-hwup-image
>  e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is 
> used)
>  f. Boot your RPI.
> --
> 2.7.4
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-firmware: Rework of brcmfmac43430 firmware handling

[Andrei Gherzan]

On Sat, Apr 09, 2016 at 12:48:03PM +0200, toolmmy wrote:
> The current version of the recipe produces the following warnings while 
> createing an image:
>
> WARNING: The license listed Firmware-broadcom_brcm80211 was not in the 
> licenses collected for recipe linux-firmwa
> re
> WARNING: [log_check] td-core-image: found a warning message in the logfile 
> (keyword 'WARNING:'):
> [log_check] WARNING: The license listed Firmware-broadcom_brcm80211 was not 
> in the licenses collected for recipe
> linux-firmware
>
> This commit contains a rework of the brcm80211 firmware handling and deploys 
> the firmware and the LICENSE files that fixes the warning messages.
>
> Signed-off-by: Tom Doehring <tool...@gmail.com>
> ---
>  .../linux-firmware/linux-firmware_git.bbappend   | 20 
> 
>  1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend 
> b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> index f0c9fe2..20ef05f 100644
> --- a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> +++ b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> @@ -1,6 +1,10 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> -LIC_FILES_CHKSUM_append = 
> "file://${WORKDIR}/LICENSE.broadcom_brcm80211;md5=8cba1397cda6386db37210439a0da3eb"
> +LICENSE_append = " & Firmware-broadcom_brcm80211"
> +
> +LIC_FILES_CHKSUM_append = " 
> file://${WORKDIR}/LICENSE.broadcom_brcm80211;md5=8cba1397cda6386db37210439a0da3eb"
> +
> +NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = 
> "LICENSE.broadcom_brcm80211"
>
>  SRC_URI_append = " \
>  file://brcmfmac43430-sdio.bin \
> @@ -9,21 +13,21 @@ SRC_URI_append = " \
>  "
>
>  do_install_append() {
> -cp ${WORKDIR}/brcmfmac43430-sdio.* ${D}/lib/firmware/brcm
> +cp ${WORKDIR}/brcmfmac43430-sdio.* ${D}/lib/firmware/brcm/
> +cp ${WORKDIR}/LICENSE.broadcom_brcm80211 ${D}/lib/firmware/
>  }
>
> -PACKAGES =+ "${PN}-brcm43430"
> +PACKAGES =+ "${PN}-brcm43430 ${PN}-brcm43430-license"
> +
> +LICENSE_${PN}-brcm43430 = "Firmware-broadcom_brcm80211"
> +FILES_${PN}-brcm43430-license = "/lib/firmware/LICENSE.broadcom_brcm80211"
>  FILES_${PN}-brcm43430 = " \
>  /lib/firmware/brcm/brcmfmac43430-sdio.bin \
>  /lib/firmware/brcm/brcmfmac43430-sdio.txt \
>  "
>
> -LICENSE_append = " & Firmware-broadcom_brcm80211"
> -NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = 
> "LICENCE.broadcom_brcm80211"
> -LICENSE_${PN}-brcm43430 = "LICENSE.broadcom_brcm80211"
> +RDEPENDS_${PN}-brcm43430 += "${PN}-brcm43430-license"
>
>  ALTERNATIVE_LINK_NAME[brcmfmac-sdio.bin] = 
> "/lib/firmware/brcm/brcmfmac-sdio.bin"
>  ALTERNATIVE_TARGET_linux-firmware-brcm43430[brcmfmac-sdio.bin] = 
> "/lib/firmware/brcm/brcmfmac43430-sdio.bin"
>  ALTERNATIVE_linux-firmware-brcm43430 = "brcmfmac-sdio.bin"
> -
> -RDEPENDPS_${PN}-brcm43430 += "${PN}-broadcom-license"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 2/2] raspberrypi3: set core frequency

[Andrei Gherzan]

On Mon, Apr 11, 2016 at 05:54:45PM -0400, Trevor Woerner wrote:
> Pegging the core frequency at 250 avoids any fluctuations of the baud rate on
> the console.
>
> See:
>   https://www.raspberrypi.org/forums/viewtopic.php?f=107=138223
>
> Signed-off-by: Trevor Woerner <twoer...@gmail.com>
> ---
>  conf/machine/raspberrypi3.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> index cb6056e..81301c3 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -9,3 +9,4 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
>  include conf/machine/raspberrypi2.conf
>
>  SERIAL_CONSOLE = "115200 ttyS0"
> +CORE_FREQ = "250"

I think it would be better to use enable_uart in config.txt for this
situation. Setting it to 1 would work on all the rpi versions with
current firmware (to be tested).

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console

[Andrei Gherzan]

On Wed, Apr 13, 2016 at 04:20:36AM +0200, Andrei Gherzan wrote:
> On Mon, Apr 11, 2016 at 05:54:44PM -0400, Trevor Woerner wrote:
> > The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> > /dev/ttyAMA0.
> >
> > Signed-off-by: Trevor Woerner <twoer...@gmail.com>
> > ---
> >  conf/machine/raspberrypi3.conf | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> > index 1b73f2f..cb6056e 100644
> > --- a/conf/machine/raspberrypi3.conf
> > +++ b/conf/machine/raspberrypi3.conf
> > @@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> >  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
> >
> >  include conf/machine/raspberrypi2.conf
> > +
> > +SERIAL_CONSOLE = "115200 ttyS0"
>
> As this seems not to be unified anymore, would it make sense to remove
> it from rpi-base.inc and define it in every machine conf?
>

Or we can use the replace method in firmware setting it to serial0.
https://github.com/RPi-Distro/repo/issues/22

> --
> Andrei Gherzan



--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console

[Andrei Gherzan]

On Mon, Apr 11, 2016 at 05:54:44PM -0400, Trevor Woerner wrote:
> The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> /dev/ttyAMA0.
>
> Signed-off-by: Trevor Woerner <twoer...@gmail.com>
> ---
>  conf/machine/raspberrypi3.conf | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> index 1b73f2f..cb6056e 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
>  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
>
>  include conf/machine/raspberrypi2.conf
> +
> +SERIAL_CONSOLE = "115200 ttyS0"

As this seems not to be unified anymore, would it make sense to remove
it from rpi-base.inc and define it in every machine conf?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc Rename linux.inc to prevent it from impacting other machines

[Andrei Gherzan]

On Mon, Apr 11, 2016 at 11:37:50AM -0700, Alan Stice wrote:
> Attempting submitting this patch from my linux machine to hopefully correct
> the line wrapping issue.
>

Is fine now. Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 0/5] Various upgrade/fixes from Technux

[Andrei Gherzan]

On Wed, Mar 30, 2016 at 04:35:44PM +0200, Petter Mabäcker wrote:
> Various fixes from Technux, with focus on PiTFT28 resistive support and
> Official Raspberry Pi 7 inch touchscreen enablers.
>
> Petter Mabäcker (5):
>   pitft: Add support for pitft28r
>   rpi-base.inc: Remove deprecated MACHINE_FEATURES
>   rpi-base.inc: Add overlay for rpi-ft5406
>   .gitignore: Ignore some additional files
>   linux-raspberrypi: Drop support for 3.14
>
>  .gitignore |   2 +
>  README |   3 +-
>  conf/machine/include/rpi-base.inc  |   4 +-
>  recipes-bsp/bootfiles/rpi-config_git.bb|   6 +
>  .../rpi/xorg.conf.d/98-pitft.conf  |   5 +
>  .../rpi/xorg.conf.d/99-calibration.conf|   6 +
>  .../rpi/xorg.conf.d/99-pitft.conf  |   5 -
>  .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |   6 +-
>  .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 
> -
>  ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 --
>  recipes-kernel/linux/linux-raspberrypi.inc |   2 +
>  recipes-kernel/linux/linux-raspberrypi_3.14.bb |  11 -
>  12 files changed, 30 insertions(+), 518 deletions(-)
>  create mode 100644 
> recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
>  create mode 100644 
> recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
>  delete mode 100644 
> recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi-3.14/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
>  delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.14.bb
>
> --
> 1.9.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks Petter.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Andrei Gherzan]

Hello,

On Mon, Apr 04, 2016 at 09:45:55PM +0200, Herrie wrote:
>
> Andrei,
>
> Hopefully better like this. Changed it to plain text at my end now for below
> patch
>

Sadly nothing changed. Lines are still wrapped breaking the patch.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Andrei Gherzan]

Hello,

On Mon, Apr 04, 2016 at 08:40:32PM +0200, Herrie wrote:
> From 164d6ec1b054fa241e65ac4961d204edd9965061 Mon Sep 17 00:00:00 2001
> From: Alan Stice <a...@alanstice.com>
> Date: Thu, 10 Mar 2016 08:52:07 -0800
> Subject: [PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc Rename
>  linux.inc to prevent it from impacting other machines while building
> multiple targets with same architecture sharing sstate.
>
> Signed-off-by: Alan Stice <a...@alanstice.com>
> Signed-off-by: Herman van Hazendonk <github@herrie.org>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc |   2 +-
>  recipes-kernel/linux/linux-rpi.inc | 132
> +
>  recipes-kernel/linux/linux.inc | 132
> -
>  3 files changed, 133 insertions(+), 133 deletions(-)
>  create mode 100644 recipes-kernel/linux/linux-rpi.inc
>  delete mode 100644 recipes-kernel/linux/linux.inc
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 24e7fe2..7ab1de2 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -1,4 +1,4 @@
> -require linux.inc
> +require linux-rpi.inc
>  inherit linux-raspberrypi-base
>
>  DESCRIPTION = "Linux Kernel for Raspberry Pi"
> diff --git a/recipes-kernel/linux/linux-rpi.inc
> b/recipes-kernel/linux/linux-rpi.inc
> new file mode 100644
> index 000..fae78b7
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-rpi.inc
> @@ -0,0 +1,132 @@
> +DESCRIPTION = "Linux Kernel"
> +SECTION = "kernel"
> +LICENSE = "GPLv2"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> +
> +inherit kernel siteinfo
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# Enable OABI compat for people stuck with obsolete userspace
> +ARM_KEEP_OABI ?= "1"
> +
> +# Quirk for udev greater or equal 141
> +UDEV_GE_141 ?= "1"
> +
> +# Set the verbosity of kernel messages during runtime
> +# You can define CMDLINE_DEBUG in your local.conf or distro.conf to
> override this behaviour
> +CMDLINE_DEBUG ?= '${@base_conditional("DISTRO_TYPE", "release", "quiet",
> "debug", d)}'

There seems to be issues in applying this patch as some of the lines get
wrapped to (probably) 80 chars or so. Could you please make sure you
send this patch in plain text and without this wrapping? Thanks man.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Andrei Gherzan]

On Mon, Apr 04, 2016 at 08:33:00PM +0200, Petter Mabäcker wrote:
> On 04/04/2016 07:54 PM, Andrei Gherzan wrote:
> >Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> >---
> >  README | 5 -
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> >diff --git a/README b/README
> >index 536926b..542b135 100644
> >--- a/README
> >+++ b/README
> >@@ -73,7 +73,10 @@ revision: HEAD
> >  a. source poky/oe-init-build-env rpi-build
> >  b. Add needed layer to bblayers.conf:
> >  - meta-raspberrypi
> >-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
> >+c. Set MACHINE in local.conf to one of the supported boards:
> >+- raspberrypi
> >+- raspberrypi2
> >+- raspberrypi3
> >  d. bitbake rpi-hwup-image
> >  e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is 
> > used)
> >  f. Boot your RPI.
> Good, this is a tiny but important change! Should we also mention
> raspberrypi0? Currently it just includes raspberrypi.conf and the the
> raspberrypi0 MACHINEOVERRIDE isn't used for anything, but still it is a
> defined MACHINE. What do you think?
>

Forgot it. Will send PR2.

> BR Petter

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 README | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 536926b..542b135 100644
--- a/README
+++ b/README
@@ -73,7 +73,10 @@ revision: HEAD
 a. source poky/oe-init-build-env rpi-build
 b. Add needed layer to bblayers.conf:
 - meta-raspberrypi
-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
+c. Set MACHINE in local.conf to one of the supported boards:
+- raspberrypi
+- raspberrypi2
+- raspberrypi3
 d. bitbake rpi-hwup-image
 e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
 f. Boot your RPI.
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi] Adding more screens / PiTFT support.

[Andrei Gherzan]

On Mon, Apr 04, 2016 at 05:09:03PM +0200, Petter Mabäcker wrote:
>
>
> 2016-04-04 15:17 skrev GUEYTAT Julien:
>
> > Hi,
> >
> > I would like to
> add PiTFT support to the meta-raspberry layer. Or at least I would like
> to add it in my own BSP layer.
> >
> > I read that Peter were playing with
> that recently. Could you please give me some hints to do so?
> >
> > I
> have at least two more screens to integrate.
> >
> > If someone could
> point me to an example of a BSP based on meta-raspberrypi that would be
> awesome.
> >
> > Thanks in advance,
> >
> > Best Regards
> >
> > JULIEN
> GUEYTAT
> >
> > INGÉNIEUR INFORMATIQUE
> >
> > 1027, avenue du Docteur
> Julien Lefebre BP27
> >
> > 06271 Villeneuve-Loubet Cedex
> >
> > Fixe : +33
> (0) 492 024 545
> > Mob : +33(0) 617 980 383
> > Fax : +33(0) 492 024 546
> >
> Email : j.guey...@cdssoft.studiel.fr
> >
> > www : www.studiel.fr [1]
> >
>
> > PPENSEZ ENVIRONNEMENT, IMPRIMEZ SEULEMENT SI NÉCESSAIRE
>
> Hi Julien,
>
>
> After some discussions with the community, we decided that the
> official meta-raspberrypi pitft support should be added using
> MACHINE_FEATURES. If you look in README for meta-raspberrypi there are
> some basic description about how to enable support:
>
> For a already
> supported pitft model (pitft22 is supported and 28r is on it's way
> https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html),
> you can just add below MACHINE_FEATURES to local.conf:
>
>
> MACHINE_FEATURES += "pitft pitft22"
>
> In order to add support for
> additional models you can use
> https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html as
> a reference.
>  Basically what you need are to:
>
> * add the overlay for
> the screen
>
> * Add dtoverlay option with wanted default arguments in
> rpi-config_git.bb
>
> * Add a default calibration (if needed)
>
> Assuming
> an overlay exists for your model, it shouldn't be so tricky to fix the
> rest..
>

As Petter says, everything should be in the README. Try to give it a
spin and tell us how it goes.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] userland: Fix tearing effect seen with wayland compositors

[Andrei Gherzan]

On Tue, Mar 29, 2016 at 08:44:31PM -0700, Khem Raj wrote:
> Introduce EGL flush in few more places
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  ...Fix-for-framerate-with-nested-composition.patch | 46 
> ++
>  1 file changed, 39 insertions(+), 7 deletions(-)
>
> diff --git 
> a/recipes-graphics/userland/userland/0013-Fix-for-framerate-with-nested-composition.patch
>  
> b/recipes-graphics/userland/userland/0013-Fix-for-framerate-with-nested-composition.patch
> index 6377e31..2fa9d66 100644
> --- 
> a/recipes-graphics/userland/userland/0013-Fix-for-framerate-with-nested-composition.patch
> +++ 
> b/recipes-graphics/userland/userland/0013-Fix-for-framerate-with-nested-composition.patch
> @@ -1,20 +1,39 @@
> -From 7f424ce48f6c14118aea2ab770b3bbf87e1f0393 Mon Sep 17 00:00:00 2001
> +From e5affc4ff145eedf61e2625a8919622c92d0b8ba Mon Sep 17 00:00:00 2001
>  From: Khem Raj <raj.k...@gmail.com>
> -Date: Thu, 24 Mar 2016 14:30:58 -0700
> -Subject: [PATCH 13/13] Fix for framerate with nested composition
> +Date: Tue, 29 Mar 2016 20:38:30 -0700
> +Subject: [PATCH 13/14] Fix for framerate with nested composition
>
>  frame rate appears irregular and lower than expected when using nested 
> composition.
>
>  Signed-off-by: Khem Raj <raj.k...@gmail.com>
>  ---
> - interface/khronos/egl/egl_client.c | 1 +
> - 1 file changed, 1 insertion(+)
> + interface/khronos/egl/egl_client.c | 9 -
> + 1 file changed, 8 insertions(+), 1 deletion(-)
>
>  diff --git a/interface/khronos/egl/egl_client.c 
> b/interface/khronos/egl/egl_client.c
> -index 024f3ed..95bb581 100644
> +index 024f3ed..d8a007c 100644
>  --- a/interface/khronos/egl/egl_client.c
>  +++ b/interface/khronos/egl/egl_client.c
> -@@ -2360,6 +2360,7 @@ EGLAPI EGLBoolean EGLAPIENTRY 
> eglSwapBuffers(EGLDisplay dpy, EGLSurface surf)
> +@@ -2342,6 +2342,9 @@ EGLAPI EGLBoolean EGLAPIENTRY 
> eglSwapBuffers(EGLDisplay dpy, EGLSurface surf)
> +  surface->back_wl_buffer = buffer;
> +   }
> +
> ++  glFlush();
> ++  glFinish();
> ++
> +   RPC_CALL7(eglIntSwapBuffers_impl,
> + thread,
> + EGLINTSWAPBUFFERS_ID_V2,
> +@@ -2353,6 +2356,8 @@ EGLAPI EGLBoolean EGLAPIENTRY 
> eglSwapBuffers(EGLDisplay dpy, EGLSurface surf)
> + 
> RPC_UINT(khrn_platform_get_window_position(surface->win)),
> + RPC_INT(surface->back_wl_buffer->resource));
> +
> ++  RPC_FLUSH(thread);
> ++
> +   surface->front_wl_buffer->in_use = 1;
> +   wl_surface_attach(wl_egl_window->wl_surface,
> + surface->front_wl_buffer->wl_buffer,
> +@@ -2360,10 +2365,11 @@ EGLAPI EGLBoolean EGLAPIENTRY 
> eglSwapBuffers(EGLDisplay dpy, EGLSurface surf)
> wl_surface_damage(wl_egl_window->wl_surface, 0, 0,
>   surface->width, surface->height);
> wl_surface_commit(wl_egl_window->wl_surface);
> @@ -22,6 +41,19 @@ index 024f3ed..95bb581 100644
>
> while(ret != -1 && surface->back_wl_buffer->in_use)
>ret = wl_display_dispatch_queue(wl_display, 
> process->wl_queue);
> +-   } else
> ++   } else {
> + #endif
> +RPC_CALL6(eglIntSwapBuffers_impl,
> +  thread,
> +@@ -2376,6 +2382,7 @@ EGLAPI EGLBoolean EGLAPIENTRY 
> eglSwapBuffers(EGLDisplay dpy, EGLSurface surf)
> +  
> RPC_UINT(khrn_platform_get_window_position(surface->win)));
> +
> +    RPC_FLUSH(thread);
> ++   }
> +
> + #ifdef ANDROID
> +CLIENT_UNLOCK();
>  --
>  2.7.4
>
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] firmware: Update to 20160326

[Andrei Gherzan]

On Tue, Mar 29, 2016 at 08:44:30PM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  recipes-bsp/common/firmware.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index 2c4f497..c1117d6 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,5 +1,5 @@
> -RPIFW_SRCREV ?= "028b1f6585280bd0a21885973589c4b101355597"
> -RPIFW_DATE ?= "20160303"
> +RPIFW_SRCREV ?= "046effa13ebc4cc7601df4f06f4834bd0eebb0f8"
> +RPIFW_DATE ?= "20160326"
>  RPIFW_SRC_URI ?= 
> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>  RPIFW_S ?= "${WORKDIR}/git"
>
> --
> 2.7.4
>
> --
> _______
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/1] userland: In case of wayland configuration build needs wayland-native

[Andrei Gherzan]

Building wayland support requires availability of wayland-scanner to avoid
build errors like:

| /bin/sh:
| 
/home/andrei/work/yocto/build-rpi-master/tmp/sysroots/x86_64-linux/usr/bin/wayland-scanner:
| No such file or directory

Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 recipes-graphics/userland/userland_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index ca9123e..536c3ec 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
-DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
 
 PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
'wayland', '', d)}"
 
-PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
-DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland"
+PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
-DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
 
 CFLAGS_append = " -fPIC"
 
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH 4/6] linux-firmware: Add brcmfmac43430 firmware

[Andrei Gherzan]

On Fri, Mar 25, 2016 at 11:34:21AM +1100, Jonathan Liu wrote:
> Hi Theodor,
>
> On 10 March 2016 at 01:15, Theodor Gherzan <theo...@gherzan.ro> wrote:
> > From: Theodor Gherzan <theo...@resin.io>
> >
> > Signed-off-by: Theodor Gherzan <theo...@resin.io>
> > ---
> >  .../linux-firmware/LICENSE.broadcom_brcm80211  | 205 
> > +
> >  .../linux-firmware/brcmfmac43430-sdio.bin  | Bin 0 -> 368957 bytes
> >  .../linux-firmware/brcmfmac43430-sdio.txt  |  66 +++
> >  .../linux-firmware/linux-firmware_git.bbappend |  29 +++
> >  4 files changed, 300 insertions(+)
> >  create mode 100644 
> > recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
> >  create mode 100644 
> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.bin
> >  create mode 100644 
> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.txt
> >  create mode 100644 
> > recipes-kernel/linux-firmware/linux-firmware_git.bbappend
>
> I get the following warning when building an image that installs
> linux-firmware-ralink package (but not any of the other firmware
> packages):
> [log_check] WARNING: The license listed Firmware-broadcom_brcm80211
> was not in the licenses collected for recipe linux-firmware
>
> It seems the license is not being packaged correctly.
>
> Could you please have a look?

Theodor,

Any chance you can take a look on this?

Cheers!

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi-4.4: Add the pitft22 overlay from adafruit

[Andrei Gherzan]

Makefile
> +@@ -43,6 +43,7 @@ dtbo-$(RPI_DT_OVERLAYS) += pi3-disable-b
> + dtbo-$(RPI_DT_OVERLAYS) += pi3-miniuart-bt.dtbo
> + dtbo-$(RPI_DT_OVERLAYS) += piscreen.dtbo
> + dtbo-$(RPI_DT_OVERLAYS) += piscreen2r.dtbo
> ++dtbo-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtbo
> + dtbo-$(RPI_DT_OVERLAYS) += pitft28-capacitive.dtbo
> + dtbo-$(RPI_DT_OVERLAYS) += pitft28-resistive.dtbo
> + dtbo-$(RPI_DT_OVERLAYS) += pps-gpio.dtbo
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index f7c5bfb..8e4530f 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,6 +1,10 @@
> -LINUX_VERSION ?= "4.4.3"
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -SRCREV = "36babd89241c85258acebe06616f1f1a58356f8e"
> -SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y"
> +LINUX_VERSION ?= "4.4.6"
> +
> +SRCREV = "2faaa2ccef9e4c595bd26f14285c225ceea6097e"
> +SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
> +   file://0001-dts-add-overlay-for-pitft22.patch \
> +"
>
>  require linux-raspberrypi.inc
> --
> 1.9.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged all to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 18/23] firmware: Upgrade to latest stable 20160209

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:57PM +, Khem Raj wrote:
> Readme change a bit thats why LIC_FILES_CHKSUM changed
> 
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  recipes-bsp/bootfiles/bcm2835-bootfiles.bb | 2 +-
>  recipes-bsp/common/firmware.inc| 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/bootfiles/bcm2835-bootfiles.bb 
> b/recipes-bsp/bootfiles/bcm2835-bootfiles.bb
> index 0665944..b279e15 100644
> --- a/recipes-bsp/bootfiles/bcm2835-bootfiles.bb
> +++ b/recipes-bsp/bootfiles/bcm2835-bootfiles.bb
> @@ -1,7 +1,7 @@
>  DESCRIPTION = "Closed source binary files to help boot the ARM on the 
> BCM2835."
>  LICENSE = "Proprietary"
>  
> -LIC_FILES_CHKSUM = 
> "file://LICENCE.broadcom;md5=e86e693d19572ee64cc8b17fb062faa9"
> +LIC_FILES_CHKSUM = 
> "file://LICENCE.broadcom;md5=4a4d169737c0786fb9482bb6d30401d1"
>  
>  inherit deploy
>  
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index 020f0ed..2e0864e 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,5 +1,5 @@
> -RPIFW_SRCREV ?= "f7108cfdc715f79c5fd051fb4c3ae6f4b1b01f23"
> -RPIFW_DATE ?= "20151021"
> +RPIFW_SRCREV ?= "3442862c10fab68c2e88d660d2e69c143bb1f00c"
> +RPIFW_DATE ?= "20160209"
>  RPIFW_SRC_URI ?= 
> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>  RPIFW_S ?= "${WORKDIR}/git"
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Dropped as rpi3 patch set updated firmware to a newer version. Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Update revision to include rpi3 support

[Andrei Gherzan]

On Wed, Mar 09, 2016 at 04:15:02PM +0200, Theodor Gherzan wrote:
> From: Theodor Gherzan <theo...@resin.io>
> 
> Signed-off-by: Theodor Gherzan <theo...@resin.io>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> index e26019e..b55c9ff 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>  
> -LINUX_VERSION ?= "4.1.17"
> +LINUX_VERSION ?= "4.1.18"
>  
> -SRCREV = "cb2f10196a9b718a2d94bb4ac0887c2ea14988ae"
> +SRCREV = "fcc9ad149fbe78e9931b8e769ac54d5430587465"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y \
> file://0001-dts-add-overlay-for-pitft22.patch \
>"
> -- 
> 2.1.4
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged the entire patch set to master. Thanks.

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

Re: [yocto] Raspberry Pi 2 BSP build problem

[Andrei Gherzan]

On Mon, Mar 7, 2016 at 9:10 PM, Alan Hughes <alanhug...@e2eservices.co.uk>
wrote:

> I've been trying to build a BSP using Yocto 2.0 (Jethro) targetting a
> Raspberry Pi 2. Everything goes OK until we reach the point of building the
> "u-boot-rpi" package, at which point it blows up saying that it cannot find
> the file "linux/compiler-gcc5.h". I've looked on the web for any clues, but
> to date have not found anything relevent. If anyone has any suggestions I
> would be more than happy to try them out.
>
>
>
Hi Alan,

This is a known issue. Can you try to apply
https://github.com/resin-os/resin-via-arm/blob/master/layers/meta-resin-via-arm/recipes-bsp/u-boot/files/0001-uboot-support-gcc5.patch
and see if it fixes it?

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

Re: [yocto] [meta-raspberrypi][PATCH 00/23] Kernel/userland upgrade wayland support and clang fixes

[Andrei Gherzan]

Hi Khen,

I started to merge the ones that were obvious. The rest need rebasing,
conflict fixing and so on. And then I test them locally. So it will take a
while. But I'll merge as I test. So you can easily see the progress.

--
Andrei Gherzan

On Wed, Mar 2, 2016 at 3:21 PM, Khem Raj <raj.k...@gmail.com> wrote:

> Andrei
>
> I see you merged few of patches from here
> What is status of rest of series ?
>
> This series has been tested to work with Webkit and weston images
> on Pi2
>
>
>
> On Sat, Feb 27, 2016 at 7:26 AM, Khem Raj <raj.k...@gmail.com> wrote:
> > This patchset has been growing for a while, Adds recipes for kenrel 4.4
> and switches
> > to use kernel 4.4
> > Fixes userland to compile with clang
> > Upgrade userland to latest
> > Add option to support GPU_MEM_1024
> > Upgrade firmware to latest
> >
> > Khem Raj (23):
> >   userland: Upgrade to latest git master
> >   userland: Fix build with clang compiler
> >   userland: Add wayland support
> >   weston: Enable rpi compositor backend
> >   rpi-gpio: Upgrade to 0.6.1 and fix build with clang
> >   eglinfo-x11,eglinfo-fb: Add EGLINFO_DEVICE via bbappends
> >   python-rtimu: Fix build with musl
> >   wiringPi: Fix build with musl
> >   Delete rpc flushing of thread in glEGLImageTargetTexture2DOES
> >   rpio: Include sys/types.h for caddr_t
> >   userland: Define PROJECT_APIVER and rprovide libgles2 libgl
> >   userland: Add wayland to deps if in DISTRO_FEATURES
> >   userland: Fix build race with wayland support
> >   gstreamer1.0-omx: Add raspberry pi optimization patches and config
> > options
> >   weston: Specify egl and compositor options for rpi
> >   gstreamer1.0-omx: Backports and fixes for smooth video playback
> >   linux-raspberrypi: Upgrade 4.1 kernel to 4.1.17
> >   firmware: Upgrade to latest stable 20160209
> >   rpi-config: Upgrade to tip of tree to get GPU_MEM_1024
> >   linux-raspberrypi: Add recipe for 4.4 release
> >   userland: Upgrade to latest
> >   linux-raspberrypi: Upgrade 4.4.1 -> 4.4.2
> >   userland: Drop extern inline patches
> >
> >  README |2 +
> >  conf/machine/include/rpi-default-versions.inc  |2 +-
> >  recipes-bsp/bootfiles/bcm2835-bootfiles.bb |2 +-
> >  recipes-bsp/bootfiles/rpi-config_git.bb|5 +-
> >  recipes-bsp/common/firmware.inc|4 +-
> >  ...0001-include-asm-ioctl.h-for-ioctl-define.patch |   33 +
> >  recipes-devtools/python/python-rtimu_git.bb|4 +-
> >  .../rpi-gpio/0001-Remove-nested-functions.patch|  294 +++
> >  .../{rpi-gpio_0.5.11.bb => rpi-gpio_0.6.1.bb}  |6 +-
> >  ...-types.h-explicitly-for-getting-caddr_t-d.patch |   30 +
> >  recipes-devtools/python/rpio_0.10.0.bb |6 +-
> >  ...de-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch |   58 +
> >  recipes-devtools/wiringPi/wiringpi_git.bb  |8 +-
> >  recipes-graphics/eglinfo/eglinfo-fb_%.bbappend |1 +
> >  recipes-graphics/eglinfo/eglinfo-x11_%.bbappend|1 +
> >  .../userland/0001-fix-gcc-5.x-inlines.patch|   26 -
> >  .../userland/userland/0002-fix-musl-build.patch|   22 -
> >  .../0002-set-VMCS_INSTALL_PREFIX-to-usr.patch  |7 +-
> >  ...make-generate-and-install-pkgconfig-files.patch |   24 +-
> >  .../0003-fix-alloc-size-uninitialized.patch|   13 -
> >  ...-applications-to-set-next-resource-handle.patch |  208 +++
> >  ...ayland-Add-support-for-the-Wayland-winsys.patch | 1880
> 
> >  .../0007-wayland-Add-Wayland-example.patch |  866 +
> >  ...-wayland-egl-Add-bcm_host-to-dependencies.patch |   28 +
> >  ...emove-faulty-assert-to-make-weston-happy-.patch |   29 +
> >  ...0-zero-out-wl-buffers-in-egl_surface_free.patch |   33 +
> >  ...011-initialize-front-back-wayland-buffers.patch |   34 +
> >  .../userland/userland/0012-Remove-RPC_FLUSH.patch  |   27 +
> >  .../userland/0013-fix-cmake-dependency-race.patch  |   78 +
> >  .../0014-Fix-enum-conversion-warnings.patch|   99 ++
> >  recipes-graphics/userland/userland_git.bb  |   33 +-
> >  recipes-graphics/wayland/weston_%.bbappend |4 +
> >  recipes-graphics/weston/weston_%.bbappend  |7 +
> >  recipes-kernel/linux/linux-raspberrypi_4.1.bb  |4 +-
> >  ...raspberrypi_4.1.bb => linux-raspberrypi_4.4.bb} |6 +-
> >  .../gstreamer1.0-omx/0001-config-files-path.patch  |  137 ++
> >  ...o-acquire-buffer-when-src-pad-isn-t-activ.patch |   47 +
&g

Re: [yocto] [meta-raspberrypi][PATCH v4 1/1] pitft: Add PiTFT22 support

[Andrei Gherzan]

On Wed, Mar 02, 2016 at 12:47:59AM +0100, Andrei Gherzan wrote:
> From: Petter Mabäcker <pet...@technux.se>
>
> - Add support to build overlays for PiTFT22 in the kernel.
> - Setup a basic configuration for the driver
>
> The PiTFT22 support is optional and can be enabled by adding below in
> local.conf:
>
> MACHINE_FEATURES += "pitft pitft22"
>
> This patch also includes restructuring of kernel patches per kernel version
> specific directories.
>
> [Support #70]
>
> Signed-off-by: Petter Mabäcker <pet...@technux.se>
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  README |   7 +
>  conf/machine/include/rpi-base.inc  |   1 +
>  recipes-bsp/bootfiles/rpi-config_git.bb|   7 +
>  .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 
> +
>  ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 ++
>  .../0001-dts-add-overlay-for-pitft22.patch | 110 +
>  .../0001-dts-add-overlay-for-pitft22.patch | 110 +
>  .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 
> -
>  ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 --
>  recipes-kernel/linux/linux-raspberrypi_3.14.bb |   2 +
>  recipes-kernel/linux/linux-raspberrypi_3.18.bb |   7 +-
>  recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   6 +-
>  12 files changed, 745 insertions(+), 501 deletions(-)
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-3.14/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-3.18/0001-dts-add-overlay-for-pitft22.patch
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi/0001-ASoC-Add-BCM2708-fixes.patch
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
>
> diff --git a/README b/README
> index 129f5e2..536926b 100644
> --- a/README
> +++ b/README
> @@ -226,6 +226,13 @@ MACHINE_FEATURES += "pitft"
>  NOTE: To get this working the overlay for the PiTFT model must be build,
>added and specified as well (dtoverlay= in config.txt)
>
> +Below is a list of currently supported PiTFT models in meta-raspberrypi,
> +the modelname should be added as a MACHINE_FEATURES in local.conf like below:
> +- MACHINE_FEATURES += "pitft "
> +
> +List of currently supported models:
> +- pitft22
> +
>
>  4. Extra apps
>  =
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index c8f6cd6..27f09ad 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
>  overlays/iqaudio-dac-overlay.dtb \
>  overlays/iqaudio-dacplus-overlay.dtb \
>  overlays/lirc-rpi-overlay.dtb \
> +overlays/pitft22-overlay.dtb \
>  overlays/pps-gpio-overlay.dtb \
>  overlays/w1-gpio-overlay.dtb \
>  overlays/w1-gpio-pullup-overlay.dtb \
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index bfe00d1..4d41723 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
>  PR = "r4"
>
>  PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
> +PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
>
>  inherit deploy
>
> @@ -83,6 +84,12 @@ do_deploy() {
>  echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +
> +# PiTFT22 display support
> +if [ "${PITFT22}" = "1" ]; then
> +echo "# Enable PITFT22 display" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +fi
>  }
>
>  addtask deploy before do_package after do_install
> diff --git 
> a/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
>  
> b/recipes-kern

Re: [yocto] [meta-raspberrypi][PATCH v3 6/6] pitft: Add PiTFT22 support

[Andrei Gherzan]

t; ++
> + 2 files changed, 70 insertions(+)
> + create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
> +
> +diff --git a/arch/arm/boot/dts/overlays/Makefile 
> b/arch/arm/boot/dts/overlays/Makefile
> +index 1a60e9c..a2535a2 100644
> +--- a/arch/arm/boot/dts/overlays/Makefile
>  b/arch/arm/boot/dts/overlays/Makefile
> +@@ -37,6 +37,7 @@ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += piscreen2r-overlay.dtb
> ++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += pitft28-capacitive-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
> + dtb-$(RPI_DT_OVERLAYS) += pps-gpio-overlay.dtb
> +diff --git a/arch/arm/boot/dts/overlays/pitft22-overlay.dts 
> b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
> +new file mode 100755
> +index 000..894ba22
> +--- /dev/null
>  b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
> +@@ -0,0 +1,69 @@
> ++/*
> ++ * Device Tree overlay for pitft by Adafruit
> ++ *
> ++ */
> ++
> ++/dts-v1/;
> ++/plugin/;
> ++
> ++/ {
> ++compatible = "brcm,bcm2835", "brcm,bcm2708", "brcm,bcm2709";
> ++
> ++fragment@0 {
> ++target = <>;
> ++__overlay__ {
> ++status = "okay";
> ++
> ++spidev@0{
> ++status = "disabled";
> ++};
> ++
> ++spidev@1{
> ++status = "disabled";
> ++};
> ++};
> ++};
> ++
> ++fragment@1 {
> ++target = <>;
> ++__overlay__ {
> ++pitft_pins: pitft_pins {
> ++brcm,pins = <25>;
> ++brcm,function = <1>; /* out */
> ++brcm,pull = <0>; /* none */
> ++};
> ++};
> ++};
> ++
> ++fragment@2 {
> ++target = <>;
> ++__overlay__ {
> ++/* needed to avoid dtc warning */
> ++#address-cells = <1>;
> ++#size-cells = <0>;
> ++
> ++pitft: pitft@0{
> ++compatible = "ilitek,ili9340";
> ++reg = <0>;
> ++pinctrl-names = "default";
> ++pinctrl-0 = <_pins>;
> ++
> ++spi-max-frequency = <3200>;
> ++rotate = <90>;
> ++fps = <25>;
> ++bgr;
> ++buswidth = <8>;
> ++dc-gpios = < 25 0>;
> ++debug = <0>;
> ++};
> ++
> ++};
> ++};
> ++
> ++__overrides__ {
> ++speed =   <>,"spi-max-frequency:0";
> ++rotate =  <>,"rotate:0";
> ++        fps = <>,"fps:0";
> ++debug =   <>,"debug:0";
> ++};
> ++};
> +--
> +1.9.1
> +
> diff --git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb 
> b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> index a1fe6b4..9234f70 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> @@ -1,8 +1,9 @@
>  LINUX_VERSION ?= "3.18.16"
>
>  SRCREV = "1bb18c8f721ef674a447f3622273f2e2de7a205c"
> -SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y"
> -
> +SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y \
> +   file://0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch \
> +  "
>  require linux-raspberrypi.inc
>
>  # Create missing out of tree 'overlays' directory prior to install step
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> index 3a3cf40..b657c85 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> @@ -1,6 +1,8 @@
>  LINUX_VERSION ?= "4.1.10"
>
>  SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
> -SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
> +SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y \
> +   file://0001-dts-add-overlay-for-pitft22.patch \
> +  "
>
>  require linux-raspberrypi.inc

Cheers Peter!

Based on this patch I pushed a v4:
- resolve conflicts
- use patches specific for a certain kernel version in separate directories -
  easier to visualize

What do you think?

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

[yocto] [meta-raspberrypi][PATCH v4 1/1] pitft: Add PiTFT22 support

[Andrei Gherzan]

From: Petter Mabäcker <pet...@technux.se>

- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINE_FEATURES += "pitft pitft22"

This patch also includes restructuring of kernel patches per kernel version
specific directories.

[Support #70]

Signed-off-by: Petter Mabäcker <pet...@technux.se>
Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
---
 README |   7 +
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   7 +
 .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 +
 ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 ++
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 -
 ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 --
 recipes-kernel/linux/linux-raspberrypi_3.14.bb |   2 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   7 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   6 +-
 12 files changed, 745 insertions(+), 501 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.18/0001-dts-add-overlay-for-pitft22.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-ASoC-Add-BCM2708-fixes.patch
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch

diff --git a/README b/README
index 129f5e2..536926b 100644
--- a/README
+++ b/README
@@ -226,6 +226,13 @@ MACHINE_FEATURES += "pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be added as a MACHINE_FEATURES in local.conf like below:
+- MACHINE_FEATURES += "pitft "
+
+List of currently supported models:
+- pitft22
+
 
 4. Extra apps
 =
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index bfe00d1..4d41723 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
 PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 
 inherit deploy
 
@@ -83,6 +84,12 @@ do_deploy() {
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# PiTFT22 display support
+if [ "${PITFT22}" = "1" ]; then
+echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch 
b/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
new file mode 100644
index 000..26c71b8
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
@@ -0,0 +1,263 @@
+From e73a69601c65103b0e032e6093af0f00a1e1af3a Mon Sep 17 00:00:00 2001
+From: Florian Meier <florian.me...@koalo.de>
+Date: Fri, 22 Nov 2013 14:33:38 +0100
+Subject: [PATCH 1/2] ASoC: Add BCM2708 fixes
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+(cherry-pick remaining parts of
+730cb8a1216f9da3d097072

Re: [yocto] [meta-chip] How to flash yocto's output into CHIP

[Andrei Gherzan]

On 1 Mar 2016 19:45, "Jens Lucius"  wrote:
>
> Hi
>
> There is a pull request for the meta-sunxi layer. Maybe this would be a
good starting point?
>
> https://github.com/linux-sunxi/meta-sunxi/pull/126
>

That looks like duplicated work with meta-chip... Hm...

> Regards,
>
> Jens
>
>
> Am 23.02.2016 um 21:09 schrieb Valentin Le bescond:
>>
>> Hi,
>>
>> I'm wondering if anyone managed to flash the CHIP board with a
(successful) yocto image build.
>>
>> I didn't succeed but here are the few things I found :
>>
>> Comparing the files expected in CHIP-tools/ and the ones available in
Yocto deploy/image/chip/ I see some are missing in yocto :
>> uboot-env.bin
>> sunxi-spl-with-ecc.bin
>>
>> I tried using the ones downloaded with chip-update-firmware.sh but it
doesn't work...
>>
>> While flashing, at some point, the chip (in FEL mode) disconnects the
USB connection. If it goes well the chip reconnects as a ttyACM0. If it
doesn't go well (which is my case), chip never shows up !
>>
>> If anyone managed to get the thing working please let me know. If not I
am willing to try any idea you may have.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-chip][PATCH] added md5 for ntc's modified u-boot Licences/README file.

[Andrei Gherzan]

Hi Valentin,

Would you be able to repush with a commit title as stated in the commit
guidelines link from Readme?
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

Thanks a lot.

On 20 Feb 2016 5:26 pm, "Valentin LE BESCOND" 
wrote:
>
> From: Nitnelav 
>
> Signed-off-by: Nitnelav 
> ---
>  recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb b/recipes-bsp/u-boot/
u-boot-chip_git.bb
> index 2342478..0b9032f 100644
> --- a/recipes-bsp/u-boot/u-boot-chip_git.bb
> +++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
> @@ -8,6 +8,8 @@ PROVIDES += "u-boot"
>  UBOOT_VERSION ?= "2015.07"
>  PV = "${UBOOT_VERSION}+git${SRCPV}"
>
> +LIC_FILES_CHKSUM =
"file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
> +
>  SRCREV ?= "854d5fcc641d8d8914c03a69d7172815d5b81a99"
>  BRANCH ?= "chip/stable"
>  SRC_URI = "git://github.com/NextThingCo/CHIP-u-boot.git;branch=${BRANCH}"
> --
> 1.9.1
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-chip] How to flash yocto's output into CHIP

[Andrei Gherzan]

Hello,

On 24 Feb 2016 12:04 am, "Valentin Le bescond" 
wrote:
>
> I searched a bit more :
>
> The sunxi-spl-with-ecc.bin is built using the spl-image-builder bin in
the CHIP-tools folder (found here :
https://github.com/NextThingCo/CHIP-tools.git)
> I found a set of parameters (here : line 52 :
https://github.com/soderstrom-rikard/CHIP-tools/blob/chip/stable/chip-fel-flash.sh)
but I have no idea if it's right or wrong.
> That would give us :
> spl-image-builder -d -r 3 -u 4096 -o 1664 -p 16384 -c 1024 -s 64
sunxi-spl.bin sunxi-spl-with-ecc.bin
>
> I found that the uboot-env.bin file is not used to flash the chip (using
chip-fel-flash.sh file).
> But it should be easy to generate it as it is made with the "mkenvimage"
program that is found (an built by yocto) in the CHIP-uboot repo.
>
> Still not flashing though.
>
> I will look on the UART port of the chip for further tests. I hope to see
u-boot messages while flashing.
>
>
>
> Le mar. 23 févr. 2016 à 21:09, Valentin Le bescond <
valentin.lebesc...@gmail.com> a écrit :
>>
>> Hi,
>>
>> I'm wondering if anyone managed to flash the CHIP board with a
(successful) yocto image build.
>>
>> I didn't succeed but here are the few things I found :
>>
>> Comparing the files expected in CHIP-tools/ and the ones available in
Yocto deploy/image/chip/ I see some are missing in yocto :
>> uboot-env.bin
>> sunxi-spl-with-ecc.bin
>>
>> I tried using the ones downloaded with chip-update-firmware.sh but it
doesn't work...
>>
>> While flashing, at some point, the chip (in FEL mode) disconnects the
USB connection. If it goes well the chip reconnects as a ttyACM0. If it
doesn't go well (which is my case), chip never shows up !
>>
>> If anyone managed to get the thing working please let me know. If not I
am willing to try any idea you may have.
>>

I did flash chip successfully with Yocto artifacts. Haven't tried since I
created the layer but it surely worked and should work now too. Hopefully
I'll get some time to try it.

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

Re: [yocto] [meta-raspberrypi][PATCH v3 5/6] pitft: Add basic support for PiTFT

[Andrei Gherzan]

ram=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> diff --git 
> a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
>  
> b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
> new file mode 100644
> index 000..0d2b36b
> --- /dev/null
> +++ 
> b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
> @@ -0,0 +1,5 @@
> +Section "Device"
> +Identifier "Adafruit PiTFT"
> +Driver "fbdev"
> +Option "fbdev" "/dev/fb1"
> +EndSection
> diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
> b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
> index 2cf40f8..0ae2ee0 100644
> --- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
> +++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
> @@ -1,10 +1,17 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> -SRC_URI_append_rpi = " file://xorg.conf.d/10-evdev.conf "
> +SRC_URI_append_rpi = " file://xorg.conf.d/10-evdev.conf \
> +   file://xorg.conf.d/99-pitft.conf \
> + "
>
>  do_install_append_rpi () {
>   install -d ${D}/${sysconfdir}/X11/xorg.conf.d/
> - install -m 0644 ${WORKDIR}/xorg.conf.d/* 
> ${D}/${sysconfdir}/X11/xorg.conf.d/
> + install -m 0644 ${WORKDIR}/xorg.conf.d/10-evdev.conf 
> ${D}/${sysconfdir}/X11/xorg.conf.d/
> +
> + PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
> + if [ "${PITFT}" = "1" ]; then
> + install -m 0644 ${WORKDIR}/xorg.conf.d/99-pitft.conf 
> ${D}/${sysconfdir}/X11/xorg.conf.d/
> + fi
>  }
>
>  FILES_${PN}_rpi += "${sysconfdir}/X11/xorg.conf 
> ${sysconfdir}/X11/xorg.conf.d/*"
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 8c7c46c..e31270d 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -53,7 +53,11 @@ do_install_prepend() {
>  do_deploy_append() {
>  # Deploy cmdline.txt
>  install -d ${DEPLOYDIR}/bcm2835-bootfiles
> -echo "${CMDLINE}" > ${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
> +PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
> +if [ ${PITFT} = "1" ]; then
> +PITFT_PARAMS="fbcon=map:10 fbcon=font:VGA8x8"
> +fi
> +echo "${CMDLINE}${PITFT_PARAMS}" > 
> ${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
>  }
>
>  do_rpiboot_mkimage() {

Merged to master.

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

Re: [yocto] [meta-raspberrypi][PATCH v3 1/6] README: Add SPI bus chapter to content

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 02:46:08PM +0100, Petter Mabäcker wrote:
> The optional SPI bus chapter was missing in the content list.
>
> While at it also place it together with the other "optional" chapters,
> instead of in the end.
>
> Signed-off-by: Petter Mabäcker <pet...@technux.se>
> ---
>  README | 28 +++-
>  1 file changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/README b/README
> index 16ac1cb..a168692 100644
> --- a/README
> +++ b/README
> @@ -20,10 +20,11 @@ Contents:
>  2.F. Optional - Video camera support with V4L2 drivers
>  2.G. Optional - Enable offline compositing support
>  2.H. Optional - Enable kgdb over console support
> -2.I. Images
> -2.J. Boot to U-Boot
> -2.K. Image with Initramfs
> -2.L. Device tree support
> +2.I. Optional - Enable SPI bus
> +2.J. Images
> +2.K. Boot to U-Boot
> +2.L. Image with Initramfs
> +2.M. Device tree support
>  3. Extra apps
>  3.A. omxplayer
>  4. Source code and mirrors
> @@ -145,7 +146,13 @@ To add the kdbg over console (kgdboc) parameter to the 
> kernel command line,
>  set this variable in local.conf:
>  ENABLE_KGDB = "1"
>
> -2.I. Images
> +2.I. Optional - Enable SPI bus
> +==
> +When using device tree kernels, set this variable to enable the SPI bus
> +ENABLE_SPI_BUS = "1"
> +
> +
> +2.J. Images
>  ===
>  * rpi-hwup-image
>  Hardware up image
> @@ -155,7 +162,7 @@ ENABLE_KGDB = "1"
>  Image based on rpi-basic-image which includes most of the packages in 
> this
>  layer and some media samples.
>
> -2.J. Boot to U-Boot
> +2.K. Boot to U-Boot
>  ===
>  To have u-boot load kernel image, set in your local.conf
>  KERNEL_IMAGETYPE = "uImage"
> @@ -163,7 +170,7 @@ KERNEL_IMAGETYPE = "uImage"
>  This will make kernel.img be u-boot image which will load uImage.
>  By default, kernel.img is the actual kernel image (ex. Image).
>
> -2.K. Image with Initramfs
> +2.L. Image with Initramfs
>  =
>  To build an initramfs image :
>  * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
> @@ -176,7 +183,7 @@ To build an initramfs image :
>  * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
>  - KERNEL_INITRAMFS = "-initramfs"
>
> -2.L. Device tree support
> +2.M. Device tree support
>  =
>  Device tree for RPi is only supported when using linux-raspberrypi 3.18+
>  kernels.
> @@ -189,11 +196,6 @@ kernels.
>  NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
> disabled for
>older kernel versions.
>
> -2.M. Optional - enable SPI bus
> -==
> -When using device tree kernels, set this variable to enable the SPI bus
> -ENABLE_SPI_BUS = "1"
> -
>  3. Extra apps
>  =
>

I restructured a little the readme and included a similar change. It is master.
Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH v3 4/6] rpi-base.inc: Allow MACHINE_FEATURES appends

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 02:46:11PM +0100, Petter Mabäcker wrote:
> Ensure that it's possible to add MACHINE_FEATURES from places that will
> be executed before rpi-base.inc (like e.g. local.conf), without having
> them overrided.
>
> Signed-off-by: Petter Mabäcker <pet...@technux.se>
> ---
>  conf/machine/include/rpi-base.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index e097702..c8f6cd6 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -37,7 +37,7 @@ KERNEL_DEVICETREE ?= " \
>  "
>  KERNEL_IMAGETYPE ?= "Image"
>
> -MACHINE_FEATURES = "kernel26 apm usbhost keyboard vfat ext2 screen 
> touchscreen alsa bluetooth wifi sdio"
> +MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
> touchscreen alsa bluetooth wifi sdio"
>
>  # Raspberry Pi has no hardware clock
>  MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"

Merged to master. Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH v3 3/6] rpi-config: I2C support

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 02:46:10PM +0100, Petter Mabäcker wrote:
> With newer kernels (>=3.18) that supports device-trees I2C
> should be enabled with device-trees.
>
> This is now support by adding:
> ENABLE_I2C = "1"
> in local.conf
>
> This will enable the dtparams:
> i2c1
> i2c_arm
>
> Signed-off-by: Petter Mabäcker <pet...@technux.se>
> ---
>  README  | 21 +
>  recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
>  2 files changed, 19 insertions(+), 8 deletions(-)
>
> diff --git a/README b/README
> index a168692..8ef4e7a 100644
> --- a/README
> +++ b/README
> @@ -21,10 +21,11 @@ Contents:
>  2.G. Optional - Enable offline compositing support
>  2.H. Optional - Enable kgdb over console support
>  2.I. Optional - Enable SPI bus
> -2.J. Images
> -2.K. Boot to U-Boot
> -2.L. Image with Initramfs
> -2.M. Device tree support
> +2.J. Optional - Enable I2C
> +2.K. Images
> +2.L. Boot to U-Boot
> +2.M. Image with Initramfs
> +2.N. Device tree support
>  3. Extra apps
>  3.A. omxplayer
>  4. Source code and mirrors
> @@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
>  When using device tree kernels, set this variable to enable the SPI bus
>  ENABLE_SPI_BUS = "1"
>
> +2.J. Optional - Enable I2C
> +==
> +When using device tree kernels, set this variable to enable I2C
> +ENABLE_I2C = "1"
>
> -2.J. Images
> +2.K. Images
>  ===
>  * rpi-hwup-image
>  Hardware up image
> @@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
>  Image based on rpi-basic-image which includes most of the packages in 
> this
>  layer and some media samples.
>
> -2.K. Boot to U-Boot
> +2.L. Boot to U-Boot
>  ===
>  To have u-boot load kernel image, set in your local.conf
>  KERNEL_IMAGETYPE = "uImage"
> @@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
>  This will make kernel.img be u-boot image which will load uImage.
>  By default, kernel.img is the actual kernel image (ex. Image).
>
> -2.L. Image with Initramfs
> +2.M. Image with Initramfs
>  =
>  To build an initramfs image :
>  * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
> @@ -183,7 +188,7 @@ To build an initramfs image :
>  * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
>  - KERNEL_INITRAMFS = "-initramfs"
>
> -2.M. Device tree support
> +2.N. Device tree support
>  =
>  Device tree for RPi is only supported when using linux-raspberrypi 3.18+
>  kernels.
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index aa11b25..ccb9b7f 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -72,6 +72,12 @@ do_deploy() {
>  echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +
> +if [ -n "${ENABLE_I2C}" ]; then
> +echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +fi
>  }
>
>  addtask deploy before do_package after do_install

I rebased this on current master and merged to master. Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH v3 2/6] .gitignore: Ignore .swp files

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 02:46:09PM +0100, Petter Mabäcker wrote:
> Signed-off-by: Petter Mabäcker <pet...@technux.se>
> ---
>  .gitignore | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index 1677b58..f235765 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,2 +1,3 @@
>  build*
>  *~
> +.*.swp

Merged to master. Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH 1/1] omxplayer: Add patch to fix host-user-contaminated QA

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 11:32:53AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> Signed-off-by: Jonathan Liu <net...@gmail.com>
> ---
>  .../don-t-preserve-file-attributes-when-cp.patch   | 18 
> ++
>  recipes-multimedia/omxplayer/omxplayer_git.bb  |  1 +
>  2 files changed, 19 insertions(+)
>  create mode 100644 
> recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
>
> diff --git 
> a/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
>  
> b/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
> new file mode 100644
> index 000..08df12e
> --- /dev/null
> +++ 
> b/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
> @@ -0,0 +1,18 @@
> +When running install (fakeroot) host-user-contaminated will fail because dist
> +rule copies files while preserving file attributes like user ID.
> +
> +Upstream-Status: Submitted [https://github.com/popcornmix/omxplayer/pull/431]
> +Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> +
> +Index: git/Makefile
> +===
> +--- git.orig/Makefile
>  git/Makefile
> +@@ -87,5 +87,5 @@ dist: omxplayer.bin omxplayer.1
> + cp COPYING $(DIST)/usr/share/doc/omxplayer
> + cp README.md $(DIST)/usr/share/doc/omxplayer/README
> + cp omxplayer.1 $(DIST)/usr/share/man/man1
> +-cp -a ffmpeg_compiled/usr/lib/*.so* $(DIST)/usr/lib/omxplayer/
> ++cp -P ffmpeg_compiled/usr/lib/*.so* $(DIST)/usr/lib/omxplayer/
> + tar -czf omxplayer-dist.tar.gz $(DIST)
> +\ No newline at end of file
> diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
> b/recipes-multimedia/omxplayer/omxplayer_git.bb
> index a0690a0..c8251fe 100644
> --- a/recipes-multimedia/omxplayer/omxplayer_git.bb
> +++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
> @@ -18,6 +18,7 @@ SRC_URI = 
> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
> 
> file://0004-Add-FFMPEG_EXTRA_CFLAGS-and-FFMPEG_EXTRA_LDFLAGS.patch \
> file://fix-tar-command-with-DIST.patch \
> file://use-native-pkg-config.patch \
> +   file://don-t-preserve-file-attributes-when-cp.patch \
> "
>  S = "${WORKDIR}/git"
>

Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH 10/23] rpio: Include sys/types.h for caddr_t

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:49PM +, Khem Raj wrote:
> Fixes build with musl
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  ...-types.h-explicitly-for-getting-caddr_t-d.patch | 30 
> ++
>  recipes-devtools/python/rpio_0.10.0.bb |  6 ++---
>  2 files changed, 33 insertions(+), 3 deletions(-)
>  create mode 100644 
> recipes-devtools/python/rpio/0001-include-sys-types.h-explicitly-for-getting-caddr_t-d.patch
>
> diff --git 
> a/recipes-devtools/python/rpio/0001-include-sys-types.h-explicitly-for-getting-caddr_t-d.patch
>  
> b/recipes-devtools/python/rpio/0001-include-sys-types.h-explicitly-for-getting-caddr_t-d.patch
> new file mode 100644
> index 000..bed9749
> --- /dev/null
> +++ 
> b/recipes-devtools/python/rpio/0001-include-sys-types.h-explicitly-for-getting-caddr_t-d.patch
> @@ -0,0 +1,30 @@
> +From c86bfacc98d58244f532626954ed00d84ecfa82d Mon Sep 17 00:00:00 2001
> +From: Khem Raj <raj.k...@gmail.com>
> +Date: Sat, 30 Jan 2016 17:12:37 -0800
> +Subject: [PATCH] include sys/types.h explicitly for getting caddr_t 
> definition
> +
> +Helps fixing build on musl where sys/types.h is not included indirectly
> +as happening on glibc
> +
> +Signed-off-by: Khem Raj <raj.k...@gmail.com>
> +---
> +Upstream-Status: Submitted
> +
> + source/c_gpio/c_gpio.c | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/source/c_gpio/c_gpio.c b/source/c_gpio/c_gpio.c
> +index 25a04ca..70df632 100644
> +--- a/source/c_gpio/c_gpio.c
>  b/source/c_gpio/c_gpio.c
> +@@ -29,6 +29,7 @@
> + #include 
> + #include 
> + #include 
> ++#include 
> + #include 
> + #include "c_gpio.h"
> +
> +--
> +2.7.0
> +
> diff --git a/recipes-devtools/python/rpio_0.10.0.bb 
> b/recipes-devtools/python/rpio_0.10.0.bb
> index 1cc1661..69ecb6f 100644
> --- a/recipes-devtools/python/rpio_0.10.0.bb
> +++ b/recipes-devtools/python/rpio_0.10.0.bb
> @@ -7,9 +7,9 @@ LIC_FILES_CHKSUM = 
> "file://README.rst;beginline=41;endline=53;md5=d5d95d7486a4d9
>
>  SRCNAME = "RPIO"
>
> -SRC_URI = "\
> -  
> http://pypi.python.org/packages/source/R/RPIO/${SRCNAME}-${PV}.tar.gz \
> -  "
> +SRC_URI = 
> "http://pypi.python.org/packages/source/R/RPIO/${SRCNAME}-${PV}.tar.gz \
> +   
> file://0001-include-sys-types.h-explicitly-for-getting-caddr_t-d.patch \
> +   "
>  S = "${WORKDIR}/${SRCNAME}-${PV}"
>
>  inherit setuptools

Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH 07/23] python-rtimu: Fix build with musl

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:46PM +, Khem Raj wrote:
> ioctl(3) needs to include asm/ioctl.h for its signature
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  ...0001-include-asm-ioctl.h-for-ioctl-define.patch | 33 
> ++
>  recipes-devtools/python/python-rtimu_git.bb|  4 ++-
>  2 files changed, 36 insertions(+), 1 deletion(-)
>  create mode 100644 
> recipes-devtools/python/python-rtimu/0001-include-asm-ioctl.h-for-ioctl-define.patch
>
> diff --git 
> a/recipes-devtools/python/python-rtimu/0001-include-asm-ioctl.h-for-ioctl-define.patch
>  
> b/recipes-devtools/python/python-rtimu/0001-include-asm-ioctl.h-for-ioctl-define.patch
> new file mode 100644
> index 000..4a93a1c
> --- /dev/null
> +++ 
> b/recipes-devtools/python/python-rtimu/0001-include-asm-ioctl.h-for-ioctl-define.patch
> @@ -0,0 +1,33 @@
> +From c3aa4af56652b403e304ea5f321acfe289e42922 Mon Sep 17 00:00:00 2001
> +From: Khem Raj <raj.k...@gmail.com>
> +Date: Sat, 30 Jan 2016 16:07:14 -0800
> +Subject: [PATCH] include asm/ioctl.h for ioctl() define
> +
> +also fixes errors e.g.
> +
> +../../RTIMULib/RTIMUHal.cpp:208:29: error: '_IOC_SIZEBITS' was not
> +declared in this scope
> + return ioctl(m_SPI, SPI_IOC_MESSAGE(1), );
> +
> +Signed-off-by: Khem Raj <raj.k...@gmail.com>
> +---
> +Upstream-Status: Submitted
> +
> + RTIMULib/RTIMUHal.cpp | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/RTIMULib/RTIMUHal.cpp b/RTIMULib/RTIMUHal.cpp
> +index f9c3d15..d968326 100644
> +--- a/RTIMULib/RTIMUHal.cpp
>  b/RTIMULib/RTIMUHal.cpp
> +@@ -29,6 +29,7 @@
> + #if !defined(WIN32) && !defined(__APPLE__)
> +
> + #include 
> ++#include 
> +
> + RTIMUHal::RTIMUHal()
> + {
> +--
> +2.7.0
> +
> diff --git a/recipes-devtools/python/python-rtimu_git.bb 
> b/recipes-devtools/python/python-rtimu_git.bb
> index f51a234..63c92b3 100644
> --- a/recipes-devtools/python/python-rtimu_git.bb
> +++ b/recipes-devtools/python/python-rtimu_git.bb
> @@ -5,7 +5,9 @@ SECTION = "devel/python"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = 
> "file://../../LICENSE;md5=96cdecb41125f498958e09b72faf318e"
>
> -SRC_URI = 
> "git://github.com/RPi-Distro/RTIMULib.git;protocol=http;branch=master"
> +SRC_URI = 
> "git://github.com/RPi-Distro/RTIMULib.git;protocol=http;branch=master \
> +   
> file://0001-include-asm-ioctl.h-for-ioctl-define.patch;patchdir=../.. \
> +  "
>  SRCREV = "b949681af69b45f0f7f4bb53b6770037b5b02178"
>
>  S = "${WORKDIR}/git/Linux/python/"

Hi Raj! Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH 08/23] wiringPi: Fix build with musl

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:47PM +, Khem Raj wrote:
> Include asm/ioctl.h for _IOC_SIZEBITS
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  ...de-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch | 58 
> ++
>  recipes-devtools/wiringPi/wiringpi_git.bb  |  8 +--
>  2 files changed, 62 insertions(+), 4 deletions(-)
>  create mode 100644 
> recipes-devtools/wiringPi/wiringpi/0001-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
>
> diff --git 
> a/recipes-devtools/wiringPi/wiringpi/0001-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
>  
> b/recipes-devtools/wiringPi/wiringpi/0001-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
> new file mode 100644
> index 000..5de5853
> --- /dev/null
> +++ 
> b/recipes-devtools/wiringPi/wiringpi/0001-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch
> @@ -0,0 +1,58 @@
> +From 7f65eb37a82a6d9b095d9c8f262ad9dd205acd03 Mon Sep 17 00:00:00 2001
> +From: Khem Raj <raj.k...@gmail.com>
> +Date: Sat, 30 Jan 2016 16:57:38 -0800
> +Subject: [PATCH] include  directly for _IOC_SIZEBITS
> +
> +Fixes errors like
> +| wiringPiSPI.c: In function 'wiringPiSPIDataRW':
> +| wiringPiSPI.c:89:35: error: '_IOC_SIZEBITS' undeclared (first use in
> +this function)
> +
> +Signed-off-by: Khem Raj <raj.k...@gmail.com>
> +---
> +Upstream-Status: Submitted
> +
> + wiringPi/wiringPi.c| 1 +
> + wiringPi/wiringPiI2C.c | 1 +
> + wiringPi/wiringPiSPI.c | 1 +
> + 3 files changed, 3 insertions(+)
> +
> +diff --git a/wiringPi/wiringPi.c b/wiringPi/wiringPi.c
> +index 32e5100..cb5db9d 100644
> +--- a/wiringPi/wiringPi.c
>  b/wiringPi/wiringPi.c
> +@@ -64,6 +64,7 @@
> + #include 
> + #include 
> + #include 
> ++#include 
> + #include 
> + #include 
> + #include 
> +diff --git a/wiringPi/wiringPiI2C.c b/wiringPi/wiringPiI2C.c
> +index c787bce..efdf53c 100644
> +--- a/wiringPi/wiringPiI2C.c
>  b/wiringPi/wiringPiI2C.c
> +@@ -52,6 +52,7 @@
> + #include 
> + #include 
> + #include 
> ++#include 
> +
> + #include "wiringPi.h"
> + #include "wiringPiI2C.h"
> +diff --git a/wiringPi/wiringPiSPI.c b/wiringPi/wiringPiSPI.c
> +index 453df31..ae3c7d9 100644
> +--- a/wiringPi/wiringPiSPI.c
>  b/wiringPi/wiringPiSPI.c
> +@@ -27,6 +27,7 @@
> + #include 
> + #include 
> + #include 
> ++#include 
> + #include 
> + #include 
> +
> +--
> +2.7.0
> +
> diff --git a/recipes-devtools/wiringPi/wiringpi_git.bb 
> b/recipes-devtools/wiringPi/wiringpi_git.bb
> index 4254a0a..9d2206b 100644
> --- a/recipes-devtools/wiringPi/wiringpi_git.bb
> +++ b/recipes-devtools/wiringPi/wiringpi_git.bb
> @@ -9,10 +9,10 @@ SRCREV = "d79506694d7ba1c3da865d095238289d6175057d"
>
>  S = "${WORKDIR}/git"
>
> -SRC_URI = "\
> -  git://git.drogon.net/wiringPi \
> -  file://0001-Add-initial-cross-compile-support.patch \
> -  "
> +SRC_URI = "git://git.drogon.net/wiringPi \
> +   file://0001-Add-initial-cross-compile-support.patch \
> +   file://0001-include-asm-ioctl.h-directly-for-_IOC_SIZEBITS.patch \
> +   "
>
>  COMPATIBLE_MACHINE = "raspberrypi"
>

Hi Raj! Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH 19/23] rpi-config: Upgrade to tip of tree to get GPU_MEM_1024

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:58PM +, Khem Raj wrote:
> Document it in README
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  README  | 2 ++
>  recipes-bsp/bootfiles/rpi-config_git.bb | 5 -
>  2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/README b/README
> index 16ac1cb..efe885b 100644
> --- a/README
> +++ b/README
> @@ -90,6 +90,8 @@ GPU_MEM_256 : GPU memory in megabyte for the 256MB 
> Raspberry Pi. Ignored by the
>512MB RP. Overrides gpu_mem. Max 192. Default not set.
>  GPU_MEM_512 : GPU memory in megabyte for the 512MB Raspberry Pi. Ignored by 
> the
>256MB RP. Overrides gpu_mem. Max 448. Default not set.
> +GPU_MEM_1024: GPU memory in megabyte for the 1024MB Raspberry Pi. Ignored by 
> the
> +  256MB/512MB RP. Overrides gpu_mem. Max 944. Default not set.
>
>  2.C.Optional - Add purchased license codecs:
>  
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index aa11b25..4cdffca 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384
>
>  COMPATIBLE_MACHINE = "raspberrypi"
>
> -SRCREV = "5d2ca5f9bcb1b239c051e20c05a233fd79cf09d5"
> +SRCREV = "648ffc470824c43eb0d16c485f4c24816b32cd6f"
>  SRC_URI = 
> "git://github.com/Evilpaul/RPi-config.git;protocol=git;branch=master \
>"
>
> @@ -54,6 +54,9 @@ do_deploy() {
>  if [ -n "${GPU_MEM_512}" ]; then
>  sed -i '/#gpu_mem_512/ c\gpu_mem_512=${GPU_MEM_512}' 
> ${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
> +if [ -n "${GPU_MEM_1024}" ]; then
> +sed -i '/#gpu_mem_1024/ c\gpu_mem_1024=${GPU_MEM_1024}' 
> ${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +fi
>
>  # Video camera support
>  if [ -n "${VIDEO_CAMERA}" ]; then

Hi Raj,

Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH 17/23] linux-raspberrypi: Upgrade 4.1 kernel to 4.1.17

[Andrei Gherzan]

On Sat, Feb 27, 2016 at 03:26:56PM +, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> index 3a3cf40..d5bfa45 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> @@ -1,6 +1,6 @@
> -LINUX_VERSION ?= "4.1.10"
> +LINUX_VERSION ?= "4.1.17"
>
> -SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
> +SRCREV = "cb2f10196a9b718a2d94bb4ac0887c2ea14988ae"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
>
>  require linux-raspberrypi.inc

Hi Raj,

Merged to master. Thank you.

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

Re: [yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 02:44:36PM +0100, Petter Mabäcker wrote:
>2016-02-28 12:02 skrev Andrei Gherzan:
>
> On Sun, Feb 28, 2016 at 11:51:58AM +0100, Andrei Gherzan wrote:
>
>  On Sun, Feb 28, 2016 at 08:56:33AM +0100, Petter Mab�cker wrote:
>
>  2016-01-14 17:40 skrev Petter Mab?cker: [Support #69] Signed-off-by:
>  Petter Mab?cker <[1][1]pet...@technux.se> ---
>  recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++-- 1 file
>  changed, 2 insertions(+), 2 deletions(-) diff --git
>  a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
>  b/recipes-kernel/linu x/linux-raspberrypi_4.1.bb index
>  3a3cf40..cae459a 100644 ---
>  a/recipes-kernel/linux/linux-raspberrypi_4.1.bb +++
>  b/recipes-kernel/linux/linux-raspberrypi_4.1.bb @@ -1,6 +1,6 @@
>  -LINUX_VERSION ?= "4.1.10" +LINUX_VERSION ?= "4.1.15" -SRCREV =
>  "b74df9228c27f55361c065bc5dbfba88861cc771" +SRCREV =
>  "02a8ee530e32b08e5df44f10e24d5fd82bb960e3" SRC_URI =
>  "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.
>  y " require linux-raspberrypi.inc Hi Andrei, This commit can be
>  skipped, since Khem have done an even newer update of the 4.1 kernel
>  (4.1.10 --> 4.1.17) in the large series of commits from yesterday
>  ([2]https://lists.yoctoproject.org/pipermail/yocto/2016-February/028
>  754.ht ml). Do you want me to send an updated version of this series
>  of commit without it or not? BR Petter References 1.
>  mailto:[3]pet...@technux.se
>
>  Thanks Peter. No need to bother. I'll keep in mind not to pull this
>  patch.
>
> Petter,
>
> Actually I do have a request. Could you please send the v2 again (or a v3)
> cause even if they are on the ml archive I don't have it in my mailbox (this
> kinda worries me). Sorry for this and thank you in advance.
>
> --
> Andrei Gherzan
>
>I will send up a v3 with the kernel bump commit removed (and also a fix
>for a minor typo in the README..).
>
>BR Petter

Thank you Peter. This is the next one in line for testing and merging.

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

Re: [yocto] [meta-raspberrypi][PATCH v4 1/2] linux-raspberry.inc: add initramfs support

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 12:48:35PM +0100, Andrei Gherzan wrote:
> From: Stéphane Cerveau <scerv...@voxtok.com>
>
> append initramfs creation to install RPi bootloader trailer
>
> Signed-off-by: Stéphane Cerveau <vox...@voxtok.com>
> Signed-off-by: Andrei Gherzan <and...@gherzan.ro>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc | 10 ++
>  1 file changed, 10 insertions(+)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 8c7c46c..1befee4 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -64,4 +64,14 @@ do_rpiboot_mkimage() {
>  fi
>  fi
>  }
> +
> +do_bundle_initramfs_append() {
> +if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
> +if test -n "${KERNEL_DEVICETREE}"; then
> +# Add RPi bootloader trailer to kernel image to enable 
> DeviceTree support
> +${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok 
> ${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
> +fi
> +    fi
> +}
> +
>  addtask rpiboot_mkimage before do_install after do_compile
> --
> 2.7.0
>

Merged both patches to master.

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