commit | b9f7c1de73ad44c4c6ced7dab8b2a402468cec5d | [log] [tgz] |
---|---|---|
author | Ninad Palsule <ninadpalsule@us.ibm.com> | Tue May 16 10:39:31 2023 -0500 |
committer | Ninad Palsule <ninadpalsule@us.ibm.com> | Tue May 16 15:56:12 2023 +0000 |
tree | 9c14866d0d31bb820340f3f669f91321816d20cc | |
parent | ca6a4837d07e4e27445ae7f8ad5c5dfd952a5bbe [diff] |
Added Connect() method in console DBUS interface The "xyz.openbmc_project.Console.Access" interface is updated to add new method called Connect(). This method returns the unix socket file descriptor. The consumer can use this file descriptor to receive the console data. The leaf node in the object path is a console id. Also, the "SocketName" property is deprecated and removed to avoid exposing implementation details about the console. The tree for the "default" console id. $ busctl tree xyz.openbmc_project.Console.default `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/console `-/xyz/openbmc_project/console/default The introspect for the "default" console id. $ busctl introspect xyz.openbmc_project.Console.default \ /xyz/openbmc_project/console/default NAME TYPE SIGNATURE RESULT/VALUE FLAGS org.freedesktop.DBus.Introspectable interface - - - .Introspect method - s - org.freedesktop.DBus.Peer interface - - - .GetMachineId method - s - .Ping method - - - org.freedesktop.DBus.Properties interface - - - .Get method ss v - .GetAll method s a{sv} - .Set method ssv - - .PropertiesChanged signal sa{sv}as - - xyz.openbmc_project.Console.Access interface - - - .Connect method - h - Change-Id: I52472320de0990dcf0e802add87141a97288085c Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir