build system: order per-region files to optimize placement success
Make sure that files with a fixed position are placed first (whose order
doesn't matter: either they collide or they don't), then all aligned
files (where we just hope that the right thing happens) and finally the
files with no further requirements (again, hope).
It's still a pretty good heuristic given a typical coreboot image.
The global sorting that happens earlier in the build flow will be
removed in the future to make room for per-region requirements.
Signed-off-by: Patrick Georgi <email@example.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <firstname.lastname@example.org>
Reviewed-by: Aaron Durbin <email@example.com>
1 file changed