This fix an error building 'nvram' for ccardimx28js:
ERROR: Fetcher failure: Unable to find revision ... in branch master even from
upstream
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This cleans following warning:
Use of PRINC is deprecated.
The PR server should be used to automatically increment the PR.
See: https://wiki.yoctoproject.org/wiki/PR_Service
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The boot partions name has been changed in u-boot, so change it also
here to match current u-boot.
https://jira.digi.com/browse/DEL-949
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Building u-boot with Yocto does not show the version string in the
u-boot header. This is due to how Yocto compiles u-boot. It creates a
.scmversion file which may contain LOCALVERSION strings but in our case
it's empty. Later at build time u-boot's setlocalversion script detects
that file exists and exits with no further action (because it assumes
the file contains the version string).
https://jira.digi.com/browse/DEL-1007
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Fetch the source from the dey-1.6/maint branch which contains a fix
for a kernel oops introduced by the Yocto GCC 4.8.1 compiler.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The build was failing in our Jenkins server (Debian 6) with:
error: 'MS_PRIVATE' undeclared
error: 'MS_REC' undeclared
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The way to create rootfs images has changed in poky master. The whole
process has been reworked in python and the hook to create a new image
is the IMAGE_CMD variable. The old 'runimagecmd' shell function has
been deleted so we cannot override it in our custom class.
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This workaround is not needed anymore as the git fetcher bug is fixed in
poky's master branch.
This reverts commit 982af63902.
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Currently Vivante does not provide a valid GL API so Xorg fails to link
against it, we cannot workaround it easily in newer Xorg version so
instead of maintaining a pile of patches for it we use 1.14.4 version
as an interim solution.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
PR was based on meta-fsl-arm's 'linux-imx.inc' INC_PR, but this was
removed after Dora, so we need to remove PR from our kernel recipes to
avoid a bitbake parser error:
${INC_PR}.0/git')} exception SyntaxError: EOL while scanning string literal
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
linux-dey.inc is a copy of meta-fsl-arm's linux-imx recipe file, so
instead of copying the whole recipe just use that (including the file)
and code the differences.
While on it, add RDEPENDS_kernel-base="" to remove the dependence of the
rootfs image recipes on the linux image. We don't need/use the kernel
image in the rootfs as we load it from a different partition. This makes
rootfs images a bit smaller.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It was added to fix [DEL-898] but it is no longer needed after the
underlying changes in the rootfs hierarchy (added '/run' mountpoint)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These files were needed in previous versions of Yocto to overcome
different problems. Remove them as the default ones in current Yocto
version are good enough for our platforms.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Provides fw_printenv/fw_setenv utilities to read/write the u-boot
environment from Linux.
https://jira.digi.com/browse/DEL-800
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
change the directory (cd) and make the symbolic link in a subshell to
preserve the current working directory for any subsequent command.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We have all the kernels configured with DEVTMPFS support, so there is
no need to have static nodes in the image files. They are not used at
runtime because a TMPFS is mounted at '/dev'.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the moment this image is a VFAT file system containing the kernel
and the device tree blobs.
https://jira.digi.com/browse/DEL-932
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This package is now used in both ccimx6adpt and ccardimx28js.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
bitbake git's fetcher uses 'ls-remote' to get the branch revision to
checkout. If the repository has two branches ending equally the 'git
ls-remote' just picks the first one regardless of that being the correct
one.
In our case we were bitten by this bug because our git repo has:
...sha1-revision... refs/heads/android/v3.10/master
...sha1-revision... refs/heads/v3.10/master
and the fetcher was using the android branch instead of linux's
v3.10/master.
A patch has been sent upstream but while that gets applied to Dora
maintenance branch the workaround here is to set the absolute path in
the kernel's bitbake recipe.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Previously jffs2 images flashed from u-boot were not booting Linux. The
kernel was unable to mount the rootfs.
There have been some patches lately in the kernel that fix this problem,
so build jffs2 images.
Nevertheless the default image type is still ubifs when using linux 3.x.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
nvram, ubootenv and update_flash are machine related utilities. They
need to be configured per-platform via MACHINE_EXTRA_RDEPENDS and thus
leaving packagegroup-dey-core as much platform-agnostic as possible.
This also allows to skip these utilities for platforms not using them.
https://jira.digi.com/browse/DEL-915
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These utilities are very tight to the hardware so they need to be in
the BSP layer. This way they can also be installed in a poky distro
core-image-minimal without meta-digi-dey layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>