Patch Set 1:

Patch Set 1: Code-Review+2

Somewhat related, if google/kahlee ships with AGESA_SPLIT_MEMORY_FILES=y, who would need AGESA_SPLIT_MEMORY_FILES=n? Is it that a different set of blobs are under 3rdparty/ or what's going on here?

I doubt anyone would _need_ a non-split image. There's only one blob that's under 3rdparty currently, and that's a non-split one. It seems like amd/padmelon w/Prarie Falcon has landed, or is close, and will use the single image. (BTW, I'm not sure who's driving that but it's not something I'm working on besides a few reviews. So I don't know much more than you do.)

Well at the moment I consider You Marshall to be the 'coreboot man inside AMD'. If you are not driving to get things improved about these blob formats and licenses and repositories then who is.

Specifically, I meant I don't know who is pushing Embedded's Padmelon board and Prairie Falcon. SilverBack had been interested in working on it, and I've asked Richard what's going on, yet I can't say whether the Embedded group was requesting it or not. As you might imagine, AMD has multiple organizations and business units, and Embedded is pretty far removed from my group.

I appreciate that I'm perceived as the coreboot man inside AMD, but I don't plan to be able to change the whole company overnight; that will require time, staffing, and a little persuasion. In the meantime, I'm your best option for improvements. Regarding refreshing the Stoney Ridge binaryPI(s), I'm open to suggestions for where you would prioritize that vs. the other things in progress. AFAIK the only boards using Stoney Ridge are Chromebooks, with Google-built custom blobs, and amd/padmelon with a particular APU. Also, I think I've mentioned it elsewhere that I'm trying to get AMD to enable more companies to support/deploy binaryPI.

View Change

To view, visit change 37676. To unsubscribe, or for help writing mail filters, visit settings.