diff options
| author | Jakub Czapiga <jacz@semihalf.com> | 2021-10-21 10:54:36 +0000 |
|---|---|---|
| committer | Patrick Georgi <pgeorgi@google.com> | 2021-10-26 16:27:56 +0000 |
| commit | 965b05adafe3384c3a2a74d642b3e95c00814668 (patch) | |
| tree | fecedbafcba149184cfc748081d9159ba58064ea /Documentation | |
| parent | 0515aa1978ad9795ea0e9a1b0dcada7f3a13f21c (diff) | |
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>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/releases/coreboot-4.15-relnotes.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/releases/coreboot-4.15-relnotes.md b/Documentation/releases/coreboot-4.15-relnotes.md index 5701eb0c96..334d4cae06 100644 --- a/Documentation/releases/coreboot-4.15-relnotes.md +++ b/Documentation/releases/coreboot-4.15-relnotes.md @@ -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 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 |