Remove obmc-openpower-* machine features
The openpower layer supports a usage pattern of building non
openpower systems with the openpower layer included in the layer
configuration (introduced with 008b81bb).
As a part of 008b81bb a number of distro and machine features
were added. As with MRW and UBI before it, these features
are distro policy and not machine features. As such remove the
machine features.
Additionally converge the three feature variants down to a single
openpower feature since there aren't any in-tree systems that don't
enable all three.
Add a distro override and fix up combined feature checks to use
this override instead for improved readability.
Add a new distro configuration that enables these features and
point all Openpower sample local.conf files to this new distro
config.
Tested: Built and validated Witherspoon, Palmetto images
Change-Id: Ifa3df61fbe1803f00c38956c265604ba91d7d127
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-openbmc-machines/meta-openpower/meta-ibm/meta-romulus/conf/local.conf.sample b/meta-openbmc-machines/meta-openpower/meta-ibm/meta-romulus/conf/local.conf.sample
index cfc3cef..b2b739f 100644
--- a/meta-openbmc-machines/meta-openpower/meta-ibm/meta-romulus/conf/local.conf.sample
+++ b/meta-openbmc-machines/meta-openpower/meta-ibm/meta-romulus/conf/local.conf.sample
@@ -63,7 +63,7 @@
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
-DISTRO ?= "openbmc-phosphor"
+DISTRO ?= "openbmc-openpower"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not