1OBMC_BMC_INSTANCES ?= "0" 2OBMC_CHASSIS_INSTANCES ?= "0" 3OBMC_CHECKSTOP_INSTANCES ?= "0" 4OBMC_FAN_INSTANCES ?= "" 5OBMC_HOST_INSTANCES ?= "0" 6OBMC_POWER_BUTTON_INSTANCES ?= "0" 7OBMC_POWER_INSTANCES ?= "0" 8OBMC_RESET_BUTTON_INSTANCES ?= "0" 9OBMC_WATCHDOG_INSTANCES ?= "0" 10 11# obmc-bmc-state-manager 12# 13# Provides an implementation of the xyz.openbmc_project.State.BMC 14# interface. 15VIRTUAL-RUNTIME_obmc-bmc-state-manager ?= "phosphor-state-manager-bmc" 16 17# obmc-chassis-state-manager 18# 19# Provides an implementation of the xyz.openbmc_project.State.Chassis 20# interface. 21VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "phosphor-state-manager-chassis" 22 23# obmc-host-state-manager 24# 25# Provides an implementation of the xyz.openbmc_project.State.Host 26# interface. 27VIRTUAL-RUNTIME_obmc-host-state-manager ?= "phosphor-state-manager-host" 28 29# obmc-discover-system-state 30# 31# Provides an implementation of phosphor-discover-system-state, which, if the 32# host is powered off, will check the current power policy and, if necessary, 33# power the host back on. 34VIRTUAL-RUNTIME_obmc-discover-system-state ?= "phosphor-state-manager-discover" 35 36# obmc-fan-presence 37# 38# Provides implementations of fan presence detection 39VIRTUAL-RUNTIME_obmc-fan-presence ?= "phosphor-fan-presence-tach" 40 41# obmc-fan-control 42# 43# Provides implementations of fan control 44VIRTUAL-RUNTIME_obmc-fan-control ?= "phosphor-fan-control" 45 46# obmc-inventory-manager 47# 48# Provides an implementation of the xyz.openbmc_project.Inventory.Manager 49# interface. 50VIRTUAL-RUNTIME_obmc-inventory-manager ?= "phosphor-inventory-manager" 51 52# obmc-led-manager 53# 54# Provides an implementation of the xyz.openbmc_project.ledmanager interface. 55VIRTUAL-RUNTIME_obmc-leds-manager ?= "phosphor-led-manager" 56 57# obmc-led-monitor 58# 59# Provides an implementation of the FRU fault monitor. 60VIRTUAL-RUNTIME_obmc-led-monitor ?= "phosphor-led-manager-faultmonitor" 61 62# obmc-led-sysfs 63# 64# Provides an implementation of xyz.openbmc_project.Led.Physical for 65# Linux kernel LED subsystem LEDs. 66VIRTUAL-RUNTIME_obmc-leds-sysfs ?= "phosphor-led-sysfs" 67 68# obmc-bmc-download-mgr 69# 70# Provides an implementation of the xyz.openbmc_project.Common.TFTP 71# interface. 72VIRTUAL-RUNTIME_obmc-bmc-download-mgr ?= "phosphor-software-manager-download-mgr" 73 74# obmc-bmc-version 75# 76# Provides an implementation of the xyz.openbmc_project.Software.Version 77# interface. 78VIRTUAL-RUNTIME_obmc-bmc-version ?= "phosphor-software-manager-version" 79 80# obmc-bmc-updater 81# 82# Provides an implementation of the xyz.openbmc_project.Software.Activation 83# interface. 84VIRTUAL-RUNTIME_obmc-bmc-updater ?= "phosphor-software-manager-updater" 85 86# obmc-sensors-hwmon 87# 88# Provides an implementation of xyz.openbmc_project.Sensor.Value 89# for hwmon sensors. 90VIRTUAL-RUNTIME_obmc-sensors-hwmon ?= "phosphor-hwmon" 91 92# obmc-dump-manager 93# Provide support for managing dump 94VIRTUAL-RUNTIME_obmc-dump-manager ?= "phosphor-debug-collector-manager" 95 96# obmc-dump-monitor 97# Provide support for monitoring BMC core dumps 98VIRTUAL-RUNTIME_obmc-dump-monitor ?= "phosphor-debug-collector-monitor" 99 100PREFERRED_PROVIDER_virtual/obmc-system-mgmt ??= "obmc-phosphor-sysd" 101 102# phosphor-hwmon-config 103# 104# The phosphor-hwmon package can have its configuration generated 105# automatically if the MRW feature is enabled. 106VIRTUAL-RUNTIME_phosphor-hwmon-config ?= "" 107 108# obmc-network-manager 109# 110# Provide support for managing network 111VIRTUAL-RUNTIME_obmc-network-manager ?= "phosphor-network" 112 113# Configuration overrides for phosphor-ipmi-fru. 114# 115# The phosphor-ipmi-fru application is data-driven and requires an input 116# mapping of how the host firmware reports inventory via IPMI and the mapping 117# of that inventory metadata to DBus objects interfaces and properties. 118 119# The phosphor-ipmi-fru application is data-driven and requires an input 120# mapping of how the host firmware reports inventory via IPMI. 121# This virtual is a native recipe that provides that mapping by installing 122# configuration files in the format and native sysroot location expected by 123# the phosphor-ipmi-fru build process. 124PREFERRED_PROVIDER_virtual/phosphor-ipmi-fru-hostfw-config ?= "phosphor-ipmi-fru-hostfw-config-example-native" 125 126# The phosphor-ipmi-fru application is data-driven and requires an input 127# mapping of IPMI inventory metadata to DBus objects interfaces and properties. 128# This virtual is a native recipe that provides that mapping by installing 129# configuration files in the format and native sysroot location expected by 130# the phosphor-ipmi-fru build process in the native sysroot. 131PREFERRED_PROVIDER_virtual/phosphor-ipmi-fru-inventory ?= \ 132 "phosphor-ipmi-fru-inventory-example-native" 133 134PREFERRED_PROVIDER_virtual/phosphor-ipmi-fru-properties ?= \ 135 "phosphor-ipmi-fru-properties-native" 136 137PREFERRED_PROVIDER_virtual/phosphor-ipmi-fru-read-inventory ?= \ 138 "phosphor-ipmi-fru-read-inventory-example-native" 139 140# Configuration overrides for phosphor-host-ipmid. 141# 142# The phosphor-host-ipmid application is data-driven. 143 144# The phosphor-host-ipmid application is data-driven and requires an input 145# mapping of IPMI inventory sensor metadata to DBus objects interfaces and properties. 146# This virtual is a native recipe that provides that mapping by installing 147# configuration files in the format and native sysroot location expected by 148# the phosphor-host-ipmid build process in the native sysroot. 149PREFERRED_PROVIDER_virtual/phosphor-ipmi-sensor-inventory ?= \ 150 "phosphor-ipmi-sensor-inventory-native" 151 152# The phosphor-host-ipmid application is data-driven and requires an input 153# mapping of inventory object path to the sensor number and sensor metadata. 154# This virtual is a native recipe that provides that mapping by installing 155# configuration files in the format and native sysroot location expected by 156# the phosphor-host-ipmid build process in the native sysroot. 157PREFERRED_PROVIDER_virtual/phosphor-ipmi-inventory-sel ?= \ 158 "phosphor-ipmi-inventory-sel-native" 159 160# Various other overrides. 161 162# The phosphor-led-manager application is data-driven and requires an input 163# yaml of LED group and members. 164# This virtual is a native recipe that provides that mapping by installing 165# configuration files in the format and native sysroot location expected by 166# the phosphor-led-manager build process in the native sysroot. 167PREFERRED_PROVIDER_virtual/phosphor-led-manager-config-native ?= \ 168 "phosphor-led-manager-config-example-native" 169 170# The phosphor-logging application has a data driven plugin that adds FRU 171# callout information to error logs, when applications generating error logs 172# add the requisite callout metadata to the systemd journal. The plugin requires 173# an input mapping of Linux sysfs devices to OpenBMC DBus objects. 174# This virtual is a native recipe that provides that mapping by installing 175# configuration files in the format and native sysroot location expected by 176# the phosphor-logging build process in the native sysroot. 177PREFERRED_PROVIDER_virtual/phosphor-logging-callouts ?= \ 178 "phosphor-logging-callouts-example-native" 179 180# The phosphor-fan-presence application is data driven and requires an input 181# YAML that maps fans to their tach sensors. This virtual is a recipe that 182# provides that mapping by installing configuration files in the format and 183# sysroot location expected by the phosphor-fan-presence build process in the 184# sysroot. 185PREFERRED_PROVIDER_virtual/phosphor-fan-presence-config ?= \ 186 "phosphor-fan-presence-config" 187 188# The phosphor-fan-control application is data driven and requires a YAML file 189# to define the fans in the system. This virtual is a recipe that provides 190# that definition by installing the YAML file in the format and sysroot 191# location expected by the phosphor-fan-control build process in the sysroot. 192PREFERRED_PROVIDER_virtual/phosphor-fan-control-fan-config ?= \ 193 "phosphor-fan-control-fan-config" 194 195# The phosphor-gpio-monitor application is data-driven and requires an input. 196# The application then watches the passed in input event entry for the 197# change in polarity for the value matching user input. Once the required 198# condition is met, it calls into a systemd target file if one is mentioned 199# in input. 200PREFERRED_PROVIDER_virtual/obmc-gpio-monitor ?= "phosphor-gpio-monitor" 201 202# The phosphor-watchdog application is data-driven and requires an input. 203# The application then starts a timer in disabled state. User of this timer 204# needs to first enable and then use it. This also provides a way for changing 205# the timeout if needed. 206PREFERRED_PROVIDER_virtual/obmc-watchdog ?= "phosphor-watchdog" 207 208# obmc-user-mgmt 209# 210# Provides an implementation of xyz.openbmc_project.User.Manager catering 211# to user management 212VIRTUAL-RUNTIME_obmc-user-mgmt ?= "phosphor-user-manager" 213 214OBMC_DBUS_PATH_ROOT ?= "/xyz/openbmc_project" 215OBMC_DBUS_IFACE_ROOT ?= "xyz.openbmc_project" 216 217# VIRTUAL-RUNTIME_phosphor-ipmi-providers are the set of shared library 218# plugins for the host-ipmid application. By default the IPMI FRU plugin 219# is enabled. Additionally the host-ipmid recipe uses 220# VIRTUAL-RUNTIME_phosphor-ipmi-providers to compute a list of potential 221# IPMI whitelist recipe dependencies. For example: 222# 223# VIRTUAL-RUNTIME_phosphor-ipmi-providers ?= "phosphor-ipmi-fru" 224# 225# Will add a build dependency to host-ipmid on the 226# phosphor-ipmi-fru-whitelist-native recipe. 227VIRTUAL-RUNTIME_phosphor-ipmi-providers ?= "phosphor-ipmi-fru" 228 229# Set security headers on builds 230require conf/distro/include/security_flags.inc 231 232# Disable security on croserver. 233# Remove if https://github.com/open-power/eCMD/pull/433 is ever merged 234SECURITY_STRINGFORMAT_pn-croserver = "" 235# obmc-libobmc-intf doesn't compile with security flags enabled 236SECURITY_CFLAGS_pn-obmc-libobmc-intf = "" 237 238# remove when https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/39984 239# is merged and rev bumped 240SECURITY_CFLAGS_pn-pldm = "" 241 242# We generally want to enable LTO with meson 243EXTRA_OEMESON_append_class-target = " -Db_lto=true" 244 245# Set the root password to '0penBmc' 246inherit extrausers 247 248EXTRA_USERS_PARAMS_pn-obmc-phosphor-image = " \ 249 usermod -p '\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/' root; \ 250 " 251