diff options
| author | Vernon Mauery <vernon.mauery@linux.intel.com> | 2019-03-22 22:25:14 +0300 |
|---|---|---|
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-04-29 23:02:39 +0300 |
| commit | 3313659bf25c9ad4d608282d088a1717977983e9 (patch) | |
| tree | a0ce9b2dac008bcf4ce1e467d223147d53916cbf /meta-openembedded/meta-python/recipes-devtools/python | |
| parent | d378c5e096c2e6e54d06bed5b5c273c218129256 (diff) | |
| download | openbmc-3313659bf25c9ad4d608282d088a1717977983e9.tar.xz | |
Make phosphor-ipmi-net parameterized per iface
The end goal is to run one netipmid bridge per interface, so that
stopping that bridge will effectively shut down RMCP+ to that interface.
Including this package (phosphor-ipmi-net) in a yocto build will
automatically enable RMCP+ on the default interface (eth0). To change
the default interface enabled, set the value in a bbappend:
RMCPP_IFACE = "eth2"
If more than one network device for RMCP+ is needed, then a bbappend
should be added to enable netipmid on that device using syntax like
as follows:
phosphor-ipmi-net_%.bbappend:
ALT_RMCPP_IFACE = "eth1"
SYSTEMD_SERVICE_${PN} += " \
${PN}@${ALT_RMCPP_IFACE}.service \
${PN}@${ALT_RMCPP_IFACE}.socket \
"
(From meta-phosphor rev: e46895beb45726a2154e66f30d5f41167014d127)
Change-Id: If856e938f5be95ca450bb4403d1c20ebcf11a7c6
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python')
0 files changed, 0 insertions, 0 deletions
