commit | e11e2faa924243c298ade492a770a01c6179d6d0 | [log] [tgz] |
---|---|---|
author | Sunitha Harish <sunharis@in.ibm.com> | Thu Feb 03 04:25:31 2022 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Apr 12 21:26:02 2022 +0000 |
tree | d4a6f56f0607487d32d8b1f0b9e0be1aeae08f1c | |
parent | ae1cf7b02df1e44e857bd9f7167fbaf062a8e9a7 [diff] |
Add StaticNTPServers propetry to EthernetInterface Currently there is no way to differentiate between the Static and DHCP assigned NTP servers at dbus This commit adds StaticNTPServers peroperty to hold the static configuration of NTP servers. This is a read-write property. The existing NTPServer propery will hold both static and DHCP assigned NTP servers. This is a read-only property. Signed-off-by: Sunitha Harish <sunharis@in.ibm.com> Change-Id: If6ac588c268473802ebb1b8f08144df594ac943a
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir