On Tue, Dec 10, 2019 at 11:19 AM Jorge Fernandez Monteagudo <[email protected]> wrote: > > >> So, before I can send the board status, should I wait for someone to > >> upload the changes > >> to the repository? > > > >You can wait. Keep in mind board removals for binaryPI are (currently) > >scheduled for 14th December. > > > >It would be wiser to learn to contribute and upload the required fixes > >to gerrit yourself. Clearly, you have already managed to bisect a boot > >regression issue, so your previous statement of "I can only help with > >uploading board-status at release times" is just ... lame. > > Hi Kyösti, > > I've been able to push a Bettong board status (commit > 31848f291a5f9b8ed0cf5e7c2f6651d1b56a1086) > yesterday. The patches I've sent to Gerrit still are not merged but I think > we are on the right track. > What's more is needed to avoid Bettong deprecation? > > Regards, > Jorge
Thanks The board-status you submitted relies on local changes. Can you send output of 'git log --oneline db945ff860' so we have better record of what you had done to make it boot again? You need to replicate [1] for NORTHBRIDGE_AMD_PI_00660F01 and [2] for mb/amd/bettong. AGESA blobs were sometimes modified in unpredictable ways, so it probably will not work out-of-the-box. [1] https://review.coreboot.org/c/coreboot/+/32421 [2] https://review.coreboot.org/c/coreboot/+/32363 Kyösti _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
