-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 04/28/2018 02:37 PM, Mike Banon wrote:
Hi Mike,
PC Engines alix1c - AMD LX - 2017-09-17 PC Engines alix2d - AMD LX
- 2017-09-17 PC Engines apu1 - AMD Family 14h (AGESA) - 2017-09-05
PC Engines apu2 // apu3 // apu4 // apu5 - AMD 00730F01 (PI) - 2017-10-26
What is expected frequency of sending board status updates? We have all those board and even some awaiting port to coreboot.
We are committed to keep those platforms on the master but I'm not sure if I understand rules based on which platforms are planned for removal.
We maintain coreboot tree with customer specific customizations that will probably never lend in mainline, because of that we are rather interested to make coreboot work with PC Engines platforms on tagged releases and not exactly on any random commit in between. Any commit approach would require firmware validation automation which we will eventually have. So if release cycles take a lot of time then IMO delayed board status update should be allowed.
Second thing that IMO is problematic in board status is assumption that system have to boot with vanilla coreboot. This is problematic when you have to use customized version of SeaBIOS or any other payload used for booting system.
Because of long weekend we will send board status updates for boards under 3mdeb maintainership before 11 May. Please let me know if feel this is too late.
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com