aboutsummaryrefslogtreecommitdiffstats
path: root/conf/machine
AgeCommit message (Collapse)Author
2020-11-04rpi-default-settings: Replace default parselogs with parselogs_rpiKhem Raj
rpi kernel spits out additional errors in kernel logs which should be ignored, there is no easy way to extend parselogs testcase other than inheriting it into another testcase and use that testcase instead Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-08-26rpi-default-versions: Switch defaults to 5.4Pierre-Jean Texier
Linux Kernel 5.4 is now considered stable. See [1] to check the current apt stable kernel. [1] - https://github.com/raspberrypi/firmware/blob/stable/extra/uname_string7 Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
2020-08-10Generalize the naming of the bootfiles deploy directoryJeff Ithier
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>
2020-08-10conf/machine/include/rpi-base.inc: Added can1 interface to bspcolin
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>
2020-08-10Revert "Generalize the naming of the bootfiles deploy directory"Andrei Gherzan
This reverts commit a907c3261ef583f898803706cd596d372c6644cb.
2020-07-27Generalize the naming of the bootfiles deploy directoryJeff Ithier
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>
2020-07-23rpi-base: add SERIAL_CONSOLES_CHECK to default to SERIAL_CONSOLESChristopher Clark
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>
2020-07-14rpi-base.inc: Include modules if IR is enabledLeon Anavi
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>
2020-06-14rpi-base.inc: Add infrared dtboLeon Anavi
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>
2020-04-30rpi-base.inc: Include modules if I2C is enaledLeon Anavi
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>
2020-04-20rpi-base.inc: Add kernel modules to all imagesLeon Anavi
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>
2020-04-20raspberrypi3: Switch to vc4-fkms-v3d.Drew Moseley
This seems to be required to have a functional DSI display. Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
2020-04-08rpi-base: Drop old dtbo namesKhem Raj
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>
2020-04-08rpi-u-boot-scr: Set u-boot-default-script as providerFabio Berton
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>
2020-03-31rpi-base.conf: add disable-bt.dtbo and miniuart-bt.dtbo overlays.Orne Brocaar
Closes #602. Signed-off-by: Orne Brocaar <info@brocaar.com>
2020-01-24rpi-base.inc: use wic.bz2 for all rpi machines by defaultPierre-Jean Texier
This change moves the default image for all rpi machines. We moved from rpi-sdimg to wic.bz2. Also enable wic.bmap image generation. From the documentation in [1], Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large files, like raw system image files, can be copied or flashed a lot faster and more reliably with bmaptool than with traditional tools, like "dd" or "cp". Example: $: sudo bmaptool copy <image-name>.wic.xz /dev/<your-block-device> [1] - https://github.com/intel/bmap-tools Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
2020-01-24gstreamer1.0-omx: let virtual/libomxil dependency to pull userlandMartin Jansa
* and adjust VIRTUAL-RUNTIME_libomxil to pull runtime provider for libomxil Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2020-01-14Add support for PiTFT 2.8" with capacitive touchErik Botö
Add support for the Adafruit PiTFT Plus 320x240 2.8" TFT with Capacitive Touchscreen, using the same patterns used for the other versions of the PiTFT screens. Signed-off-by: Erik Botö <erik.boto@gmail.com>
2020-01-08raspberrypi-cm3.conf: drop KBUILD_DEFCONFIG definitionRicardo Salveti
KBUILD_DEFCONFIG should be defined by the kernel recipe instead, such as linux-raspberrypi. Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
2020-01-07conf/machine: add pci to MACHINE_FEATURES for Pi4Allen Wild
This pulls in the pciutils package (including `lspci`) via packagegroup-base. Signed-off-by: Allen Wild <allenwild93@gmail.com>
2019-09-16rpi-base.inc: Introduce DISABLE_VC4GRAPHICSAndrei Gherzan
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>
2019-09-16raspberrypi*.conf: Remove vc4 configuration as we already default to itAndrei Gherzan
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>
2019-08-15raspberrypi4-64: Remove the 3G RAM limitationAndrei Gherzan
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>
2019-07-25raspberrypi4-64.conf: Limit RAM to 3GAndrei Gherzan
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>
2019-07-19raspberrypi*: Define ARMSTUB for all machinesAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-18rpi-base.inc: Enabling open-source vc4graphics driver for all RPI platformsRiyaz
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>
2019-07-18raspberrypi4-64.conf: Remove memory limitationAndrei Gherzan
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>
2019-07-16raspberrypi4.conf: The firmware uses kernel7l.img when LPAE is supportedAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-16raspberrypi4-64.conf: Uboot configuration and drop armstubAndrei Gherzan
We drop armstub configuration because the new firmware includes them. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-16raspberrypi4.conf: Define uboot defconfigAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04raspberrypi4-64.conf: Define a machine feature for armstubsAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04raspberrypi4-64.conf: Initial machine configurationAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-07-04raspberrypi4-64.conf: Introduce RPi arm64 machineAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30raspberrypi4: Use vc4-fkms-v3dAndrei Gherzan
Currently, we use vc4-kms-v3d as the default overlay for VC4 but this seems to break vc4 at runtime on RPi4. Change this to vc4-fkms-v3d for now as this is the default Raspbian ons as well. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30rpi-base.inc: Include the "fake" KMS dtboAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30raspberrypi4.conf: Add initial machine 32 bit configurationAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30rpi-base: Rename the rpi0w dtbAndrei Gherzan
This change is following the rename in the kernel: commit 6f91b5dbfdb62a434571a73f2dc15181963e3bea Author: Phil Elwell <phil@raspberrypi.org> Date: Tue May 28 16:36:04 2019 +0100 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30raspberrypi3.conf: Clarify machine modeAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-06-30rpi-base.inc: Include rpi4 dtbAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-05-29rpi-default-versions: Switch defaults to 4.19Khem Raj
4.19 is now declared stable, see https://github.com/raspberrypi/linux/issues/2931#issuecomment-494016355 Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-04-24linux-raspberrypi: Switch default back to 4.14.yPaul Barker
The 4.19.y kernel is not yet considered stable upstream as discussed in the following GitHub issues: https://github.com/agherzan/meta-raspberrypi/issues/410 https://github.com/raspberrypi/linux/issues/2931 Signed-off-by: Paul Barker <paul@betafive.co.uk>
2019-02-24machines: Switch default kernel to 4.19Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-02-24dtbo: Remove lirc-rpi overlayKhem Raj
kernel 4.19 does not have this overlay Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-02-19raspberrypi-cm3.conf: Define it as a stand alone machineAndrei Gherzan
As well, define the correct configuration for this machine. Tested this with and without u-boot on CM3 (with internal storage) and CM3+ without internal storage. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
2019-02-07raspberrypi3-64.conf: Use more appropriate tuneKhem Raj
rpi3 is based on cortex-a53 implementation which is armv8+crc+simd now that OE-Core has the appropriate tunes, switch to using the new tune file, bonus, is that chromium will be more optimized now Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-12-18rpi-default-providers.inc: use virtual/libgbm instead of libgbmMing Liu
This is to be consistent with the latest OE. Signed-off-by: Ming Liu <liu.ming50@gmail.com>
2018-12-12Add Pican2 supportFabien Lahoudere
In order to make Pican 2 work, we : - add mcp2515.dto to the overlay list - add a variable to enable it in local.conf - create a udev rule to mount interface http://skpang.co.uk/catalog/pican2-canbus-board-for-raspberry-pi-23-p-1475.html Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
2018-11-23linux-firmware: replace machine override with new recipesPeter A. Bigot
Raspberry Pi hardware requires firmware that supersedes or is not present in the standard linux-firmware distribution. These files are maintained in the RPi-Distro project on github. Several attempts have been made to reconcile conflicts between what's in linux-firmware and what the hardware needs. The existing approach is functional but not maintainable since it combines material from three repositories into a single package that claims to be linux-firmware. Remove the appends that change the content of linux-firmware for rpi hardware. Add two new recipes that follow the RPi-Distro repositories: * firmware-nonfree which forked from linux-firmware and replaces content is provided as linux-firmware-rpidistro; * bluez-firmware which forked from (very old) bluez and adds content is provided as bluez-firmware-rpidistro. The packages are named to make clear that these come from RPi-Distro, rather than generic sources. Licensing attempts to record the state of licensing as documented in RPi-Distro. Resolves: #298 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2018-11-07machines: Drop VC4_CMA_SIZEKhem Raj
setting cma is not required with latest vc4 driver Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-10-31rpi-base.inc: Add gpio-key to the device tree overlaysOtavio Salvador
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>