The linux-yocto-dev kernel is 4.1 based and has the support needed to
enable the intel-quark bsp without additional patching
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Some modules in the KERNEL_MODULE_AUTOLOAD list were removed when including
the meta-intel layer. It turns out the problem happens due to using the +=
operator together with machine overrides. Using _append_machine fixes this.
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
Acked-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The SRCREV lines were removed in:
8b4ab82 intel-common: Remove SRCREVs from linux-yocto-dev
The LINUX_VERSION override should have been removed/commented at the
same time as it is of course directly tied to the SRCREV.
Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
BSP linux-yocto bbappend files should make all variable updates with
machine-specific overrides. As it stands, building qemux86 with
meta-intel in BBLAYERS will add uio and iwlwifi to
KERNEL_MODULES_AUTOLOAD. This corrects that.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
oecore/poky layer changed, needing replacement of all the module_autoload_*
recipe variables by the KERNEL_MODULE_AUTOLOAD variable.
This fixes these kind of buildtime errors coming from the meta-intel layer:
ERROR: KERNEL_MODULE_AUTOLOAD has replaced module_autoload_iwlwifi, please replace it!
Addresses bug:
[YOCTO #6460]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The default AUTOREV mechanism is thwarted by SRCREV overrides in
bbappends. -dev is intended to be built using AUTOREV unless overriden
by the user in local.conf or similar. Use the defaults in the bbappends.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
In the intel common kernel recipes, instead of corei7-64-intel-common,
intel-corei7-64-intel-common was specified as override. This was masking
the KMACHINE and KBRANCH variables defined in these recipes causing
unexpected build issues for kernels of BSPs like nuc.
Fixes bug:
[YOCTO #6123]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
The automatic SRCREV AUTOREV anonymous python in linux-yocto-dev.bb
will only trigger on the PREFERRED_PROVIDER_virtual/kernel being
linux-yocto-dev if it is set in local.conf, or a similar file parsed
prior to itself.
Since these two machines currently specify linux-yocto-dev in the
machine configuration, the AUTOREV doesn't trigger - and we do not want
AUTOREV specified in the recipe itself to avoid breakage in the event
of no network access.
This is a bizarre little corner case as machines typically do not
specify linux-yocto-dev. For the time being, fix the do_fetch failure by
specifying SRCREVs for the two intel-core* machines. Users who want
AUTOREV can specify THAT in their local.conf. This way it doesn't break
out of the box.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Remove all redundant linux-yocto recipes where the BSP is able to reuse
the intel-common version.
Update the common bbappends with the KERNEL_FEATURES and
module_autoload* statements from the consolidated bbappends.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The intel-core* BSPs now have their own BSP description in linux-yocto.
Update the recipe accordingly.
All the existing BSPs (with the exception of the emgd variants) are now
supported across these two BSPs.
For machines that derive from the intel-common-pkgarch, allow the
common linux-yocto-dev recipe to build for them by specifying $MACHINE
for the common machine overrides (core2-32-intel-common and
corei7-64-intel-common).
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Add a linux-yocto-dev bbappend to the common area for use by the two
upcoming new core2-32 and corei7-64 common BSPs.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
