Age | Commit message (Collapse) | Author |
|
The rpi-4.9.y branch has not been updated since July 2018.
Signed-off-by: Paul Barker <paul@betafive.co.uk>
|
|
Signed-off-by: Paul Barker <paul@betafive.co.uk>
|
|
* The branch rpi-4.19.y (and rpi-4.18.y) was recently force pushed and
current d65a0f76d3adcf86a6f5c614c68edb3aeb3b8590 nor previous
3c468fc8191d276e3e9efd976a0ff71271f3fc51 aren't included in any
branch, from my local checkout update:
e24b1f6c0c79..5f4b16e4a8d6 rpi-4.14.y -> up/rpi-4.14.y
e54efc381a97..22bb67b8e2e8 rpi-4.14.y-rt -> up/rpi-4.14.y-rt
3a1a31d70660...d58c595b013f rpi-4.18.y -> up/rpi-4.18.y (forced update)
48dfbb408fdd...ab8652c03fa0 rpi-4.19.y -> up/rpi-4.19.y (forced update)
[new branch] rpi-4.20.y -> up/rpi-4.20.y
[new branch] rpi-5.0.y -> up/rpi-5.0.y
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
The rpi-4.19.y branch has been rebased and the commit specified for
4.19.30 no longer exists upstream.
Signed-off-by: Peter A. Bigot <pab@pabigot.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>
|
|
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: Zahari Petkov <zahari@balena.io>
|
|
Latest bluez-firmware release updates BCM4345C0.hcd to
003.001.025.0156.0280, restoring LE scan capability.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
|
|
This helps to ignore dangling bbappend when meta-oe is not included in
layer mix
Fixes #366
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
select the rt kernel by adding in local.conf:
PREFERRED_PROVIDER_virtual/kernel = "linux-raspberrypi-rt"
Signed-off-by: Phong Tran <tranmanphong@gmail.com>
|
|
To match 20181211 firmware
Signed-off-by: Pepijn de Vos <pepijndevos@gmail.com>
|
|
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
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>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
- raspbian-nf = "b518de45ced519e8f7a499f4778100173402ae43"
- raspbian-bluez = "ade2bae1aaaebede09abb8fb546f767a0e4c7804"
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* this will make this bbappend a bit more version agnostic
* depends on oe-core commits from:
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153164.html
to prevent including ${PN}-cypress-license package twice in PACKAGES
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153165.html
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Contains the following changes:
7f9c648dad64 drm/vc4: Move IRQ enable to PM path
which fixes an unbalanced IRQ enable warning, which was rapported
in #286
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* use INITRAMFS_SYMLINK_NAME from new kernel-artifact-names.bbclass
instead of KERNEL_INITRAMFS
* the documentation says that KERNEL_INITRAMFS should be used to
define extension of initramfs, but in linux-raspberrypi.inc it's
defined only to 1 or empty based on INITRAMFS_IMAGE_BUNDLE variable
and I don't see any code in meta-raspberry or oe-core which would
use KERNEL_INITRAMFS to actualy name the initramfs artifact to create:
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
used in classes/sdcard_image-rpi.bbclass
* also fix the assumption that there is -${MACHINE} suffix in:
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
because that's defined as KERNEL_IMAGE_SYMLINK_NAME and some DISTROs
might use different value
* this depends on oe-core changes which were merged today:
http://git.openembedded.org/openembedded-core/commit/?id=7d0ef0eaa1bfe97015a774c26f5791622e7e8b12
* this is the last piece of previous pull-request:
https://github.com/agherzan/meta-raspberrypi/pull/159
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Upstream recipe was updated and the license checksum needed refresh.
See: <https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e3bec3951b2f95e5f9a592cc3f64c8f5fb152f57>
Signed-off-by: Hugo Hromic <hhromic@gmail.com>
|
|
The attempt to Raspbian updated firmware blobs in packages separate from
linux-firmware introduced unresolvable conflicts with the standard
linux-firmware roll-up package. Revert to using an augmented
linux-firmware recipe that overrides and adds firmware from two Raspbian
repositories that have up-to-date images.
Closes #244
Signed-off-by: Peter A. Bigot <pab@pabigot.com>
|
|
Signed-off-by: Peter A. Bigot <pab@pabigot.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
There's no reason to support the old, outdated ARM OABI when upstream
linux-raspberrypi doesn't support this by default.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
CONFIG_BLK_DEV_DRBD: Deciding whether to use the in-kernel DRBD module or the
external drbd recipe in meta-networking is a policy decision and doesn't belong
in our BSP layer.
CONFIG_LEGACY_PTYS: These are legacy for a reason. They're not enabled in the
defconfig so they shouldn't be required for rpi devices. Let's drop this here,
it can be added back in a distro layer where (if) needed.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
We force the command line at runtime via cmdline.txt anyway.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
This is obsolete, undocumented and won't work anyway since we force the kernel
command line to ${CMDLINE} via the cmdline.txt file.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
KERNEL_ENABLE_CGROUPS: This is obsolete, all required config options for cgroups
are enabled by default.
KERNEL_INITRAMFS: Some of the config options we set are already enabled by
default.
UDEV_GE_141: This is long obsolete and all the required config options are
already set in the defconfig.
ARM_KEEP_OABI: AEABI=y and OABI_COMPAT=n are already set in the defconfig.
CONFIG_LOCALVERSION_AUTO: This setting is already disabled in the defconfig.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
We have a few recipes which only deploy files that go into the boot partition
and do not create packages to be installed into the rootfs. These recipes don't
need to run the usual packaging tasks so we can drop them to speed up the build
a little.
We also have a bunch of recipes that don't need the usual toolchain as they just
copy files or invoke native commands like `mkimage`. So to speed up the build a
little more we can set INHIBIT_DEFAULT_DEPS to avoid an unnecessary dependency
on the toolchain.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
This branch is still getting a few fixes upstream.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
From patch message:
In some cross build environments such as the Yocto Project build environment
it provides an ncurses library that is compiled differently than the host's
version. This causes display corruption problems when the host's curses
includes are used instead of the includes from the provided compiler are
overridden. There is a second case where there is no curses libraries at
all on the host system and menuconfig will just fail entirely.
The solution is simply to allow an override variable in check-lxdialog.sh
for environments such as the Yocto Project. Adding a CROSS_CURSES_LIB and
CROSS_CURSES_INC solves the issue and allowing compiling and linking against
the right headers and libraries.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
This packages only the firmware needed for the RaspberryPi boards. We use the
RPi-Distro as it's already maintained by the Raspbian guys and we get better
support for the RaspberryPi needed firmwares.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
It's alive! (a.k.a. upstream have stopped rebasing this branch)
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|
|
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
|