aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm63xx/patches-4.19
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2019-12-29 01:55:54 +0100
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-02-08 18:39:28 +0100
commite4ba8c82947efd39b014496de32ee73e1bec9c71 (patch)
tree29f70c0bddc4c68df25838ca3c055c1b783c3031 /target/linux/brcm63xx/patches-4.19
parent757715c4749a4942a82ca7b333047c44c454b3c5 (diff)
downloadupstream-e4ba8c82947efd39b014496de32ee73e1bec9c71.tar.gz
upstream-e4ba8c82947efd39b014496de32ee73e1bec9c71.tar.bz2
upstream-e4ba8c82947efd39b014496de32ee73e1bec9c71.zip
brcm63xx: use more systematic names for image and DTS files
This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/brcm63xx/patches-4.19')
0 files changed, 0 insertions, 0 deletions