summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-core/systemd/obmc-targets
AgeCommit message (Collapse)AuthorFilesLines
2023-02-14meta-phosphor: mapper cleanupsBrad Bishop1-4/+0
Mapper ships with systemd unit and dbus configuration files now, so remove unnecessary bitbake classes. Mapper is dbus-activated, so obmc-mapper.target dependencies are redundant and no longer necessary. obmc-mapper.target is the last target in obmc-targets, so remove that recipe and any dependencies on it. Change-Id: I59ff8dcd480b4449d0ef59422ba80c12848dade9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2021-07-18Install obmc-mapper.target from obmc-targets packageLei YU1-0/+4
The obmc-mapper.target was installed by phosphor-state-manager package. It works fine if phosphor-state-manager is installed. Unfortunately, x86 systems typically uses x86-power-control instead of phosphor-state-manager to implement the state manager, and the obmc-mapper.target is missing there. So a system with x86-power-control does not have a valid obmc-mapper.target, and the services depdend on the target will be started in unexpected order. The obmc-mapper.target is really a common target, let obmc-targets.bb install it. Tested: Verify the g220a build has a valid obmc-mapper.target and the phosphor-virtual-sensor service starts after the target. Also verify the targets in phosphor-state-manager are not installed. Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: Idb069385a6c6c7add5331a1bf3efc0babc005d62
2020-02-10move state systemd files to phosphor-state-managerAndrew Geissler33-234/+0
The OpenBMC target and service systemd files have been moved to phosphor-state-manager. This commit will move to those changes and delete the files from meta-phosphor. Bump Details: phosphor-state-manager: srcrev bump 4640d48e99..c101157e5b Andrew Geissler (3): move state manager service files into its repo ensure reboot service runs after host stopped move openbmc targets into this repo Tested: - Verified data files and services were all in expected location within witherspoon QEMU run - Verified openbmc systemd target were all in expected location within witherspoon QEMU run - HW CI will verify targets are still working as expected (From meta-phosphor rev: 77cfb0f54a23c3efeba26100110e54055accd16d) Change-Id: If5048f63d07ce45b4bc1f2303d1e87275324a818 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-22meta-phosphor: drop obmc-standby systemd targetPatrick Venture1-9/+0
The obmc-standby.target is no longer used, and therefore should be dropped. (From meta-phosphor rev: 381e36eb42c19ae1886fba91aa8551c3c12a9902) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ib941989130be497ef6e7c72cdacf46de6c318792 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-16Remove waits on chassis-control in host targetsMatt Spinler4-8/+0
The org.openbmc.control.Chassis service is no longer used for anything and is being removed, so remove the waits on it. (From meta-phosphor rev: 0603d1636896adce54710c3658dcd9f701d97b77) Change-Id: I03872ee827562be1d7e6d06d6503545ad1d38af6 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-06update upstream subtreesBrad Bishop24-37/+37
A number of corequisites exist so squashing these all into one patch. meta-ingrasys - refresh master bc513127f4..67bcaf389f meta-hxt - refresh master 86a4df514f..8fe0d38bbb meta-phosphor - refresh master 06c09d7cce..df6ddae3d2 meta-quanta - refresh master 4f126361a1..53f3025271 Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-03-29meta-phosphor: Drop recipe for phosphor-restBrad Bishop1-2/+0
This application doesn't have any in-tree users. As such, drop the recipe and its dependencies. (From meta-phosphor rev: 296cc521f5a1c8c87c63a5b475b23c876241bf22) Change-Id: Ie0ce809f84a133c023f96b4727550690583cb9df Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-06meta-phosphor: Move layer content from common/Brad Bishop35-0/+253
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>