Having RPI_KERNEL_DEVICETREE_OVERLAYS:append = " overlays/bcm2712d0.dtbo"
in raspberrypi5.conf is not applying when building an 64bit compatible image
with raspberrypi-armv8. Thus moving into the rpi-base.inc
This fix the boot of this image on Raspberry Pi 5 hw rev 1.1
Signed-off-by: Thomas Roos <throos@amazon.de>
We need the uart dts overlays to enable a specific uart peripheral.
For example if you use the disable-bt overlay, you have to enable
the uart0 dts overlay to be able to use uart0 peripheral.
Signed-off-by: Pierrick Curt <pierrickcurt@gmail.com>
All bcm2712 are built for arm64 builds alone and rpi-base.inc is included
by 32-bit machine configs as well. Recently, kernel moved thesr dts files
into arch/arm64/boot/dts/broadcom/ folder [1]
[1] 10c77e119e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
There is anoter hifiberry hat, for which there is currently
no overlay added to the build, so let's add it:
hifiberry-dacplusadcpro.dtbo
Signed-off-by: Pascal Huerst <pascal.huerst@gmail.com>
Add overlays/vc4-kms-v3d-pi5.dtbo to use vc4-kms-v3d driver on
Raspberry Pi 5.
This work was sponsored by GOVCERT.LU.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
This fix is needed to bring the complete dependency chain in order to guarantee
the recursive runtime dependencies [1] of do_populate_lic_deploy in do_populate_lic
will run as expected.
[1] openembedded-core/meta/classes-recipe/license_image.bbclass:do_populate_lic_deploy[recrdeptask] += "do_populate_lic do_deploy"
Fix the following image build issues:
| ERROR: lmp-base-console-image-1.0-r0 do_populate_lic_deploy: Couldn't find license information for dependency rpi-config
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
wic images depend on the kernel device trees, and therefore should
depend on virtual/kernel:do_deploy to make sure these are present in the
deploy directory.
Most of the time, this dependency is satisfied indirectly since a rootfs
image will depend on the kernel, but add it explicitly for the cases
where it is not.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
It can be useful to disable the WiFi for hardening reasons.
And it probably lower the power consumption a bit.
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
ERROR: Multiple .bb files are due to be built which each provide
libav/libpostproc:
/../../meta-raspberrypi/recipes-multimedia/rpidistro-ffmpeg/rpidistro-ffmpeg_4.3.4.bb
/../../openembedded-core/meta/recipes-multimedia/ffmpeg/ffmpeg_5.1.2.bb
Ensures bitbake understands which recipe to select first.
Signed-off-by: Vincent Davis Jr <vince@underview.tech>
This patch is based on an analog patch from Christopher Boyd <xpboyd@gmail.com> committed at meta-freescale.
(see 954d7a7d7a)
Signed-off-by: Oliver Lang <quantenkeks@gmail.com>
The new raspberrypi-armv7.conf aims at supporting all the ARMv7
Raspberry Pi boards.
This initial support was tested on:
* Raspberry Pi 4 Model B
* Raspberry Pi 3 Model B
* Raspberry Pi 0 2 WiFi
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
The kernel image deployment is now defined in IMAGE_BOOT_FILES as a
separate variable: RPI_EXTRA_IMAGE_BOOT_FILES. This allows a custom
kernel image deployment by redefining this variable when needed.
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
All 32-bit machines are sharing the list of machine dtbs with the
exception of raspberrypi0-2w. Move this away too to unify the
machine configurations.
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Adds ability to select rpidistro version of vlc and ffmpeg over oe-core version.
via the PREFERRED_PROVIDER_vlc & PREFERRED_PROVIDER_ffmpeg
variables.
Signed-off-by: Vincent Davis Jr <vince@underview.tech>
Adds support for software i2c controller on gpio pins
RPI_EXTRA_CONFIG += "\
dtoverlay=i2c-gpio,bus=7,i2c_gpio_sda=6,i2c_gpio_scl=5 \
"
Will configure a /dev/i2c-7 bus with sda=gpio#6 and slc=gpio#5
The overlay documentation can be found here:
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README
Signed-off-by: Bernhard Guillon <Bernhard.Guillon@begu.org>
Since RPi kernel commit 9e87248154a633b18b4900ee742d9894b49e019b FKMS overlay
for Pi4 family is split into a separate file. Not shipping the overlay means
FKMS does not load correctly on these devices and VC4 is not brought up.
Signed-off-by: Michal Toman <michal@toman.sk>
- Feature is enabled with ENABLE_GPIO_SHUTDOWN variable
- Include the gpio-shutdown overlay
- If using SysV init include the additional keymap and inittab entries
to bind the KEY_POWER event
- Systemd init does not require any additional bindings
Signed-off-by: Otto Esko <otto.esko@gmail.com>
Some machines need to have the kernel toggle a gpio when an external
power source needs to shut off power to complete a shutdown and de-energize
the processor. gpio-poweroff provides this functionality but was omitted
from the kernel overlays brought oveer by the rpi-layer from the kernel.
Signed-off-by: Cameron Kellough <cameron@telemetrak.com>
This is the result of automated script conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
overlay_map.dtb arranges that when config.txt requests "vc4-kms-v3d"
the rpi4 will actually load "vc4-kms-v3d-pi4" and fixups like that.
It is present on the official distros, and must be put into the
overlays subdirectory in the boot partition.
For a detailed description of the overlay_map.dts file see:
https://www.raspberrypi.org/documentation/configuration/device-tree.md#part2.2.10
vc4-kms-v3d-pi4 is required for the arm based kms driver on the rpi4.
Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
In theory, this would allow one to use the official 7-inch touchscreen
in combination with the (non-firmware) kms driver by adding the
following lines to config.txt:
ignore_lcd=1
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch
Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
To allow other layers to easily provide a default kernel preference to
use with the Raspberry Pi MACHINEs, switch to use the ??= assignment
operator for setting the default kernel and the device tree value in
this layer.
This change is motivated by enabling Xen support in meta-virtualization
to use the raspberrypi4-64 MACHINE definition from this layer with the
Yocto Linux kernels.
Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com>
Added imx219.dtbo file in the overlays, and added dtoverlay in
/boot/config.txt define based.
To enable Sony Raspberry pi camera imx219 sensor, need to set
the variable RASPBERRYPI_CAMERA_V2 as 1.
In future, we can add any camera overlays here to support and
use them with libcamera.
Signed-off-by: Madhavan Krishnan <madhavan.krishnan@linaro.org>
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>
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>
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>
