Re: [yocto] [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add

[Trevor Woerner]

> what about use BOOT_IMG = "boot-${MACHINE}-${DATETIME}.img" instead? That
> will leave the previous build for debug and avoid trouble.

Using boot-${MACHINE}-${DATETIME}.img doesn't work, it leads to the following
errors:

ERROR: When reparsing 
/z/rockchip/master/layers/openembedded-core/meta/recipes-core/images/core-image-minimal.bb.do_image_rockchip_gpt_img,
 the basehash value changed from 7150ddd4bffcc76eed6ec85216596f3b to 
2c30fda706826e991aaf953180edc3b2. The metadata is not deterministic and this 
needs to be fixed.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [yocto-2.2.1][PATCH] Revert "tty: serial: 8250: add CON_CONSDEV to flags"

[Dengke Du]

From: Herbert Xu 

Upstream commit: 6741f551a0b26479de2532ffa43a366747e6dbf3

This commit needs to be reverted because it prevents people from
using the serial console as a secondary console with input being
directed to tty0.

IOW, if you boot with console=ttyS0 console=tty0 then all kernels
prior to this commit will produce output on both ttyS0 and tty0
but input will only be taken from tty0.  With this patch the serial
console will always be the primary console instead of tty0,
potentially preventing people from getting into their machines in
emergency situations.

Fixes: d03516df8375 ("tty: serial: 8250: add CON_CONSDEV to flags")
Signed-off-by: Herbert Xu 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman 

Upstream-Status: Backport
Signed-off-by: Dengke Du 
---
 drivers/tty/serial/8250/8250_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/tty/serial/8250/8250_core.c 
b/drivers/tty/serial/8250/8250_core.c
index dcf43f6..fa823a5 100644
--- a/drivers/tty/serial/8250/8250_core.c
+++ b/drivers/tty/serial/8250/8250_core.c
@@ -675,7 +675,7 @@ static struct console univ8250_console = {
.device = uart_console_device,
.setup  = univ8250_console_setup,
.match  = univ8250_console_match,
-   .flags  = CON_PRINTBUFFER | CON_ANYTIME | CON_CONSDEV,
+   .flags  = CON_PRINTBUFFER | CON_ANYTIME,
.index  = -1,
.data   = _reg,
 };
-- 
2.8.1

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

[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.0 Alejandro Hernandez
python2.7.12   2.7.13Alejandro Hernandez
python-native 2.7.12   2.7.13Alejandro Hernandez
python3-native3.5.23.6.0 Alejandro Hernandez
liberation-fonts  1.04 2.00.1Alexander Kanavin
2.x depends on fontforge pa...
libnl 3.2.28   3.2.29Alexander Kanavin
systemtap 3.0  3.1   Alexander Kanavin
boost 1.62.0   1.63.0Alexander Kanavin
openssl   1.0.2k   1.1.0eAlexander Kanavin
bjam-native   1.62.0   1.63.0Alexander Kanavin
libiconv  1.14 1.15  Alexander Kanavin
ed1.9  4.2.2 Alexander Kanavin
kbd   2.0.32.0.4 Alexander Kanavin
gperf 3.0.43.1   Alexander Kanavin
nss   3.27.1   3.28.1Alexander Kanavin
gnutls3.5.73.5.9 Alexander Kanavin
ffmpeg3.2.23.2.4 Alexander Kanavin
bash-completion   2.4  2.5   Alexander Kanavin
btrfs-tools   4.8.54.9.1 Alexander Kanavin
libwebp   0.5.10.6.0 Alexander Kanavin
babeltrace1.5.11.5.2 Alexander Kanavin
webkitgtk 2.14.2   2.14.5Alexander Kanavin
sysprof   3.22.3   3.23.90   Alexander Kanavin
systemtap-uprobes 3.0  3.1   Alexander Kanavin
iso-codes 3.72 3.74  Alexander Kanavin
epiphany  3.22.3   3.22.6Alexander Kanavin
mkelfimage4.0+gitX 4.5+gitAUTOINC+0b...  Alexander Kanavin
mkelfimage has been removed...
perl  5.24.0   5.24.1Aníbal Limón
perl-native   5.24.0   5.24.1Aníbal Limón
dpkg  1.18.7   1.18.22   Aníbal Limón
pinentry  0.9.21.0.0 Armin Kuster
linux-libc-headers4.9  4.10.1Bruce 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
curl  7.52.1   7.53.1Chen 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
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
sudo  1.8.18p1 1.8.19p2  Chen Qi
flex  2.6.22.6.3 Chen Qi
grep  2.27 3.0   Chen Qi
build-appliance-i...  15.0.0   16.0.1Cristian Iorga
chkconfig 1.3.58   1.8   Dengke Du
Version 1.5 requires selinux
ltp   20160126 20170116  Dengke Du
python3-setuptools32.1.1   34.3.0Edwin Plauchu
python-setuptools 32.1.1   34.3.0Edwin Plauchu
createrepo0.4.11   0.10.4Hongxu Jia   
Versions after 0.9.* use YU...
bash  4.3.30   4.4   Hongxu Jia
libinput  1.6.11.6.901   Jussi Kukkonen
wayland   1.12.0   1.13.0Jussi Kukkonen
weston1.11.1   2.0.0 Jussi Kukkonen
gtk-icon-utils-na...  3.22.7   3.22.8Jussi Kukkonen
libx11-diet   1.6.41.6.5 Jussi Kukkonen
libx111.6.41.6.5

Re: [yocto] Conflicts: Meta-layers with same priority

[SatyaNarayana Sampangi]

Thanks Paul.

-Satya Sampangi

On Mon, Feb 27, 2017 at 2:31 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> On Sunday, 26 February 2017 9:24:05 PM NZDT SatyaNarayana Sampangi wrote:
> > Hi all,
> >
> > I need to know, if two meta-layers in poky has the same priority, then
> how
> > it is resolved.
> >
> > say e.g,
> >
> > mylayer-1 with default priority:6
> > mylayer-2 with default priority:6
> >
> > How it will be resolved.
>
> If you mean which of two recipes with the same name will be selected, it
> will
> be the same as if the recipes were in the same layer - i.e. other
> mechanisms
> such as the version number (higher is preferred); DEFAULT_PREFERENCE (if
> specified); or PREFERRED_VERSION_recipename will be used to determine which
> gets selected.
>
> In general if one of these layers is under your control you are probably
> best
> advised to set the priority different there as desired, or use
> PREFERRED_VERSION to explicitly choose the desired version for recipes
> which
> are overlayed.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/2] yocto-bsp: remove 4.4 bbappend

[Bruce Ashfield]

The 4.4 kernel has been dropped, so we remove the associated bbappends.

Signed-off-by: Bruce Ashfield 
---
 .../recipes-kernel/linux/linux-yocto_4.4.bbappend  | 26 --
 1 file changed, 26 deletions(-)
 delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
deleted file mode 100644
index d92bfc0f516f..
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ /dev/null
@@ -1,26 +0,0 @@
-KBRANCH_genericx86  = "standard/base"
-KBRANCH_genericx86-64  = "standard/base"
-
-KMACHINE_genericx86 ?= "common-pc"
-KMACHINE_genericx86-64 ?= "common-pc-64"
-KBRANCH_edgerouter = "standard/edgerouter"
-KBRANCH_beaglebone = "standard/beaglebone"
-KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
-
-SRCREV_machine_genericx86?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
-SRCREV_machine_genericx86-64 ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
-SRCREV_machine_edgerouter ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
-SRCREV_machine_beaglebone ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
-SRCREV_machine_mpc8315e-rdb ?= "b01922f8b85d96b9f6996b17ed0995c6f782fdbf"
-
-COMPATIBLE_MACHINE_genericx86 = "genericx86"
-COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-COMPATIBLE_MACHINE_edgerouter = "edgerouter"
-COMPATIBLE_MACHINE_beaglebone = "beaglebone"
-COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
-
-LINUX_VERSION_genericx86 = "4.4.41"
-LINUX_VERSION_genericx86-64 = "4.4.41"
-LINUX_VERSION_edgerouter = "4.4.41"
-LINUX_VERSION_beaglebone = "4.4.41"
-LINUX_VERSION_mpc8315e-rdb = "4.4.41"
-- 
2.5.0

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

[yocto] [PATCH 0/2] poky/yocto-bsps: kernel version updates

[Bruce Ashfield]

Hi all,

These patches depend on the series sent to oe-core on Sunday February 26th.

That series introduces 4.10 as the latest kernel, and includes built/boot
testing for the qemu machines. As such, we can jump over 4.9 and make
4.10 the default version.

Also, since 4.4 is dropped in that series, we drop the 4.4 bbappend.

Bruce

The following changes since commit ebd2ca05bb2fff117f0467bb02762757c469ec6e:

  linux-yocto: drop 4.4 recipes (2017-02-26 21:52:40 -0500)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (2):
  poky: make 4.10 the qemu* default
  yocto-bsp: remove 4.4 bbappend

 meta-poky/conf/distro/poky.conf| 14 ++--
 .../recipes-kernel/linux/linux-yocto_4.4.bbappend  | 26 --
 2 files changed, 7 insertions(+), 33 deletions(-)
 delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend

-- 
2.5.0

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

Re: [yocto] Trying to build yocto-morty on ubuntu-16, machine reboots in the middle of the build

[akuster808]

On 2/25/17 8:16 AM, Joshua Watt wrote:
> 
> On 02/24/2017 11:36 AM, Burton, Ross wrote:
>>
>> On 23 February 2017 at 13:24, William McKinney > > wrote:
>>
>> I’m trying to build the yocto-morty release on an ubuntu 16.04.2
>> LTS box with 16GB of memory and plenty of disk space.  More than
>> once the machine appears to just reboot in the middle of the
>> build.  Has anyone else experienced this?  The krogoth and jethro
>> release build successfully on the same box.
>>
>>
>> Sounds like you've got hardware problems - obviously there's nothing
>> that Yocto can be doing to induce a reboot.
>>
>> I'd start with a memcheck and extended SMART tests.
> FWIW, I was having similar problems and a good blast of compressed air
> to my CPU heat sink fixed the problem. I ran 'dmesg -w' while building
> and it was pretty obvious that my CPU was overheating because I got a
> lot of messages like:
> 
> [ 3657.188178] mce: [Hardware Error]: Machine check events logged
> [ 3957.206279] CPU2: Core temperature above threshold, cpu clock
> throttled (total events = 1005969)
> 
> I wonder if there are some changes in Morty that make it better utilize
> the CPU compared to the other releases?

It's not just Morty. I have had this issue with other releases and on
Master. In my cases, the issues tend to be limited to building on
laptops. I have not seen this on towers or servers.

Try tuning your build to reduce the number for cpus and threads used.
see  PARALLEL_MAKE and BB_NUMBER_THREADS.

- armin



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

Re: [yocto] Python3 partial rootfs installation

[Paul Eggleton]

On Sunday, 26 February 2017 12:10:24 AM NZDT Jakob Simon-Gaarde wrote:
> Thanks for the answer. I tried adding it as a dependency but I get this:
> ERROR: Nothing PROVIDES 'python3-modules'

Based on your email, this is a runtime situation you are trying to resolve - 
and python3-modules is a runtime target, but that error suggests you are 
adding to DEPENDS which is for build-time dependencies.

You probably want to add python3-modules to IMAGE_INSTALL in your image recipe 
or perhaps to RDEPENDS_${PN} in the recipe for the custom software you're 
building.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Conflicts: Meta-layers with same priority

[Paul Eggleton]

On Sunday, 26 February 2017 9:24:05 PM NZDT SatyaNarayana Sampangi wrote:
> Hi all,
> 
> I need to know, if two meta-layers in poky has the same priority, then how
> it is resolved.
> 
> say e.g,
> 
> mylayer-1 with default priority:6
> mylayer-2 with default priority:6
> 
> How it will be resolved.

If you mean which of two recipes with the same name will be selected, it will 
be the same as if the recipes were in the same layer - i.e. other mechanisms 
such as the version number (higher is preferred); DEFAULT_PREFERENCE (if 
specified); or PREFERRED_VERSION_recipename will be used to determine which 
gets selected.

In general if one of these layers is under your control you are probably best 
advised to set the priority different there as desired, or use 
PREFERRED_VERSION to explicitly choose the desired version for recipes which 
are overlayed.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Conflicts: Meta-layers with same priority

[SatyaNarayana Sampangi]

Hi all,

I need to know, if two meta-layers in poky has the same priority, then how
it is resolved.

say e.g,

mylayer-1 with default priority:6
mylayer-2 with default priority:6

How it will be resolved.

Answers would be appreciated!

Thanks in Advance,
satya
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto