There is no guarantee that a fix delay is actually enough, because with
the BT_EN gpio, we only control activation of bluetooth on the chip. But
we don't know the status of the whole chip.
Also hciattach has anyway a timeout of 5 seconds, so 0.1 seconds does
probably not make a big difference in this regard.
So in order to make it the safest possible, we can only rely a failure
handling and retrying. The number 5 for retries has been defined since
repeated restart of the service with only 3 retries leads to failure
pretty quickly. At 4 there is no failure anymore. So with 5 we are sure
the risk of failure is really low.
BugzID: 70195
This package contains gpioset, gpiofind, etc
This tools are required to access the gpios from shell scripts.
Also fixes the RDEPENDS ${PN}
BugzID: 65420
Name the BT_EN gpio in the device tree when you want to use this service.
It has to be found with the command: "gpiofind BT_EN".
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
The default behavior is to try to build u-boot-initial-env
Which is not implemented in our u-boot repo.
Part of yocto update to dunfell release.
BugzID: 69636
Afer upgrading meta-freescale to dunfell, the new default tune is
a35-crypto instead of aarch64.
Part of yocto update to dunfell release.
BugzID: 69636
system-state-framework: added recipes for the broker, extmod and
sysstate parts.
move include files to ${STAGING_KERNEL_BUILDDIR}/include/broker/
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
Co-authored-by: Ramon Moesching <ramon.moesching@netmodule.com>
Reviewed-on: https://git.netmodule.intranet/yoctoproject/meta-netmodule-bsp/pulls/70
The name to use is actually the name defined in the layer.conf of the
target layer and not the name of the directory itself (which can
actually change).
BugzID: 69469
It was already the case for HW18: eth2 was the default.
Now with HW25, we can't rely either on eth0 name since it is assigned by
default to the wrong port.
We are therefor using lan0 for HW25 and make the nm-conf recipe more
generic.
BugzID: 69468
nmhw21 and hw26 are using common u-boot code base.
Thus we are creating symlink from nmhw21 to hw26.
With this fix jenkins packaging stage is working again.
BugzID: 69325
Signed-off-by: Ramon Moesching <ramon.moesching@netmodule.com>
This patch is removing wlan config to use the backports instead. But the
backports are not compatible with other kernel than virtual/kernel.
We must therefor rely in the default wlan for the moment
BugzID: 69147
Changing KERNEL_PACKAGE_NAME allows this variant of the kernel to live
its own life in tmp/work/ instead of being shared in tmp/work-shared.
It is also not providing virtual/kernel.
This way, the "official" kernel (virtual/kernel) is never modified and
rebuilt, leading to strange behavior regarding deployed licenses.
BugzID: 69147
Since imx-boot is different than a classic u-boot we need to handle it
separatly. bootloader-config does not support it so we use this variable
to remove it at build time.
BugzID: 69098
In order to make the service start faster we make it less nice.
It will therefor have more cpu resources to setup the modem faster. The
overall goal being to have WWAN connectivity earlier during boot
process.
BugzID: 67742
Due typo and wrong usage bbappends were never applied to
meta-ublox-module layer.
BugzID 68069
Signed-off-by: Ramon Moesching <ramon.moesching@netmodule.com>
After changing the distro config to allow reproducible builds, a side
effect was that the date printed during uboot startup was 1 Jan 1970.
In order to get the real build date in uboot, we must unset the
SOURCE_DATE_EPOCH variable.
BugzID: 67738
The wifi and bluetooth chip ti wl18xx firmware files are handled by seperate
meta-netmodule-wlan layer.
BugzID: 67576
Signed-off-by: Ramon Moesching <ramon.moesching@netmodule.com>
Alexandre Bard
Lucien Mueller
Ramon Moesching