[meta-raspberrypi][morty][PATCH 0/2] Stable branch kernel upgrades

[meta-raspberrypi][morty][PATCH 0/2] Stable branch kernel upgrades

[Paul Barker]

I'm not 100% sure what the current policy is for upgrading the kernel in
meta-raspberrypi on a stable branch. I think it's a good idea to pull in
upgrades from the stable kernel series when available though so that we can
incorporate any upstream bugfixes. I'm also only considering backporting
upgrades we've already made on master.

I've also picked up the upgrade to the 4.9 kernel recipe as the old git hash
no longer exists upstream.

I've built & boot tested both 4.4 and 4.9 kernels on a rpi3 using morty plus
these patches.

Let me know if this is wanted for stable branches or not. If it is wanted, I'll
try to do this once a month or so for morty (and pyro when it's released) until
the end of the 12-month support period for each release.

Khem Raj (1):
  linux-raspberrypi_4.9.bb: Upgrade to 4.9.10

Paul Barker (1):
  linux-raspberrypi_4.4: Update to 4.4.48

 ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 ++++++++++++++++++++++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb      |  4 +--
 recipes-kernel/linux/linux-raspberrypi_4.9.bb      |  5 ++--
 3 files changed, 34 insertions(+), 4 deletions(-)
 create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch

-- 
2.11.0

[meta-raspberrypi][morty][PATCH 1/2] linux-raspberrypi_4.4: Update to 4.4.48

[Paul Barker]

Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
---
 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 0f78225..b235772 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.43"
+LINUX_VERSION ?= "4.4.48"
 
-SRCREV = "17ca1c930978a9ea6ddfec61fd0e2043e8ab3b17"
+SRCREV = "7ddf96fbb7d637b79b449c7bd1c8d35f00571e4b"
 SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
            file://0001-fix-dtbo-rules.patch \
 "
-- 
2.11.0

[meta-raspberrypi][morty][PATCH 2/2] linux-raspberrypi_4.9.bb: Upgrade to 4.9.10

[Paul Barker]

From: Khem Raj <raj.khem@gmail.com>

Fix dtbo builds for arm64

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
---
 ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 ++++++++++++++++++++++
 recipes-kernel/linux/linux-raspberrypi_4.9.bb      |  5 ++--
 2 files changed, 32 insertions(+), 2 deletions(-)
 create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch

diff --git a/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch b/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
new file mode 100644
index 0000000..e8bc52e
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
@@ -0,0 +1,29 @@
+From 922ce1fd0eb810b713f6ffa9a7ab97c11b6e38cf Mon Sep 17 00:00:00 2001
+From: Khem Raj <raj.khem@gmail.com>
+Date: Fri, 10 Feb 2017 17:57:08 -0800
+Subject: [PATCH] build/arm64: Add rules for .dtbo files for dts overlays
+
+We now create overlays as .dtbo files.
+
+Signed-off-by: Khem Raj <raj.khem@gmail.com>
+---
+ arch/arm64/Makefile | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
+index 3635b8662724..822fefeb1cd0 100644
+--- a/arch/arm64/Makefile
++++ b/arch/arm64/Makefile
+@@ -113,6 +113,9 @@ zinstall install:
+ %.dtb: scripts
+ 	$(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
+ 
++%.dtbo: | scripts
++	$(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++
+ PHONY += dtbs dtbs_install
+ 
+ dtbs: prepare scripts
+-- 
+2.11.1
+
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
index cffea1a..dcca369 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
@@ -1,8 +1,9 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.9.4"
+LINUX_VERSION ?= "4.9.10"
 
-SRCREV = "8b0be887f834e7eccf0de3edf630003880779a5f"
+SRCREV = "095c4480e1f623bdc8a221a171ef13b2223706b1"
 SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
+           file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
 "
 require linux-raspberrypi.inc
-- 
2.11.0

Re: [meta-raspberrypi][morty][PATCH 2/2] linux-raspberrypi_4.9.bb: Upgrade to 4.9.10

[Gary Thomas]

On 2017-02-19 12:18, Paul Barker wrote:
> From: Khem Raj <raj.khem@gmail.com>
>
> Fix dtbo builds for arm64
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
> ---
>  ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 ++++++++++++++++++++++
>  recipes-kernel/linux/linux-raspberrypi_4.9.bb      |  5 ++--
>  2 files changed, 32 insertions(+), 2 deletions(-)
>  create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch b/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
> new file mode 100644
> index 0000000..e8bc52e
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
> @@ -0,0 +1,29 @@
> +From 922ce1fd0eb810b713f6ffa9a7ab97c11b6e38cf Mon Sep 17 00:00:00 2001
> +From: Khem Raj <raj.khem@gmail.com>
> +Date: Fri, 10 Feb 2017 17:57:08 -0800
> +Subject: [PATCH] build/arm64: Add rules for .dtbo files for dts overlays
> +
> +We now create overlays as .dtbo files.
> +
> +Signed-off-by: Khem Raj <raj.khem@gmail.com>
> +---
> + arch/arm64/Makefile | 3 +++
> + 1 file changed, 3 insertions(+)
> +
> +diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> +index 3635b8662724..822fefeb1cd0 100644
> +--- a/arch/arm64/Makefile
> ++++ b/arch/arm64/Makefile
> +@@ -113,6 +113,9 @@ zinstall install:
> + %.dtb: scripts
> + 	$(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
> +
> ++%.dtbo: | scripts
> ++	$(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
> ++
> + PHONY += dtbs dtbs_install
> +
> + dtbs: prepare scripts
> +--
> +2.11.1
> +
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> index cffea1a..dcca369 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> @@ -1,8 +1,9 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.9.4"
> +LINUX_VERSION ?= "4.9.10"
>
> -SRCREV = "8b0be887f834e7eccf0de3edf630003880779a5f"
> +SRCREV = "095c4480e1f623bdc8a221a171ef13b2223706b1"
>  SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
> +           file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
>  "
>  require linux-raspberrypi.inc
>

+1 since the previous revision has gone walk-about :-(

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [meta-raspberrypi][morty][PATCH 0/2] Stable branch kernel upgrades

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]

Kernel upgrades for kernels are probably fine it's just incompatible
metadata changes that we have to be careful about

On Sun, Feb 19, 2017 at 3:20 AM Paul Barker <paul@paulbarker.me.uk> wrote:

> I'm not 100% sure what the current policy is for upgrading the kernel in
> meta-raspberrypi on a stable branch. I think it's a good idea to pull in
> upgrades from the stable kernel series when available though so that we can
> incorporate any upstream bugfixes. I'm also only considering backporting
> upgrades we've already made on master.
>
> I've also picked up the upgrade to the 4.9 kernel recipe as the old git
> hash
> no longer exists upstream.
>
> I've built & boot tested both 4.4 and 4.9 kernels on a rpi3 using morty
> plus
> these patches.
>
> Let me know if this is wanted for stable branches or not. If it is wanted,
> I'll
> try to do this once a month or so for morty (and pyro when it's released)
> until
> the end of the 12-month support period for each release.
>
> Khem Raj (1):
>   linux-raspberrypi_4.9.bb: Upgrade to 4.9.10
>
> Paul Barker (1):
>   linux-raspberrypi_4.4: Update to 4.4.48
>
>  ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29
> ++++++++++++++++++++++
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb      |  4 +--
>  recipes-kernel/linux/linux-raspberrypi_4.9.bb      |  5 ++--
>  3 files changed, 34 insertions(+), 4 deletions(-)
>  create mode 100644
> recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
>
> --
> 2.11.0
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 3197 bytes --]

Re: [meta-raspberrypi][morty][PATCH 0/2] Stable branch kernel upgrades

[Andrei Gherzan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Feb 20, 2017 at 02:04:41AM +0000, Khem Raj wrote:
> Kernel upgrades for kernels are probably fine it's just incompatible
> metadata changes that we have to be careful about
>
> On Sun, Feb 19, 2017 at 3:20 AM Paul Barker <paul@paulbarker.me.uk> wrote:
>
> > I'm not 100% sure what the current policy is for upgrading the kernel in
> > meta-raspberrypi on a stable branch. I think it's a good idea to pull in
> > upgrades from the stable kernel series when available though so that we can
> > incorporate any upstream bugfixes. I'm also only considering backporting
> > upgrades we've already made on master.
> >

I do agree as well that kernel updates are a good idea to backport as
long as they build and boot fine.

> > I've also picked up the upgrade to the 4.9 kernel recipe as the old git
> > hash
> > no longer exists upstream.
> >
> > I've built & boot tested both 4.4 and 4.9 kernels on a rpi3 using morty
> > plus
> > these patches.
> >
> > Let me know if this is wanted for stable branches or not. If it is wanted,
> > I'll
> > try to do this once a month or so for morty (and pyro when it's released)
> > until
> > the end of the 12-month support period for each release.
> >

Sounds good. Thanks Paul.

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

iQIzBAEBCAAdFiEE90oi/MnVCYFbB1m0Jrqo2vaxFPYFAliqi/UACgkQJrqo2vax
FPaEsg//QrALm5iqtKhrCVRlPmBvA9ghQYWB26D/1t6K6W31wa2El3Wqvh0JrqGJ
UhAuRFSly0prwkbpBqTyIMvj2DsVoZXclwk0+58c/scNDzu515PkvjhoUWUvcCq9
yTVNwKgKB2AAZEzOukjm5SgCFej5SxM5nrpuQhx2Gj9GNZVdNMWSoPLuTh8stZ/v
gVAp6Do0SHXHUBlJ1f1CsLERtcDCK6Afne2Vtp4IEXNVgMPH8N/rEtEx0vMv+WN/
ZGtGOa7bV9PVqjHOGQ5YaDOLaAV6MkcKu+GoimnKk7cneBmZ+6EC5V0DPQpOdVmZ
966SEVfOowaddZcbQsAezQZWQxvAtEPTW0FWFCeV+gFc/3O8XipKRhiDZbcGwj1b
x4v+GDbR1+iDf5quR7AT948l73ooKA5WMs+toQ9G3uOVlClbK2TdKM/dt0KOH4cU
JDURJn9FLTJfz85gPS09ILedO8RTJH0Avv1/9xeYDeTMNKhNL83R1G+gZAG4pu0S
bE3CYzy6vjwzkLTqgCo7Ivk460RGzXaIHcrgOo7vBqSlq/8kexC1xBLrOUavVpG7
5DuXokr0XExExTy4xt7jZVGhaUyts62J+pvJwwZGjHYAiTL1HoSUsljA/SAHcog4
d4zgCZtquLa4tBsnqMsvOP0rWX6BPG3kkA6znL/u67O5rjisJ4M=
=g68H
-----END PGP SIGNATURE-----

Re: [meta-raspberrypi][morty][PATCH 0/2] Stable branch kernel upgrades

[Andrei Gherzan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Feb 19, 2017 at 11:18:02AM +0000, Paul Barker wrote:
> I'm not 100% sure what the current policy is for upgrading the kernel in
> meta-raspberrypi on a stable branch. I think it's a good idea to pull in
> upgrades from the stable kernel series when available though so that we can
> incorporate any upstream bugfixes. I'm also only considering backporting
> upgrades we've already made on master.
>
> I've also picked up the upgrade to the 4.9 kernel recipe as the old git hash
> no longer exists upstream.
>
> I've built & boot tested both 4.4 and 4.9 kernels on a rpi3 using morty plus
> these patches.
>
> Let me know if this is wanted for stable branches or not. If it is wanted, I'll
> try to do this once a month or so for morty (and pyro when it's released) until
> the end of the 12-month support period for each release.
>
> Khem Raj (1):
>   linux-raspberrypi_4.9.bb: Upgrade to 4.9.10
>
> Paul Barker (1):
>   linux-raspberrypi_4.4: Update to 4.4.48
>
>  ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 ++++++++++++++++++++++
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb      |  4 +--
>  recipes-kernel/linux/linux-raspberrypi_4.9.bb      |  5 ++--
>  3 files changed, 34 insertions(+), 4 deletions(-)
>  create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
>
> --
> 2.11.0
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged both to morty branch. Thanks.

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

iQIzBAEBCAAdFiEE90oi/MnVCYFbB1m0Jrqo2vaxFPYFAliqjJcACgkQJrqo2vax
FPZfZw//cP6SM6UNz2D/r2AVirGhmdQcJwdXzkVhaS9D1MFZlCMCdxixj/RCedXP
x9VDjYhqu+xWYssCz9fgCq9Sdx4VCe0TLdIA9zbq3EFx7jLRzmO5QCz+F4ZcKgwJ
NzY6VRjxSKf2fFWRIDUiQ0PB9IYSdbYr4g4Vkjed+peC5t1UENnhmTAF6OpBycK5
Bb70MTpCWAKgyNlNi8hX2Q/Xd9fdC1NQc6sO8qWDSWqWC5itDZ2EPqMPWzsbjtSv
9KKP0D4RKYUQ0vt/Rzg6YuGv2PujM/JB/TCn/uRiVDeFJEvwOKOLMZhmnYRLlZa6
syaroZSGpB+Me7ams+UBZiyCa+uq2Eqtd/uxn7mmrgnfyamwbOibvIcooB/At1iX
mON+g5SlV3BCf0QCVpoo1YS9moLjfxt9WCos2J1ZLhM+tFC3rRryuYYgrLLus/CR
cRPXTvOURx/iX4o1he/RYzQQ1yi23POBzzVVRM14Y0BvnPtfX6rmAVlR6wY+08CF
br3ez2xEZWkA0Raoo1WaDyZ4yvoMX+2fMUObbYtYinJaMhHY5wntEUIvmKHr23x5
8vZxWrRABJ3X9tFHwLJIP9Vg52tsYvzB/eQfrRMuwjfxTrrql0fUMuKh0mwi5XPU
cLu/k8Ha5O8C2NFJGXiplblbG690kYQM8Txoh/D7JKc1IKdRyTs=
=+Md4
-----END PGP SIGNATURE-----