On Tue, 2016-06-21 at 08:22 -0500, Rob Herring wrote: > > +Required properties (in root node): > > +- compatible value: > > + compatible = "arm,<family>,<variant>", "arm,<family>"; > > + where <family> is one of: > > + - "fvp-base" for the Base FVP > > + - "fvp-ve" for the VE FVP > > + and <variant> is the part of the model's executable filename with > the family > > + name omitted, converted to lower case, and with non-alphanumeric > characters > > + replaced with '-'. E.g. the Base FVP that has two AEMv8 CPU > clusters has an > > + executable file called FVP_Base_AEMv8A-AEMv8A, so the compatible > value for > > Naming conventions of the exe aren't going to change? Almost certainly will at some point, as will the very name Fixed Virtual Platform, what 'families' ARM produce and their naming, and the configuration of the 'hardware' compiled into the models. These are software models, so can be changed easily at the whim of marketing, or current perceived requirements from engineers and managers. So generally, it's a moving target, that doesn't fit nicely into the needs producing device-trees. -- Tixy -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
