skiboot 6.0.5 was released on Wednesday July 11th, 2018. It replaces skiboot-6.0.4 as the current stable release in the 6.0.x series.
It is recommended that 6.0.5 be used instead of any previous 6.0.x version.
Over skiboot-6.0.4 we have several bug fixes, including important ones for NVLINK2 and NX.
phb4: Delay training till after PERST is deasserted
This helps some cards train on the second PERST (ie fast-reboot). The reason is not clear why but it helps, so YOLO!
pci: Fix PCI_DEVICE_ID()
The vendor ID is 16 bits not 8. This error leaves the top of the vendor ID in the bottom bits of the device ID, which resulted in e.g. a failure to run the PCI quirk for the AST VGA device.
Fixes: 2b841bf0ef1b (present in v5.7-rc1)
phb4/capp: Calculate STQ/DMA read engines based on link-width for PEC
Presently in CAPI mode the number of STQ/DMA-read engines allocated on PEC2 for CAPP is fixed to 6 and 0-30 respectively irrespective of the PCI link width. These values are only suitable for x8 cards and quickly run out if a x16 card is plugged to a PEC2 attached slot. This usually manifests as CAPP reporting TLBI timeout due to these messages getting stalled due to insufficient STQs.
To fix this we update enable_capi_mode() to check if PEC2 chiplet is in x16 mode and if yes then we allocate 4/0-47 STQ/DMA-read engines for the CAPP traffic.
capi: Select the correct IODA table entry for the mbt cache.
With the current code, the capi mmio window is not correctly configured in the IODA table entry. The first entry (generally the non-prefetchable BAR) is overwrriten. This patch sets the capi window bar at the right place.
occ: sensors: Fix the size of the phandle array ‘sensors’ in DT
Fixes: 99505c03f493 (present in v5.10-rc4)
vpd: Add vendor property to processor node
Processor FRU vpd doesn’t contain vendor detail. We have to parse module VPD to get vendor detail.
vpd: Sanitize VPD data
On OpenPower system, VPD keyword size tells us the maximum size of the data. But they fill trailing end with space (0x20) instead of NULL. Also spec doesn’t stop user to have space (0x20) within actual data.
This patch discards trailing spaces before populating device tree.
NX/VAS for POWER9¶
NX: Add NX coprocessor init opal call
The read offset (4:11) in Receive FIFO control register is incremented by FIFO size whenever CRB read by NX. But the index in RxFIFO has to match with the corresponding entry in FIFO maintained by VAS in kernel. VAS entry is reset to 0 when opening the receive window during driver initialization. So when NX842 is reloaded or in kexec boot, possibility of mismatch between RxFIFO control register and VAS entries in kernel. It could cause CRB failure / timeout from NX.
This patch adds nx_coproc_init opal call for kernel to initialize readOffset (4:11) and Queued (15:23) in RxFIFO control register.
Fixes: 3b3c5962f432 (present in v5.8-rc1)