summaryrefslogtreecommitdiff
path: root/meta-intel/conf
AgeCommit message (Collapse)AuthorFilesLines
2020-05-14meta-intel: Change layer compatibility to dunfellJames Feist1-1/+1
(From meta-intel rev: 7375df904a659ab4e634c5e2444b520710bfba38) Change-Id: I787add5ff159def5c5fc00cd7ce31b331bea7bdc Signed-off-by: James Feist <james.feist@linux.intel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-12-12meta-intel: Fix layer priorityJason M. Bills1-1/+2
After adding the rsyslog bbappend some changes were not applied because the meta-phosphor layer also has an rsyslog bbappend at a higher priority. This change makes meta-intel depend on meta-phosphor so that recipes here are treated with a higher priority. Tested: rsyslog.conf override from meta-intel is applied. (From meta-intel rev: 89efcbb081b11050f8532addd4521e17afede3d6) Change-Id: I6e40e12129118743ad019ff126bcb6c40960cb7c Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-26meta-intel: add intel suffix to recipesPatrick Venture1-0/+2
Add a suffix, "intel" to all common intel recipe changes. The suffix is defined in intel.inc, which is included already in the s2600wf machine conf and likely any platform including meta-intel. (From meta-intel rev: 4fc52d948f7549472683ae26a10d5c60abde1537) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I3561dc40115894d5aa6a08fe723bf214100daefa Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-26meta-intel: add zeus compatibilityJames Feist1-1/+1
(From meta-intel rev: afeaa26538a9859e2475b323cb9c94363c1c6b80) Change-Id: Icb50d99bab3d5ae3cebe8bc874a292c0bbe7e655 Signed-off-by: James Feist <james.feist@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-24meta-intel: Remove references to INTELBASEBrad Bishop1-3/+0
INTELBASE 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-intel rev: bbf062e439732ac0a9e62bdc02e7baab0967cae4) Change-Id: Ief59bb83ab71946dab61c04db7781ff9fd1b6e17 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-09meta-intel: 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-intel rev: 8a61b573a9f4586ba204fd38e71433575872e8aa) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ie818ed3781969761beaeb8aaccaedf43dd841dbc Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-10Intel: set layer compatibility to thudEd Tanous1-1/+1
(From meta-intel rev: 6cf746d64cbbcbec01548cf0dcaed89e58fde4b6) Change-Id: Ic9c51fe7dc4496abb42928d6fda871c32ca328bd Signed-off-by: Ed Tanous <ed.tanous@intel.com> Signed-off-by: James Feist <james.feist@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-09meta-intel: Add intel-dbus-interfacesYong Li1-0/+3
This recipe is used for Intel specific features and IPMI OEM commands. Tested By: bitbake intel-dbus-interfaces (From meta-intel rev: c5a33a96c6ae6eeaedc5d314c8497dc358eff589) Change-Id: I0ce1a37d271fbe43612c75308b02068426a12e0b Signed-off-by: Yong Li <yong.b.li@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-12-03Fix LAYERSERIES_COMPAT warning for meta-intel.Jia, Chunhui1-0/+1
Add LAYERSERIES_COMPAT_xx lines in layer.conf to specify OpenEmbedded-Core version that we are compatible with. (From meta-intel rev: 5a9067a52ea29df3d87779a7497d06f92ae2acc4) Change-Id: I4579ab6a031ccd48ca73610903a6f3a8a9af6a8c Signed-off-by: Jia, Chunhui <chunhui.jia@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-09Set correct obmc-host-ipmi-hw for s2600wfYong Li1-1/+1
s2600wf uses kcs instead of bt Tested By: With change change, the below bitbake message will disappear: NOTE: Multiple providers are available for runtime virtual-obmc-host-ipmi-hw (phosphor-ipmi-bt, phosphor-ipmi-hw-example, phosphor-ipmi-kcs) Consider defining a PREFERRED_RPROVIDER entry to match virtual-obmc-host-ipmi-hw (From meta-intel rev: e3e3d2eb0032639076f8a5ce758bbe5c95d21edb) Change-Id: Ie1c38af151c4953569bff1bd16b98221eb6652de Signed-off-by: Yong Li <yong.b.li@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley2-0/+31
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>