Have you given any further thought to a programmatic way to express that certain options or values are dependent upon firmware version? This particular instance is harmless because previous ABLs treat this value as if it were 115200, but for example the fact that MemPmuBistTestSelect is required for some versions but invalid for others seems like the kind of thing we're going to need to come up with a way to encode. I know that AMD considers the build-time tooling to be tightly bound to the firmware but we oughtta be better than that. :)
wesolows says: