> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf
> Of John Crispin
> Sent: Tuesday, July 14, 2015 8:47 PM
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH CC 0/5] ar71xx: backport of support for
> devolo dLAN d
On 15/07/2015 09:21, Guenther Kelleter wrote:
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
>> Behalf
>> Of John Crispin
>> Sent: Tuesday, July 14, 2015 8:47 PM
>> To: openwrt-devel@lists.openwrt.org
>> Subject: Re: [OpenWrt-Devel] [P
On 15/07/2015 08:20, Álvaro Fernández Rojas wrote:
> You're right, device tree doesn't provide that functionality directly,
> but there's a preinit script which exports it from DT:
> https://github.com/openwrt-es/openwrt/blob/master/package/base-files/files/lib/preinit/10_sysinfo
>
> The LEDs ar
On 2015-05-15 16:25, Darik Horn wrote:
> Move the `--recursive` switch from `git clone` to `git submodule`
> so that submodules are cloned for upstream branches where the
> PKG_SOURCE_VERSION commit-ish has a different .gitmodules
> configuration than the repository default.
>
> This is, for examp
backport of r46248.
Signed-off-by: Jaehoon You
---
target/linux/ar71xx/base-files/etc/diag.sh | 1 +
.../ar71xx/base-files/etc/uci-defaults/01_leds | 8 ++
.../ar71xx/base-files/etc/uci-defaults/02_network | 1 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../
On Tue, 2015-07-14 at 18:19 +0200, Rafał Miłecki wrote:
> On 28 June 2015 at 05:37, Ian Kent wrote:
> > Let me rework this using the bus number as you recommend.
> > I'll repost my updated patch series once I've done that.
>
> Hi Ian,
>
> Is there any chance you'll find a moment for it anytime s
Hi,
On Wed, Jul 15, 2015 at 7:05 AM, Cezary Jackiewicz
wrote:
> This patch adds buttons support for Huawei EchoLife HG553.
>
> Signed-off-by: Cezary Jackiewicz
Generally looks good, but a few nitpicks:
> ---
>
> diff --git a/target/linux/brcm63xx/dts/hg553.dts
> b/target/linux/brcm63xx/dts/hg
On Wed, Jul 15, 2015 at 7:59 AM, Rafał Miłecki wrote:
> On 15 July 2015 at 07:05, Cezary Jackiewicz
> wrote:
>> @@ -6,6 +6,25 @@
>> model = "Huawei EchoLife HG553";
>> compatible = "huawei,hg553", "brcm,bcm6358";
>>
>> + gpio-keys-polled {
>> + compatible = "g
On 15/07/2015 12:23, Jonas Gorski wrote:
> On Wed, Jul 15, 2015 at 7:59 AM, Rafał Miłecki wrote:
>> On 15 July 2015 at 07:05, Cezary Jackiewicz
>> wrote:
>>> @@ -6,6 +6,25 @@
>>> model = "Huawei EchoLife HG553";
>>> compatible = "huawei,hg553", "brcm,bcm6358";
>>>
>>> + g
Hi,
Atheros hardware supports multiple wireless interfaces, and ath9k
driver takes advantage of that.
What is not clear to me is why if you have two interfaces, one in sta
mode and other in ap mode then ap interface isn't available until sta
interface is connected to upstream AP.
Why? Is there an
Hi,
It is a known issue, some descriptions you can find there -
http://vonger.cn/?p=1778
I guess it is not depend on a driver or hw.
15.07.2015, 13:33, "valent.turko...@gmail.com" :
> Hi,
> Atheros hardware supports multiple wireless interfaces, and ath9k
> driver takes advantage of that.
>
> Wh
On 15 July 2015 at 12:37, Yaroslav Syrytsia wrote:
> Hi,
>
> It is a known issue, some descriptions you can find there -
> http://vonger.cn/?p=1778
> I guess it is not depend on a driver or hw.
Yaroslav thanks man you saved me lots of headache! :)
>From reading blog post you linked this seams t
I don't understad how that script even works! Here is the script from
that blog post - http://pastebin.com/ihNAfbcr
Why use wifi-iface[99] ? Who has 100 wifi interfaces? When I manually
run "uci show wireless.@wifi-iface[99]" I get "uci: Entry not found"
as expected.
__
On 07/15/2015 12:08 PM, valent.turko...@gmail.com wrote:
> On 15 July 2015 at 12:37, Yaroslav Syrytsia wrote:
>> Hi,
>>
>> It is a known issue, some descriptions you can find there -
>> http://vonger.cn/?p=1778
>> I guess it is not depend on a driver or hw.
>
> Yaroslav thanks man you saved me l
> Because there is only one pysical hardware and the hardware can only be
> tuned to one channel. The STA interface needs to look for the channel
> the AP is on and as long as the channel is not determined we can not
> start an AP.
I think that all of us understand limitations of one physical hard
The script is a bit ugly ... but the main idea is correct :)
But i would prefer next behavior: if STA has lost the connection to upstream
AP, then our AP must not fail and switch to the channel from our config file or
to last used channel (aka STA channel) ...
Maybe someone from OpenWRT develop
> When using DFS channels on Ath10k kernel log has warning message 'failed
> to process fft', typically when under medium/heavy traffic. Ticket
> https://dev.openwrt.org/ticket/19316 discusses and concludes messages
> are harmless. They do still contribute to log noise, so this patch
> enables th
Hi John,
how is the testing going ? i would like to also pull this intot he CC
which means there is not that much time left.
Pretty well, see mail from yesterday. After a fresh pull today, the
patch
also applied without any warning/notice to 3.18.18 and the stick is also
working with the sam
otherwise it's not picked up by toolchain:
staging_dir/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_musl-1.1.10/lib/gcc/mipsel-openwrt-linux-musl/4.8.3/../../../../mipsel-openwrt-linux-musl/bin/ld:
cannot find -lsw
Signed-off-by: Roman Yeryomin
---
package/network/config/swconfig/Makefile | 4 ++-
This patch add support for Planex MZK-DP150N.
a mini router on the MT7620A SoC with one Ethernet port and a 802.11n 2.4 GHz
radio.
Signed-off-by: YuheiOKAWA
---
target/linux/ramips/base-files/etc/board.d/01_leds | 3 +
.../linux/ramips/base-files/etc/board.d/02_network | 7 ++
target/linux/ra
This patch adds buttons support for Huawei EchoLife HG553.
Changes:
- add empty line...
- change codes to hexadecimal
Signed-off-by: Cezary Jackiewicz
---
diff --git a/target/linux/brcm63xx/dts/hg553.dts
b/target/linux/brcm63xx/dts/hg553.dts
index 140e2de..4d79824 100644
--- a/target/linux/br
Allow to use radius server to mac authentication.
Config section:
..
option 'macfilter' 'radius'
option 'auth_server' '192.168.1.100'
option 'auth_secret' 'RadiusPassword'
option 'auth_port' '1812'
Tested with freeradius and Coova/radproxy.
Signed-off-by: Cezary Jackiewicz
---
dif
> Hi,
>
> how is the testing going ? i would like to also pull this intot he CC
> which means there is not that much time left.
>
> also the patch sent was missing proper subject and SoB.
>
> John
Hi John,
Sorry about the delay, it seems I've managed to kill the second USB-port
in my main r
On 15/07/2015 19:41, Matti Laakso wrote:
>> Hi,
>>
>> how is the testing going ? i would like to also pull this intot he CC
>> which means there is not that much time left.
>>
>> also the patch sent was missing proper subject and SoB.
>>
>> John
>
> Hi John,
>
> Sorry about the delay, it s
NCM specs are not actually mandating a specific position in the frame for
the NDP (Network Datagram Pointer). However, some Huawei devices will
ignore our aggregates if it is not placed after the datagrams it points
to. Add support for doing just this, in a per-device configurable way.
While at it,
On 15/07/2015 13:22, Matti Laakso wrote:
>> When using DFS channels on Ath10k kernel log has warning message 'failed
>> to process fft', typically when under medium/heavy traffic. Ticket
>> https://dev.openwrt.org/ticket/19316 discusses and concludes messages
>> are harmless. They do still contri
On 15 July 2015 at 18:34, Cezary Jackiewicz wrote:
> This patch adds buttons support for Huawei EchoLife HG553.
> Changes:
> - add empty line...
> - change codes to hexadecimal
You usually want to put version comments in the comments part. Having
above won't make too much sense when browsing log
27 matches
Mail list logo
