Re: [OpenWrt-Devel] [PATCH] mpc85xx: use wpad-mini in WDR4900 profile instead of wpad
Someone accepted the patch in patchwork [1] but as far as I can see nobody applied the patch. Could someone with the appropriate priveleges apply the patch please? Thanks a lot Philipp On Wed, Aug 06, 2014 at 02:09:09PM +0200, Philipp Borgers wrote: This change makes the profile of WDR4900 more consistent with other router specific profiles. Signed-off-by: Philipp Borgers borg...@mi.fu-berlin.de --- target/linux/mpc85xx/profiles/tp-link.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mpc85xx/profiles/tp-link.mk b/target/linux/mpc85xx/profiles/tp-link.mk index abab0f0..47ddacd 100644 --- a/target/linux/mpc85xx/profiles/tp-link.mk +++ b/target/linux/mpc85xx/profiles/tp-link.mk @@ -9,7 +9,7 @@ define Profile/TLWDR4900 NAME:=TP-Link TL-WDR4900 PACKAGES:=\ kmod-usb-core kmod-usb2 kmod-usb2-fsl \ - kmod-ath9k wpad + kmod-ath9k wpad-mini endef define Profile/TLWDR4900/Description -- 2.0.1 pgpHdTzAfj1T8.pgp Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Problems with ffmpeg and alsa-lib
On 10/13/2014 10:48 PM, Ted Hess wrote: 2 - Building alsa-lib has no dependency on the host system's audio setup. The problem you are seeing is indeed a problem with your build environment, and what tools you have installed. More information is needed about our build system and target config before I can help you. I'm building on Ubuntu 14.04, for ar71xx and au1000 targets. The problem happens in OpenWRT 14.07 and trunk. It looks like the host gcc gets called with the target CFLAGS, see the config.log below. Tell me if there is anything else you need to know. bruno build_dir/target-mips_34kc_uClibc-0.9.33.2/alsa-lib-1.0.28/config.log - This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by alsa-lib configure 1.0.28, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --target=mips-openwrt-linux --host=mips-openwrt-linux --build=x86_64-linux-gnu --program-prefix= --program-suffix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share --localstatedir=/var --mandir=/usr/man --infodir=/usr/info --disable-nls --disable-python --disable-debug --without-debug --with-float=soft --with-versioned=no ## - ## ## Platform. ## ## - ## hostname = shiva uname -m = x86_64 uname -r = 3.13.0-37-generic uname -s = Linux uname -v = #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/host/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/host/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/host/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin PATH: /home/br1/dev/openwrt/trunk/openwrt/staging_dir/host/bin PATH: /home/br1/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /usr/local/games ## --- ## ## Core tests. ## ## --- ## configure:2281: loading site script /home/br1/dev/openwrt/trunk/openwrt/include/site/mips-openwrt-linux-uclibc | #!/bin/sh | | . $TOPDIR/include/site/mips-linux | . $TOPDIR/include/site/linux-uclibc | configure:2414: checking build system type configure:2428: result: x86_64-pc-linux-gnu configure:2448: checking host system type configure:2461: result: mips-openwrt-linux-gnu configure:2497: checking for a BSD-compatible install configure:2565: result: /usr/bin/install -c configure:2576: checking whether build environment is sane configure:2626: result: yes configure:2675: checking for mips-openwrt-linux-strip configure:2702: result: mips-openwrt-linux-uclibc-strip configure:2767: checking for a thread-safe mkdir -p configure:2806: result: /bin/mkdir -p configure:2819: checking for gawk configure:2835: found /usr/bin/gawk configure:2846: result: gawk configure:2857: checking whether make sets $(MAKE) configure:2879: result: yes configure:2970: checking whether to enable maintainer-specific portions of Makefiles configure:2979: result: yes configure:3005: checking whether make supports nested variables configure:3022: result: yes configure:3039: checking for cross-compiler configure:3048: result: gcc configure:3063: checking for mips-openwrt-linux-gcc configure:3090: result: gcc configure:3359: checking for C compiler version configure:3368: gcc --version 5 gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3379: $? = 0 configure:3368: gcc -v 5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
Re: [OpenWrt-Devel] [PATCH] [dnsmasq] support enforced start-IP, end-IP, netmask
On 09/10/2014 17:07, Bastian Bittorf wrote:
[dnsmasq] support enforced start-IP, end-IP, netmask
there are corner cases where the simple setup via start/end/limit
option does not fit, in our case we need to hand out
192.168.2.1 ... 192.168.2.254 with a netmask of /24 but
the underlying interface has 192.168.0.1/16 so the smart
autodetection method of the init-script does not work.
our section looks like:
config dhcp 'roaming'
option interface 'voyager'
option force_netmask 255.255.255.0
option force_startaddr 192.168.2.1
option force_endaddr 192.168.2.254
we use the setup for having an decentralized roaming
mechanism for an OLSR-mesh-network.
Hi,
this feature already exists. use the netmask option inside the dhcp section
John
Signed-off-by: Bastian Bittorf bitt...@bluebottle.com
---
package/network/services/dnsmasq/files/dnsmasq.init |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/network/services/dnsmasq/files/dnsmasq.init
b/package/network/services/dnsmasq/files/dnsmasq.init
index 942acd7..3c0399b 100644
--- a/package/network/services/dnsmasq/files/dnsmasq.init
+++ b/package/network/services/dnsmasq/files/dnsmasq.init
@@ -406,6 +406,9 @@ dhcp_add() {
config_get leasetime $cfg leasetime
config_get options $cfg options
config_get_bool dynamicdhcp $cfg dynamicdhcp 1
+ config_get force_netmask $cfg force_netmask
+ config_get force_startaddr $cfg force_startaddr
+ config_get force_endaddr $cfg force_endaddr
leasetime=${leasetime:-12h}
start=$(dhcp_calc ${start:-100})
@@ -413,7 +416,7 @@ dhcp_add() {
[ $limit -gt 0 ] limit=$((limit-1))
eval $(ipcalc.sh ${subnet%%/*} $netmask $start $limit)
if [ $dynamicdhcp = 0 ]; then END=static; fi
- xappend
--dhcp-range=$networkid,$START,$END,$NETMASK,$leasetime${options:+ $options}
+ xappend
--dhcp-range=$networkid,${force_startaddr:-$START},${force_endaddr:-$END},${force_netmask:-$NETMASK},$leasetime${options:+
$options}
dhcp_option_add $cfg $networkid
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [dnsmasq] support enforced start-IP, end-IP, netmask
try this
config dhcp 'roaming'
option interface 'voyager'
option netmask '255.255.255.0'
option start 1
option limit 253
On 14/10/2014 12:25, John Crispin wrote:
On 09/10/2014 17:07, Bastian Bittorf wrote:
[dnsmasq] support enforced start-IP, end-IP, netmask
there are corner cases where the simple setup via start/end/limit
option does not fit, in our case we need to hand out
192.168.2.1 ... 192.168.2.254 with a netmask of /24 but
the underlying interface has 192.168.0.1/16 so the smart
autodetection method of the init-script does not work.
our section looks like:
config dhcp 'roaming'
option interface 'voyager'
option force_netmask 255.255.255.0
option force_startaddr 192.168.2.1
option force_endaddr 192.168.2.254
we use the setup for having an decentralized roaming
mechanism for an OLSR-mesh-network.
Hi,
this feature already exists. use the netmask option inside the dhcp section
John
Signed-off-by: Bastian Bittorf bitt...@bluebottle.com
---
package/network/services/dnsmasq/files/dnsmasq.init |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/network/services/dnsmasq/files/dnsmasq.init
b/package/network/services/dnsmasq/files/dnsmasq.init
index 942acd7..3c0399b 100644
--- a/package/network/services/dnsmasq/files/dnsmasq.init
+++ b/package/network/services/dnsmasq/files/dnsmasq.init
@@ -406,6 +406,9 @@ dhcp_add() {
config_get leasetime $cfg leasetime
config_get options $cfg options
config_get_bool dynamicdhcp $cfg dynamicdhcp 1
+config_get force_netmask $cfg force_netmask
+config_get force_startaddr $cfg force_startaddr
+config_get force_endaddr $cfg force_endaddr
leasetime=${leasetime:-12h}
start=$(dhcp_calc ${start:-100})
@@ -413,7 +416,7 @@ dhcp_add() {
[ $limit -gt 0 ] limit=$((limit-1))
eval $(ipcalc.sh ${subnet%%/*} $netmask $start $limit)
if [ $dynamicdhcp = 0 ]; then END=static; fi
-xappend
--dhcp-range=$networkid,$START,$END,$NETMASK,$leasetime${options:+
$options}
+xappend
--dhcp-range=$networkid,${force_startaddr:-$START},${force_endaddr:-$END},${force_netmask:-$NETMASK},$leasetime${options:+
$options}
dhcp_option_add $cfg $networkid
}
___
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] [PATCH] mpc85xx: use wpad-mini in WDR4900 profile instead of wpad
applied in r42896, sorry about that ... On 14/10/2014 10:02, Philipp Borgers wrote: Someone accepted the patch in patchwork [1] but as far as I can see nobody applied the patch. Could someone with the appropriate priveleges apply the patch please? Thanks a lot Philipp On Wed, Aug 06, 2014 at 02:09:09PM +0200, Philipp Borgers wrote: This change makes the profile of WDR4900 more consistent with other router specific profiles. Signed-off-by: Philipp Borgers borg...@mi.fu-berlin.de --- target/linux/mpc85xx/profiles/tp-link.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mpc85xx/profiles/tp-link.mk b/target/linux/mpc85xx/profiles/tp-link.mk index abab0f0..47ddacd 100644 --- a/target/linux/mpc85xx/profiles/tp-link.mk +++ b/target/linux/mpc85xx/profiles/tp-link.mk @@ -9,7 +9,7 @@ define Profile/TLWDR4900 NAME:=TP-Link TL-WDR4900 PACKAGES:=\ kmod-usb-core kmod-usb2 kmod-usb2-fsl \ -kmod-ath9k wpad +kmod-ath9k wpad-mini endef define Profile/TLWDR4900/Description -- 2.0.1 ___ 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] [PATCH] mpc85xx: use wpad-mini in WDR4900 profile instead of wpad
On 14/10/14 13:32, John Crispin wrote: applied in r42896, sorry about that ... If it's not much trouble maybe BB branch too? I just got my wdr4900 today ;-) On 14/10/2014 10:02, Philipp Borgers wrote: Someone accepted the patch in patchwork [1] but as far as I can see nobody applied the patch. Could someone with the appropriate priveleges apply the patch please? Thanks a lot Philipp On Wed, Aug 06, 2014 at 02:09:09PM +0200, Philipp Borgers wrote: This change makes the profile of WDR4900 more consistent with other router specific profiles. Signed-off-by: Philipp Borgers borg...@mi.fu-berlin.de --- target/linux/mpc85xx/profiles/tp-link.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mpc85xx/profiles/tp-link.mk b/target/linux/mpc85xx/profiles/tp-link.mk index abab0f0..47ddacd 100644 --- a/target/linux/mpc85xx/profiles/tp-link.mk +++ b/target/linux/mpc85xx/profiles/tp-link.mk @@ -9,7 +9,7 @@ define Profile/TLWDR4900 NAME:=TP-Link TL-WDR4900 PACKAGES:=\ kmod-usb-core kmod-usb2 kmod-usb2-fsl \ - kmod-ath9k wpad + kmod-ath9k wpad-mini endef define Profile/TLWDR4900/Description -- 2.0.1 ___ 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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mpc85xx: use wpad-mini in WDR4900 profile instead of wpad
On 14/10/2014 12:33, Daniel Petre wrote: On 14/10/14 13:32, John Crispin wrote: applied in r42896, sorry about that ... If it's not much trouble maybe BB branch too? I just got my wdr4900 today ;-) applied in r42898 On 14/10/2014 10:02, Philipp Borgers wrote: Someone accepted the patch in patchwork [1] but as far as I can see nobody applied the patch. Could someone with the appropriate priveleges apply the patch please? Thanks a lot Philipp On Wed, Aug 06, 2014 at 02:09:09PM +0200, Philipp Borgers wrote: This change makes the profile of WDR4900 more consistent with other router specific profiles. Signed-off-by: Philipp Borgers borg...@mi.fu-berlin.de --- target/linux/mpc85xx/profiles/tp-link.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mpc85xx/profiles/tp-link.mk b/target/linux/mpc85xx/profiles/tp-link.mk index abab0f0..47ddacd 100644 --- a/target/linux/mpc85xx/profiles/tp-link.mk +++ b/target/linux/mpc85xx/profiles/tp-link.mk @@ -9,7 +9,7 @@ define Profile/TLWDR4900 NAME:=TP-Link TL-WDR4900 PACKAGES:=\ kmod-usb-core kmod-usb2 kmod-usb2-fsl \ - kmod-ath9k wpad +kmod-ath9k wpad-mini endef define Profile/TLWDR4900/Description -- 2.0.1 ___ 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 ___ 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
[OpenWrt-Devel] [PATCH] lantiq: allow pcie to be disabled by dts + vgv7519 fix pci irq + disable pcie by dts
Signed-off-by: Eddi De Pieri e...@depieri.net
---
target/linux/lantiq/dts/VGV7519.dtsi |6 ++-
.../0151-lantiq-ifxmips_pcie-use-of.patch | 51
2 files changed, 56 insertions(+), 1 deletion(-)
create mode 100644
target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
diff --git a/target/linux/lantiq/dts/VGV7519.dtsi
b/target/linux/lantiq/dts/VGV7519.dtsi
index 146d06a..e67c07f 100644
--- a/target/linux/lantiq/dts/VGV7519.dtsi
+++ b/target/linux/lantiq/dts/VGV7519.dtsi
@@ -206,11 +206,15 @@
lantiq,delay-lo = 0; /* 0.0ns delay */
interrupt-map-mask = 0xf800 0x0 0x0 0x7;
interrupt-map =
- 0x7000 0 0 1 icu0 29 1 // slot 14, irq 29
+ 0x7000 0 0 1 icu0 30 1 // slot 14, irq 30
;
gpio-reset = gpio 21 0;
req-mask = 0x1; /* GNT1 */
};
+
+ pcie@d90 {
+ status = disabled;
+ };
};
gphy-xrx200 {
diff --git
a/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
b/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
new file mode 100644
index 000..eeffa88
--- /dev/null
+++ b/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
@@ -0,0 +1,51 @@
+--- linux-3.14.18.orig/arch/mips/pci/ifxmips_pcie.c2014-09-27
14:55:19.0 +0200
linux-3.14.18/arch/mips/pci/ifxmips_pcie.c 2014-10-09 13:45:12.0
+0200
+@@ -18,6 +18,8 @@
+ #include linux/pci_regs.h
+ #include linux/module.h
+
++#include linux/of_platform.h
++
+ #include ifxmips_pcie.h
+ #include ifxmips_pcie_reg.h
+
+@@ -1048,7 +1050,7 @@
+ extern int (*ltq_pci_plat_arch_init)(struct pci_dev *dev);
+ extern int (*ltq_pci_map_irq)(const struct pci_dev *dev, u8 slot, u8 pin);
+
+-static int __init ifx_pcie_bios_init(void)
++static int __init ifx_pcie_bios_probe(struct platform_device *pdev)
+ {
+ void __iomem *io_map_base;
+ int pcie_port;
+@@ -1090,6 +1092,30 @@
+
+ return 0;
+ }
++
++static const struct of_device_id ifxmips_pcie_match[] = {
++{ .compatible = lantiq,pcie-xrx200 },
++{},
++};
++MODULE_DEVICE_TABLE(of, ifxmips_pcie_match);
++
++static struct platform_driver ltq_pci_driver = {
++.probe = ifx_pcie_bios_probe,
++.driver = {
++.name = pcie-xrx200,
++.owner = THIS_MODULE,
++.of_match_table = ifxmips_pcie_match,
++},
++};
++
++int __init ifx_pcie_bios_init(void)
++{
++int ret = platform_driver_register(ltq_pci_driver);
++if (ret)
++pr_info(pcie-xrx200: Error registering platform driver!);
++return ret;
++}
++
+ arch_initcall(ifx_pcie_bios_init);
+
+ MODULE_LICENSE(GPL);
--
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: allow pcie to be disabled by dts + vgv7519 fix pci irq + disable pcie by dts
applied in r42907, can we get the matching patch for BB please ?
On 14/10/2014 12:53, Eddi De Pieri wrote:
Signed-off-by: Eddi De Pieri e...@depieri.net
---
target/linux/lantiq/dts/VGV7519.dtsi |6 ++-
.../0151-lantiq-ifxmips_pcie-use-of.patch | 51
2 files changed, 56 insertions(+), 1 deletion(-)
create mode 100644
target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
diff --git a/target/linux/lantiq/dts/VGV7519.dtsi
b/target/linux/lantiq/dts/VGV7519.dtsi
index 146d06a..e67c07f 100644
--- a/target/linux/lantiq/dts/VGV7519.dtsi
+++ b/target/linux/lantiq/dts/VGV7519.dtsi
@@ -206,11 +206,15 @@
lantiq,delay-lo = 0; /* 0.0ns delay */
interrupt-map-mask = 0xf800 0x0 0x0 0x7;
interrupt-map =
- 0x7000 0 0 1 icu0 29 1 // slot 14, irq 29
+ 0x7000 0 0 1 icu0 30 1 // slot 14, irq 30
;
gpio-reset = gpio 21 0;
req-mask = 0x1; /* GNT1 */
};
+
+ pcie@d90 {
+ status = disabled;
+ };
};
gphy-xrx200 {
diff --git
a/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
b/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
new file mode 100644
index 000..eeffa88
--- /dev/null
+++ b/target/linux/lantiq/patches-3.14/0151-lantiq-ifxmips_pcie-use-of.patch
@@ -0,0 +1,51 @@
+--- linux-3.14.18.orig/arch/mips/pci/ifxmips_pcie.c 2014-09-27
14:55:19.0 +0200
linux-3.14.18/arch/mips/pci/ifxmips_pcie.c 2014-10-09
13:45:12.0 +0200
+@@ -18,6 +18,8 @@
+ #include linux/pci_regs.h
+ #include linux/module.h
+
++#include linux/of_platform.h
++
+ #include ifxmips_pcie.h
+ #include ifxmips_pcie_reg.h
+
+@@ -1048,7 +1050,7 @@
+ extern int (*ltq_pci_plat_arch_init)(struct pci_dev *dev);
+ extern int (*ltq_pci_map_irq)(const struct pci_dev *dev, u8 slot, u8 pin);
+
+-static int __init ifx_pcie_bios_init(void)
++static int __init ifx_pcie_bios_probe(struct platform_device *pdev)
+ {
+ void __iomem *io_map_base;
+ int pcie_port;
+@@ -1090,6 +1092,30 @@
+
+ return 0;
+ }
++
++static const struct of_device_id ifxmips_pcie_match[] = {
++{ .compatible = lantiq,pcie-xrx200 },
++{},
++};
++MODULE_DEVICE_TABLE(of, ifxmips_pcie_match);
++
++static struct platform_driver ltq_pci_driver = {
++.probe = ifx_pcie_bios_probe,
++.driver = {
++.name = pcie-xrx200,
++.owner = THIS_MODULE,
++.of_match_table = ifxmips_pcie_match,
++},
++};
++
++int __init ifx_pcie_bios_init(void)
++{
++int ret = platform_driver_register(ltq_pci_driver);
++if (ret)
++pr_info(pcie-xrx200: Error registering platform driver!);
++return ret;
++}
++
+ arch_initcall(ifx_pcie_bios_init);
+
+ MODULE_LICENSE(GPL);
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi to all, I've applied to kernel patch for vpe committed for falcon, fixed for vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M vpe1_wired_tlb_entries=1 Now I get: [ 175.672000] Here I am: #1 [ 175.672000] Here I am: #2 [ 175.676000] Here I am: #3 [ 175.68] Here I am: #4 [ 175.68] Here I am: #5 [ 175.684000] Here I am: cpu1_base_addr: 83e0 #6 [ 175.688000] Here I am: #7 [ 175.692000] Here I am: #8 [ 175.70] Unhandled kernel unaligned access[#1]: [ 175.70] CPU: 0 PID: 1516 Comm: tapidemo Not tainted 3.14.18 #40 [ 175.70] task: 829819b0 ti: 82b54000 task.ti: 82b54000 [ 175.70] $ 0 : 77d95290 bf001f38 cc123456 [ 175.70] $ 4 : a3e0 00082280 8000 [ 175.70] $ 8 : a6e5d6ef 00080080 00ff 91008110 [ 175.70] $12 : 807f807f 293f1500 00fe00fe [ 175.70] $16 : 82b55da0 8296 8296 [ 175.70] $20 : 0001 82b55e88 [ 175.70] $24 : [ 175.70] $28 : 82b54000 82b55d60 7fd3aec8 8295ee84 [ 175.70] Hi: 1b08 [ 175.70] Lo: 6c20 [ 175.70] epc : bf001f44 0xbf001f44 [ 175.70] Not tainted [ 175.70] ra: 8295ee84 ifx_mps_download_firmware+0x378/0x43c [drv_vmmc] [ 175.70] Status: 1100fd03 KERNEL EXL IE [ 175.70] Cause : 00800014 [ 175.70] BadVA : cc123456 [ 175.70] PrId : 00019555 (MIPS 34Kc) [ 175.70] Modules linked in: rt2800pci rt2800mmio rt2800lib iptable_nat rt2x00pci rt2x00mmio rt2x00lib pppoe nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp nf_conntrack ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables drv_vmmc crc_itu_t crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables pppoatm ppp_generic slhc br2684 atm drv_tapi ipv6 eeprom_93cx6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug [ 175.70] Process tapidemo (pid: 1516, threadinfo=82b54000, task=829819b0, tls=77e7b440) [ 175.70] Stack : 829640f0 cc123456 8040bd94 80408c60 82b55e68 cf68 ffea [ 175.70]82964f90 20004f11 82b55e04 8295ad0c 0007 8296 82961b88 8294c084 [ 175.70]77d13008 00082280 829640f0 2000 2000 [ 175.70]7fe68968 2000560f 829640f0 8294fb5c 82b55ef8 82b01000 ff9c [ 175.70]8004710e 82fd9800 77d13008 000822a0 [ 175.70]... [ 175.70] Call Trace: [ 175.70] [8295ad0c] ifx_mps_ioctl+0x4c8/0x754 [drv_vmmc] [ 175.70] [8294c084] VMMC_ChipAccessInit+0xd4/0xe64 [drv_vmmc] [ 175.70] [8294fb5c] VMMC_Dev_Spec_Ioctl+0x4bc/0x5f0 [drv_vmmc] [ 175.70] [8004710e] __kfifo_alloc+0xfe/0x100 [ 175.70] [8019580c] lookup_fast+0x58/0x2e8 [ 175.70] [8004710e] __kfifo_alloc+0xfe/0x100 [ 175.70] [82846254] TAPI_Ioctl+0xd4/0xda0 [drv_tapi] [ 175.70] [800e837c] do_filp_open+0x3c/0xa4 [ 175.70] [828403a4] 0x828403a4 [ 175.70] [800f7d80] do_vfs_ioctl+0x558/0x5c0 [ 175.70] [8012e6b4] getname_flags+0x40/0x14c [ 175.70] [800f5258] do_sys_open+0x218/0x240 [ 175.70] [8001c034] SyS_ioctl+0x50/0x94 [ 175.70] [8000843c] handle_sys+0x11c/0x140 [ 175.70] [ 175.70] [ 175.70] Code: 3c06 34ca00ff 00aa4824 ac69 8c68 240cc0ff 35070100 ac67 ac600010 [ 175.984000] ---[ end trace 108c9297dfbeb9c8 ]--- It seems kernel crash on /* copy FW image to base address of CPU1 */ IFXOS_CpyFromUser ((IFX_void_t *)cpu1_base_addr, (IFX_void_t *)pFWDwnld-data, pFWDwnld-length)) Any suggestion? On Sat, Oct 11, 2014 at 5:35 PM, Eddi De Pieri e...@depieri.net wrote: Hi to all, I've started to figure out how much work is needed to support fxs on vr9 board like mine. On latest trunk : - owsip is missing (i know is bugged with 32mbram) - ltq-tapidemo is m issing - lantiq falcon fxs support seems broken It seems to me that by rebasing some patch for falcon should be possible to make vmmc for vr9 working (or at least to build for now...). You agree? Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/3] rb532: add 3.14 support / sysupgrade-support
* Roman Yeryomin leroi.li...@gmail.com [10.10.2014 13:07]: On 7 October 2014 08:32, Roman Yeryomin leroi.li...@gmail.com wrote: Signed-off-by: Roman Yeryomin ro...@advem.lv --- target/linux/rb532/config-3.14 | 148 + thanks for the patches! i have 2 x rb532 running with 3.10 - it seems at the moment there is no sysupgrade-support available. how can i flash a 'bin/rb532/openwrt-rb532-combined-jffs2-128k.bin' on a running box (also with jffs2). mtd? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/3] rb532: add 3.14 support / sysupgrade-support
On 14/10/2014 15:09, Bastian Bittorf wrote: * Roman Yeryomin leroi.li...@gmail.com [10.10.2014 13:07]: On 7 October 2014 08:32, Roman Yeryomin leroi.li...@gmail.com wrote: Signed-off-by: Roman Yeryomin ro...@advem.lv --- target/linux/rb532/config-3.14 | 148 + thanks for the patches! i have 2 x rb532 running with 3.10 - it seems at the moment there is no sysupgrade-support available. how can i flash a 'bin/rb532/openwrt-rb532-combined-jffs2-128k.bin' on a running box (also with jffs2). mtd? this part is missing in your sentence :) and then use the info so i can implement said missing feature bye, bastian ___ 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] [PATCH] [dnsmasq] support enforced start-IP, end-IP, netmask
On 10/14/14 7:07 AM, Bastian Bittorf wrote: * John Crispin blo...@openwrt.org [14.10.2014 12:36]: try this config dhcp 'roaming' option interface 'voyager' option netmask '255.255.255.0' option start 1 option limit 253 it does not work. this is my interface: Do you know: 192.168.0.0/16 with start=257, limit=253 gives range 192.168.1.1-192.168.1.253 (maybe off by one)? -- -Justin justinval...@gmail.com smime.p7s Description: S/MIME Cryptographic Signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add u-APSD and WPA-PSK-file options to hostapd
I'm sorry, I've sent the wrong diff. Actually the code is right, but the diff is based on the root filesystem and not on the source repo. I'm going to send an updated patch (actually, two patches, so it is cleaner :) ). Regards, Vittorio G ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [dnsmasq] support enforced start-IP, end-IP, netmask
Hi. it does not work. this is my interface: [...] Actually it should work just fine even without option netmask if you specify the start as ipaddr: # ipcalc.sh 192.168.0.1 16 192.168.8.1 252 IP=192.168.0.1 NETMASK=255.255.0.0 BROADCAST=192.168.255.255 NETWORK=192.168.0.0 PREFIX=16 START=192.168.8.1 END=192.168.8.251 So this should work: config dhcp 'roaming' option interface 'voyager' option start 192.168.8.1 option limit 252 ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 1/3] mac80211, hostapd: Fix hostapd_set_bss_options function call in mac80211.sh and its definition in netifd.sh
- Fix the call to hostapd_set_bss_options in mac80211.sh, since $vif is not
defined in the calling context, and $phy was not being passed to the function.
- Swap $vif and $phy in hostapd_set_bss_options, to be coherent with the old
function with the same name defined in the hostapd-common-old script.
Signed-off-by: Vittorio Gambaletta open...@vittgam.net
---
.../mac80211/files/lib/netifd/wireless/mac80211.sh |2 +-
package/network/services/hostapd/files/netifd.sh |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
index e6241de..748d0f1 100644
--- a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
+++ b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
@@ -310,7 +310,7 @@ mac80211_hostapd_setup_bss() {
hostapd_cfg=
append hostapd_cfg $type=$ifname $N
- hostapd_set_bss_options hostapd_cfg $vif || return 1
+ hostapd_set_bss_options hostapd_cfg $ifname $phy || return 1
json_get_vars wds dtim_period max_listen_int
set_default wds 0
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index 30d12e9..12c375b 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -148,8 +148,8 @@ hostapd_common_add_bss_config() {
hostapd_set_bss_options() {
local var=$1
- local phy=$2
- local vif=$3
+ local vif=$2
+ local phy=$3
wireless_vif_parse_encryption
--
1.7.9.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 3/3] hostapd: Add uapsd option to netifd.sh
The uapsd option sets the uapsd_advertisement_enabled flag in hostapd, only if
the phy actually supports the option.
Signed-off-by: Vittorio Gambaletta open...@vittgam.net
---
package/network/services/hostapd/files/netifd.sh |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index ccea5ff..48bcc9d 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -100,7 +100,7 @@ EOF
hostapd_common_add_bss_config() {
config_add_string 'bssid:macaddr' 'ssid:string'
- config_add_boolean wds wmm hidden
+ config_add_boolean wds wmm uapsd hidden
config_add_int maxassoc max_inactivity
config_add_boolean disassoc_low_ack isolate short_preamble
@@ -163,7 +163,7 @@ hostapd_set_bss_options() {
maxassoc max_inactivity disassoc_low_ack isolate auth_cache \
wps_pushbutton wps_label ext_registrar wps_pbc_in_m1 \
wps_device_type wps_device_name wps_manufacturer wps_pin \
- macfilter ssid wmm hidden short_preamble rsn_preauth
+ macfilter ssid wmm uapsd hidden short_preamble rsn_preauth
set_default isolate 0
set_default maxassoc 0
@@ -172,6 +172,7 @@ hostapd_set_bss_options() {
set_default disassoc_low_ack 1
set_default hidden 0
set_default wmm 1
+ set_default uapsd 1
append bss_conf ctrl_interface=/var/run/hostapd
if [ $isolate -gt 0 ]; then
@@ -189,6 +190,10 @@ hostapd_set_bss_options() {
append bss_conf wmm_enabled=$wmm $N
append bss_conf ignore_broadcast_ssid=$hidden $N
+ [ -n $phy ] iw phy $phy info 2/dev/null | grep -q 'Device
supports AP-side u-APSD.' {
+ append bss_conf uapsd_advertisement_enabled=$uapsd $N
+ }
+
[ $wpa -gt 0 ] {
[ -n $wpa_group_rekey ] append bss_conf
wpa_group_rekey=$wpa_group_rekey $N
[ -n $wpa_pair_rekey ] append bss_conf
wpa_ptk_rekey=$wpa_pair_rekey$N
--
1.7.9.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 2/3] hostapd: Add wpa_psk_file option to netifd.sh
The wpa_psk_file option offers the possibility to use a different WPA-PSK key
for each client. The directive points to a file with the following syntax:
mac_address wpa_passphrase_or_hex_key
Example:
00:11:22:33:44:55 passphrase_for_client_1
00:11:22:33:44:67 passphrase_for_client_2
00:11:22:33:44:89
0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
So it is possible to specify both ASCII passphrases and raw 64-chars hex keys.
Signed-off-by: Vittorio Gambaletta open...@vittgam.net
---
package/network/services/hostapd/files/netifd.sh |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index 12c375b..ccea5ff 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -134,6 +134,8 @@ hostapd_common_add_bss_config() {
config_add_string 'key1:wepkey' 'key2:wepkey' 'key3:wepkey'
'key4:wepkey' 'password:wpakey'
+ config_add_string wpa_psk_file
+
config_add_boolean wps_pushbutton wps_label ext_registrar wps_pbc_in_m1
config_add_string wps_device_type wps_device_name wps_manufacturer
wps_pin
@@ -201,7 +203,7 @@ hostapd_set_bss_options() {
wps_not_configured=1
;;
psk)
- json_get_vars key
+ json_get_vars key wpa_psk_file
if [ ${#key} -lt 8 ]; then
wireless_setup_vif_failed INVALID_WPA_PSK
return 1
@@ -210,6 +212,10 @@ hostapd_set_bss_options() {
else
append bss_conf wpa_passphrase=$key $N
fi
+ [ -n $wpa_psk_file ] {
+ [ -e $wpa_psk_file ] || touch $wpa_psk_file
+ append bss_conf wpa_psk_file=$wpa_psk_file
$N
+ }
wps_possible=1
;;
eap)
--
1.7.9.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: fix spi ath79 fast read (for 3.10 kernel)
can someone who knows m25p80 better than me figure out if this is
correct please ?
On 26/07/2014 04:52, Zhao, Gang wrote:
Fast read adds a dummy byte in tx buffer if the transfer type is
SPI_TRANSFER_FLASH_READ_CMD. The dummy byte should be ignored when
calculating read address. This is done by adding a bool variable
dummy in struct spi_transfer to indicate whether this transfer
includes the dummy byte.
Signed-off-by: Zhao, Gang gang.zhao...@gmail.com ---
.../464-spi-ath79-fix-fast-flash-read.patch| 36
++ 1 file changed, 36 insertions(+) create mode
100644
target/linux/ar71xx/patches-3.10/464-spi-ath79-fix-fast-flash-read.patch
diff --git
a/target/linux/ar71xx/patches-3.10/464-spi-ath79-fix-fast-flash-read.patch
b/target/linux/ar71xx/patches-3.10/464-spi-ath79-fix-fast-flash-read.patch
new file mode 100644
index 000..6567755 --- /dev/null +++
b/target/linux/ar71xx/patches-3.10/464-spi-ath79-fix-fast-flash-read.patch
@@ -0,0 +1,36 @@
+--- a/drivers/mtd/devices/m25p80.c
b/drivers/mtd/devices/m25p80.c +@@ -360,6 +360,10 @@ static int
m25p80_read(struct mtd_info * + t[0].type =
SPI_TRANSFER_FLASH_READ_CMD; +t[0].tx_buf = flash-command; +
t[0].len = m25p_cmdsz(flash) + (flash-fast_read ? 1 : 0); ++ ++ if
(flash-fast_read) ++ t[0].dummy = true; ++ +
spi_message_add_tail(t[0], m); + + t[1].type =
SPI_TRANSFER_FLASH_READ_DATA; +--- a/drivers/spi/spi-ath79.c
b/drivers/spi/spi-ath79.c +@@ -268,6 +268,10 @@ static int
ath79_spi_do_read_flash_cmd(s + sp-read_addr = 0; + + len =
t-len - 1; ++ ++ if (t-dummy) ++len -= 1; ++ + p =
t-tx_buf;
+ + while (len--) { +--- a/include/linux/spi/spi.h
b/include/linux/spi/spi.h +@@ -531,6 +531,7 @@ struct spi_transfer
{ + u16 delay_usecs; + u32 speed_hz; + enum
spi_transfer_type
type; ++ bool dummy; + + struct list_head transfer_list; + };
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Postfix on OpenWRT
Hi there,
One more bug:
In the /etc/init.d/postfix script is the function:
enable() {
group_exists postfix || group_add postfix 87
user_exists postfix || user_add postfix 87
group_exists postdrop || group_add postdrop 88
}
which covers standard /etc/rc.common routines when issuing command:
/etc/init.d/postfix enable
As a consequence symlinks in /etc/rc.d for automatic starting/stopping
postfix are not created.
--
Pozdrawiam
Grzesiek
Wysłane z kompa wolnego od wirusów Billa Gatesa.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Postfix on OpenWRT
Hi Grzegorz,
Thank you!
I have just fixed that by changing the name of the function.
Best regards,
Denis Shulyaka
2014-10-14 22:15 GMT+04:00 Grzegorz Sójka p...@sojka.co:
Hi there,
One more bug:
In the /etc/init.d/postfix script is the function:
enable() {
group_exists postfix || group_add postfix 87
user_exists postfix || user_add postfix 87
group_exists postdrop || group_add postdrop 88
}
which covers standard /etc/rc.common routines when issuing command:
/etc/init.d/postfix enable
As a consequence symlinks in /etc/rc.d for automatic starting/stopping
postfix are not created.
--
Pozdrawiam
Grzesiek
Wysłane z kompa wolnego od wirusów Billa Gatesa.
___
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] Watchdog support for AR531x and potential lockup
2014-10-13 19:48 GMT+04:00 Sergey Korolew d...@bittu.org.ru: Hello ! 1. Watchdog timer always decrement until zero, it cant be stopped at all. SR Yep, same for AR2315+ SoCs. And if interrupt acknowledged by writing SR one to ISR, then the timer starts counting again from 0x and SR generates another one interrupt. Not for ar531x, timer does not overlapping zero on those devices even if ISR flag cleared, and, actually, produce next interrupt. So, setting timer to 0x does not harm both platforms. What do you mean, when you say that 0x does not harm? SR Hardware reset doesn't work on AR2315 since hw bug and cause freeze if SR issued by watchdog. See details in AR2315 reset routine in SR arch/mips/ar231x/ar2315.c I tested hw reset on ar531x, and it works. Are you tested it ? AR2313 and AR2317 SoCs are reset fine by watchdog, but AR2315 and AR2316 SoCs just hung. Comments in ar2315_restart function are about different situation, not watchdog reset. SR I would like to propose use different device id strings (e.g. SR ar2315-watchdog and ar5312-watchdog) to distinguish SoCs models. This SR would help to solve several issues: SR - twisted registers (passing adjacent registers via different SR resources seems a bit odd), Why ? +4-4 address play looks worse for me :) Who cares how registers placed in address map, if we can use two pointers for them ? :) Passing all registers as one block, make /proc/iomem look nicer :) SR - possibility of hardware reset, SR - detection of watchdog clock frequency, since according to Axel Gembe SR patch DWL-2100AP's watchdog timer ticks at 48MHz. Well, interrupt generated each 96 second on my DWL-2100AP, 0x/96 resulting in 44Mhz clock. I tested several boards: DWL-2100AP (AR2313), FON2202 (AR2315), LiteStation2 (AR2316), DIR-300 (AR2317) and got the following results: Board BogoMIPS Min Max Mean Stdev DWL-2100AP 179.60 47.782 49.353 47.866 0.189 FON2202 182.68 42.200 42.268 42.227 0.014 LS2 182.68 22.229 42.375 42.265 0.019 DIR-300 182.68 42.220 43.466 42.278 0.145 40 MHz - 107 seconds timeout 48 Mhz - 89 seconds 60 sec limit should be enough. For me watchdog routines should be as simple as possible, without bells and whistles because of their life-critical status. Totally agree with you. And my proposal applies only to driver initialization, and not to its main code. I will send my driver version as soon as it be ready. -- BR, Sergey ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
