summaryrefslogtreecommitdiff
path: root/meta-inspur/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-12meta-inspur: honister: Compatible yocto releaseGeorge Liu1-1/+1
Latest upstream yocto has moved on to the 3.4 honister release. Compatible with honister for all inspur machines. Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I991415cb0db971d553eb374b7df8f634b00f4816
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
2021-01-22meta-inspur: add com/ibm to OBMC_ORG_YAML_SUBDIRSGeorge Liu1-0/+1
Since inspur/fp5280g2 machine built requires `xyz/openbmc_project`, `org/open_power` and `com/ibm`. 1. `xyz / openbmc_project` is built by default in phosphor-dbus-interfaces repo. 2. `org/open_power` has been added to `meta-openpower/conf/distro/include/openpower-distrovars.inc`. 3. Need to add the `com/ibm` to OBMC_ORG_YAML_SUBDIRS in the inspur layer and require it in fp5280g2.conf. Tested: Built fp5280g2 and ran successfully. (From meta-inspur rev: 8427a0acfa3a9b2b397e72808999db9bccdd428f) Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: Idbed3f012d7c754752757b7b75496b743efbb3aa Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-30meta-inspur: update Yocto compat for gatesgarthGeorge Liu1-1/+1
Since the current release of Yocto is gatesgarth, Add and support for gatesgarth(current) and dunsfell(previous) in meta-inspur layer. Also, remove the two earlier releases(warrior and zeus). Tested: Built successfully on fp5280g2 and on5263m5. (From meta-inspur rev: 831b68cce11da461122ee20ad371d93b60a245b1) Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I587a032a20bb645c452d16fbdc8adff3d35c965a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-05-06meta-inspur: layer.conf: add dunfell compatibilityGeorge Liu1-1/+1
Tested: Built successfully on fp5280g2 and on5263m5. (From meta-inspur rev: 9f97e52a7b7f5366732be3ffd73e08266f67dbb2) Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I55333bd59c44c6280ad54b07c164e74b5eb39a76 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-09-23meta-inspur: layer.conf: add zeus compatibilityJohn Wang1-1/+1
(From meta-inspur rev: de520bd0ba379715784a0060ca941c3c272d6054) Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I4e64add8166b48b3528473a1ef86fcde5c3dc550 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-16meta-inspur: Remove references to INSPURBASEBrad Bishop1-2/+0
INSPURBASE 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-inspur rev: 052786ad38fa172500a9f641ed26e95e25e6fbc6) Change-Id: I5394fc045042a30bdc958a6e528d9a7f947d49b9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05meta-inspur: Move recipes under meta-commonJohn Wang2-26/+3
Since meta-common is an x86 platform related meta, it would cause ambiguity if other platform related machines are created. In order to avoid ambiguity, recipses under meta-common are moved to meta-on5263m5, the meta-common folder is deleted. Tested: export TEMPLATECONF=meta-inspur/meta-on5263m5/conf source openbmc-env bitbake obmc-phosphor-image Build successfully (From meta-inspur rev: 295f5c5f6fbec43e8d5727e9a50dcba58e951cbd) Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: Iffacaf8131ec83362ec453a51818f6901f1f80e5 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-07meta-inspur: layer.conf: Add warrior compatibilityPatrick Venture1-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-inspur rev: ba5f0c7441a2ad1dd87fb1a3c37ae7ca6e66df34) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I99469a26e5cab061b07485a870692bfde220a0b1 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-30meta-inspur: Upgrade to yocoto 2.6John Wang1-1/+1
set layer compatability to thud (From meta-inspur rev: 63e6b51e20656647b7df03cdf4c6414934d993d3) Change-Id: Ia13c535f8aab24750aa3231b93521205cda3b1b2 Signed-off-by: John Wang <wangzqbj@inspur.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-12-13Add ON5263M5 platformJohn Wang2-0/+35
(From meta-inspur rev: 42e8cb80b7e8344ce9fb6ff0c40f81e0bdd03cbe) Change-Id: I8affa38b64d7db1f4826718983d049dea5ea2f26 Signed-off-by: John Wang <wangzqbj@inspur.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-29 05:10:06 +0300