- The Bluetooth daemon was always executed before setting up the
hardware, generating several problems specifically in the CCIMX6SBC.
This was causing the Bluetooth driver to override the Bluetooth name
and alias, as well as avoiding any host function on Bluetooth profiles.
Only pairing and ping was working, as well as client profile sides.
- This change also fixes some issues in the CCIMX6UL platforms with the
Bluetooth daemon failing to perform several bluetoothctl operations.
https://jira.digi.com/browse/DEL-4000https://jira.digi.com/browse/DEL-4015
Signed-off-by: David Escalona <david.escalona@digi.com>
udhcpc's '-n' option means 'Exit if lease is not obtained'.
We want to keep udhcp client alive if lease is not obtained, so when it is
possible, an IP is assigned.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
The flash_eraseall busybox utility is not used in the ccimx6 and ccimx6ul
platforms. Its corresponding patch (and the library it depends on) can be
removed from the busybox recipe.
https://jira.digi.com/browse/DEL-1320
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resuming, causing issues on the wifi interface.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3694
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resumming, causing issues on the wifi interface.
https://jira.digi.com/browse/DEL-3431
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
Bringing the Bluetooth interface down and up during suspend
is not needed and it even showed problems on the Starter Board
where the Bluetooth interface does not come up again after
having been brought down in suspend.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3416https://jira.digi.com/browse/DEL-3081
Remove preventive delays during the removal of Bluetooth and Wireless
interfaces. Tests revealed they are not needed.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The loading of the wireless module without proper arguments does nothing.
Besides, if the interface was down before going to suspend, there is no
need for the wireless module to be loaded.
The wireless module will be loaded nevertheless (with proper arguments)
when the interface is brought up.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
The suspend script was unloading the wireless module driver *only* if the
interface 'wlan0' was previously up. If the interface is down the module
does not unload and the system fails to suspend.
This patch removes the module always if it appears in the list of loaded
modules.
While on it, move the unloading of wireless after the unloading of
Bluetooth, to be in line with the reversed order in which they are loaded
on the resume_interfaces() call.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
Down the bluetooth interface before entering suspend and up it after resuming
if it is present and up.
https://jira.digi.com/browse/DEL-2806
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Start syslog earlier (from 20 to 02) so it is running and other init scripts
can use it to log into the system like the S03networking script.
https://jira.digi.com/browse/DEL-2812
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
It has been observed that the wireless interface ocassionally fails to resume
from suspend on extensive long run validation testing, so we workaround it by
bringing the interface down before suspend and bring it up again after resume
This reverts commit a77cd1406d.
https://jira.digi.com/browse/DEL-2217
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
We switch to the way it works in Android, short press (<2s) takes the target
to suspend and long press, >2s but <9s, performs a software controlled
power down.
Pressing longer than 9 seconds does the uncontrolled hardware power off
directly from the PMIC.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The suspend script did a ifup/ifdown on wlan0 to workaround issues we
had using wireless drivers on some platforms.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Microcom is a minimal version of minicom and is extremely useful
for doing basic testing on target (for instance, talking to a modem
or other serial connected device).
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
(cherry picked from commit 90c6708e948c9b9942b48d425ff21e0affc2f8d7)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add the networking configuration to support the creation of a bridge
interface.
Signed-off-by: Jose Diaz de Grenu de Pedro Jose.DiazdeGrenudePedro@digi.com
* CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP to support 'connmand' for dhcp.
* CONFIG_CTTYHACK to make easier boot from an initramdisk.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By removing the driver on ifdown and loading it on ifup we workaround some
problems found in long run suspend stability testing.
https://jira.digi.com/browse/DEL-1084
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This was needed to overcome some corner cases with storage devices on
suspend/resume using MDEV as device handler.
Now we are using UDEV and after some tests done it seems that the
'resume_storage_devices' hack is not needed anymore.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
udhcpc's '-R' option means 'Release IP on exit'.
This fixes a strange corner case on reboot: if you configure your network
interface to DHCP in '/etc/network/interfaces' AND you have some NFS
share mounted on your system, then running reboot command fails to
complete and it hangs on:
'Unmounting local filesystem'
This happens because on reboot TERM and KILL signals are sent to all
the processes in the system before umounting the local filesystem. When
udhcpc daemon receives the signal it exits and releases the IP (because
it was launched with '-R') leaving an unconfigured network interface
that later is unable to umount a network filesystem (NFS), resulting on
'reboot' command being unable to complete.
Removing the '-R' option from udchpc allows to kill the process without
unconfiguring the network interface.
https://jira.digi.com/browse/DEL-1125
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The original defconfig came from DEL. Make the defconfig more similar to
the Yocto default one.
This restores the default udhcpc options when running via ifup to '-R
-n'. This is important because without '-n' the target can wait forever
to get an IP on boot while maybe the network is not available.
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>
So the output of 'reboot' command does not spread over different lines.
This is basically a cosmetic change to make target's output on reboot a
bit more beautiful.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We use udev as device manager both for minimal and graphical images so
there is no need for these mdev extensions anymore.
https://jira.digi.com/browse/DEL-944
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Some test applications (e.g. gpio_test) use static device nodes. This
commit adds a bootscript that creates such device nodes reading from a
config file.
https://jira.digi.com/browse/DEL-458
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In ccardimx28 depending on the kernel version the console is on 'ttyAM0'
or 'ttyAMA0'. Use the standard serial port name ttyS0 for login (through
inittab) and let the device handlers create the symlink to the correct
device.
This allows to boot the same rootfs regardless of the kernel version.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The acpid applet will run at startup and will listen for power input
events.
On arrival, it will timestamp the press event, wait for the release event
and decide whether to suspend or poweroff based on the time elapsed.
https://jira.digi.com/browse/DEL-34
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Allows to use '-c' parameter to 'stat' command.
This is needed in udev's automount script (next commit).
https://jira.digi.com/browse/DEL-511
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Reviewed-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
David Escalona
Tatiana Leon
Javier Viguera
Gabriel Valcazar
Mike Engel
Pedro Perez de Heredia
Hector Palacios
Isaac Hermida
Alex Gonzalez
Paul Osborne
Jose Diaz de Grenu de Pedro