Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
Where did You get/find v4.16.2.4 packages ? W dniu 2015-07-10 o 19:31, Aleksander Wałęski pisze: Hello Martin, I've just applied your patch against trunk (r46292) and flashed this firmware. Unfortunately linked patch did not apply cleanly because some of your changes were accepted into openwrt trunk. I was able to fix it locally but I hope you will update your patch for others to test it. So far new driver seems to run smoothly but I'll give it some time. I have HUGE problems with wifi but I don't think it's related to lantiq stuff On Sun, Jun 28, 2015 at 2:02 AM, Martin Blumenstingl martin.blumensti...@googlemail.com wrote: On Sat, Jun 6, 2015 at 3:23 PM, Sylwester Petela ssc...@gmail.com wrote: After 9 days and bit of performance drop I reverted back to stripped out init script and also lowered debug level to default so I can track what is causing these issues. If it is a driver issue then you can test the new version (more info below). A few days ago I got a new set of DSL drivers - version 4.16.2.4 to be exact. I am writing this very email while connected with that updated driver. (this is with firmware 5.7.3.3.0.7-5.7.1.5.0.2 / 186b5406e6511c97d997b48f5e0ec5ad3f62600d on a VDSL line). The patch for updating the DSL driver can be found here: [0] Please note that it depends on [1] Regards, Martin [0] https://gist.github.com/xdarklight/3452b26620b28f3bc577 [1] https://lists.openwrt.org/pipermail/openwrt-devel/2015-June/033911.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: ath10k Suppress 'failed to process fft' warning messages.
When using DFS channels on Ath10k kernel log has warning message 'failed
to process fft', typically when under medium/heavy traffic. Ticket
https://dev.openwrt.org/ticket/19316 discusses and concludes messages
are harmless. They do still contribute to log noise, so this patch
enables them only in driver debug mode. Hopefully this will stop people
like me worrying about them.
Tested on Archer C7
Signed-off-by: Kevin Darbyshire-Bryant ke...@darbyshire-bryant.me.uk
---
.../931-ath10k_suppress_failed_to_process_fft_warning.patch | 11 +++
1 file changed, 11 insertions(+)
create mode 100644
package/kernel/mac80211/patches/931-ath10k_suppress_failed_to_process_fft_warning.patch
diff --git
a/package/kernel/mac80211/patches/931-ath10k_suppress_failed_to_process_fft_warning.patch
b/package/kernel/mac80211/patches/931-ath10k_suppress_failed_to_process_fft_warning.patch
new file mode 100644
index 000..dceab0f
--- /dev/null
+++
b/package/kernel/mac80211/patches/931-ath10k_suppress_failed_to_process_fft_warning.patch
@@ -0,0 +1,11 @@
+--- a/drivers/net/wireless/ath/ath10k/wmi.c
b/drivers/net/wireless/ath/ath10k/wmi.c
+@@ -2658,7 +2658,7 @@ void ath10k_wmi_event_spectral_scan(stru
+ fftr, fftr_len,
+ tsf);
+ if (res 0) {
+- ath10k_warn(ar, failed to process fft report:
%d\n,
++ ath10k_dbg(ar, ATH10K_DBG_WMI, failed to
process fft report: %d\n,
+ res);
+ return;
+ }
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Hard float ABI for BCM2708/BCM2709
Hi, I've noticed that OpenWrt currently uses the soft-float ABI in the Raspberry Pi images. Is there a specific reason hard float is not used, even though most other distributions like Raspbian have switched to it? I tried adding fpu to FEATURES to enable hard-float, and the generated images seem to work fine. Matthias signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hard float ABI for BCM2708/BCM2709
On 07/11/2015 07:21 PM, Florian Fainelli wrote: Le 11 juil. 2015 09:52, Matthias Schiffer mschif...@universe-factory.net a écrit : Hi, I've noticed that OpenWrt currently uses the soft-float ABI in the Raspberry Pi images. Is there a specific reason hard float is not used, even though most other distributions like Raspbian have switched to it? I do not think there was any particular reason. This was one of the few ARM-based targets that are not armv5, however armv5 may have been used as a template to kick the initial port. I tried adding fpu to FEATURES to enable hard-float, and the generated images seem to work fine. If you want to submit a patch doing this, I will gladly apply it, we may have to set a different FPU ABI between brcm2708 and 09 though. -- Florian Okay, I'll do some more tests on both brcm2708 and 09 and prepare a patch. I've noticed that currently the toolchain directory naming is somewhat broken in regard to FP ABIs: the 'fpu' FEATURES flag affects the flags the toolchain is built with (--with-float=soft), but this difference isn't reflected in the directory name. I currently see two ways to fix this: 1. Add a 'fpu' or 'softfp' suffix to the directory name (as it is done with 'spe') 2. Don't configure fpu in FEATURES, but make the value of CONFIG_HAS_FPU depend on CPU_TYPE/CPU_SUBTYPE. Can it ever happen that we need the same CPU_TYPE/CPU_SUBTYPE combination both with and without HAS_FPU? I see the flag has been introduced in r11337 by kaloz. Or even both, so the directory suffix will be adjusted accordingly when CONFIG_SOFT_FLOAT is changed manually. Matthias signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] IPTables/NAT
Hi John, I have to enable NAT with a MASQUERADING target, and to block the GUI from WAN have to server bind only the bridge address. Could anyone tell me how i can do it in the GUI itself. You should probably ask this kind of questions on the openwrt-users mailing list: https://lists.openwrt.org/cgi-bin/mailman/listinfo/ Anyway: You should take a look at Administration - Networking - Firewall in the web interface. There you will find everything for you task. Additional information is to be found here: http://wiki.openwrt.org/doc/uci/firewall (just read the introduction of each section - skip the long tables of options) As far as I understand you goals, everything should be configured properly by default. Cheers, Lars ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hard float ABI for BCM2708/BCM2709
Probably no body checked until now if it works and devs went with safe choice. Just my 2c. On 11 July 2015 at 18:51, Matthias Schiffer mschif...@universe-factory.net wrote: Hi, I've noticed that OpenWrt currently uses the soft-float ABI in the Raspberry Pi images. Is there a specific reason hard float is not used, even though most other distributions like Raspbian have switched to it? I tried adding fpu to FEATURES to enable hard-float, and the generated images seem to work fine. Matthias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hard float ABI for BCM2708/BCM2709
Le 11 juil. 2015 09:52, Matthias Schiffer mschif...@universe-factory.net a écrit : Hi, I've noticed that OpenWrt currently uses the soft-float ABI in the Raspberry Pi images. Is there a specific reason hard float is not used, even though most other distributions like Raspbian have switched to it? I do not think there was any particular reason. This was one of the few ARM-based targets that are not armv5, however armv5 may have been used as a template to kick the initial port. I tried adding fpu to FEATURES to enable hard-float, and the generated images seem to work fine. If you want to submit a patch doing this, I will gladly apply it, we may have to set a different FPU ABI between brcm2708 and 09 though. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ramips: added led support for wrtnode board
This syncs the dts file with the one provided by the wrtnode team:
https://github.com/WRTnode/openwrt-patches/blob/master/R41508/wrtnode_factory_firmware_dts.patch
Signed-off-by: Christian Mehlis christ...@m3hlis.de
---
target/linux/ramips/dts/WRTNODE.dts | 12
1 file changed, 12 insertions(+)
diff --git a/target/linux/ramips/dts/WRTNODE.dts
b/target/linux/ramips/dts/WRTNODE.dts
index 3fb2303..793c02f 100644
--- a/target/linux/ramips/dts/WRTNODE.dts
+++ b/target/linux/ramips/dts/WRTNODE.dts
@@ -7,6 +7,10 @@
model = WRTNODE;
palmbus@1000 {
+ gpio1: gpio@638 {
+ status = okay;
+ };
+
gpio2: gpio@660 {
status = okay;
};
@@ -77,4 +81,12 @@
};
};
};
+
+ gpio-leds {
+ compatible = gpio-leds;
+ indicator {
+ label = wrtnode:blue:indicator;
+ gpios = gpio1 14 1;
+ };
+ };
};
--
2.1.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] toolchain: fix gcc 4.6 build with gcc5
build error:
cfns.gperf:101:1: error: 'gnu_inline' attribute present on 'libc_name_p'
cfns.gperf:26:14: error: but not here
observed on Arch Linux
affected versions gcc 4.6, gcc 4.7
reported fixed in DragonFlyBSD issue #136
https://github.com/DragonFlyBSD/DPorts/issues/136
Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de
---
.../gcc/patches/4.6-linaro/010-documentation.patch | 2 +-
.../gcc/patches/4.6-linaro/910-mbsd_multi.patch | 6 +++---
.../4.6-linaro/920-specs_nonfatal_getenv.patch | 2 +-
toolchain/gcc/patches/4.6-linaro/999-coldfire.patch | 2 +-
.../patches/4.6-linaro/999-gcc5-gcc_cp_cfns_h.patch | 21 +
5 files changed, 27 insertions(+), 6 deletions(-)
create mode 100644
toolchain/gcc/patches/4.6-linaro/999-gcc5-gcc_cp_cfns_h.patch
diff --git a/toolchain/gcc/patches/4.6-linaro/010-documentation.patch
b/toolchain/gcc/patches/4.6-linaro/010-documentation.patch
index 25773a3..46178da 100644
--- a/toolchain/gcc/patches/4.6-linaro/010-documentation.patch
+++ b/toolchain/gcc/patches/4.6-linaro/010-documentation.patch
@@ -1,6 +1,6 @@
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
-@@ -4251,18 +4251,10 @@
+@@ -4267,18 +4267,10 @@ doc/gcc.info: $(TEXI_GCC_FILES)
doc/gccint.info: $(TEXI_GCCINT_FILES)
doc/cppinternals.info: $(TEXI_CPPINT_FILES)
diff --git a/toolchain/gcc/patches/4.6-linaro/910-mbsd_multi.patch
b/toolchain/gcc/patches/4.6-linaro/910-mbsd_multi.patch
index 51bbc7f..32b408a 100644
--- a/toolchain/gcc/patches/4.6-linaro/910-mbsd_multi.patch
+++ b/toolchain/gcc/patches/4.6-linaro/910-mbsd_multi.patch
@@ -125,7 +125,7 @@
Assume normal C execution environment
--- a/gcc/common.opt
+++ b/gcc/common.opt
-@@ -520,6 +520,10 @@ Werror=
+@@ -523,6 +523,10 @@ Werror=
Common Joined
Treat specified warning as error
@@ -136,7 +136,7 @@
Wextra
Common Var(extra_warnings) Warning
Print extra (possibly unwanted) warnings
-@@ -1156,6 +1160,9 @@ fguess-branch-probability
+@@ -1159,6 +1163,9 @@ fguess-branch-probability
Common Report Var(flag_guess_branch_prob) Optimization
Enable guessing of branch probabilities
@@ -232,7 +232,7 @@
@item -Wstack-protector
@opindex Wstack-protector
@opindex Wno-stack-protector
-@@ -6317,7 +6333,7 @@ so, the first branch is redirected to ei
+@@ -6322,7 +6338,7 @@ so, the first branch is redirected to ei
second branch or a point immediately following it, depending on whether
the condition is known to be true or false.
diff --git a/toolchain/gcc/patches/4.6-linaro/920-specs_nonfatal_getenv.patch
b/toolchain/gcc/patches/4.6-linaro/920-specs_nonfatal_getenv.patch
index 5055ae8..0b241fa 100644
--- a/toolchain/gcc/patches/4.6-linaro/920-specs_nonfatal_getenv.patch
+++ b/toolchain/gcc/patches/4.6-linaro/920-specs_nonfatal_getenv.patch
@@ -1,6 +1,6 @@
--- a/gcc/gcc.c
+++ b/gcc/gcc.c
-@@ -7772,7 +7772,10 @@ getenv_spec_function (int argc, const ch
+@@ -7830,7 +7830,10 @@ getenv_spec_function (int argc, const ch
value = getenv (argv[0]);
if (!value)
diff --git a/toolchain/gcc/patches/4.6-linaro/999-coldfire.patch
b/toolchain/gcc/patches/4.6-linaro/999-coldfire.patch
index 0913f34..e014386 100644
--- a/toolchain/gcc/patches/4.6-linaro/999-coldfire.patch
+++ b/toolchain/gcc/patches/4.6-linaro/999-coldfire.patch
@@ -1,6 +1,6 @@
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
-@@ -1805,7 +1805,7 @@ m68k-*-linux*) # Motorola m68k's runnin
+@@ -1809,7 +1809,7 @@ m68k-*-linux*) # Motorola m68k's runnin
default_m68k_cpu=68020
default_cf_cpu=5475
with_arch=${with_arch:-m68k}
diff --git a/toolchain/gcc/patches/4.6-linaro/999-gcc5-gcc_cp_cfns_h.patch
b/toolchain/gcc/patches/4.6-linaro/999-gcc5-gcc_cp_cfns_h.patch
new file mode 100644
index 000..7ab0d4c
--- /dev/null
+++ b/toolchain/gcc/patches/4.6-linaro/999-gcc5-gcc_cp_cfns_h.patch
@@ -0,0 +1,21 @@
+--- a/gcc/cp/cfns.h
b/gcc/cp/cfns.h
+@@ -53,6 +53,9 @@ __inline
+ static unsigned int hash (const char *, unsigned int);
+ #ifdef __GNUC__
+ __inline
++#ifdef __GNUC_STDC_INLINE__
++__attribute__ ((__gnu_inline__))
++#endif
+ #endif
+ const char * libc_name_p (const char *, unsigned int);
+ /* maximum key range = 391, duplicates = 0 */
+@@ -96,7 +99,7 @@ hash (register const char *str, register
+ 400, 400, 400, 400, 400, 400, 400, 400, 400, 400,
+ 400, 400, 400, 400, 400, 400, 400
+ };
+- register int hval = len;
++ register int hval = (int)len;
+
+ switch (hval)
+ {
--
2.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Build errors when activating the Device Tree flag for Raspberry Pi
Hi, I'm trying to activate the Device Tree for Raspberry Pi builds. Therefore I changed the flag # CONFIG_BCM2709_DT is not set to CONFIG_BCM2709_DT=y in /home/mine/gitrepos/openwrt2/target/linux/brcm2708/bcm2709/config-default and /home/mine/gitrepos/openwrt2/target/linux/brcm2708/bcm2708/config-default When building for BRCM2709/08 I'm getting the error == LD init/built-in.o drivers/built-in.o: In function `of_get_mac_address_mtd': /home/mine/gitrepos/openwrt2/build_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/linux-brcm2708_bcm2709/linux-3.18.17/drivers/of/of_net.c:106: undefined reference to `get_mtd_device_nm' /home/mine/gitrepos/openwrt2/build_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/linux-brcm2708_bcm2709/linux-3.18.17/drivers/of/of_net.c:110: undefined reference to `mtd_read' /home/mine/gitrepos/openwrt2/build_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/linux-brcm2708_bcm2709/linux-3.18.17/drivers/of/of_net.c:111: undefined reference to `put_mtd_device' make[5]: *** [vmlinux] Error 1 make[5]: Leaving directory `/home/mine/gitrepos/openwrt2/build_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/linux-brcm2708_bcm2709/linux-3.18.17' make[4]: *** [/home/mine/gitrepos/openwrt2/build_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/linux-brcm2708_bcm2709/linux-3.18.17/.image] Error 2 make[4]: Leaving directory `/home/mine/gitrepos/openwrt2/target/linux/brcm2708' make[3]: *** [install] Error 2 make[3]: Leaving directory `/home/mine/gitrepos/openwrt2/target/linux' make[2]: *** [target/linux/install] Error 2 make[2]: Leaving directory `/home/mine/gitrepos/openwrt2' make[1]: *** [/home/mine/gitrepos/openwrt2/staging_dir/target-arm_cortex-a7+vfp_musl-1.1.10_eabi/stamp/.target_install] Error 2 make[1]: Leaving directory `/home/mine/gitrepos/openwrt2' make: *** [world] Error 2 == Is it possible at all to activate the Device Tree for Raspberry builds at all? I'm working on the master of git://openwrt.org/openwrt.git Thanks, Michael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
