From: Ben Franske
In r41872 and r42787 Dynamic VLAN support was reintroduced, but the vlan_bridge
parameter is not read while setting up the config, so the default is used which
is undesirable for some uses.
This patch should be a corrected version of
http://patchwork.openwrt.org/patch/6344/
Hi!
I just noted that there is an issue with the firmware upgrade via LuCI
on the OM2P. The image validity check fails, because the following
script in system.lua fails:
local function image_supported()
-- XXX: yay...
return ( 0 == os.execute(
On Fri, Nov 28, 2014 at 7:20 PM, Maxime Ripard
wrote:
> Switch to a dumber implementation that will be easier to maintain in the long
> run, with only if statements instead of having nested subst calls.
>
> Signed-off-by: Maxime Ripard
> ---
> include/kernel.mk | 25 +
>
On Nov 28, 2014 5:23 AM, "Heiner Kallweit" wrote:
> Anybody with a 8216-based device who can test this?
Me me me, me me.
4300 currently running trunk with 43332 reverted.
I am at your service.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.o
Hi!
The patch in the ticket solves the problem, but there seems to be another with
IPv6 NAT.
I found a way to get around the IPv6 NAT, so this is not urgent to me anymore,
in the
hope, that this error has also something to do with IPv6 NAT ;-) Perhaps there
is a better
place to report this. If
Factor out reg_port_stats_base parameters to ar8xxx_chip.
Remove related chip_is_... checks.
Signed-off-by: Heiner Kallweit
---
.../linux/generic/files/drivers/net/phy/ar8216.c | 27 --
.../linux/generic/files/drivers/net/phy/ar8216.h | 6 -
2 files changed, 20 inser
Factor out mib_func to ar8xxx_chip. Remove related chip_is_... checks.
Signed-off-by: Heiner Kallweit
---
target/linux/generic/files/drivers/net/phy/ar8216.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c
b/ta
Factor out mii_lo_first to ar8xxx_chip.
Signed-off-by: Heiner Kallweit
---
target/linux/generic/files/drivers/net/phy/ar8216.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c
b/target/linux/generic/files/drivers/
Factor out set_mirror_regs to ar8xxx_chip.
Remove related chip_is_... checks.
Signed-off-by: Heiner Kallweit
---
.../linux/generic/files/drivers/net/phy/ar8216.c | 28 ++
1 file changed, 13 insertions(+), 15 deletions(-)
diff --git a/target/linux/generic/files/drivers/net/
Factor out chip-specific data structures from ar8xxx_priv.
Signed-off-by: Heiner Kallweit
---
.../linux/generic/files/drivers/net/phy/ar8216.c | 31 +++---
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c
b/tar
Factor out info whether switch should be configured at probe stage
to ar8xxx_chip. Remove related chip_is_... checks.
Signed-off-by: Heiner Kallweit
---
target/linux/generic/files/drivers/net/phy/ar8216.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/linux/gene
This patch series factors out more chip-specific differences
to ar8xxx_chip.
1/6 factor out info whether switch should be configured at probe stage to
ar8xxx_chip
2/6 factor out mib_func to ar8xxx_chip
3/6 factor out set_mirror_regs to ar8xxx_chip
4/6 factor out chip-specific data structures from
Hi,
This is the third attempt to rely on the defconfigs mechanism instead
of generating our own full kernel configuration file.
This has been build tested, both before and after applying the first
patch on all the supported targets so far.
You can get a list of the various build runs, with both
Rely on the Kconfig defconfig mechanism to fill all the missing options,
instead of needing to set them all in the kernel configurations like what was
previously done.
This will allow to trim down a lot the configuration files, avoid carrying
unused configuration options and preserve the developer
x64 is handled by the x86 architecture in Linux, add a case for it in
LINUX_KARCH.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/kernel.mk b/include/kernel.mk
index 97eb1f74f4f7..2d15e9ad2712 100644
--- a/include/kernel.mk
+++ b/
Switch to a dumber implementation that will be easier to maintain in the long
run, with only if statements instead of having nested subst calls.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 25 +
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a/inclu
On Fri, Nov 28, 2014 at 12:15 PM, Jonas Gorski wrote:
> On Fri, Nov 28, 2014 at 11:06 AM, Heiner Kallweit
> wrote:
> > In my tests with AR8327 this callback was never called with an addr != 0.
> > Seems logical to me as it's called for the PHY attached to the net device
> > only.
> >
> > In most
The following changes since commit 3ecf78cea81128e20d4679f258fb596e8ae09124:
kernel: 3.18: Fix patch 644 dependency chain (2014-11-28 01:29:51 +)
are available in the git repository at:
https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git
for you to fetch changes up to 627377b2fdf665c
On Fri, Nov 28, 2014 at 11:06 AM, Heiner Kallweit wrote:
> In my tests with AR8327 this callback was never called with an addr != 0.
> Seems logical to me as it's called for the PHY attached to the net device
> only.
>
> In most cases this is addr 0, just for AR8316 with port4_phy being set this
>
This bug report relates to a device using the AR8216 switch chip and a
trunk version where the additional phy reset in 3.14 was still enabled.
Seems like there was an issue with autoneg. This is not fully clear to me
as after the first phy reset in the kernel phy code we do the hw_init in
the driv
In my tests with AR8327 this callback was never called with an addr != 0.
Seems logical to me as it's called for the PHY attached to the net device
only.
In most cases this is addr 0, just for AR8316 with port4_phy being set this
could be 4.
This leads to two questions:
1. The current version of
21 matches
Mail list logo
