summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* extra-build-config.md: Document DISABLE_VC4GRAPHICSag/DISABLE_VC4GRAPHICSAndrei Gherzan2019-09-131-0/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-base.inc: Introduce DISABLE_VC4GRAPHICSAndrei Gherzan2019-09-131-1/+1
| | | | | | | | | | | | Since we enabled vc4graphics by default[1], there is no easy way to disable it if needed. This patch introduces a variable (DISABLE_VC4GRAPHICS) which when set to '1' will not add 'vc4graphics' to MACHINE_FEATURES forcing the old behaviour. One could use it in 'local.conf' for example. [1] https://github.com/agherzan/meta-raspberrypi/pull/417 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi*.conf: Remove vc4 configuration as we already default to itAndrei Gherzan2019-09-133-3/+0
| | | | | | | | | As of late[1], we defaulted to enabling vc4graphics in MACHINE_FEATURES. Let's cleanup the machine configurations as per this change. [1] https://github.com/agherzan/meta-raspberrypi/pull/417 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-linux: removed protocoll setting from SRC_URITimm Eversmeyer2019-09-121-1/+1
| | | | | | Default protocoll for git will be used. Default setting is in the most case https. Signed-off-by: Timm Eversmeyer saeugetier@gmail.com
* extra-build-config.md: add RPi 0W to UART sectionBernardo A. Rodrigues2019-09-101-1/+1
| | | | | | This makes it clear in the docs that ENABLE_UART can be used both for the RPi 0W or 3. Signed-off-by: Bernardo A. Rodrigues <bernardaraujor@gmail.com>
* linux-raspberrypi: Update 4.19 recipe to 4.19.71Andrei Gherzan2019-09-091-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot-fw-utils: apply the same rpi4 patches as for u-boot recipeMartin Jansa2019-09-093-12/+16
| | | | | | | | | | | | | | | | * otherwise u-boot-fw-utils build for rpi4 fails with: scripts/kconfig/conf --defconfig=arch/../configs/rpi_4_defconfig Kconfig *** *** Can't find default configuration "arch/../configs/rpi_4_defconfig"! *** scripts/kconfig/Makefile:128: recipe for target 'rpi_4_defconfig' failed * cannot include/require u-boot_2019.07.bbappend directly in u-boot-fw-utils_2019.07.bbappend, because then it fails with: "u-boot_2019.01.bbappend: not a BitBake file" Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* eglinfo: Drop bbappendKhem Raj2019-09-042-4/+0
| | | | | | eglinfo has been removed from OE-Core since aa36510ebe Signed-off-by: Khem Raj <raj.khem@gmail.com>
* layer.conf: Add zeus to compatible layersKhem Raj2019-09-041-1/+1
| | | | | | zeus is codename for next 3.0 release Signed-off-by: Khem Raj <raj.khem@gmail.com>
* raspberrypi-firmware: upgrade to latest to fix vc4-fkmsMartin Jansa2019-08-281-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * with 4.19.66 kernel the vc4-fkms no longer works, because it doesn't get any usable modes from firmware * this behavior was introduced probably in one of following changes: https://github.com/raspberrypi/firmware/commit/38e81f25e639d19fc0ce6e67fd39998c340a15d5 https://github.com/raspberrypi/linux/pull/3082 https://github.com/raspberrypi/linux/pull/3110 https://github.com/raspberrypi/firmware/commit/66bafab005569e3eb92ec54cd3efeee3da338738 * without this fix: root@rpijama:~# cat /proc/device-tree/soc/firmwarekms@7e600000/status okay root@rpijama:~# modeprint vc4 Starting test Resources count_connectors : 1 count_encoders : 1 count_crtcs : 1 count_fbs : 0 Connector: HDMI-A-1 id : 51 encoder id : 0 conn : connected size : 0x0 (mm) count_modes : 0 count_props : 9 props : 1 2 5 6 52 53 54 55 56 count_encoders : 1 encoders : 50 Encoder: TMDS id :50 crtc_id :0 type :2 possible_crtcs :0x1 possible_clones :0x0 Crtc id : 49 x : 0 y : 0 width : 0 height : 0 mode : 0xfec884 gamma size : 0 Ok * with this fix: martin@jama ~ $ sshc root@rpijama Warning: Permanently added 'rpijama,192.168.169.37' (ECDSA) to the list of known hosts. root@rpijama:~# modeprint vc4 Starting test Resources count_connectors : 1 count_encoders : 1 count_crtcs : 1 count_fbs : 0 Connector: HDMI-A-1 id : 51 encoder id : 50 conn : connected size : 1600x900 (mm) count_modes : 22 count_props : 9 props : 1 2 5 6 52 53 54 55 56 count_encoders : 1 encoders : 50 Mode: "1920x1080" 1920x1080 60 Mode: "1920x1080" 1920x1080 60 Mode: "1920x1080" 1920x1080 50 Mode: "1920x1080" 1920x1080 30 Mode: "1920x1080" 1920x1080 30 Mode: "1920x1080" 1920x1080 25 Mode: "1920x1080" 1920x1080 24 Mode: "1920x1080" 1920x1080 24 Mode: "1280x1024" 1280x1024 60 Mode: "1360x768" 1360x768 60 Mode: "1152x864" 1152x864 60 Mode: "1280x720" 1280x720 60 Mode: "1280x720" 1280x720 60 Mode: "1280x720" 1280x720 50 Mode: "1024x768" 1024x768 60 Mode: "800x600" 800x600 60 Mode: "720x576" 720x576 50 Mode: "720x480" 720x480 60 Mode: "720x480" 720x480 60 Mode: "640x480" 640x480 60 Mode: "640x480" 640x480 60 Mode: "720x400" 720x400 70 Encoder: TMDS id :50 crtc_id :49 type :2 possible_crtcs :0x1 possible_clones :0x0 Crtc id : 49 x : 0 y : 0 width : 1920 height : 1080 mode : 0x1fcde54 gamma size : 0 Ok * tested on raspberrypi3 B weston works fine qtbase-examples tested with: /usr/share/examples/opengl/cube/cube -platform eglfs * the same issue is now in warrior, after someone tests on raspberrypi4 it would be good to backport this to warrior as well Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* bpftool: Enable for rpi since default kernel is > 4.14 nowKhem Raj2019-08-281-3/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mesa: Enable vc4, v3d, kmsro gallium driversKhem Raj2019-08-281-3/+2
| | | | | | This enables new v3d driver which needs kmsro as dependency Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-raspberrypi-rt: update to latest commit for 4.14 seriesFrancesco Giancane2019-08-221-2/+2
| | | | | | | | Update linux kernel 4.14 series recipe for building with latest -rt branch. This fixes #474. Signed-off-by: Francesco Giancane <francescogiancane8@gmail.com>
* linux-raspberrypi: add linux-raspberrypi-rt 4.19Vincenzo Pacella2019-08-183-11/+19
| | | | | | add rt kernel recipe for version 4.19 Signed-off-by: Vincenzo Pacella <shaduz@shaduzlabs.com>
* linux-raspberrypi: update to 4.14.114Francesco Giancane2019-08-151-2/+2
| | | | | | | | | | | | | Kernel 4.19.y and above was patched to rename the Raspberry Pi Zero W dts. Unfortunately, this modification was not propagated to previous kernels, especially on the 4.14.y series which is still supported in this layer. Thus, kernel 4.14.y would not build because correct .dts file is not found. The aforementioned modification was merged as backport back in 4.14.y series. Updating to the latest commit fixes the issue. Signed-off-by: Francesco Giancane <francescogiancane8@gmail.com>
* raspberrypi4-64: Remove the 3G RAM limitationAndrei Gherzan2019-08-151-1/+1
| | | | | | | | | The PCIe bounce buffers were ported[1] in the kernel so we can remove this limitation now. [1] https://github.com/raspberrypi/linux/pull/3144 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* mesa: Add v3d and kmsro driver as wellAndrei Gherzan2019-08-151-1/+1
| | | | | | | | Videocore 5/6 support was added as a separate driver in mesa: v3d. Enable this so we can have it available for Raspberry Pi 4. Also, this driver depends on kmsro. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Update 4.19 recipe to 4.19.66Andrei Gherzan2019-08-151-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware.inc: Update to 20190718Andrei Gherzan2019-08-151-4/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* python-rtimu,python-sense-hat: Convert to py3 modulesKhem Raj2019-08-144-7/+7
| | | | | | py2 is on its way out from oe-core Signed-off-by: Khem Raj <raj.khem@gmail.com>
* omxplayer: Bump revisionKirill Goncharov2019-08-123-7/+7
| | | | | | | | Bump revision to fix playback errors on RPi 4 (https://github.com/popcornmix/omxplayer/issues/733) and update patches accordingly. Update the license hash because of the change in FSF mailing address. Signed-off-by: Kirill Goncharov <kdgoncharov@gmail.com>
* sdcard_image-rpi.bbclass: use -v for all mcopy calls and add bbfatal in case ↵Martin Jansa2019-08-061-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mcopy fails * I have this in our layer for some time: RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/vc4-fkms-v3d.dtbo" because we're using vc4graphics also on raspberrypi3 and it was working fine until recently. * now the default rpi-base.inc in warrior and master branch includes the same since: https://github.com/agherzan/meta-raspberrypi/commit/37aa050d5a44eb797540ef50408c2ca8e3da6fa0 and do_image_rpi_sdimg started failing with a bit useless log: ... Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 46.1MB 41.9MB primary boot, lba 2 46.1MB 1145MB 1099MB primary mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command. * after adding -v to mcopy calls I got slightly better log: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo WARNING: exit code 1 from a shell command. * the issue is that mcopy behavior in non-interactive shell is to fail when the target file already exists (sometimes it seems to cause mcopy to hang forever), but when you execute the run.do_image_rpi_sdimg script manually in interactive shell it will nicely show this prompt on stderr: $ dtb=vc4-fkms-v3d.dtbo recipe-sysroot-native/usr/bin/mcopy -i boot.img -s BUILD/deploy/images/raspberrypi3/$dtb ::overlays/$dtb Long file name "vc4-fkms-v3d.dtbo" already exists. a)utorename A)utorename-all r)ename R)ename-all o)verwrite O)verwrite-all s)kip S)kip-all q)uit (aArRoOsSq): o * with the bbfatal the log is finally a bit more useful: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo ERROR: mcopy cannot copy TOPDIR/BUILD/deploy/images/raspberrypi3/vc4-fkms-v3d.dtbo into boot.img WARNING: exit code 1 from a shell command. * the only exception is FATPAYLOAD where it was ignoring mcopy with || true before, I've added bbwarn, because even issues like mentioned there "vfat issues like not supporting .~lock files" are probably worth reporting as warning (why would people add .~lock to FATPAYLOAD if it cannot be copied into boot.img) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* xorg-xserver: Adapt bbappend to latest OE-coreKhem Raj2019-08-061-9/+1
| | | | | | | | There is no need to override complete packageconfig but just the openGL part, this ensures that any common change in oe-core reflects for rpi as well and does not cause the packageconfigs to go stale Signed-off-by: Khem Raj <raj.khem@gmail.com>
* packagegroup-rpi-test: Depend on wireless-regdb instead of crdaKhem Raj2019-07-301-1/+1
| | | | | | | | this should bring in crda if needed Fixes issue #456 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* drbd: Disable for rpi machinesKhem Raj2019-07-281-0/+3
| | | | | | | | | | | | | | Its enabled in linux-raspberrypi modules in defconfig so we can ignore external driver for now, fixes ERROR: linux-raspberrypi-1_4.19.58+gitAUTOINC+d5dc848c98-r0 do_packagedata_setscene: The recipe linux-raspberrypi is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /mnt/a/yoe/build/tmp/pkgdata/raspberrypi3-64/runtime/kernel-module-drbd-4.19.58.packaged (matched in manifest-raspberrypi3_64-drbd.packagedata) /mnt/a/yoe/build/tmp/pkgdata/raspberrypi3-64/runtime/kernel-module-drbd-4.19.58 (matched in manifest-raspberrypi3_64-drbd.packagedata) Please verify which recipe should provide the above files. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* layer.conf: Add meta-networking to dynamic layersKhem Raj2019-07-281-0/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* webkitgtk: Remove -DUSE_GSTREAMER_GL=OFF for vc4graphicsKhem Raj2019-07-281-1/+0
| | | | | | | | | | | | This is no longer needed, on the contrary is fails the build for webkitgtk Fixes webkitgtk-2.24.2/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:1007:33: error: use of undeclared identifier 'TEXTURE_MAPPER_COLOR_CONVERT_FLAG' | m_textureMapperFlags |= TEXTURE_MAPPER_COLOR_CONVERT_FLAG; | ^ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* userland: Upgrade to latestKhem Raj2019-07-2820-67/+98
| | | | | | | Fix build with glibc 2.30 Forward patches to 20190724 release Signed-off-by: Khem Raj <raj.khem@gmail.com>
* README.md: Use matrix chat roomAndrei Gherzan2019-07-251-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4-64.conf: Limit RAM to 3GAndrei Gherzan2019-07-251-1/+1
| | | | | | | | | | | | | | | The PCI controller on the Raspberry Pi 4 acts as a DMA controller and can only address the first 3Gb[1] of the memory space. On 32bit this was addressed by implementing bouncing buffers[2] but this currently has no support for arm64. In order to have working USB, as a workaround, we limit the ram to 3G. Fixes #446 [1] https://github.com/raspberrypi/linux/issues/3093 [2] https://github.com/raspberrypi/linux/blob/rpi-4.19.y/drivers/pci/controller/pcie-brcmstb-bounce.c Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi*: Define ARMSTUB for all machinesAndrei Gherzan2019-07-199-0/+17
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* armstubs: Error out when ARMSTUBS is not definedAndrei Gherzan2019-07-191-0/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* sdcard_image-rpi: Check for armstub based on machine featureAndrei Gherzan2019-07-191-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-config: Check for armstub based on machine featureAndrei Gherzan2019-07-191-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot: Update patches for RPi4Andrei Gherzan2019-07-1915-861/+258
| | | | | | | | | | | | After a review in upstream, some of the patches were modified. Most notable changes: 1. use directly the dtb passed by the firmware and make sure uboot doesn't tweak memory/reg 2. remove known unimplemented support (usb, eth etc.) 3. drop patches that are not needed anymore with the new firmware update (for example 0012-bcm283x-mbox-Correctly-wait-for-space-to-send.patch) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-base.inc: Enabling open-source vc4graphics driver for all RPI platformsRiyaz2019-07-181-1/+1
| | | | | | | | Vc4graphics enables drm backend on wayland Compositor (weston & westeros) Appending vc4graphics machine feature to use mesa drivers for OpenGL and V4l2 for video. Signed-off-by: Riyaz <Riyaz.l@ltts.com>
* u-boot: Replace custom fork by patchesAndrei Gherzan2019-07-1813-4/+1110
| | | | | | | | The upstream branch might suffer rebases due to effort of pushing the patches upstream. To avoid issues, let's have here the patches we need for RPi 4 support. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-config: Check some config values against "1"Carton2019-07-181-5/+5
| | | | | | | | | | | | | | | | When we read the docs, we have the feelings that theses variables are boolean ones. So I was setting, for example in my distro.conf file the variable ' ENABLE_I2C = "1" ' to enable I2C. Then I wanted to disable it by simply setting 'ENABLE_I2C' to "0" but it wasn't working. So I noticed that, for example, ' ENABLE_UART ' was checked with ' = "1" ' condition and some other "boolean" was checked against ' -n ' like for ENABLE_I2C. This commit tries to have an uniform behavior for all variables that are shown in the doc under the format ' VARIABLE = "1" ' to enable them and the reader can think they are kind of 'boolean' values. Signed-off-by: Joël Carron <joel.carron@eeproperty.ch>
* bluez5: Fixed typo (RC_URI -> SRC_URI)Carton2019-07-181-1/+1
| | | | Signed-off-by: Joël Carron <joel.carron@eeproperty.ch>
* raspberrypi4-64.conf: Remove memory limitationAndrei Gherzan2019-07-181-1/+1
| | | | | | | | We can do this because the kernel now includes a workaround for the DMA issue. https://github.com/raspberrypi/linux/pull/3080 Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19 revisionAndrei Gherzan2019-07-181-1/+1
| | | | | | | This version includes a workaround for the usable DMA memory. It limits the DMA to the first 1G. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Build dtbs with dtbs make target for all 64bit targetsAndrei Gherzan2019-07-161-3/+5
| | | | | | | We already do this for rpi3-64 and we will need it for rpi4-64 as well. See 6c4de0b5fe44b8e661f1391ee8540a7f04d75315 for more details. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19 to 4.19.58Andrei Gherzan2019-07-161-2/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4.conf: The firmware uses kernel7l.img when LPAE is supportedAndrei Gherzan2019-07-161-1/+2
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware: Update to 20190709Andrei Gherzan2019-07-161-4/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* u-boot: Use a temporary fork for RPi4 supportAndrei Gherzan2019-07-161-0/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4-64.conf: Uboot configuration and drop armstubAndrei Gherzan2019-07-161-2/+8
| | | | | | We drop armstub configuration because the new firmware includes them. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi4.conf: Define uboot defconfigAndrei Gherzan2019-07-161-0/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Bump 4.19.57 revisionAndrei Gherzan2019-07-161-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* linux-raspberrypi: Upgrade to 4.19.57Khem Raj2019-07-111-2/+5
| | | | | | | | Fixes vc4 graphics issues seen with 4.19.56 Add -@ to device tree flags so we can debug/dump the dtb with symbols, helps in debugging the overlays Signed-off-by: Khem Raj <raj.khem@gmail.com>