This fixes 'update_flash' related problems.
update_flash needs to know in which platform is running so it can decide
whether to write clean-markers for JFFS2 images or not (for example in
FSL platforms).
https://jira.digi.com/browse/DEL-221 #resolve
https://jira.digi.com/browse/DEL-222 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
While on busybox' init you can reboot the system sending a TERM signal
to pid '1' it seems that in sysvinit package this does not work, so
implement a proper reboot using the system call.
https://jira.digi.com/browse/DEL-212 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The interfaces file is different depending on whether we have single
or dual wired ethernet and whether we have a wireless or non wireless
module.
Also, add an ifup script to set the mac addresses fetched from the
kernel command line.
This commit autogenerates the /etc/network/interfaces file.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The bootloader is passing the mac address in the kernel command line.
The bluetooth startup script reads it and sets it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
With latest changes in bitbake (post-danny), crda recipe was giving
following error:
ERROR: There is a confusing multiline, partially commented expression
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This fixes 'out-of-range' errors:
~ # [ "2173165883" -eq "2173165883" ] && echo "TRUE"
sh: 2173165883: out of range
https://jira.digi.com/browse/DEL-207 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add custom /etc/init.d/networking and /etc/network/interfaces.
The networking script does the start section on the background which
inlcudes the bringing up of the interfaces. In this way DHCP does not
delay the boot up.
The interfaces file configures the wireless interface to be automatically
brought up.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This package contains firmware files for the MXS Digi family (Embedded and
boxed products).
Now it contains the bluetooth binary firmware files.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
It will be included in all machines that include the bluetooth feature,
currently the ccardxmx28js.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
There is no need to explicitly set PACKAGES variable (it is
automatically handled by packagegroup.bbclass)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If we override the variable with '=' instead of '+=' then extra image
features set in project's local.conf (EXTRA_IMAGE_FEATURES variable) are
discarded.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We use microwindows for the fbtest application. The recipe is imported
from openembedded classic and modified to work in yocto.
The configuration file has been modified to match the one in DEL legacy.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is based on the recipe found in the openembedded layer.
http://cgit.openembedded.org/openembedded/log/recipes/crda/crda_1.1.1.bb
It needs to compile with libnl 2.0, so we set a distro preferred version
for it.
Also, we make the recipe configurable to compile without gcrypt. The
Makefile is patched to compile without gcrypt.
Compiling with gcrypt would need the addition of the python-m2crypto-native
recipe which is not done so it is currently broken.
The compilation without gcrypt is how DEL is currently doing it so this
should be enough for our needs.
Also, the device manager is configurable and set to busybox-mdev by
default.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
We have been using ${PN}-${PV}, change to use only the package name and
leave ${PN}-${PV} for actual recipes.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This included the recipe where the driver is cloned from git and compiled
from source.
The recipe also copies the firmware files and the if-pre-up scrip.
Pending is the recipe to link from precompiled objects in a .tar.gz file.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>