This workaround is no longer needed with recent firmware.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 2a9c3bb5510e4ae46f53bc38b2e9e6c260a4ebc8)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The rpi_arm64 configuration supports both Raspberry Pi 3 & 4 in 64-bit
mode. Switching to this config is a small step towards supporting a
unified build for these targets.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit a4a8ce9af45b8d5aec184cf7bcc57ac856552090)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
reorder list to be in alphabetical order
Change-type: patch
Signed-off-by: Aaron Shaw <aaron@balena.io>
(cherry picked from commit 1c6673262729f60035b6d34b1fa11fc5cbf64710)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Before this patch, use of RPI_EXTRA_CONFIG += in a local.conf would overwrite
the needed 'arm_64bit=1' defined in the core recipes. The net result would be
a system that did not boot.
This patch fixes the assignment of 'arm_64bit=1' even if RPI_EXTRA_CONFIG
has been set elsewhere.
Signed-off-by: matthew@thespencers.me.uk
(cherry picked from commit 881e603ca240576f63ecaf9ca0f6370e8c3dd549)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* instead of repeating //config.txt
so many times, to make it a bit less error prone (as shown in previous commit)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
(cherry picked from commit 17eb1a2f00b6d15c073e318181ab0d34b1b5c965)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* in https://github.com/agherzan/meta-raspberrypi/pull/678 this line was acidentally changed
from "${BOOTFILES_DIR_NAME}" to "bcm2835-bootfiles", causing do_deploy to fail finding config.txt
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
(cherry picked from commit 5c9309de874a42291d19f8e03169ea00eab4a655)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
It seems like "start_x=1" needs to be earlier in the file to work properly on the Rapberry Pi 4 B.
Fixes: #670
Signed-off-by: SCVready <alejandro.solozabal@outlook.com>
(cherry picked from commit 74deec51ded5b22b31b69b30537a6e9ed0997aea)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
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>
(cherry picked from commit e0b4b8c5df410040e8cef7fbe257f1b9c1513355)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The functionality provided by this compile append is already present in
kernel-devicetree.bbclass since oe-core commit:
https://github.com/openembedded/openembedded-core/commit/74619de02774
The md5sums of the generated dtbs for raspberrypi3-64 and raspberrypi4-64 do
not change with this patch applied.
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
(cherry picked from commit a7cc636d4ef0ed7ddabf5785463dbb5c79633b1e)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
CONFIG_UBIFS_FS is used as 'm' in defconfig and depends on MTD and MTD_UBI which
is also 'm', inorder for it to include in kernel proper, set MTD_UBI=y
and MTD=y as well.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 3e2a8534a6f00d66860a9fab4c59b3117ebda43a)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
balena.io has been sponsoring the project with a build server for a
while now. It's only fair for us to mention this somewhere in our
README.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
(cherry picked from commit 3fe1f79ea2592213163f0f62a7c8fb1cb071850b)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Currently its only disabled when vc4graphics is in use but this recipe
actually needs userland and therefore can not be used for non-rpi
machines as well.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 361f42e346e59f3a3fafcfa4ab7c948969d5abf4)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Add a recipe to build a set of dispmanx examples.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
(cherry picked from commit e4f5c32925fec90ff688e51197cb052fe12af82e)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The new Raspberry Pi 400 (and perhaps the CM4 as well) use the BCM43456 chip from Broadcom/Synaptics. This adds the necessary firmware.
Signed-off-by: Aaron Shaw <aaron@balena.io>
(cherry picked from commit f82376c44432c55772941e46224f43edd1cbf2fc)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The link the brcmfmac is looking for was not created by the recipe for the raspberrypi zero w,
so the wifi was not working for this board. Adding link creation in the recipe solved the issue.
Signed-off-by: Tobias Off <sebastianoff@web.de>
(cherry picked from commit 8e35fbffb086728699667b3572ddf30d90ffdb5f)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
After mesa switched build system to meson, the logic to generate dri
related artifacts changed too, which means when no dri backend is
enabled then dri drivers and corresponding headers dont get generated
and hence we end up with missing pkgconfig files e.g. dri.pc which
usually will come from full mesa3d package, but in rpi when userland is
used we only build GL pieces of mesa.
This patch therefore enables swrast dri backend when using userland,
which gives us the needed header and .pc files to build packages like
Xorg server, since EGL driver will come from userland, the dri backend
would be unused and hence should not be effective at runtime.
Addresses issue report with https://github.com/agherzan/meta-raspberrypi/pull/773
there is no need to check for graphics stack since mesa-gl is only used
with userland graphics
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Trevor Woerner <twoerner@gmail.com>
(cherry picked from commit 6c1c9ff4ee743cd90c4107e05be136dd4cb2dee6)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The userland sources include a bunch of sample applications. Add an "allapps"
PACKAGECONFIG to allow the user to build the additional optional applications.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
(cherry picked from commit 3a1fec22c0e0cf389e8ff70ebb310f1f3c282a29)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Linux 5.10 series will be the next LTS kernel so it's likely to be the
new stable branch for linux-raspberrypi within a couple of months. Let's
get set up to test it now.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 7a6759e2424cecf57dbc7d891e89a70639faf3a8)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
There is no need for a separate inc file for the v5.4 kernel recipe.
Variable assignments are simplified where possible after merging.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 8c5809ebbb9020ac5867d25a05120a87b9da5e2c)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
This config fragment was unconditionally disabled for the v5.4 kernel
so it can be dropped.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 64f6a1b7cc6526a49b180ebc632520bbaad195bd)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The name `bootfiles` is too generic, we should use `rpi-bootfiles`
instead.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit ba3a417fbbccb5f6af9ac036eac97c87dcf4c1b7)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
This variable is set in rpi-base.inc and referenced by other recipes
which need to know the location of the bootfiles. If this is overridden
for any reason we need to ensure that the bootfiles recipe deploys to
the correct path.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit b8440b3d26fc0b59acd48ed6f3e39e00cd867f6c)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Instead of generating cmdline.txt in the kernel recipe, it is generated
in a standalone recipe and pulled in as a dependency of the bootfiles
recipe. This simplifies the process of using a linux-yocto,
linux-mainline or similiar kernel recipe instead of linux-raspberrypi.
In the rpi-cmdline recipe the command line is built from fragments which
can all be easily overridden. The variables `SERIAL` and `CMA` are
renamed to `CMDLINE_SERIAL` and `CMDLINE_CMA` for consistency. The
cmdline.txt file is created in the do_compile step to allow further
customisation via do_compile_append if needed.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 8827040d9c218f68ae3ee6a5814929888ed61581)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The bootfiles:do_deploy task already depends on rpi-config:do_deploy so
we do not explicitly need to list the dependency again in the
sdcard_image-rpi class.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit ba6a809a55514a10717bf7b371a63dae440f2cd9)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
This allows us to drop all of the custom config patching in
linux-raspberrypi.inc. It also allows the kernel config to be checked
during the build for any discrepancies between the selected config
options and the resulting .config file - this identified that
`CONFIG_DRM_VC4` depends on `CONFIG_SND` and `CONFIG_SND_SOC`.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
(cherry picked from commit 1c8ad80861f4882eb31c00e27dcc97b3cb786913)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Let's inherit kernel-arch and use ${UBOOT_ARCH} to replace the
hard-coded 'arm'.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
(cherry picked from commit 26a888d669b2d73c251c9107bd7e9871751a1ab6)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
it uses assembly files .S which needs to be processed with gcc alone
until they are made portable use gcc
Fixes
| armstub7.S:175:2: error: instruction requires: thumb
| cbz r6, 9f @ Skip this section if we are core 0
| ^
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 5db97b41a84296d4bbc8fd7ffc228124af774cf1)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Only active when meta-python is in layermix, this recipe rdeps on
python3-pillow, which comes from meta-python, until that moves to
oe-core lets hide this recipe unless meta-python is used
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 08d27cd7997867de69548d04f29d1d2d493791f3)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
while meta-python does rprovide python3-imaging via python3-pillow, its
better to not rely on that bridge, since this might disappear in future
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 07fc972c60b50ebafe7b31f2c47d3d4a81d78933)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
append operator and += when used together results in undefined behaviour
in bitbake
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 2e0b2d41cf5b2186bc534a9d9f55a62c952ea236)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
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>
(cherry picked from commit b70c7b9021e37ec765f4db9aac0e0e76f617cbac)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
This warning is gcc specific and causes build failures when building
with clang, lets therefore remove it when build is using clang compiler
Signed-off-by: Khem Raj <raj.khem@gmail.com>
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>
This patch is now backported into 5.4 stable
commit bc79abf4afea97d5ce682aa2bd1095fb74400916
so it should have been
deleted, otherwise its causing build/patch failures now as expected
Signed-off-by: Khem Raj <raj.khem@gmail.com>
