diff options
author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2021-01-19 20:05:35 +0100 |
---|---|---|
committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2021-01-23 12:45:21 +0100 |
commit | f52081bcf938efcd910832f3c3713ab9f3ca0738 (patch) | |
tree | 58cbf57000a46307d000c606c970e53e03b1a9e4 /target/linux/mxs/image | |
parent | b2bab951166ab30717b345b95b0dc8d6999ba16e (diff) | |
download | upstream-f52081bcf938efcd910832f3c3713ab9f3ca0738.tar.gz upstream-f52081bcf938efcd910832f3c3713ab9f3ca0738.tar.bz2 upstream-f52081bcf938efcd910832f3c3713ab9f3ca0738.zip |
treewide: provide global default for SUPPORTED_DEVICES
The majority of our targets provide a default value for the variable
SUPPORTED_DEVICES, which is used in images to check against the
compatible on a running device:
SUPPORTED_DEVICES := $(subst _,$(comma),$(1))
At the moment, this is implemented in the Device/Default block of
the individual targets or even subtargets. However, since we
standardized device names and compatible in the recent past, almost
all targets are following the same scheme now:
device/image name: vendor_model
compatible: vendor,model
The equal redundant definitions are a symptom of this process.
Consequently, this patch moves the definition to image.mk making it
a global default. For the few targets not using the scheme above,
SUPPORTED_DEVICES will be defined to a different value in
Device/Default anyway, overwriting the default. In other words:
This change is supposed to be cosmetic.
This can be used as a global measure to get the current compatible
with: $(firstword $(SUPPORTED_DEVICES))
(Though this is not precisely an achievement of this commit.)
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/mxs/image')
0 files changed, 0 insertions, 0 deletions