aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.vnet.ibm.com>2017-09-19 16:45:01 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>2017-09-19 16:46:11 +1000
commit6dd6a710a7ebcf6bdf81c5b49ed64d819d779987 (patch)
tree10e5f8a8da2d61d9face029560ff63146d05e55d /doc
parentef9ee96df58bfbf462b7c26da21d20d47ea9d7be (diff)
downloadskiboot-6dd6a710a7ebcf6bdf81c5b49ed64d819d779987.zip
skiboot-6dd6a710a7ebcf6bdf81c5b49ed64d819d779987.tar.gz
skiboot-6dd6a710a7ebcf6bdf81c5b49ed64d819d779987.tar.bz2
skiboot-5.4.7 release notes
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com> (cherry picked from commit 17661bef0e0968e60e0938e646e6d3ab0e201d46) Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes/skiboot-5.4.7.rst30
1 files changed, 30 insertions, 0 deletions
diff --git a/doc/release-notes/skiboot-5.4.7.rst b/doc/release-notes/skiboot-5.4.7.rst
new file mode 100644
index 0000000..b4a013e
--- /dev/null
+++ b/doc/release-notes/skiboot-5.4.7.rst
@@ -0,0 +1,30 @@
+.. _skiboot-5.4.7:
+
+=============
+skiboot-5.4.7
+=============
+
+skiboot-5.4.7 was released on Tuesday September 19th, 2017. It replaces
+:ref:`skiboot-5.4.6` as the current stable release in the 5.4.x series.
+
+Over :ref:`skiboot-5.4.6`, we have two backported bug fixes for FSP platforms:
+
+- FSP: Add check to detect FSP Reset/Reload inside fsp_sync_msg()
+
+ During FSP Reset/Reload we move outstanding MBOX messages from msgq to
+ rr_queue including inflight message (fsp_reset_cmdclass()). But we are not
+ resetting inflight message state.
+
+ In extreme corner case where we sent message to FSP via fsp_sync_msg() path
+ and FSP Reset/Reload happens before getting respose from FSP, then we will
+ endup waiting in fsp_sync_msg() until everything becomes normal.
+
+ This patch adds fsp_in_rr() check to fsp_sync_msg() and return error to
+ caller if FSP is in R/R.
+
+- platforms/ibm-fsp/firenze: Fix PCI slot power-off pattern
+
+ When powering off the PCI slot, the corresponding bits should
+ be set to 0bxx00xx00 instead of 0bxx11xx11. Otherwise, the
+ specified PCI slot can't be put into power-off state. Fortunately,
+ it didn't introduce any side-effects so far.