| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|