| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Fixes: "Bleeding Tooth" Bluetooth Vulnerability.
Signed-off-by: Eino Juhani Oltedal <einoju@gmail.com>
|
|
|
|
|
|
|
| |
When multiple kernels are being built, not all of them can deploy the
same file.
Signed-off-by: Alex Gonzalez <alexg@balena.io>
|
|
|
|
|
|
|
|
| |
* see oe-core base.bbclass changes from:
https://lists.openembedded.org/g/openembedded-core/message/143159
https://lists.openembedded.org/g/openembedded-core/message/143161
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
| |
* fixes:
https://github.com/raspberrypi/linux/issues/3885
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
with 5.4 fd580000.genet has been replaced with fd580000.ethernet in the
error text
Fixes
https://github.com/raspberrypi/linux/issues/3884
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
Use date in PV, makes is good candidate for always increasing PV
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Brings in fixes for errors seen in kernel boot log
e.g.
https://github.com/raspberrypi/linux/issues/3878
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
libcamera middleware has supported many pipelines for video frames capturing.
So defined the packageconfig, to enable the rpi pipeline and to capture frames
using the rpi camera sensor.
Signed-off-by: Madhavan Krishnan <madhavan.krishnan@linaro.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Update brcmfmac43455-sdio.bin to 7.45.206
* Add BCM43456 firmware
- brcm/brcmfmac43456-sdio.bin 7.84.17.1
- brcm/brcmfmac43456-sdio.clm_blob
- brcm/brcmfmac43456-sdio.txt
* Add compatibility links for direct firmware download to work properly
Fixes
brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lttng-modules build"
This reverts commit d1257fc1272c9dee76d79a74abc2bdeb7f5a7036.
Now lttng-modules in oe-core were updated in:
https://git.openembedded.org/openembedded-core/commit/?id=62c87d1a68c4f7c8f30c3c5330dcda9cbcbbbaa7
and the backported patch:
https://git.openembedded.org/openembedded-core/diff/meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch?id=62c87d1a68c4f7c8f30c3c5330dcda9cbcbbbaa7
now expects new writeback_queue_io API being available in LTTNG_KERNEL_RANGE(5,4,62, 5,5,0)
so we need to re-enable it.
|
|
|
|
|
|
|
|
| |
This reverts commit 84cb8538cd22586fc82daba38458909cedfec2db.
Fixes:
- https://gitlab.gnome.org/GNOME/mutter/-/issues/1421
- #711
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* otherwise we end with big archives in downloads directory without clear
indication from where they came
* e.g. in one of my jenkins builds I've noticed:
-rw-rw-r-- 1 jenkins jenkins 178M Jun 30 15:45 downloads/23548e550a757d368d3d5220373fe829b5961c42.tar.gz
-rw-rw-r-- 1 jenkins jenkins 152M Sep 5 2019 downloads/7163480fff007dc98978899b556dcf06f8a462c8.tar.gz
-rw-rw-r-- 1 jenkins jenkins 179M Jul 23 01:34 downloads/7e74bcb4f9706f36f752d1c3d3164628ccf2aae5.tar.gz
-rw-rw-r-- 1 jenkins jenkins 178M Jun 5 12:34 downloads/7eff9f6774bb43bfd61e749a0b45ffddc98c2311.tar.gz
-rw-rw-r-- 1 jenkins jenkins 177M Apr 23 14:49 downloads/84523e0b9a9e78aa69fca1f1a8d75b2bdb5155fc.tar.gz
-rw-rw-r-- 1 jenkins jenkins 178M Jan 13 2020 downloads/9d6be5b07e81bdfb9c4b9a560e90fbc7477fdc6e.tar.gz
-rw-rw-r-- 1 jenkins jenkins 463 Jul 1 03:58 downloads/23548e550a757d368d3d5220373fe829b5961c42.tar.gz.done
-rw-rw-r-- 1 jenkins jenkins 141 Jan 16 2020 downloads/7163480fff007dc98978899b556dcf06f8a462c8.tar.gz.done
-rw-rw-r-- 1 jenkins jenkins 463 Aug 1 15:40 downloads/7e74bcb4f9706f36f752d1c3d3164628ccf2aae5.tar.gz.done
-rw-rw-r-- 1 jenkins jenkins 463 Jun 6 09:54 downloads/7eff9f6774bb43bfd61e749a0b45ffddc98c2311.tar.gz.done
-rw-rw-r-- 1 jenkins jenkins 463 May 16 03:35 downloads/84523e0b9a9e78aa69fca1f1a8d75b2bdb5155fc.tar.gz.done
-rw-rw-r-- 2 jenkins jenkins 141 Aug 7 22:10 downloads/9d6be5b07e81bdfb9c4b9a560e90fbc7477fdc6e.tar.gz.done
* unfortunately using git fetcher is still problematic because of git repo size:
15G firmware
1,6G tools
-rw-rw-r-- 1 jenkins jenkins 180M Sep 17 13:59 downloads/raspberrypi-firmware-a490197f0672d948860b2b807884ae65eabc4d4f.tar.gz
-rw-rw-r-- 1 jenkins jenkins 463 Sep 17 14:09 downloads/raspberrypi-firmware-a490197f0672d948860b2b807884ae65eabc4d4f.tar.gz.done
-rw-rw-r-- 1 jenkins jenkins 324M Sep 17 14:10 downloads/raspberrypi-tools-b0c869bc929587a7e1d20a98e2dc828a24ca396a.tar.gz
-rw-rw-r-- 1 jenkins jenkins 463 Sep 17 14:10 downloads/raspberrypi-tools-b0c869bc929587a7e1d20a98e2dc828a24ca396a.tar.gz.done
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
| |
* fixes:
lttng-modules/2.12.2-r0/lttng-modules-2.12.2/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for 'trace_writeback_queue_io'
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
|
|
|
|
| |
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
|
|
|
|
|
|
| |
Correct spelling issues in the 'extra-build-config.md' file.
Signed-off-by: Andrzej Bednarski <andrzej.bednarski@gmail.com>
|
|
|
|
|
|
|
|
| |
Remove angstrom as it is no longer uptodate
Fixes Issue #563
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
These are android drivers, which help in running anbox on top of
raspberrypi machines
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
* until the fix is available upstream
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
| |
gcc-10
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
| |
Needed to provide KHR/khrplatform.h header
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This helps in getting right headers, we have made a choice to let
userland provide KHR/khrplatform.h when using it instead of mesa-gl
which could have been another provider, xserver-xorg's glx
implementation depends on virtual/libgl which in case of rpi-without-vc4
driver is provided by mesa-gl, as a result, compilation fails since no
one is providing this header in this case.
Fixes errors like
usr/include/GL/glext.h:56:10: fatal error: KHR/khrplatform.h: No such file or directory
| 56 | #include <KHR/khrplatform.h>
| | ^~~~~~~~~~~~~~~~~~~
Fixes issue #391
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
* since
https://github.com/agherzan/meta-raspberrypi/commit/36c3c2e7ca09806da460328767565bbf872a6ad8
which renamed gstreamer1.0-omx_1.14%.bbappend to gstreamer1.0-omx_1.16%.bbappend it didn't
parse with zeus and older
* with zeus it parses OK, but I believe people who use meta-raspberrypi
from dunfell branch in zeus builds should rather ask for backports they
are missing in zeus branch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
| |
Fixes the following error:
ERROR. input file "cfg/virtio.scc" does not exist
Signed-off-by: Murat Kilivan <murat.kilivan@gmail.com>
|
|
|
|
|
|
| |
Includes 5.4.59 bumps
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Needs some fixes from newer 5.4 kernel, e.g.:
1b940bbc5c55 Linux 5.4.56
df35e878d0a5 perf bench: Share some global variables to fix build with gcc 10
702d1b287fd2 perf env: Do not return pointers to local variables
73d2d6b421df perf tests bp_account: Make global variable static
to fix:
LINK perf/1.0-r9/perf-1.0/perf
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: error: perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list:2:15: invalid character
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: error: perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list:2:15: syntax error, unexpected end of file, expecting ';'
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: fatal error: unable to parse dynamic-list script file perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list
collect2: error: ld returned 1 exit status
Makefile.perf:609: recipe for target 'perf/1.0-r9/perf-1.0/perf' failed
make[2]: *** [perf/1.0-r9/perf-1.0/perf] Error 1
make[2]: *** Waiting for unfinished jobs....
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: error: perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list:2:15: invalid character
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: error: perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list:2:15: syntax error, unexpected end of file, expecting ';'
perf/1.0-r9/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/10.1.0/ld: fatal error: unable to parse dynamic-list script file perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list
collect2: error: ld returned 1 exit status
error: command 'arm-oe-linux-gnueabi-gcc' failed with exit status 1
cp: cannot stat 'perf/1.0-r9/perf-1.0/python_ext_build/lib/perf*.so': No such file or directory
Makefile.perf:571: recipe for target 'perf/1.0-r9/perf-1.0/python/perf.so' failed
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
|
|
|
|
| |
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the variable is not defined, bitbake will fail:
[...]
Task 'depends' should be specified in the form 'packagename:task'
[...]
This is because not expanding the variable leaves an invalid entry.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
This reverts commit f20ccfa11db4c0d1608cf6f3e654d29c5bfc3dd3.
|
|
|
|
| |
This reverts commit 89ca43fe6411a40d1ba8f5379e49affd78cdd644.
|
|
|
|
| |
This reverts commit fc494a35b513b05860c5a813239274017f1ef934.
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
FATPAYLOAD, DEPLOYPAYLOAD and RPI_SDIMG_EXTRA_DEPENDS
Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add DEPLOYPAYLOAD, similar to the existing FATPAYLOAD, to enable
adding files to the boot partition from the image deploy directory.
Files such as hypervisor binaries may not be present (and in fact
unwanted) within the root filesystem, so FATPAYLOAD is not sufficient.
DEPLOYPAYLOAD is implemented with support for file renaming from the
source file in the image deploy directory to the filename written into
the boot image. DEPLOYPAYLOAD is a space-separated list of entries for
additions, each of which can optionally be colon-separated:
<image deploy directory file>:<destination filename>
If the colon separator is omitted, the source deploy directory filename
is used as the destination filename.
The support for specifying the destination filename is used for
including Xen, which produces a machine-specific file in the image
deploy directory, and is written to the image partition with its
expected filename: xen.
Files that are to be included from the image deploy directory will
be produced by tasks that the do_image_rpi_sdimg[depends] must list,
so enable adding entries to that via a new variable:
RPI_SDIMG_EXTRA_DEPENDS.
These changes enable retiring a Xen-specific Raspberry Pi SD card
bbclass from meta-virtualization and have been tested on the
Raspberry Pi 4.
Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com>
|
|
|
|
|
|
|
| |
Add instructions how to use CAN_OSCILLATOR variable and declare support
for the Waveshare RS485 CAN HAT.
Signed-off-by: Jakub Luzny <jakub@luzny.cz>
|
|
|
|
|
|
| |
Current configuration (16MHz) is made for the PiCAN2 board that uses 16MHz crystal. This setting allows for use of Waveshare RS485 CAN HAT that has 8MHz crystal soldered (although according to Waveshare there is also a 12MHz crystal version of the board).
Signed-off-by: Jakub Luzny <jakub@luzny.cz>
|
|
|
|
|
|
|
| |
Added documentation for ENABLE_DUAL_CAN build configuration and support
for Pican2 Duo board.
Signed-off-by: Colin McAllister <colinmca242@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Currently ENABLE_CAN adds mcp2525-can0 to the dtoverlay.
ENABLE_DUAL_CAN was added to also add mcp2515-can1 to the dtoverlay.
This will allow a user to enable dual CAN when using a hat like the
PiCAN 2 Duo board.
Signed-off-by: Colin McAllister <colinmca242@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>
|
|
|
|
| |
This reverts commit a907c3261ef583f898803706cd596d372c6644cb.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
|