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>

target/linux/brcm63xx/dts/bcm96318ref_p300.dts → target/linux/brcm63xx/dts/bcm6318-brcm-bcm96318ref-p300.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "Broadcom BCM96318REF_P300 reference board";
-	compatible = "brcm,bcm96318ref_p300", "brcm,bcm6318";
+	compatible = "brcm,bcm96318ref-p300", "brcm,bcm6318";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/dsl-275xb-d.dts → target/linux/brcm63xx/dts/bcm6318-d-link-dsl-275xb-d1.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "D-Link DSL-2750B/DSL-2751 rev D1";
-	compatible = "d-link,dsl-275xb-d", "brcm,bcm6318";
+	compatible = "d-link,dsl-275xb-d1", "brcm,bcm6318";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/fast2704n.dts → target/linux/brcm63xx/dts/bcm6318-sagem-fast-2704n.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "Sagem F@ST2704N";
-	compatible = "sagem,f@st2704n", "brcm,bcm6318";
+	compatible = "sagem,fast-2704n", "brcm,bcm6318";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/bcm963268bu_p300.dts → target/linux/brcm63xx/dts/bcm63268-brcm-bcm963268bu-p300.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "Broadcom BCM963268BU_P300 reference board";
-	compatible = "brcm,bcm963268bu_p300", "brcm,bcm63268";
+	compatible = "brcm,bcm963268bu-p300", "brcm,bcm63268";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/bcm963281TAN.dts → target/linux/brcm63xx/dts/bcm6328-brcm-bcm963281tan.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "Broadcom bcm963281TAN reference board";
-	compatible = "brcm,bcm963281TAN", "brcm,bcm6328";
+	compatible = "brcm,bcm963281tan", "brcm,bcm6328";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/dsl-274xb-f.dts → target/linux/brcm63xx/dts/bcm6328-d-link-dsl-274xb-f1.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "D-Link DSL-2740B/DSL-2741B rev F1";
-	compatible = "d-link,dsl-274xb-f", "brcm,bcm6328";
+	compatible = "d-link,dsl-274xb-f1", "brcm,bcm6328";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/r5010unv2.dts → target/linux/brcm63xx/dts/bcm6328-nucom-r5010un-v2.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "NuCom R5010UN v2";
-	compatible = "nucom,r5010unv2", "brcm,bcm6328";
+	compatible = "nucom,r5010un-v2", "brcm,bcm6328";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";

target/linux/brcm63xx/dts/fast2704v2.dts → target/linux/brcm63xx/dts/bcm6328-sagem-fast-2704-v2.dts

@@ -6,7 +6,7 @@
 
 / {
 	model = "Sagem F@ST2704V2";
-	compatible = "sagem,f@st2704v2", "brcm,bcm6328";
+	compatible = "sagem,fast-2704-v2", "brcm,bcm6328";
 
 	chosen {
 		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";