those files reside now in the repository itself, thus the recipe
needed to be adapted
BugzID: 75350
Signed-off-by: Marc Mattmueller <marc.mattmueller@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
The two "ifs" are covering cases where the fitImage is not used and we
don't support this case.
And as the Module.symvers comment says, this has been fixed upstream in
kernel.bbclass.
BugzID: 75220
Our u-boot-nm.inc was just a copy of an outdated u-boot.inc.
I now changed the u-boot-nm.inc file to be a common configuration file
for our u-boot recipes.
BugzID: 75187
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
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>
These values are out of date with the real kernel versions and may be
misleading. Since we have only one version of the kernel, we can remove
them and "git" will be used as default value.
BugzID: 74959
These symlinks were required for compatibility with NRSW u-boot.
Since we are now using fitimage, the name of the devicetree is not
relevant since it is directly part of the fitimage.
BugzID: 74958
Instead of rewriting the full fitimage_assemble, we can just append to
the part generating the kernel entry, therefore reducing the duplicated
code.
BugzID: 74530
With this approach, we just need to change a machine.conf file to add
advanced-gnss to machine_feature in machine.conf to enable gnss-mgr,
force gpsd to start with 115200 bitrate and to disable gpsd service
because it will be started by gnss-mgr.
BugzID: 74458
And also reduce the number of created artifacts and simplify do_deploy.
The rm commands are not required. bitbake is smart enough to remove the
old deployed artifacts of a recipe.
BugzID: 74357
Signed-off-by: Patrick Zysset <patrick.zysset@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>
Because we don't have the kernel class in the netmodule-fitimage recipe,
we have to add this line there.
Signed-off-by: Lucien Mueller <lucien.mueller@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>
Reason for reverting to originial state:
- adaption of the v2x-fw-load script
- re-introduction of the v2x recipe in all of our images
- no difference when wainting on USB disconnect event or directly
releaseing the gnss module from its reset
BTW: The original timeout of 50s can be explained as the SCU held a
delay of 40s until powering the v2x module. This delay shall be
removed in the next couple of days.
BugzID: 72787
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
we power cylce now the power of the v2x module hence it is no longer
needed.
BugzID: 72787
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
the v2x-fw-load script was refactored and ready now a config file. The v2x
recipe installs a v2x config file depending on a distro variable
V2X_ENABLE_FW_LOAD. Inthere it is possible to declare a parameter line like
'is-placeholder-firmware=true' to skip the firmware load in the v2x-fw-load
script. The skip includes also the detection of the DFU mode of the module.
These changes enables us to introduce the v2x package in all our images so
that the service doesn't fail anymore when we are using our placeholder
firmware.
BugzID: 72787
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
Lucien Mueller
Alexandre Bard
Marc Mattmueller
Stefan Eichenberger