we wont backport this to AA and probably not to BB until it is properly
tested in CC
On 03/12/2014 04:55, Fernando Frediani wrote:
> Hi all,
>
> It would be great if someone could port ZRAM to AA so it can be used on
> 16MB devices too.
> Despite the kernel version doesn't have it, it had sever
On 03/12/2014 07:10, Rafał Miłecki wrote:
> Honestly, I don't know what is this file for. I don't understand
> netifd & wireless well at all. I asked for help in the Request for
> any netifd wireless documentation e-mail thread, but ppl who know
> /things/ ignored me.
can you narrow down your q
Don't restore original device settings based on the device settings flags in
system_if_down
as device flags are already reset when the device config is deleted.
Therefore move the masking of the relevant original device settings to
system_if_up.
Signed-off-by: Hans Dedecker
---
system-linux.c
Fix setup race condition when proto shell is in teardown or setup_abort state
when setup cmd is received.
Don't change the proto shell state and launch no setup in these conditions so
the proto shell teardown
timeout handler does not kill the wrong processes and proto_shell_task_finish
takes act
Improves code readibility regarding state transitions when handling teardown
event
Signed-off-by: Hans Dedecker
---
proto-shell.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/proto-shell.c b/proto-shell.c
index 86933b0..977cdbc 100644
-
Config support to force the IGMP host version on device level; possible values
are:
1|igmpv1: IGMP version 1
2|igmpv2: IGMP version 2
3|igmpv3: IGMP version 3
Signed-off-by: Hans Dedecker
---
device.c | 11 +++
device.h | 3 +++
system-dummy.c | 6 ++
syste
On 2014-12-03 11:15, Hans Dedecker wrote:
> Config support to force the IGMP host version on device level; possible
> values are:
> 1|igmpv1: IGMP version 1
> 2|igmpv2: IGMP version 2
> 3|igmpv3: IGMP version 3
>
> Signed-off-by: Hans Dedecker
I'd prefer to leave out support for the
On 03.12.2014 11:15, Hans Dedecker wrote:
Config support to force the IGMP host version on device level; possible values
are:
1|igmpv1: IGMP version 1
2|igmpv2: IGMP version 2
3|igmpv3: IGMP version 3
Thanks Hans.
However, I don't really see the point of the string logic, it s
From: Karl Palsson
Plain "remote" results in failure to connect using the gdb built with
the toolchain. (On atheros target at least) extended-remote also allows
"run" to restart the target process.
Signed-off-by: Karl Palsson
---
scripts/remote-gdb | 2 +-
1 file changed, 1 insertion(+), 1 de
oldconfig kept asking for that config symbol...
PHY_SAMSUNG_USB2 depends on DWC2
diff --git a/target/linux/generic/config-3.18
b/target/linux/generic/config-3.18
index e0e2a0b..d014334 100644
--- a/target/linux/generic/config-3.18
+++ b/target/linux/generic/config-3.18
@@ -2560,6 +2560,7 @@ CONFI
On Wed, Dec 3, 2014 at 11:23 AM, Steven Barth wrote:
> On 03.12.2014 11:15, Hans Dedecker wrote:
>
>> Config support to force the IGMP host version on device level; possible
>> values are:
>> 1|igmpv1: IGMP version 1
>> 2|igmpv2: IGMP version 2
>> 3|igmpv3: IGMP version 3
>>
>
>
>
On 03.12.2014 11:39, Hans Dedecker wrote:
Regarding the MLD version wouldn't it be preferable to have this as a
different UCI parameter as I could imagine different versions in use
for MLD and IGMP. Quite a lot of ISP's are still stuck to IGMPv2 in
their network while they're using MLDv2 for
KD20 got an IC+ phy, without the driver the phy is not properly
initialized resulting in ethernet not working unless being already
initialized by the vendor loader.
upstream commit 368b4d2b49bbbf379d9334747fbbd2fe4356
drivers: net: remove dead drivers
removed icplus.c due to the lack of in-tre
This is what the vendor bootloader does on KD20.
Signed-off-by: Daniel Golle
---
package/boot/uboot-oxnas/patches/200-icplus-phy.patch | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/package/boot/uboot-oxnas/patches/200-icplus-phy.patch
b/package/boot/uboot-o
Signed-off-by: Daniel Golle
---
package/boot/uboot-envtools/files/oxnas | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/package/boot/uboot-envtools/files/oxnas
b/package/boot/uboot-envtools/files/oxnas
index b456fb3..063ffa0 100644
--- a/package/boot/uboot-envtools/file
buildslave4 has destroyed 3/4 of snapshot builds by rapidly failing them and
preventing other buildslaves to try those target plaforms. The slave has been
broken for almost a week. For several platforms the last succesful build has
been 28-Nov, 5 days ago.
(Only those builds succeed that get
i recently removed the driver from the ralink kernel as it made the
link unstable. how does the phy behave for you without the drive
strength quirk ? does the linux phy driver work for you on this HW ?
i looked for the datasheet but failed to find it. do you have it ?
On 03/12/2014 16:03, Daniel
BXO2000n-2S/BXO5000n-2S/BXI2000n-2/BXO2000n-2S-U are 4 BHU Networks WLAN
boards, use ar9341 and ar9344 chip.
I also merge BXU2000n-2 board to same file for all BHU devices.
Signed-off-by: Terry Yang
Index: target/linux/ar71xx/base-files/etc/diag.sh
==
Hi,
patches for new boards are always welcome, a few comments below
On 04/12/2014 08:23, yangbo wrote:
> +/*
> + * BHU BXO2000n-2S-U board
> + */
> +
> +static void __init bhu_bxo2000n2s_u_setup(void)
> +{
> + bhu_ap123_setup((u8 *) KSEG1ADDR(0x1fff), (u8 *)
> KSEG1ADDR(0x1fff1000));
> +
19 matches
Mail list logo
