diff options
| author | Konstantin Aladyshev <aladyshev22@gmail.com> | 2021-02-26 12:37:07 +0300 |
|---|---|---|
| committer | Ed Tanous <ed@tanous.net> | 2021-07-20 21:04:50 +0300 |
| commit | cd9a4666e67563bad804d08b891f7d852ac6e18a (patch) | |
| tree | 2ed3c4163ee39692abde16b26146a85aa32eb7db /LICENSE | |
| parent | b4bec66b24755cf87e924d56219c60e9506f196b (diff) | |
| download | bmcweb-cd9a4666e67563bad804d08b891f7d852ac6e18a.tar.xz | |
Add support for the BootSourceOverrideMode
BootSourceOverrideMode is the BIOS boot mode to use when
the system boots from the BootSourceOverrideTarget boot source.
Possible values are:
-Legacy - The system boots in non-UEFI boot mode to
the boot source override target
-UEFI - The system boots in UEFI boot mode to
the boot source override target
For the architectures that don't implement Legacy/UEFI boot mode
property (for example POWER), don't publish BootSourceOverrideMode
interface at all.
Redfish validator has been executed on this change and no new
error was found.
Also tested with the help of the openbmc-test-automation framework.
When the Legacy/UEFI boot mode is present in the system command for
testing is:
robot -v PLATFORM_ARCH_TYPE:x86 \
-v OPENBMC_HOST:<BMC IP> \
redfish/systems/test_boot_devices.robot
When the Legacy/UEFI boot mode is not present in the system command
for testing is:
robot -v OPENBMC_HOST:<BMC IP> \
redfish/systems/test_boot_devices.robot
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Id64e428752b820d481ce15d56566dd7b06738ec0
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions