Mostly cosmetic changes to clear it a bit so customers can use it as
documentation for what variant they need to configure in their projects.
Also a couple of minor fixes: 'ext-eth' typo and duplicated 'e' variant
for ccimx53js.
https://jira.digi.com/browse/DEL-460
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to set MACHINE_VARIANT to the empty string:
MACHINE_VARIANT = ""
in the project's local.conf by running something like:
. /path/to/mkproject.sh -v "" -p <platform>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This manually reverts commit ecfdf6ae23.
Once mdev was removed as a dependency from del-image-graphical, we need
udev to load the firmware files for the wireless drivers. This job was
being done by mdev.
The reason for the commit in the first place was that both mdev and udev
were attempting to load the firmware files, so we changed the udev
rule to ignore the atheros driver. This was only needed when mdev and
udev were both running.
https://jira.digi.com/browse/DEL-450https://jira.digi.com/browse/DEL-450
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
This script is *sourced*, so we need to make sure that the variables
used do not collide with other variables that may be already in the
environment.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds basic support for platform variants. The script does
not make any sanity check on the variant name. It's user's
responsibility to use the correct variant for the platform.
https://jira.digi.com/browse/DEL-435
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>
The script in the root directory needs to be in sync with the 'master'
script in the 'meta-digi' layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Some examples need hardware to be plugged to the module (e.g. the
camera), and fail if the hardware is not there.
Signed-off-by: Javier Viguera <javier.viguera@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>
https://jira.digi.com/browse/DEL-331
While on it, fix whitespace problems (mixed tabs + spaces) in the
bitbake recipe.
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>
The previous "+=" format was doing a complete variable override instead
of an append. Features like usbhost or usbdevice were disappearing.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
Javier Viguera
Alex Gonzalez