#
f4febd00 |
| 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: I35ec9c19ae581e4dd00b515c1bba3a9c1862eeb1 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
6ac6f3df |
| 28-Apr-2022 |
Patrick Williams <patrick@stwcx.xyz> |
designs: remove 'Primary Assignee'
In almost all cases this was the same individual as the author or not filled in. Nobody seems to know what this means in the context of OpenBMC, so we dropped it
designs: remove 'Primary Assignee'
In almost all cases this was the same individual as the author or not filled in. Nobody seems to know what this means in the context of OpenBMC, so we dropped it from the design template. Clean up all the existing designs to remove them.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I01309f0b63d1e0c53fb596521595c5f39f365301
show more ...
|
#
26119113 |
| 12-Apr-2022 |
Andrew Geissler <geissonator@yahoo.com> |
fail-boot: allow host to gracefully shutdown
Utilization of this feature in IBM manufacturing brought to light a deficiency in this design. When the host firmware is booting and logs an error that t
fail-boot: allow host to gracefully shutdown
Utilization of this feature in IBM manufacturing brought to light a deficiency in this design. When the host firmware is booting and logs an error that triggers this function, it would be ideal to allow that host firmware the opportunity to gracefully shut themself down prior to stopping them and moving the host state to quiesced.
This allows the host firmware to find and log any other relevant errors (think something like verifying all dimms in the system). It's much better to find all of these in one boot vs. needing to boot each time to find each bad dimm.
This also allows host firmware a chance to properly write out any cached data and handle any other relevant shutdown operations.
Change-Id: I99dd4a6afa2bf943eff87ef8f2fe670ebd264052 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
#
2bc8dac0 |
| 03-Aug-2021 |
Konstantin Aladyshev <aladyshev22@gmail.com> |
Update links to phosphor-dbus-interfaces YAMLs These commands were used to automatically correct the links: find ./ -type f -exec sed -i 's/phosphor-dbus-interfaces\/tree\/master \/x
Update links to phosphor-dbus-interfaces YAMLs These commands were used to automatically correct the links: find ./ -type f -exec sed -i 's/phosphor-dbus-interfaces\/tree\/master \/xyz/phosphor-dbus-interfaces\/tree\/master\/yaml\/xyz/g' {} + find ./ -type f -exec sed -i 's/phosphor-dbus-interfaces\/blob\/master \/xyz/phosphor-dbus-interfaces\/blob\/master\/yaml\/xyz/g' {} + Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: Icdb96d947f30e4df4f68c4df7300cce0449d3286
show more ...
|
#
6ebb9bd1 |
| 23-Jun-2020 |
Andrew Geissler <geissonator@yahoo.com> |
fail boot on host errors Clarify that the boot block software can be utilized for more then just the hw callout scenario. The openpower-pels extension within phosphor-logging wi
fail boot on host errors Clarify that the boot block software can be utilized for more then just the hw callout scenario. The openpower-pels extension within phosphor-logging will be utilizing these interfaces to halt the boot when certain host PEL errors are sent to the BMC. Change-Id: Ia635724469d042e7d0f95aa904e8042fd53a94b6 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
#
f9b334a7 |
| 20-Feb-2020 |
Andrew Geissler <geissonator@yahoo.com> |
fail boot on hw error This is a design proposal on how to handle requirements by our manufacturing team in regards to ensuring a computer system is not shipped to a customer with bro
fail boot on hw error This is a design proposal on how to handle requirements by our manufacturing team in regards to ensuring a computer system is not shipped to a customer with broken components and to ensure quick detection and repair of an issue. Change-Id: I32dedd31e2f04b7d9602214974a2ac2e1573885a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|