[OpenPower-Firmware] op-build v2.5-rc1 released

[Stewart Smith]

On Wed, May 20, 2020, at 5:50 AM, Dan Horák wrote:
> On Tue, 19 May 2020 14:02:37 +0200
> Dan Horák <dan at danny.cz> wrote:
> 
> > On Tue, 19 May 2020 07:47:58 -0300
> > Klaus Heinrich Kiwi <klaus at linux.vnet.ibm.com> wrote:
> > 
> > > 
> > > 
> > > On 4/30/2020 4:34 PM, Klaus Heinrich Kiwi wrote:
> > > > Release Notes for OpenPower Firmware v2.5-rc1
> > > > =============================================
> > > > 
> > > > op-build v2.5-rc1 was released on Thursday, April 30th, 2020. It
> > > > should become the next stable release of op-build, following on
> > > > from v2.4, first released on July 28th, 2019.
> > > Folks,
> > > 
> > > So far we haven't got feedback on op-build v2.5-rc1. I'm specially 
> > > interested in Power8 feedback, and non-IBM platforms.
> > 
> > we should be able to provide feedback for Tyan Palmetto and Habanero
> > in the next few days
> 
> Habanero looks good (= boots into Fedora 32 with the updated firmware)
> 
> [root at localhost ~]# lsmcode
> Version of System Firmware : 
>  Product Name          : OpenPOWER Firmware
>  Product Version       : open-power-habanero-v2.5-rc1-1-gbe6dabe5
>  Product Extra         : 	skiboot-v6.6
>  Product Extra         : 	bmc-firmware-version-2.04
>  Product Extra         : 	occ-p8-841e28a
>  Product Extra         : 	hostboot-p8-3267aff-p7e1af9d
>  Product Extra         : 	buildroot-2019.05.3-17-g522600dd45
>  Product Extra         : 	capp-ucode-p9-dd2-v4
> 
> except ^^^
> p9-dd2 doesn't look right for p8

This is actually okay - the CAPP ucode repository has tagged versions that represent the latest processor that it supports. So the problem is only if you have a CPU newer than what the tag is (or need a bug fixed that's in the v5 tag, if it existed).