diff options
-rw-r--r-- | meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf | 2 | ||||
-rw-r--r-- | meta-ibm/meta-romulus/conf/local.conf.sample | 2 |
2 files changed, 3 insertions, 1 deletions
diff --git a/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf b/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf new file mode 100644 index 000000000..9a5920a66 --- /dev/null +++ b/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf @@ -0,0 +1,2 @@ +require conf/distro/openbmc-openpower.conf +require conf/distro/include/phosphor-isolation.inc diff --git a/meta-ibm/meta-romulus/conf/local.conf.sample b/meta-ibm/meta-romulus/conf/local.conf.sample index 7bad7cd82..83a3f9b22 100644 --- a/meta-ibm/meta-romulus/conf/local.conf.sample +++ b/meta-ibm/meta-romulus/conf/local.conf.sample @@ -63,7 +63,7 @@ MACHINE ??= "romulus" # Ultimately when creating custom policy, people will likely end up subclassing # these defaults. # -DISTRO ?= "openbmc-openpower" +DISTRO ?= "openbmc-romulus" # 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 |