Since the included files are in the same directory, it makes more sense
to include them relatively.
More specifically, it is a problem for ti33x.inc that exists in meta-ti
which is now used for hw34.
id:502637
Since we worked mainly on the ramdisk image, the test-image was almost
empty and lacking the minimum components.
This components are now defined in a packagegroup which is included in
all nwl-images.
It also include a new MACHINE_FEATURE : nrsw-ready.
This feature allows us to not include NRSW modules for devices that are
not supported by NRSW: for the moment it is mainly the devices supported
by core-os like cn9130-cf-pro. These devices are build against there
custom kernel against which the NRSW modules are not buildable.
id:458169
INFO: The image address entries in the fitImage changed
e.g. "fpga@1" -> "fpga-1"
see: commit 6047be9f8f0f5d616fda11d83b682c1b8aeaa0ae in meta-openembedded
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
The are several advantages to use the yocto recipe as base:
- The checkout of the git repo is done differently: it makes the
do_fetch task faster than it would be with the default behavior which
is to clone the entire repository.
- It is possible to share part of the build process by defining the
KMACHINE variable: All machines with the same KMACHINE value will
share (at least part of) the build environment, speeding up compile
time.
- It is possible to conditionally add configs through the
KERNEL_FEATURES variable, without needing to rebuild from scratch when
changing the features.
The new recipe also directly takes advantage of the KERNEL_FEATURES to
add support for init ram disks.
A another change happening with this commit is the kernel modules to
autoload being defined in a single file and (as the defconfig) depend on
the SOC_FAMILY variable (sitara or armada).
id:413752
Alexandre Bard
Lucien Mueller
Marcel Reichmuth