commit | abd67bdf742ba4967e332ea72d7db07d6fba71d0 | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Tue May 21 02:11:46 2024 -0500 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Tue May 21 09:00:18 2024 +0000 |
tree | 137d463c766d6742acfc222830e08a28febbf484 | |
parent | cd2d64a7fecced8da8fe951542a76c987d28231c [diff] |
com.ibm: Add DI property to ipzvpd VINI interface The property DI reflects keyword required to hold DRAM manufacturer ID in case of DIMMs. Change-Id: I197d13a006ad9bad5225d951b730cca57c263749 Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson
. The typical meson
workflow is: meson builddir && ninja -C builddir
.
The meson files used to handle the YAML files are automatically generated and found under the gen
subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen
subdirectory: cd gen && ./regenerate-meson
.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir