summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* linux-raspberrypi: Only deploy cmdline.txt for the main kernelwarriorAlex Gonzalez2020-10-121-6/+8
| | | | | | | When multiple kernels are being built, not all of them can deploy the same file. Signed-off-by: Alex Gonzalez <alexg@balena.io>
* linux-raspberrypi: Bump to 4.19 recipe to 4.19.88Andrei Gherzan2020-03-191-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump to 4.19 recipe to 4.19.81Andrei Gherzan2020-03-191-2/+2
| | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> (cherry picked from commit f18092898881d7ec31872639063231224c11c65d)
* linux-raspberrypi=4.19.80 bcm2835-bootfiles=20191021Martin Jansa2020-03-192-6/+6
| | | | | | | | | | * 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 <Martin.Jansa@gmail.com> (cherry picked from commit 609df9391701e4c82b2807fe8ffe3bca55b9787e)
* linux-raspberrypi: Updating the linux revision to resolve video rendering issueKhan30332020-02-201-2/+2
| | | | | Signed-off-by: Khan3033 <Riyaz.l@ltts.com> (cherry picked from commit cee2557dc872ddaf721e6badb981c7772503f8ea)
* Merge pull request #541 from floion/update_wifi_firmwareFlorin Sarbu2019-12-202-52/+4
|\ | | | | linux-firmware-rpidistro_git: Update wifi firmware
| * linux-firmware-rpidistro_git: Update wifi firmwareFlorin Sarbu2019-12-202-52/+4
|/ | | | | | | | | | | | | This updates brcmfmac43455-sdio.bin to version 7.45.189 and brcmfmac43430-sdio.bin to version 7.45.98.83 This updated upstream firmware also includes the changes from 0001-brcmfmac43455-sdio.txt-Follow-raspbian-change-for-bo.patch so we remove this patch along with removing the do_clean_pc function which is not needed anymore since we don't apply any other patches to the upstream source. Signed-off-by: Florin Sarbu <florin@balena.io>
* linux-raspberrypi-rt: Update 4.19 recipe to 4.19.71Vincenzo Pacella2019-10-181-2/+2
| | | | Signed-off-by: Vincenzo Pacella <shaduz@shaduzlabs.com>
* extra-build-config.md: add RPi 0W to UART sectionBernardo A. Rodrigues2019-09-161-1/+1
| | | | | | This makes it clear in the docs that ENABLE_UART can be used both for the RPi 0W or 3. Signed-off-by: Bernardo A. Rodrigues <bernardaraujor@gmail.com>
* raspberrypi-linux: removed protocoll setting from SRC_URITimm Eversmeyer2019-09-161-1/+1
| | | | | | Default protocoll for git will be used. Default setting is in the most case https. Signed-off-by: Timm Eversmeyer saeugetier@gmail.com
* extra-build-config.md: Document DISABLE_VC4GRAPHICSAndrei Gherzan2019-09-161-0/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-base.inc: Introduce DISABLE_VC4GRAPHICSAndrei Gherzan2019-09-161-1/+1
| | | | | | | | | | | | Since we enabled vc4graphics by default[1], there is no easy way to disable it if needed. This patch introduces a variable (DISABLE_VC4GRAPHICS) which when set to '1' will not add 'vc4graphics' to MACHINE_FEATURES forcing the old behaviour. One could use it in 'local.conf' for example. [1] https://github.com/agherzan/meta-raspberrypi/pull/417 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi*.conf: Remove vc4 configuration as we already default to itAndrei Gherzan2019-09-163-3/+0
| | | | | | | | | As of late[1], we defaulted to enabling vc4graphics in MACHINE_FEATURES. Let's cleanup the machine configurations as per this change. [1] https://github.com/agherzan/meta-raspberrypi/pull/417 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot-fw-utils: apply the same rpi4 patches as for u-boot recipeMartin Jansa2019-09-093-13/+17
| | | | | | | | | | | | | | | | * 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 <Martin.Jansa@gmail.com>
* raspberrypi-firmware: upgrade to latest to fix vc4-fkmsMartin Jansa2019-09-091-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 <Martin.Jansa@gmail.com>
* linux-raspberrypi: Update 4.19 recipe to 4.19.71Andrei Gherzan2019-09-091-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: add linux-raspberrypi-rt 4.19Vincenzo Pacella2019-08-193-11/+19
| | | | | | add rt kernel recipe for version 4.19 Signed-off-by: Vincenzo Pacella <shaduz@shaduzlabs.com>
* raspberrypi4-64: Remove the 3G RAM limitationAndrei Gherzan2019-08-161-1/+1
| | | | | | | | | The PCIe bounce buffers were ported[1] in the kernel so we can remove this limitation now. [1] https://github.com/raspberrypi/linux/pull/3144 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Update 4.19 recipe to 4.19.66Andrei Gherzan2019-08-161-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* mesa: Add v3d and kmsro driver as wellAndrei Gherzan2019-08-161-1/+1
| | | | | | | | Videocore 5/6 support was added as a separate driver in mesa: v3d. Enable this so we can have it available for Raspberry Pi 4. Also, this driver depends on kmsro. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware.inc: Update to 20190718Andrei Gherzan2019-08-161-4/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* omxplayer: Bump revisionKirill Goncharov2019-08-163-7/+7
| | | | | | | | Bump revision to fix playback errors on RPi 4 (https://github.com/popcornmix/omxplayer/issues/733) and update patches accordingly. Update the license hash because of the change in FSF mailing address. Signed-off-by: Kirill Goncharov <kdgoncharov@gmail.com>
* packagegroup-rpi-test: Depend on wireless-regdb instead of crdaKhem Raj2019-08-161-1/+1
| | | | | | | | this should bring in crda if needed Fixes issue #456 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* layer.conf: Add meta-networking to dynamic layersKhem Raj2019-08-161-0/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* webkitgtk: Remove -DUSE_GSTREAMER_GL=OFF for vc4graphicsKhem Raj2019-08-161-1/+0
| | | | | | | | | | | | This is no longer needed, on the contrary is fails the build for webkitgtk Fixes webkitgtk-2.24.2/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:1007:33: error: use of undeclared identifier 'TEXTURE_MAPPER_COLOR_CONVERT_FLAG' | m_textureMapperFlags |= TEXTURE_MAPPER_COLOR_CONVERT_FLAG; | ^ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* userland: Upgrade to latestKhem Raj2019-08-1620-67/+98
| | | | | | | Fix build with glibc 2.30 Forward patches to 20190724 release Signed-off-by: Khem Raj <raj.khem@gmail.com>
* README.md: Use matrix chat roomAndrei Gherzan2019-08-161-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* sdcard_image-rpi.bbclass: use -v for all mcopy calls and add bbfatal in case ↵Martin Jansa2019-08-141-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mcopy fails * I have this in our layer for some time: RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/vc4-fkms-v3d.dtbo" because we're using vc4graphics also on raspberrypi3 and it was working fine until recently. * now the default rpi-base.inc in warrior and master branch includes the same since: https://github.com/agherzan/meta-raspberrypi/commit/37aa050d5a44eb797540ef50408c2ca8e3da6fa0 and do_image_rpi_sdimg started failing with a bit useless log: ... Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 46.1MB 41.9MB primary boot, lba 2 46.1MB 1145MB 1099MB primary mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command. * after adding -v to mcopy calls I got slightly better log: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo WARNING: exit code 1 from a shell command. * the issue is that mcopy behavior in non-interactive shell is to fail when the target file already exists (sometimes it seems to cause mcopy to hang forever), but when you execute the run.do_image_rpi_sdimg script manually in interactive shell it will nicely show this prompt on stderr: $ dtb=vc4-fkms-v3d.dtbo recipe-sysroot-native/usr/bin/mcopy -i boot.img -s BUILD/deploy/images/raspberrypi3/$dtb ::overlays/$dtb Long file name "vc4-fkms-v3d.dtbo" already exists. a)utorename A)utorename-all r)ename R)ename-all o)verwrite O)verwrite-all s)kip S)kip-all q)uit (aArRoOsSq): o * with the bbfatal the log is finally a bit more useful: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo ERROR: mcopy cannot copy TOPDIR/BUILD/deploy/images/raspberrypi3/vc4-fkms-v3d.dtbo into boot.img WARNING: exit code 1 from a shell command. * the only exception is FATPAYLOAD where it was ignoring mcopy with || true before, I've added bbwarn, because even issues like mentioned there "vfat issues like not supporting .~lock files" are probably worth reporting as warning (why would people add .~lock to FATPAYLOAD if it cannot be copied into boot.img) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* drbd: Disable for rpi machinesKhem Raj2019-08-141-0/+3
| | | | | | | | | | | | | | Its enabled in linux-raspberrypi modules in defconfig so we can ignore external driver for now, fixes ERROR: linux-raspberrypi-1_4.19.58+gitAUTOINC+d5dc848c98-r0 do_packagedata_setscene: The recipe linux-raspberrypi is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /mnt/a/yoe/build/tmp/pkgdata/raspberrypi3-64/runtime/kernel-module-drbd-4.19.58.packaged (matched in manifest-raspberrypi3_64-drbd.packagedata) /mnt/a/yoe/build/tmp/pkgdata/raspberrypi3-64/runtime/kernel-module-drbd-4.19.58 (matched in manifest-raspberrypi3_64-drbd.packagedata) Please verify which recipe should provide the above files. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot: Backport patch to fix u-boot compilation without USB configAndrei Gherzan2019-07-302-0/+74
| | | | | | | | | | | | | 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 <andrei@balena.io>
* raspberrypi4-64.conf: Limit RAM to 3GAndrei Gherzan2019-07-261-1/+1
| | | | | | | | | | | | | | | The PCI controller on the Raspberry Pi 4 acts as a DMA controller and can only address the first 3Gb[1] of the memory space. On 32bit this was addressed by implementing bouncing buffers[2] but this currently has no support for arm64. In order to have working USB, as a workaround, we limit the ram to 3G. Fixes #446 [1] https://github.com/raspberrypi/linux/issues/3093 [2] https://github.com/raspberrypi/linux/blob/rpi-4.19.y/drivers/pci/controller/pcie-brcmstb-bounce.c Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot: Fix patches names in SRC_URIAndrei Gherzan2019-07-261-6/+4
| | | | | | | This issue was introduced by b76252c98520b79e012495f8022f238f66c20b05 where the backported patches were not reflected in SRC_URI. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi*: Define ARMSTUB for all machinesAndrei Gherzan2019-07-209-0/+17
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* armstubs: Error out when ARMSTUBS is not definedAndrei Gherzan2019-07-201-0/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* sdcard_image-rpi: Check for armstub based on machine featureAndrei Gherzan2019-07-201-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-config: Check for armstub based on machine featureAndrei Gherzan2019-07-201-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-base.inc: Enabling open-source vc4graphics driver for all RPI platformsRiyaz2019-07-201-1/+1
| | | | | | | | Vc4graphics enables drm backend on wayland Compositor (weston & westeros) Appending vc4graphics machine feature to use mesa drivers for OpenGL and V4l2 for video. Signed-off-by: Riyaz <Riyaz.l@ltts.com>
* u-boot: Replace custom fork by patches (warrior backport)Andrei Gherzan2019-07-209-4/+509
| | | | | | | | | | 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 <andrei@gherzan.ro>
* rpi-config: Check some config values against "1"Carton2019-07-201-5/+5
| | | | | | | | | | | | | | | | 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 <joel.carron@eeproperty.ch>
* bluez5: Fixed typo (RC_URI -> SRC_URI)Carton2019-07-201-1/+1
| | | | Signed-off-by: Joël Carron <joel.carron@eeproperty.ch>
* raspberrypi4-64.conf: Remove memory limitationAndrei Gherzan2019-07-201-1/+1
| | | | | | | | We can do this because the kernel now includes a workaround for the DMA issue. https://github.com/raspberrypi/linux/pull/3080 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19 revisionAndrei Gherzan2019-07-201-1/+1
| | | | | | | This version includes a workaround for the usable DMA memory. It limits the DMA to the first 1G. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Build dtbs with dtbs make target for all 64bit targetsAndrei Gherzan2019-07-201-3/+5
| | | | | | | We already do this for rpi3-64 and we will need it for rpi4-64 as well. See 6c4de0b5fe44b8e661f1391ee8540a7f04d75315 for more details. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19 to 4.19.58Andrei Gherzan2019-07-201-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4.conf: The firmware uses kernel7l.img when LPAE is supportedAndrei Gherzan2019-07-201-1/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware: Update to 20190709Andrei Gherzan2019-07-201-4/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot: Use a temporary fork for RPi4 supportAndrei Gherzan2019-07-201-0/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4-64.conf: Uboot configuration and drop armstubAndrei Gherzan2019-07-201-2/+8
| | | | | | We drop armstub configuration because the new firmware includes them. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4.conf: Define uboot defconfigAndrei Gherzan2019-07-201-0/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19.57 revisionAndrei Gherzan2019-07-201-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>