Fix futility mocking & add GBB region only if we don't already use
WP_RO otherwise flashrom will complain on write as those 2 regions
overlap
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock-func: set dmidecode to return 0 by default
if test variable isn't defined this likely means that this value
doesn't matter for test purposes.
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock-func: cbmem shouldn't exit in failure in normal check
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock-func: cbfstool: allow specifying fmap regions in binary
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
dts-functions: set_flashrom_update_params: don't use $1 directly
It's hard to know exactly what this argument is for otherwise as this
function isn't documented
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
deploy: don't use mktemp so profile arguments are always the same
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
dts-boot: create TEMP_DIR
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: cbfstool: return 1 if not coreboot
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
cbfstool: don't mock when we check update binary config
Except in some cases where we want to possibly test for identical
config between update binary and current firmware.
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
dasharo-deploy: add 2>>ERR_LOG_FILE redirection
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: cbmem: check if coreboot
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
dts-functions: download_keys: use 'mkdir -p' so it doesn't error out
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: add cbmem_common_mock which returns error if not coreboot
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: add msrtool and mei-amt-check common mock
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: ifdtool: call original ifdtool if used with update binary
Fixes situation on QEMU that results in user not being asked whether to
continue flashing without ME even though we want to test with ME enabled
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: flashrom: verify internal chip use
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: add bootsplash presence mocking
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: both flashrom and cbfstool allow writing over existing file
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: bootsplash region might exist without custom bootsplash
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
check_if_me_disabled: Don't use mocked functions with 'grep -q'
Otherwise grep will break pipe immediately after matching searched
string which will result in mocked function being immediately stopped
even before finishing. It also results in e.g. tool wrapper not writing
used command to profile
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: Add separate ME disabled and ME HAP disabled
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: add cbfstool smmstore mocking
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
common-mock: simplify fuse mock
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
dts-functions: check_if_boot_guard_enabled: hide rdmsr output
remove non-existent command, likely pasted by mistake
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
include: hal: add cbfstool_add_firmware_section_mock
Signed-off-by: Daniil Klimuk <daniil.klimuk@3mdeb.com>
use dont_mock instead of cbfstool_add_firmware_section_mock
Signed-off-by: Daniil Klimuk <daniil.klimuk@3mdeb.com>
common-mock: rename regions to _regions
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
goal
This functions should check only for payloads. We do have another
function called "check_if_dasharo" for checking if we have Dasharo
firmware flashed.
Change the function names to adhere to the "check_if_dasharo" function.
Signed-off-by: Daniil Klimuk <daniil.klimuk@3mdeb.com>
Dasharo firmware is installed
Transition is only possible from Dasharo firmware. If the stock firmware
installed - one should use Initial deployment.
Signed-off-by: Daniil Klimuk <daniil.klimuk@3mdeb.com>
Othrwise we need to determine whether to display this option or not.
To make a transition, at least three things should be checked:
1. Check, what firmware and platform we are running DTS on.
2. Check, whether the current combination of platform x firmware has
available transitions.
3. Check, whether the firmware is available for download.
The first point is done by sourcing dts-nevironment.sh. The second is
done inside check_for_transition and requires running board_config. But
we cannot run board config every time we want, because it mey overwrite
some global variable or cause asking to choose your platform (for some
NovaCustom laptops). The third is not a problem.
Signed-off-by: Daniil Klimuk <daniil.klimuk@3mdeb.com>
Michał Iwanicki
Daniil Klimuk
Artur Raglis