On 20 December 2015 at 22:56, Florian Fainelli wrote:
> Le 16 déc. 2015 09:21, "Rafał Miłecki" a écrit :
>>
>> When using cli, print link state the same way kernel used to do it.
>> This will allow kernel switching PORT_LINK from SWITCH_TYPE_STRING.
>>
>> Signed-off-by: Rafał Miłecki
>> ---
> [s
On 20 December 2015 at 19:23, Stefan Rompf wrote:
> On Mittwoch, 16. Dezember 2015 18:19:01 Rafał Miłecki wrote:
>
>> So far we were sending link data as a string. It got some drawbacks:
>> 1) Didn't allow writing clean user space apps reading link state. It was
>>needed to do some screen scra
2015-12-21 12:03 GMT+08:00 xinglp :
> 2015-12-21 0:20 GMT+08:00 Felix Fietkau :
>> On 2015-12-20 17:00, Arjen de Korte wrote:
>>> Citeren Felix Fietkau :
>>>
On 2015-12-20 11:52, Arjen de Korte wrote:
> Since commit 47771 it seems my WNDR4300 router suffers from a memory
> leak. Before
2015-12-21 0:20 GMT+08:00 Felix Fietkau :
> On 2015-12-20 17:00, Arjen de Korte wrote:
>> Citeren Felix Fietkau :
>>
>>> On 2015-12-20 11:52, Arjen de Korte wrote:
Since commit 47771 it seems my WNDR4300 router suffers from a memory
leak. Before then, the amount of free memory was always
Le 16 déc. 2015 09:21, "Rafał Miłecki" a écrit :
>
> When using cli, print link state the same way kernel used to do it.
> This will allow kernel switching PORT_LINK from SWITCH_TYPE_STRING.
>
> Signed-off-by: Rafał Miłecki
> ---
[snip]
> + link->eee &
SWLIB_LINK_FLA
Le 16 déc. 2015 09:19, "Rafał Miłecki" a écrit :
>
> So far we were sending link data as a string. It got some drawbacks:
> 1) Didn't allow writing clean user space apps reading link state. It was
>needed to do some screen scraping.
> 2) Forced whole PORT_LINK communication to be string based.
Hello,
On Sunday, December 20, 2015 08:20:12 PM Roman Yeryomin wrote:
> On 20 December 2015 at 15:13, Christian Lamparter
> wrote:
> > On Sunday, December 20, 2015 02:30:39 AM Roman Yeryomin wrote:
> >> Some (possibly broken) bootloaders incorreclty initialize at8033
> >> phy. This patch enables
Signed-off-by: Roman Yeryomin
---
target/linux/rb532/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/rb532/Makefile b/target/linux/rb532/Makefile
index 3086462..9033eb4 100644
--- a/target/linux/rb532/Makefile
+++ b/target/linux/rb532/Makefile
@@ -11,7 +1
Signed-off-by: Roman Yeryomin
---
target/linux/rb532/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/rb532/Makefile b/target/linux/rb532/Makefile
index e5c6ad7..3086462 100644
--- a/target/linux/rb532/Makefile
+++ b/target/linux/rb532/Makefile
@@ -9,7 +9,
4.1 got little bit larger than 4MB and I couldn't get lzma loader
working on this platform
Signed-off-by: Roman Yeryomin
---
target/linux/rb532/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/rb532/image/Makefile
b/target/linux/rb532/image/Makefil
Hi Rafał,
On Mittwoch, 16. Dezember 2015 18:19:01 Rafał Miłecki wrote:
> So far we were sending link data as a string. It got some drawbacks:
> 1) Didn't allow writing clean user space apps reading link state. It was
>needed to do some screen scraping.
> 2) Forced whole PORT_LINK communicatio
On 20 December 2015 at 15:13, Christian Lamparter
wrote:
> Hello,
>
> On Sunday, December 20, 2015 02:30:39 AM Roman Yeryomin wrote:
>> Some (possibly broken) bootloaders incorreclty initialize at8033
>> phy. This patch enables sgmii autonegotiation mode.
>>
>> Signed-off-by: Roman Yeryomin
>> --
On 2015-12-20 17:00, Arjen de Korte wrote:
> Citeren Felix Fietkau :
>
>> On 2015-12-20 11:52, Arjen de Korte wrote:
>>> Since commit 47771 it seems my WNDR4300 router suffers from a memory
>>> leak. Before then, the amount of free memory was always around 75%,
>>> but since then it steadily decre
Citeren Felix Fietkau :
On 2015-12-20 11:52, Arjen de Korte wrote:
Since commit 47771 it seems my WNDR4300 router suffers from a memory
leak. Before then, the amount of free memory was always around 75%,
but since then it steadily decreases until it runs out of memory and
reboots. The process t
Hello,
I tried to compile and test trunk on two Linksys-routers (1200AC and
1900ACv2). After manually enabling the Generic Thermal sysfs driver,
compilation went fine. However, none of the routers want to boot.
Hooking up a serial shows what seems to be a filsystem issue, the
following error is re
Hello,
On Sunday, December 20, 2015 02:30:39 AM Roman Yeryomin wrote:
> Some (possibly broken) bootloaders incorreclty initialize at8033
> phy. This patch enables sgmii autonegotiation mode.
>
> Signed-off-by: Roman Yeryomin
> ---
Can you tell us a bit about the "possibly broken" bootloaders you
On 2015-12-20 11:52, Arjen de Korte wrote:
> Since commit 47771 it seems my WNDR4300 router suffers from a memory
> leak. Before then, the amount of free memory was always around 75%,
> but since then it steadily decreases until it runs out of memory and
> reboots. The process then starts all
Since commit 47771 it seems my WNDR4300 router suffers from a memory
leak. Before then, the amount of free memory was always around 75%,
but since then it steadily decreases until it runs out of memory and
reboots. The process then starts all over again. After a couple of
days of 'git bisec
Hi,
I'm bumping again, this patch is necessary to make the gigabit switch work
on the Mikrotik 951G-2HnD (tested on CC).
Thanks,
Baptiste
On Wed, Nov 25, 2015 at 06:18:29PM +0100, Baptiste Jonglez wrote:
> Hi,
>
> Sorry to bump up the thread again. Is there anything blocking to merge
> this pa
Hi,
Any news on this patch? As requested, the v2 patch introduces a
configuration knob to disable requesting option 121.
Thanks,
Baptiste
On Fri, Nov 20, 2015 at 11:50:56PM +0100, Baptiste Jonglez wrote:
> From: Baptiste Jonglez
>
> This option is useful when the gateway configured by DHCP ca
> "John" == John Crispin writes:
John> i'll try to test during the day. i had tested most socs but
John> apparently 5350 still has an issue.
Yes, I saw this too, and was about to report it. I'm seeing it on an
AsiaRF AWM002, which is also an RT5350.
swconfig list returns nothing, fwiw.
Hi all,
I've been working on a patch for making POSIX ACL support and userspace
support of POSIX ACL and XATTR (extended attributes) a configuration
option at compile time and noticed something rather wonky:
While for POSIX ACL the default is disabled both at the kernel
level and in userpace
22 matches
Mail list logo
