Re: [LEDE-DEV] custom files not working?

> "Koen" == Koen Vandeputte writes: Koen> On 2018-04-26 20:16, Hannu Nyman wrote: >> Custom files work quite normally for me. Just compiled and flashed >> r6763-746c590882, and I can see my custom files quite normally in >> /etc. >> >> At the first glance I do

[LEDE-DEV] [PATCH] ubusd: Use linked list for queued messages

The fixed size array for queuing messages led to discarding messages when it was full, using a linked list instead solves this issue. Having the list_head link in the ubus_msg_buf itself avoids the allocation of more memory for an independent list. The motivation was that for a recursive "ubus

Re: [LEDE-DEV] [PATCH] wolfssl: fix options and add support for wpa_supplicant features

On Sat, Apr 28, 2018 at 9:55 PM, Daniel Golle wrote: > Some options' default values have been changed upstream, others were > accidentally inverted (CONFIG_WOLFSSL_HAS_DES3). Also add options > needed to build hostapd/wpa_supplicant against wolfssl. Sorry for the late

Re: [LEDE-DEV] [PATCH v2] dropbear: bump to 2018.76

On 05/02/2018 05:37 PM, Koen Vandeputte wrote: > Config moved from option.h to localoptions.h > refreshed all patches > > deleted upstreamed patches: > - 010-runtime-maxauthtries.patch > - 610-skip-default-keys-in-custom-runs.patch > > introduced new patch: > - 610-disable-ec-by-default.patch >

Re: [LEDE-DEV] [PATCH v1 0/3] at91 patch series.

On 02/05/18 20:20, sandeepsheriker.mallikar...@microchip.com wrote: Hi John, These patches should be applied on top of patch "[LEDE-DEV, 09/12] u-boot-at91: fix DTC command not found." (i.e Patch series subject [LEDE-DEV, 01/12] at91bootstrap:update to v3.8.10).However all of these

Re: [LEDE-DEV] [PATCH v1 0/3] at91 patch series.

Hi John, These patches should be applied on top of patch "[LEDE-DEV, 09/12] u-boot-at91: fix DTC command not found." (i.e Patch series subject [LEDE-DEV, 01/12] at91bootstrap:update to v3.8.10).However all of these patches have been accepted in

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

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 On Wed, 2 May 2018, Linus

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

On Wed, May 2, 2018 at 10:01 AM, Linus Walleij wrote: > Network does not come up either, I suspect it is because of missing the > Realtek PHY driver, so will investigate this further. I found the culprit, sent you a patch adding ethernet to the DNS-313 and Wiliboard

[LEDE-DEV] [PATCH] gemini: Add ethernet to DNS-313 and Wiliboard

This adds an interrim patch for v4.14 based on an upstream commit to get ethernet working on D-Link DNS-313 (probably also on the Wiliboards) Signed-off-by: Linus Walleij --- ...-dts-Add-ethernet-to-a-bunch-of-platforms.patch | 123 + 1 file

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

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 On Wed, 2 May 2018, Joel

[LEDE-DEV] [RFC PATCH 2/2] odhcpd: adjust configuration default

Move the odhcpd lease state file from /tmp/hosts/odhcpd to /var/run/hosts.d/odhcpd.leases. The motivation of this change is to align the lease state file (which essentially is a commented hosts(5) format) location with the one used by dnsmasq for the temporary hosts(5) file holding user-assigned

[LEDE-DEV] [RFC PATCH 1/2] dnsmasq: adjust configuration defaults

- Change the hosts(5) files directory from /tmp/hosts/ to /var/run/hosts.d/ - Change the lease database path /tmp/dhcp.leases to /var/run/dhcp.leases - Remove "leasefile" and "resolvfile" options from default /etc/config/dhcp The motivation of this change is twofold; first to make the file and

[LEDE-DEV] [RFC PATCH 0/2] Adjust DHCP/DNS defaults for better consistency

This small patch series changes the default location of various temporary and automatically generated files used by dnsmasq and odhcpd during normal operation. The main motivation is to move the /tmp/hosts/ directory out of /tmp/ since it does not really belong there, it is a directory of dynamic

[LEDE-DEV] [PATCH v2] dropbear: bump to 2018.76

Config moved from option.h to localoptions.h refreshed all patches deleted upstreamed patches: - 010-runtime-maxauthtries.patch - 610-skip-default-keys-in-custom-runs.patch introduced new patch: - 610-disable-ec-by-default.patch This patch adds the EC definitions which are altered by the

Re: [LEDE-DEV] custom files not working?

On 2018-04-26 20:16, Hannu Nyman wrote: Custom files work quite normally for me. Just compiled and flashed r6763-746c590882, and I can see my custom files quite normally in /etc. At the first glance I do not see any obvious mistake in your workflow. Firstly: Testing this in detail shows

[LEDE-DEV] [PATCH 1/2] kernel: bump 4.9 to 4.9.97

Refreshed all patches Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte --- include/kernel-version.mk | 4 +- .../ar7/patches-4.9/300-add-ac49x-platform.patch | 4 +-

[LEDE-DEV] [PATCH 2/2] kernel: bump 4.14 to 4.14.38

Refreshed all patches Compile-tested on: cns3xxx, imx6, x86_64 Runtime-tested on: cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte --- include/kernel-version.mk| 4 ++-- target/linux/brcm47xx/patches-4.14/159-cpu_fixes.patch

Re: [LEDE-DEV] [PATCH] dropbear: bump to 2018.76

On 2018-04-28 15:47, Hauke Mehrtens wrote: On 04/27/2018 05:58 PM, Koen Vandeputte wrote: Config moved from option.h to localoptions.h refreshed all patches deleted upstreamed patches: - 010-runtime-maxauthtries.patch - 610-skip-default-keys-in-custom-runs.patch introduced new patch: -

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

On 2018-05-02 11:01, Linus Walleij wrote: On Wed, May 2, 2018 at 12:18 AM, Linus Walleij wrote: On Sun, Apr 29, 2018 at 8:32 PM, Roman Yeryomin wrote: Linus, could you test that branch on your device and see if network is working by default?

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

On Wed, May 2, 2018 at 12:41 AM, Joel Wirāmu Pauling wrote: > any chance for support for the > Goldengate SoC found in the Almond+. Currently attempting to reuse it for a > home automation project but it's ancient kernel is terrible and even doing > basic things like vlans are

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14

On Wed, May 2, 2018 at 12:18 AM, Linus Walleij wrote: > On Sun, Apr 29, 2018 at 8:32 PM, Roman Yeryomin wrote: >> >> Linus, could you test that branch on your device and see if network is >> working by default? > > I've pulled in the branch and building

[LEDE-DEV] [PATCH] gemini: Fix hard disk boot on D-Link devices

Since the D-Link devices boot from hard disk we need to add the following changes to Gemini: - Supply a bootarg in the device tree so we can boot from the right partition (/dev/sda4 on DNS-313) - Disable forced command line in config so the kernel picks up the right bootargs from the device