aboutsummaryrefslogtreecommitdiffstats
path: root/util/git-hooks/commit-msg
diff options
context:
space:
mode:
authorEdward O'Callaghan <quasisec@google.com>2022-11-14 09:16:21 +1100
committerAnastasia Klimchuk <aklm@chromium.org>2023-01-26 20:43:25 +0000
commit7d888a30827ae4bfc72d3098204083598f375294 (patch)
treec8df38bd6ee4e73d732a8ba674fcb5a563a69cfa /util/git-hooks/commit-msg
parent7ffa626d1278a167c430c55891bbb6f979a5ab92 (diff)
downloadflashrom-7d888a30827ae4bfc72d3098204083598f375294.tar.gz
flashrom-7d888a30827ae4bfc72d3098204083598f375294.tar.bz2
flashrom-7d888a30827ae4bfc72d3098204083598f375294.zip
flashrom.c: Supplement `chip->unlock()` calls with wp unlocking
The full writeprotect implementation has proper support and ability to unlock flash over spi25_statusreg.c. Therefore if the required bits are available for the given chip prefer proper writeprotect support instead of adhoc spi25_statusreg.c helpers. BUG=b:237485865 BRANCH=none TEST=Tested on grunt DUT (prog: sb600spi, flash: W25Q128.W): `flashrom --wp-range 0x0,0x1000000 \ flashrom --wp-status # Result: range=0x0,0x1000000 \ flashrom -w random.bin # Result: success \ flashrom -v random.bin # Result: success \ flashrom --wp-status # Result: range=0x0,0x1000000` TEST=Tested that chips without WP support can still be unlocked by deleting decode_range for W25Q128.W flashchip and retesting on the grunt DUT. Change-Id: I74b3f5d3a17749ea60485b916b2d87467a5d8b2f CoAuthored-by: Nikolai Artemiev <nartemiev@google.com> Signed-off-by: Nikolai Artemiev <nartemiev@google.com> Signed-off-by: Edward O'Callaghan <quasisec@google.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/69517 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Edward O'Callaghan <quasisec@chromium.org> Reviewed-by: Anastasia Klimchuk <aklm@chromium.org> Reviewed-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Diffstat (limited to 'util/git-hooks/commit-msg')
0 files changed, 0 insertions, 0 deletions