[yocto] [meta-rockchip][PATCH] README: remove irrelevant information

2017-04-29 Thread Trevor Woerner 
As of openembedded-core commit 2b3ae58f5eaecc8474761c543ff5347aa0e3c4c8 hardfp
is enabled by default.

Signed-off-by: Trevor Woerner 
---
 README | 16 
 1 file changed, 16 deletions(-)

diff --git a/README b/README
index b2e89f3..7f4a499 100644
--- a/README
+++ b/README
@@ -49,7 +49,6 @@ Table of Contents
   I. Configure yocto/oe environment
  II. Building a second level bootloader based on kexec
 III. Booting your device
- IV. Performance
 
 I. Configure yocto/oe environment
 
@@ -127,18 +126,3 @@ linux-next from tftp='tftp://192.168.0.5/zImage 
dtb=tftp://192.168.0.5/
 Then, plug your SDCARD into your Rockchip device and power on the board. If
 everything worked fine, Petitboot should be started automatically and list all 
 entries found in the configuration file.
-
-IV. Performance
-===
-
-By default a BSP layer should not be tuning a build, this is a DISTRO-level
-decision. As such the default machine settings are meant to be the lowest
-common denominator in order to maximize generality. If you are interested in
-tweaking your build to maximize performance you can either use a DISTRO that
-has these same goals, or you can add settings in your configuration files
-(e.g. local.conf) as follows:
-
-   for rk3288:
-   DEFAULTTUNE = "cortexa17hf-neon-vfpv4"
-   for rk3066:
-   DEFAULTTUNE = "cortexa9-neon"
-- 
2.12.0.rc1.48.g076c053

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

[yocto] Release Candidate Build for yocto-2.3.rc3 now available.

2017-04-29 Thread Poky Build User 

A release candidate build for yocto-2.3.rc3 is now available at:


http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc3


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 112643bbb731a6ccac7f4f5bde7f78d8fa2f9c15 
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd 
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6 
poky : a00f8981d8d2b361cc2c5d08d7cc6040c79af3cb 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: 
git://git.yoctoproject.org/yocto-autobuilder\nEmail: joshua.g.l...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Raspberry Pi 3 build issue

2017-04-29 Thread alexis . lothore 
Hello,
I finally figured out what was messing my build, and it was a poor 
mistake from my side... I am posting it here for anyone who could encounter a 
similar issue.

I did let my custom layer in my bblayer.conf. I did not think it could 
break the build, but I forgot about the bbappends there. In fact there was one 
bbappend trying to 
patch a dts file, and I poorly mixed overrides in the bbappend : I used a 
SRC_URI_raspberrypi3 to add the patch in the bbappend, but I also have put 
the patch in a machine specific directory (raspberrypi3/xxx.patch). 
Letting only the second option seems to be the correct way to proceed
(http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#best-practices-to-follow-when-creating-layers,
 
section "Place Machine-Specific Files in Machine-Specific Locations)

Regards,

On Tue, 25 Apr 2017, alexis.loth...@gmail.com wrote:

> Hello Paul,
> thanks for the try. It should means that there is a detail on my setup 
> which prevents the build from being done. I encounter the error on the 
> commits id your provided too. I also tried being on last tag on poky 
> project for morty branch, without success. I also suspected my python 
> configuration/version so I resintalled it completely, but It made no 
> change to the error.
> 
> On Tue, 25 Apr 2017, Paul Barker wrote:
> 
> > On Mon, Apr 24, 2017 at 7:25 PM,   wrote:
> > > Hello,
> > > I am currently encountering an issue with meta-raspberry and more
> > > specifically Raspberry Pi 3 build. Since I was not sure the problem was
> > > not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both
> > > checked out on morty, and meta dependencies on morty too), but the problem
> > > is still appearing, trying to build the image rpi-hwup-image with BDISTRO
> > > poky for MACHINE
> > > raspberrypi3 :
> > >
> > > ➜ build git:(morty) bitbake rpi-hwup-image
> > > Loading cache: 100%
> > > |#|
> > > Time: 0:00:00
> > > Loaded 2 entries from dependency cache.
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:
> > > Exception during build_dependencies for PKG_kernel-image | ETA: --:--:--
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:
> > > Error during finalise of
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:
> > > Exception during build_dependencies for PKG_kernel-image
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:
> > > Error during finalise of
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> > > ERROR: ExpansionError during parsing
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > Traceback (most recent call last):
> > > bb.data_smart.ExpansionError: Failure expanding variable PKG_kernel-image,
> > > expression was
> > > kernel-image-${@legitimize_package_name('${@get_kernelversion_headers('/home/alexis/Projets/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.9.21+git${SRCPV}-r0/linux-raspberrypi3-standard-build')}')}
> > > which triggered exception SyntaxError: invalid syntax (PKG_kernel-image,
> > > line 1)
> > > Summary: There were 4 WARNING messages shown.
> > > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> > >
> > > I am executing the build on an x86 machine with Debian 8.
> > >
> > > Unfortunately, since the problem seems to appear right at parsing, I
> > > cannot get the exact variable expansion with bitbake -e. Apparently my
> > > Yocto setup does not encounter the issue if I try the build for another
> > > RPI target, like raspberrypi0. Any advice on how to troubleshoot this
> > > issue ?
> > > --
> > 
> > I've just tried to reproduce this using a fresh clone of poky and
> > meta-raspberrypi on the morty branch. I edited bblayers.conf to add
> > the meta-raspberrypi layer and then edited local.conf to set MACHINE =
> > "raspberrypi3", those were my only changes. I then ran "bitbake
> > rpi-hwup-image" and it's correctly parsed all the recipes and started
> > the build.
> > 
> > Which exact commits of poky and meta-raspberrypi are you using? I have
> > the following:
> > 
> > meta
> > meta-poky
> > meta-yocto-bsp= "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
> > meta-raspberrypi  = "morty:28d4404f89eb59d406b4976c0e3f5ca19137ba74"
> > 
> > Thanks,
> > 
> > -- 
> > Paul Barker
> > Co-Founder & Principal Engineer
> > Togán Labs Ltd
> > -- 
___

