As Felix and John said, probably the best choice will be leave the
Lantiq subtargets with the current structure.
Additionally could be a good idea tuning the XWAY subtarget to 34kc
and enable dsp extensions to achieve better performance in the Danube,
AR9 and VR9 boards. This diff is an example of how it could be done:
Index: trunk/target/linux/lantiq/svip_be/target.mk
===================================================================
--- trunk/target/linux/lantiq/svip_be/target.mk (revisión: 36545)
+++ trunk/target/linux/lantiq/svip_be/target.mk (copia de trabajo)
@@ -3,6 +3,7 @@
BOARDNAME:=SVIP Big Endian
FEATURES:=squashfs jffs2
DEVICE_TYPE:=other
+CFLAGS=-mtune=mips32r2
DEFAULT_PACKAGES+= uboot-svip hostapd-mini
Index: trunk/target/linux/lantiq/xway/target.mk
===================================================================
--- trunk/target/linux/lantiq/xway/target.mk (revisión: 36545)
+++ trunk/target/linux/lantiq/xway/target.mk (copia de trabajo)
@@ -2,6 +2,7 @@
SUBTARGET:=xway
BOARDNAME:=XWAY
FEATURES:=squashfs jffs2 atm
+CFLAGS=-mtune=34kc -mdsp
DEFAULT_PACKAGES+=kmod-leds-gpio kmod-gpio-button-hotplug
Index: trunk/target/linux/lantiq/svip_le/target.mk
===================================================================
--- trunk/target/linux/lantiq/svip_le/target.mk (revisión: 36545)
+++ trunk/target/linux/lantiq/svip_le/target.mk (copia de trabajo)
@@ -3,6 +3,7 @@
BOARDNAME:=SVIP Little Endian
FEATURES:=squashfs jffs2
DEVICE_TYPE:=other
+CFLAGS=-mtune=mips32r2
DEFAULT_PACKAGES+= uboot-svip hostapd-mini
Index: trunk/target/linux/lantiq/falcon/target.mk
===================================================================
--- trunk/target/linux/lantiq/falcon/target.mk (revisión: 36545)
+++ trunk/target/linux/lantiq/falcon/target.mk (copia de trabajo)
@@ -3,6 +3,7 @@
BOARDNAME:=Falcon
FEATURES:=squashfs jffs2
DEVICE_TYPE:=other
+CFLAGS=-mtune=mips32r2
DEFAULT_PACKAGES+= kmod-ifxos gpon-base-files kmod-leds-gpio
kmod-ledtrig-heartbeat \
kmod-gpon-optic-drv gpon-optic-drv kmod-gpon-onu-drv gpon-onu-drv \
Index: trunk/target/linux/lantiq/ase/target.mk
===================================================================
--- trunk/target/linux/lantiq/ase/target.mk (revisión: 36545)
+++ trunk/target/linux/lantiq/ase/target.mk (copia de trabajo)
@@ -2,6 +2,7 @@
SUBTARGET:=ase
BOARDNAME:=Amazon-SE
FEATURES:=squashfs jffs2 atm
+CFLAGS=-mtune=mips32r2
DEFAULT_PACKAGES+=kmod-pppoa ppp-mod-pppoa linux-atm atm-tools
br2684ctl kmod-ltq-dsl-ase ltq-dsl-app
Index: trunk/target/linux/lantiq/Makefile
===================================================================
--- trunk/target/linux/lantiq/Makefile (revisión: 36545)
+++ trunk/target/linux/lantiq/Makefile (copia de trabajo)
@@ -13,7 +13,7 @@
LINUX_VERSION:=3.8.11
-CFLAGS=-Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -mno-branch-likely
+CFLAGS=-Os -pipe -mips32r2 -fno-caller-saves -mno-branch-likely
define Target/Description
Build firmware images for Lantiq SoC
More aggressive optimizations, like -mt, must be selected by the user.
Finally, i've tested a Danube board with -mtune=34kc and strangely
there is no difference than selecting -mtune=24kec
José Vázquez
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
