| commit | 0ef46c1e65fb6e88667d468bad88932be481ab54 | [log] [tgz] |
|---|---|---|
| author | Tejas Patil <tejaspp@ami.com> | Mon Jul 19 17:34:57 2021 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Aug 02 07:10:51 2021 -0500 |
| tree | 6ff293a1f6d42031d8558d3591d82945f23c5924 | |
| parent | 73989f1d73172536ab04ea9e84dd68a3d49ed77a [diff] |
Network: Add support for MTU propery This commit adds support for the MTU property under the "xyz.openbmc_project.Network.EthernetInterface" interface. This property shows the maximum size of the Protocol Data Uint (PDU) in bytes, that can be passed in an Ethernet frame on the network interface. Tested: Verified this property on "xyz.openbmc_project.Network.EthernetInterface" interface. busctl introspect xyz.openbmc_project.Network /xyz/openbmc_project/network/eth3 NAME TYPE SIGNATURE RESULT/VALUE FLAGS xyz.openbmc_project.Network.EthernetInterface interface - - - .MTU property u 1500 emits-change writable Signed-off-by: Tejas Patil <tejaspp@ami.com> Change-Id: I3aa758edf5cfee25c928934c315d705920094c00
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 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