Skip to content

Commit d1e2f74

Browse files
committed
add skiboot-5.4.0-rc4 release notes
Signed-off-by: Stewart Smith <[email protected]>
1 parent e5720d3 commit d1e2f74

File tree

1 file changed

+50
-0
lines changed

1 file changed

+50
-0
lines changed
+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
.. _skiboot-5.4.0-rc4:
2+
3+
=================
4+
skiboot-5.4.0-rc4
5+
=================
6+
7+
skiboot-5.4.0-rc4 was released on Tuesday November 8th 2016. It is the
8+
fourth (and hopefully final) release candidate of skiboot 5.4, which will
9+
become the new stable release of skiboot following the 5.3 release, first
10+
released August 2nd 2016.
11+
12+
skiboot-5.4.0-rc4 contains all bug fixes as of :ref:`skiboot-5.3.7`
13+
and :ref:`skiboot-5.1.18` (the currently maintained stable releases).
14+
15+
For how the skiboot stable releases work, see :ref:`stable-rules` for details.
16+
17+
Since this is a release candidate, it should *NOT* be put into production.
18+
19+
With this release candidate, I'm hoping that it's the last one, and that within
20+
the week we're able to tag a final 5.4.0 release. There is one bit of code I'm
21+
hoping to merge in before the final 5.4.0, and that's the p8dtu platform
22+
definition. The aim is for skiboot-5.4.x to be in op-build v1.13, which is due
23+
by November 23rd 2016.
24+
25+
Over :ref:`skiboot-5.4.0-rc3`, we have a few changes:
26+
27+
- Add BMC platform to enable correct OEM IPMI commands
28+
29+
An out of tree platform (p8dtu) uses a different IPMI OEM command
30+
for IPMI_PARTIAL_ADD_ESEL. This exposed some assumptions about the BMC
31+
implementation in our core code.
32+
33+
Now, with platform.bmc, each platform can dictate (or detect) the BMC
34+
that is present. We allow it to be set at runtime rather than purely
35+
statically in struct platform as it's possible to have differing BMC
36+
implementations on the one machine (e.g. AMI BMC or OpenBMC).
37+
38+
- hw/ipmi-sensor: Fix setting of firmware progress sensor properly.
39+
40+
On FSP systems, OPAL was incorrectly setting firmware status
41+
on a sensor id "00" which doesn't exist.
42+
43+
- pflash: remove stray d in from info message
44+
- libflash/pflash: support whole chip erase on mtd access
45+
- boot_test: fix typo in console message
46+
- core/pci: Fix criteria in pci_cfg_reg_filter(), i.e. NVLink didn't work.
47+
48+
- Remove KERNEL_COMMAND_LINE mention from config.h
49+
50+
We removed the functionality but not the define.

0 commit comments

Comments
 (0)