Re: [OpenWrt-Devel] Firewall settings must be manually changed for 6to4
On Sun, Dec 30, 2018 at 4:40 AM Jo-Philipp Wich wrote: > > Hi, > > > I recently set up an OpenWrt 18.06.1 router at a place where the ISP > > does not provide native IPv6, but does provide their own 6to4 > > tunnelling server. I installed 6to4 and ip-full on the router and > > configured WAN6, but was puzzled as to why IPv6 wasn't working until I > > discovered that the default firewall settings block forwarded traffic. > > Changing "Forward" from "reject" to "accept" under "General Settings" > > resolved the problem. > > This is a huge security issue, you should not do that, ever. > You likely need both an ingress rule allowing protocol 41 traffic and > join the wan6 interface to the existing wan zone. I didn't see an option in LuCI to allow protocol 41 traffic. How do I set that up? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] abc7ed2c ath79: add support for D-Link DIR-859 A1
Is there any reason this would should fail or brick a 859L A3? On the D-Link site they don't separate A1 or A3 so I should be fine? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCHv2] uclibc++: Add upstream patches fixing several bugs
This allows some packages like crtmpserver to compile with uClibc++.
Only patches that fix bugs were added. Upstream added a bunch of build
changes that I kept out to keep things simple.
Upstreamed patches start at 100.
Patches sent to upstream start at 200.
Signed-off-by: Rosen Penev
---
Added a patch that was sent to upstream that fixes
compilation for gptfdisk.
package/libs/uclibc++/Makefile| 2 +-
.../libs/uclibc++/patches/006-eabi_fix.patch | 20 -
.../uclibc++/patches/020-template-fix.patch | 22 -
.../patches/030-memory_corruption_fix.patch | 114 ---
.../uclibc++/patches/040-delete-c++14.patch | 20 -
...-erase-on-derived-__base_associative.patch | 40 -
...00-unwind-Fix-ARM-EABI-build-failure.patch | 71 ++
...initions-avoid-redefinition-warnings.patch | 32 +
.../patches/102-string-Silence-warning.patch | 29 +
...-add-missing-operator-implementation.patch | 36 +
...m-fix-string-getline-to-set-noskipws.patch | 30 +
...o-gets-was-removed-from-C11-LWG-2249.patch | 27 +
.../patches/106-C-14-sized-allocation.patch | 105 +++
...stream-ostream-Fix-building-with-g-5.patch | 48 +
.../108-string-assign-fix-two-bugs.patch | 131 +++
...09-algorithm-Fix-decl-of-stable_sort.patch | 109 +++
.../110-add-refcounted-exceptions.patch | 158
...plice-to-empty-list-from-other.begin.patch | 84 ++
.../112-cstdio-conditionalize-tmpnam.patch| 41 +
...amic-exception-specification-depreca.patch | 831 ++
.../patches/114-silence-some-warnings.patch | 109 +++
...-erase-on-derived-__base_associative.patch | 91 ++
...it-integer-support-for-32-bit-system.patch | 171
23 files changed, 2104 insertions(+), 217 deletions(-)
delete mode 100644 package/libs/uclibc++/patches/020-template-fix.patch
delete mode 100644
package/libs/uclibc++/patches/030-memory_corruption_fix.patch
delete mode 100644 package/libs/uclibc++/patches/040-delete-c++14.patch
delete mode 100644
package/libs/uclibc++/patches/050-Bugfix-erase-on-derived-__base_associative.patch
create mode 100644
package/libs/uclibc++/patches/100-unwind-Fix-ARM-EABI-build-failure.patch
create mode 100644
package/libs/uclibc++/patches/101-basic_definitions-avoid-redefinition-warnings.patch
create mode 100644
package/libs/uclibc++/patches/102-string-Silence-warning.patch
create mode 100644
package/libs/uclibc++/patches/103-istream-add-missing-operator-implementation.patch
create mode 100644
package/libs/uclibc++/patches/104-iostream-fix-string-getline-to-set-noskipws.patch
create mode 100644
package/libs/uclibc++/patches/105-cstdio-gets-was-removed-from-C11-LWG-2249.patch
create mode 100644
package/libs/uclibc++/patches/106-C-14-sized-allocation.patch
create mode 100644
package/libs/uclibc++/patches/107-istream-ostream-Fix-building-with-g-5.patch
create mode 100644
package/libs/uclibc++/patches/108-string-assign-fix-two-bugs.patch
create mode 100644
package/libs/uclibc++/patches/109-algorithm-Fix-decl-of-stable_sort.patch
create mode 100644
package/libs/uclibc++/patches/110-add-refcounted-exceptions.patch
create mode 100644
package/libs/uclibc++/patches/111-list-fix-splice-to-empty-list-from-other.begin.patch
create mode 100644
package/libs/uclibc++/patches/112-cstdio-conditionalize-tmpnam.patch
create mode 100644
package/libs/uclibc++/patches/113-silence-c-11-dynamic-exception-specification-depreca.patch
create mode 100644
package/libs/uclibc++/patches/114-silence-some-warnings.patch
create mode 100644
package/libs/uclibc++/patches/115-Fix-erase-on-derived-__base_associative.patch
create mode 100644
package/libs/uclibc++/patches/200-istream-Add-64-bit-integer-support-for-32-bit-system.patch
diff --git a/package/libs/uclibc++/Makefile b/package/libs/uclibc++/Makefile
index 7133a7ef33..cdd64591e4 100644
--- a/package/libs/uclibc++/Makefile
+++ b/package/libs/uclibc++/Makefile
@@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=uclibc++
PKG_VERSION:=0.2.4
-PKG_RELEASE:=3
+PKG_RELEASE:=4
PKG_SOURCE:=uClibc++-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=http://cxx.uclibc.org/src/
diff --git a/package/libs/uclibc++/patches/006-eabi_fix.patch
b/package/libs/uclibc++/patches/006-eabi_fix.patch
index 893c2d60b6..4f8e57c5c5 100644
--- a/package/libs/uclibc++/patches/006-eabi_fix.patch
+++ b/package/libs/uclibc++/patches/006-eabi_fix.patch
@@ -16,23 +16,3 @@
namespace std
{
a/include/unwind-cxx.h
-+++ b/include/unwind-cxx.h
-@@ -173,6 +173,7 @@ extern std::unexpected_handler __unexpec
-
- // This is the exception class we report -- "GNUCC++\0".
- const _Unwind_Exception_Class __gxx_exception_class
-+#ifndef __ARM_EABI_UNWINDER__
- = _Unwind_Exception_Class) 'G'
-<< 8 | (_Unwind_Exception_Class) 'N')
- << 8 | (_Unwind_Exception_Class) 'U')
-@@ -181,6 +182,9 @@ const _Unwind_Exception_Class __gxx_exce
- << 8 | (_Unwind_Exception_Class) '+')
- << 8 | (_Unwind_Exception_Class) '+')
-<< 8 | (_Unwind
[OpenWrt-Devel] [PATCH] ath79: use caldata patching for Archer C58/C59
With this commit the TP-Link Archer C58 and Archer C59 use caldata
patching in order to set the correct 5GHz MAC-address.
Tested on TP-Link Archer C59 v1.
For more details see commit 330965b.
Signed-off-by: David Bauer
---
.../ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata | 1 +
.../ath79/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac | 4
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index b9a987d418..9469602f77 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -152,6 +152,7 @@ case "$FIRMWARE" in
tplink,archer-c58-v1|\
tplink,archer-c59-v1)
ath10kcal_extract "art" 20480 12064
+ ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary mac
8) -1)
ln -sf /lib/firmware/ath10k/pre-cal-pci-\:00\:00.0.bin \
/lib/firmware/ath10k/QCA9888/hw2.0/board.bin
;;
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
index bb55b1c11c..14d4f6b9d6 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
+++ b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
@@ -24,10 +24,6 @@ case "$board" in
[ "$PHYNBR" -eq 1 ] && \
echo $(k2t_get_mac "lan_mac") >
/sys${DEVPATH}/macaddress
;;
- tplink,archer-c58-v1|\
- tplink,archer-c59-v1)
- echo $(macaddr_add $(mtd_get_mac_binary mac 8) $(($PHYNBR -
1)) ) > /sys${DEVPATH}/macaddress
- ;;
*)
;;
esac
--
2.20.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firewall settings must be manually changed for 6to4
On Sun, Dec 30, 2018 at 1:38 PM Torbjorn Jansson wrote: > > On 2018-12-30 12:40, Jo-Philipp Wich wrote: > > Hi, > > > >> I recently set up an OpenWrt 18.06.1 router at a place where the ISP > >> does not provide native IPv6, but does provide their own 6to4 > >> tunnelling server. I installed 6to4 and ip-full on the router and > >> configured WAN6, but was puzzled as to why IPv6 wasn't working until I > >> discovered that the default firewall settings block forwarded traffic. > >> Changing "Forward" from "reject" to "accept" under "General Settings" > >> resolved the problem. > > > > This is a huge security issue, you should not do that, ever. > > You likely need both an ingress rule allowing protocol 41 traffic and > > join the wan6 interface to the existing wan zone. > > > > ~ Jo > > > > > your correct. > > this discussion made me wonder something related to 6rd. > assuming you have an isp that provides 6rd settings via dhcpv4 options openwrt > auto creates a 6rd interface for you, what firewall zone do this interface end > up in by default? > i assume it ends up in same zone as its associated ipv4 interface right? so > likely wan. > > reason for asking is that when looking at what interfaces is in what zone this > auto created interface is not listed. In case of an auto created 6rd interface the interface will end up by default in the zone of the associated ipv4 interface. This can be overruled by specifying the zone6rd uci parameter in the associated ipv4 network config Hans > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v3] ath79: add support for GL.iNet GL-AR750S
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 --- Changes since v2: - removed usbpower led node - removed blank lines - add microsd hint to commit message --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
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 ---
This patch adds supports for GL-AR750S.
Right now this patch adds nor image generation only.
NAND image generation is not supportet at the moment.
Furtheremore the MicroSD port is not implemented as of now.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x switch button, 1x reset button
- LED: 3x LEDS (green)
- Another LED can be accessed on GPIO 7 if soldered
Flash instruction:
- Set static ip to 192.168.1.2
- Unplug the power cord
- Hold reset button
- Plug power back in
- Right led will flash 5 times
- Release reset button
- Browse to 192.168.1.1
- Choose sysupgrade image in NOR-flash section
- Press "update nor firmware"
- After successful transfer unplug network cable before device restarts
Signed-off-by: Christoph Krapp
---
.../ath79/base-files/etc/board.d/02_network | 4 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 9 +-
.../linux/ath79/dts/qca9563_glinet_ar750s.dts | 153 ++
target/linux/ath79/image/generic.mk | 9 ++
4 files changed, 171 insertions(+), 4 deletions(-)
create mode 100644 target/linux/ath79/dts/qca9563_glinet_ar750s.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 004ab59573..b9a0f356bf 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -93,6 +93,10 @@ ath79_setup_interfaces()
glinet,gl-x750)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ glinet,ar750s)
+ ucidef_add_switch "switch0" \
+ "0@eth0" "2:lan:2" "3:lan:1" "1:wan"
+ ;;
nec,wg800hp)
ucidef_add_switch "switch0" \
"0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 53f57be824..2118d2b06b 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,11 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary art
0) -1)
;;
+ glinet,ar750s|\
+ tplink,re450-v2)
+ ath10kcal_extract "art" 20480 2116
+ ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
+ ;;
glinet,gl-x750)
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
@@ -122,10 +127,6 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) -1)
;;
- tplink,re450-v2)
- ath10kcal_extract "art" 20480 2116
- ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
- ;;
ubnt,unifiac-lite|\
ubnt,unifiac-mesh|\
ubnt,unifiac-mesh-pro|\
diff --git a/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
new file mode 100644
index 00..b46a75c4af
--- /dev/null
+++ b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
@@ -0,0 +1,153 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include
+#include
+
+#include "qca956x.dtsi"
+
+/ {
+ compatible = "glinet,ar750s", "qca,qca9563";
+ model = "GL.iNet GL-AR750S";
+
+ chosen {
+ bootargs = "console=ttyS0,115200n8";
+ };
+
+ aliases {
+ led-boot = &power;
+ led-failsafe = &power;
+ led-running = &power;
+ led-upgrade = &power;
+ };
+
+ keys {
+ compatible = "gpio-keys-polled";
+ poll-interval = <20>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&jtag_disable_pins>;
+
+ button0 {
+ label = "reset";
+ linux,code = ;
+ gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
+ };
+
+ button1 {
+ label = "button right";
+ linux,code = ;
+ gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
+ };
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
>There is nothing about upgrading U-Boot on the device from this e-mail topic. but there is about upgrading firmware via u-boot and according to the above linked kresin comment that procedure is unreliable On 30/12/2018, Mathias Kresin wrote: > 30/12/2018 15:15, Tom Psyborg: >> On 30/12/2018, Piotr Dymacz wrote: >>> Hi Tom, >>> >>> On 30.12.2018 15:03, Tom Psyborg wrote: >>> >>> [...] >>> >>> If it's possible to update from the stock firmware via a >>> webinterface, >>> it's fine. If not, the way via u-boot works as well. >>> >>> Mathias >>> >> >> Aren't you embarrassed being such a hypocrite liar? > > Prove your point or troll somewhere else. > > Mathias > No u-boot upgrade, remember? https://github.com/lede-project/source/pull/1246#issuecomment-320228337 >>> >>> u-boot upgrade != upgrade via u-boot. >>> >>> -- >>> Cheers, >>> Piotr >>> >> >> Hi >> >> No, there was no misunderstanding. For kresin u-boot upgrade doesn't >> lead to a working router even if one knows how to READ documentation >> that explains upgrade via u-boot. >> > Are you on a vendetta? > > The install instructions from this patch recommends to do the initial > OpenWrt installation via bootloader recovery. Nowhere a replacement of > the preinstalled bootloader is mentioned. > > My linked comment rather proves my point, as I asked to test the > provided instructions to do the initial OpenWrt installation via > bootloader commandline instead of using the stock webinterface hack > (which I asked to add to the wiki instead). > it proves exactly what i replied in this mail to pope2k > Anyway, thanks for the chat > Mathias > what chat? i do not use chatrooms, ever ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
30/12/2018 15:15, Tom Psyborg: On 30/12/2018, Piotr Dymacz wrote: Hi Tom, On 30.12.2018 15:03, Tom Psyborg wrote: [...] If it's possible to update from the stock firmware via a webinterface, it's fine. If not, the way via u-boot works as well. Mathias Aren't you embarrassed being such a hypocrite liar? Prove your point or troll somewhere else. Mathias No u-boot upgrade, remember? https://github.com/lede-project/source/pull/1246#issuecomment-320228337 u-boot upgrade != upgrade via u-boot. -- Cheers, Piotr Hi No, there was no misunderstanding. For kresin u-boot upgrade doesn't lead to a working router even if one knows how to READ documentation that explains upgrade via u-boot. Are you on a vendetta? The install instructions from this patch recommends to do the initial OpenWrt installation via bootloader recovery. Nowhere a replacement of the preinstalled bootloader is mentioned. My linked comment rather proves my point, as I asked to test the provided instructions to do the initial OpenWrt installation via bootloader commandline instead of using the stock webinterface hack (which I asked to add to the wiki instead). Anyway, thanks for the chat Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
Hi Tom, On 30.12.2018 15:15, Tom Psyborg wrote: On 30/12/2018, Piotr Dymacz wrote: Hi Tom, On 30.12.2018 15:03, Tom Psyborg wrote: [...] If it's possible to update from the stock firmware via a webinterface, it's fine. If not, the way via u-boot works as well. Mathias Aren't you embarrassed being such a hypocrite liar? Prove your point or troll somewhere else. Mathias No u-boot upgrade, remember? https://github.com/lede-project/source/pull/1246#issuecomment-320228337 u-boot upgrade != upgrade via u-boot. -- Cheers, Piotr Hi No, there was no misunderstanding. For kresin u-boot upgrade doesn't lead to a working router even if one knows how to READ documentation that explains upgrade via u-boot. Please stop insulting others, you are actively violating rule 12: [0]. If you have a problem with someone else opinion, discuss that using private channel, not a public mailing list. And next time read e-mails more carefully because you are simply wrong here. There is nothing about upgrading U-Boot on the device from this e-mail topic. [0] https://openwrt.org/rules -- Cheers, Piotr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
On 30/12/2018, Piotr Dymacz wrote: > Hi Tom, > > On 30.12.2018 15:03, Tom Psyborg wrote: > > [...] > > If it's possible to update from the stock firmware via a webinterface, > it's fine. If not, the way via u-boot works as well. > > Mathias > Aren't you embarrassed being such a hypocrite liar? >>> >>> Prove your point or troll somewhere else. >>> >>> Mathias >>> >> >> No u-boot upgrade, remember? >> https://github.com/lede-project/source/pull/1246#issuecomment-320228337 > > u-boot upgrade != upgrade via u-boot. > > -- > Cheers, > Piotr > Hi No, there was no misunderstanding. For kresin u-boot upgrade doesn't lead to a working router even if one knows how to READ documentation that explains upgrade via u-boot. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
Hi Tom, On 30.12.2018 15:03, Tom Psyborg wrote: [...] If it's possible to update from the stock firmware via a webinterface, it's fine. If not, the way via u-boot works as well. Mathias Aren't you embarrassed being such a hypocrite liar? Prove your point or troll somewhere else. Mathias No u-boot upgrade, remember? https://github.com/lede-project/source/pull/1246#issuecomment-320228337 u-boot upgrade != upgrade via u-boot. -- Cheers, Piotr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
On 30/12/2018, Mathias Kresin wrote: > 30/12/2018 14:51, Tom Psyborg: >> On 30/12/2018, Mathias Kresin wrote: >>> 30/12/2018 12:35, Tom Psyborg: On 30/12/2018, Christoph Krapp via openwrt-devel 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. > > -- Forwarded message -- > From: Christoph Krapp > To: openwrt-devel@lists.openwrt.org > Cc: > Bcc: > Date: Sun, 30 Dec 2018 10:53:54 +0100 > Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S > This patch adds supports for GL-AR750S. > > Specification: > - SOC: QCA9563 (775MHz) > - Flash: 16 MiB (W25Q128FVSG) > - RAM: 128 MiB DDR2 > - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN > - Wireless: 2.4GHz (bgn) and 5GHz (ac) > - USB: 1x USB 2.0 port > - Button: 1x switch button, 1x reset button > - LED: 3x LEDS (green) > > Flash instruction: > Upload image via uboot web recovery Hi upgrade procedure from GL firmware via webserver is required and missing in your changeset >>> >>> Nah, it isn't and wasn't ever a hard requirement. >>> >>> If it's possible to update from the stock firmware via a webinterface, >>> it's fine. If not, the way via u-boot works as well. >>> >>> Mathias >>> >> >> Aren't you embarrassed being such a hypocrite liar? > > Prove your point or troll somewhere else. > > Mathias > No u-boot upgrade, remember? https://github.com/lede-project/source/pull/1246#issuecomment-320228337 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] brcm63xx: VH4032N: fix the power led and the wlan button
- use the blue LED for power, since the red LED is already used by
CFE in emergency mode.
- use the correct code for the wlan button
Signed-off-by: Daniel Gonzalez Cabanelas
---
Changes in v2:
- the v1 patch was truncated, fixed
target/linux/brcm63xx/base-files/etc/diag.sh | 2 +-
target/linux/brcm63xx/dts/vh4032n.dts| 8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/target/linux/brcm63xx/base-files/etc/diag.sh
b/target/linux/brcm63xx/base-files/etc/diag.sh
index afb3478..34464ec 100644
--- a/target/linux/brcm63xx/base-files/etc/diag.sh
+++ b/target/linux/brcm63xx/base-files/etc/diag.sh
@@ -43,7 +43,7 @@ set_state() {
status_led="spw303v:green:power+adsl"
;;
vh4032n)
- status_led="VH4032N:red:power"
+ status_led="VH4032N:blue:power"
;;
vr-3025un)
status_led="VR-3025un:green:power"
diff --git a/target/linux/brcm63xx/dts/vh4032n.dts
b/target/linux/brcm63xx/dts/vh4032n.dts
index 6788026..fd5a182 100644
--- a/target/linux/brcm63xx/dts/vh4032n.dts
+++ b/target/linux/brcm63xx/dts/vh4032n.dts
@@ -26,10 +26,10 @@
debounce-interval = <60>;
};
- wps {
- label = "wps";
+ wlan {
+ label = "wlan";
gpios = <&pinctrl 35 1>;
- linux,code = ;
+ linux,code = ;
debounce-interval = <60>;
};
};
@@ -56,11 +56,11 @@
power_blue {
label = "VH4032N:blue:power";
gpios = <&pinctrl 22 0>;
+ default-state = "on";
};
power_red {
label = "VH4032N:red:power";
gpios = <&pinctrl 24 0>;
- default-state = "on";
};
voice_blue {
label = "VH4032N:blue:voice";
--
2.6.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
30/12/2018 14:51, Tom Psyborg: On 30/12/2018, Mathias Kresin wrote: 30/12/2018 12:35, Tom Psyborg: On 30/12/2018, Christoph Krapp via openwrt-devel 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. -- Forwarded message -- From: Christoph Krapp To: openwrt-devel@lists.openwrt.org Cc: Bcc: Date: Sun, 30 Dec 2018 10:53:54 +0100 Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S This patch adds supports for GL-AR750S. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR2 - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN - Wireless: 2.4GHz (bgn) and 5GHz (ac) - USB: 1x USB 2.0 port - Button: 1x switch button, 1x reset button - LED: 3x LEDS (green) Flash instruction: Upload image via uboot web recovery Hi upgrade procedure from GL firmware via webserver is required and missing in your changeset Nah, it isn't and wasn't ever a hard requirement. If it's possible to update from the stock firmware via a webinterface, it's fine. If not, the way via u-boot works as well. Mathias Aren't you embarrassed being such a hypocrite liar? Prove your point or troll somewhere else. Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
On 30/12/2018, Mathias Kresin wrote: > 30/12/2018 12:35, Tom Psyborg: >> On 30/12/2018, Christoph Krapp via openwrt-devel >> 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. >>> >>> -- Forwarded message -- >>> From: Christoph Krapp >>> To: openwrt-devel@lists.openwrt.org >>> Cc: >>> Bcc: >>> Date: Sun, 30 Dec 2018 10:53:54 +0100 >>> Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S >>> This patch adds supports for GL-AR750S. >>> >>> Specification: >>> - SOC: QCA9563 (775MHz) >>> - Flash: 16 MiB (W25Q128FVSG) >>> - RAM: 128 MiB DDR2 >>> - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN >>> - Wireless: 2.4GHz (bgn) and 5GHz (ac) >>> - USB: 1x USB 2.0 port >>> - Button: 1x switch button, 1x reset button >>> - LED: 3x LEDS (green) >>> >>> Flash instruction: >>> Upload image via uboot web recovery >> >> Hi >> >> upgrade procedure from GL firmware via webserver is required and >> missing in your changeset > > Nah, it isn't and wasn't ever a hard requirement. > > If it's possible to update from the stock firmware via a webinterface, > it's fine. If not, the way via u-boot works as well. > > Mathias > Aren't you embarrassed being such a hypocrite liar? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/8] kernel: add DT binding support to the fit parser
Hi Christian,
On 11.12.2018 02:10, Christian Lamparter wrote:
On Monday, December 10, 2018 10:28:22 PM CET John Crispin wrote:
On 10/12/2018 16:47, Piotr Dymacz wrote:
> Hi Christian,
>
> On 09.12.2018 16:34, Christian Lamparter wrote:
>> It allows specifying default and Netgear parsers directly in the DT.
>>
>> Signed-off-by: Christian Lamparter
>> ---
>> .../linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_fit.c | 6 ++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git
>> a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_fit.c
>> b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_fit.c
>> index f356adcd4e..b7e56fc083 100644
>> --- a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_fit.c
>> +++ b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_fit.c
>> @@ -120,9 +120,15 @@ mtdsplit_fit_parse(struct mtd_info *mtd,
>> return 2;
>> }
>> +static const struct of_device_id mtdsplit_fit_of_match_table[] = {
>> +{ .compatible = "openwrt,fit-firmware" },
>
> Shouldn't that be "denx,fit", same as in case of "denx,uimage"? AFAIK,
> FIT format also comes from U-Boot and it's not OpenWrt specific
> (please, correct me if I'm wrong here).
>
I didn't know that DENX is fine with calling this mtdsplit binding their own
creation, since their u-boot does not contain any bindings for this (yet?).
So I went for openwrt,fit-firmware because OpenWrt puts so much more than
just the FIT in that partition. The FIT, rootfs, optional padding and
rootfs_data(aligned JFFS2 marker) are concatenated together in that specific
order so the firmware can be flashed in one go.
On boot The u-boot only loads the first thing it finds at a specified
offset of the flash (Note: the FIT image does have support to store a
rootfs in it too! But from what I can tell, no official OpenWrt image
is using this feature). Only the kernel uses a combination of
mtdsplit_fit/uimage and mtdsplit_squashfs.c to create the dynamic mtd
partitions for the kernel, rootfs and rootfs_data.
And this is also true for the legacy uImage format. OpenWrt already uses
"denx,uimage" binding for mtd parser which does much more than just
finding and creating kernel partition based on the uImage header.
That said, I'm fine with calling it "denx,fit" and I hope DENX is as well :-D.
My suggestion was more about keeping consistency here. So if at some
point OpenWrt (or upstream) decides it should be "openwrt,xyz" I won't
complain. But I think we should at least be consistent with the naming -
so if "openwrt,fit" then also "openwrt,uimage".
PS. Sorry for the late reply, I know that changes are already in tree.
--
Cheers,
Piotr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
Hey,
I stumbled of some more stuff. Comments inline.
Am So., 30. Dez. 2018 um 13:27 Uhr schrieb Christoph Krapp via
openwrt-devel :
>
> 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.
>
>
> -- Forwarded message --
> From: Christoph Krapp
> To: openwrt-devel@lists.openwrt.org
> Cc:
> Bcc:
> Date: Sun, 30 Dec 2018 13:26:31 +0100
> Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S
> This patch adds supports for GL-AR750S.
> Right now this patch only adds nor image generation.
> NAND image generation is not supportet at the moment.
>
> Specification:
> - SOC: QCA9563 (775MHz)
> - Flash: 16 MiB (W25Q128FVSG)
> - RAM: 128 MiB DDR2
> - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
> - Wireless: 2.4GHz (bgn) and 5GHz (ac)
> - USB: 1x USB 2.0 port
> - Button: 1x switch button, 1x reset button
> - LED: 3x LEDS (green)
The gl.Inet webpage mentions a " TF Card Slot (128GB Max.) " as well.
Any idea if it works and how it might be connected?
>
> Flash instruction:
> - Set static ip to 192.168.1.2
> - Unplug the power cord
> - Hold reset button
> - Plug power back in
> - Right led will flash 5 times
> - Release reset button
> - Browse to 192.168.1.1
> - Choose sysupgrade image in NOR-flash section
> - Press "update nor firmware"
> - After successful transfer unplug network cable before device restarts
>
> Signed-off-by: Christoph Krapp
> ---
> .../ath79/base-files/etc/board.d/02_network | 4 +
> .../etc/hotplug.d/firmware/11-ath10k-caldata | 9 +-
> .../linux/ath79/dts/qca9563_glinet_ar750s.dts | 160 ++
> target/linux/ath79/image/generic.mk | 9 +
> 4 files changed, 178 insertions(+), 4 deletions(-)
> create mode 100644 target/linux/ath79/dts/qca9563_glinet_ar750s.dts
>
> diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
> b/target/linux/ath79/base-files/etc/board.d/02_network
> index 004ab59573..b9a0f356bf 100755
> --- a/target/linux/ath79/base-files/etc/board.d/02_network
> +++ b/target/linux/ath79/base-files/etc/board.d/02_network
> @@ -93,6 +93,10 @@ ath79_setup_interfaces()
> glinet,gl-x750)
> ucidef_set_interfaces_lan_wan "eth1" "eth0"
> ;;
> + glinet,ar750s)
> + ucidef_add_switch "switch0" \
> + "0@eth0" "2:lan:2" "3:lan:1" "1:wan"
> + ;;
> nec,wg800hp)
> ucidef_add_switch "switch0" \
> "0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
> diff --git
> a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
> b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
> index 53f57be824..2118d2b06b 100644
> --- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
> +++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
> @@ -92,6 +92,11 @@ case "$FIRMWARE" in
> ath10kcal_extract "art" 20480 2116
> ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary
> art 0) -1)
> ;;
> + glinet,ar750s|\
> + tplink,re450-v2)
> + ath10kcal_extract "art" 20480 2116
> + ath10kcal_patch_mac $(macaddr_add $(cat
> /sys/class/net/eth0/address) +1)
> + ;;
> glinet,gl-x750)
> ath10kcal_extract "art" 20480 2116
> ath10kcal_patch_mac $(macaddr_add $(cat
> /sys/class/net/eth0/address) +1)
> @@ -122,10 +127,6 @@ case "$FIRMWARE" in
> ath10kcal_extract "art" 20480 2116
> ath10kcal_patch_mac $(macaddr_add $(cat
> /sys/class/net/eth0/address) -1)
> ;;
> - tplink,re450-v2)
> - ath10kcal_extract "art" 20480 2116
> - ath10kcal_patch_mac $(macaddr_add $(cat
> /sys/class/net/eth0/address) +1)
> - ;;
> ubnt,unifiac-lite|\
> ubnt,unifiac-mesh|\
> ubnt,unifiac-mesh-pro|\
> diff --git a/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
> b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
> new file mode 100644
> index 00..eff7aafaf6
> --- /dev/null
> +++ b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
> @@ -0,0 +1,160 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
> +/dts-v1/;
> +
> +#include
> +#include
> +
> +#include "qca956x.dtsi"
> +
> +/ {
> + compatible = "glinet,ar750s", "qca,qca9563";
> + model = "GL.iNet GL-AR750S";
> +
> + chosen {
> + bootargs = "console=ttyS0,115200n8";
> + };
> +
> + aliases {
> + led-boot = &power;
> + led-failsafe = &power;
> + led-running = &power;
> + led-upgrade = &power;
> + };
> +
> + keys {
> + compatible = "gpio-keys-polled"
Re: [OpenWrt-Devel] Firewall settings must be manually changed for 6to4
On 2018-12-30 12:40, Jo-Philipp Wich wrote: Hi, I recently set up an OpenWrt 18.06.1 router at a place where the ISP does not provide native IPv6, but does provide their own 6to4 tunnelling server. I installed 6to4 and ip-full on the router and configured WAN6, but was puzzled as to why IPv6 wasn't working until I discovered that the default firewall settings block forwarded traffic. Changing "Forward" from "reject" to "accept" under "General Settings" resolved the problem. This is a huge security issue, you should not do that, ever. You likely need both an ingress rule allowing protocol 41 traffic and join the wan6 interface to the existing wan zone. ~ Jo your correct. this discussion made me wonder something related to 6rd. assuming you have an isp that provides 6rd settings via dhcpv4 options openwrt auto creates a 6rd interface for you, what firewall zone do this interface end up in by default? i assume it ends up in same zone as its associated ipv4 interface right? so likely wan. reason for asking is that when looking at what interfaces is in what zone this auto created interface is not listed. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
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 ---
This patch adds supports for GL-AR750S.
Right now this patch only adds nor image generation.
NAND image generation is not supportet at the moment.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x switch button, 1x reset button
- LED: 3x LEDS (green)
Flash instruction:
- Set static ip to 192.168.1.2
- Unplug the power cord
- Hold reset button
- Plug power back in
- Right led will flash 5 times
- Release reset button
- Browse to 192.168.1.1
- Choose sysupgrade image in NOR-flash section
- Press "update nor firmware"
- After successful transfer unplug network cable before device restarts
Signed-off-by: Christoph Krapp
---
.../ath79/base-files/etc/board.d/02_network | 4 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 9 +-
.../linux/ath79/dts/qca9563_glinet_ar750s.dts | 160 ++
target/linux/ath79/image/generic.mk | 9 +
4 files changed, 178 insertions(+), 4 deletions(-)
create mode 100644 target/linux/ath79/dts/qca9563_glinet_ar750s.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 004ab59573..b9a0f356bf 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -93,6 +93,10 @@ ath79_setup_interfaces()
glinet,gl-x750)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ glinet,ar750s)
+ ucidef_add_switch "switch0" \
+ "0@eth0" "2:lan:2" "3:lan:1" "1:wan"
+ ;;
nec,wg800hp)
ucidef_add_switch "switch0" \
"0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 53f57be824..2118d2b06b 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,11 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary art
0) -1)
;;
+ glinet,ar750s|\
+ tplink,re450-v2)
+ ath10kcal_extract "art" 20480 2116
+ ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
+ ;;
glinet,gl-x750)
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
@@ -122,10 +127,6 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) -1)
;;
- tplink,re450-v2)
- ath10kcal_extract "art" 20480 2116
- ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
- ;;
ubnt,unifiac-lite|\
ubnt,unifiac-mesh|\
ubnt,unifiac-mesh-pro|\
diff --git a/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
new file mode 100644
index 00..eff7aafaf6
--- /dev/null
+++ b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
@@ -0,0 +1,160 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include
+#include
+
+#include "qca956x.dtsi"
+
+/ {
+ compatible = "glinet,ar750s", "qca,qca9563";
+ model = "GL.iNet GL-AR750S";
+
+ chosen {
+ bootargs = "console=ttyS0,115200n8";
+ };
+
+ aliases {
+ led-boot = &power;
+ led-failsafe = &power;
+ led-running = &power;
+ led-upgrade = &power;
+ };
+
+ keys {
+ compatible = "gpio-keys-polled";
+ poll-interval = <20>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&jtag_disable_pins>;
+
+ button0 {
+ label = "reset";
+ linux,code = ;
+ gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
+ };
+
+ button1 {
+ label = "button right";
+ linux,code = ;
+ gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
+ };
+
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ power: power {
+ label = "gl-ar750s:green:power";
+ gp
[OpenWrt-Devel] [PATCH v2] ath79: add support for GL.iNet GL-AR750S
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 --- Changes since v1 (thx Mathias Kresin & Piotr Dymacz): - fixed whitespace issues - added detailed uboot web recovery instructions - fixed usbpower led node label - added alias for power led node - cleaned up DEVICE_PACKAGES - use default image generation logic --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
30/12/2018 12:35, Tom Psyborg: On 30/12/2018, Christoph Krapp via openwrt-devel 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. -- Forwarded message -- From: Christoph Krapp To: openwrt-devel@lists.openwrt.org Cc: Bcc: Date: Sun, 30 Dec 2018 10:53:54 +0100 Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S This patch adds supports for GL-AR750S. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR2 - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN - Wireless: 2.4GHz (bgn) and 5GHz (ac) - USB: 1x USB 2.0 port - Button: 1x switch button, 1x reset button - LED: 3x LEDS (green) Flash instruction: Upload image via uboot web recovery Hi upgrade procedure from GL firmware via webserver is required and missing in your changeset Nah, it isn't and wasn't ever a hard requirement. If it's possible to update from the stock firmware via a webinterface, it's fine. If not, the way via u-boot works as well. Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: Fix gpio-leds for P2812HNUF1 and TDW8980
While at it rename node name to the generic `leds`.
Signed-off-by: Petr Štetiar
---
target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts | 3 ++-
target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts| 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts
b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts
index 911a2d6..7626a54 100644
--- a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts
+++ b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts
@@ -11,7 +11,8 @@
led-usb2 = &led_usb2;
};
- gpio-leds {
+ leds {
+ compatible = "gpio-leds";
led_usb1: usb1 {
label = "p2812hnuf1:green:usb1";
gpios = <&gpio 38 GPIO_ACTIVE_LOW>;
diff --git a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts
b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts
index 76875e7..6d686a8 100644
--- a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts
+++ b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts
@@ -6,7 +6,8 @@
compatible = "tplink,tdw8980", "tplink,tdw89x0", "lantiq,xway",
"lantiq,vr9";
model = "TP-LINK TD-W8980";
- gpio-leds {
+ leds {
+ compatible = "gpio-leds";
wifi2 {
label = "tdw8980:green:wlan5ghz";
gpios = <&gpio 24 GPIO_ACTIVE_LOW>;
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firewall settings must be manually changed for 6to4
Hi, > I recently set up an OpenWrt 18.06.1 router at a place where the ISP > does not provide native IPv6, but does provide their own 6to4 > tunnelling server. I installed 6to4 and ip-full on the router and > configured WAN6, but was puzzled as to why IPv6 wasn't working until I > discovered that the default firewall settings block forwarded traffic. > Changing "Forward" from "reject" to "accept" under "General Settings" > resolved the problem. This is a huge security issue, you should not do that, ever. You likely need both an ingress rule allowing protocol 41 traffic and join the wan6 interface to the existing wan zone. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
On 30/12/2018, Christoph Krapp via openwrt-devel 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. > >-- Forwarded message -- >From: Christoph Krapp >To: openwrt-devel@lists.openwrt.org >Cc: >Bcc: >Date: Sun, 30 Dec 2018 10:53:54 +0100 >Subject: [PATCH] ath79: add support for GL.iNet GL-AR750S >This patch adds supports for GL-AR750S. > > Specification: > - SOC: QCA9563 (775MHz) > - Flash: 16 MiB (W25Q128FVSG) > - RAM: 128 MiB DDR2 > - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN > - Wireless: 2.4GHz (bgn) and 5GHz (ac) > - USB: 1x USB 2.0 port > - Button: 1x switch button, 1x reset button > - LED: 3x LEDS (green) > > Flash instruction: > Upload image via uboot web recovery Hi upgrade procedure from GL firmware via webserver is required and missing in your changeset ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] config: enable some useful features on !SMALL_FLASH devices
Daniel Golle [2018-12-29 06:51:32]: > config KERNEL_AIO > config KERNEL_FHANDLE > config KERNEL_FANOTIFY > + default y if !SMALL_FLASH What about `FEATURES += nas` to make it clear and don't abuse SMALL_FLASH. > config KERNEL_CGROUPS > config KERNEL_CPUSETS > config KERNEL_CGROUP_CPUACCT > config KERNEL_RESOURCE_COUNTERS > config KERNEL_MEMCG > config KERNEL_MEMCG_KMEM > menuconfig KERNEL_CGROUP_SCHED > config KERNEL_FAIR_GROUP_SCHED > config KERNEL_RT_GROUP_SCHED > config KERNEL_NAMESPACES > config KERNEL_LXC_MISC > config KERNEL_SECCOMP_FILTER > config KERNEL_SECCOMP > - default n > + default y if !SMALL_FLASH What about `FEATURES += containers` ? Daniel Engberg [2018-12-30 10:21:46]: > however KERNEL_CGROUPS, config KERNEL_NAMESPACES, config KERNEL_LXC_MISC, > KERNEL_SECCOMP_FILTER are very limited use cases to my knowledge and more or > less only used on x86*? There are other quite powerful platforms like mvebu, imx6, ipq etc. where you could use this as well. -- ynezz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
Hey Christoph,
find my comments inline.
Mathias
30/12/2018 10:53, Christoph Krapp:
This patch adds supports for GL-AR750S.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x switch button, 1x reset button
- LED: 3x LEDS (green)
Flash instruction:
Upload image via uboot web recovery
And how to get into the uboot web recovery mode?
Signed-off-by: Christoph Krapp
---
.../ath79/base-files/etc/board.d/02_network | 4 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 9 +-
.../linux/ath79/dts/qca9563_glinet_ar750s.dts | 153 ++
target/linux/ath79/image/generic.mk | 12 ++
4 files changed, 174 insertions(+), 4 deletions(-)
create mode 100644 target/linux/ath79/dts/qca9563_glinet_ar750s.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 004ab59573..b9a0f356bf 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -93,6 +93,10 @@ ath79_setup_interfaces()
glinet,gl-x750)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ glinet,ar750s)
+ ucidef_add_switch "switch0" \
+ "0@eth0" "2:lan:2" "3:lan:1" "1:wan"
+ ;;
nec,wg800hp)
ucidef_add_switch "switch0" \
"0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 53f57be824..2118d2b06b 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,11 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary art
0) -1)
;;
+ glinet,ar750s|\
+ tplink,re450-v2)
+ ath10kcal_extract "art" 20480 2116
+ ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
+ ;;
glinet,gl-x750)
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
@@ -122,10 +127,6 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) -1)
;;
- tplink,re450-v2)
- ath10kcal_extract "art" 20480 2116
- ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
- ;;
ubnt,unifiac-lite|\
ubnt,unifiac-mesh|\
ubnt,unifiac-mesh-pro|\
diff --git a/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
new file mode 100644
index 00..64b346ae9c
--- /dev/null
+++ b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
@@ -0,0 +1,153 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include
+#include
+
+#include "qca956x.dtsi"
+
+/ {
+ compatible = "glinet,ar750s", "qca,qca9563";
+ model = "GL.iNet GL-AR750S";
+
+ chosen {
+ bootargs = "console=ttyS0,115200n8";
+ };
You have a lot of spaces vs. tabs issues at least in the dts file.
Please make sure to use tabs everywhere.
+
+ keys {
+ compatible = "gpio-keys-polled";
+ poll-interval = <20>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&jtag_disable_pins>;
+
+ button0 {
+ label = "reset";
+ linux,code = ;
+ gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
+ };
+
+button1 {
+ label = "button right";
+ linux,code = ;
+ gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
+ };
+
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ power {
Please add an aliases node, to configure boot status indication via this
led. Have a look at the other dts files for examples.
+ label = "gl-ar750s:green:power";
+ gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
+ default-state = "keep";
+ };
+
+usbpower {
green:wan vs. usbpower. Either is wrong here.
+ label = "gl-ar750s:green:wan";
+ gpios = <&gpio 7 GPIO_ACTIVE_LOW>;
+ };
+
+ wlan2g {
+ label = "gl-ar750s:green:wlan2g";
+ gpios = <&gpio 19 GPIO_ACTIVE_LOW>;
+
Re: [OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
Hi Christoph, On 30.12.2018 10:54, Christoph Krapp via openwrt-devel wrote: This patch adds supports for GL-AR750S. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) This device comes with SPI NOR + NAND combination. You should at least mention that in your patch and let others know that your patch is incomplete and makes use of only part of the available flash storage. -- Cheers, Piotr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ath79: add support for GL.iNet GL-AR750S
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 ---
This patch adds supports for GL-AR750S.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x switch button, 1x reset button
- LED: 3x LEDS (green)
Flash instruction:
Upload image via uboot web recovery
Signed-off-by: Christoph Krapp
---
.../ath79/base-files/etc/board.d/02_network | 4 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 9 +-
.../linux/ath79/dts/qca9563_glinet_ar750s.dts | 153 ++
target/linux/ath79/image/generic.mk | 12 ++
4 files changed, 174 insertions(+), 4 deletions(-)
create mode 100644 target/linux/ath79/dts/qca9563_glinet_ar750s.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 004ab59573..b9a0f356bf 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -93,6 +93,10 @@ ath79_setup_interfaces()
glinet,gl-x750)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ glinet,ar750s)
+ ucidef_add_switch "switch0" \
+ "0@eth0" "2:lan:2" "3:lan:1" "1:wan"
+ ;;
nec,wg800hp)
ucidef_add_switch "switch0" \
"0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 53f57be824..2118d2b06b 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,11 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary art
0) -1)
;;
+ glinet,ar750s|\
+ tplink,re450-v2)
+ ath10kcal_extract "art" 20480 2116
+ ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
+ ;;
glinet,gl-x750)
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
@@ -122,10 +127,6 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) -1)
;;
- tplink,re450-v2)
- ath10kcal_extract "art" 20480 2116
- ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +1)
- ;;
ubnt,unifiac-lite|\
ubnt,unifiac-mesh|\
ubnt,unifiac-mesh-pro|\
diff --git a/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
new file mode 100644
index 00..64b346ae9c
--- /dev/null
+++ b/target/linux/ath79/dts/qca9563_glinet_ar750s.dts
@@ -0,0 +1,153 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include
+#include
+
+#include "qca956x.dtsi"
+
+/ {
+ compatible = "glinet,ar750s", "qca,qca9563";
+ model = "GL.iNet GL-AR750S";
+
+ chosen {
+ bootargs = "console=ttyS0,115200n8";
+ };
+
+ keys {
+ compatible = "gpio-keys-polled";
+ poll-interval = <20>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&jtag_disable_pins>;
+
+ button0 {
+ label = "reset";
+ linux,code = ;
+ gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
+ };
+
+button1 {
+ label = "button right";
+ linux,code = ;
+ gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
+ };
+
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ power {
+ label = "gl-ar750s:green:power";
+ gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
+ default-state = "keep";
+ };
+
+usbpower {
+ label = "gl-ar750s:green:wan";
+ gpios = <&gpio 7 GPIO_ACTIVE_LOW>;
+ };
+
+ wlan2g {
+ label = "gl-ar750s:green:wlan2g";
+ gpios = <&gpio 19 GPIO_ACTIVE_LOW>;
+ linux,default-trigger = "phy1tpt";
+ };
+
+ wlan5g {
+ label = "gl-ar750s:green:wlan5g";
+ gpios = <&gpio
Re: [OpenWrt-Devel] [PATCH] config: enable some useful features on !SMALL_FLASH devices
Hi, KERNEL_AIO, KERNEL_FHANDLE and KERNEL_FANOTIFY makes sense _if_ you're using some kind of storage device however KERNEL_CGROUPS, config KERNEL_NAMESPACES, config KERNEL_LXC_MISC, KERNEL_SECCOMP_FILTER are very limited use cases to my knowledge and more or less only used on x86*? Keep in mind that 8Mbyte flash devices falls under the non tiny category and you don't have much space to begin with and far from everyone uses external storage devices on such devices which requires the kernel features mentioned. Best regards, Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
