linux/meta-raspberrypi.git/recipes-bsp, branch warrior

linux-raspberrypi=4.19.80 bcm2835-bootfiles=20191021

2020-03-19T14:16:46+00:00

* Upgrade the kernel to latest with corresponding firmware. * This VC4 firmware is compatible with network boot described here: https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/raspberry_pi4_network_boot_beta.md Signed-off-by: Martin Jansa (cherry picked from commit 609df9391701e4c82b2807fe8ffe3bca55b9787e)

u-boot-fw-utils: apply the same rpi4 patches as for u-boot recipe

2019-09-09T14:52:40+00:00

* otherwise u-boot-fw-utils build for rpi4 fails with: scripts/kconfig/conf --defconfig=arch/../configs/rpi_4_defconfig Kconfig *** *** Can't find default configuration "arch/../configs/rpi_4_defconfig"! *** scripts/kconfig/Makefile:128: recipe for target 'rpi_4_defconfig' failed * cannot include/require u-boot_2019.07.bbappend directly in u-boot-fw-utils_2019.07.bbappend, because then it fails with: "u-boot_2019.01.bbappend: not a BitBake file" Signed-off-by: Martin Jansa

raspberrypi-firmware: upgrade to latest to fix vc4-fkms

2019-09-09T14:52:40+00:00

* with 4.19.66 kernel the vc4-fkms no longer works, because it doesn't get any usable modes from firmware * this behavior was introduced probably in one of following changes: https://github.com/raspberrypi/firmware/commit/38e81f25e639d19fc0ce6e67fd39998c340a15d5 https://github.com/raspberrypi/linux/pull/3082 https://github.com/raspberrypi/linux/pull/3110 https://github.com/raspberrypi/firmware/commit/66bafab005569e3eb92ec54cd3efeee3da338738 * without this fix: root@rpijama:~# cat /proc/device-tree/soc/firmwarekms@7e600000/status okay root@rpijama:~# modeprint vc4 Starting test Resources count_connectors : 1 count_encoders : 1 count_crtcs : 1 count_fbs : 0 Connector: HDMI-A-1 id : 51 encoder id : 0 conn : connected size : 0x0 (mm) count_modes : 0 count_props : 9 props : 1 2 5 6 52 53 54 55 56 count_encoders : 1 encoders : 50 Encoder: TMDS id :50 crtc_id :0 type :2 possible_crtcs :0x1 possible_clones :0x0 Crtc id : 49 x : 0 y : 0 width : 0 height : 0 mode : 0xfec884 gamma size : 0 Ok * with this fix: martin@jama ~ $ sshc root@rpijama Warning: Permanently added 'rpijama,192.168.169.37' (ECDSA) to the list of known hosts. root@rpijama:~# modeprint vc4 Starting test Resources count_connectors : 1 count_encoders : 1 count_crtcs : 1 count_fbs : 0 Connector: HDMI-A-1 id : 51 encoder id : 50 conn : connected size : 1600x900 (mm) count_modes : 22 count_props : 9 props : 1 2 5 6 52 53 54 55 56 count_encoders : 1 encoders : 50 Mode: "1920x1080" 1920x1080 60 Mode: "1920x1080" 1920x1080 60 Mode: "1920x1080" 1920x1080 50 Mode: "1920x1080" 1920x1080 30 Mode: "1920x1080" 1920x1080 30 Mode: "1920x1080" 1920x1080 25 Mode: "1920x1080" 1920x1080 24 Mode: "1920x1080" 1920x1080 24 Mode: "1280x1024" 1280x1024 60 Mode: "1360x768" 1360x768 60 Mode: "1152x864" 1152x864 60 Mode: "1280x720" 1280x720 60 Mode: "1280x720" 1280x720 60 Mode: "1280x720" 1280x720 50 Mode: "1024x768" 1024x768 60 Mode: "800x600" 800x600 60 Mode: "720x576" 720x576 50 Mode: "720x480" 720x480 60 Mode: "720x480" 720x480 60 Mode: "640x480" 640x480 60 Mode: "640x480" 640x480 60 Mode: "720x400" 720x400 70 Encoder: TMDS id :50 crtc_id :49 type :2 possible_crtcs :0x1 possible_clones :0x0 Crtc id : 49 x : 0 y : 0 width : 1920 height : 1080 mode : 0x1fcde54 gamma size : 0 Ok * tested on raspberrypi3 B weston works fine qtbase-examples tested with: /usr/share/examples/opengl/cube/cube -platform eglfs * the same issue is now in warrior, after someone tests on raspberrypi4 it would be good to backport this to warrior as well Signed-off-by: Martin Jansa

raspberrypi-firmware.inc: Update to 20190718

2019-08-16T14:17:26+00:00

Signed-off-by: Andrei Gherzan

u-boot: Backport patch to fix u-boot compilation without USB config

2019-07-30T15:46:42+00:00

Raspberry Pi 4 doesn't have a working USB driver in u-boot. This makes the defconfig not to enable the relevant config case which breaks the build with: error: expected '}' before 'BOOT_TARGET_DEVICES_references_USB_without_CONFIG_CMD_USB' This was fixed in upstream and we backport the relevant commit. Signed-off-by: Andrei Gherzan

u-boot: Fix patches names in SRC_URI

2019-07-26T13:09:18+00:00

This issue was introduced by b76252c98520b79e012495f8022f238f66c20b05 where the backported patches were not reflected in SRC_URI. Signed-off-by: Andrei Gherzan

armstubs: Error out when ARMSTUBS is not defined

2019-07-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

rpi-config: Check for armstub based on machine feature

2019-07-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

u-boot: Replace custom fork by patches (warrior backport)

2019-07-20T20:56:21+00:00

The upstream branch might suffer rebases due to effort of pushing the patches upstream. To avoid issues, let's have here the patches we need for RPi 4 support. These patches are backported on the u-boot version in warrior. Signed-off-by: Andrei Gherzan

rpi-config: Check some config values against "1"

2019-07-20T20:56:21+00:00

When we read the docs, we have the feelings that theses variables are boolean ones. So I was setting, for example in my distro.conf file the variable ' ENABLE_I2C = "1" ' to enable I2C. Then I wanted to disable it by simply setting 'ENABLE_I2C' to "0" but it wasn't working. So I noticed that, for example, ' ENABLE_UART ' was checked with ' = "1" ' condition and some other "boolean" was checked against ' -n ' like for ENABLE_I2C. This commit tries to have an uniform behavior for all variables that are shown in the doc under the format ' VARIABLE = "1" ' to enable them and the reader can think they are kind of 'boolean' values. Signed-off-by: Joël Carron