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
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
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
hw23: Force wpa-supplicant and hostapd versions
meta-netmodule-wlan provides modified versions of these tools, but they
seem to not work properly on HW23. Since this HW is anyway not supported
in meta-netmodule-wlan, we force the usage of latest stable version.
BugzID: 77173
Co-authored-by: Patrick Zysset <patrick.zysset@netmodule.com>
Reviewed-on: https://git.netmodule.intranet/yoctoproject/meta-netmodule-bsp/pulls/111
Co-Authored-By: Alexandre Bard <alexandre.bard@netmodule.com>
Co-Committed-By: Alexandre Bard <alexandre.bard@netmodule.com>
With this change we are building the same kernel config for all
hardwares belonging to the same platform. The configs only differ from
one or two drivers which are enabled or not and they are anyway not
loaded as long as the devicetree is not matching.
But having only one config for several hardwares is reducing maintenance
(like enabling or disabling kernel security features) and also reducing
build time when building for different machines.
BugzID: 75223
ATM the system state framework only works properly if we have the da9063
with working ignition.
BugzID: 74987
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
This will bring pciutils automatically to all machines:
- all armada machines
- all am33x machines
- imx8 hw23
BugzID: 73589
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
and remove the machine feature on hw26 since it is derived from hw21
machine config.
BugzID: 73593
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
In order to pull in some chip specific firmware / drivers or tool there
are also one specific wifi feature per wifi chip:
- ath-wifi for atheros chips
- ti-wifi for TI chips
- ublox-wifi for u-blox chips
BugzID: 75593
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
This recipe lets us create a fitimage outside of the kernel recipe.
For this to work we need to create just the zImage from the standard
kernel recipe.
BugzID: 73616
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
The v2x firmware load script contained also the usb hub reset which
affects the GNSS modem. This means that the GNSS modem worked only
when the v2x recipe was enabled. But without firmware the v2x-service
fails at start-up which affects all other images except vcu.
Therefore the usb-hub reset part was extracted from the v2x firmware
load script so that we decouple those two functions. ZF/OM need a
failing v2x service when no firmware is loaded, thus the v2x service
was moved back to the vcu image (see meta-netmodule-om).
The systemd services v2x and gnss-init depend now on usb-hub-reset
whereas gnss-init additionally depends on v2x (if available).
BugzID: 72787
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
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
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
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
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>
The DLM board does not have V2X module. Therefor we must remove related
software components. These components will there be enabled by looking
at v2x in MACHINE_FEATURES.
BugzID: 66088
Instead of checking if we are building for an IMX target to include or
not the jody bbappends, we are now including them only when the ublox
meta-layer is present, which offer more scalability for futur HW design.
BugzID: 65947
wwan-config is a rework of ublox-gsm-config.
It is more generic and allows better extension and customization.
BugzID: 61873
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
The SERIAL_CONSOLES defaults to ttyS0 and
therefore a getty on ttyS0 is opened by systemd.
set USE_VT to 0 because we don't have virtual ttys.
BugzID: 61141
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
wlconf-bin is fetching from git repository with branch name which is
derivied from MACHINE variable.
wlconf-bin is used for ti wl18xx bt/wifi chip which use mainly used on
nmhw21 and similar boards. On imx8-nmhw23 we are using u-blox jody-w1.
Signed-off-by: Ramon Moesching <ramon.moesching@netmodule.com>
Alexandre Bard
Lucien Mueller
Marc Mattmueller
Ramon Moesching
Patrick Zysset