[Skiboot] [PATCH] Remove POWER7 and POWER7+ support

[Stewart Smith]

Alexey Kardashevskiy <aik at ozlabs.ru> writes:
> On 04/06/2019 18:38, Oliver wrote:
>> On Tue, Jun 4, 2019 at 6:34 PM Vaidyanathan Srinivasan
>> <svaidy at linux.ibm.com> wrote:
>>>
>>> * Stewart Smith <stewart at linux.ibm.com> [2019-06-03 15:38:34]:
>>>
>>>> It's been a good long while since either OPAL POWER7 user touched a
>>>> machine, and even longer since they'd have been okay using an old
>>>> version rather than tracking master.
>>>>
>>>> There's also been no testing of OPAL on POWER7 systems for an awfully
>>>> long time, so it's pretty safe to assume that it's very much bitrotted.
>>>
>>> hmm... So can we document the last working OPAL version for a P7?
>>>
>>> I agree that we can remove support because it is not being actively
>>> tested and maintained.  :(
>>>
>>> However we should document what version/stable branch should be run on
>>> a P7 to keep the machine working/useful.
>> 
>> I all of our P7s that ran OPAL mysteriously died at some point so
>> we're not sure. If you happen to have one, can you record the OPAL
>> version it's using? :)
>> 
>> Alexey was the last person actively using a VPL, so he might know.
>
>
> I have booted vpl1 which is p7 with the p5ioc2 IO hub (i.e. even worse
> than PHB3) and FSP. I booted it last night, it has lots of "ELOG"
> messages (below) so the boot time header is lost and the machine itself
> struggles to boot every time (something in kexec seems broken but the
> latest kernel which supports this is v4.4) so I am leaving it running -
> you can try and figure out the running skiboot sha1 or reboot it and see
> it in the serial console (sshpass -p foo ssh aik:vpl1 at serial).
>
>
> ===
> [36921559136511,5] ELOG: Notified of log 0x503d2e5d (size: 3208)
> [36921559139676,5] ELOG: Log entry 0x503d2e5d discarded
> ===


skiboot-5.1.18-opdirty seems to be it, and
https://open-power.github.io/skiboot/doc/release-notes/skiboot-5.2.0-rc1.html
says we removed p5ioc in the next major version, so 5.1.x seems to be
where it's at.

-- 
Stewart Smith
OPAL Architect, IBM.