Re: [coreboot] A case for branching AGESA

[ron minnich]

So, if someone came to me with this problem:
building all the targets is slow
and this solution:
get rid of a bunch of them

I'd tell them to go back for more data, because that's just not enough
information.

Why's it slow? Where's the time going? How many files, on average, are part
of an AGESA build vs., e.g., a newer chromebook build? How big are they?
How many files do they include?

But sawing off one's leg because it hurts seems like a rushed decision.

So, what's going on here? Can we get a bit more specific about the problem,
and a bit less drastic about the solution?

ron