Re: [LEDE-DEV] new ath79 target
Hi John, This is great news. Thank you so much for all of your work ;-) it is very appreciated! -Paul Original Message Subject: Re: [LEDE-DEV] new ath79 target From: John Crispin To: Paul Blazejowski Date: 5/8/2018, 12:28:10 AM > > > On 08/05/18 05:31, Paul Blazejowski wrote: >> John, >> >> I wanted to ask if the Netgear WNDR3700v4 router will also be ported to >> the new ath97 target down the road? And possibly get 4.14 or newer >> kernel? >> >> Thanks! > Hi Paul, > > the aim is to move all board over mid term. > > John > >> ___ >> Lede-dev mailing list >> Lede-dev@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/lede-dev > ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] new ath79 target
On 08/05/18 05:31, Paul Blazejowski wrote: John, I wanted to ask if the Netgear WNDR3700v4 router will also be ported to the new ath97 target down the road? And possibly get 4.14 or newer kernel? Thanks! Hi Paul, the aim is to move all board over mid term. John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
On 07/05/18 20:34, Arjen de Korte wrote: Citeren Jo-Philipp Wich : Hi Bjørn, the current timings of the DO zone are: ;; ANSWER SECTION: openwrt.org. 1800 IN SOA ns1.digitalocean.com. hostmaster.openwrt.org. ( 1525688668 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 1800 ; minimum (30 minutes) ) This all looks fine, but what slightly worries me that the nameservers listed in the Whois information for openwrt.org still mention the old ones: whois openwrt.org Domain Name: OPENWRT.ORG Registry Domain ID: D104186352-LROR Registrar WHOIS Server: whois.tucows.com Registrar URL: http://www.tucows.com Updated Date: 2018-05-06T20:40:09Z [...] Name Server: ARRAKIS.DUNE.HU Name Server: BELATEGEUSE.DUNE.HU Name Server: SOAPSTONE.YURI.ORG.UK I've switched nameservers for several of my domains (including .org) and I recall this never took more than a few hours. It could be I'm impatient, but as of now, when running a trace, the above are still listed as the openwrt.org nameservers. Of course, *caches* would show stale data for up to a day, but running 'dig soa +trace openwrt.org' should resolve to the DO nameservers by now. Hi, nameservers were switched over to DO at 5 am CEST today. things should start smoothing out shortly. John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] new ath79 target
John, I wanted to ask if the Netgear WNDR3700v4 router will also be ported to the new ath97 target down the road? And possibly get 4.14 or newer kernel? Thanks! ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] Add procd triggers only for interfaces that dnsmasq is interested in.
On 05/07/2018 06:37 PM, hux wrote: Signed-off-by: hux --- Right now interface.update events are sent out by netifd upon interface state, route, address (lifetime), prefix lifetime changes. Dnsmasq is only interested in interface state changes and currently adds an interface trigger for all the "interface.*" events. In combination with commit 23bba9cb330, which triggers a SIGHUP signal to dnsmasq, IPv6 address/prefix lifetime changes on the wan will trigger dnsmasq reloads which can become frequent in case of shorter lifetimes. To avoid frequent dnsmasq reload, this patch adds specific interface triggers. During dnsmasq init, it loops dhcp uci section. If the value of the ignore option is set to 0, then the corresponding interface trigger is not installed. Otherwise, if the ignore option value is 1, then procd_add_interface_trigger is called and the trigger is added. It would be nice, if the root cause in netifd and procd as a combination was somehow resolved. Bug tracker that's been idle awhile: https://bugs.openwrt.org/index.php?do=details&task_id=713 - Eric ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] new ath79 target
On 07.05.2018 09:13, John Crispin wrote:
Hi,
I have just pushed the new ath79 target to trunk. This will replace
ar71xx mid term, switching the target over to pure OF. a few boards
are already supported, would be great if people could start moving
boards over that they use. I am available to help via ML, mail, irc,
... AHB wifi is still missing but we'll get that working the next few
days.
John
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
so I tried adding TP-LINK WR1043ND-V3 the same hardware as WR1043ND-V2
I attached the dts files (of course they need more work), the diff to
the tree and the boot log
some advice is needed
Regards
diff --git a/target/linux/ath79/image/Makefile
b/target/linux/ath79/image/Makefile
index 5f1edcbdb2..a425320d8e 100644
--- a/target/linux/ath79/image/Makefile
+++ b/target/linux/ath79/image/Makefile
@@ -5,6 +5,13 @@ KERNEL_LOADADDR = 0x8006
DEVICE_VARS += CMDLINE CONSOLE IMAGE_SIZE BOARDNAME LOADER_FLASH_OFFS
LOADER_TYPE ATH_SOC
+ifeq ($(SUBTARGET),generic)
+include ./generic.mk
+include ./tp-link.mk
+include ./generic-ubnt.mk
+endif
+include ./legacy.mk
+
define Build/loader-common
rm -rf $@.src
$(MAKE) -C lzma-loader \
diff --git a/target/linux/ath79/image/tp-link.mk
b/target/linux/ath79/image/tp-link.mk
index bbe4054143..25e79ae769 100644
--- a/target/linux/ath79/image/tp-link.mk
+++ b/target/linux/ath79/image/tp-link.mk
@@ -30,7 +30,7 @@ define Build/mktplinkfw-combined
-m $(TPLINK_HEADER_VERSION) \
-k $@ \
-o $@.new \
- -s -S \
+ -s \
-c
@mv $@.new $@
endef
@@ -58,12 +58,13 @@ define Device/tplink
TPLINK_HWREV := 0x1
TPLINK_HEADER_VERSION := 1
LOADER_TYPE := gz
+# FILESYSTEM := squashfs
KERNEL := kernel-bin | patch-cmdline | lzma
KERNEL_INITRAMFS := kernel-bin | patch-cmdline | lzma | mktplinkfw-combined
# IMAGES := sysupgrade.bin
IMAGES := sysupgrade.bin factory.bin
IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade
-# IMAGE/factory.bin := append-rootfs | mktplinkfw factory | a
+ IMAGE/factory.bin := append-rootfs | mktplinkfw factory
endef
define Device/tplink-nolzma
@@ -115,5 +116,22 @@ define Device/tl_wr1043nd_v1
DEVICE_PROFILE := TLWR1043
TPLINK_HWID := 0x10430001
endef
+TARGET_DEVICES += tl_wr1043nd_v1
-#TARGET_DEVICES += tl_wr1043nd_v1
+define Device/tl-wr1043nd-v2
+ $(Device/tplink-8mlzma)
+ ATH_SOC := qca9558
+ DEVICE_TITLE := TP-LINK TL-WR1043N/ND v2
+ DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
+ BOARDNAME := TL-WR1043ND-v2
+ DEVICE_PROFILE := TLWR1043
+ TPLINK_HWID := 0x10430002
+endef
+TARGET_DEVICES += tl-wr1043nd-v2
+
+define Device/tl-wr1043nd-v3
+ $(Device/tl-wr1043nd-v2)
+ DEVICE_TITLE := TP-LINK TL-WR1043N/ND v3
+ TPLINK_HWID := 0x10430003
+endef
+TARGET_DEVICES += tl-wr1043nd-v3
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
/dts-v1/;
#include
#include
#include "qca9557.dtsi"
/ {
compatible = "tplink,tl-wr1043nd-v2", "qca,qca9557";
model = "TP-Link TL-WR1043ND Version 2";
memory@0 {
device_type = "memory";
reg = <0x0 0x800>;
};
extosc: ref {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-output-names = "ref";
clock-frequency = <4000>;
};
leds {
compatible = "gpio-leds";
system {
label = "tp-link:green:system";
gpios = <&gpio 19 GPIO_ACTIVE_LOW>;
linux,default-trigger = "heartbeat";
};
usb {
label = "tp-link:green:usb";
gpios = <&gpio 15 GPIO_ACTIVE_LOW>;
default-state = "off";
};
wifi_green {
label = "tp-link:green:wlan";
gpios = <&gpio 12 GPIO_ACTIVE_LOW>;
default-state = "off";
};
wifi_wps {
label = "tp-link:green:wps";
gpios = <&gpio 18 GPIO_ACTIVE_LOW>;
default-state = "off";
};
};
keys {
compatible = "gpio-keys-polled";
#address-cells = <1>;
#size-cells = <0>;
poll-interval = <100>;
button@0 {
label = "Reset button";
linux,code = ;
gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
debounce-interval = <60>;
};
button@1 {
label = "RFKILL button";
linux
[LEDE-DEV] [PATCH] Add procd triggers only for interfaces that dnsmasq is interested in.
Signed-off-by: hux
---
Right now interface.update events are sent out by netifd upon interface state,
route, address (lifetime), prefix lifetime changes. Dnsmasq is only interested
in interface state changes and currently adds an interface trigger for all the
"interface.*" events.
In combination with commit 23bba9cb330, which triggers a SIGHUP signal to
dnsmasq, IPv6 address/prefix lifetime changes on the wan will trigger dnsmasq
reloads which can become frequent in case of shorter lifetimes.
To avoid frequent dnsmasq reload, this patch adds specific interface triggers.
During dnsmasq init, it loops dhcp uci section. If the value of the ignore
option is set to 0, then the corresponding interface trigger is not installed.
Otherwise, if the ignore option value is 1, then procd_add_interface_trigger is
called and the trigger is added.
package/network/services/dnsmasq/Makefile | 2 +-
package/network/services/dnsmasq/files/dnsmasq.init | 14 +-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/package/network/services/dnsmasq/Makefile
b/package/network/services/dnsmasq/Makefile
index b6502bf5d0..60ed9ed6fb 100644
--- a/package/network/services/dnsmasq/Makefile
+++ b/package/network/services/dnsmasq/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=dnsmasq
PKG_VERSION:=2.79
-PKG_RELEASE:=3
+PKG_RELEASE:=4
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz
PKG_SOURCE_URL:=http://thekelleys.org.uk/dnsmasq/
diff --git a/package/network/services/dnsmasq/files/dnsmasq.init
b/package/network/services/dnsmasq/files/dnsmasq.init
index 1881b2bcdc..2c71a777c3 100644
--- a/package/network/services/dnsmasq/files/dnsmasq.init
+++ b/package/network/services/dnsmasq/files/dnsmasq.init
@@ -1042,10 +1042,22 @@ dnsmasq_stop()
rm -f ${BASEDHCPSTAMPFILE}.${cfg}.*.dhcp
}
+add_interface_trigger()
+{
+ local interface ignore
+
+ config_get interface "$1" interface
+ config_get_bool ignore "$1" ignore 0
+
+ [ -n "$interface" -a $ignore -eq 0 ] && procd_add_interface_trigger
"interface.*" "$interface" /etc/init.d/dnsmasq reload
+}
+
service_triggers()
{
procd_add_reload_trigger "dhcp" "system"
- procd_add_raw_trigger "interface.*" 2000 /etc/init.d/dnsmasq reload
+
+ config_load dhcp
+ config_foreach add_interface_trigger dhcp
}
boot()
--
2.11.0
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: bump to 4.9.98
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 --- Compile-tested on: ipq806x Runtime-tested on: ipq806x Tested-by: Michael Yartys ‐‐‐ Original Message ‐‐‐ On 7 May 2018 6:56 PM, Kevin Darbyshire-Bryant via Lede-dev wrote: > 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.Refresh patches. > > Tested-on: ar71xx Archer C7 v2 > > Signed-off-by: Kevin Darbyshire-Bryant l...@darbyshire-bryant.me.uk > > include/kernel-version.mk | 4 ++-- > > .../linux/ar7/patches-4.9/300-add-ac49x-platform.patch | 4 ++-- > > .../403-mtd_fix_cfi_cmdset_0002_status_check.patch | 14 +++--- > > .../411-mtd-cfi_cmdset_0002-force-word-write.patch | 6 +++--- > > .../ar71xx/patches-4.9/500-MIPS-fw-myloader.patch | 2 +- > > .../ar71xx/patches-4.9/604-MIPS-ath79-no-of.patch | 2 +- > > target/linux/ath25/patches-4.9/107-ar5312_gpio.patch | 2 +- > > .../patches-4.9/950-0031-Add-dwc_otg-driver.patch | 2 +- > > ...-Fulfill-user-BO-creation-requests-from-the-k.patch | 2 +- > > ...-Fix-OOPSes-from-trying-to-cache-a-partially-.patch | 2 +- > > 15-01-MIPS-BCM63XX-add-clkdev-lookup-support.patch | 2 +- > > .../322-MIPS-BCM63XX-switch-to-IRQ_DOMAIN.patch | 2 +- > > target/linux/generic/hack-4.9/220-gc_sections.patch | 2 +- > > .../generic/hack-4.9/301-mips_image_cmdline_hack.patch | 2 +- > > .../generic/pending-4.9/300-mips_expose_boot_raw.patch | 4 ++-- > > .../generic/pending-4.9/304-mips_disable_fpu.patch | 2 +- > > ...PS-mm-remove-no-op-dma_map_ops-where-possible.patch | 12 ++-- > > ...-cfi_cmdset_0002-add-buffer-write-cmd-timeout.patch | 2 +- > > .../generic/pending-4.9/630-packet_socket_type.patch | 16 > > ...w-rejecting-with-source-address-failed-policy.patch | 16 > > .../generic/pending-4.9/890-uart_optional_sysrq.patch | 2 +- > > .../patches-4.9/090-increase_entropy_pools.patch | 2 +- > > target/linux/lantiq/patches-4.9/0152-lantiq-VPE.patch | 2 +- > > .../patches-4.9/817-usb-support-layerscape.patch | 18 +- > > .../patches-4.9/102-powerpc-add-cmdline-override.patch | 2 +- > > 25 files changed, 63 insertions(+), 63 deletions(-) > > diff --git a/include/kernel-version.mk b/include/kernel-version.mk > > index cf84e31f7b..fc0856554c 100644 > > --- a/include/kernel-version.mk > > +++ b/include/kernel-version.mk > > @@ -4,12 +4,12 @@ LINUX_RELEASE?=1 > > LINUX_VERSION-3.18 = .71 > > LINUX_VERSION-4.4 = .121 > > -LINUX_VERSION-4.9 = .96 > > +LINUX_VERSION-4.9 = .98 > > LINUX_VERSION-4.14 = .37 > > LINUX_KERNEL_HASH-3.18.71 = > 5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240 > > LINUX_KERNEL_HASH-4.4.121 = > 44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729 > > -LINUX_KERNEL_HASH-4.9.96 = > 826f596eb5197f8b17304649c2990dd7b766f5c79076cae79f4261c40cea877f > > +LINUX_KERNEL_HASH-4.9.98 = > 12cd90355adbc946e7e95aa5cdef2dd99b8e166cb64fe53a91c3e1d8f81810ef > > LINUX_KERNEL_HASH-4.14.37 = > 8197e7ed3620713e412905430a7bf93e2048384042ffba189a66f0eeb6908e92 > > remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1 > > diff --git a/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch > b/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch > > index 67ed3e494a..639f09709b 100644 > > --- a/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch > > +++ b/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch > > @@ -37,7 +37,7 @@ > > #define AR7_IRQ_UART0 15 > > --- a/arch/mips/Kconfig > > +++ b/arch/mips/Kconfig > > -@@ -160,7 +160,7 @@ config AR7 > > +@@ -161,7 +161,7 @@ config AR7 > > select HAVE_CLK > > help > > Support for the Texas Instruments AR7 System-on-a-Chip > > @@ -46,7 +46,7 @@ > > config ATH25 > > bool "Atheros AR231x/AR531x SoC support" > > -@@ -1004,6 +1004,7 @@ config MIPS_PARAVIRT > > +@@ -1005,6 +1005,7 @@ config MIPS_PARAVIRT > > endchoice > > source "arch/mips/alchemy/Kconfig" > > diff --git > a/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch > > b/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch > > index 415d835ee3..3a7fe99e65 100644 > > --- > a/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch > > +++ > b/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch > > @@ -1,6 +1,6 @@ > > --- a/drivers/mtd/chips/cfi_cmdset_0002.c > > +++ b/drivers/mtd/chips/cfi_cmdset_0002.c > > -@@ -1630,8 +1630,8 @@ static int __xipram do_write_oneword(str > > +@@ -1631,8 +1631,8 @@ static in
Re: [LEDE-DEV] [PATCH V1][RFC][procd] udevtrigger: trigger devices w/o dev sysfs entry
hi John, On 5/5/18 8:48 AM, John Crispin wrote: > > > On 22/03/18 16:22, Sergiy Kibrik wrote: >> A lot of devices aren't represented via major/minor numbers >> and thus don't have dev entry in their sysfs directory, like >> network devices, USB, power supplies etc. >> It looks to be the rigth thing to trigger them as well. >> >> Anyway, it's up to the hotplug daemon to decide what to do with devices, >> it needs full vision of what's present in the system. >> >> Signed-off-by: Sergiy Kibrik > > Hi, > sorry for the late reply. i just ran this patch on a router and it slows > boot down by ~1sec due to having to process a huge pile of extra events. > > --- before --- > [ 5.124584] random: procd: uninitialized urandom read (4 bytes read) > Press the [f] key and hit [enter] to enter failsafe mode > Press the [1], [2], [3] or [4] key and hit [enter] to select the debug > level > [ 7.489347] procd: - early - > > --- after --- > [ 5.128390] random: procd: uninitialized urandom read (4 bytes read) > Press the [f] key and hit [enter] to enter failsafe mode > Press the [1], [2], [3] or [4] key and hit [enter] to select the debug > level > [ 8.345346] procd: - early - > > are you trying to grab events for a specific device type ? maybe we can > narrow this down a bit more and not process all events during coldplug. > I'm detecting a hotplug (or disconnect) of USB OTG power supply. Device classes which aren't represented by dev entry seem to be left w/o a sensible way to handle events from them... -- regards, Sergiy signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 2/2] kernel: bump 4.14 to 4.14.38
W dniu 07.05.2018 o 14:46, Koen Vandeputte pisze: > > > On 2018-05-06 23:41, Koen Vandeputte wrote: >> >> >> On 06-05-18 19:25, Tomasz Maciej Nowak wrote: >>> Hi Koen. >>> >>> W dniu 03.05.2018 o 11:57, Koen Vandeputte pisze: All, Please skip these. It does not apply anymore due to: "kernel: add missing in6_dev_put_clear call to an ipv6 network patch" Also .. yet another kernel bump was released yesterday .. >>> If You'll be doing kernel bump for 4.14.39 or later, You cane safely drop >>> these patches: >>> >>> target/linux/mvebu/patches-4.14/522-PCI-aardvark-fix-logic-in-PCI-configuration-read-write-functions.patch >>> target/linux/mvebu/patches-4.14/523-PCI-aardvark-set-PIO_ADDR_LS-correctly-in-advk_pcie_rd_conf.patch >>> target/linux/mvebu/patches-4.14/524-PCI-aardvark-set-host-and-device-to-the-same-MAX-payload-size.patch >>> target/linux/mvebu/patches-4.14/525-PCI-aardvark-use-isr1-instead-of-isr0-interrupt-in-legacy-irq-mode.patch >>> target/linux/mvebu/patches-4.14/526-PCI-aardvark-disable-LOS-state-by-default.patch >>> target/linux/mvebu/patches-4.14/527-PCI-aardvark-fix-PCIe-max-read-request-size-setting.patch >>> >>> Thanks for all Your work. >> Hi, >> I started working on the V2 last week, and it seems not all of these were >> upstreamed. >> If I have some time, I'll check it further in detail tomorrow how it should >> be handled. >> > I've gone into the details of it, also checking the online discussions > between the author and Bjorn Helgaas. [1] > > It seems it is still ongoing .. and the safest option according to me is to > keep the MPS at 128 for now, ensuring no malformed communication happens > between the RC and the endpoints. > Dropping this patch would be cleaner and might very slightly improving > performance, but at the cost of potential communication errors with specific > devices. > > The disable-LoS patch is similar and should also be kept for now. > > > Please let me know if you disagree (and why :) ) > OK, seems I was bit to hasty. That's a valid point about those two patches. Given that Thomas dropped the mentioned patches in later series revision [1] and is working on better solution, let's keep them for now (better safe than sorry). Initially I added the whole series regarding this [2] bug report. That made the mini PCIe port working without kernel lockups or panics. After some of the patches got accepted, I removed the series and included the fixes which still made my cards JWX6051 (ath9k) and U7612E-H1 (mt76) working, didn't observe any issues. Unfortunately since the beginning my board is missing one element and it's not providing 1.5V to mini PCIe port, so cards requiring it do not work. Because of that my testing has been limited. Last week I ordered the missing element and at end of the week I should be ready for testing the rest of cards. I'll report back if those test show any difference with or without those patches. 1. https://www.spinics.net/lists/linux-pci/msg70774.html 2. https://bugzilla.kernel.org/show_bug.cgi?id=196339 > > Koen > > [1] https://patchwork.kernel.org/patch/9976017/ V2 later on .. Koen >>> Cheers, Tomasz. >>> >> > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev Regards, Tomasz. -- TMN ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
Citeren Jo-Philipp Wich : Hi Bjørn, the current timings of the DO zone are: ;; ANSWER SECTION: openwrt.org.1800 IN SOA ns1.digitalocean.com. hostmaster.openwrt.org. ( 1525688668 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 1800 ; minimum (30 minutes) ) This all looks fine, but what slightly worries me that the nameservers listed in the Whois information for openwrt.org still mention the old ones: whois openwrt.org Domain Name: OPENWRT.ORG Registry Domain ID: D104186352-LROR Registrar WHOIS Server: whois.tucows.com Registrar URL: http://www.tucows.com Updated Date: 2018-05-06T20:40:09Z [...] Name Server: ARRAKIS.DUNE.HU Name Server: BELATEGEUSE.DUNE.HU Name Server: SOAPSTONE.YURI.ORG.UK I've switched nameservers for several of my domains (including .org) and I recall this never took more than a few hours. It could be I'm impatient, but as of now, when running a trace, the above are still listed as the openwrt.org nameservers. Of course, *caches* would show stale data for up to a day, but running 'dig soa +trace openwrt.org' should resolve to the DO nameservers by now. dig +trace openwrt.org @resolver1.opendns.com ; <<>> DiG 9.11.2 <<>> +trace openwrt.org @resolver1.opendns.com ;; global options: +cmd . 518400 IN NS a.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS m.root-servers.net. ;; Received 239 bytes from 208.67.222.222#53(resolver1.opendns.com) in 6 ms org.172800 IN NS b2.org.afilias-nst.org. org.172800 IN NS d0.org.afilias-nst.org. org.172800 IN NS a2.org.afilias-nst.info. org.172800 IN NS b0.org.afilias-nst.org. org.172800 IN NS a0.org.afilias-nst.info. org.172800 IN NS c0.org.afilias-nst.info. org.86400 IN DS 9795 7 2 3922B31B6F3A4EA92B19EB7B52120F031FD8E05FF0B03BAFCF9F891B FE7FF8E5 org.86400 IN DS 9795 7 1 364DFAB3DAF254CAB477B5675B10766DDAA24982 org.86400 IN RRSIG DS 8 1 86400 2018052017 2018050716 39570 . XKyDB9S0mMInUMOgX8U0H3/Kjvrj4AuiYRfnxyYUMD/LLOQhTSRv/xKQ OWl2jQB7wq3hQEecQn+Zd/410BxtWZ4xxv8dYRKqt8m9HEZzG/b0gDje wOqOANWZ8v7StnYlNWUFvS11q0rG0yFubSy+TO6aIQQ4aHA7ZmqPGfzq CbfqWv6ynMfNtdzQJS4+3kZlTmYKUqZrEAL3o3/7qD5cmSp7buqI8W5j /oTV3Ku74Xo1RDd6RXSZi8aYXKYu6PJ6N82o73OEPzqhWVgjX8KC4aOP VoQajzCX5YFAlYXpjtcgJti0/3HqeVqnpHtPF8sSroDCnUFIB+IlNBy2 b0M5lg== ;; Received 813 bytes from 2001:500:12::d0d#53(g.root-servers.net) in 37 ms openwrt.org.86400 IN NS arrakis.dune.hu. openwrt.org.86400 IN NS belategeuse.dune.hu. openwrt.org.86400 IN NS soapstone.yuri.org.uk. h9p7u7tr2u91d0v0ljs9l1gidnp90u3h.org. 86400 IN NSEC3 1 1 1 D399EAAB H9PARR669T6U8O1GSG9E1LMITK4DEM0T NS SOA RRSIG DNSKEY NSEC3PARAM h9p7u7tr2u91d0v0ljs9l1gidnp90u3h.org. 86400 IN RRSIG NSEC3 7 2 86400 20180528183058 20180507173058 1862 org. J1DhIPJyQfBjOpsQYwFcQC2vZcgxohyH+56fQvSKNKd86uvtk5szsjlS GpbkcA03uSqpNNuaj5lj+MzfedQvaHfxxVKQI+3cEsBqPVfN9oAvu2Lv wKVsIIaAm8sS0/l8DR4Xryz+5DAjZCfdjZq+sRNbDYc8dGpsQXkCZfRe StY= 6tvuefea073v78a07f9tbfq3d98qfrud.org. 86400 IN NSEC3 1 1 1 D399EAAB 6U03DTEM7DQG048778H41JO23I0SKBJT A RRSIG 6tvuefea073v78a07f9tbfq3d98qfrud.org. 86400 IN RRSIG NSEC3 7 2 86400 20180522152438 20180501142438 1862 org. BuA1elggJfC0Gax9Rzfb+GKx5S9NWbleZKWskqIqjLsS6tVVqvB46Q/M OYg2kav8gBg2zOv7zNywOKuQH4W4hYfVwqTVnb/iE2r2pHefEDh21ZZD RcrdfqJ082D7tvPe+/31qZdtjwashQ+R3Gr0WZLRhA+o4NK2Gwp/8ZGX Irs= ;; Received 623 bytes from 199.19.53.1#53(c0.org.afilias-nst.info) in 6 ms ;; Received 40 bytes from 78.47.151.105#53(soapstone.yuri.org.uk) in 16 ms They still don't. Regards, Jo ___ Lede-dev mailing list Lede-dev@lists.infradead.org
[LEDE-DEV] [PATCH] kernel: bump to 4.9.98
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 --- Refresh patches. Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant --- include/kernel-version.mk | 4 ++-- .../linux/ar7/patches-4.9/300-add-ac49x-platform.patch | 4 ++-- .../403-mtd_fix_cfi_cmdset_0002_status_check.patch | 14 +++--- .../411-mtd-cfi_cmdset_0002-force-word-write.patch | 6 +++--- .../ar71xx/patches-4.9/500-MIPS-fw-myloader.patch | 2 +- .../ar71xx/patches-4.9/604-MIPS-ath79-no-of.patch | 2 +- target/linux/ath25/patches-4.9/107-ar5312_gpio.patch | 2 +- .../patches-4.9/950-0031-Add-dwc_otg-driver.patch | 2 +- ...-Fulfill-user-BO-creation-requests-from-the-k.patch | 2 +- ...-Fix-OOPSes-from-trying-to-cache-a-partially-.patch | 2 +- 15-01-MIPS-BCM63XX-add-clkdev-lookup-support.patch | 2 +- .../322-MIPS-BCM63XX-switch-to-IRQ_DOMAIN.patch| 2 +- target/linux/generic/hack-4.9/220-gc_sections.patch| 2 +- .../generic/hack-4.9/301-mips_image_cmdline_hack.patch | 2 +- .../generic/pending-4.9/300-mips_expose_boot_raw.patch | 4 ++-- .../generic/pending-4.9/304-mips_disable_fpu.patch | 2 +- ...PS-mm-remove-no-op-dma_map_ops-where-possible.patch | 12 ++-- ...-cfi_cmdset_0002-add-buffer-write-cmd-timeout.patch | 2 +- .../generic/pending-4.9/630-packet_socket_type.patch | 16 ...w-rejecting-with-source-address-failed-policy.patch | 16 .../generic/pending-4.9/890-uart_optional_sysrq.patch | 2 +- .../patches-4.9/090-increase_entropy_pools.patch | 2 +- target/linux/lantiq/patches-4.9/0152-lantiq-VPE.patch | 2 +- .../patches-4.9/817-usb-support-layerscape.patch | 18 +- .../patches-4.9/102-powerpc-add-cmdline-override.patch | 2 +- 25 files changed, 63 insertions(+), 63 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index cf84e31f7b..fc0856554c 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -4,12 +4,12 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .71 LINUX_VERSION-4.4 = .121 -LINUX_VERSION-4.9 = .96 +LINUX_VERSION-4.9 = .98 LINUX_VERSION-4.14 = .37 LINUX_KERNEL_HASH-3.18.71 = 5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240 LINUX_KERNEL_HASH-4.4.121 = 44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729 -LINUX_KERNEL_HASH-4.9.96 = 826f596eb5197f8b17304649c2990dd7b766f5c79076cae79f4261c40cea877f +LINUX_KERNEL_HASH-4.9.98 = 12cd90355adbc946e7e95aa5cdef2dd99b8e166cb64fe53a91c3e1d8f81810ef LINUX_KERNEL_HASH-4.14.37 = 8197e7ed3620713e412905430a7bf93e2048384042ffba189a66f0eeb6908e92 remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1 diff --git a/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch b/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch index 67ed3e494a..639f09709b 100644 --- a/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch +++ b/target/linux/ar7/patches-4.9/300-add-ac49x-platform.patch @@ -37,7 +37,7 @@ #define AR7_IRQ_UART0 15 --- a/arch/mips/Kconfig +++ b/arch/mips/Kconfig -@@ -160,7 +160,7 @@ config AR7 +@@ -161,7 +161,7 @@ config AR7 select HAVE_CLK help Support for the Texas Instruments AR7 System-on-a-Chip @@ -46,7 +46,7 @@ config ATH25 bool "Atheros AR231x/AR531x SoC support" -@@ -1004,6 +1004,7 @@ config MIPS_PARAVIRT +@@ -1005,6 +1005,7 @@ config MIPS_PARAVIRT endchoice source "arch/mips/alchemy/Kconfig" diff --git a/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch b/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch index 415d835ee3..3a7fe99e65 100644 --- a/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch +++ b/target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch @@ -1,6 +1,6 @@ --- a/drivers/mtd/chips/cfi_cmdset_0002.c +++ b/drivers/mtd/chips/cfi_cmdset_0002.c -@@ -1630,8 +1630,8 @@ static int __xipram do_write_oneword(str +@@ -1631,8 +1631,8 @@ static int __xipram do_write_oneword(str break; } @@ -11,7 +11,7 @@ /* Latency issues. Drop the lock, wait a while and retry */ UDELAY(map, chip, adr, 1); -@@ -1647,6 +1647,8 @@ static int __xipram do_write_oneword(str +@@ -1648,6 +1648,8 @@ static int __xipram do_write_oneword(str ret = -EIO; } @@ -20,7 +20,7 @@ xip_enable(map, chip, adr); op_done: if (mode == FL_OTP_WRITE) -@@ -2225,7 +2227,6 @@ static int cfi_amdstd_panic_write(struct +@@ -2226,7 +2228,6 @@ static int cfi_amdstd_panic_write(struct return 0; } @@ -28,7 +28,
Re: [LEDE-DEV] OFF: openwrt.org down?
On 07/05/2018 13:21, Levente wrote: lev@mercury:~$ nslookup openwrt.org ;; Got SERVFAIL reply from 10.0.99.111, trying next server Server:10.0.99.99 Address:10.0.99.99#53 ** server can't find openwrt.org: SERVFAIL ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev They changed their main DNS servers, you can't access the site until your DNS provider has refreshed their lists to reflect this change. I had the same issue on my tethering connection, I set up manual IP and set OpenDNS as DNS server (which is usually better than whatever default DNS you might have on your device) 208.67.222.222 and fallback 208.67.222.220 like I do on my home network, now I can reach openwrt.org. -Alberto ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 1/2] helpers: make the proto field as a list rather than one option
Hi Pierre, is there anything speaking against just adding a 2nd section for TCP? ~ Jo ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH 2/2] helpers.conf: support also tcp in the CT sip helper
Signed-off-by: Pierre Lebleu --- helpers.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/helpers.conf b/helpers.conf index 5591a8f..b8ae857 100644 --- a/helpers.conf +++ b/helpers.conf @@ -67,7 +67,7 @@ config helper option description 'SIP VoIP connection tracking' option module 'nf_conntrack_sip' option family 'any' - option proto 'udp' + option proto 'tcpudp' option port '5060' config helper -- 1.9.1 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH 1/2] helpers: make the proto field as a list rather than one option
The field proto in the struct fw3_cthelper should be implemented
as a list in order to support multiple protocols.
For example, the helper for SIP should be able to support both
TCP and UDP within only one entry in the config file.
config helper
option name 'sip'
option description 'SIP VoIP connection tracking'
option module 'nf_conntrack_sip'
option family 'any'
option proto 'tcpudp'
option port '5060'
Signed-off-by: Pierre Lebleu
---
helpers.c | 56 +---
helpers.h | 3 +++
options.h | 2 +-
redirects.c | 2 +-
rules.c | 4 ++--
5 files changed, 56 insertions(+), 11 deletions(-)
diff --git a/helpers.c b/helpers.c
index 8cad0b3..36317d2 100644
--- a/helpers.c
+++ b/helpers.c
@@ -25,7 +25,7 @@ const struct fw3_option fw3_cthelper_opts[] = {
FW3_OPT("module", string, cthelper, module),
FW3_OPT("description", string, cthelper, description),
FW3_OPT("family", family, cthelper, family),
- FW3_OPT("proto", protocol, cthelper, proto),
+ FW3_LIST("proto", protocol, cthelper, proto),
FW3_OPT("port",port, cthelper, port),
{ }
@@ -47,6 +47,23 @@ test_module(struct fw3_cthelper *helper)
}
static bool
+check_cthelper_proto(const struct fw3_cthelper *helper)
+{
+ struct fw3_protocol *proto;
+
+ if (list_empty(&helper->proto))
+ return false;
+
+ list_for_each_entry(proto, &helper->proto, list)
+ {
+ if (!proto->protocol || proto->any || proto->invert)
+ return false;
+ }
+
+ return true;
+}
+
+static bool
check_cthelper(struct fw3_state *state, struct fw3_cthelper *helper, struct
uci_element *e)
{
if (!helper->name || !*helper->name)
@@ -57,7 +74,7 @@ check_cthelper(struct fw3_state *state, struct fw3_cthelper
*helper, struct uci_
{
warn_section("helper", helper, e, "must have a module
assigned");
}
- else if (!helper->proto.protocol || helper->proto.any ||
helper->proto.invert)
+ else if (!check_cthelper_proto(helper))
{
warn_section("helper", helper, e, "must specify a protocol");
}
@@ -84,6 +101,7 @@ fw3_alloc_cthelper(struct fw3_state *state)
helper->enabled = true;
helper->family = FW3_FAMILY_ANY;
+ INIT_LIST_HEAD(&helper->proto);
list_add_tail(&helper->list, &state->cthelpers);
@@ -157,6 +175,20 @@ fw3_lookup_cthelper(struct fw3_state *state, const char
*name)
return NULL;
}
+bool
+fw3_cthelper_check_proto(const struct fw3_cthelper *h, const struct
fw3_protocol *proto)
+{
+ struct fw3_protocol *p;
+
+ list_for_each_entry(p, &h->proto, list)
+ {
+ if (p->protocol == proto->protocol)
+ return true;
+ }
+
+ return false;
+}
+
struct fw3_cthelper *
fw3_lookup_cthelper_by_proto_port(struct fw3_state *state,
struct fw3_protocol *proto,
@@ -178,7 +210,7 @@ fw3_lookup_cthelper_by_proto_port(struct fw3_state *state,
if (!h->enabled)
continue;
- if (h->proto.protocol != proto->protocol)
+ if (!fw3_cthelper_check_proto(h, proto))
continue;
if (h->port.set && (!port || !port->set))
@@ -198,11 +230,11 @@ fw3_lookup_cthelper_by_proto_port(struct fw3_state *state,
static void
print_helper_rule(struct fw3_ipt_handle *handle, struct fw3_cthelper *helper,
- struct fw3_zone *zone)
+ struct fw3_zone *zone, struct fw3_protocol *proto)
{
struct fw3_ipt_rule *r;
- r = fw3_ipt_rule_create(handle, &helper->proto, NULL, NULL, NULL, NULL);
+ r = fw3_ipt_rule_create(handle, proto, NULL, NULL, NULL, NULL);
if (helper->description && *helper->description)
fw3_ipt_rule_comment(r, helper->description);
@@ -215,6 +247,16 @@ print_helper_rule(struct fw3_ipt_handle *handle, struct
fw3_cthelper *helper,
fw3_ipt_rule_replace(r, "zone_%s_helper", zone->name);
}
+static void
+expand_helper_rule(struct fw3_ipt_handle *handle, struct fw3_cthelper *helper,
+ struct fw3_zone *zone)
+{
+ struct fw3_protocol *proto;
+
+ list_for_each_entry(proto, &helper->proto, list)
+ print_helper_rule(handle, helper, zone, proto);
+}
+
void
fw3_print_cthelpers(struct fw3_ipt_handle *handle, struct fw3_state *state,
struct fw3_zone *zone)
@@ -249,7 +291,7 @@ fw3_print_cthelpers(struct fw3_ipt_handle *handle, struct
fw3_state *state,
if (!test_module(helper))
continue;
- print_helper_rule(handle, helper, zone);
+ expand_helper_rule(handle, helper, zone);
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
Hi Bjørn, the current timings of the DO zone are: ;; ANSWER SECTION: openwrt.org.1800 IN SOA ns1.digitalocean.com. hostmaster.openwrt.org. ( 1525688668 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 1800 ; minimum (30 minutes) ) Regards, Jo ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
Jo-Philipp Wich writes: > Hi Joerg, John. > > I created an openwrt.org zone on Digital Ocean now so you could delegate > the name servers to ns1.digitalocean.com, ns2.digitalocean.com and > ns3.digitalocean.com, maybe with one of the SPI machines thrown into the > mix... Good! I hope you implicitly fixed one important issue I missed yesterday: The openwrt.org SOA expire value was extremely low, greatly increasing the risk of ending up where we are now - with all slaves failing due to a failing master. Scrolling back in one of my terminals I found this: openwrt.org.14400 IN SOA arrakis.dune.hu. root.dune.hu. 2018020702 3600 600 86400 3600 I am not entirely sure what the current best practice is, but I don't think I've ever seen anyone recommending anyting less than a week. Using 24 hours is ehhm risky is the most polite I can think of. The lede-project.org SOA looks fine, so I'd recommend you just copy those timeouts (which you probably already did?) Bjørn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 2/2] kernel: bump 4.14 to 4.14.38
On 2018-05-06 23:41, Koen Vandeputte wrote: On 06-05-18 19:25, Tomasz Maciej Nowak wrote: Hi Koen. W dniu 03.05.2018 o 11:57, Koen Vandeputte pisze: All, Please skip these. It does not apply anymore due to: "kernel: add missing in6_dev_put_clear call to an ipv6 network patch" Also .. yet another kernel bump was released yesterday .. If You'll be doing kernel bump for 4.14.39 or later, You cane safely drop these patches: target/linux/mvebu/patches-4.14/522-PCI-aardvark-fix-logic-in-PCI-configuration-read-write-functions.patch target/linux/mvebu/patches-4.14/523-PCI-aardvark-set-PIO_ADDR_LS-correctly-in-advk_pcie_rd_conf.patch target/linux/mvebu/patches-4.14/524-PCI-aardvark-set-host-and-device-to-the-same-MAX-payload-size.patch target/linux/mvebu/patches-4.14/525-PCI-aardvark-use-isr1-instead-of-isr0-interrupt-in-legacy-irq-mode.patch target/linux/mvebu/patches-4.14/526-PCI-aardvark-disable-LOS-state-by-default.patch target/linux/mvebu/patches-4.14/527-PCI-aardvark-fix-PCIe-max-read-request-size-setting.patch Thanks for all Your work. Hi, I started working on the V2 last week, and it seems not all of these were upstreamed. If I have some time, I'll check it further in detail tomorrow how it should be handled. I've gone into the details of it, also checking the online discussions between the author and Bjorn Helgaas. [1] It seems it is still ongoing .. and the safest option according to me is to keep the MPS at 128 for now, ensuring no malformed communication happens between the RC and the endpoints. Dropping this patch would be cleaner and might very slightly improving performance, but at the cost of potential communication errors with specific devices. The disable-LoS patch is similar and should also be kept for now. Please let me know if you disagree (and why :) ) Koen [1] https://patchwork.kernel.org/patch/9976017/ V2 later on .. Koen Cheers, Tomasz. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] brcm2708: add squashfs rootfs image
On Saturday, May 5, 2018 3:44:15 PM CEST Paul Spooren wrote:
> On Thu, Mar 29, 2018 at 9:22 AM, Daniel Golle
> wrote:
> > On Tue, Mar 27, 2018 at 07:42:18PM +0200, Christian Lamparter wrote:
> >> This patch adds a image with squashfs as the root filesystem.
> >> A rootfs_data partition will be generated on the first boot
> >> and placed inside the rootfs partition (just after the squashfs
> >> image).
> >> [...]
>
> I tried the patch and the created squashfs works! However, trying a
> sysupgrade errored saying it's unsupported.
Ok, I can look into this, but I would need more information to
debug it:
Can you please trace from where the message is coming from?
By chance: Does it look it is created by the fwtool check? [0]
("Device $device is not supported by this image") or was it a
different message?
Also, can you please tell me which sysupgrade method
(good-old sysupgrade via ssh/serial or the LuCI App) you used?
If you went through ssh, it should look like this: (tested with rpi-b)
|squashfs:
|root@rpi-b:/tmp# sysupgrade -v
openwrt-brcm2708-bcm2708-rpi-squashfs-sdcard.img.gz
|Reading partition table from bootdisk...
|Reading partition table from image...
|Saving config files...
|boot/config.txt
|etc/config/attendedsysupgrade
|[...]
|etc/uhttpd.crt
|Commencing upgrade. All shell sessions will be closed now.
|Connection to rpi-b closed by remote host.
|Connection to rpi-b closed.
and for ext4:
|root@rpi-b:/tmp# sysupgrade -v openwrt-brcm2708-bcm2708-rpi-ext4-sdcard.img.gz
|Reading partition table from bootdisk...
|Reading partition table from image...
|Saving config files...
|boot/config.txt
|etc/config/attendedsysupgrade
|[...]
|etc/uhttpd.crt
|Commencing upgrade. All shell sessions will be closed now.
|Connection to rpi-b closed by remote host.
|Connection to rpi-b closed.
In my testing the LuCI app did work as well, as long as I tested with
the rpi-3 (this is a bit of a problem, since it has a use... unlike the
old rpi-b it replaced). The rpi-b is currently not in the snapshot.yml [2].
(But there's an easy WA: edit /tmp/sysinfo/board_name).
As for adding the various RaspberryPI: There's the issue that the RPI-3(+)
and RPI3-CM can also have the rpi-2 image installed because the user
specifically wanted the 32-bit ARMv7 environment (over the 64-Bit ARMv8).
And this is a problem, because the database model 'board_rename_table' in
tables.sql [3] does not look like it can handle 1:n mappings required
for this case.
> Is it possible we have to teach the sysupgrade that squashfs is compatible,
> too?
I switched the brcm2708 target to x86's sysupgrade routines in
"brcm2708: use x86's upgrade scripts for all rpi targets" [1].
This sysupgrade method works by comparing the MBR partition layout
on the sdcard and if the layout is compatible it "dd" the
(extracted) data into the /dev/mmcblk0p[12] partitions. The method
and tools don't really care about whats in the partitions though.
It should work regardless of what filesystem is being used...
so yeah: o_O?! (I'm really wondering what went wrong?)
> Except from that, it works and runs with no problems on my RPI3, please
> merge.
>
> Regarding the doubts of Christian, is there any problem producing the
> ext4 and squashfs per default?
Maybe CDN? Since two images are now created for every (sub-)target.
That said, x86 is doing the same with combined-ext4.img.gz and
combined-squash.img.gz ;) . Maybe someone can provide some
downloadstats on which image is more popular?
Best Regards,
Christian
[0]
[1]
[2]
[3]
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] OFF: openwrt.org down?
lev@mercury:~$ nslookup openwrt.org ;; Got SERVFAIL reply from 10.0.99.111, trying next server Server:10.0.99.99 Address:10.0.99.99#53 ** server can't find openwrt.org: SERVFAIL ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] dnsmasq: bump to 2.80test2
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 ---
Refresh patches and backport:
Be persistent with broken-upstream-DNSSEC warnings.
Fix DHCP broken-ness when --no-ping AND --dhcp-sequential-ip are set.
Add logging for DNS error returns from upstream and local configuration.
Compile & run tested: ar71xx Archer C7 v2
Signed-off-by: Kevin Darbyshire-Bryant
---
package/network/services/dnsmasq/Makefile | 8 +-
...tent-with-broken-upstream-DNSSEC-warnings.patch | 26 +++
...oken-ness-when-no-ping-AND-dhcp-sequentia.patch | 35
...-for-DNS-error-returns-from-upstream-and-.patch | 184 +
.../services/dnsmasq/patches/240-ubus.patch| 8 +-
5 files changed, 253 insertions(+), 8 deletions(-)
create mode 100644
package/network/services/dnsmasq/patches/0001-Be-persistent-with-broken-upstream-DNSSEC-warnings.patch
create mode 100644
package/network/services/dnsmasq/patches/0002-Fix-DHCP-broken-ness-when-no-ping-AND-dhcp-sequentia.patch
create mode 100644
package/network/services/dnsmasq/patches/0003-Add-logging-for-DNS-error-returns-from-upstream-and-.patch
diff --git a/package/network/services/dnsmasq/Makefile
b/package/network/services/dnsmasq/Makefile
index b6502bf5d0..7fa61ad04f 100644
--- a/package/network/services/dnsmasq/Makefile
+++ b/package/network/services/dnsmasq/Makefile
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=dnsmasq
-PKG_VERSION:=2.79
-PKG_RELEASE:=3
+PKG_VERSION:=2.80test2
+PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz
-PKG_SOURCE_URL:=http://thekelleys.org.uk/dnsmasq/
-PKG_HASH:=78ad74f5ca14fd85a8bac93f764cd9d60b27579e90eabd3687ca7b030e67861f
+PKG_SOURCE_URL:=http://thekelleys.org.uk/dnsmasq/test-releases
+PKG_HASH:=e731666094699afcbad947f89f7f8afbf92e5ddc3c915459d4936159d81116f0
PKG_LICENSE:=GPL-2.0
PKG_LICENSE_FILES:=COPYING
diff --git
a/package/network/services/dnsmasq/patches/0001-Be-persistent-with-broken-upstream-DNSSEC-warnings.patch
b/package/network/services/dnsmasq/patches/0001-Be-persistent-with-broken-upstream-DNSSEC-warnings.patch
new file mode 100644
index 00..beeb15435c
--- /dev/null
+++
b/package/network/services/dnsmasq/patches/0001-Be-persistent-with-broken-upstream-DNSSEC-warnings.patch
@@ -0,0 +1,26 @@
+From f84e674d8aa2316fea8d2145a40fcef0441e3856 Mon Sep 17 00:00:00 2001
+From: Simon Kelley
+Date: Fri, 4 May 2018 16:29:57 +0100
+Subject: [PATCH 1/3] Be persistent with broken-upstream-DNSSEC warnings.
+
+Signed-off-by: Kevin Darbyshire-Bryant
+---
+ src/dnssec.c | 7 +--
+ 1 file changed, 1 insertion(+), 6 deletions(-)
+
+--- a/src/dnssec.c
b/src/dnssec.c
+@@ -876,12 +876,7 @@ int dnssec_validate_ds(time_t now, struc
+
+ if (rc == STAT_INSECURE)
+ {
+- static int reported = 0;
+- if (!reported)
+- {
+-reported = 1;
+-my_syslog(LOG_WARNING, _("Insecure DS reply received, do upstream DNS
servers support DNSSEC?"));
+- }
++ my_syslog(LOG_WARNING, _("Insecure DS reply received, do upstream DNS
servers support DNSSEC?"));
+ rc = STAT_BOGUS;
+ }
+
diff --git
a/package/network/services/dnsmasq/patches/0002-Fix-DHCP-broken-ness-when-no-ping-AND-dhcp-sequentia.patch
b/package/network/services/dnsmasq/patches/0002-Fix-DHCP-broken-ness-when-no-ping-AND-dhcp-sequentia.patch
new file mode 100644
index 00..eb15113857
--- /dev/null
+++
b/package/network/services/dnsmasq/patches/0002-Fix-DHCP-broken-ness-when-no-ping-AND-dhcp-sequentia.patch
@@ -0,0 +1,35 @@
+From 0669ee7a69a004ce34fed41e50aa575f8e04427b Mon Sep 17 00:00:00 2001
+From: Simon Kelley
+Date: Fri, 4 May 2018 16:46:24 +0100
+Subject: [PATCH 2/3] Fix DHCP broken-ness when --no-ping AND
+ --dhcp-sequential-ip are set.
+
+Signed-off-by: Kevin Darbyshire-Bryant
+---
+ CHANGELOG | 3 ++-
+ src/dhcp.c | 2 +-
+ 2 files changed, 3 insertions(+), 2 deletions(-)
+
+--- a/CHANGELOG
b/CHANGELOG
+@@ -14,7 +14,8 @@ version 2.80
+ when the upstream namesevers do not support DNSSEC, and in this
+ case no DNSSEC validation at all is occuring.
+
+-
++Fix DHCP broken-ness when --no-ping AND --dhcp-sequential-ip
++ are set. Thanks to Daniel Miess for help with this.
+
+
+ version 2.79
+--- a/src/dhcp.c
b/src/dhcp.c
+@@ -678,7 +678,7 @@ struct ping_result *do_icmp_ping(time_t
+ if ((count >= max) || option_bool(OPT_NO_PING) || loopback)
+ {
+ /* overloaded, or configured not to check, loopback interface, return
"not in use" */
+- dummy.hash = 0;
++ dummy.hash = hash;
+ return &dummy;
+ }
+ else if (icmp_ping(addr))
diff --git
a/package/network/services/dnsmasq/patches/0003-Add-logging-for-DNS-error-returns-from-upstream-and-.patch
b/package/network/services/dnsmasq/pat
Re: [LEDE-DEV] MMAP memory out of sync on AR71xx Rambutan (8devices) board.
On 05/06/2018 09:00 PM, Rosen Penev wrote: > On Sun, May 6, 2018 at 10:08 AM, Rosen Penev wrote: >> On Sun, May 6, 2018 at 3:52 AM, Daniel Danzberger wrote: >>> MMAP'ed memory that has been allocated via 'get_zeroed_page(GFP_KERNEL)' or >>> 'vmalloc()' doesn't always contain the same data when accessed from >>> userspace. >>> >>> This means all userspace programs using mmap to access kernel memory aren't >>> always working properly on the Rambutan board. I am currently testing if >>> other >>> ar71xx devices are affected as well. >>> >>> I first noticed this when using ALSA's mmap api to capture audio. >>> >>> Here is the feed for a kmod + userpace util to reproduce the issue: >>> g...@github.com:dddaniel/mmaptest.git >>> >>> The kernel module simply allocates a page and initializes it with 0xff. >>> The userspace application then mmap's and reads this page 10 times with a >>> 500ms >>> delay an checks if all data is 0xff. >>> >>> --- >>> root@OpenWrt:/# mmaptest-user >>> mmap addr: 0x77a04000 >>> [ 760.464968] mmap page 7573000 at va 87573000 >>> check memory ...FAIL (at byte 0) >>> check memory ...FAIL (at byte 96) >>> check memory ...FAIL (at byte 96) >>> check memory ...FAIL (at byte 96) >>> check memory ...FAIL (at byte 128) >>> --- >>> >>> I have no idea whats causing it. Does anybody have a hint on how to fix >>> this ? >>> >> Try reverting >> https://github.com/torvalds/linux/commit/c00ab4896ed5f7d89af6f90b809e2c0197c6d170 > Disregard that. That commit should have no impact. > > I just tested it on an Archer C7v4 and the issue is present as well. > This was probably causing data corruption for me when I used an > external hard drive... > > Strange that sometimes it works and sometimes not.Yes, the same in my tests. > Look's like this issue appears on all ar71xx devices. > > Did you encounter this issue with kernel 4.9? For me, 4.4 caused no > data corruption on my external hard drive. I can't tell right now. I was trying to use an older version with kernel 4.4, but it fails to build. > > There seems to be a pattern with kernel 4.9 breaking various MIPS devices... >>> -- >>> Regards >>> >>> Daniel Danzberger >>> embeDD GmbH, Alter Postplatz 2, CH-6370 Stans >>> >>> ___ >>> Lede-dev mailing list >>> Lede-dev@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/lede-dev > -- Regards Daniel Danzberger embeDD GmbH, Alter Postplatz 2, CH-6370 Stans ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] new ath79 target
On 07/05/18 08:13, John Crispin wrote: Hi, I have just pushed the new ath79 target to trunk. This will replace ar71xx mid term, switching the target over to pure OF. a few boards are already supported, would be great if people could start moving boards over that they use. I am available to help via ML, mail, irc, ... AHB wifi is still missing but we'll get that working the next few days. John small note as i know a few folks are already starting to use the target, the set_speed() and set_mii() callbacks used inside ag71xx_main/adjust_link are not fully implemented for some of the newer QCA silicon as i did not have access to that HW. I already added empty if clauses for the relevant SoCs. so if you are not getting any link up and/or traffic flow, this should be the first place to look. If you fail to recognize the PHYs also let me know and paste your dts while doing so, John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ath79: u-boot partitions should be read-only in dts
Some of the new ath79 device trees were missing read-only tags on the
u-boot partitions. This adds the tags where previously missing.
Signed-off-by: Russell Senior
---
target/linux/ath79/dts/ar7241_ubnt-unifi.dts | 1 +
target/linux/ath79/dts/ar7241_ubnt-xm.dtsi | 1 +
target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts | 1 +
3 files changed, 3 insertions(+)
diff --git a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
index aaafb08424..9c8c86cb97 100644
--- a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
+++ b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
@@ -71,6 +71,7 @@
partition@0 {
label = "u-boot";
reg = <0x00 0x04>;
+ read-only;
};
partition@1 {
diff --git a/target/linux/ath79/dts/ar7241_ubnt-xm.dtsi
b/target/linux/ath79/dts/ar7241_ubnt-xm.dtsi
index cd7da2089b..983c446783 100644
--- a/target/linux/ath79/dts/ar7241_ubnt-xm.dtsi
+++ b/target/linux/ath79/dts/ar7241_ubnt-xm.dtsi
@@ -80,6 +80,7 @@
partition@0 {
label = "u-boot";
reg = <0x00 0x04>;
+ read-only;
};
partition@1 {
diff --git a/target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts
b/target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts
index 9589925eb5..42bcc6967e 100644
--- a/target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts
+++ b/target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts
@@ -97,6 +97,7 @@
partition@0 {
label = "u-boot";
reg = <0x00 0x02>;
+ read-only;
};
partition@1 {
--
2.17.0
--
Russell Senior, President
russ...@personaltelco.net
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] ath79: relicense DTS files to the GPL 2.0+ / MIT
On 07/05/18 11:31, Rafał Miłecki wrote: On 7 May 2018 at 10:46, Felix Fietkau wrote: On 2018-05-07 09:47, Rafał Miłecki wrote: From: Rafał Miłecki Some maintainers prefer DTS files licensed under permissive license like MIT / BSD. As all DT bindings should be OS independent and DTS files are pretty separated from Linux code it probably makes sense to share them across projects. The safest solution is to use dual licensing: that way it stays clear these files can be used in GPL projects without depending on current belief of licenses compatibility. Signed-off-by: Rafał Miłecki Some of these files are based on upstream GPL code, did you contact the original authors already? I wasn't aware of that. I assumed they are all John's work based on our quick IRC conversation: [09:08] blogic: are you author for target/linux/ath79/dts/*.dts files? [09:08] *of [09:14] rmilecki: yes [09:14] rmilecki: feel free to change the license text and push a fix ah sorry i forgot about that, let me fix it ... ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] ath79: relicense DTS files to the GPL 2.0+ / MIT
On 7 May 2018 at 10:46, Felix Fietkau wrote: > On 2018-05-07 09:47, Rafał Miłecki wrote: >> From: Rafał Miłecki >> >> Some maintainers prefer DTS files licensed under permissive license like >> MIT / BSD. As all DT bindings should be OS independent and DTS files are >> pretty separated from Linux code it probably makes sense to share them >> across projects. >> >> The safest solution is to use dual licensing: that way it stays clear >> these files can be used in GPL projects without depending on current >> belief of licenses compatibility. >> >> Signed-off-by: Rafał Miłecki > Some of these files are based on upstream GPL code, did you contact the > original authors already? I wasn't aware of that. I assumed they are all John's work based on our quick IRC conversation: [09:08] blogic: are you author for target/linux/ath79/dts/*.dts files? [09:08] *of [09:14] rmilecki: yes [09:14] rmilecki: feel free to change the license text and push a fix -- Rafał ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] ath79: relicense DTS files to the GPL 2.0+ / MIT
On 2018-05-07 09:47, Rafał Miłecki wrote: > From: Rafał Miłecki > > Some maintainers prefer DTS files licensed under permissive license like > MIT / BSD. As all DT bindings should be OS independent and DTS files are > pretty separated from Linux code it probably makes sense to share them > across projects. > > The safest solution is to use dual licensing: that way it stays clear > these files can be used in GPL projects without depending on current > belief of licenses compatibility. > > Signed-off-by: Rafał Miłecki Some of these files are based on upstream GPL code, did you contact the original authors already? - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] igmpproxy: bump to 0.2.1
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 --- > On 7 May 2018, at 09:34, John Crispin wrote: > > Hi Kevin, > > apparently you have a 10->11 patch in your tree that needs to be applied > prior to the 11->12 update > > John Oh :-( That means https://github.com/openwrt/openwrt/pull/828 still hasn’t been applied. Cheers, Kevin D-B 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A --- End Message --- ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ath79: use the new DT fixed partitions syntax
From: Rafał Miłecki
This new syntax is slightly better designed & uses "compatible" string.
For details see Documentation/devicetree/bindings/mtd/partition.txt .
Signed-off-by: Rafał Miłecki
---
target/linux/ath79/dts/ar7161_netgear_wndr3800.dts | 40 +++--
target/linux/ath79/dts/ar7241_ubnt-unifi.dts | 68 --
target/linux/ath79/dts/ar7241_ubnt-xm.dtsi | 68 --
target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts | 34 ++-
target/linux/ath79/dts/ar9330_gl_ar150.dts | 46 ---
target/linux/ath79/dts/ar9331_ew_dorin.dts | 46 ---
target/linux/ath79/dts/qca9558_om5p_ac.dts | 46 ---
7 files changed, 195 insertions(+), 153 deletions(-)
diff --git a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts
b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts
index ba6e9ae03c..a175fd7698 100644
--- a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts
+++ b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts
@@ -139,26 +139,32 @@
reg = <0>;
spi-max-frequency = <2500>;
- partition@0 {
- label = "u-boot";
- reg = <0x00 0x05>;
- read-only;
- };
+ partitions {
+ compatible = "fixed-partitions";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "u-boot";
+ reg = <0x00 0x05>;
+ read-only;
+ };
- partition@1 {
- label = "u-boot-env";
- reg = <0x05 0x02>;
- };
+ partition@1 {
+ label = "u-boot-env";
+ reg = <0x05 0x02>;
+ };
- partition@2 {
- label = "firmware";
- reg = <0x7 0xf8>;
- };
+ partition@2 {
+ label = "firmware";
+ reg = <0x7 0xf8>;
+ };
- partition@3 {
- label = "art";
- reg = <0xff 0x01>;
- read-only;
+ partition@3 {
+ label = "art";
+ reg = <0xff 0x01>;
+ read-only;
+ };
};
};
};
diff --git a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
index aaafb08424..1fa2d82db3 100644
--- a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
+++ b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts
@@ -68,37 +68,43 @@
reg = <0>;
spi-max-frequency = <2500>;
- partition@0 {
- label = "u-boot";
- reg = <0x00 0x04>;
- };
-
- partition@1 {
- label = "u-boot-env";
- reg = <0x04 0x01>;
- };
-
- partition@2 {
- label = "firmware";
- reg = <0x05 0x75>;
- };
-
- partition@3 {
- label = "board_config";
- reg = <0x7a 0x01>;
- read-only;
- };
-
- partition@4 {
- label = "cfg";
- reg = <0x7b 0x04>;
- read-only;
- };
-
- art: partition@5 {
- label = "art";
- reg = <0x7f 0x01>;
- read-only;
+ partitions {
+ compatible = "fixed-partitions";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "u-boot";
+ reg = <0x00 0x04>;
+ };
+
+ partition@1 {
+ label = "u-boot-env";
+ reg = <0x04 0x01>;
+ };
+
+ partition@2 {
+ label = "firmware";
+ reg = <0x05 0x75>;
+ };
+
+ partition@3 {
+ label = "board_config";
+ reg = <0x7a 0x01>;
+ read-only;
+ };
+
+
Re: [LEDE-DEV] [PATCH] igmpproxy: bump to 0.2.1
Hi Kevin, apparently you have a 10->11 patch in your tree that needs to be applied prior to the 11->12 update John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH V2] ath79: relicense DTS files to the GPL 2.0+ / MIT
On 07/05/18 10:10, Rafał Miłecki wrote: From: Rafał Miłecki Some maintainers prefer DTS files licensed under permissive license like MIT / BSD. As all DT bindings should be OS independent and DTS files are pretty separated from Linux code it probably makes sense to share them across projects. The safest solution is to use dual licensing: that way it stays clear these files can be used in GPL projects without depending on current belief of licenses compatibility. Signed-off-by: Rafał Miłecki Acked-by: John Crispin --- V2: Use the new "GPL-2.0-or-later" identifier --- target/linux/ath79/dts/ar7100.dtsi | 2 +- target/linux/ath79/dts/ar7161_netgear_wndr3800.dts | 2 +- target/linux/ath79/dts/ar7241.dtsi | 2 +- target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-nano-m.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-unifi.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dtsi | 2 +- target/linux/ath79/dts/ar7242.dtsi | 2 +- target/linux/ath79/dts/ar7242_buffalo_wzr-hp-g450h.dts | 2 +- target/linux/ath79/dts/ar724x.dtsi | 2 +- target/linux/ath79/dts/ar9132.dtsi | 2 +- target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts | 2 +- target/linux/ath79/dts/ar9330.dtsi | 2 +- target/linux/ath79/dts/ar9330_gl_ar150.dts | 2 +- target/linux/ath79/dts/ar9331.dtsi | 2 +- target/linux/ath79/dts/ar9331_dpt_module.dts | 2 +- target/linux/ath79/dts/ar9331_dragino_ms14.dts | 2 +- target/linux/ath79/dts/ar9331_ew_dorin.dts | 2 +- target/linux/ath79/dts/ar9331_omega.dts| 2 +- target/linux/ath79/dts/ar9331_tl_mr3020.dts| 2 +- target/linux/ath79/dts/ath79.dtsi | 2 +- target/linux/ath79/dts/qca9557.dtsi| 2 +- target/linux/ath79/dts/qca9558_om5p_ac.dts | 2 +- 25 files changed, 25 insertions(+), 25 deletions(-) diff --git a/target/linux/ath79/dts/ar7100.dtsi b/target/linux/ath79/dts/ar7100.dtsi index d4a973f505..9957b8df60 100644 --- a/target/linux/ath79/dts/ar7100.dtsi +++ b/target/linux/ath79/dts/ar7100.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT #include #include "ath79.dtsi" diff --git a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts index 60102b03ab..ba6e9ae03c 100644 --- a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts +++ b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241.dtsi b/target/linux/ath79/dts/ar7241.dtsi index f2efbe4358..91ebea54e0 100644 --- a/target/linux/ath79/dts/ar7241.dtsi +++ b/target/linux/ath79/dts/ar7241.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT #include "ar724x.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts index d14e2fdcb0..067c612516 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts index 91fbac039e..8fbd7a6eec 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts index ef2e407b87..e1ef6d7095 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts index c1829cb4f9..aaafb08424 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241_ubnt-xm.dts b/target
[LEDE-DEV] [PATCH V2] ath79: relicense DTS files to the GPL 2.0+ / MIT
From: Rafał Miłecki Some maintainers prefer DTS files licensed under permissive license like MIT / BSD. As all DT bindings should be OS independent and DTS files are pretty separated from Linux code it probably makes sense to share them across projects. The safest solution is to use dual licensing: that way it stays clear these files can be used in GPL projects without depending on current belief of licenses compatibility. Signed-off-by: Rafał Miłecki --- V2: Use the new "GPL-2.0-or-later" identifier --- target/linux/ath79/dts/ar7100.dtsi | 2 +- target/linux/ath79/dts/ar7161_netgear_wndr3800.dts | 2 +- target/linux/ath79/dts/ar7241.dtsi | 2 +- target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-nano-m.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-unifi.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dtsi | 2 +- target/linux/ath79/dts/ar7242.dtsi | 2 +- target/linux/ath79/dts/ar7242_buffalo_wzr-hp-g450h.dts | 2 +- target/linux/ath79/dts/ar724x.dtsi | 2 +- target/linux/ath79/dts/ar9132.dtsi | 2 +- target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts | 2 +- target/linux/ath79/dts/ar9330.dtsi | 2 +- target/linux/ath79/dts/ar9330_gl_ar150.dts | 2 +- target/linux/ath79/dts/ar9331.dtsi | 2 +- target/linux/ath79/dts/ar9331_dpt_module.dts | 2 +- target/linux/ath79/dts/ar9331_dragino_ms14.dts | 2 +- target/linux/ath79/dts/ar9331_ew_dorin.dts | 2 +- target/linux/ath79/dts/ar9331_omega.dts| 2 +- target/linux/ath79/dts/ar9331_tl_mr3020.dts| 2 +- target/linux/ath79/dts/ath79.dtsi | 2 +- target/linux/ath79/dts/qca9557.dtsi| 2 +- target/linux/ath79/dts/qca9558_om5p_ac.dts | 2 +- 25 files changed, 25 insertions(+), 25 deletions(-) diff --git a/target/linux/ath79/dts/ar7100.dtsi b/target/linux/ath79/dts/ar7100.dtsi index d4a973f505..9957b8df60 100644 --- a/target/linux/ath79/dts/ar7100.dtsi +++ b/target/linux/ath79/dts/ar7100.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT #include #include "ath79.dtsi" diff --git a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts index 60102b03ab..ba6e9ae03c 100644 --- a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts +++ b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241.dtsi b/target/linux/ath79/dts/ar7241.dtsi index f2efbe4358..91ebea54e0 100644 --- a/target/linux/ath79/dts/ar7241.dtsi +++ b/target/linux/ath79/dts/ar7241.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT #include "ar724x.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts index d14e2fdcb0..067c612516 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts index 91fbac039e..8fbd7a6eec 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts index ef2e407b87..e1ef6d7095 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts index c1829cb4f9..aaafb08424 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241_ubnt-xm.dts b/target/linux/ath79/dts/ar7241_ubnt-xm.dts index 3461c5b4c3..efb01f7b51 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-xm.dts ++
[LEDE-DEV] [PATCH] ath79: relicense DTS files to the GPL 2.0+ / MIT
From: Rafał Miłecki Some maintainers prefer DTS files licensed under permissive license like MIT / BSD. As all DT bindings should be OS independent and DTS files are pretty separated from Linux code it probably makes sense to share them across projects. The safest solution is to use dual licensing: that way it stays clear these files can be used in GPL projects without depending on current belief of licenses compatibility. Signed-off-by: Rafał Miłecki --- target/linux/ath79/dts/ar7100.dtsi | 2 +- target/linux/ath79/dts/ar7161_netgear_wndr3800.dts | 2 +- target/linux/ath79/dts/ar7241.dtsi | 2 +- target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-nano-m.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts| 2 +- target/linux/ath79/dts/ar7241_ubnt-unifi.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dts | 2 +- target/linux/ath79/dts/ar7241_ubnt-xm.dtsi | 2 +- target/linux/ath79/dts/ar7242.dtsi | 2 +- target/linux/ath79/dts/ar7242_buffalo_wzr-hp-g450h.dts | 2 +- target/linux/ath79/dts/ar724x.dtsi | 2 +- target/linux/ath79/dts/ar9132.dtsi | 2 +- target/linux/ath79/dts/ar9132_tl_wr1043nd_v1.dts | 2 +- target/linux/ath79/dts/ar9330.dtsi | 2 +- target/linux/ath79/dts/ar9330_gl_ar150.dts | 2 +- target/linux/ath79/dts/ar9331.dtsi | 2 +- target/linux/ath79/dts/ar9331_dpt_module.dts | 2 +- target/linux/ath79/dts/ar9331_dragino_ms14.dts | 2 +- target/linux/ath79/dts/ar9331_ew_dorin.dts | 2 +- target/linux/ath79/dts/ar9331_omega.dts| 2 +- target/linux/ath79/dts/ar9331_tl_mr3020.dts| 2 +- target/linux/ath79/dts/ath79.dtsi | 2 +- target/linux/ath79/dts/qca9557.dtsi| 2 +- target/linux/ath79/dts/qca9558_om5p_ac.dts | 2 +- 25 files changed, 25 insertions(+), 25 deletions(-) diff --git a/target/linux/ath79/dts/ar7100.dtsi b/target/linux/ath79/dts/ar7100.dtsi index d4a973f505..e652df5b4b 100644 --- a/target/linux/ath79/dts/ar7100.dtsi +++ b/target/linux/ath79/dts/ar7100.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT #include #include "ath79.dtsi" diff --git a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts index 60102b03ab..c195b541e8 100644 --- a/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts +++ b/target/linux/ath79/dts/ar7161_netgear_wndr3800.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241.dtsi b/target/linux/ath79/dts/ar7241.dtsi index f2efbe4358..09bcbece62 100644 --- a/target/linux/ath79/dts/ar7241.dtsi +++ b/target/linux/ath79/dts/ar7241.dtsi @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT #include "ar724x.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts index d14e2fdcb0..374a039a90 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-bullet-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts index 91fbac039e..84a7d06f03 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-nano-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts index ef2e407b87..4934353718 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-rocket-m.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT /dts-v1/; #include "ar7241_ubnt-xm.dtsi" diff --git a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts index c1829cb4f9..9ecbe42be9 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-unifi.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-unifi.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0+ OR MIT /dts-v1/; #include diff --git a/target/linux/ath79/dts/ar7241_ubnt-xm.dts b/target/linux/ath79/dts/ar7241_ubnt-xm.dts index 3461c5b4c3..72ddef33d4 100644 --- a/target/linux/ath79/dts/ar7241_ubnt-xm.dts +++ b/target/linux/ath79/dts/ar7241_ubnt-xm.dts @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: GPL-2.0 +// SPD
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
On 07/05/18 09:11, Jo-Philipp Wich wrote: Hi Joerg, John. I created an openwrt.org zone on Digital Ocean now so you could delegate the name servers to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com, maybe with one of the SPI machines thrown into the mix... ~ Jo Hi Joerg, We concluded as per vote on this ML that we would like to switch the DNS over to the machines Jow named above. Thanks alot for your help in getting this done ! John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org
Hi Joerg, John. I created an openwrt.org zone on Digital Ocean now so you could delegate the name servers to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com, maybe with one of the SPI machines thrown into the mix... ~ Jo signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