Re: [yocto] [meta-rockchip][PATCH] linux: version bump to 4.11-rc8

2017-04-29 Thread Trevor Woerner 
Applied, thanks!

It's nice to finally see those "mmc_host mmc2: Bus speed (slot 0) = 5000Hz
(slot req 5200Hz, actual 5000HZ div = 0)" messages gone :-)

On Fri 2017-04-28 @ 03:58:57 PM, Romain Perier wrote:
> Linux kernel 4.11 being released soon, bump recipe to 4.11-rc8.
> 
> Signed-off-by: Romain Perier 
> ---
>  recipes-kernel/linux/linux_4.10.bb | 19 ---
>  recipes-kernel/linux/linux_4.11.bb | 20 
>  2 files changed, 20 insertions(+), 19 deletions(-)
>  delete mode 100644 recipes-kernel/linux/linux_4.10.bb
>  create mode 100644 recipes-kernel/linux/linux_4.11.bb
> 
> diff --git a/recipes-kernel/linux/linux_4.10.bb 
> b/recipes-kernel/linux/linux_4.10.bb
> deleted file mode 100644
> index e1d0aa4..000
> --- a/recipes-kernel/linux/linux_4.10.bb
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -# Copyright (C) 2017 Romain Perier
> -# Copyright (C) 2017 Eddie Cai
> -# Released under the MIT license (see COPYING.MIT for the terms)
> -
> -require recipes-kernel/linux/linux-yocto.inc
> -
> -SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
> -
> -SRCREV = "7089db84e356562f8ba737c29e472cc42d530dbc"
> -LINUX_VERSION = "4.10"
> -# Override local version in order to use the one generated by linux build 
> system
> -# And not "yocto-standard"
> -LINUX_VERSION_EXTENSION = ""
> -PR = "r1"
> -PV = "${LINUX_VERSION}-rc8"
> -
> -# Include only supported boards for now
> -COMPATIBLE_MACHINE = 
> "(radxarock|marsboard-rk3066|firefly-rk3288|rock2-square)"
> -deltask kernel_configme
> diff --git a/recipes-kernel/linux/linux_4.11.bb 
> b/recipes-kernel/linux/linux_4.11.bb
> new file mode 100644
> index 000..6058661
> --- /dev/null
> +++ b/recipes-kernel/linux/linux_4.11.bb
> @@ -0,0 +1,20 @@
> +# Copyright (C) 2017 Romain Perier
> +# Copyright (C) 2017 Eddie Cai
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
> +
> +SRCREV = "5a7ad1146caa895ad718a534399e38bd2ba721b7"
> +LINUX_VERSION = "4.11"
> +# Override local version in order to use the one generated by linux build 
> system
> +# And not "yocto-standard"
> +LINUX_VERSION_EXTENSION = ""
> +PR = "r1"
> +PV = "${LINUX_VERSION}-rc8"
> +
> +# Include only supported boards for now
> +COMPATIBLE_MACHINE = 
> "(radxarock|marsboard-rk3066|firefly-rk3288|rock2-square)"
> +deltask kernel_configme
> +
> -- 
> 1.8.3.1
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 4/5] u-boot-rockchip: remove duplicated variables

2017-04-29 Thread Trevor Woerner 
This doesn't succeed for me:

ERROR: 
/opt/oe/configs/z/build-master/firefly-rk3288/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb:
 This recipe does not have the LICENSE field set (u-boot-rockchip)
ERROR: Failed to parse recipe: 
/opt/oe/configs/z/build-master/firefly-rk3288/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb

But it does work if I add...

On Fri 2017-04-28 @ 04:01:25 PM, Romain Perier wrote:
>  # Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
>  # Copyright (C) 2017 Trevor Woerner <twoer...@gmail.com>
> +# Copyright (C) 2017 Romain Perier <romain.per...@collabora.com>
>  # Released under the MIT license (see COPYING.MIT for the terms)
>  
>  require recipes-bsp/u-boot/u-boot.inc
require recipes-bsp/u-boot/u-boot-common_2017.01.inc
>  
>  DESCRIPTION = "Rockchip next-dev U-Boot"
> -LICENSE = "GPLv2+"
> -LIC_FILES_CHKSUM = 
> "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
>  COMPATIBLE_MACHINE = "(firefly-rk3288)"
...

Does this make sense?

I'm building against openembedded-core
e584be78f92ee6f08f570c239698d56ac78d05f9

Build Configuration:
BB_VERSION= "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "opensuse-42.2"
TARGET_SYS= "arm-oe-linux-gnueabi"
MACHINE   = "firefly-rk3288"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
    TUNE_FEATURES = "arm armv7ve vfp thumb neon callconvention-hard"
TARGET_FPU= "hard"
meta-rockchip = 
"devs/rperier/20170429:0d89dcc4a5a2827b68d920bbd32e4aece774b5eb"
meta  = "master:e584be78f92ee6f08f570c239698d56ac78d05f9"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto