| commit | a82161ace395968c3b26306d52c4c304e33a16af | [log] [tgz] |
|---|---|---|
| author | Ravi Teja <raviteja28031990@gmail.com> | Mon Jan 23 10:57:42 2023 -0600 |
| committer | Ravi Teja <raviteja28031990@gmail.com> | Tue Apr 25 22:40:06 2023 -0500 |
| tree | 32b710b653cc1292d5a321361acce7c3422c441d | |
| parent | 927d0930ca70a3767ffae6ae092d51d3a8415250 [diff] |
Add Network Static Route D-bus Interface Static routing provides the network administrator with full control over the routing behavior of the BMC network. This commit adds static route d-bus interface and properties required. Change-Id: Ib6abea1a9ce2f55cb54489c334b0072bf4fb726e Signed-off-by: Ravi Teja <raviteja28031990@gmail.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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir