1.. _skiboot-6.0.10: 2 3============== 4skiboot-6.0.10 5============== 6 7skiboot 6.0.10 was released on Wednesday October 31st, 2018. It replaces 8:ref:`skiboot-6.0.9` as the current stable release in the 6.0.x series. 9 10It is recommended that 6.0.10 be used instead of any previous 6.0.x version 11due to the bug fixes it contains. 12 13The bug fixes are: 14 15- Recognise signed VERSION partition 16- hdata/i2c: Skip unknown device type 17 18 Do not add unknown I2C devices to device tree. 19- hdata/i2c: Make SPD workaround more workaroundy 20 21 We have a hack in the I2C device parser to fix up entries generated by 22 hostboot for the DIMM SPD devices. For some reason they get reported as 23 128Kbit EEPROMs which is bad since those have a different I2C interface 24 to an actual SPD device. 25 26 Oddly enough, the FSP also gets this wrong in a slightly different way. 27 In the FSP case they are reported as a at24c04 (4Kbit) EEPROM, which 28 also has a different I2C interface. 29 30 To fix both these problems for any eeprom we find on that bus to have 31 the compatible string of "spd". 32 33- hdata/i2c: Add whitelisting for Host I2C devices 34 35 Many of the devices that we get information about through HDAT are for 36 use by firmware rather than the host operating system. This patch adds 37 a boolean flag to hdat_i2c_info structure that indicates whether devices 38 with a given purpose should be reserved for use inside of OPAL (or some 39 other firmware component, such as the OCC). 40- Add fast-reboot property to /ibm,opal DT node 41 42 this means that if it's permanently disabled on boot, the test suite can 43 pick that up and not try a fast reboot test. 44- libflash: Add ipmi-hiomap (currently for Witherspoon only) 45 46 ipmi-hiomap implements the PNOR access control protocol formerly known 47 as "the mbox protocol" but uses IPMI instead of the AST LPC mailbox as a 48 transport. As there is no-longer any mailbox involved in this alternate 49 implementation the old protocol name is quite misleading, and so it has 50 been renamed to "the hiomap protoocol" (Host I/O Mapping protocol). The 51 same commands and events are used though this client-side implementation 52 assumes v2 of the protocol is supported by the BMC. 53- AMI BMC: use 0x3a as OEM command 54 55 The 0x3a OEM command is for IBM commands, while 0x32 was for AMI ones. 56 Sometime in the P8 timeframe, AMI BMCs were changed to listen for our 57 commands on either 0x32 or 0x3a. Since 0x3a is the direction forward, 58 we'll use that, as P9 machines with AMI BMCs probably also want these 59 to work, and let's not bet that 0x32 will continue to be okay. 60- astbmc: Set romulus BMC type to OpenBMC 61- Fixes to bulid with GCC8 62- phb4/capp: Use link width to allocate STQ engines to CAPP 63 64 Update phb4_init_capp_regs() to allocates STQ Engines to CAPP/PEC2 65 based on link width instead of always assuming it to x8. 66 67 Also re-factor the function slightly to evaluate the link-width only 68 once and cache it so that it can also be used to allocate DMA read 69 engines. 70- phb4/capp: Update the expected Eye-catcher for CAPP ucode lid 71 72 Currently on a FSP based P9 system load_capp_code() expects CAPP ucode 73 lid header to have eye-catcher magic of 'CAPPPSLL'. However skiboot 74 currently supports CAPP ucode only lids that have a eye-catcher magic 75 of 'CAPPLIDH'. This prevents skiboot from loading the ucode with this 76 error message: :: 77 78 CAPP: ucode header invalid 79 80 We fix this issue by updating load_capp_ucode() to use the eye-catcher 81 value of 'CAPPLIDH' instead of 'CAPPPSLL'. 82