Documentation/releases/4.15: Add note about libpayload improvements
Change-Id: I3043e70523db1b7f1df90789a69eadd155848bb0 Signed-off-by: Jakub Czapiga <jacz@semihalf.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/58521 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Paul Menzel <paulepanter@mailbox.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
parent
0515aa1978
commit
965b05adaf
|
@ -25,5 +25,16 @@ Previously, the default behaviour for Intel chipset lockdown was to let the FSP
|
||||||
do it. Since all related mainboards used the coreboot mechanisms for chipset
|
do it. Since all related mainboards used the coreboot mechanisms for chipset
|
||||||
lockdown, the default behaviour was changed to that.
|
lockdown, the default behaviour was changed to that.
|
||||||
|
|
||||||
|
### Payloads unit testing
|
||||||
|
|
||||||
|
Libpayload now supports the mock architecture, which can be used for unit testing
|
||||||
|
payloads. (For examples see
|
||||||
|
[depthcharge](https://chromium.googlesource.com/chromiumos/platform/depthcharge/)
|
||||||
|
payload)
|
||||||
|
|
||||||
|
### Unit testing infrastructure
|
||||||
|
|
||||||
|
Unit testing of libpayload is now possible in the same fashion as in the main
|
||||||
|
coreboot tree.
|
||||||
|
|
||||||
### Add significant changes here
|
### Add significant changes here
|
||||||
|
|
Loading…
Reference in New Issue