For most of the overrides the order is not important since all overrides
are used.
But when using a file specific to a machine, only one override is used
and in this case the order is important: the last override matching is
used. So we must keep more specific overrides at the end.
id:366284
This override was useful in the past when we had a lot of features
defined directly using the machine name. But now it is not needed
anymore.
It is actually the source of problems when using specific files for both
hw24 and 25: Since the HW24 overrides was at the end, the files for it
were always used and the files for HW25 were ignored.
id:366284
The default APN configuration is only required for TOBY-L2. For LARA, it
is properly handled through the QMI interface.
For LARA the only supported profile is RMNET, so this is not
configurable.
tpID: #354963
LARA-L6 is using a QMI interface so we need to enable QMI and the
"generic" plugin.
Also we need to backport libqmi to have the version matching
ModemManager 1.14.
BugzID: 81947
Now all scenarios with a user module are covered:
- static setup with a user module will create a bridge with static IP
- dhcp setup with a user module will put a static IP on the UM and DHCP
on the main interface
BugzID: 81969
This is a setup required for the factory testing image: the user module
must be reachable from the CPU. And since the subnet of the fct ethernet
port and the subnet of the user module are the same, we must bridge them
together.
BugzID: 81969
This is the new VCU pro based on HW26 but which includes the user
module.
Because of this change, we cannot reuse HW21 nor HW26 machines.
BugzID: 81969
After discussion with the maintainers, the problem actually lies in the
kernel drivers where a dash is forbidden. But the da9063-hwmon driver
was using a deprecated function which was not checking the name.
BugzID: 81093
These two hardware have the ability to read out the wwan modem supply to
know when it is completely turned off.
This is abstracted to wwan-config through lmsensors rules.
BugzID: 80542
It is suspected that having this variable containing a local path is the
reason why when building from sstate, the kernel sometimes need to be
rebuild.
BugzID: 80858
Deploying directly the DEPLOY_DIR_IMAGE bypasses the shared state
mechanism implemented in the deploy class, leading to the image not
being properly deployed when building entirely from sstate.
BugzID: 80331
As explained in the comment, the start of this service may include some
power cycles of the modem and also the startup of ModemManager. All of
this may take longer than the default 90 seconds in some special cases.
This should anyway not be a problem since this service is self resilient
and can handle errors during startup.
BugzID: 80178
As for the kernel, we don't need to build them for every MACHINE and
will save some build time when building them only once per architecture.
BugzID: 80015
As explained in the comments, in yocto the kernel is expected to be
built for each MACHINE and not for each architecture as we do.
Therefor all tools related to kernel must also be adapted.
BugzID: 80015
These dependencies lead to a partial rebuild of the kernel when
switching machine, even where they are actually using the exact same
kernel sources and config.
BugzID: 80015
Instead of having one kernel recipe with two hashes, it makes more sense
and is easier to maintain two recipes with the same name but different
versions. The shared part is in an include file.
Each machine then chooses which version it wants to use with
PREFERRED_VERSION variable.
BugzID: 79987
It happens that a soft reset is failing and blocking the chip in a state
where it always times out. The only wait to get out of this is to hard
reset the bluetooth chip.
BugzID: 77171
Mr Jenkins
Alexandre Bard
Marc Mattmueller