On Thursday, June 30, 2016 12:25:15 PM CEST Hans de Goede wrote:
quoted
So then how about making use of a more specific compatible string?
e.g.
brcmf {
compatible = "foo,ap6210", "brcm,bcm4329-fmac";
...
};
and if the compatible has more than one element you request
FW_NAME_<compatible>.txt as the nvram file. Or try each comptible (and
lastly no suffix) until you get a match. (AFAICT, this is what the
"model" property was originally intended for anyway, but almost nobody
did it right, and everyone put a user readable string into "model" for
boards instead of the ePAPR defined compatible string).
Hmm, interesting idea. Not sure how easy / hard it will be to implement
this, but from a dt binding point of view it seems elegant.
Kalle, Arend, what do you think of this ?
I think that's reasonable. Also, we have precedent for using things like
the boardid as part of the compatible string, which would help do what
Kalle suggested earlier with "nvram-<boardtype>-<boardrev>.txt",
as we get that for free by trying out all the compatible strings.
Arnd