Re: [LEDE-DEV] [OpenWrt-Devel] Talks between OpenWrt and LEDE

OpenLEDE - /ˈōpənlēdē/ On Wed, Dec 21, 2016 at 11:06 PM, Russell Senior wrote: > > Val> Now, please try to explain how to pronounce OpenLEDE and make sure > Val> the correct pronunciation sticks :-) > > It doesn't matter how they pronounce it, as long as they can

Re: [LEDE-DEV] ath10k firmware crashes in mesh mode on QCA9880

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Adrian, I have not done much

Re: [LEDE-DEV] ath10k firmware crashes in mesh mode on QCA9880

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Thank you for your help Rajkumar,

Re: [LEDE-DEV] QCA Dakota support

<chunk...@googlemail.com> wrote: > Hello Alexis, > > On Sunday, November 27, 2016 12:18:00 PM CET Alexis Green wrote: >> Could you post .config for your build? I cloned your repo and >> successfully built and installed an image, but I'm seeing some rather >> weird be

Re: [LEDE-DEV] QCA Dakota support

Hi Christian, Could you post .config for your build? I cloned your repo and successfully built and installed an image, but I'm seeing some rather weird behavior. I get kernel oops (null derefrence) in bridge code when I connect a client to WPA2 AP that is bridged. The oops is gone after I

Re: [LEDE-DEV] [PATCH v4] base-files: Ensure reset only works if an overlay exists

I’m guessing it’s because there might some random error message from grep? Maybe use -s option for grep instead to suppress error messages? > On Oct 23, 2016, at 12:30 PM, Bastian Bittorf wrote: > > * Chris Blake [23.10.2016 21:10]: >> +OVERLAY="$( grep '

[LEDE-DEV] [PATCH] rsyslog: do not daemonize and allow procd to manage rsyslogd

This allows user to stop and/or restart the daemon. Currently, running "/etc/init.d/rsyslogd stop" does not stop the daemon once it's started. Signed-off-by: Alexis Green <ale...@cessp.it> --- net/rsyslog/files/rsyslog.init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)