heads
heads copied to clipboard
linuxboot
bump common boards to coreboot 415 and kernel 510
Last tests shows that a different kernel config will be necessary for xx30-flash legacy and maximized boards, where only legacy and maximized currently exists.
As far as we are concerned, and since no gpg nor encryption nor network operations are happening under xx30-flash boards, the kernel could be axed more and have network support and crypto algos completely removed under kernel configurations. That is next step. I will push local changes in a hit so collaboration can happen.
No, a simple kernel version is not possible under 4mb CBFS available total space for xx30-flash boards.
Another solution is to keep 4.14 kernel there, but as far as build time is important, this would be less desirable both for local and CI builds. The more shared the happier will be CircleCI free tier at the end of the month
The simplest solution as of now is to keep legacy xx30-flash boards on kernel 4.14 and bump others to newer kernel version. At some point, I do not see even value into bumping kernel version for flash boards. So renaming those configs with kernel versions in filename will be next step.
Will test that, but as we know, that means longer build times on CI because multiple kernel versions will need to be built, so maybe building only for releases, if releases comes to Heads at some point, since the task of that board is only to flash internally. And the costs of time investment into making 4mb ROM and stripping and axing down kernel size for each kernel bump... this is really a burden at this point I will notninvest time in.
Otherwise, we now know that if all boards share the same kernel version and coreboot versions, with new CircleCI 30 parallelizes steps, we could build each new commit for all boards under 1h if we have proper cache from a past 30 days build, or a little more then one hour otherwise: https://app.circleci.com/pipelines/github/tlaurion/heads/884/workflows/d8c4ed84-360c-408b-8269-7407a50eaf57