linux/meta-boot2qt.git/meta-nvidia-extras, branch v5.11.2

Merge remote-tracking branch 'origin/morty' into pyro

2018-02-05T08:17:31+00:00

Automotive related changes left intact for pyro, as they require further work than just a basic merge due component branching differences etc. * origin/morty [MERGED]: qt5: don't build tests by default qbsp: fix replace tags quickcompiler: update to 5.9.4 release revision meta-qt5: update to Qt 5.9.4 RC meta-qt5: update to Qt 5.9.4 snapshot meta-qt5: update meta layer poky: update revision ppp: remove obsolete patch meta-qt5: update meta layer internal-build: prepend mirror variables qtdeviceutilities: update revision meta-qt5: update meta layer poky: update revision * origin/morty [NOT MERGED]: Fix license checksum due to incremented year number Update GammaRay revision multiscreen-demo: update revision and fix startup automotive: update revisions sdk: add qtapplicationmanger staticdev package qtivi: enable ivigenerator for toolchain appman: add dependency to nativesdk-qtdeclarative qtivi: Update to the latest version and add PACKAGECONFIG options for qtsimulator Changes not staged for commit: recipes-qt/automotive/gammaray_git.bb recipes-qt/automotive/multiscreen-demo_git.bb recipes-qt/automotive/qtapplicationmanager_git.bb recipes-qt/automotive/qtivi_git.bb recipes-qt/packagegroups/nativesdk-packagegroup-b2qt-automotive-qt5-toolchain-host.bb recipes-qt/packagegroups/packagegroup-b2qt-automotive-qt5-toolchain-target.bb Conflicts: recipes-qt/automotive/gammaray_git.bb recipes-qt/automotive/neptune-ui_git.bb recipes-qt/automotive/qtapplicationmanager_git.bb recipes-qt/automotive/qtivi_git.bb recipes-qt/qt5/qtdeviceutilities.bb recipes-qt/qt5/qtquickcompiler_git.bb scripts/manifest.xml Task-number: QTBUG-65164 Change-Id: I98fe358aaaf55a609dc34f7b8cc65525d493ff26

tegra: correctly append to DEPENDS

2017-11-07T06:18:34+00:00

Cannot use += together with _class-target override. Change-Id: I6f67f1b5eb972264cb9242b91266b5b8329d9ee2 Reviewed-by: Mikko Gronoff

tegra: include older version of weston for Drive CX

2017-08-19T05:39:02+00:00

The NVidia toolchain is dependent on using older version of weston/wayland than poky/pyro currently provides. Add recipes from poky/krogoth which was still working. Change-Id: Iaab46edcdf01afd7eed30747395c80fb4bd68c39 Reviewed-by: Mikko Gronoff

tegra: fix nvidia recipe issues with pyro

2017-08-17T06:45:24+00:00

systemd-compat-units: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum] openssl-native-1.0.2h-r0 do_populate_sysroot: sstate found an absolute path symlink Change-Id: I98b49e109792d302a165e4975d2818d0614489f0 Reviewed-by: Mikko Gronoff

tegra: correctly add dependency

2017-06-06T07:43:45+00:00

The class override did not append new dependencies correctly. Change-Id: I8311310eb67ea482cdf16b3cf2ed7551f1fe1693 Reviewed-by: Mikko Gronoff

tegra: update to [4.1.4.0] Vibrante 4.1 Linux Drive CX2

2017-04-28T09:13:42+00:00

Task-number: QTAUTO-272 Change-Id: I63a564996a363cdd14f14f51a88364f9a9f99d73 Reviewed-by: Teemu Holappa

Rename nvidia extra layers

2017-02-15T08:32:05+00:00

Reserve meta-tegra-extras for the open source meta-tegra layer used for Jetson TX1 and TK1. Change-Id: I78b168105f306ee342671b612205d68b56016c14 Reviewed-by: Mikko Gronoff

Fix to NVidia's tegra configurations.

2016-05-05T08:16:14+00:00

Changed both nvidia-logan and tegra-t18x to use the same metalayer from the Vibrante 4.0 SDK. Kernel sources and libraries are stored into the internal CI repository. These definitions can be overridden by SDK folder using following environment variables: export KERN_DIR=~/Vibrante4.0_RC1/vibrante-t186ref-linux_src/kernel export PLATFORM_TOPDIR=~/Vibrante4.0_RC1/vibrante-t186ref-linux export TOOLCHAIN_PATH=~/Vibrante4.0_RC1/toolchains/tegra-4.9-nv export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE TOOLCHAIN_PATH KERN_DIR PLATFORM_TOPDIR" Change-Id: If58a0fcbe01daa9a55dd041b79a9d80a90fde284 Reviewed-by: Samuli Piippo

nvidia-t18x support

2016-03-22T14:16:00+00:00

Steps to use this: Set up vibrante installation, mine looks like this: $ ls -l ~/VibranteSDK total 234880 drwxrwxr-x 1 louai louai 298 Mar 20 2014 eclipse -r-xr-xr-x 1 louai louai 171826846 Jan 4 09:59 NVIDIA_Tegra_Graphics_Debugger_2.1_linux-v4l_l4t-egl.run -r--r--r-- 1 louai louai 68688729 Jan 4 09:59 NVIDIA_Tegra_System_Profiler_2.5-linux-x64.tar.gz drwxr-xr-x 1 louai louai 262 Jan 5 14:50 toolchains drwxrwxr-x 1 louai louai 34 Jan 5 13:55 vibrante-oss-src drwxr-xr-x 1 louai louai 12 Jan 4 09:47 vibrante-t186ref-cuda drwxrwxr-x 1 louai louai 264 Feb 10 10:50 vibrante-t186ref-foundation drwxr-xr-x 1 louai louai 164 Jan 5 14:49 vibrante-t186ref-foundation_src drwxrwxr-x 1 louai louai 228 Jan 5 13:56 vibrante-t186ref-linux drwxr-xr-x 1 louai louai 314 Feb 10 10:58 vibrante-t186ref-linux_sr Set up Yocto build dir: $ mkdir ~/work $ cd ~/work $ ~/tqtc-b2qt/yocto-meta/b2qt-init-build-env init --device tegra-t18x Add NVIDIA's Yocto things: $ mkdir ~/work/sources/nvidia-layer $ cd ~/work/sources/nvidia-layer $ tar xf ~/VibranteSDK/vibrante-t186ref-linux_src/yocto/nvidia-layer.tgz $ cd - Set up build environment: $ export MACHINE=tegra-t18x $ . setup-environment.sh Set the following environment variables: $ export KERN_DIR=~/VibranteSDK/vibrante-t186ref-linux_src/kernel $ export PLATFORM_TOPDIR=~/VibranteSDK/vibrante-t186ref-linux $ export TOOLCHAIN_PATH=~/VibranteSDK/toolchains/tegra-4.9-nv $ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE TOOLCHAIN_PATH KERN_DIR PLATFORM_TOPDIR" Add NVLAYER_DIR to local.conf: $ echo 'NVLAYER_DIR = "${TOPDIR}/../sources/nvidia-layer"' >> conf/local.conf Build your image: $ bitbake b2qt-embedded-qt5-image Flash your board: $ cd $PLATFORM_TOPDIR $ mv targetfs targetfs-old $ cd targetfs && tar xf /path/to/rootfs.tar.bz2 $ cd ../../vibrante-t186ref-foundation/utils/scripts/bootburn $ ./bootburn.sh -b p2382-t186 Change-Id: I4209cd0c19a007c4457460fd67342fc579c2a735 Reviewed-by: Teemu Holappa