summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/conf/layer.conf
Commit message (Collapse)AuthorAgeFilesLines
* layer.conf: Update to honisterRichard Purdie2021-07-291-1/+1
| | | | | | | | | 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>
* layer.conf: Update for hardknott release seriesRichard Purdie2021-03-151-1/+1
| | | | | | (From meta-yocto rev: f07f28224c9d3d1af5e7a63151da8ad4731fd1c5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "yocto-bsp: explicitly set preferred version for reference boards"Kevin Hao2021-01-131-6/+0
| | | | | | | | | | | | | | | | 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>
* yocto-bsp: explicitly set preferred version for reference boardsBruce Ashfield2021-01-051-0/+6
| | | | | | | | | | | | | 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>
* meta-poky/meta-yocto-bsp layer.conf: Move to depend on gatesgarth release ↵Richard Purdie2020-05-181-1/+1
| | | | | | | | codename (From meta-yocto rev: a6b17a67a7478fb6536eff388bfd30f058388fd5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to new dunfell release nameRichard Purdie2020-03-151-1/+1
| | | | | | (From meta-yocto rev: a1ae7e14edd36007adf027e21711f016e0f25658) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for zeus seriesRichard Purdie2019-10-081-1/+1
| | | | | | (From meta-yocto rev: 339de6c86cc93b24ed7faaa7012d0768c626a11c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to warrior release name seriesRichard Purdie2019-04-021-1/+1
| | | | | | (From meta-yocto rev: 85ed7ed9d3b34562b1df30e67aa0698facdb0dd5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update sumo->thud in preparation for releaseRichard Purdie2018-09-241-1/+1
| | | | | | (From meta-yocto rev: 2404cddc02b428fb510574b02707f7e0b68e31e8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie2018-04-061-1/+1
| | | | | | (From meta-yocto rev: db28e5c97895d2a25098aaac7f0a65d4f2a01866) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* beaglebone-yocto: rename beaglebone machine to beaglebone-yoctoJoshua Lock2017-11-111-1/+1
| | | | | | | | | | | | | | | | | 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>
* meta-yocto: Add LAYERSERIES_COMPAT markup to layer.confRichard Purdie2017-06-121-0/+1
| | | | | | | | | 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>
* meta-yocto-bsp: Bump layer version after the BSP changesRichard Purdie2014-03-311-1/+1
| | | | | | (From meta-yocto rev: e4369b7f9f5c5cb533dbaa40a1e8a88d79c2b2f1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Bumping LAYERVERSION_yoctobsp to account for atom-pcElizabeth Flanagan2013-08-271-1/+1
| | | | | | | | | | | | | | | | | 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>
* meta-yocto*/conf/layer.conf: tweak BBFILES commentsPaul Eggleton2013-04-101-1/+1
| | | | | | | | | | "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>
* layer.conf: avoid unnecessary early expansion with :=Christopher Larson2013-03-191-3/+3
| | | | | | | | | 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>
* meta-yocto: Split into distro and bsp componentsRichard Purdie2012-09-051-0/+11
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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-12 12:13:46 +0000