Prepare for the scarthgap release.
(From meta-yocto rev: 5be4f867a3fba39103a569eb4ecf10c39eca3742)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This marks the layers as compatible with honister now they use the new override
syntax.
(From meta-yocto rev: ea637ebd5a79e5d023bbf347d633568bcb7506a2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit da27ca50eebf80463cb8d7b85f3b705254823413.
We usually select the preferred kernel version in the machine conf. This
is also what recommend in the BSP Developer's Guide. The beaglebone-yocto
and edgerouter have already done this in their machine conf files.
Resetting it in the layer conf is redundant. So revert this patch first,
we will also explicitly select the kernel version for the x86 machines
in the following patch.
(From meta-yocto rev: 825645ff2b663ae5c5845e8ae4679f6e346eac8c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When we are bumping the default kernel version for the qemu*
reference boards, but before the h/w reference boards have been
updated, we need to explicitly set the default kernel version
for those boards. Otherwise, we'll end up with warnings about
preferred versions of kernel modules not being available
(From meta-yocto rev: da27ca50eebf80463cb8d7b85f3b705254823413)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The beaglebone BSP provided in this layer is a reference implementation
usingonly mainline components available in core Yocto Project layers,
whereas Texas Instruments maintain a full-featured BSP in the meta-ti
layer.
Rename the reference machine to prevent namespace collisions with the
version maintained by the SoC vendor.
[YOCTO #12326]
(From meta-yocto rev: e32882938eca7f50548deab84dab78b4aef31b95)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested.
(From meta-yocto rev: ca35ea46708e0514e4d5a20950880be0bf1d4147)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to maintain autobuilder compatibility with prior releases
we'll need to decide on if we should build atom-pc or genericx86
based on LAYERVERSION_yoctobsp.
if LAYERVERSION_yoctobsp < 2 we build out atom-pc else
we build out genericx86
(From meta-yocto rev: 775ed00b9248c780e4c0e6768c439e4ebb65d9ed)
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Cc: Ross Burton <ross.burton@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
"packages" was the old name (pre-2010) under which the recipe files were
stored.
(From meta-yocto rev: b8c2e0207147105093bf6aa9beb340d4422cfb42)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake handles immediate expansions of LAYERDIR for us automatically.
(From meta-yocto rev: ee59f1ec94ba8474876603dad1ab32d131227f49)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now we have settled on best practises and compliance criteria, bring meta-yocto
into compliance by separating out the hardware support components into
meta-yocto-bsp leaving policy configuration in meta-yocto.
Also rename the meta-yocto scripts directory to OE-Core can be a clearly
isolated component in poky.
(From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie
Kevin Hao
Bruce Ashfield
Joshua Lock
Elizabeth Flanagan
Paul Eggleton
Christopher Larson