diff options
| author | Evan Benn <evanbenn@chromium.org> | 2022-11-10 16:02:40 +1100 |
|---|---|---|
| committer | Edward O'Callaghan <quasisec@chromium.org> | 2022-11-24 03:33:12 +0000 |
| commit | 4c8572f103989232b9a24c319c40c12cba2bde97 (patch) | |
| tree | b608ccf0115afa9b1cd2f4401bf858479d2ce0e3 /tests/meson.build | |
| parent | d8be2ced58ef22dad6ee1265ddaeef6b38259b1c (diff) | |
| download | flashrom-4c8572f103989232b9a24c319c40c12cba2bde97.tar.gz flashrom-4c8572f103989232b9a24c319c40c12cba2bde97.tar.bz2 flashrom-4c8572f103989232b9a24c319c40c12cba2bde97.zip | |
flashrom_tester: Change the wp_toggle semantics
wp_toggle and wp_range had some confusing behaviour where enabling wp
would set a range, but disabling wp would not unset the range
(explicitly). This was a way to workaround the MTD kernel driver
semantics. Now make things very explicit, enabling software write
protect will set the range to the whole chip. Disabling write protect
will set the range to 0,0. This makes all drivers behave the same as
MTD, and documents the exact behaviour explicitly.
BUG=b:244663741
BRANCH=None
TEST=flashrom_tester --libflashrom host # MTD and non-MTD
TEST=flashrom_tester --flashrom_binary # MTD and non-MTD
Change-Id: Ia01d612d988e6580a7c5f0fd448ccc319ce9b181
Signed-off-by: Evan Benn <evanbenn@chromium.org>
Reviewed-on: https://review.coreboot.org/c/flashrom/+/69417
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Edward O'Callaghan <quasisec@chromium.org>
Diffstat (limited to 'tests/meson.build')
0 files changed, 0 insertions, 0 deletions