summaryrefslogtreecommitdiff
path: root/meta-aspeed/recipes-kernel/linux
diff options
context:
space:
mode:
authorLei YU <yulei.sh@bytedance.com>2021-06-10 11:01:54 +0300
committerPatrick Williams <patrick@stwcx.xyz>2021-07-18 14:51:28 +0300
commit065ca47c7af1861cba3245477d29c25faadf6f9d (patch)
tree1d65d57b15ef502ae3326eeea23a892af15566ac /meta-aspeed/recipes-kernel/linux
parent60c84e6d8a653f3f3335851f34c002acaff067f2 (diff)
downloadopenbmc-065ca47c7af1861cba3245477d29c25faadf6f9d.tar.xz
Install obmc-mapper.target from obmc-targets package
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
Diffstat (limited to 'meta-aspeed/recipes-kernel/linux')
0 files changed, 0 insertions, 0 deletions