Hi there.
After issuing the following commands:
wget
https://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2
-O - | tar xj
cd OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2
On Wednesday 12 November 2014 16:39:38 André Gaul wrote:
Hey openwrt devs!
I'm observing 100% reproducible kernel oopses with a recent openwrt
(tested with trunk and barrier breaker) on a Mikrotik Routerboard RB435
which is equipped with 5 minipci cards. The board boots up fine if all
wifi
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/config-3.10| 1 +
target/linux/ar71xx/config-3.14| 1 +
.../ar71xx/files/arch/mips/ath79/mach-mr900.c | 158 +
.../730-MIPS-ath79-add-mr900-support.patch
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +++
target/linux/ar71xx/base-files/etc/uci-defaults/01_leds| 6 ++
target/linux/ar71xx/base-files/etc/uci-defaults/02_network | 1 +
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
package/kernel/om-watchdog/files/om-watchdog.init | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/kernel/om-watchdog/files/om-watchdog.init
b/package/kernel/om-watchdog/files/om-watchdog.init
index 3479522..eb24226 100644
---
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
package/boot/uboot-envtools/files/ar71xx | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/boot/uboot-envtools/files/ar71xx
b/package/boot/uboot-envtools/files/ar71xx
index f660883..fb3d3e9 100644
---
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh | 7 ++-
target/linux/ar71xx/base-files/lib/upgrade/platform.sh | 2 ++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/files/arch/mips/ath79/mach-mr900.c | 1 +
.../patches-3.10/731-MIPS-ath79-add-mr900v2-support.patch | 10 ++
.../patches-3.14/731-MIPS-ath79-add-mr900v2-support.patch | 10 ++
3 files
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
scripts/om-fwupgradecfg-gen.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/om-fwupgradecfg-gen.sh b/scripts/om-fwupgradecfg-gen.sh
index 8869059..e132954 100644
--- a/scripts/om-fwupgradecfg-gen.sh
+++
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 ++-
target/linux/ar71xx/base-files/etc/uci-defaults/01_leds| 3 ++-
target/linux/ar71xx/base-files/etc/uci-defaults/02_network | 1 +
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/generic/profiles/openmesh.mk | 11 +++
target/linux/ar71xx/image/Makefile | 3 ++-
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/generic/profiles/openmesh.mk
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
package/kernel/om-watchdog/files/om-watchdog.init | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/om-watchdog/files/om-watchdog.init
b/package/kernel/om-watchdog/files/om-watchdog.init
index eb24226..36b31da
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
package/boot/uboot-envtools/files/ar71xx | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/boot/uboot-envtools/files/ar71xx
b/package/boot/uboot-envtools/files/ar71xx
index fb3d3e9..321b537 100644
---
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh | 1 +
target/linux/ar71xx/base-files/lib/upgrade/platform.sh | 2 ++
2 files changed, 3 insertions(+)
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh
Signed-off-by: Sven Eckelmann s...@open-mesh.com
---
target/linux/ar71xx/generic/profiles/openmesh.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ar71xx/generic/profiles/openmesh.mk
b/target/linux/ar71xx/generic/profiles/openmesh.mk
index 6f714d5..100636e
When a device with the same name is deleted and created again in the kernel
the ifindex changes.
A race condition will occur when netlink event messages linked to the old device
are processed and will thus overwrite the correct ifindex of the new device.
Further make sure a valid ifindex is in
Reverse path filtering config support; possible values are:
0: no source validation
1/strict: strict mode as packet will be dropped if the
incoming interface is not the best reverse path
2/loose: loose mode as packet will be dropped if the
source address is not reachable via
Don't resolve the ifindex of the parent device again
when adding vlandev and macvlan devices as the ifindex
has already been resolved.
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
system-linux.c | 12 ++--
1 files changed, 2 insertions(+), 10 deletions(-)
diff --git
Adds support to accept packets with local source address.
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
device.c |9 +
device.h |3 +++
system-linux.c | 18 ++
3 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/device.c b/device.c
On 2014-11-13 14:35, Hans Dedecker wrote:
When a device with the same name is deleted and created again in the kernel
the ifindex changes.
A race condition will occur when netlink event messages linked to the old
device
are processed and will thus overwrite the correct ifindex of the new
On 13.11.2014 09:29, Grzegorz Sójka wrote:
#include iostream.h
That is not valid C++ anymore for including a standard header.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
On Thu, Nov 13, 2014 at 3:00 PM, Felix Fietkau n...@openwrt.org wrote:
On 2014-11-13 14:35, Hans Dedecker wrote:
When a device with the same name is deleted and created again in the
kernel
the ifindex changes.
A race condition will occur when netlink event messages linked to the
old
Am 13.11.2014 um 10:07 schrieb Tijs Van Buggenhout:
It would be more meaningful if the memory addresses of (at least the top of)
the stack trace were mapped onto their symbolic names, using the System.map
of
your kernel. You can do this manually or by using ksymoops or recompile your
Hello any body,
is there still support for ASUS USB-AC56
with Realtek RTL8812AU - 802.11ac 867Mbps (5GHz) + 300Mbps (2.4GHz)
in OpenWRT?
Thanks
signature.asc
Description: PGP signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Don't resolve the ifindex of the parent device again
when adding vlandev and macvlan devices as the ifindex
has already been resolved.
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
system-linux.c | 12 ++--
1 files changed, 2 insertions(+), 10 deletions(-)
diff --git
When a device with the same name is deleted and created again in the kernel
the ifindex changes.
A race condition will occur when netlink event messages linked to the old device
are processed and will thus overwrite the correct ifindex of the new device.
Further make sure a valid ifindex is in
Reverse path filtering config support; possible values are:
0: no source validation
1|strict: strict mode as packet will be dropped if the
incoming interface is not the best reverse path
2|loose: loose mode as packet will be dropped if the
source address is not reachable via
Adds support to accept packets with local source address.
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
device.c |9 +
device.h |3 +++
system-linux.c | 18 ++
3 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/device.c b/device.c
On 11/13/14 09:29, Grzegorz Sójka wrote:
[]
wget
https://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2
-O - | tar xj
cd OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2
Most likely a copy paste error when deriving ar8327_sw_set_ports
from ar8xxx_sw_set_ports.
Remove unused variable.
Signed-off-by: Heiner Kallweit hkallwe...@gmail.com
---
target/linux/generic/files/drivers/net/phy/ar8216.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
See also ticket 17800
With kernel=3.14 autonegotiation is disabled at least for AR8327 based
switches. Reason is that with 3.14 an additional phy reset was
introduced in phy_init_hw in drivers/net/phy/phy_device.c
This reset clears BMCR_ANENABLE.
After the reset phy_init_hw calls the driver's
On 2014-11-13 22:00, Heiner Kallweit wrote:
See also ticket 17800
With kernel=3.14 autonegotiation is disabled at least for AR8327 based
switches. Reason is that with 3.14 an additional phy reset was
introduced in phy_init_hw in drivers/net/phy/phy_device.c
This reset clears BMCR_ANENABLE.
Am 13.11.2014 um 22:18 schrieb Felix Fietkau:
On 2014-11-13 22:00, Heiner Kallweit wrote:
See also ticket 17800
With kernel=3.14 autonegotiation is disabled at least for AR8327 based
switches. Reason is that with 3.14 an additional phy reset was
introduced in phy_init_hw in
Hi, all,
i try to compile openwrt with external toolchain, and it fails when
compile ther kernel.
i check the TARGET_CROSS in rules.mk and make a little modification.
and compile success.
i don't know if someone has fixed this issue. the patch below works well
on my environment.
diff
Hi, all,
i try to compile openwrt with external toolchain, and it fails when
compile ther kernel.
i check the TARGET_CROSS in rules.mk and make a little modification.
and compile success.
i don't know if someone has fixed this issue. the patch below works well
on my environment.
diff
35 matches
Mail list logo
