| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The flow of synchronization targets during a obmc-host-stop@.target is
the following:
obmc-host-stop-pre -> obmc-host-stopping -> obmc-host-stopped
The obmc-host-stop-pre is where we notify the host that a shutdown is
occurring and allow it to gracefully shut itself down. This is where
xyz.openbmc_project.Ipmi.Internal.SoftPowerOff.service should run.
(From meta-phosphor rev: 7290bebb60ee03ff649c04fd430bb4dbef979fe9)
Change-Id: Ib3dd748e73b0d4a056d508caabe6c9c2351b5ab8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
OpenBMC has two implementations of the soft off function. This function
is utilized to tell the host to shutdown gracefully and for the BMC to
wait for that shutdown.
The implementation used depends on the interface being used to talk
with the host. There is the IPMI based interface and the new PLDM based
interface.
In theory, only one of these interfaces should be used to talk with the
host on a system. In reality there are some systems such as rainier
which are in the process of switching from IPMI to PLDM. In this case
both services for soft off are installed into the image.
Since this co-existence of both packages on a single system is a
temporary situation, put a simple change in which ensures the IPMI soft
off service does not run if the PLDM one is present. The assumption here
is that if the newer PLDM based package is installed, the system owner
prefers the PLDM soft off service be utilized.
(From meta-phosphor rev: 4c6e2c14a957111a7875eb03abb3121fab61f073)
Change-Id: If843f578590b99a90e53116f8cefc4065332e999
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
