summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* conf/machine/include/rpi-base.inc: Added can1 interface to bspcolin2020-08-101-0/+1
| | | | | | | | | The device tree only supports a single CAN interface. This prevents compatiblity with dual-CAN boards like the PiCAN2 Duo. The mcp2515-can1 device tree blob for overlay was added to RPI_KERNEL_DEVICETREE_OVERLAYS in order to support dual-CAN hats. Signed-off-by: Colin McAllister <colinmca242@gmail.com>
* Revert "Generalize the naming of the bootfiles deploy directory"Andrei Gherzan2020-08-105-82/+78
| | | | This reverts commit a907c3261ef583f898803706cd596d372c6644cb.
* u-boot: Move fw_env.config to u-boot appendFabio Berton2020-08-052-12/+8
| | | | | | | | | | | | | | | The u-boot-env is provided by u-boot recipe and not by libubootenv, so right recipe to append is the u-boot. Adding the rpi-u-boot-scr in DEPENDS variable is wrong because it is forcing rpi-u-boot-scr to be a dependency, but it'll fail if I have another recipe that provides bootscript, once both recipes provide the same file. The default value of u-boot-default-script is rpi-u-boot-scr, so right way is to use u-boot-default-script and change the PREFERRED_PROVIDER_u-boot-default-script if needed. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> (cherry picked from commit fc72c061411ea78515a670b63b0d44c13451cb78)
* u-boot-rpi: Locate local patches with FILESEXTRAPATHS.Drew Moseley2020-08-041-0/+2
| | | | Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
* Generalize the naming of the bootfiles deploy directoryJeff Ithier2020-07-275-78/+82
| | | | | | | | | | The raspberry pi 4 variant has a BCM2711 chip, however it still uses the same boot files as the BCM2835 used in previous generations. This change generalizes the naming of the directory generated in the $DEPLOY_DIR to avoid the implication that the files are only meant for the BCM2835. Signed-off-by: Jeff Ithier <ithijme@gmail.com>
* rpi-base: add SERIAL_CONSOLES_CHECK to default to SERIAL_CONSOLESChristopher Clark2020-07-231-0/+1
| | | | | | | | As per the example in the bsp-guide, and the qemu and other machine configs. Assists when running virtualized, where serial console device can differ. Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com>
* docs/extra-build-config.md: InfraredLeon Anavi2020-07-141-0/+12
| | | | | | | | Add instructions how to use variable ENABLE_IR for infrared support, for example with LIRC. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-base.inc: Include modules if IR is enabledLeon Anavi2020-07-141-0/+1
| | | | | | | | | | | | | | Add kernel modules gpio-ir and gpio-ir-tx to variable MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS if ENABLE_IR is set to 1. Variable ENABLE_IR enables infrared support (for LIRC). This change affects images based on packagegroup-core-boot, including the core-image-minimal image. For other images (based on packagegroup-base) kernel modules are provide through variable MACHINE_EXTRA_RRECOMMENDS. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-config: Add ENABLE_IR variable for infraredLeon Anavi2020-07-141-0/+9
| | | | | | | | | | | | | | | Users who want infrared device tree overlays gpio-ir and gpio-ir-tx to be set in config.txt can now easily do it through variable ENABLE_IR, for example in local.conf: ENABLE_IR = "1" By default the GPIO pin for gpio-ir is set to 18 and the pin for gpio-ir-tx is 17. Both pins can be easily changed by modifying variables GPIO_IR and GPIO_IR_TX (for example in local.conf). Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* packagegroup-rpi-test: resolve `wireless-regdb` conflictJon Magnuson2020-07-141-1/+1
| | | | | | | | | Replaces `wireless-regdb` with `wireless-regdb-static` provided by poky. Fixes #639. Signed-off-by: Jon Magnuson <jon.magnuson@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* userland: Update to 2020-06-24 top commitKhem Raj2020-07-1422-78/+144
| | | | | | Forward port patches Signed-off-by: Khem Raj <raj.khem@gmail.com>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-07-141-4/+4
| | | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi: bump to Linux version 5.4.51Pierre-Jean Texier2020-07-141-2/+2
| | | | | | | | | | Fixes: ERROR: linux-raspberrypi-1_5.4.50+gitAUTOINC+856e83151c-r0 do_fetch: Fetcher failure: Unable to find revision 856e83151cf3f802c495585ac176bb135a08030f in branch rpi-5.4.y even from upstream ERROR: linux-raspberrypi-1_5.4.50+gitAUTOINC+856e83151c-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source. Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi: bump to 5.4.50 since upstream was force-pushedChristopher Clark2020-07-141-2/+2
| | | | | Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libubootenv_%.bbappend: Add fw_env.configLeon Anavi2020-07-142-0/+13
| | | | | | | | | | Add fw_env.config that uses at run-time /boot/uboot.env generated through the boot scripts (specifically boot.cmd.in) from recipe rpi-u-boot-scr. This configuration file is required to successfully run fw_printenv from the user space. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-u-boot-scr: Create uboot.env via boot.cmd.inLeon Anavi2020-07-141-0/+1
| | | | | | | | | Modify boot.cmd.in from recipe rpi-u-boot-scr to create uboot.env in the /boot partition when using U-Boot. This change is required to successfully run fw_printenv from the user space. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot: Fix booting raspberrypi CM3 moduleMarek Belisko2020-06-292-0/+53
| | | | | | | | | With stock u-boot v2020.01 which we use from poky CM3 module won't boot. We need to apply this patch in order to have platform again working. Add it only for cm3 to not break anything else. Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
* lirc_%.bbappend: RemoveLeon Anavi2020-06-252-180/+0
| | | | | | | | | | | Temporary remove the LIRC patch because it is not compatible with version 0.9.4d which is at the moment provided by branch dunfell from meta-openembedded/meta-oe. This patch should be applied again when LIRC version 0.10.1 or newer is available at branch dunfell of meta-openembedded/meta-oe (as of the moment this version is available at master). Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* Update layer-contents.md to include pi4M. ter Woord2020-06-221-0/+2
| | | | Signed-off-by: Matthijs ter Woord <matthijsterwoord@gmail.com>
* linux-raspberrypi_5.4.bb: Upgrade to 5.4.47Khem Raj2020-06-222-12/+12
| | | | | | | | Drop backported patches which are already in this release Fixes Issue #658 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* lirc_%.bbappend: Fix for gpio-irLeon Anavi2020-06-222-0/+180
| | | | | | | | | | | | | | | Apply Raspberry Pi specific fix to use LIRC with gpio-ir kernel module with which the signal from /dev/lircX is slightly different from that of lirc_dev (which was used with older LIRC and kernel versions). The patch has been published by neuralassembly and he has shared more details in the Raspberry Pi community forum: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=235256 LIRC ticket #359 tracks the upstreaming of this issue: https://sourceforge.net/p/lirc/tickets/359/ Co-authored-by: neuralassembly <neuralassembly@gmail.com> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* linux-raspberrypi_5.4.bb: Move to 5.4.45Khem Raj2020-06-141-2/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi: bump to Linux version 4.19.126Pierre-Jean Texier2020-06-141-2/+2
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-06-141-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* rpi-base.inc: Add infrared dtboLeon Anavi2020-06-141-0/+2
| | | | | | | Add device tree binary overlays gpio-ir-tx and gpio-ir-tx to support peripherals for sending and receiving infrared signals. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* docs: Remove reference to xz-compressed sdimgBrandon Verkamp2020-05-231-2/+2
|
* docs: Correct Quick Start instructions to show the new .wic.bz2 extensionBrandon Verkamp2020-05-231-4/+4
| | | | | | | Corrects README.md to indicate that the new generated image extension is .wic.bz2 rather than sdimg as previously stated. Signed-off-by: Brandon Verkamp <jadelclemens@gmail.com>
* linux-raspberrypi: Update to latest on 5.4 releaseKhem Raj2020-05-231-2/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi_5.4.bb: Update to 5.4.35Khem Raj2020-05-231-2/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi: bump to Linux version 4.19.120Pierre-Jean Texier2020-05-231-2/+2
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-05-231-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* rpi-base.inc: Include modules if I2C is enaledLeon Anavi2020-04-301-1/+3
| | | | | | | | | | | | Add kernel modules i2c-dev and i2c-bcm2708 to variable MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS if ENABLE_I2C is set to 1. This affects images based on packagegroup-core-boot, including the core-image-minimal image. For other images (based on packagegroup-base) kernel modules are provide through variable MACHINE_EXTRA_RRECOMMENDS. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* linux-raspberrypi_5.4.bb: Update to latestKhem Raj2020-04-301-1/+1
| | | | | | brings in some pinmux and dtoverlays Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi_5.4.bb: Update to latestBartłomiej Burdukiewicz2020-04-301-2/+2
| | | | Signed-off-by: Bartłomiej Burdukiewicz <bartlomiej.burdukiewicz@gmail.com>
* psplash: Do not define ALTERNATIVE_PRIORITY for non-existing providerKhem Raj2020-04-201-2/+1
| | | | | | | | This simply causes build warnings about priority of two packages being same, but infact this is redundant, therefore remove setting ALTERNATIVE_PRIORITY for psplash-raspberrypi Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-firmware-rpidistro: Upgrade to 20190114-1+rpt6Khem Raj2020-04-201-2/+2
| | | | | | Adjust PV to reflect the release and make it a bit meaningful Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi: bump to Linux version 4.19.115Pierre-Jean Texier2020-04-201-2/+2
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-04-201-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* linux-raspberrypi_5.4.bb: Update to latestKhem Raj2020-04-201-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-base.inc: Add kernel modules to all imagesLeon Anavi2020-04-201-1/+1
| | | | | | | | | | | | | | Add kernel modules, including i2c-dev and i2c-bcm2708, to variable MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS. This way kernel modules will be present in all images based on packagegroup-core-boot, including the core-image-minimal image. Otherwise, if modules, are in variable MACHINE_EXTRA_RRECOMMENDS they will be added only in images based on packagegroup-base, which does not include the core-image-minimal or core-image-full-cmdline images. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* raspberrypi3: Switch to vc4-fkms-v3d.Drew Moseley2020-04-202-0/+2
| | | | | | This seems to be required to have a functional DSI display. Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
* linux-raspberrypi_5.4.bb: Backport the patch to use CHECK macro instead of ↵Khem Raj2020-04-204-18/+142
| | | | | | | | | | | | RET_IF Revert couple of regressions for selftest Fixes | /usr/src/debug/kernel-selftest/1.0-r0/kernel-selftest-1.0/tools/testing/selftests/bpf/test_select_reuseport.c:671: undefined reference to `RET_IF' Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi_5.4.bb: Enable powersave options in kconfigKhem Raj2020-04-092-0/+14
| | | | | | | | Will let system hibernate and suspend, its initial setup, there is more work needed to get it going fully without problems in userspace, which will follow Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi_5.4.bb: Update to latest and fix build with binutils 2.34Khem Raj2020-04-091-1/+4
| | | | | | | | | perf fails to build without bfd patch still, therefore apply it to 5.4 as well. Update to latest on 5.4 branch Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Revert "qtbase: Drop xkb packageconfig"Khem Raj2020-04-081-1/+1
| | | | This reverts commit eaa131425923a06e8be7547842bc2c105363f18e.
* linux-raspberrypi: Add recipes for kernel 5.4Khem Raj2020-04-082-0/+18
| | | | | | | 5.4 is slated to be next hop for linux-raspberrypi, here add the recipes, default is still 4.19, we can switch that later Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-base: Drop old dtbo namesKhem Raj2020-04-081-2/+0
| | | | | | | | pi3-disable-bt is renamed to disable-bt and pi3-miniuart-bt is renamed to miniuart-bt in 2014, now with 5.4 these are not recognised anymore and miniuart-bt and disable-bt are already part of RPI_KERNEL_DEVICETREE_OVERLAYS Signed-off-by: Khem Raj <raj.khem@gmail.com>
* userland: Fix build with gcc10Khem Raj2020-04-082-0/+33
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* qtbase: Drop xkb packageconfigKhem Raj2020-04-081-1/+1
| | | | | | meta-qt5 master has dropped it too Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rpi-u-boot-scr: Set u-boot-default-script as providerFabio Berton2020-04-084-2/+6
| | | | | | | | | Add u-boot-default-script to the PROVIDES variable to make easier to replace boot script in another layer just by changing PREFERRED_PROVIDER_u-boot-default-script variable. Set rpi-u-boot-scr as the default provider for meta-raspberrypi. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>