fsi-scan: make systemd wants relationship

systemd recommends a wants vs. requires relationship so this is a small
step in that direction for OpenBMC.

This also alleviates a common pain point in bringup where FSI is not
working properly or a FSI device is not present in the system. With a
requires relationship, the chassis poweron target fails. What a user
really wants is for the power on to still succeed.

Other firmware, which requires FSI, will detect issues during the host
boot and take proper actions.

Tested:
Injected fail into fsi-scan service and verified with this change that
chassis power on still succeeded.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6b97d8fb51bb54d46549886834225b1e661525e2
2 files changed
tree: b2c55738e1c7b7f50dc0a08049fdbec9700285be
  1. classes/
  2. conf/
  3. recipes-bsp/
  4. recipes-devtools/
  5. recipes-phosphor/
  6. COPYING.apache-2.0
  7. COPYING.MIT
  8. LICENSE
  9. MAINTAINERS
  10. README.md
README.md

OpenEmbedded/Yocto/OpenBMC BSP layer for OpenPOWER reference platforms

This layer provides support for the BMC firmware on OpenPOWER reference platforms, and/or a base upon which to create a BMC firmware implementation on any POWER system.

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: master
revision: HEAD

URI: https://github.com/openbmc/meta-phosphor
branch: master
revision: HEAD

URI: https://github.com/openbmc/meta-aspeed
branch: master
revision: HEAD

More information on OpenPOWER can be found here.

Contributing

meta-openpower patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.

Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-openpower is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.

Patch checklist. Please ensure patches adhere to the following guidelines:

For questions or help please come join us on the mailing list or in IRC.