[Skiboot] [PATCH] Document changes to how firmware versions are passed to host on P9

[Stewart Smith]

Vasant Hegde <hegdevasant at linux.vnet.ibm.com> writes:
> On 07/19/2016 12:58 PM, Stewart Smith wrote:
>> We won't do mi-version/ml-version, but we will always have version.
>
> Stewart,
>
> Sorry for late response.
>
>>
>> Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>
>> ---
>>   doc/device-tree/ibm,opal/firmware.txt | 4 +++-
>>   doc/opal-api/power9-changes.txt       | 1 +
>>   2 files changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/doc/device-tree/ibm,opal/firmware.txt b/doc/device-tree/ibm,opal/firmware.txt
>> index eab497058be4..3376fba86f37 100644
>> --- a/doc/device-tree/ibm,opal/firmware.txt
>> +++ b/doc/device-tree/ibm,opal/firmware.txt
>> @@ -18,11 +18,13 @@ firmware {
>>   'symbol-map' property describes OPAL symbol start address and size.
>>
>>   'version' property describes OPAL version. Replaces 'git-id', so may
>> -not be present.
>> +not be present. On POWER9 and above, it is always present.
>>
>>   'mi-version' property describes Microcode Image. Only on IBM FSP systems.
>> +Will (likely) not be present on POWER9 systems.
>>
>>   'ml-version' property describes Microcode Level. Only on IBM FSP systems.
>> +Will (likely) not be present on POWER9 systems.
>
> I failed to understand why it will not be present on FSP based P9 system? Any 
> reason?
>
> update_flash (user space tool) makes use of these properties.

I think we should put it in a better place, a node that describes the
state of the host firmware at boot time, and some API to get the
*current* state of host firmware. Same for BMC firmware.

-- 
Stewart Smith
OPAL Architect, IBM.