summaryrefslogtreecommitdiff
path: root/meta-ingrasys/conf/layer.conf
AgeCommit message (Collapse)AuthorFilesLines
2021-08-24treewide: remove gategarth from layer-supportPatrick Williams1-1/+1
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current and the upcoming. Remove 'gatesgarth' is it is now 2 releases back. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
2021-08-11meta-ingrasys: meta-zaius: Cleanup for Yocto override syntax changeBrandon Kim1-1/+1
Cleanup with ``` convert-overrides.py meta-ingrasys git grep -l _zaius -- meta-ingrasys \ | xargs sed -i 's/_zaius/:zaius/' ``` After cleanup ``` $ git grep "_[a-z0-9_/-]*[ :]" -- meta-ingrasys | grep '.bb' meta-ingrasys/meta-zaius/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend:# compose_list is not defined immediately so don't use := ``` Signed-off-by: Brandon Kim <brandonkim@google.com> Change-Id: Ib2da97530167688313ac16aedd69168137788c86
2021-04-06hardknott: yocto releaseAndrew Geissler1-1/+1
Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
2020-11-06meta-ingrasys: update Yocto compat for gatesgarthPatrick Williams1-1/+1
The next release of Yocto is soon and most of the upstream layers have switched support strings for it. Support layer compat for gatesgarth (current) and dunsfell (previous). (From meta-ingrasys rev: 52368129e9b624f9acd98c6156ea7a5d6d21ba4f) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: If78b0ef8b9db95b8af2254d4b299a6c28e262044 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-16dunfell: add support for new layerAndrew Geissler1-1/+1
(From meta-ingrasys rev: f6f1bf099107971f737a87b8fd4f85fadc0a3e78) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: If877cad79cb8f581c1b28e012837402e5e73d956 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-09-20meta-ingrasys: layer.conf: add zeus compatibilityPatrick Venture1-1/+1
OE-core master will be dropping warrior soon; zeus is the next release. (From meta-ingrasys rev: 9e946a348a50d439bbacafaf4f27f9910983d23b) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I302038aaab5a120587e734bc1c8bbf30d93cbe20 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-18meta-ingrasys: Remove references to INGRASYSBASEBrad Bishop1-3/+0
INGRASYSBASE is only used for pointing at licenses...point at the licenses in oe-core in meta/files/common-licenses instead. to match the defacto convention used in other oe layers like meta-openembedded. (From meta-ingrasys rev: fcd2b2998a76f00307bb2ff821efa8ff8ef87c68) Change-Id: I76d73574778db36a649f20ccc0a5149f616743af Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-09meta-ingrasys: layer.conf: set BBFILE_PATTERNPatrick Venture1-1/+1
Bitbake uses this regex to associate recipes and bbappends from BBFILES (which contains recipes and bbappends from -all- layers listed in bblayers.conf) to this layer. The association is then used to map the BBFILE_PRIORITY value for this layer onto the recipes provided by this layer. BBFILE_PRIORITY is used to determine which recipe to use when the same recipe appears in multiple layers. Without BBFILE_PATTERN set, recipes in this layer will get a default priority and not the priority specified in BBFILE_PRIORITY. This layer doesn't set a priority anyway, so functionally this patch is a noop but it is an improvement from a correctness standpoint, and it makes a warning go away. (From meta-ingrasys rev: 7a286ca0dba71a6ef309ff031cafc06e2c00cb8d) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: If0d38267efdf74a6d010278b5604ac517f4487da Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-05meta-ingrasys: layer.conf: Add warrior compatibilityBrad Bishop1-1/+1
oe-core branched in preparation for the upcoming 2.7 Yocto release and as of 13e45ff requires core layer compatibility to "warrior" instead of "thud". We'll retain compatibility for both until we do our own branch or stop testing thud. (From meta-ingrasys rev: bc513127f473da3cdadf59f4836043e8dbf2e3bf) Change-Id: Ic35d93d2d24506a9a8f50bda9f5f76af0c97208b Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-09reset upstream subtrees to yocto 2.6Brad Bishop1-1/+1
Reset the following subtrees on thud HEAD: poky: 87e3a9739d meta-openembedded: 6094ae18c8 meta-security: 31dc4e7532 meta-raspberrypi: a48743dc36 meta-xilinx: c42016e2e6 Also re-apply backports that didn't make it into thud: poky: 17726d0 systemd-systemctl-native: handle Install wildcards meta-openembedded: 4321a5d libtinyxml2: update to 7.0.1 042f0a3 libcereal: Add native and nativesdk classes e23284f libcereal: Allow empty package 030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG 179a1b9 gtest: update to 1.8.1 Squashed OpenBMC subtree compatibility updates: meta-aspeed: Brad Bishop (1): aspeed: add yocto 2.6 compatibility meta-ibm: Brad Bishop (1): ibm: prepare for yocto 2.6 meta-ingrasys: Brad Bishop (1): ingrasys: set layer compatibility to yocto 2.6 meta-openpower: Brad Bishop (1): openpower: set layer compatibility to yocto 2.6 meta-phosphor: Brad Bishop (3): phosphor: set layer compatibility to thud phosphor: libgpg-error: drop patches phosphor: react to fitimage artifact rename Ed Tanous (4): Dropbear: upgrade options for latest upgrade yocto2.6: update openssl options busybox: remove upstream watchdog patch systemd: Rebase CONFIG_CGROUP_BPF patch Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-08meta-ingrasys: master refresh 94d26b9f7d..c5f9312e58Brad Bishop1-0/+3
Update meta-ingrasys to master HEAD. Patrick Venture (5): meta-ingrasys: add INGRASYSBASE meta-ingrasys: zaius: ipmi-inventory-map-native: set LICENSE field meta-ingrasys: zaius: chassis: avsbus-control: set LICENSE field meta-ingrasys: zaius: chassis: refclock-fixup: set LICENSE field meta-ingrasys: zaius: chassis: vcs-control: set LICENSE field Change-Id: I58d8793a08e2e8333ccc4f71608365dec0ff8a8e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley1-0/+6
The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>