This is needed for package post installation scripts to run their
second stage in the target.
For this to happen we also need to remove the "remove_packaging_data_files"
from the rootfs post process commands.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Also enable CONFIG_BRIDGE in kernel configs (which is required to use
brctl)
https://jira.digi.com/browse/DEL-156 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Enable RFKILL. Otherwise on boot we get an error message:
rfkill: Cannot open RFKILL control device
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
We need the kernel configuration file in /boot for some of the postint
scripts that aim to do smart things like autoconfigure the 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>
The bootloader is passing the mac address and wdmode in the kernel command
line.
The driver startup script reads and and sets them.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The bootloader is passing the mac address in the kernel command line.
The driver startup script reads it and sets it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Seems that the options Yocto was using to generate the jffs flash image
are not correct for ccardxmx28js. Specially mkfs.jffs2's padding option
'-p' was making the rootfs corrupted on second boot (as explained in
JIRA DEL-218).
Finally i decided to use the same mkfs.jffs2 parameters we were using in
DEL and those seems to be working fine.
https://jira.digi.com/browse/DEL-218 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These new defconfigs are needed after merging the wireless and non wireless
products in the linux kernel source.
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>
U-Boot has a set of pre-defined make targets per platform that allow
to configure u-boot for different variants (128sdram,4Kpage,dbg etc.)
This change allows to use a UBOOT_CONFIG_VARIANT variable in your
local.conf file to choose which variant to build.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCard needs a bootstreamed (.sb) u-boot to boot from flash. This
is flashed using u-boot.
This changes compiles a bootstream u-boot image. The bootlets are compiled
separately and it's U-Boot's Makefile that calls elftosb to generate the
final bootstream.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
Javier Viguera
Alex Gonzalez