Re: [LEDE-DEV] Strange build error

> On Aug 28, 2017, at 6:17 PM, Zoltan Gyarmati > wrote: > > On 08/28/2017 01:52 PM, Zoltan Gyarmati wrote: >> Dear All, >> >> i'm fighting with an odd build error on my build server VPS, using >> current master and the RT5350F-OLINUXINO profile: >> >> When

Re: [LEDE-DEV] proper protocol for submitting patches that should be upstreamed as well?

> On Aug 28, 2017, at 6:15 AM, rpj...@crashcourse.ca wrote: > > do the LEDE admins look for that stuff like that > and upstream it automatically? No, as it’s your patch, you need to be the one presenting it so you can answer questions about it, make changes if asked to do so, etc.

Re: [LEDE-DEV] Strange build error

On 08/28/2017 01:52 PM, Zoltan Gyarmati wrote: > Dear All, > > i'm fighting with an odd build error on my build server VPS, using > current master and the RT5350F-OLINUXINO profile: > > When trying to re-build the LEDE tree (after a successful initial > build), i get this error: > >> make[5]:

Re: [LEDE-DEV] [PATCH 13/13] sunxi: Add A64 support with cortex53 subtarget

Hi, On 03-08-17, Hauke Mehrtens wrote: > This adds initial support for the A64 Allwinner SoC to LEDE. > It will be build in the new cortexa53 subtarget. > > Currently it only supports the pine64 and the image is able to boot on > this SoC. Thanks for the patches! I tested them on a pine64+ 1GB

Re: [LEDE-DEV] proper protocol for submitting patches that should be upstreamed as well?

rpj...@crashcourse.ca schrieb am 28.08.2017 um 14:15: > >been away from openwrt for a while, just jumped back in with LEDE, so > will have a few questions shortly, but this one should(?) be simple. > >the recipe for submitting patches for LEDE looks pretty straightforward, > but is there

[LEDE-DEV] [PATCH] dnsmasq: mitigate CVE-2017-13704

Work around a problem where answer_request() attempts to clear from the end of a request to end of request buffer but the end of the buffer is at the same place as the start. Originally this meant that memset() tried to clear data before the buffer leading to segmentation violation. Instead only

Re: [LEDE-DEV] [PATCH] kernel: fix VDSO problem on MIPS

On 08/28/2017 02:08 PM, Rafał Miłecki wrote: > On 11 August 2017 at 00:14, Hauke Mehrtens wrote: >> This fixes the VDSO problems on the Lantiq VR9 MIPS SoC. >> The gettimeofday() sometimes returned old data because of a cache >> aliasing problems on MIPS CPUs, to work around

Re: [LEDE-DEV] [PATCH] busybox: update to 1.27.2

Tested-by: Koen Vandeputte Run-tested on cns3xxx target. Nothing broke afaik :) Koen ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Info about MTD_SPI_NOR_USE_4K_SECTORS

Few people asked me about the MTD_SPI_NOR_USE_4K_SECTORS. Somehow I got responsible for it ;) It doesn't seem like a big thing, but since I was asked, let me describe it. So initially this feature was added by Gabor in: generic: disable 'small sector' erase in m25p80 driver

[LEDE-DEV] proper protocol for submitting patches that should be upstreamed as well?

been away from openwrt for a while, just jumped back in with LEDE, so will have a few questions shortly, but this one should(?) be simple. the recipe for submitting patches for LEDE looks pretty straightforward, but is there anything special that needs to be done if said patch should also

Re: [LEDE-DEV] [PATCH] kernel: fix VDSO problem on MIPS

On 11 August 2017 at 00:14, Hauke Mehrtens wrote: > This fixes the VDSO problems on the Lantiq VR9 MIPS SoC. > The gettimeofday() sometimes returned old data because of a cache > aliasing problems on MIPS CPUs, to work around this problem VDSO > gettimeofday support was

[LEDE-DEV] Strange build error

Dear All, i'm fighting with an odd build error on my build server VPS, using current master and the RT5350F-OLINUXINO profile: When trying to re-build the LEDE tree (after a successful initial build), i get this error: > make[5]: Entering directory >

[LEDE-DEV] [PATCH] kernel: update 4.9 to 4.9.45

Refreshed all patches Compiled & run-tested on targets: cns3xxx, imx6 Signed-off-by: Koen Vandeputte --- include/kernel-version.mk | 4 ++-- target/linux/generic/hack-4.9/930-crashlog.patch | 4 ++--

Re: [LEDE-DEV] uhttpd/luci authentication using SSL client certificates

Citeren Simon Wunderlich : Hi guys, we would like to use SSL client certificates to authenticate to a OpenWRT/LEDE router using UHTTPD/LUCI. We use a private PKI/certificate chain and would only like to admit users to the WebUI which present a valid SSL client

Re: [LEDE-DEV] uhttpd/luci authentication using SSL client certificates

Hi Simon, this is not implemented in uhttpd. ~ J ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Transmit timeouts with mtk_eth_soc and MT7621

Hello again, On Sat, Aug 26, 2017 at 4:57 PM, Kristian Evensen wrote: > I did not have to wait very long before anything. Unfortunately, my > router crashed right after I sent the previous email. So I guess that > means back to the drawing board. I have kept working

[LEDE-DEV] uhttpd/luci authentication using SSL client certificates

Hi guys, we would like to use SSL client certificates to authenticate to a OpenWRT/LEDE router using UHTTPD/LUCI. We use a private PKI/certificate chain and would only like to admit users to the WebUI which present a valid SSL client certificate through their web browser. I've found a note in

[LEDE-DEV] [PATCH 2/2] main: add start|stop|flush|reload|restart event handling

Add -e option for fw3 start|stop|flush|reload|restart events. If option is set, then common hotplug events are executed in dir '/etc/hotplug.d/firewall' Signed-off-by: Florian Eckert --- main.c | 13 +++-- utils.c | 33 + utils.h | 5