diff options
| author | Edward O'Callaghan <quasisec@google.com> | 2022-06-30 18:12:40 +1000 |
|---|---|---|
| committer | Anastasia Klimchuk <aklm@chromium.org> | 2022-07-17 23:08:47 +0000 |
| commit | c9b7ae55d1f75640a363e85d6c318e822eb255ef (patch) | |
| tree | cad087ceef2b18089aeb41a3a227fa98f1304f6e /cli_classic.c | |
| parent | df0bbf07dec6fcfe8f03f2a0774630a9135c2711 (diff) | |
| download | flashrom-c9b7ae55d1f75640a363e85d6c318e822eb255ef.tar.gz flashrom-c9b7ae55d1f75640a363e85d6c318e822eb255ef.tar.bz2 flashrom-c9b7ae55d1f75640a363e85d6c318e822eb255ef.zip | |
realtek_mst_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: Ifb303989fdb67f7267002bd0425f3d050450ec93
Signed-off-by: Edward O'Callaghan <quasisec@google.com>
Reviewed-on: https://review.coreboot.org/c/flashrom/+/65545
Reviewed-by: Thomas Heijligen <src@posteo.de>
Reviewed-by: Anastasia Klimchuk <aklm@chromium.org>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'cli_classic.c')
0 files changed, 0 insertions, 0 deletions