| commit | bcb24e1338cf2818d9e4d389eaba46b871ba60c1 | [log] [tgz] |
|---|---|---|
| author | William A. Kennington III <wak@google.com> | Wed Jul 06 16:01:31 2022 -0700 |
| committer | William A. Kennington III <wak@google.com> | Fri Aug 19 02:43:39 2022 +0000 |
| tree | 8c2294641b1674ca91cb3d73b129b814c1c7abed | |
| parent | 7311efe3cbabaa6e86c3b33997cb6ef48e52180b [diff] |
EthernetInterface: Split up dynamic config properties Having all of the dynamic configuration options grouped together makes it harder for clients to specify independent properties as they have to deal with reading unrelated settings and a combinatorically expanding enum. This change adds properties mirrored from DHCPEnabled that split up the different DHCP4/DHCP6/RA acceptance options. Change-Id: If9c0c84fcda6578a894b7bfe2d87ebe030f125de Signed-off-by: William A. Kennington III <wak@google.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir