On Wed, 2015-05-13 at 06:34 +0200, Rafał Miłecki wrote:
> On 13 May 2015 at 03:49, Ian Kent wrote:
> > On Tue, 2015-05-12 at 19:31 +0200, Rafał Miłecki wrote:
> >> On 12 May 2015 at 15:10, Hante Meuleman wrote:
> >> > Added two functions to the bcm47xx_nvram module to get and release copies
> >>
HI, all
this is a patch try to fix libubus-lua's memory leak problem
Best regards
Signed-off-by:Chen Bin
---
--- a/lua/ubus.c
+++ b/lua/ubus.c
@@ -666,6 +666,7 @@ ubus_lua__gc(lua_State *L)
{
struct ubus_lua_connection *c = luaL_checkudata(L, 1, METANAME);
+ blob_buf_free(&c->
On 13 May 2015 at 03:49, Ian Kent wrote:
> On Tue, 2015-05-12 at 19:31 +0200, Rafał Miłecki wrote:
>> On 12 May 2015 at 15:10, Hante Meuleman wrote:
>> > Added two functions to the bcm47xx_nvram module to get and release copies
>> > of the complete nvram contents. This can be used by for example
On Tue, 2015-05-12 at 19:31 +0200, Rafał Miłecki wrote:
> On 12 May 2015 at 15:10, Hante Meuleman wrote:
> > Added two functions to the bcm47xx_nvram module to get and release copies
> > of the complete nvram contents. This can be used by for example brcmfmac
> > to get complete nvram contents whi
On 2015-05-12 15:10, Hante Meuleman wrote:
> Added two functions to the bcm47xx_nvram module to get and release copies
> of the complete nvram contents. This can be used by for example brcmfmac
> to get complete nvram contents which will after some parsing be sent to
> device.
>
> Signed-off-by
Currently port 6 is shown as up 10MBit/half in LUCI and swconfig.
Reason is that all bits in the port 6 config are zero.
This means that also the aneg flag is not set and in this case
ar8216_read_port_link hardcodes the link to be up.
This is no real problem but a little annoying.
To fix this init
On 12 May 2015 at 15:10, Hante Meuleman wrote:
> Added two functions to the bcm47xx_nvram module to get and release copies
> of the complete nvram contents. This can be used by for example brcmfmac
> to get complete nvram contents which will after some parsing be sent to
> device.
Thanks for send
Applied, thanks.
On 12.05.2015 13:11, Hans Dedecker wrote:
The default packet steering behavior can be configured via the parameter
default_ps in the global section; the default value is true to keep
backwards compatibility.
Device packet steering (rps/xps) config can still be used to override t
Hello,
I have tplink 1043nd with BB
Problem is that I have dhcp client on WAN and if I unplug cable from WAN,
it doesnt change status, give up dhcp address.
Even worse is that if I plug cable with another end point with another
network, WAN dhcp client doesnt pull new IP, I must click on "Conne
Added two functions to the bcm47xx_nvram module to get and release copies
of the complete nvram contents. This can be used by for example brcmfmac
to get complete nvram contents which will after some parsing be sent to
device.
Signed-off-by: Hante Meuleman
---
diff --git
a/target/linux/bcm53x
Hello,
I found out that if I make a mistake in a branch or commit expression in the
feeds.conf file the updating procedure fails silently. This patch fixes this
behavior and returns error code 1 if something went wrong.
Best Regards,
Martin Strba??ka
Signed-off-by: Martin Strbacka
---
scripts
The default packet steering behavior can be configured via the parameter
default_ps in the global section; the default value is true to keep
backwards compatibility.
Device packet steering (rps/xps) config can still be used to override the
default behavior.
This allows you to disable packet steerin
It is a bit more than just changing request_firmware_nowait into
request_firmware. The worker in core.c needs to be removed. The
function brcmf_pcie_setup needs to be updated as it cannot call
device_release_driver during probe. As a result
brcmf_fw_get_firmwares_pcie has to return the error, w
Ok, thanks, that requires the wifi device to be completely up and
initialized. There is way more involved in getting that synchronous.
So what about the idea of adding a delay of two seconds to
brcmfmac_module_init? Would that patch be accepted?
-Original Message-
From: Rafał Miłecki [m
On 2015-05-12 11:33, Hante Meuleman wrote:
> Understood, what is wifi detect using as input? Do the netdevs have to
> be up? Where is the information that wifi app is reading coming from?
It looks for registered cfg80211 wiphys. It does not care about netdevs.
> brcmfmac uses different method for
On 12 May 2015 at 11:33, Hante Meuleman wrote:
> Understood, what is wifi detect using as input? Do the netdevs have to
> be up? Where is the information that wifi app is reading coming from?
What about just checking it by yourself?
vim package/base-files/files/sbin/wifi
vim package/kernel/mac802
Understood, what is wifi detect using as input? Do the netdevs have to
be up? Where is the information that wifi app is reading coming from?
brcmfmac uses different method for firmware loading. It is not as
easily patched as the ath10k driver. But I would like to know exactly
what wifi detect u
On 2015-05-12 10:35, Hante Meuleman wrote:
> The boot script gives 1 second for wifi modules to settle. For newer
> routers
>
> like R8000 which has three wifi devices which all need to be firmware
>
> downloaded, nvram downloaded and initialized this delay is getting very
>
> tight. On some boo
On 12 May 2015 at 10:35, Hante Meuleman wrote:
> The boot script gives 1 second for wifi modules to settle. For newer routers
>
> like R8000 which has three wifi devices which all need to be firmware
>
> downloaded, nvram downloaded and initialized this delay is getting very
>
> tight. On some boo
The boot script gives 1 second for wifi modules to settle. For newer routers
like R8000 which has three wifi devices which all need to be firmware
downloaded, nvram downloaded and initialized this delay is getting very
tight. On some bootups it was seen that not all wifi modules were
initialized by
The R8000 AP has more than 32K nvram memory. This was an issue for the
userspace app "nvram". This got fixed at some point, but then it was reverted:
http://git.openwrt.org/?p=openwrt.git;a=commit;h=9258d82f1d4a79f86ea72aad349b3f3eeb772d87
Why was it reverted? Would be good to know what exact rea
Do not mimic the vlan configuration in some devices like R8000 as the
configuration is to be used with SW accelerators not available in OpenWRT.
It is not possible to use the switch with vlan port configuration 0 1 2 3 5 7
8,
without making some huge modifications. When this configuration is us
22 matches
Mail list logo
