AMD AGESA and binaryPI board removals, last calls

[Kyösti Mälkki]

Hi

Regarding the deprecation of AGESA and binaryPI platforms.

As of 15th Dec 2019 following boards have been transformed to meet
4.11 release requirements, and most have a fresh board-status uploaded
now too:

* asrock/e350m1
* asrock/imb-a180
* asus/f2a85-m
* gizmosphere/gizmo
* hp/pavilion_m6_1035dx
* lenovo/g505s
* pcengines/apu1
* pcengines/apu2

I have seen some active development for the boards listed below, and I
am postponing the source removals for these until 2nd Feb 2020. As
these boards are no longer build-tested they may degrade fast.

* amd/bettong
* asus/am1i-a
* biostar/am1ml

Developers will help people who have these platforms to bring their
board sources to current standards. The process begins by uploading a
fresh board-status result for the board you volunteer to work on and
announce this by replying to this thread.

Unless followilng boards see activity in form of boot success/failure
reports on the mailing list or in the board-status repository, their
sources will be removed from master 31st Dec 2019.

* amd/db-ft3b-lc
* amd/inagua
* amd/lamar
* amd/olivehill
* amd/olivehillplus
* amd/parmer
* amd/persimmon
* amd/thatcher
* amd/south_station
* amd/union_station
* bap/ode_e20XX
* bap/ode_e21XX
* biostar/a68n_5200
* elmex/pcm205400
* gizmosphere/gizmo2
* hp/abm
* jetway/nf81-t56n-lf
* lippert/frontrunner-af
* lippert/toucan-af
* msi/ms7721

Furthermore:
* amd/bettong removal, should it happen, triggers CarrizoPI (00660F01) removal
* amd/lamar removal, should it happen, triggers KaveriPI (00630F01) removal

Once a board has its source removed, it will face the standard review
process should someone want to bring it back. Reincarnations until
next (4.12) release might not be accepted.

Kind regards,
Kyösti Mälkki

[Marshall Dawson]

> amd/bettong removal, should it happen, triggers CarrizoPI (00660F01)
>
> removal

We ought to have all the backward-compatibility for CZ and the Embedded
variants landed in stoneyridge and amd_blobs now.  I think it should be a
fairly easy changeover for amd/bettong from cpu/nb/sb to
soc/amd/stoneyridge if someone is able to spend the time on it.  The older
0060F01 AGESA was superseded years ago by StoneyPI, and has practically no
chance of ever being updated again.  Padmelon may be the preferred board
now but I believe there are likely still Bettongs in the field.

* amd/lamar removal, should it happen, triggers KaveriPI (00630F01) removal
>

I doubt this APU ever got any traction, and I suspect nobody cares much
about it now.

Unless followilng boards see activity ...
>

I'll look up some people I assume are still in the AMD Embedded group and
let them know that support for these platforms is about to go away.  Some,
like the Stations, surely nobody cares about.  The reference boards, like
persimmon, olivehill* and db-ft3b-lc seem more important, but I believe are
only considered legacy now.  I don't see APUs for any of the other Family
15h boards on the website.

Thanks,
Marshall

On Sun, Dec 15, 2019 at 11:46 AM Kyösti Mälkki 
wrote:
> Hi
>
> Regarding the deprecation of AGESA and binaryPI platforms.
>
> As of 15th Dec 2019 following boards have been transformed to meet
> 4.11 release requirements, and most have a fresh board-status uploaded
> now too:
> asrock/e350m1
> asrock/imb-a180
> asus/f2a85-m
> gizmosphere/gizmo
> hp/pavilion_m6_1035dx
> lenovo/g505s
> pcengines/apu1
> pcengines/apu2
>
> I have seen some active development for the boards listed below, and I
> am postponing the source removals for these until 2nd Feb 2020. As
> these boards are no longer build-tested they may degrade fast.
> amd/bettong
> asus/am1i-a
> biostar/am1ml
>
> Developers will help people who have these platforms to bring their
> board sources to current standards. The process begins by uploading a
> fresh board-status result for the board you volunteer to work on and
> announce this by replying to this thread.
>
> Unless followilng boards see activity in form of boot success/failure
> reports on the mailing list or in the board-status repository, their
> sources will be removed from master 31st Dec 2019.
> amd/db-ft3b-lc
> amd/inagua
> amd/lamar
> amd/olivehill
> amd/olivehillplus
> amd/parmer
> amd/persimmon
> amd/thatcher
> amd/south_station
> amd/union_station
> bap/ode_e20XX
> bap/ode_e21XX
> biostar/a68n_5200
> elmex/pcm205400
> gizmosphere/gizmo2
> hp/abm
> jetway/nf81-t56n-lf
> lippert/frontrunner-af
> lippert/toucan-af
> msi/ms7721
>
> Furthermore:
> amd/bettong removal, should it happen, triggers CarrizoPI (00660F01)
>
> removal
> amd/lamar removal, should it happen, triggers KaveriPI (00630F01) removal
>
> Once a board has its source removed, it will face the standard review
> process should someone want to bring it back. Reincarnations until
> next (4.12) release might not be accepted.
>
> Kind regards,
> Kyösti Mälkki
> _______________________________________________
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Jorge Fernandez Monteagudo]

Hi Marshall
> amd/bettong removal, should it happen, triggers CarrizoPI (00660F01) removal
>
> We ought to have all the backward-compatibility for CZ and the Embedded variants landed in stoneyridge and amd_blobs now.  I think it should be a fairly easy changeover for amd/bettong from cpu/nb/sb to soc/amd
> /stoneyridge if someone is able to spend the time on it.  The older 0060F01 AGESA was superseded years ago by StoneyPI, and has practically no chance of ever being updated again.  Padmelon may be the preferred >board now but I believe there are likely still Bettongs in the field.

I would like to try to do the modifications to avoid bettong removal. I'll have some time this Xmas holidays to spend on it.
But I'm still struggling with the minimal changes to be able to generate a board_status report because no commits I've done
are merged. I don't know exactly how to proceed to avoid deprecation...

Thanks!
Jorge

[Kyösti Mälkki]

On Tue, Dec 17, 2019 at 8:13 AM Jorge Fernandez Monteagudo
 wrote:
> Hi Marshall
> > amd/bettong removal, should it happen, triggers CarrizoPI (00660F01) removal
> >
> > We ought to have all the backward-compatibility for CZ and the Embedded variants landed in stoneyridge and amd_blobs now.  I think it should be a fairly easy changeover for amd/bettong from cpu/nb/sb to soc/amd
> > /stoneyridge if someone is able to spend the time on it.  The older 0060F01 AGESA was superseded years ago by StoneyPI, and has practically no chance of ever being updated again.  Padmelon may be the preferred >board now but I believe there are likely still Bettongs in the field.
>
> I would like to try to do the modifications to avoid bettong removal. I'll have some time this Xmas holidays to spend on it.
> But I'm still struggling with the minimal changes to be able to generate a board_status report because no commits I've done
> are merged. I don't know exactly how to proceed to avoid deprecation...

AMD is not valueing my work or fulfilling their part of the
agreements, so I am leaving these size 13 shoes behind for someone to
fill. From what I know, the only persons I could recommend for further
binaryPI related reviews are not being for these tasks either.

Regards,
Kyösti Mälkki