summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* linux-raspberrypi: Drop CONFIG_OABI_COMPAT completelypbarker/for-masterPaul Barker2018-04-201-8/+0
| | | | | | | 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>
* linux-raspberrypi: Drop inappropriate forced settingsPaul Barker2018-04-201-4/+0
| | | | | | | | | | | | 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>
* linux-raspberrypi: Don't set CONFIG_CMDLINEPaul Barker2018-04-201-3/+0
| | | | | | We force the command line at runtime via cmdline.txt anyway. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Drop support for CMDLINE_NFSROOT_USBPaul Barker2018-04-201-14/+0
| | | | | | | 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>
* linux-raspberrypi: Drop unnecessary configurationsPaul Barker2018-04-201-42/+0
| | | | | | | | | | | | | | | | | 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>
* Don't use RDEPENDS in recipes which don't create packagesPaul Barker2018-04-202-2/+2
| | | | | | | | RDEPENDS is fairly meaningless for recipes which don't create a package to be installed into the rootfs. Instead we should be using DEPENDS to guarantee correct ordering of build tasks. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* Drop unnecessary dependencies and tasksPaul Barker2018-04-207-5/+20
| | | | | | | | | | | | | | 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>
* linux-raspberrypi-dev: Update to v4.16.yPaul Barker2018-04-201-2/+2
| | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Update to v4.14.34Paul Barker2018-04-201-2/+2
| | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Update v4.9.y kernelPaul Barker2018-04-201-1/+1
| | | | | | This branch is still getting a few fixes upstream. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Allow specification of ncurses locationPaul Barker2018-04-204-4/+74
| | | | | | | | | | | | | | | | | | 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>
* rpi-config: support more commonly used config variables and update documentationHugo Hromic2018-04-202-5/+88
| | | | | | | | | | | Added support for and documented the following new extra build options: * gpu_freq overclocking option * disable boot rainbow splash screen * configure the boot delay after GPU firmware loading * configure common HDMI and composite video options Signed-off-by: Hugo Hromic <hhromic@gmail.com>
* bluez5: update bluez-firmwarePeter A. Bigot2018-04-153-0/+3
| | | | | | | | | | | | Updated BCM43430A1.hcd to bluez-firmware_1.2-3+rpt4.1.debian.tar.xz Added BCM4345C0.hcd for RasperryPi 3B+ support Files from https://github.com/RPi-Distro/bluez-firmware at commit 50fa5628b5c2fd6c59090fb18f02af9fd98c3170 Closes Issue #222 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
* layer.conf: add LAYERSERIES_COMPATMartin Jansa2018-04-061-0/+2
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* udev-udisks-rules-rpi: Hide initial boot partition from udisks2Andreas Müller2018-04-062-0/+21
| | | | | | | | | | | | | | | | | If I am not mistaken, many desktops (kde/lxqt/xfce..) use udisks2 to ask for devices which can be mounted. Without this patch the initial boot partition can be mounted by a single click on folder displayed on desktop or file manager. Why it is suggested to add this recipe to an image: * It removes annoying icon in desktop/file manager. * The initial boot partition is vfat. Unpriviledged users can modify content. E.g by removing files accidently, images can be turned into non-booting condition easily. And from security point of view, it is a disaster. FWIW: Have similar in all my BSPs vor very long time. Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
* mesa: enable dri3 explicitlyAndreas Müller2018-04-061-1/+5
| | | | | | | | Currently oe-core enables dri3 only for x11 AND vulcan. Although patch enabling dri3 by default in oe-core was sent out, make sure here dri3 is enabled - whatever oe-core suggest in the future. Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
* Merge pull request #215 from agherzan/ag_rpi3bplusPaul Barker2018-04-0312-96/+76
|\ | | | | RasperryPi 3B+ support
| * layer-contents.md: Update documentationag_rpi3bplusAndrei Gherzan2018-03-291-0/+12
| | | | | | | | | | | | | | * Raspberry Pi 3B+ support mentioned * Add info about linux-firmware-raspbian Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * linux-firmware: Remove as replaced by linux-firmware-raspbianAndrei Gherzan2018-03-293-85/+0
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * raspberrypi0-wifi.conf: Use linux-firmware-raspbian packageAndrei Gherzan2018-03-291-1/+1
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * rpi-base.inc: Add Raspberry Pi 3B+ dtbAndrei Gherzan2018-03-291-0/+1
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * raspberrypi3-64.conf: Use linux-firmware-raspbian packages and add bcm43455Andrei Gherzan2018-03-291-1/+1
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * raspberrypi3.conf: Use linux-firmware-raspbian packages and add bcm43455Andrei Gherzan2018-03-291-1/+1
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * linux-firmware-raspbian: New recipe which uses RPi-Distro repositoryAndrei Gherzan2018-03-291-0/+53
| | | | | | | | | | | | | | | | 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>
| * firmware: Update to 20180313Andrei Gherzan2018-03-281-5/+4
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * linux-raspberrypi: Update 4.14 recipe to 4.14.30Andrei Gherzan2018-03-281-2/+2
| | | | | | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
| * linux-raspberrypi: Update 4.9 recipe to current HEADAndrei Gherzan2018-03-281-1/+1
|/ | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
* docs: Remove reference to deprecated imagesPaul Barker2018-03-232-8/+6
| | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* gstreamer1.0-omx: refresh and clean-up patchesHugo Hromic2018-03-2311-296/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixes: WARNING: gstreamer1.0-omx-1.12.4-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify <recipe> devtool finish --force-patch-refresh <recipe> <layer_path> Then the updated patches and the source tree (in devtool's workspace) should be reviewed to make sure the patches apply in the correct place and don't introduce duplicate lines (which can, and does happen when some of the context is ignored). Further information: http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450 Details: Applying patch 0001-config-files-path.patch patching file config/bellagio/gstomx.conf Hunk #1 succeeded at 1 with fuzz 2. Hunk #2 succeeded at 9 with fuzz 2. patching file config/rpi/gstomx.conf Hunk #8 succeeded at 63 with fuzz 2. Hunk #10 succeeded at 82 with fuzz 2. Hunk #11 succeeded at 92 with fuzz 2. Now at patch 0001-config-files-path.patch deleted obsolete `gstreamer1.0-omx` directory with duplicated patches that are also in `gstreamer1.0-omx-1.12`. made file naming for `gstreamer1.0-omx_%.bbappend` consistent with the rest of the layer recipes. Signed-off-by: Hugo Hromic <hhromic@gmail.com>
* Merge pull request #202 from kraj/kraj/masterPaul Barker2018-03-184-248/+223
|\ | | | | Upgrade to 4.14 kernel
| * userland: Add wayland support for libbrcmEGLKhem Raj2018-03-081-240/+213
| | | | | | | | | | | | | | | | | | | | | | | | | | These renames are recently added https://github.com/raspberrypi/userland/commit/dd98890106c3c6145f640c4cfb825be937282a93 Some packages e.g. libSDL2 has started using the new names and are resulting in undefined symbols e.g. | /mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-bec-linux-gnueabi/libsdl2-mixer/2.0.2-r0/recipe-sysroot/usr/lib/libb rcmEGL.so: undefined reference to `wl_resource_post_error' Signed-off-by: Khem Raj <raj.khem@gmail.com>
| * firmware: Use snapshots from master againKhem Raj2018-03-081-5/+7
| | | | | | | | | | | | | | This time use the snapshot archives to avoid repo clone size issues Signed-off-by: Khem Raj <raj.khem@gmail.com>
| * userland: Update to master as of 20180219Khem Raj2018-03-081-2/+2
| | | | | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
| * linux-raspberrypi-4.14: Update past 4.14.22Khem Raj2018-03-081-1/+1
|/ | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* gstreamer1.0-omx: remove unused patchesMaxin B. John2018-03-082-62/+0
| | | | | | | | Remove the following unused patches: 1. 0002-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch 2. 0003-fix-decoder-flushing.patch Signed-off-by: Maxin B. John <maxin.john@intel.com>
* bluez5: brcm43438: update device dependencyPeter A. Bigot2018-03-071-1/+1
| | | | | | | | A previous patch changed the BT serial device to the alias, but did not update the device dependency resulting in the service failing to start on boot. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
* rpi-base.inc: set default wic kickstart filePeter A. Bigot2018-03-071-0/+1
| | | | | | | While wic is not a standard image, adding it to IMAGE_FSTYPES in local.conf will fail unless a WKS_FILE is provided. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
* sdimage-raspberrypi.wks: find /boot partition on mmcblk0Peter A. Bigot2018-03-071-2/+2
| | | | | | | | | | | | Recently wic was modified to no longer exclude /boot from partitions added to fstab. The --on parameter in many kickstart specifications insufficiently resolved the MMC device, resulting in attempts to mount /dev/mmcblkp1 as boot when the device should be /dev/mmcblk0p1. With systemd the mount failure is an error and the system drops into emergency mode. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
* rpi-basic-image: Refactor to avoid double deprecation warningsPaul Barker2018-02-281-2/+7
| | | | | | | | If rpi-basic-image is based on rpi-hwup-image, both deprecation warnings are printed which may be confusing. Therefore let's just copy over the relevant bits of rpi-hwup-image for now. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Change default version to 4.14.yPaul Barker2018-02-281-1/+1
| | | | | | | This matches the change made in the upstream firmware repository earlier in February. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Add recipe for v4.14.yPaul Barker2018-02-281-0/+6
| | | | | | It's alive! (a.k.a. upstream have stopped rebasing this branch) Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* firmware: Update to recent commitPaul Barker2018-02-281-5/+5
| | | | | | | | | | | | There hasn't been a tagged version of the firmware lately, but there have been several bugfixes listed in the commit history and we're about to move to v4.14.y as the default kernel so let's get up-to-date. The actual commit used is the most recent change to the firmware files as of 2018-02-26, the most recent commits which only change the kernel image and other files we don't use are ignored. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi-dev: Update to v4.15.yPaul Barker2018-02-281-2/+2
| | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-raspberrypi: Update to v4.9.80Paul Barker2018-02-281-2/+2
| | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* rpi-*-image: Deprecate old image namesPaul Barker2018-02-283-2/+10
| | | | | | | | | | | | | | | As discussed on the issue tracker, it's confusing for meta-raspberrypi to have its own set of image names filling the same jobs as the core images. Therefore we are marking these images as deprecated and will be removing them in the future. The recommended replacement images are as follows: rpi-hwup-image -> core-image-minimal rpi-basic-image -> core-image-base The image 'rpi-test-image' will be kept and is not marked as deprecated, it is still useful for testing. It it updated to be based on 'core-image-base'. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* rpio: Use pypi.bbclassPaul Barker2018-02-281-5/+3
| | | | | | This should resolve recent issues with the non-https URL in SRC_URI. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* Fix do_image_rpi_sdimg/do_image_wic dependenciesPaul Barker2018-02-282-0/+4
| | | | | | | | | | | | | | | | | | | | | The dependency resolution code in bitbake has recently been optimized and this seems to have slightly changed the behaviour of do_image_rpi_sdimg and do_image_wic. We ensure that the main build artifacts are present by depending on the relevant do_deploy and do_populate_sysroot tasks. However, we need to ensure that other build tasks for these dependencies have also been executed before we try to create our image. This can be achieved by adding a recursive dependency on do_build, so that the do_build tasks of all recipes in the dependency chain of do_image_rpi_sdimg/do_image_wic are executed before the image function itself is executed. The original issue seen here was that 'recipedata' files were not copied to 'tmp/deploy/licenses' as do_populate_lic for each dependency had not been ran before the image creation function. The write_deploy_manifest function from license.bbclass (listed in IMAGE_POSTPROCESS_COMMAND) therefore failed. Adding the recursive dependency on do_build fixes this issue, ensuring do_populate_lic runs before do_image_rpi_sdimg/do_image_wic. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* u-boot: Update RPi Zero W defconfig to support DTB.Drew Moseley2018-02-142-0/+47
| | | | | | | | | | | | This makes the defconfig more consistent with the RPi 3 and CONFIG_OF_EMBED is needed to get the RPi firmware provided DTB to function. Recently removed by: a50e19695f2cc655ef6248b77c8244519dbb468c u-boot: drop upstreamed patches in v2018.01 however this change missed the cutoff for v2018.01 Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
* linux-firmware: fix addition of NVRAM file to image (fixes #184)Hugo Hromic2018-02-051-1/+1
| | | | Signed-off-by: Hugo Hromic <hhromic@gmail.com>
* userland: Update to latest masterJeff Wannamaker2018-02-0217-51/+197
| | | | | | | | | | Add patch to allow multiple wayland clients per process userland has limit of one wayland client per process and thereby allow compositors to launch multiple wayland client apps Signed-off-by: Jeff Wannamaker <jeff_wannamaker@cable.comcast.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-06-14 14:22:11 +0000