[OpenWrt-Devel] [PATCH v4 1/2] Add ubnt_hsr platform flag and enable for UniFi Outdoor Plus

On Tue Jun 16 23:16:46 CEST 2015, Stefan Rompf wrote: Add tuner for the HSR filter of the UniFi Outdoor Plus access point. Usage of the tuner is controlled at runtime by ath9k_platform_data. The code can be enabled or disabled by a compile time option. Dear All, How do I tell if the above

[OpenWrt-Devel] Q: procd / respawn if process dies

while trying to understand the procd respawn-trigger, I wrote this testscript: #!/bin/sh /etc/rc.common START=50 USE_PROCD=1 PROG=/tmp/test.sh start_service() { { echo '#!/bin/sh' echo 'logger START-$0 $$' echo 'sleep 10'

Re: [OpenWrt-Devel] Q: procd / respawn if process dies

* Yousong Zhou [08.12.2015 15:59]: > respawn is an instance attribute, moving that statement inside the > open/close instance block should do the job thanks for the hint, this works! bye, bastian ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] Q: procd / respawn if process dies

Am 08.12.2015 22:45 schrieb "Bastian Bittorf" : > > while trying to understand the procd > respawn-trigger, I wrote this testscript: > > #!/bin/sh /etc/rc.common > START=50 > USE_PROCD=1 > PROG=/tmp/test.sh > > start_service() > { > { > echo

Re: [OpenWrt-Devel] [OpenWrt] openwrt build system costs: support of or foundation over?

On Mon, Dec 7, 2015 at 8:26 PM, Eric Schultz wrote: > Dave, > > Thanks for bringing this up. Based upon my conversations at the OpenWrt > summit and observations, an official OpenWrt Foundation would be a positive > development. I heard at least a few companies say

[OpenWrt-Devel] Fwd: [homenet] Protocol Action: 'Home Networking Control Protocol' to Proposed Standard (draft-ietf-homenet-hncp-10.txt)

While I'm dreaming of steadier funding for things I care about, ietf homenet wg's work is nearly complete. *most* of the work is already done in openwrt to make all the ietf homenet proposed standards work, and indeed, be the default in openwrt. However nobody is funded anymore to take it

Re: [OpenWrt-Devel] Fwd: [homenet] Protocol Action: 'Home Networking Control Protocol' to Proposed Standard (draft-ietf-homenet-hncp-10.txt)

Why has this been cross posted to the OpenWrt *Development* List? I fail to see any relevance to the usual and prevailing use of this list. On Tue, Dec 8, 2015 at 10:52 AM, Dave Taht wrote: > While I'm dreaming of steadier funding for things I care about, > ietf homenet

Re: [OpenWrt-Devel] Fwd: [homenet] Protocol Action: 'Home Networking Control Protocol' to Proposed Standard (draft-ietf-homenet-hncp-10.txt)

On Tue, Dec 8, 2015 at 6:48 PM, L. D. Pinney wrote: > Why has this been cross posted to the OpenWrt Development List? > > I fail to see any relevance to the usual and prevailing use of this list. Well, I do keep hoping more folk within openwrt actually try the hnet-full and

[OpenWrt-Devel] [PATCH] uboot-lantiq: fix build with gcc5

Signed-off-by: Mathias Kresin --- .../patches/0045-no_extern_inline.patch| 101 + .../uboot-lantiq/patches/0046-no_weak_alias.patch | 28 ++ .../patches/0047-add-gcc5-support.patch| 93 +++ 3 files changed, 222

[OpenWrt-Devel] WiFi on RT5350 not performing well

Hello All, Working on an RT5350 based system with a generic version of CC 15.05 and the also the latest trunk head I noticed that the WiFi performance was very poor. ssh was very sluggish and file transfers would hang after about 150Kbytes of data were transferred. After some investigation

[OpenWrt-Devel] [PATCH] lantiq: fix led setup after switch to uci-defaults-new.sh

The switch to uci-defaults-new.sh revealed a bug in the former used uci-defaults.sh, which failed to add leds with colons in the led name. This bug isn't any longer present in uci-defaults-new.sh and therefore all via DT defined leds will be added to /etc/config/system with their initial on/off