Raspberry PI 3 kernel, firmware and dtb update

PATCH New Ubaldo Porcheddu 4 participants 8 messages Mar 31, 2016 – Apr 23, 2016 Broadcom BCM2711/BCM2835 Arm architecture

lore

Share & tools

lore

Ubaldo Porcheddu

author

2016-03-31 10:51 UTC #0 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Signed-off-by Ubaldo Porcheddu <[email protected]>

---
 board/raspberrypi/genimage-raspberrypi2.cfg | 1 +
 configs/raspberrypi2_defconfig              | 4 ++--
 package/rpi-firmware/rpi-firmware.mk        | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

board/raspberrypi/genimage-raspberrypi2.cfg +1 -0

index 443c821..453fb00 100644
@@ -2,6 +2,7 @@ image boot.vfat {
   vfat {
     files = {
       "bcm2709-rpi-2-b.dtb",
+      "bcm2710-rpi-3-b.dtb",
       "rpi-firmware/bootcode.bin",
       "rpi-firmware/cmdline.txt",
       "rpi-firmware/config.txt",

configs/raspberrypi2_defconfig +2 -2

index ce41ee3..b77db14 100644
@@ -13,13 +13,13 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="d33d0293e245badc4ca6ede3984d8bb8ea63cb1a"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="20fe468af4bb40fec0f81753da4b20a8bfc259c9"
 BR2_LINUX_KERNEL_DEFCONFIG="bcm2709"
 BR2_LINUX_KERNEL_ZIMAGE=y
 
 # Build the DTB from the kernel sources
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b bcm2710-rpi-3-b"
 
 BR2_PACKAGE_RPI_FIRMWARE=y
 # BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS is not set

package/rpi-firmware/rpi-firmware.mk +1 -1

index 291da3a..8476678 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-RPI_FIRMWARE_VERSION = 8b4e5482b52e6fb438dddc0d88ba0ba8d44af54b
+RPI_FIRMWARE_VERSION = 951799bbcd795ddf27769d14acf4813fdcbe53dc
 RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
 RPI_FIRMWARE_LICENSE = BSD-3c
 RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom

Signature · 1 line

1.9.1

Peter Korsgaard

2016-04-19 20:45 UTC #1 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Quoted 8 lines

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Ubaldo" == Ubaldo Porcheddu <[email protected]> writes:
Signed-off-by Ubaldo Porcheddu <[email protected]>
---
 board/raspberrypi/genimage-raspberrypi2.cfg | 1 +
 configs/raspberrypi2_defconfig              | 4 ++--
 package/rpi-firmware/rpi-firmware.mk        | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

Thanks for the patch, but can you instead split it up 2 seperate patches (with sensible descriptions) - One bumping the rpi-firmware version and one updating the rpi2 config to also support rpi3.

The rpi3 afaik uses a different serial port than rpi2. How will that work if we use the same defconfig for both boards? Perhaps it makes more sense to have a seperate raspberrypi3_defconfig?

Quoted 52 lines

board/raspberrypi/genimage-raspberrypi2.cfg +1 -0

index 443c821..453fb00 100644
@@ -2,6 +2,7 @@ image boot.vfat {
   vfat {
     files = {
       "bcm2709-rpi-2-b.dtb",
+      "bcm2710-rpi-3-b.dtb",
       "rpi-firmware/bootcode.bin",
       "rpi-firmware/cmdline.txt",
       "rpi-firmware/config.txt",

configs/raspberrypi2_defconfig +2 -2

index ce41ee3..b77db14 100644
@@ -13,13 +13,13 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="d33d0293e245badc4ca6ede3984d8bb8ea63cb1a"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="20fe468af4bb40fec0f81753da4b20a8bfc259c9"
 BR2_LINUX_KERNEL_DEFCONFIG="bcm2709"
 BR2_LINUX_KERNEL_ZIMAGE=y
 
 # Build the DTB from the kernel sources
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b bcm2710-rpi-3-b"
 
 BR2_PACKAGE_RPI_FIRMWARE=y
 # BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS is not set

package/rpi-firmware/rpi-firmware.mk +1 -1

index 291da3a..8476678 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-RPI_FIRMWARE_VERSION = 8b4e5482b52e6fb438dddc0d88ba0ba8d44af54b
+RPI_FIRMWARE_VERSION = 951799bbcd795ddf27769d14acf4813fdcbe53dc
 RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
 RPI_FIRMWARE_LICENSE = BSD-3c
 RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom

Signature · 6 lines

1.9.1

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 1 line

Bye, Peter Korsgaard

Yann E. MORIN

2016-04-19 21:33 UTC #2 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Ubaldo, Peter, All,

On 2016-04-19 22:45 +0200, Peter Korsgaard spake thusly:

Quoted 9 lines

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Ubaldo" == Ubaldo Porcheddu <[email protected]> writes:
Signed-off-by Ubaldo Porcheddu <[email protected]>
---
 board/raspberrypi/genimage-raspberrypi2.cfg | 1 +
 configs/raspberrypi2_defconfig              | 4 ++--
 package/rpi-firmware/rpi-firmware.mk        | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

Quoted 7 lines

Thanks for the patch, but can you instead split it up 2 seperate patches (with sensible descriptions) - One bumping the rpi-firmware version and one updating the rpi2 config to also support rpi3.
The rpi3 afaik uses a different serial port than rpi2. How will that work if we use the same defconfig for both boards? Perhaps it makes more sense to have a seperate raspberrypi3_defconfig?

Yes, expecially since the CPU is not the same, andthat we may^Wwill one day have it run in 64-bit mode (one can dream, no?).

So yes, make it a separate defconfig, please.

Regards,
Yann E. MORIN.

Quoted 60 lines

Quoted 52 lines

board/raspberrypi/genimage-raspberrypi2.cfg +1 -0

index 443c821..453fb00 100644
@@ -2,6 +2,7 @@ image boot.vfat {
   vfat {
     files = {
       "bcm2709-rpi-2-b.dtb",
+      "bcm2710-rpi-3-b.dtb",
       "rpi-firmware/bootcode.bin",
       "rpi-firmware/cmdline.txt",
       "rpi-firmware/config.txt",

configs/raspberrypi2_defconfig +2 -2

index ce41ee3..b77db14 100644
@@ -13,13 +13,13 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="d33d0293e245badc4ca6ede3984d8bb8ea63cb1a"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="20fe468af4bb40fec0f81753da4b20a8bfc259c9"
 BR2_LINUX_KERNEL_DEFCONFIG="bcm2709"
 BR2_LINUX_KERNEL_ZIMAGE=y
 
 # Build the DTB from the kernel sources
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2709-rpi-2-b bcm2710-rpi-3-b"
 
 BR2_PACKAGE_RPI_FIRMWARE=y
 # BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS is not set

package/rpi-firmware/rpi-firmware.mk +1 -1

index 291da3a..8476678 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-RPI_FIRMWARE_VERSION = 8b4e5482b52e6fb438dddc0d88ba0ba8d44af54b
+RPI_FIRMWARE_VERSION = 951799bbcd795ddf27769d14acf4813fdcbe53dc
 RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
 RPI_FIRMWARE_LICENSE = BSD-3c
 RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom

Signature · 6 lines

1.9.1

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 5 lines

Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 6 lines

.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

Peter Korsgaard

2016-04-20 07:08 UTC #3 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Quoted 8 lines

Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Yann" == Yann E MORIN <[email protected]> writes:
The rpi3 afaik uses a different serial port than rpi2. How will that work if we use the same defconfig for both boards? Perhaps it makes more sense to have a seperate raspberrypi3_defconfig?
Yes, expecially since the CPU is not the same, andthat we may^Wwill one day have it run in 64-bit mode (one can dream, no?).

Yeah. I don't know about the rpi foundation, but there seems to be quite some aarch64 activity around it in mainline U-Boot/Linux.

With the recent vc4 work it might make sense to add rpi defconfigs using mainline as well?

Signature · 2 lines

Venlig hilsen,
Peter Korsgaard

Ubaldo Porcheddu

author

2016-04-20 08:37 UTC #4 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Hi,

Il 2016-04-20 08:08 Peter Korsgaard ha scritto:

Quoted 12 lines

Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Yann" == Yann E MORIN <[email protected]> writes:
The rpi3 afaik uses a different serial port than rpi2. How will
that
Quoted 1 line
Quoted 1 line
work if we use the same defconfig for both boards? Perhaps it makes
more
Quoted 3 lines
Quoted 1 line
sense to have a seperate raspberrypi3_defconfig?
Yes, expecially since the CPU is not the same, andthat we may^Wwill
one
Quoted 1 line
day have it run in 64-bit mode (one can dream, no?).

Quoted 7 lines

Yeah. I don't know about the rpi foundation, but there seems to be quite
some aarch64 activity around it in mainline U-Boot/Linux.
With the recent vc4 work it might make sense to add rpi defconfigs using
mainline as well?

I am going to submit a patch right now with just the firmware upgrade and I will then try a separate rpi3 defconfig to start with.

Gustavo Zacarias

2016-04-20 14:25 UTC #5 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

In reply to Peter Korsgaard

Quoted 5 lines · Peter Korsgaard

Yeah. I don't know about the rpi foundation, but there seems to be quite some aarch64 activity around it in mainline U-Boot/Linux.
With the recent vc4 work it might make sense to add rpi defconfigs using mainline as well?

I have a WIP rpi2 open defconfig, however the kernel part eludes me a bit, plain vanilla doesn't seem ready for vc4 right away and i'm probably missing some patches/pull to complete enable it (symptom: oops). I can share in private if anybody is interested in picking up/trying to fix. Regards.

Peter Korsgaard

2016-04-23 08:36 UTC #6 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

Quoted 6 lines

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Gustavo" == Gustavo Zacarias <[email protected]> writes:
Quoted 3 lines · Peter Korsgaard
Yeah. I don't know about the rpi foundation, but there seems to be quite some aarch64 activity around it in mainline U-Boot/Linux.

Quoted 8 lines

Quoted 2 lines
With the recent vc4 work it might make sense to add rpi defconfigs using mainline as well?
I have a WIP rpi2 open defconfig, however the kernel part eludes me a bit, plain vanilla doesn't seem ready for vc4 right away and i'm probably missing some patches/pull to complete enable it (symptom:
oops).
I can share in private if anybody is interested in picking up/trying to fix.

Ok, thanks. I don't actually have rpi2, so I'll leave it until we have something working.

Signature · 2 lines

Venlig hilsen,
Peter Korsgaard

Yann E. MORIN

2016-04-23 16:53 UTC #7 lore raw

PATCH 1/1 Raspberry PI 3 kernel, firmware and dtb update

In reply to Peter Korsgaard

Ubaldo, All,

On 2016-04-20 09:08 +0200, Peter Korsgaard spake thusly:

Quoted 3 lines

The rpi3 afaik uses a different serial port than rpi2. How will that work if we use the same defconfig for both boards? Perhaps it makes more sense to have a seperate raspberrypi3_defconfig?

BTW, the serial port that is available on the 40-pin header on RPi3 is ttyS0 (I forgot to mention that previously; not sure it was figured out yet, so better re-hash it just in case).

Regards,
Yann E. MORIN.

Signature · 6 lines

.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'