[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   Version  Upstream version  Maintainer   
NoUpgradeReason
  ---    ---  
--
python3   3.5.23.6.1 Alejandro Hernandez
python3-native3.5.23.6.1 Alejandro Hernandez
gobject-introspec...  1.50.0   1.52.0Alexander Kanavin
mobile-broadband-...  20151214 20170310  Alexander Kanavin
webkitgtk 2.14.5   2.16.0Alexander Kanavin
openssl   1.0.2k   1.1.0eAlexander Kanavin
gdbm  1.12 1.13  Alexander Kanavin
libpthread-stubs  0.3  0.4   Alexander Kanavin
vala  0.34.4   0.36.1Alexander Kanavin
lzo   2.09 2.10  Alexander Kanavin
libiconv  1.14 1.15  Alexander Kanavin
gnome-desktop33.22.2   3.24.0Alexander Kanavin
ed1.14.1   1.14.2Alexander Kanavin
nspr  4.13.1   4.14  Alexander Kanavin
gperf 3.0.43.1   Alexander Kanavin
libarchive3.2.23.3.1 Alexander Kanavin
gnutls3.5.93.5.10Alexander Kanavin
dtc   1.4.21.4.4 Alexander Kanavin
btrfs-tools   4.9.14.10.2Alexander Kanavin
mkelfimage4.0+gitX 4.5+gitAUTOINC+0b...  Alexander Kanavin
mkelfimage has been removed...
sysprof   3.22.3   3.24.0Alexander Kanavin
mpg1231.23.8   1.24.0Alexander Kanavin
kconfig-frontends 3.12.0.0 4.7.0.0   Alexander Kanavin
epiphany  3.22.6   3.24.0Alexander Kanavin
qemu  2.8.02.8.1 Aníbal Limón
apt   1.2.12   1.4   Aníbal Limón
libxml-namespaces...  1.11 1.12  Aníbal Limón
libxml-sax-base-perl  1.08 1.09  Aníbal Limón
apt-native1.2.12   1.4   Aníbal Limón
dpkg  1.18.10  1.18.23   Aníbal Limón
pinentry  0.9.21.0.0 Armin Kuster
libpcre2  10.2210.23 Armin Kuster
linux-libc-headers4.10 4.10.8Bruce Ashfield
libunwind 1.1+gitX 1.2+gitAUTOINC+cc...  Bruce Ashfield
pciutils  3.5.23.5.4 Chen Qi
kmod-native   23+gitX  24+gitAUTOINC+ef4...  Chen Qi
busybox   1.25.0+gitX  1.26.2+gitAUTOINC...  Chen Qi
dbus  1.10.14  1.10.16   Chen Qi
byacc 20161202 20170201  Chen Qi
cups  2.2.22.2.3 Chen Qi
systemd   232  233   Chen Qi
util-linux2.29.1   2.29.2Chen Qi
kmod  23+gitX  24+gitAUTOINC+ef4...  Chen Qi
dbus-test 1.10.14  1.10.16   Chen Qi
sed   4.2.24.4   Chen Qi
sysstat   11.5.4   11.5.5Chen Qi
systemd-boot  232  233   Chen Qi
flex  2.6.02.6.3 Chen Qi
coreutils 8.26 8.27  Chen Qi
build-appliance-i...  15.0.0   16.0.1Cristian Iorga
openssh   7.4p17.5p1 Dengke Du
json-glib 1.2.21.2.8 Dengke Du
u-boot-fw-utils   2017.01  2017.03   Denys Dmytriyenko
u-boot-mkimage2017.01  2017.03   Denys Dmytriyenko
u-boot2017.01  2017.03   Denys Dmytriyenko
python3-pygobject 3.22.0   3.24.0Edwin Plauchu
python3-setuptools32.1.1   34.3.3Edwin Plauchu
python-setuptools 32.1.1   34.3.3Edwin Plauchu
gpgme 1.8.01.9.0 Hongxu Jia
bash  4.3.30   4.4   Hongxu Jia
ghostscript   9.20 9.21  

Re: [yocto] Patch failures

[Bruce Ashfield]

On 2017-04-16 7:43 PM, Paul D. DeRocco wrote:

I'm trying to migrate an Atom-based build from Fido to Morty, and also
switch from 32-bit mode to x32. On a clean build, it gets about half way
through, and then suddenly coughs up a patch error. I've put blank lines
between the log lines so that the email word wrap won't be as confusing:

--

DEBUG: Executing shell function do_patch

(1/660) ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch

[INFO]: check of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
ule-addresses-dur.patch with "git am" did not pass, trying reduced
context.

[INFO]: Context reduced git-am of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
ule-addresses-dur.patch with "git am" did not work, trying "apply".

error: patch failed: arch/arm/mm/fault.c:448

error: arch/arm/mm/fault.c: patch does not apply

[ERROR]: Application of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-
the-TLB-for-module-addresses-dur.patch failed.

 Patch needs to be refreshed. Sample resolution script:

 .git/rebase-apply/resolve_rejects

WARNING:
/home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/run.do_patch.3069
0:1 exit 1 from 'kgit-s2q --gen -v --patches .kernel-meta/'

ERROR: Function failed: do_patch (log file is located at
/home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/log.do_patch.3069
0)

--

If I start bitbake again, it detects a "fence", and proceeds a little
further. I can do it over and over again, and it keeps building more and
more, but this can't be right, can it? The strange thing is that the
patches are all about ARM, PowerPC, etc., which have nothing to do with my
system. Could this be some fundamental misconfiguration having to do with
my MACHINE? At the beginning of my local.conf, I have:


The content of the patches isn't relative. All the patches are applied
all the time. Doing arch specific patches in a large patch queue turns
into a dependency soup ... hence the entire linux-yocto queue is
checked against the build branch on each build, and if something is
missing, patches are pushed.

What that sounds like is that your BSP doesn't have a proper definition
and hence entry point to the patching process. As such, whatever branch
is being built doesn't have the patches applied .. and hence the patches
are pushed and fail to apply in your context.

I can't say from what you've provided why the BSP description isn't
valid, but if the kernel recipe and layers are something I can look at,
I can debug more.

There were some changes between those releases that tweaked the kernel
meta-data processing .. and that could be the issue, but again, I can't
say without seeing all the details.

Bruce



MACHINE ?= "chroma-bsp"
DEFAULTTUNE = "core2-64-x32"
baselib = "libx32"

where chroma-bsp is defined in my own layer. My chroma-bsp.conf file
contains (among other things):

PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt"
PREFERRED_VERSION_linux-yocto-rt ?= "4.8%"
require conf/machine/include/tune-atom.inc
require conf/machine/include/x86-base.inc

I'm not really good at this. Does anyone see anything wrong?



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

Re: [yocto] [meta-raspberrypi][PATCH 2/2] x264: Fix build for armv6 RaspberryPi boards

[Andrei Gherzan]

On Mon, Apr 17, 2017 at 02:00:20AM +, Khem Raj wrote:
> On Sun, Apr 16, 2017 at 6:14 PM Andrei Gherzan  wrote:
>
> > quant-a.S uses rbit thumb instruction unconditionally even though only
> > from ARMV6T2 this is available (which is not the case for RPI1, RPI0
> > etc). Avoid this by disabling asm.
>
>
> It would be bette to control it in component's own build system how much do
> we lose in performance if any do you know
>

I haven't tested myself but I know people who did and reported a 10%
performance hit.

Now I see two more options - other than this one:
1. Deactivate in configure ASM if not HAVE_ARMV6T2 - don't see any
fuctional difference
2. emulate rbit if not HAVE_ARMV6T2 - do you have any ideas on how to do
this? I'd like this solution as rbit is the only instruction failing so
we could take advantage of the other optimisations.

PS: in the meanwhile i merged it to unblock the builds.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] Patch failures

[Khem Raj]

What's your build OS

On Sun, Apr 16, 2017 at 6:09 PM Paul D. DeRocco 
wrote:

> I'm trying to migrate an Atom-based build from Fido to Morty, and also
> switch from 32-bit mode to x32. On a clean build, it gets about half way
> through, and then suddenly coughs up a patch error. I've put blank lines
> between the log lines so that the email word wrap won't be as confusing:
>
> --
>
> DEBUG: Executing shell function do_patch
>
> (1/660) ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch
>
> [INFO]: check of
> .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
> ule-addresses-dur.patch with "git am" did not pass, trying reduced
> context.
>
> [INFO]: Context reduced git-am of
> .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
> ule-addresses-dur.patch with "git am" did not work, trying "apply".
>
> error: patch failed: arch/arm/mm/fault.c:448
>
> error: arch/arm/mm/fault.c: patch does not apply
>
> [ERROR]: Application of
> .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-
> the-TLB-for-module-addresses-dur.patch failed.
>
>  Patch needs to be refreshed. Sample resolution script:
>
>  .git/rebase-apply/resolve_rejects
>
> WARNING:
> /home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
> yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/run.do_patch.3069
> 0:1 exit 1 from 'kgit-s2q --gen -v --patches .kernel-meta/'
>
> ERROR: Function failed: do_patch (log file is located at
> /home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
> yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/log.do_patch.3069
> 0)
>
> --
>
> If I start bitbake again, it detects a "fence", and proceeds a little
> further. I can do it over and over again, and it keeps building more and
> more, but this can't be right, can it? The strange thing is that the
> patches are all about ARM, PowerPC, etc., which have nothing to do with my
> system. Could this be some fundamental misconfiguration having to do with
> my MACHINE? At the beginning of my local.conf, I have:
>
> MACHINE ?= "chroma-bsp"
> DEFAULTTUNE = "core2-64-x32"
> baselib = "libx32"
>
> where chroma-bsp is defined in my own layer. My chroma-bsp.conf file
> contains (among other things):
>
> PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt"
> PREFERRED_VERSION_linux-yocto-rt ?= "4.8%"
> require conf/machine/include/tune-atom.inc
> require conf/machine/include/x86-base.inc
>
> I'm not really good at this. Does anyone see anything wrong?
>
> --
>
> Ciao,   Paul D. DeRocco
> Paulmailto:pdero...@ix.netcom.com
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] x264: Fix build for armv6 RaspberryPi boards

[Khem Raj]

On Sun, Apr 16, 2017 at 6:14 PM Andrei Gherzan  wrote:

> quant-a.S uses rbit thumb instruction unconditionally even though only
> from ARMV6T2 this is available (which is not the case for RPI1, RPI0
> etc). Avoid this by disabling asm.


It would be bette to control it in component's own build system how much do
we lose in performance if any do you know

>
>
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-multimedia/x264/x264_git.bbappend | 1 +
>  1 file changed, 1 insertion(+)
>  create mode 100644 recipes-multimedia/x264/x264_git.bbappend
>
> diff --git a/recipes-multimedia/x264/x264_git.bbappend
> b/recipes-multimedia/x264/x264_git.bbappend
> new file mode 100644
> index 000..c1cb3bc
> --- /dev/null
> +++ b/recipes-multimedia/x264/x264_git.bbappend
> @@ -0,0 +1 @@
> +EXTRA_OECONF_append_raspberrypi = " --disable-asm"
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] README: document 64 bit r-pi3 variant for MACHINE

[Andrei Gherzan]

On Fri, Apr 07, 2017 at 02:59:22PM -0400, Paul Gortmaker wrote:
> Signed-off-by: Paul Gortmaker 
> ---
>  README | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/README b/README
> index 9fdd5eb523df..19c38c3a085a 100644
> --- a/README
> +++ b/README
> @@ -80,6 +80,7 @@ c. Set MACHINE in local.conf to one of the supported boards:
>  - raspberrypi0
>  - raspberrypi2
>  - raspberrypi3
> +- raspberrypi3-64 (64 bit kernel & userspace)
>  - raspberrypi-cm (dummy alias for raspberrypi)
>  - raspberrypi-cm3 (dummy alias for raspberrypi2)
>  d. bitbake rpi-hwup-image
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks Paul.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 6/6] psplash: Let distro override the default splash image if it provides

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 11:21:33AM -0700, Khem Raj wrote:
> BSPs should not be overriding the distro splash images, here we
> reduce the priority of psplash-raspberrypi below 100 so the defaults
> from distros can kick in.
>
> Signed-off-by: Khem Raj 
> ---
>  recipes-core/psplash/psplash_git.bbappend | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-core/psplash/psplash_git.bbappend 
> b/recipes-core/psplash/psplash_git.bbappend
> index 65dc30f..698564b 100644
> --- a/recipes-core/psplash/psplash_git.bbappend
> +++ b/recipes-core/psplash/psplash_git.bbappend
> @@ -1,2 +1,4 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> -SPLASH_IMAGES += "file://psplash-raspberrypi-img.h;outsuffix=raspberrypi"
> +SPLASH_IMAGES_append_rpi = " 
> file://psplash-raspberrypi-img.h;outsuffix=raspberrypi"
> +ALTERNATIVE_PRIORITY_psplash-raspberrypi[psplash] = "10"
> +
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks!

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 4/5] eglinfo-fb: Mark is userland specific

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:20:34AM -0700, Khem Raj wrote:
> It does not yet compile/work with vc4 open graphics driver
>
> Signed-off-by: Khem Raj 
> ---
>  recipes-graphics/eglinfo/eglinfo-fb_%.bbappend | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/recipes-graphics/eglinfo/eglinfo-fb_%.bbappend 
> b/recipes-graphics/eglinfo/eglinfo-fb_%.bbappend
> index 7f8b600..7692133 100644
> --- a/recipes-graphics/eglinfo/eglinfo-fb_%.bbappend
> +++ b/recipes-graphics/eglinfo/eglinfo-fb_%.bbappend
> @@ -1 +1,2 @@
>  EGLINFO_DEVICE_rpi  = "raspberrypi"
> +COMPATIBLE_HOST_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
> 'vc4graphics', 'null', '"(.*)"', d)}"
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks!

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 3/5] userland: Upgrade to latest

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:20:33AM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj 
> ---
>  .../0002-wayland-Add-support-for-the-Wayland-winsys.patch| 12 
> ++--
>  recipes-graphics/userland/userland_git.bb|  2 +-
>  2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git 
> a/recipes-graphics/userland/userland/0002-wayland-Add-support-for-the-Wayland-winsys.patch
>  
> b/recipes-graphics/userland/userland/0002-wayland-Add-support-for-the-Wayland-winsys.patch
> index 324fa91..c054572 100644
> --- 
> a/recipes-graphics/userland/userland/0002-wayland-Add-support-for-the-Wayland-winsys.patch
> +++ 
> b/recipes-graphics/userland/userland/0002-wayland-Add-support-for-the-Wayland-winsys.patch
> @@ -1,4 +1,4 @@
> -From 5f9e011a6c15b3a05b3be412d7ba5c1077ececf1 Mon Sep 17 00:00:00 2001
> +From 61a9d792ed774af43e592aa8fdb2a18488696d0f Mon Sep 17 00:00:00 2001
>  From: Tomeu Vizoso 
>  Date: Tue, 1 Oct 2013 13:19:20 +0200
>  Subject: [PATCH 02/13] wayland: Add support for the Wayland winsys
> @@ -102,7 +102,7 @@ index 358d2b4..4da4448 100644
>  +
>  +$ BUILD_WAYLAND=1 ./buildme.
>  diff --git a/buildme b/buildme
> -index 1061745..d0e6e54 100755
> +index b8fd440..a780bb6 100755
>  --- a/buildme
>  +++ b/buildme
>  @@ -8,6 +8,10 @@ fi
> @@ -117,7 +117,7 @@ index 1061745..d0e6e54 100755
>   # Native compile on the Raspberry Pi
>   mkdir -p build/raspberry/$BUILDSUBDIR
>  @@ -32,9 +36,13 @@ elif [ "$1" = "--native" ]; then
> - make -j 6 $*
> + make -j `nproc` $*
>   else
>   # Cross compile on a more capable machine
>  +if [ -n "$BUILD_WAYLAND" ]; then
> @@ -128,7 +128,7 @@ index 1061745..d0e6e54 100755
>   pushd build/arm-linux/$BUILDSUBDIR
>  -cmake 
> -DCMAKE_TOOLCHAIN_FILE=../../../makefiles/cmake/toolchains/arm-linux-gnueabihf.cmake
>  -DCMAKE_BUILD_TYPE=$BUILDTYPE ../../..
>  +cmake 
> -DCMAKE_TOOLCHAIN_FILE=../../../makefiles/cmake/toolchains/arm-linux-gnueabihf.cmake
>  -DCMAKE_BUILD_TYPE=$BUILDTYPE $WAYLAND_VARS ../../..
> - make -j 6
> + make -j `nproc`
>
>   if [ "$1" != "" ]; then
>  diff --git a/host_applications/linux/apps/raspicam/CMakeLists.txt 
> b/host_applications/linux/apps/raspicam/CMakeLists.txt
> @@ -1604,7 +1604,7 @@ index 37fdae1..fe3619a 100755
>   }
>   #endif
>  diff --git a/interface/vmcs_host/vc_vchi_dispmanx.c 
> b/interface/vmcs_host/vc_vchi_dispmanx.c
> -index 133e86d..45f4cff 100755
> +index 7a6cdcd..eab146e 100755
>  --- a/interface/vmcs_host/vc_vchi_dispmanx.c
>  +++ b/interface/vmcs_host/vc_vchi_dispmanx.c
>  @@ -1319,3 +1319,45 @@ static void *dispmanx_notify_func( void *arg ) {
> @@ -1885,5 +1885,5 @@ index 000..ad90d30
>  +set(${_sources} ${${_sources}} PARENT_SCOPE)
>  +endfunction()
>  --
> -2.12.0
> +2.12.2
>
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index afbe5ac..9526fae 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 = "cdb5da59f939eb4078e90ed0e3c231c498ba9957"
> +SRCREV = "f0642e3b58d8a140a3f7621630c15fbfa794b19d"
>
>  SRC_URI = "\
>  
> git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks Khem!

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 2/5] linux-raspberrypi_4.9.bb: Update to 4.9.21

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:20:32AM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj 
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> index 3aba67b..c0e8b83 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.9.13"
> +LINUX_VERSION ?= "4.9.21"
>
> -SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2"
> +SRCREV = "5e4ee836560d4c0371e109bf469e1ad808ae7a44"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
>  "
>  require linux-raspberrypi.inc
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged a similar patch to master.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 5/5] firmware: Update to 1.20170405 release

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:20:35AM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj 
> ---
>  recipes-bsp/common/firmware.inc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index 53c469e..1c3a911 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,10 +1,10 @@
> -RPIFW_DATE ?= "20170303"
> +RPIFW_DATE ?= "20170405"
>  RPIFW_SRC_URI ?= 
> "https://github.com/raspberrypi/firmware/archive/1.${RPIFW_DATE}.tar.gz;
>  RPIFW_S ?= "${WORKDIR}/firmware-1.${RPIFW_DATE}"
>
>  SRC_URI = "${RPIFW_SRC_URI}"
> -SRC_URI[md5sum] = "c87bc1bffbb8f254fc739e34baa03b02"
> -SRC_URI[sha256sum] = 
> "ee8758d7e63c8fea7c8b7b476ff1c09f9591c74349b7751036a78ae5b88eca36"
> +SRC_URI[md5sum] = "ea82d14a7cd8cfae9b78e00d4e56bc71"
> +SRC_URI[sha256sum] = 
> "2f4e5bddbac1372590db203002c35cbba3fb9d6172a93c314ee27bf05ae13bff"
>
>  PV = "${RPIFW_DATE}"
>
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged a similar patch.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 1/5] pitft: Add support for pitft35r

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:20:31AM -0700, Khem Raj wrote:
> From: Rob Woolley 
>
> The support for the PiTFT 3.5 inch resistive touchscreen is optional.
> It may be enabled by adding the following line in local.conf:
>
> MACHINE_FEATURES += "pitft pitft35r"
>
> Signed-off-by: Rob Woolley 
> Signed-off-by: Khem Raj 
> ---
>  README  | 1 +
>  conf/machine/include/rpi-base.inc   | 1 +
>  conf/machine/raspberrypi3-64.conf   | 1 +
>  recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
>  4 files changed, 9 insertions(+)
>
> diff --git a/README b/README
> index 9fdd5eb..e44475c 100644
> --- a/README
> +++ b/README
> @@ -241,6 +241,7 @@ the modelname should be added as a MACHINE_FEATURES in 
> local.conf like below:
>  List of currently supported models:
>  - pitft22
>  - pitft28r
> +- pitft35r
>
>  3.O. Misc. display
>  ==
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 092cbeb..9bcb91d 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
>  overlays/lirc-rpi.dtbo \
>  overlays/pitft22.dtbo \
>  overlays/pitft28-resistive.dtbo \
> +overlays/pitft35-resistive.dtbo \
>  overlays/pps-gpio.dtbo \
>  overlays/rpi-ft5406.dtbo \
>  overlays/w1-gpio.dtbo \
> diff --git a/conf/machine/raspberrypi3-64.conf 
> b/conf/machine/raspberrypi3-64.conf
> index ca10ed9..0efe3ff 100644
> --- a/conf/machine/raspberrypi3-64.conf
> +++ b/conf/machine/raspberrypi3-64.conf
> @@ -23,6 +23,7 @@ KERNEL_DEVICETREE = " \
>  overlays/lirc-rpi.dtbo \
>  overlays/pitft22.dtbo \
>  overlays/pitft28-resistive.dtbo \
> +overlays/pitft35-resistive.dtbo \
>  overlays/pps-gpio.dtbo \
>  overlays/rpi-ft5406.dtbo \
>  overlays/w1-gpio.dtbo \
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index af55983..b3c5084 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -18,6 +18,7 @@ PR = "r5"
>  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)}"
> +PITFT35r="${@bb.utils.contains("MACHINE_FEATURES", "pitft35r", "1", "0", d)}"
>
>  VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
> "0", d)}"
>
> @@ -99,6 +100,11 @@ do_deploy() {
>  echo 
> "dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>  fi
>
> +if [ "${PITFT35r}" = "1" ]; then
> +echo "# Enable PITFT35r display" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "dtoverlay=pitft35-resistive,rotate=90,speed=4200,fps=20" 
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +fi
> +
>  # UART support
>  if [ "${ENABLE_UART}" = "1" ]; then
>  echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> --
> 2.12.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged the patches from Rob. Thanks.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 1/7] rpi-gpio: Update to v0.6.2

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 09:13:07PM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-devtools/python/{rpi-gpio_0.6.1.bb => rpi-gpio_0.6.2.bb} | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename recipes-devtools/python/{rpi-gpio_0.6.1.bb => rpi-gpio_0.6.2.bb} (78%)
>
> diff --git a/recipes-devtools/python/rpi-gpio_0.6.1.bb 
> b/recipes-devtools/python/rpi-gpio_0.6.2.bb
> similarity index 78%
> rename from recipes-devtools/python/rpi-gpio_0.6.1.bb
> rename to recipes-devtools/python/rpi-gpio_0.6.2.bb
> index 89f601b..a08ea98 100644
> --- a/recipes-devtools/python/rpi-gpio_0.6.1.bb
> +++ b/recipes-devtools/python/rpi-gpio_0.6.2.bb
> @@ -10,8 +10,8 @@ SRC_URI = "\
>
> http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
>file://0001-Remove-nested-functions.patch \
>"
> -SRC_URI[md5sum] = "254d0443a436eb241367c487274e7197"
> -SRC_URI[sha256sum] = 
> "54e5fb06d9ea1a1389a497fb5a06dfa950c86303b0f4ba89b68c55999d1df064"
> +SRC_URI[md5sum] = "9db86fd5f3bae872de9dbb068ee0b096"
> +SRC_URI[sha256sum] = 
> "82acff0ef6bbe3cdf6f4dbdd73d96add5294bb94baf7f51c1d901861af3c2392"
>
>  S = "${WORKDIR}/${SRCNAME}-${PV}"
>
> --
> 2.12.1
>

Merged entire patch set to master.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH 1/2] omxplayer: Bump to head and fix missing native dependency

[Andrei Gherzan]

On Mon, Apr 17, 2017 at 02:12:05AM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-multimedia/omxplayer/omxplayer_git.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
> b/recipes-multimedia/omxplayer/omxplayer_git.bb
> index 72297d0..0e0f9ba 100644
> --- a/recipes-multimedia/omxplayer/omxplayer_git.bb
> +++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
> @@ -7,10 +7,10 @@ SECTION = "console/utils"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
>
> -DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba 
> libssh libomxil coreutils-native"
> +DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba 
> libssh libomxil coreutils-native curl-native"
>  PR = "r4"
>
> -SRCREV = "62fb580260adb9b01e5694bb4374fb9a5f6f1021"
> +SRCREV = "061425a5eabf6e9ee43229911c073a863d144038"
>  SRC_URI = 
> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
> 
> file://0001-Remove-Makefile.include-which-includes-hardcoded.patch \
> 
> file://0002-Libraries-and-headers-from-ffmpeg-are-installed-in-u.patch \
> --
> 2.12.2
>

Merged to master.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

Re: [yocto] [meta-raspberrypi][PATCH v2 0/3] pitft: Add support for pitft35r

[Andrei Gherzan]

On Thu, Apr 13, 2017 at 07:37:48PM +0100, Andrei Gherzan wrote:
> Hi Rob,
>
> On Thu, Apr 13, 2017 at 3:09 PM, Rob Woolley  
> wrote:
> > Hi Andrei,
> >
> > Does this patchset look okay?
> >
> > Are there any further changes you would like me to make?
>
> Looks good. I'll test it and merge it soon.

Merged to master. Thanks.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

[yocto] [meta-raspberrypi][PATCH 2/2] x264: Fix build for armv6 RaspberryPi boards

[Andrei Gherzan]

quant-a.S uses rbit thumb instruction unconditionally even though only
from ARMV6T2 this is available (which is not the case for RPI1, RPI0
etc). Avoid this by disabling asm.

Signed-off-by: Andrei Gherzan 
---
 recipes-multimedia/x264/x264_git.bbappend | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 recipes-multimedia/x264/x264_git.bbappend

diff --git a/recipes-multimedia/x264/x264_git.bbappend 
b/recipes-multimedia/x264/x264_git.bbappend
new file mode 100644
index 000..c1cb3bc
--- /dev/null
+++ b/recipes-multimedia/x264/x264_git.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF_append_raspberrypi = " --disable-asm"
-- 
2.12.2

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

[yocto] [meta-raspberrypi][PATCH 1/2] omxplayer: Bump to head and fix missing native dependency

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-multimedia/omxplayer/omxplayer_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index 72297d0..0e0f9ba 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,10 +7,10 @@ SECTION = "console/utils"
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh 
libomxil coreutils-native"
+DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh 
libomxil coreutils-native curl-native"
 PR = "r4"
 
-SRCREV = "62fb580260adb9b01e5694bb4374fb9a5f6f1021"
+SRCREV = "061425a5eabf6e9ee43229911c073a863d144038"
 SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
file://0001-Remove-Makefile.include-which-includes-hardcoded.patch \

file://0002-Libraries-and-headers-from-ffmpeg-are-installed-in-u.patch \
-- 
2.12.2

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Andreas Müller]

On Mon, Apr 17, 2017 at 2:27 AM, Trevor Woerner  wrote:
> On Mon 2017-04-17 @ 01:52:57 AM, Andreas Müller wrote:
>> On Sun, Apr 16, 2017 at 1:16 AM, Trevor Woerner  wrote:
>> > w00T! \O/
>> >
>> > Swapping out meta-raspberrypi for your meta-raspi-light works!!! I now have
>> > accelerated glmark2-es2 ~40FPS :-D
>> 40fps for glmark-es2 (did you mean glxgears)? The total result I get
>> for Pi3 on X11 (xfce) is ~105-117 depending on cpu-governor. I don't
>> know what Desktop/window manager you use but for graphics benchmarking
>> you should disable compositor.
>
> ;-) haha ;-)
> You couldn't just let me be happy?!
OK - I am really sorry for this :
> Yesterday it was running at 1FPS (*one*!! and probably less)
> ;-) haha ;-)
>
> I'm using openbox, I can't imagine anything more minimal than that. But I
> think I see where the difference lies. I usually run glmark2-es2 fullscreen.
Yeah openbox seems light weight and does no compositing.
> When I run it in its own little window:
>
> root@raspberrypi3:~# glmark2-es2
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> ===
> glmark2 2014.03
> ===
> OpenGL Information
> GL_VENDOR: Broadcom
> GL_RENDERER:   Gallium 0.4 on VC4 V3D 2.1
> GL_VERSION:OpenGL ES 2.0 Mesa 17.0.2
> ===
> [build] use-vbo=false: FPS: 126 FrameTime: 7.937 ms
> [build] use-vbo=true: FPS: 140 FrameTime: 7.143 ms
> [texture] texture-filter=nearest: FPS: 146 FrameTime: 6.849 ms
> [texture] texture-filter=linear: FPS: 141 FrameTime: 7.092 ms
> [texture] texture-filter=mipmap: FPS: 135 FrameTime: 7.407 ms
> [shading] shading=gouraud: FPS: 118 FrameTime: 8.475 ms
> [shading] shading=blinn-phong-inf: FPS: 102 FrameTime: 9.804 ms
> [shading] shading=phong: FPS: 69 FrameTime: 14.493 ms
> [shading] shading=cel: FPS: 69 FrameTime: 14.493 ms
> [bump] bump-render=high-poly: FPS: 68 FrameTime: 14.706 ms
> [bump] bump-render=normals: FPS: 154 FrameTime: 6.494 ms
> [bump] bump-render=height: FPS: 148 FrameTime: 6.757 ms
> [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 106 FrameTime: 9.434 ms
> [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 71 FrameTime: 
> 14.085 ms
> [pulsar] light=false:quads=5:texture=false: FPS: 129 FrameTime: 7.752 
> ms
> [desktop] 
> blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 44 
> FrameTime: 22.727 ms
> [desktop] effect=shadow:windows=4: FPS: 90 FrameTime: 11.111 ms
> [buffer] 
> columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map:
>  FPS: 63 FrameTime: 15.873 ms
> [buffer] 
> columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata:
>  FPS: 62 FrameTime: 16.129 ms
> [buffer] 
> columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map:
>  FPS: 73 FrameTime: 13.699 ms
> [ideas] speed=duration: FPS: 132 FrameTime: 7.576 ms
> [jellyfish] : FPS: 98 FrameTime: 10.204 ms
> [terrain] : FPS: 5 FrameTime: 200.000 ms
> [shadow] : FPS: 79 FrameTime: 12.658 ms
> [refract] : FPS: 20 FrameTime: 50.000 ms
> [conditionals] fragment-steps=0:vertex-steps=0: FPS: 145 FrameTime: 
> 6.897 ms
> [conditionals] fragment-steps=5:vertex-steps=0: FPS: 124 FrameTime: 
> 8.065 ms
> [conditionals] fragment-steps=0:vertex-steps=5: FPS: 145 FrameTime: 
> 6.897 ms
> [function] fragment-complexity=low:fragment-steps=5: FPS: 139 
> FrameTime: 7.194 ms
> [function] fragment-complexity=medium:fragment-steps=5: FPS: 39 
> FrameTime: 25.641 ms
> [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 135 
> FrameTime: 7.407 ms
> [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 
> 136 FrameTime: 7.353 ms
> [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 91 
> FrameTime: 10.989 ms
> ===
>   glmark2 Score: 101
> ===
> root@raspberrypi3:~# cat /proc/loadavg
> 0.15 0.15 0.09 1/130 458
>
> So, yes, I seem to be getting roughly what you're seeing.
Yes I think the difference of our results is noise
>
> I have no idea what govenor I'm using, whatever is the default.
I assume it is ondemand. That is default/fine (if you don't want to
play music keyboard/sequencer).
>
> Here's what I get for fullscreen:
>

[yocto] Patch failures

[Paul D. DeRocco]

I'm trying to migrate an Atom-based build from Fido to Morty, and also
switch from 32-bit mode to x32. On a clean build, it gets about half way
through, and then suddenly coughs up a patch error. I've put blank lines
between the log lines so that the email word wrap won't be as confusing:

--

DEBUG: Executing shell function do_patch

(1/660) ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch

[INFO]: check of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
ule-addresses-dur.patch with "git am" did not pass, trying reduced
context.

[INFO]: Context reduced git-am of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod
ule-addresses-dur.patch with "git am" did not work, trying "apply".

error: patch failed: arch/arm/mm/fault.c:448

error: arch/arm/mm/fault.c: patch does not apply

[ERROR]: Application of
.kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-
the-TLB-for-module-addresses-dur.patch failed.

 Patch needs to be refreshed. Sample resolution script:

 .git/rebase-apply/resolve_rejects

WARNING:
/home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/run.do_patch.3069
0:1 exit 1 from 'kgit-s2q --gen -v --patches .kernel-meta/'

ERROR: Function failed: do_patch (log file is located at
/home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux-
yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/log.do_patch.3069
0)

--

If I start bitbake again, it detects a "fence", and proceeds a little
further. I can do it over and over again, and it keeps building more and
more, but this can't be right, can it? The strange thing is that the
patches are all about ARM, PowerPC, etc., which have nothing to do with my
system. Could this be some fundamental misconfiguration having to do with
my MACHINE? At the beginning of my local.conf, I have:

MACHINE ?= "chroma-bsp"
DEFAULTTUNE = "core2-64-x32"
baselib = "libx32"

where chroma-bsp is defined in my own layer. My chroma-bsp.conf file
contains (among other things):

PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt"
PREFERRED_VERSION_linux-yocto-rt ?= "4.8%"
require conf/machine/include/tune-atom.inc
require conf/machine/include/x86-base.inc

I'm not really good at this. Does anyone see anything wrong?

-- 

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Andreas Müller]

On Mon, Apr 17, 2017 at 2:30 AM, Trevor Woerner  wrote:
> On Mon 2017-04-17 @ 01:23:25 AM, Andreas Müller wrote:
>> > Thank you very much for your explanations, they really cleared up a lot of
>> > stuff in my head. Already I'm 10x smarter on this stuff (which doesn't say
>> > much about where I started!) ;-) It was probably a good thing I spent the 
>> > last
>> > couple days grinding away, your explanations were perfect for where I'm at.
>> Some very good document explaining FOSS graphics stack is [1] - take
>> the time and some coffee :)
>
> link? :-)
Sure..

http://blog.mecheye.net/2012/06/the-linux-graphics-stack/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Trevor Woerner]

On Mon 2017-04-17 @ 01:23:25 AM, Andreas Müller wrote:
> > I got chromium building with it (it was a simple DEPENDS) and on the image I
> > just built sound is already working!
> * You have chromium building (and running?). This is on my endless
> TODO-list (have firefox on my image but that crashes more or less
> immediately - wonder what other people do with it)

There's been a nice surge in interest/help with chromium lately (not to
mention getting people to push upstream!) The recipes in OE are still building
a rather old version (54.0.2810.2) but it builds and works for x11 on x86
(qemux86), x86-64 (minnow), armv7 (bbb, raspi3-32), and armv8 (dragon 410c);
it builds for a couple more (firefly and raspi3-64) but I can't get xorg
working so I can't test it running.

You'll probably want to set the following PACKAGECONFIGs:

PACKAGECONFIG_pn-chromium = "disable-api-keys-info-bar 
ignore-lost-context impl-side-painting"

And (as I've mentioned) you'll need to add "mesa" to the DEPENDS (although I'm
not sure why it's now needed nor how to make that change in a "nice" way since
the non-accelerated version doesn't need it).

I'm not fully up-to-date on the wayland side, but I believe it builds and
works on wayland for roughly the same list plus beagleX15 and hikey. The
wayland version is slightly older at 53.0.2785.143.

There are people working on newer versions up to 59, but so far nobody's
pushing upstream. I'm hoping to take a look and getting something working. The
way chromium is built changed around the late 53 early 54 timeframe so a new
procedure is needed.

I've been running and testing with vc4 on my raspi3 for the last two hours
or so. I've seen one crash once when I tried to full-screen youtube, but
subsequent attempts have succeeded, so I'm not sure if those two events are
related. I've been doodling around in youtobe for all this time and it's been
mostly working except for that one instance.

> * I have not tested that (I need low latency and plugs for playing music)

The sound came though the HDMI for me. It's the first time I've heard a board
make noise :-)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Trevor Woerner]

On Mon 2017-04-17 @ 01:23:25 AM, Andreas Müller wrote:
> > Thank you very much for your explanations, they really cleared up a lot of
> > stuff in my head. Already I'm 10x smarter on this stuff (which doesn't say
> > much about where I started!) ;-) It was probably a good thing I spent the 
> > last
> > couple days grinding away, your explanations were perfect for where I'm at.
> Some very good document explaining FOSS graphics stack is [1] - take
> the time and some coffee :)

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Trevor Woerner]

On Mon 2017-04-17 @ 01:52:57 AM, Andreas Müller wrote:
> On Sun, Apr 16, 2017 at 1:16 AM, Trevor Woerner  wrote:
> > w00T! \O/
> >
> > Swapping out meta-raspberrypi for your meta-raspi-light works!!! I now have
> > accelerated glmark2-es2 ~40FPS :-D
> 40fps for glmark-es2 (did you mean glxgears)? The total result I get
> for Pi3 on X11 (xfce) is ~105-117 depending on cpu-governor. I don't
> know what Desktop/window manager you use but for graphics benchmarking
> you should disable compositor.

;-) haha ;-)
You couldn't just let me be happy?!
Yesterday it was running at 1FPS (*one*!! and probably less)
;-) haha ;-)

I'm using openbox, I can't imagine anything more minimal than that. But I
think I see where the difference lies. I usually run glmark2-es2 fullscreen.
When I run it in its own little window:

root@raspberrypi3:~# glmark2-es2
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
===
glmark2 2014.03
===
OpenGL Information
GL_VENDOR: Broadcom
GL_RENDERER:   Gallium 0.4 on VC4 V3D 2.1
GL_VERSION:OpenGL ES 2.0 Mesa 17.0.2
===
[build] use-vbo=false: FPS: 126 FrameTime: 7.937 ms
[build] use-vbo=true: FPS: 140 FrameTime: 7.143 ms
[texture] texture-filter=nearest: FPS: 146 FrameTime: 6.849 ms
[texture] texture-filter=linear: FPS: 141 FrameTime: 7.092 ms
[texture] texture-filter=mipmap: FPS: 135 FrameTime: 7.407 ms
[shading] shading=gouraud: FPS: 118 FrameTime: 8.475 ms
[shading] shading=blinn-phong-inf: FPS: 102 FrameTime: 9.804 ms
[shading] shading=phong: FPS: 69 FrameTime: 14.493 ms
[shading] shading=cel: FPS: 69 FrameTime: 14.493 ms
[bump] bump-render=high-poly: FPS: 68 FrameTime: 14.706 ms
[bump] bump-render=normals: FPS: 154 FrameTime: 6.494 ms
[bump] bump-render=height: FPS: 148 FrameTime: 6.757 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 106 FrameTime: 9.434 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 71 FrameTime: 
14.085 ms
[pulsar] light=false:quads=5:texture=false: FPS: 129 FrameTime: 7.752 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: 
FPS: 44 FrameTime: 22.727 ms
[desktop] effect=shadow:windows=4: FPS: 90 FrameTime: 11.111 ms
[buffer] 
columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map:
 FPS: 63 FrameTime: 15.873 ms
[buffer] 
columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata:
 FPS: 62 FrameTime: 16.129 ms
[buffer] 
columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map:
 FPS: 73 FrameTime: 13.699 ms
