diff options
author | Edward O'Callaghan <quasisec@google.com> | 2022-06-30 19:53:16 +1000 |
---|---|---|
committer | Thomas Heijligen <src@posteo.de> | 2022-07-30 07:19:20 +0000 |
commit | a97bbba09a2cb145685cc2a6715f9b1cdcdd197e (patch) | |
tree | 3cd970f96a027beffccdef8e56c04decd17dedb7 /util/flashrom_tester/src/lib.rs | |
parent | 84ba82c0e8a79ba14103aa039faf35955d277c74 (diff) | |
download | flashrom-a97bbba09a2cb145685cc2a6715f9b1cdcdd197e.tar.gz flashrom-a97bbba09a2cb145685cc2a6715f9b1cdcdd197e.tar.bz2 flashrom-a97bbba09a2cb145685cc2a6715f9b1cdcdd197e.zip |
mediatek_i2c_spi.c: Add allow_brick=yes programmer param
Currently i2c programmers do not have a safe allow listing
mechanism via board_enable to facilitate fully qualified
chip detection.
Since i2c addresses alone can overlap a user may make the mistake
of using the wrong programmer. Although unlikely, it is within the
realm of possibility that a user could accidently somehow program
another chip on their board.
Change-Id: I2b8f7a9bfae68354105f3196cc40b9d5e795afdf
Signed-off-by: Edward O'Callaghan <quasisec@google.com>
Reviewed-on: https://review.coreboot.org/c/flashrom/+/65554
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Felix Singer <felixsinger@posteo.net>
Reviewed-by: Anastasia Klimchuk <aklm@chromium.org>
Reviewed-by: Thomas Heijligen <src@posteo.de>
Diffstat (limited to 'util/flashrom_tester/src/lib.rs')
0 files changed, 0 insertions, 0 deletions