Re: [LEDE-DEV] issue with rt61-pci

Hi, It seems that this issue is due to DMA. But... i can't find where is the setup of dma for pci bus for bcm6358 Regards On Sun, Sep 25, 2016 at 9:39 AM, Eddi De Pieri wrote: > Hi, > > I've just flashed an old device with onboard a rt2661 pci card. > > > Lede-Trunk/Openwrt

[LEDE-DEV] [PATCH] scripts/feeds: use git rev-parse for getting revision

From: Rafał Miłecki It provides simpler output so we don't need extra head and cut commands. Signed-off-by: Rafał Miłecki --- scripts/feeds | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/feeds b/scripts/feeds index

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

On 2 November 2016 at 11:12, wrote: > If so, wouldn't it be clearer (for people like me :) ) if there were two > seperate patches (i.e. one for kernel update+refreshes itself and one for the > internal > refreshes (or refreshes that have been missed in previous updates) )? It

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

On 2.11.2016 13:48, p.wa...@gmx.at wrote: I come to this conclusion: it may happen, that local changes/patches have effect on other patches in the chain, resulting in a fuzzed applying of these. That is right. Patches are chained and 'quilt' applies them in order. The same file can be

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

Thank you Hannu for taking you time and writing those lines, which clarify the whole situation for me. Now I also understand why the mvebu-patch is done here. If I take some of your words > From Openwrt/LEDE perspective, the kernel source is the original kernel > source + the ~100 generic + the

Re: [LEDE-DEV] [PATCH] include: Cortex-A53 is an aarch64 CPU

On 2016-11-01 20:46, Florian Fainelli wrote: > Fixes: SVN 48964 > Signed-off-by: Florian Fainelli > --- > include/target.mk | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/target.mk b/include/target.mk > index c9c02fa03632..94d9570de387

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

Stijn Segers schreef op 2016-11-02 09:44: On 2016-11-02 03:17, Outback Dingo wrote: [...] I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev commit 411babb28a3091f693832fb30d475aa1e99c6d11 which is a merge of the latest ipfilters changes That's weird... Can't

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

p.wassi at gmx.at wrote on Wed Nov 2 03:12:32 PDT 2016: > What may be my problem here is, that I'm totally stuck to the kernel changelog, which leads to my question: is it the case, that the patches getting refreshed here are not directly related to the upstream kernel changes. Being "stuck

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

@Stijn, @Hannu: Thank you for your explanation, I got it by now and I'm totally wrong in interpreting the mvebu-patch. Sorry for causing this flurry. If we stick to the mvebu-patch, what I still do not understand, is why this patch refreshing is needed here. According to

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

On 2016-11-02 03:17, Outback Dingo wrote: [...] I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev commit 411babb28a3091f693832fb30d475aa1e99c6d11 which is a merge of the latest ipfilters changes That's weird... Can't check now, at work, will check this evening.

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

On 02-11-16 10:45, p.wa...@gmx.at wrote: >> I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev > I've just gone throgh the changes, and there is definitely more than just > 'refreshing' the line numbers/offsets. This is seen at [1]. Have a special > look > at [2] at the

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

> I would also concur with this course, as I have done just that > successfully. and have it now running on 4.4.30 :) That's also what I did here. Compile/run tested on kirkwood, brcm47xx, ar71xx > Id be incline to ask for a resubmission, as this patch appears the be > overkill and not

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

On Wed, Nov 2, 2016 at 4:45 PM, wrote: >> I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev > > I've just gone throgh the changes, and there is definitely more than just > 'refreshing' the line numbers/offsets. This is seen at [1]. Have a special > look

Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30

> I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev I've just gone throgh the changes, and there is definitely more than just 'refreshing' the line numbers/offsets. This is seen at [1]. Have a special look at [2] at the bottom of this mail, the line containing the caiman

[LEDE-DEV] [PATCH netifd] interface: Fix triggering of interface update event

In case the keep flag is set in proto_shell_update_link no interface update event is triggered when IPv4/6 addresses/routes/... are updated as the proto_event callback is not called due to keep being set. Unconditionally call the proto_event callback handler in proto_shell_update_link but let the