diff options
author | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-10-13 16:32:36 +1100 |
---|---|---|
committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-10-13 16:36:10 +1100 |
commit | fd19bdff9f67066216040d0455690e4e16036ca7 (patch) | |
tree | cc10a7cc07fc7194e0e861737e95862cddc6c2a0 /doc | |
parent | d40160f6ffa919447807f2d62c25fbd547623361 (diff) | |
parent | e91d12a94866d4232e51aa757b87e5bf0891e6d2 (diff) | |
download | skiboot-fd19bdff9f67066216040d0455690e4e16036ca7.zip skiboot-fd19bdff9f67066216040d0455690e4e16036ca7.tar.gz skiboot-fd19bdff9f67066216040d0455690e4e16036ca7.tar.bz2 |
Merge branch 'stable': FSP leds fix and skiboot 5.1.7 release notes
Diffstat (limited to 'doc')
-rw-r--r-- | doc/release-notes/skiboot-5.1.7.txt | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/doc/release-notes/skiboot-5.1.7.txt b/doc/release-notes/skiboot-5.1.7.txt new file mode 100644 index 0000000..29f9ed5 --- /dev/null +++ b/doc/release-notes/skiboot-5.1.7.txt @@ -0,0 +1,29 @@ +skiboot-5.1.7 +------------- + +skiboot-5.1.7 was released on October 13th, 2015. + +skiboot-5.1.7 is the 8th stable release of 5.1, it follows skiboot-5.1.6 +(which was released October 8th, 2015). + +Skiboot 5.1.7 contains all fixes from skiboot-5.1.6 and is a minor bug +fix release with one important bug fix for FSP systems. + +Over skiboot-5.1.6, we have the following changes: + +Generic: +- PHB3: Retry fundamental reset + This introduces another PHB3 state (PHB3_STATE_FRESET_START) + allowing to redo fundamental reset if the link doesn't come up + in time at the first attempt, to improve the robustness of PHB's + fundamental reset. If the link comes up after the first reset, + the 2nd reset won't be issued at all. + +FSP based systems: +- hw/fsp/fsp-leds.c: use allocated buffer for FSP_CMD_GET_LED_LIST response + + This fixes a bug where we would overwrite roughly 4kb of memory belonging + to Linux when the FSP would ask firmware for a list of LEDs in the system. + This wouldn't happen often (once before Linux was running and possibly + only once during runtime, and *early* runtime at that) but it was possible + for this corruption to show up and be detected. |