| commit | 8db5d8d74a8c74bf9ce4e9a95c062a5eec30835f | [log] [tgz] |
|---|---|---|
| author | Johnathan Mantey <johnathanx.mantey@intel.com> | Wed Dec 22 14:40:37 2021 -0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 18:45:05 2022 +0000 |
| tree | a748c28e5122a3ae61b97735a84eb116a029ac4e | |
| parent | 6326b04e62bd7c28bfab5a4d428a399be6575d5f [diff] |
Add additional DHCP configuration options The existing D-Bus DHCPConf enumearation values do not allow IPv6 Stateless DHCP to be assigned. The IPv4 entries are sufficient, as DHCP for the v4 stack is truly a boolean. IPv6 is, at minimum, a ternary control. Adding new enumerations allows the IPv6 configruation to be done in a more abstract fashion than the current IPv6AcceptRA D-Bus entry. This D-Bus entry is a direct reflection of how systemd-networkd manages Routint Advertisement, and by extension DHCPv6. Only phosphor-network needs this knowledge. Tested: The changes compile. Also, in combination with changes made to phosphor-network, many busctl set/get property commands were issued to confirm the enumerations were performing as expected. Change-Id: I42a46549fed8b2d2187ea6a7eb7278c63b84bbef Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.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