| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
and dev recipe
* COPYING was changed only 4 times (last time in 5.6 with:
https://github.com/torvalds/linux/commit/74835c7db0322 )
so hopefully it will last for a while
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
| |
* 5.10.11 is now considered stable:
https://github.com/raspberrypi/firmware/blob/stable/extra/uname_string7
https://github.com/raspberrypi/firmware/commit/8572bb50bf24a9ffef949ced69776e66559f4afe
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Aurelian Zanoschi <aurelian17@gmail.com>
|
|
|
|
|
|
|
|
| |
By default in case of CM4 IO board, the USB ports (header + built-in)
are disabled. In order to enable them the DWC2 mode needs to be set to
host.
Signed-off-by: Aurelian Zanoschi <aurelian17@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, the do_compile log is cluttered with dtc warnings that should only
be printed when compiling with W="123":
...
/soc: node has a reg or ranges property, but no unit name
/soc/gpu: missing or empty reg/ranges property
/soc/firmware/gpio: missing or empty reg/ranges property
...
This happens because we pass dtc flags via KERNEL_EXTRA_ARGS directly on the
make command line, preventing scripts/Makefile.lib logic from appending flags
that silence dtc warnings (all assignments done from within a makefile, to a
variable specified on the command line, are ignored).
oe-core commit [1] introduced the dedicated KERNEL_DTC_FLAGS variable to pass
dtc flags via the environment. Use this variable to get rid of the do_compile
log noise.
The md5sums of the generated dtbs for raspberrypi3-64 and raspberrypi4-64 do
not change with this patch applied.
[1] https://github.com/openembedded/openembedded-core/commit/063b5de86624
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
|
|
|
|
|
|
|
| |
'recipes-kernel/linux/linux-yocto.inc' already inherits 'kernel'.
This commit removes the superfluous one in 'linux-raspberrypi.inc'.
Signed-off-by: Jonas Vautherin <jonas.vautherin@protonmail.ch>
|
|
|
|
|
|
|
| |
Move the layer paths used by kas into a `layers` subdirectory and add
this to the git ignore list.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
| |
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
| |
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
|
|
| |
This workaround is no longer needed with recent firmware.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
add justboom overlays
Change-type: patch
Signed-off-by: Aaron Shaw <shawaj@gmail.com>
|
|
|
|
|
|
|
| |
reorder list to be in alphabetical order
Change-type: patch
Signed-off-by: Aaron Shaw <aaron@balena.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
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Add a recipe to build a set of dispmanx examples.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
|
|
|
|
|
|
| |
Fix the "allapps" PACKAGECONFIG to avoid the QA warning/error:
userland-20201027-r0 do_configure: QA Issue: userland: invalid PACKAGECONFIG: allapps [invalid-packageconfig]
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
| |
on raspberrypi zero w
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
This is not need any more to build with gstreamer 1.18
Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
This config fragment was unconditionally disabled for the v5.4 kernel
so it can be dropped.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
| |
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
|
|
|
| |
The name `bootfiles` is too generic, we should use `rpi-bootfiles`
instead.
Signed-off-by: Paul Barker <pbarker@konsulko.com>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Let's inherit kernel-arch and use ${UBOOT_ARCH} to replace the
hard-coded 'arm'.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
refresh patches
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|