History log of /openbmc/phosphor-psu-code-mgmt/README.md (Results 1 – 11 of 11)
Revision Date Author Comments
# 783406e6 17-Nov-2024 Shawn McCarney <shawnmm@us.ibm.com>

Get model using command line tool

Get the PSU model using a command line tool specified in the meson
options. The default tool is 'psutils --get-model'. The tool should
get the model data directly

Get model using command line tool

Get the PSU model using a command line tool specified in the meson
options. The default tool is 'psutils --get-model'. The tool should
get the model data directly from the PSU.

This is more accurate than getting the Model property of the Asset
interface on D-Bus. Inventory Manager saves its state to files. When
the BMC is booted, Inventory Manager initializes itself using the saved
state. This is necessary to handle the scenario where the BMC is
rebooted while the rest of the system is powered on (such as a
concurrent BMC code update).

However, if all power was removed from the system, a PSU may have been
added/removed/replaced while the BMC was offline. When the BMC boots,
the Inventory Manager saved state is not correct.

Eventually the PSU monitoring application will update the model on
D-Bus, but this can take a non-trivial amount of time. This is
especially true if EntityManager is used to provide the PSU bus and
address information to the PSU monitoring application.

Tested:
* Verified all automated tests build and run successfully
* Verified application uses command line tool to obtain model
* Verified command line tool was returning the correct model
* Test where command line tool fails with non-zero exit code
* Tested where all PSU information available when application starts
* Tested where PSU information is obtained after application starts
using the InterfacesAdded handler
* Tested where PSU presence changes and is obtained by the
PropertiesChanged handler
* Full test plan is available at
https://gist.github.com/smccarney/87bd821a6d317ec0915d1f162028ff01

Change-Id: Ia9d35850aa6ac27dd006679991272232d67390ff
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...


# 7b8a1ef0 29-Jul-2024 George Liu <liuxiwei@ieisystem.com>

README.md: Fix MD031 warnings

The following warnings are generated by using markdownlint analysis:
```
MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "``

README.md: Fix MD031 warnings

The following warnings are generated by using markdownlint analysis:
```
MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```text"]
```
Refer to markdown-lint [1] to fix MD031
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/031-blanks-around-fences.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I2aa71ac5f54645acbb6343b1c83ff0ce332bc83f

show more ...


# 4638e449 29-Jul-2024 George Liu <liuxiwei@ieisystem.com>

README.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

README.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: Ia972149545434ca0bf601f4b45b4792e8cdb8304

show more ...


# 4ba2edcc 06-Jan-2023 Chicago Duan <duanzhijia01@inspur.com>

Fix bug: Fix spelling errors

Fix spelling errors.

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: Ibf7c6598be90d6a19d4a39adef0dee2202d9f0a6


# b8f30754 08-Dec-2022 Patrick Williams <patrick@stwcx.xyz>

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: Ic3aebc1879f7e8dd74c0d90b555b8076ec10b6e0
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...


# 7905f587 25-Jun-2021 Chicago Duan <duanzhijia01@inspur.com>

Fix unavailable code-update.md link

Fix unavailable code-update.md link.

Tested:
The new link test is OK

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: If5466abb8eb28570e90c921eb

Fix unavailable code-update.md link

Fix unavailable code-update.md link.

Tested:
The new link test is OK

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: If5466abb8eb28570e90c921eb629f92fe17f0ba7

show more ...


# d48ae5fb 01-Jan-2020 Chicago Duan <duanzhijia01@inspur.com>

generate-psu-tar: Add machine name and remove single "-" options

Remove single "-" options because there are too many similar options.

The openbmc image manager expects "MachineName" in MANIFEST th

generate-psu-tar: Add machine name and remove single "-" options

Remove single "-" options because there are too many similar options.

The openbmc image manager expects "MachineName" in MANIFEST that matches
the BMC's OPENBMC_TARGET_MACHINE in /etc/os-release.
* If there is no MachineName in MANIFEST, it logs a warning for now;
* If they do not match, an error is reported and the version is deleted.

Add --machineName argument for generate-psu-tar to make it support the
"MachineName".

Tested: Verify that when a correct machine name is given, the tarball is
processed by image manager correctly;
And if an invalid machine name is given, the tarball uploaded
will get "Machine name doesn't match" error and is deleted.

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: Ie39e01ae7e4a48fade3459a7eb82da214e0400e9

show more ...


# c6db1142 23-Dec-2019 Lei YU <mine260309@gmail.com>

README: Add description about the usage of this repo

Add the description of several usage of this repo:
* How to generate a PSU image tarball;
* How to update the PSU image;
* How the version is upd

README: Add description about the usage of this repo

Add the description of several usage of this repo:
* How to generate a PSU image tarball;
* How to update the PSU image;
* How the version is updated when PSU is replaced.

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I8727a27be138e03e6feecc26205f1c4b0adf8fbe

show more ...


# 8ccc653e 23-Dec-2019 Lei YU <mine260309@gmail.com>

README: Introduce vendor-specific tools

Add detailed description about what the vendor-specific tools shall do,
and how to configure meson to specify the vendor-specific tools.

It also updates meso

README: Introduce vendor-specific tools

Add detailed description about what the vendor-specific tools shall do,
and how to configure meson to specify the vendor-specific tools.

It also updates meson_options.txt to use updated psutils from
phosphor-power by default.

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I17a508b675a754e76645d08d49547f669385813e

show more ...


# 1799f381 17-Oct-2019 Gunnar Mills <gmills@us.ibm.com>

Update local-ci-build.md link

local-ci-build.md is moving under testing/ as part of
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/26244

26244 should merge before this is merged.

Tested: With

Update local-ci-build.md link

local-ci-build.md is moving under testing/ as part of
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/26244

26244 should merge before this is merged.

Tested: With https://jbt.github.io/markdown-editor/
Change-Id: I6346e0073ce6ea40a51ce81ee1059a2d053e6949
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

show more ...


# 9b846121 27-Aug-2019 Lei YU <mine260309@gmail.com>

Rename README to README.md

So that github correctly formats the markdown texts.

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I0f0a410c9fb43ba13c37e63009c71bc28af67bdc