This lowers the maintenance of these layers. The manifest used with repo
deals with the specific sha1s.
https://jira.digi.com/browse/DEL-495
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The xserver-common package in meta-openembedded replaces and conflicts
with the x11-common package in poky.
But by default poky sets the VIRTUAL-RUNTIME_xserver_common variable
in packagegroup-core-x11 to x11-common.
This causes a build error on the rootfs creation step when images with
the dev-pkgs image feature are compiled. The build error is not quite
understood, but forcing the xserver common in the distribution works
and resolves any doubt regarding to which is the package actually
being included in the target system.
xserver-common was also the package included by default in normal (non
development) builds.
https://jira.digi.com/browse/DEL-488
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
These images contain debug tools as the tcf-agent which are required to
perform SDK operations like run and debug.
https://jira.digi.com/browse/DEL-488
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* Do not hard-code the DISTRO* values and set them from the environment
* Move the build information to a different file (following commit)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The ADT installer compiled from "bitbake adt-installer" needs qemu images
available at adtrepo.yoctoproject.org/$VERSION. To avoid having to deploy
an adtrepo ourselves, we need to change the distro version to the upstream
version.
There are further problems with the ADT installation that need to change
the SDK_VENDOR to the poky default of pokysdk and to have the SDKPATH also
with the default value.
With this change the adt-installer is installed without errors.
https://jira.digi.com/browse/DEL-478
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
psplash utility is throwing errors on target's shutdown when using the
serial terminal as console. Override the psplash initscript configuration
so it only runs on target's boot.
https://jira.digi.com/browse/DEL-260
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The patches are specific to the package version, so move then to a
versioned folder and remove the version from the patch filenames.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There were two problems here:
* The 'vssconfig' files need to be removed so the displays are
auto-configured directly.
* Fix a problem with a missing library. The code tries to 'dlopen' a
shared library using the symbolic link instead of the soname. But the
symbolic link is only installed with the development package PN-dev,
so it's not available with the normal 'gst-fsl-plugin' package. Added
patch that fixes this problem.
https://jira.digi.com/browse/DEL-167
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This plugin is conflicting somehow with the other vorbis plugin throwing
some error messages when using gstreamer:
(gst-plugin-scanner:873): GLib-GObject-WARNING **: cannot register existing type `GstVorbisDec'
(gst-plugin-scanner:873): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(gst-plugin-scanner:873): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed
Disabling the plugin does remove the error messages with no
functionality loss (as we have the standard vorbis plugin)
https://jira.digi.com/browse/DEL-447
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This gives more time for the interfaces to resume.
This fixes a race condition where the script tries to bring up the
wireless interface before actually being available.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed for the ConnectCard for MX28 bluetooth variants.
It is created by mdev in del-image-minimal and udev needs to do it in
del-image-graphical.
We are appending to the 10-imx.rules file which already exists in
meta-fsl-arm.
https://jira.digi.com/browse/DEL-450
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The patch sent upstream (meta-fsl-arm) was acepted and integrated so
this change is no longer needed.
This reverts commit 7d7d7ee49c.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The default network manager included with the x11-sato packagegroup is
connman. It cannot coexist with ifup and /etc/network/interfaces. For
connman to work properly we would require:
- To modify netbase to leave an interfaces file with only the loopback
interface for graphical images.
- To compile the wpa_supplicant with dbus support and to leave connman the
task of starting it without a configuration file but with the dbus API (-u)
- We would need a way to run pre up scripts for all interfaces, so that the
wired interfaces can set the mac addresses passed by uboot and the wireless
interfaces can use the appropriate launch scripts.
Currently connman has no way to launch scripts before bringing an interface
up. It could be done with udev, but reportedly this does not work well
because sometimes connman brings the interface up before the udev rule is
run.
It may be that future versions of connman fix this, for example by
providing a command line tool.
For the moment it is easier to have no graphical network manager. That way
both del-image types share the network settings. In the future we may want
to revisit the need for a graphical network manager.
Fixes https://jira.digi.com/browse/DEL-387
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
If you don't want to use meta-digi-del and use only the BSP layer
(meta-digi-arm) to build a generic image (like core-image-minimal) you
need the DIGI_MIRROR variable in this layer because some of the BSP
recipes (kernel, u-boot) use it to get the source.
So this allows to build core-image-minimal for Digi platforms without
using meta-digi-del.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
nvram-dev package has a runtime dependence on libdigi:
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for nvram-dev:
* libdigi (= 1.0-del.r0) *
* opkg_install_cmd: Cannot install package nvram-dev.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
They contain the sha1s of the upstream poky, meta-fsl-arm and
meta-openembedded we are basing this drop on. These sha1s are also
included in the manifest file for the drop so they could safely be removed
from here once we are building release images on the Jenkins server.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Those packages are already runtime dependences of gst-fsl-plugin, so
there is no need to explictly add them here.
https://jira.digi.com/browse/DEL-162
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For MX5 machines, gst-fsl-plugin has build-time dependences on the
pre-built fsl-mm-mp3enc and fsl-mm-flv codec libraries.
If the mp3enc library is not in the sysroot, the 'libmfw_gst_mp3enc.so'
is not built.
If the fsl-mm-flv is not in the sysroot, the configure process warns
about:
"Unable to determine soname of lib_flv_parser_arm9_elinux.3.0.so library"
and the resulting 'aiur_registry.arm11.cf' gets a wrong entry for
flv_parser library.
Similar patch was sent upstream (meta-fsl-arm). Once upstream integrates
the patch, this commit should be reverted.
https://jira.digi.com/browse/DEL-162
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
So it gets installed in del-image-graphical and removable devices (like
MMC and micro SD) are automounted.
https://jira.digi.com/browse/DEL-159
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Running:
bitbake -c cleanall packagegroup-machine-base
was failing due to those trailing backslashes.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Reduce kernel console loglevel for all platforms.
* Protect DMA zone for MX5 platforms (for gstreamer/vpu)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Yocto v1.3 (Danny) does *not* have python-m2crypto-native support so
enabling VIRTUAL-RUNTIME_crda_use_gcrypt breaks the build.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Disable DEVCACHE to remove error message on boot.
https://jira.digi.com/browse/DEL-262 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Those symlinks point to files which belong to busybox-mdev package, so
at running time this adds a dependency to busybox package on
busybox-mdev package.
This is wrong for del-image-graphical where we want to use 'udev'
instead of 'mdev'.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It uses the nl80211 API which some drivers (like Redpine) do not support.
https://jira.digi.com/browse/DEL-164
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
When building an RPM based system, the linux kernel image was installed
after the netbase image so the /boot/config* file was not found.
Strangely that worked fine on IPK based systems.
Fixes https://jira.digi.com/browse/DEL-364
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
According to the poky reference manual, if a machine feature is not
included in the distro features it will not be supported.
Not convinced that works that way, but just in case I am adding all the
machine features to distro features. It shouldn't hurt.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
I have split the machine configuration in two:
-The module machine configuration include, for example ccimx53.inc
-The machine configuration (for example cimx53js.conf) which includes
the variant configuration.
This will allow for customers to create their own machine keeping the
module include file.
The variant can be configured in the local.conf file with a
MACHINE_VARIANT variable.
The variant names are made up of the interface initials as follows:
w: wifi
e: externel ethernel
b: bluetooth
1: 1-wire
a: accelerometer
g: GPU
v: VPU
128: 128MB RAM
4k: 1024MB NAND (only for MX51 JTAG flash)
For details regarding the supported variants, each machine configuration
file contains a comment with a variants table.
https://jira.digi.com/browse/DEL-330
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
An error appeared trying to setup a jenkins job to build yocto.
When using dettached repos for the different layers (as a result of
using 'repo' tool) bitbake somehow fails to parse 'base-files' recipe
because the branch of the layers is '(no branch)'.
The error message is:
ERROR: ExpansionError during parsing /data/jenkins/jobs/yocto_test/workspace/digi-yocto-sdk.jviguera_mkproject/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb: Failure expanding variable do_install: ShellSyntaxError: LexToken(TOKEN,'nobranch',0,0)
followed by:
LexToken(RPARENS,')',0,0)
LexToken(TOKEN,':34e5537e67b655b8d2effbbecc207d88eea52b87"\nmeta-fsl-arm = "',0,0)
LexToken(LPARENS,'(',0,0)
LexToken(TOKEN,'nobranch',0,0)
LexToken(RPARENS,')',0,0)
This commit fixes the problem.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
iw, Remove summary and leave description.
packagegroup-del-bluetooth, remove trailing line.
vsftpd,pointercal-xinput, add colon at the end of FILESEXTRAPATHS_prepend
del-examples-*, add COMPATIBLE_MACHINE to some examples
packagegroup-del-qt, remove comments.
https://jira.digi.com/browse/DEL-282
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Alex Gonzalez
Javier Viguera