Re: [OpenWrt-Devel] [PATCH] build: add mkrasimage
Hi On 2018-08-17, Christian Lamparter wrote: > On Thursday, August 16, 2018 12:31:38 PM CEST David Bauer wrote: > > On 8/16/18 3:12 AM, Karl Palsson wrote: [...] > [...] (And there is at least > one more device that can make use of ras: the NBG6817). Adding support for a factory image for the NBG6817 by using make-ras is on my radar, but as that router is in use as my main router with a rather complex vlan and 4addr setup, it might take a while until I find an opportunity to look into it. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020
On Sat, Aug 18, 2018 at 5:04 AM David Bauer wrote: > > Sysupgrading to ath79 from ar71xx currently fails because of mismatching > supported_devices. ar71xx is expecting "tl-mr3020" which is missing in > the ath79 image. Upgrading from ath79 is unaffected, as the image > contains the old string for ar71xx and the new one coming from the > device-tree. NAK from me. > > Signed-off-by: David Bauer > --- > target/linux/ath79/image/tiny-tp-link.mk | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/target/linux/ath79/image/tiny-tp-link.mk > b/target/linux/ath79/image/tiny-tp-link.mk > index 6ccc9d7dba..dadcd24b42 100644 > --- a/target/linux/ath79/image/tiny-tp-link.mk > +++ b/target/linux/ath79/image/tiny-tp-link.mk > @@ -17,7 +17,7 @@ define Device/tplink_tl-mr3020-v1 >DEVICE_TITLE := TP-LINK TL-MR3020 v1 >DEVICE_PACKAGES := kmod-usb-core kmod-usb-chipidea2 > kmod-usb-ledtrig-usbport >TPLINK_HWID := 0x3021 > - SUPPORTED_DEVICES += tl-mr3020-v1 > + SUPPORTED_DEVICES += tl-mr3020 > endef > TARGET_DEVICES += tplink_tl-mr3020-v1 > > -- > 2.18.0 > > > ___ > 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
Re: [OpenWrt-Devel] [PATCH] build: add mkrasimage
Hi Christian, I wrote the bash version because of issues in the past with C implementations of firmware packers for the Meraki routers (mkmerakifw.c and mkmerakifw-old.c). The issue there was that the main dev was coming from a sysadmin background and as with many OpenWrt users he had problems with C (endiannes!). As for what implementation is better. Why not let Karl Palsson (or any other commentor that wants to join ;) ) decide? I didn't want to start a race here, I was just more comfortable with finishing my C implementation as i have a problem with understanding such shell-scripts. From my understanding your linked script fixed the issues? I'm not sure why the script in OpenWRT is that old. IIRC i took it directly from your tree without further modifications. Note: The NBG6617 isn't the only device from ZyXEL that utilize the ras image. In fact, the "original" version of the notes above was written by Benjamin Berg and can still be found as a rather long comment in the NBG6616 image generation code under /target/linux/ar71xx/image/generic.mk [0]. (And there is at least one more device that can make use of ras: the NBG6817). So chances are, there that whatever "wins" will need to be updated to support those routers as well. Good point (didn't thought about that). At first glance the NBG6817 looks identical while the NBG6616 is missing the kernel-header part. I will see how i can support those two devices. There is also the NBG6716 around, but his one is using legacy build-code. So for this patch i see it as out-of-scope (although the header looks identical to the NBG6616). Best wishes David ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020
On 8/19/18 12:13 AM, Karl Palsson wrote: > These were removed as "it was intended to be required to force > when switching "architectures"" I disagreed then, but it got > railed through, so it's good to see I'm not the only one who > thought you should be able to upgrade from ar71xx to ath79 on the > same hardware> See also https://github.com/openwrt/openwrt/pull/1222 I understand the point of signaling people that things are most like going to break with the target-switch. I was expecting the compatible string to be there exactly for this reason as the compatible string for ath79 is automatically added from the device-tree. I'm not sure which approach is "better". On one hand, this makes upgrading via LuCI (with settings not preserved) not possible. I would expect people to read release nodes and follow the path accordingly, on the other hand you could argue one who is reading release notes is also capable of upgrading via CLI/SSH. Middle ground would be (in my opinion) to allow forced sysupgrade via LuCI, but I'm not sure how much effort this would be. Best wishes David ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020
David Bauer wrote: > Sysupgrading to ath79 from ar71xx currently fails because of > mismatching supported_devices. ar71xx is expecting "tl-mr3020" > which is missing in the ath79 image. Upgrading from ath79 is > unaffected, as the image contains the old string for ar71xx and > the new one coming from the device-tree. These were removed as "it was intended to be required to force when switching "architectures"" I disagreed then, but it got railed through, so it's good to see I'm not the only one who thought you should be able to upgrade from ar71xx to ath79 on the same hardware See also https://github.com/openwrt/openwrt/pull/1222 Cheers, Karl P > > Signed-off-by: David Bauer > --- > target/linux/ath79/image/tiny-tp-link.mk | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/target/linux/ath79/image/tiny-tp-link.mk > b/target/linux/ath79/image/tiny-tp-link.mk index > 6ccc9d7dba..dadcd24b42 100644 > --- a/target/linux/ath79/image/tiny-tp-link.mk > +++ b/target/linux/ath79/image/tiny-tp-link.mk > @@ -17,7 +17,7 @@ define Device/tplink_tl-mr3020-v1 >DEVICE_TITLE := TP-LINK TL-MR3020 v1 >DEVICE_PACKAGES := kmod-usb-core kmod-usb-chipidea2 > kmod-usb-ledtrig-usbport >TPLINK_HWID := 0x3021 > - SUPPORTED_DEVICES += tl-mr3020-v1 > + SUPPORTED_DEVICES += tl-mr3020 > endef > TARGET_DEVICES += tplink_tl-mr3020-v1 > > -- > 2.18.0 > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel signature.html Description: OpenPGP Digital Signature ___ 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 Fritz!Box 4020
This commit adds support for the AVM Fritz!Box 4020 WiFi-router. SoC: Qualcomm Atheros QCA9561 (Dragonfly) 750MHz RAM: Winbond W971GG6KB-25 FLASH: Macronix MX25L12835F WiFi: QCA9561 b/g/n 3x3 450Mbit/s USB: 1x USB 2.0 IN:WPS button, WiFi button OUT: Power LED green, Internet LED green, WLAN LED green, LAN LED green, INFO LED green, INFO LED red UART: Header Next to Black metal shield Pinout is 3.3V - RX - TX - GND (Square Pad is 3.3V) The Serial setting is 115200-8-N-1. Tested and working: - Ethernet (LAN + WAN) - WiFi (correct MAC) - Installation via EVA bootloader - OpenWRT sysupgrade - Buttons - LEDs Not working: - USB port A few words about the shift-register: AVM used a trick to control the shift-register for the LEDs with only 2 pins, SERCLK and MOSI. Q7S, normally used for daisy-chaining multiple shift-registers, pulls the latch, moving the shift register-state to the storage register. It also pulls down MR (normally pulled up) to clear the storage register, so the latch gets released and will not be pulled by the remaining bits in the shift-register. Shift register is all-zero after this. For that we need to make sure output 7 is set to high on driver probe. We accomplish this by using gpio-hogging. Installation via EVA: In the first seconds after Power is connected, the bootloader will listen for FTP connections on 169.254.157.1 (Might also be 192.168.178.1). Firmware can be uploaded like following: ftp> quote USER adam2 ftp> quote PASS adam2 ftp> binary ftp> debug ftp> passive ftp> quote MEDIA FLSH ftp> put openwrt-sysupgrade.bin mtd1 Note that this procedure might take up to two minutes. After transfer is complete you need to powercycle the device to boot OpenWRT. Signed-off-by: David Bauer --- v3 changes: - Rebased onto master - Add GPIO-hog to device-tree - Add SR description to commit message - Removed initvals kernel-patch .../ath79/base-files/etc/board.d/01_leds | 4 + .../ath79/base-files/etc/board.d/02_network | 5 + .../etc/hotplug.d/firmware/10-ath9k-eeprom| 3 + .../linux/ath79/dts/qca9561_avm_fritz4020.dts | 180 ++ target/linux/ath79/image/generic.mk | 14 ++ 5 files changed, 206 insertions(+) create mode 100644 target/linux/ath79/dts/qca9561_avm_fritz4020.dts diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds b/target/linux/ath79/base-files/etc/board.d/01_leds index 73f350cae2..9d63254a67 100755 --- a/target/linux/ath79/base-files/etc/board.d/01_leds +++ b/target/linux/ath79/base-files/etc/board.d/01_leds @@ -17,6 +17,10 @@ avm,fritz300e) ucidef_set_led_rssi "rssimediumhigh" "RSSIMEDIUMHIGH" "$boardname:green:rssi3" "wlan0" "60" "100" ucidef_set_led_rssi "rssihigh" "RSSIHIGH" "$boardname:green:rssi4" "wlan0" "80" "100" ;; +avm,fritz4020) + ucidef_set_led_netdev "wan" "WAN" "$boardname:green:wan" "eth0" + ucidef_set_led_switch "lan" "LAN" "$boardname:green:lan" "switch0" "0x1E" + ;; buffalo,whr-g301n) ucidef_set_led_netdev "wan" "WAN" "$boardname:green:wan" "eth0" ucidef_set_led_switch "lan1" "LAN1" "$boardname:green:lan1" "switch0" "0x02" 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 603251954b..1854583418 100755 --- a/target/linux/ath79/base-files/etc/board.d/02_network +++ b/target/linux/ath79/base-files/etc/board.d/02_network @@ -44,6 +44,7 @@ ath79_setup_interfaces() etactica,eg200) ucidef_set_interface_lan "eth0" "dhcp" ;; + avm,fritz4020|\ glinet,ar150|\ glinet,ar300m) ucidef_set_interfaces_lan_wan "eth1" "eth0" @@ -155,6 +156,10 @@ ath79_setup_macs() avm,fritz300e) lan_mac=$(fritz_tffs -n maca -i $(find_mtd_part "tffs (1)")) ;; + avm,fritz4020) + lan_mac=$(fritz_tffs -n maca -i $(find_mtd_part "tffs (1)")) + wan_mac=$(fritz_tffs -n macb -i $(find_mtd_part "tffs (1)")) + ;; dlink,dir-825-b1) lan_mac=$(mtd_get_mac_text "caldata" 65440) wan_mac=$(mtd_get_mac_text "caldata" 65460) diff --git a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom index f668a82fa2..9cbce4cecd 100644 --- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom +++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom @@ -97,6 +97,9 @@ board=$(board_name) case "$FIRMWARE" in "ath9k-eeprom-ahb-1810.wmac.bin") case $board in + avm,fritz4020) + ath9k_eeprom_extract_reverse "urlader" 5441 1088 + ;; iodata,wn-ac1167dgr|\ iodata,wn-ac1600dgr2) ath9k_eeprom_extract "art" 4096 1088 diff --git
[OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020
Sysupgrading to ath79 from ar71xx currently fails because of mismatching supported_devices. ar71xx is expecting "tl-mr3020" which is missing in the ath79 image. Upgrading from ath79 is unaffected, as the image contains the old string for ar71xx and the new one coming from the device-tree. Signed-off-by: David Bauer --- target/linux/ath79/image/tiny-tp-link.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ath79/image/tiny-tp-link.mk b/target/linux/ath79/image/tiny-tp-link.mk index 6ccc9d7dba..dadcd24b42 100644 --- a/target/linux/ath79/image/tiny-tp-link.mk +++ b/target/linux/ath79/image/tiny-tp-link.mk @@ -17,7 +17,7 @@ define Device/tplink_tl-mr3020-v1 DEVICE_TITLE := TP-LINK TL-MR3020 v1 DEVICE_PACKAGES := kmod-usb-core kmod-usb-chipidea2 kmod-usb-ledtrig-usbport TPLINK_HWID := 0x3021 - SUPPORTED_DEVICES += tl-mr3020-v1 + SUPPORTED_DEVICES += tl-mr3020 endef TARGET_DEVICES += tplink_tl-mr3020-v1 -- 2.18.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenWrt 18.06.1 service release
The OpenWrt Community is proud to announce the first service release of stable OpenWrt 18.06 series, which marks the first major version after the remerger of the LEDE and OpenWrt projects. OpenWrt 18.06.1 incorporates a number of mostly security oriented fixes backported from the development branch during the last two weeks. --- Some selected highlights of the service release are: * Linux kernel updated to versions 4.9.120/4.14.63 (from 4.9.111/4.14.52 in v18.06.0) * Security fixes for Curl, Mbedtls, OpenSSL and the Linux kernel * Binary builds for the at91 and ath25 targets * Updated mwlwifi driver * Improved input validation for rpcd uci ubus calls * Crash fixes in libuci * Assorted bug fixes in netifd For a detailed list of changes since 18.06.0 refer to https://openwrt.org/releases/18.06/changelog-18.06.1 --- For latest information about the 18.06 series, refer to the wiki at: https://openwrt.org/releases/18.06/ To download the v18.06.1 images, navigate to: https://downloads.openwrt.org/releases/18.06.1/ Have fun! The OpenWrt Community ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
