Skip to content

Commit cb18213

Browse files
committed
skiboot 5.4.0-rc3 release notes
Signed-off-by: Stewart Smith <[email protected]>
1 parent 1f4b254 commit cb18213

File tree

2 files changed

+43
-0
lines changed

2 files changed

+43
-0
lines changed

doc/release-notes/skiboot-5.4.0-rc2.rst

+2
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
.. _skiboot-5.4.0-rc2:
2+
13
=================
24
skiboot-5.4.0-rc2
35
=================
+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
.. _skiboot-5.4.0-rc3:
2+
3+
=================
4+
skiboot-5.4.0-rc3
5+
=================
6+
7+
skiboot-5.4.0-rc3 was released on Wednesday November 2nd 2016. It is the
8+
third release candidate of skiboot 5.4, which will become the new stable
9+
release of skiboot following the 5.3 release, first released August 2nd 2016.
10+
11+
skiboot-5.4.0-rc3 contains all bug fixes as of :ref:`skiboot-5.3.7`
12+
and :ref:`skiboot-5.1.18` (the currently maintained stable releases).
13+
14+
For how the skiboot stable releases work, see :ref:`stable-rules` for details.
15+
16+
Since this is a release candidate, it should *NOT* be put into production.
17+
18+
The current plan is to release a new release candidate every week until we
19+
feel good about it. The aim is for skiboot-5.4.x to be in op-build v1.13, which
20+
is due by November 23rd 2016.
21+
22+
Over :ref:`skiboot-5.4.0-rc2`, we have a few changes:
23+
24+
- pflash: Fail when file is larger than partition
25+
You can still shoot yourself in the foot by passing --force.
26+
- core/flash: Don't do anything clever for OPAL_FLASH_{READ, WRITE, ERASE}
27+
This fixes a bug where opal-prd and opal-gard could fail.
28+
Fixes: `<https://github.com/open-power/skiboot/issues/44>`_
29+
- boot-tests: force BMC to boot from non-golden side
30+
- fast-reset: Send special reset sequence to operational CPUs only.
31+
Fixes fast-reset for cases where there are garded CPUs
32+
- Secure/Trusted boot: be much clearer about what is being measured where.
33+
- Secure/Trusted boot: be more resilient to disabled TPM(s).
34+
- Secure/Trusted boot: The ``force-secure-mode`` NVRAM setting introduced
35+
temporarily in :ref:`skiboot-5.4.0-rc2` has changed behaviour. Now, by
36+
default, the ``secure-mode`` flag in the device tree is obeyed. As always,
37+
any skiboot NVRAM options are in no way ABI, API or supported and may cause
38+
unfinished verbose analogies to appear in release notes relating to the
39+
dangers of using developer only options.
40+
- gard: Fix compiler warning on modern GCC targetting ARM 32-bit
41+
- opal-prd: systemd scripts improvements, only run on supported systems

0 commit comments

Comments
 (0)