aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.vnet.ibm.com>2016-05-05 12:28:10 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>2016-05-05 12:28:10 +1000
commita49d21c9b29dfb38229761b0294f36308c8bde66 (patch)
tree3ae6ed880f34f8296f7b7aff691a7f4b96d388ad
parenta2c5edeb2b0b357785033150c97ddeada5932f2d (diff)
downloadskiboot-skiboot-5.2.2.zip
skiboot-skiboot-5.2.2.tar.gz
skiboot-skiboot-5.2.2.tar.bz2
Add skiboot 5.2.2 release notesskiboot-5.2.2
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
-rw-r--r--doc/release-notes/skiboot-5.2.2.txt32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/release-notes/skiboot-5.2.2.txt b/doc/release-notes/skiboot-5.2.2.txt
new file mode 100644
index 0000000..603270c
--- /dev/null
+++ b/doc/release-notes/skiboot-5.2.2.txt
@@ -0,0 +1,32 @@
+skiboot-5.2.2
+-------------
+
+skiboot-5.2.2 was released on Thursday May 5th, 2016.
+
+skiboot-5.2.2 is the third stable release of skiboot 5.2, the new stable
+release of skiboot, which will take over from the 5.1.x series which was
+first released August 17th, 2015.
+
+Skiboot 5.2.2 replaces skiboot-5.2.1 as the current stable version, which was
+released on April 27th, 2016. Over skiboot-5.2.1, skiboot 5.2.2 contains
+one bug fix targetted at P8NVL systems, notably the Garrison platform.
+
+skiboot-5.2.2 contains all bug fixes as of skiboot-5.1.16.
+
+This is the second release that will follow the (now documented) Skiboot
+stable rules - see doc/stable-skiboot-rules.txt.
+
+Over skiboot-5.2.1, the following fixes are included:
+
+P8NVL/Garrison:
+- PHB3: Fix corruption of pref window register
+ On P8+ Garrison platform, the root port's pref window register might
+ be not writable and we have to emulate the window because of hardware
+ defect. In order to detect that, we read the register content, write
+ inversed value and read the register content again. The register is
+ regarded as read-only if the values from the two continuous read are
+ same. However, the original register content isn't written back and
+ it causes corruption on pref window register if it's writable.
+
+ This fixes the above issue by writing the original content back to
+ the register at the end.