commit | 99f7a66305d8d0a20d5e36082ce2d2939ca6cbf5 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Wed May 17 15:24:31 2023 -0500 |
committer | Andrew Geissler <geissonator@yahoo.com> | Wed May 17 15:25:06 2023 -0500 |
tree | fbc729b6934d086ef8ea37e587c8dca7b43be382 | |
parent | 390fccb10f015956f4e4b91252a328d472a6bbfb [diff] |
systemd: no installation in templated targets Upstream yocto introduced a change via e510222 (systemd-systemctl: fix instance template WantedBy symlink construction). This fixes a bug that we in OpenBMC had been taking advantage of in that we were able to document our templated target dependencies without it actually doing anything. The real installation of services within targets occurs in our bitbake recipes due to the complexity of chassis and host instances on a per machine basis. Leave the dependency information in the service files but comment them out. It's useful to be able to look at a service and understand which targets it's going to be installed into by the bitbake recipes. In some cases, we had hard coded the target instance, which does install the service correctly, but only in that one target. All services should be installed via the bitbake recipe to ensure the service is properly installed in all instances of the target. Once the bump for this commit goes into openbmc/openbmc, I will ensure the recipe is updated to install all services correctly. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I80aa53404644f83bdbd5cbfbbdafc190011a75c8
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser
configure option. This parser differs from the OpenPower VPD parser in the following ways:
#
and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.