History log of /openbmc/phosphor-net-ipmid/phosphor-ipmi-net@.socket (Results 1 – 2 of 2)
Revision Date Author Comments
# b601994f 05-Apr-2023 Andrew Geissler <geissonator@yahoo.com>

ipmi-net: ensure eth device present

Some OpenBMC systems may support a mix of eth0-only and eth0/eth1 ports
on their BMC device. In some cases, this support may be in a shared
flash image that suppo

ipmi-net: ensure eth device present

Some OpenBMC systems may support a mix of eth0-only and eth0/eth1 ports
on their BMC device. In some cases, this support may be in a shared
flash image that supports both systems.

For example, IBM is building a system under the "p10bmc" bitbake machine
that only has a single ethernet port, eth0, wired up on it. The system
is still utilizing an AST2600, but only wired eth0 out of the system for
cost purposes.

Since the "p10bmc" machine is a shared target there is no way to remove
services that assume eth1 is present during the build process. Instead,
rely on the fact that the device will be present in /sys/class/net/
if in fact the system supports the network device.

Tested:
- Verified that a p10bmc Rainier machine with 2 eth ports still ran
these units for both ports
- Verified that a p10bmc Bonnell machine with only eth0 ran these units
for eth0 but not eth1

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I7e9db01fe26a4195802db4dcccffb412fbbe4a86

show more ...


# d92bc324 15-Mar-2019 Vernon Mauery <vernon.mauery@linux.intel.com>

spawn one rmcpp bridge per interface

According to the new architecture, each bridge should be a separate
process, or at the very least, be attached on a separate D-Bus
connection wit

spawn one rmcpp bridge per interface

According to the new architecture, each bridge should be a separate
process, or at the very least, be attached on a separate D-Bus
connection with a well-known name that corresponds to the channel name.

This commit brings netipmid to a state where it can be launched as:
systemctl start phosphor-ipmi-net@eth0

with a parameterized unit file and socket file that binds the socket to
the interface specified. If not launched this way, it will by default be
bound to all interfaces.

This includes the new parameterized service and socket file and the
autoconf/automake magic to install them to the correct place.

Tested-by: launch netipmid via current unit file/socket file
launch netipmid via parameterize unit file/socket file

Change-Id: Ib202015fb560da269e535f11c0ac316b17f6c262
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>

show more ...