regenerate-meson: enable meson formattingSigned-off-by: Patrick Williams <patrick@stwcx.xyz>Change-Id: I5bc2c84cf2ebb3a8d64c96bf3c02e4f34d1f28dd
build: support registry generationsdbus++-gen-meson version 10 adds support for redfish registrygeneration and greatly simplifies the install directives.Regenerate the YAML meson files and modif
build: support registry generationsdbus++-gen-meson version 10 adds support for redfish registrygeneration and greatly simplifies the install directives.Regenerate the YAML meson files and modify the base meson.buildas necessary. Also, format meson.build with `meson format`.Signed-off-by: Patrick Williams <patrick@stwcx.xyz>Change-Id: I77586fca7742d5468803913cb45276ca57271655
show more ...
regenerate-meson: re-run with latest from sdbusplusThe sdbus++-gen-meson has a new version, which requires regeneratingall the meson in this repository. Re-run the `regenerate-meson`script.Sig
regenerate-meson: re-run with latest from sdbusplusThe sdbus++-gen-meson has a new version, which requires regeneratingall the meson in this repository. Re-run the `regenerate-meson`script.Signed-off-by: Patrick Williams <patrick@stwcx.xyz>Change-Id: Ib3fe091253297e6cf82ddf2be8175bf3f4a495f4
regenerate-meson: re-run with latest from sdbusplusThe sdbus++-gen-meson has a new version, which requires regeneratingall the meson in this repository. Re-run the `regenerate-meson`script.Cha
regenerate-meson: re-run with latest from sdbusplusThe sdbus++-gen-meson has a new version, which requires regeneratingall the meson in this repository. Re-run the `regenerate-meson`script.Change-Id: Ic72fe80376052d5749ba007bb87be25c83a46279Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
gen: update due to sdbusplus-gen-meson changeSigned-off-by: Patrick Williams <patrick@stwcx.xyz>Change-Id: I9491eb608d9c6849b3e39fe212054a3651bfb824
treewide: Create yaml directoryThis allows the propagated yamldir paramter to work correctly insubproject style builds. We don't want other files in the projectconflicting with tools that scan th
treewide: Create yaml directoryThis allows the propagated yamldir paramter to work correctly insubproject style builds. We don't want other files in the projectconflicting with tools that scan the yamldir.Change-Id: Ie2759c7f3baf399392cdda0e507055ceb262d2e1Signed-off-by: William A. Kennington III <wak@google.com>
build: Regenerate meson for sdbus++ updateChange-Id: I6c7b9fc22d7acf593c268713b2ef837ab983b956Signed-off-by: William A. Kennington III <wak@google.com>
build: regenerate meson with latest sdbusplus versionSigned-off-by: Patrick Williams <patrick@stwcx.xyz>Change-Id: Idb01b777bb90b165c906aacad24b0d3c9b0e93d2
add BMC node properties for modular node systemIn modular node system, there are several nodes inone chassis, and each node has its BMC. One nodeBMC takes primary role, BMC in other nodes works a
add BMC node properties for modular node systemIn modular node system, there are several nodes inone chassis, and each node has its BMC. One nodeBMC takes primary role, BMC in other nodes works assecondary.Both primary BMC and secondary BMC manage their localnode source, they are peer to peer. Sometimes, theyneed to communicate each other, for example, primaryBMC needs to show all event log including secondarynode event log, so it's needed to identify primaryand secondary BMC role.In order to keep the modular node information ineach BMC, it's needed to define DBUS propertiesto indicate BMC nodes and BMC role for each BMCnode, then knows how many nodes in system andwhat's its BMC role in each node.The interface is:"xyz.openbmc_project.State.BMCRedundancy"And the object path is:"/xyz/openbmc_project/State/BMCRedundancy"The "Associations" object path is:"/xyz/openbmc_project/State/BMCRedundancy/Contained"Tested:It's tested in a modular system with multi-BMC.Change-Id: I2383a059503c7a59abc839a1109c656b20745087Signed-off-by: Chen Yugang <yugang.chen@linux.intel.com>Signed-off-by: Patrick Williams <patrick@stwcx.xyz>