Re: [LEDE-DEV] procd - shutdown. Why ?

On 26/07/2016 13:36, reiner otto wrote: > > > On a remote LEDE from time to time I see > Jul 22 00:41:36 xx.xx.xx.xx procd: - shutdown - > and a reboot. > Any idea, why this can happen ? something called halt or reboot > For the developer(s): It might be a good idea, to provide some more in

Re: [LEDE-DEV] [PATCH ver. B] ramips: unify etc/board.d/01_leds configuration

Just to transport the idea what I'm thinking of: take set_wifi_led as an example. Imagine the function was built like this: > set_wifi_led() { > case $# in > 1|\ > 2) > ucidef_set_led_netdev "wifi_led" "wifi" "${1}" > "${2:-wlan0}" >

Re: [LEDE-DEV] lede forum

Folks, I was planning to advocate for a forum as well. I have enjoyed using the Discourse forum (http://discourse.org) with several projects. (If you haven't seen it, it's a new forum system, designed by people who have used lots of bad ones, and intend to fix those problems.) I have some exper

[LEDE-DEV] procd - shutdown. Why ?

On a remote LEDE from time to time I see Jul 22 00:41:36 xx.xx.xx.xx procd: - shutdown - and a reboot. Any idea, why this can happen ? For the developer(s): It might be a good idea, to provide some more info about the reason. It would definitely help on a remote, embdded system, to trace down p

Re: [LEDE-DEV] lede forum

Folks, I was planning to advocate for a forum as well. I have enjoyed using the Discourse forum (http://discourse.org) with several projects. (If you haven't seen it, it's a new forum system, designed by people who have used lots of bad ones, and intend to fix those problems.) I have some exper

Re: [LEDE-DEV] [PATCH ver. B] ramips: unify etc/board.d/01_leds configuration

> > What about this approach: > > without changing every call to set_usb_led(), we leave set_usb_led() in > > place, > > don't use a hardcoded triggering device there, but instead have a second > > parameter, with a default value. > > Something like ${2:-wlan0} ? > > yes, that sound like a good p

[LEDE-DEV] [PATCH v2] ramips: unify etc/board.d/01_leds configuration

From: P.Wassi Introduce an optional parameter at the local set_usb_led and set_wifi_led function such that they can take a triggering device. If no parameter is passed, behaviour is unchanged. Signed-off-by: P.Wassi --- This allows use of this functions in future devices, which do not use USB 1-

Re: [LEDE-DEV] Ethernet link up/down mt7688 board not detected by hotplug

Anyone has seen same behaviour on its mt7628, mt7688 or ralink board which uses esw_rt3052.c driver? Thanks 2016-07-19 18:19 GMT+02:00 Baptiste Clenet : > Additional information: > Board is down and ethernet unplugged. > Board is switched on, I wait for end of boot then I plug ethernet > cable, he

Re: [LEDE-DEV] [PATCH 1/2] docs: development: add instructions for staging trees

On 07/26/2016 11:20 AM, Daniel Golle wrote: > Signed-off-by: Daniel Golle Acked-by: Jo-Philipp Wich > --- > development.txt | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/development.txt b/development.txt > index 3a6..e4fb09b 100644 > --- a/development.txt > +++ b/devel

Re: [LEDE-DEV] [PATCH 2/2] docs: index: replace 'router' with 'device'

On 07/26/2016 11:20 AM, Daniel Golle wrote: > LEDE also runs on a lot of non-router devices, such as NAS boxes, > single-board computers or even inside virtual machines. > > Signed-off-by: Daniel Golle Acked-by: Jo-Philipp Wich > --- > docs/index.txt | 23 --- > 1 file cha

[LEDE-DEV] [PATCH 2/2] docs: index: replace 'router' with 'device'

LEDE also runs on a lot of non-router devices, such as NAS boxes, single-board computers or even inside virtual machines. Signed-off-by: Daniel Golle --- docs/index.txt | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/docs/index.txt b/docs/index.txt i

[LEDE-DEV] [PATCH 1/2] docs: development: add instructions for staging trees

Signed-off-by: Daniel Golle --- development.txt | 9 + 1 file changed, 9 insertions(+) diff --git a/development.txt b/development.txt index 3a6..e4fb09b 100644 --- a/development.txt +++ b/development.txt @@ -69,6 +69,15 @@ All patches need to be sent in a format that they are listed

Re: [LEDE-DEV] [PATCH] mesh: Set correct secondary channel offset if HT40 is disabled

Tested-by: Koen vandeputte > This patch also solves the same issue in IBSS mode Koen On 2016-07-26 04:45, Masashi Honma wrote: Previously, secondary channel offset could be non zero even though disable_ht40=1. This patch fixes it. Signed-off-by: Masashi Honma -