| commit | 3826910ef8f91c05562a716929221745c92dd9d7 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Tue May 30 15:24:50 2023 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed May 31 10:19:49 2023 +0000 |
| tree | 4da3e3476ff530e3ac0f7e78cadbdd409e580698 | |
| parent | abb61a0ff2d9ca0351292a48f8980ca7dd0127a7 [diff] |
Add xyz.openbmc_project.Console.UART Formalize an ad-hoc interface currently implemented in obmc-console. This will contain attributes for each console object that is connected to a physical UART. Other console objects (e.g. VUART) would not implement this interface. could be extended to support additional console attributes, but for now a writable `Baud` property is the only item. Change-Id: Ib4c9f1e24b4843281c222e882586a0fd44af723b Signed-off-by: Jonathan Doman <jonathan.doman@intel.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