The original options were named and described under the false assumption that the chipset lockdown would only be executed during S3 resume. Fix that. Change-Id: I435a3b63dd294aa766b1eccf1aa80a7c47e55c95 Signed-off-by: Nico Huber <nico.h@gmx.de> Reviewed-on: https://review.coreboot.org/21327 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Rudolph <siro@das-labor.org> |
||
|---|---|---|
| .. | ||
| amd | ||
| broadcom | ||
| intel | ||
| nvidia | ||
| ricoh/rl5c476 | ||
| sis/sis966 | ||
| ti | ||
| via | ||