Revision Date Author Comments
# 29755255 03-Dec-2025 Andrew Geissler <geissonator@yahoo.com>

remove installs on templated services and targets

New yocto is getting more stringent on installation of templated service
and targets.

Templated services are installed by bitbake recipes so there'

remove installs on templated services and targets

New yocto is getting more stringent on installation of templated service
and targets.

Templated services are installed by bitbake recipes so there's no
need to have the WantedBy/RequiredBy in those services.

Here's a summary of the error we get for packages which have templated
services doing an install:
```
ERROR: obmc-phosphor-image-1.0-r0 do_rootfs: Postinstall scriptlets of
['<package>' 'inst returned 1, marking as unpacked only, configuration
required on target']
If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget:${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
```

Tested:
- Confirmed image builds with new yocto and services are still installed
as expected

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

show more ...


# cadaab77 18-Apr-2024 Patrick Williams <patrick@stwcx.xyz>

phosphor-host-condition-gpio: enable multi-host support

The current implementation fails with:

```
[ 18.664351] systemd[1]: phosphor-host-condition-gpio@1.service: Two services allocated for the

phosphor-host-condition-gpio: enable multi-host support

The current implementation fails with:

```
[ 18.664351] systemd[1]: phosphor-host-condition-gpio@1.service: Two services allocated for the same bus name xyz.openbmc_project.State.HostCondition.Gpio, refusing operation.
```

Add the host id into the reserved bus name to avoid collisions.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia4f291d20df913d3f506d976a961a770a81724fc

show more ...


# ba2241c6 26-Oct-2021 Thang Tran <thuutran@amperecomputing.com>

Support checking host status via GPIO pins

Currently, openBmc supports checking host status via ipmi and PLDM
method. However, not all of platforms support IPMI and PLDM. Some
platforms, like Ampere

Support checking host status via GPIO pins

Currently, openBmc supports checking host status via ipmi and PLDM
method. However, not all of platforms support IPMI and PLDM. Some
platforms, like Ampere Mt.Jade checks input GPIO to detect Host
firmware boot status. This commit supports Dbus method to check host
status via GPIO pins, it checks the value of "host0-ready/-n" pin to
detect HOST is ready or not.

Tested:
1. Update GPIO pin to detect host0 ready to "host0-ready"
in the device tree.
2. Enable host-gpios option and add executable and service
files to openBmc software then flash to the board.
3. In the BMC console, check host-gpio-condition via command
"busctl tree xyz.openbmc_project.State.HostCondition.Gpio"
Result as below:
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/Gpios
`-/xyz/openbmc_project/Gpios/host0
4. Turn on/off the HOST0 then check the host status via
command
"busctl get-property \
xyz.openbmc_project.State.HostCondition.Gpio \
/xyz/openbmc_project/Gpios/host0 \
xyz.openbmc_project.Condition.HostFirmware \
CurrentFirmwareCondition"
Result as below:
"xyz.openbmc_project.Condition.HostFirmware.\
FirmwareCondition.<Running/Off>"

Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I20e38e76c5b70119f0c86e5b497d47453d7c5a6c

show more ...