[ideas] speed=duration: FPS: 132 FrameTime: 7.576 ms
[jellyfish] : FPS: 98 FrameTime: 10.204 ms
[terrain] : FPS: 5 FrameTime: 200.000 ms
[shadow] : FPS: 79 FrameTime: 12.658 ms
[refract] : FPS: 20 FrameTime: 50.000 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 145 FrameTime: 
6.897 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 124 FrameTime: 
8.065 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 145 FrameTime: 
6.897 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 139 
FrameTime: 7.194 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 39 
FrameTime: 25.641 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 135 
FrameTime: 7.407 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 136 
FrameTime: 7.353 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 91 
FrameTime: 10.989 ms
===
  glmark2 Score: 101 
===
root@raspberrypi3:~# cat /proc/loadavg 
0.15 0.15 0.09 1/130 458

So, yes, I seem to be getting roughly what you're seeing.

I have no idea what govenor I'm using, whatever is the default.

Here's what I get for fullscreen:

root@raspberrypi3:~# glmark2-es2 --fullscreen --annotate
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
===
glmark2 2014.03
===
OpenGL Information
GL_VENDOR: Broadcom
GL_RENDERER:   Gallium 

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Andreas Müller]

On Sun, Apr 16, 2017 at 1:16 AM, Trevor Woerner  wrote:
> w00T! \O/
>
> Swapping out meta-raspberrypi for your meta-raspi-light works!!! I now have
> accelerated glmark2-es2 ~40FPS :-D
40fps for glmark-es2 (did you mean glxgears)? The total result I get
for Pi3 on X11 (xfce) is ~105-117 depending on cpu-governor. I don't
know what Desktop/window manager you use but for graphics benchmarking
you should disable compositor.

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Andreas Müller]

On Sun, Apr 16, 2017 at 1:16 AM, Trevor Woerner  wrote:
> w00T! \O/
>
> Swapping out meta-raspberrypi for your meta-raspi-light works!!! I now have
> accelerated glmark2-es2 ~40FPS :-D
>
> Now I have to figure out why...
>
> Also, chromium wouldn't build with meta-raspi2-light, but that's probably a
> quick fix, GL/glx.h was missing.
>
> Adding 'MACHINE_FEATURES_append = " vc4graphics"' to local.conf with
> meta-raspberrypi caused a kernel Oops. The system continues to run, but
> graphics/X doesn't work.
>
> One thing I've noticed about both meta-raspberrypi and meta-raspi-light are
> that in both cases (using vc4) the boot colour square (firmware?), processor
> core count berries, and kernel splash screen are missing. But that's not too
> important.
Yes - but I think this is not a bug. For me the so called 'rainbow'
screen was the indication I have VC4 properly set up.
>
> Thank you very much for your explanations, they really cleared up a lot of
> stuff in my head. Already I'm 10x smarter on this stuff (which doesn't say
> much about where I started!) ;-) It was probably a good thing I spent the last
> couple days grinding away, your explanations were perfect for where I'm at.
Some very good document explaining FOSS graphics stack is [1] - take
the time and some coffee :)
>
> Any idea how mesa and mesa-gl differ? That one's still an outlier for me; they
> both come from the same source base!
* userland builds egl/gles2 libraries
* mesa-gl is a drop in for (Desktop) OpenGL to ensure we can build
applications which need it. AFAIK it is shipped with swrast - so not
really useful.
>
> On Sat 2017-04-15 @ 08:09:02 PM, Andreas Müller wrote:
>> In the long run I would start a discussion:
>>
>> * Mesa/VC4 is not a machine feature only available on 64Bit Pi3 only:
>> It is common to all version of RaspberryPi. Using mesa should be a
>> decision easily selected by a setting somewhere. The only reason 64Bit
>> Pi3 gets VC4 by default is that userland is not working for 64Bit -
>> see commit 9d418db5ed2962821987ac90c07c3a61e40c0814)
>> * Why still use userland? Dropping it would make things MUCH easier:
>> All the decisions based vc4graphics in MACHINE_FEATURES could be
>> removed (that's what my fork does)
>
> Agreed! Maybe a new thread? I'd want to do more experiments wrt 32 vs 64 and
> vc4 vs userland before being able to contribute.
>
I cherry-pick from meta-raspberrypi what I can - also Pi3-64
configuration. But I have not run a test with 64Bit on Pi3 (I don't
expect any enhancements for my use cases).

Your next email:
> I got chromium building with it (it was a simple DEPENDS) and on the image I
> just built sound is already working!
* You have chromium building (and running?). This is on my endless
TODO-list (have firefox on my image but that crashes more or less
immediately - wonder what other people do with it)
* I have not tested that (I need low latency and plugs for playing music)

Have fun and keep me updated...

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Trevor Woerner]

On Sat 2017-04-15 @ 08:09:02 PM, Andreas Müller wrote:
> You can have
> accelerated X11 + wayland in one image without any trouble with proper
> working modesetting (and HDMI sound is on it's way).

I got chromium building with it (it was a simple DEPENDS) and on the image I
just built sound is already working!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 3/7] firmware.inc: Bump to 20170405

[Andrei Gherzan]

On Fri, Apr 14, 2017 at 04:43:16PM -0700, Khem Raj wrote:
> same :) see my series.
>

You were a little faster so you won.
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


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

[yocto] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

Hello All

I have put together recipes for upcoming gcc-7 major release as well
as glibc 2.26 release, which we would target for next release ( 2.4 )

There are several changes in gcc-7 which will need fixing packages. If you have
time to spare feel free to give it a shot and send fixes for the packages or bug
reports. Below are commits you can cherry-pick independently.

gcc7 -  
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/gcc7=9562231d6a37ea9c59086927bf0c854fd40b29cd

glib-2.26 - 
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/glibc-2.26=6e91059d3f6ca0f4468ff59a2c7449be301ee100

Refer to

https://gcc.gnu.org/gcc-7/porting_to.html

For porting issues with gcc7

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