staging/lynxis, branch master

WIP: rework image builder code for x86

2019-08-05T12:02:38Z

tools/mktplinkfw2: show exact exceed bytes when the image is to big

2019-08-05T12:01:59Z

When an image is too big it's useful to show how many bytes the image is to big. Signed-off-by: Alexander Couzens

tools/mktplinkfw2: add support to pack bootloader

2019-08-05T12:01:59Z

The 841v13 and 841v14 can not flash any image without bootloader over the WebUI due a bug in the oem firmware upgrade software. Allow mktplinkfw2 to integrate bootloaders. An image with the bootloader looks: |------------| |image header| |------------| |bootloader | |------------| |optional pad| |------------| |image header| |------------| |kernel image| |------------| |rootfs image| |------------| The padding depends on the bootloader size. The 2nd image header must start on a 64k boundary. Signed-off-by: Alexander Couzens

tools/mktplinkfw2: add support to extract bootloader images

2019-08-05T12:01:59Z

tplinkfw2 images from TP-Link contains a bootloader image in most cases. -x will create a -bootloader.bin file. Signed-off-by: Alexander Couzens

ath79: add support for D-Link DIR-842 C1

2019-08-05T08:54:11Z

Hardware spec of DIR-842 C1: SoC: QCA9563 DRAM: 128MB DDR2 Flash: 16MB SPI-NOR Switch: QCA8337N WiFi 5.8GHz: QCA9888 WiFi 2.4Ghz: QCA9563 USB: circuit onboard, but components are not soldered Flash instructions: 1. Upgrade the factory.bin through the factory web interface or the u-boot failsafe interface. The firmware will boot up correctly for the first time. Do not power off the device after OpenWrt has booted. Otherwise the u-boot will enter failsafe mode as the checksum of the firmware has been changed. 2. Upgrade the sysupgrade.bin in OpenWrt. After upgrading completes the u-boot won't complain about the firmware checksum and it's OK to use now. 3. If you powered off the device before upgrading the sysupgrade.bin, just upgrade the factory.bin through the u-boot failsafe interface and then goto step 2. Signed-off-by: Jackson Lim [fix whitespace issues] Signed-off-by: David Bauer

ath79: add SUPPORTED_DEVICES for TP-Link TL-WR841N/ND v9 to v12

2019-08-05T08:54:11Z

In ar71xx, v10 and v12 did not have separate board_name. Signed-off-by: Adrian Schmutzler

ath79: add support for TP-Link TL-WR841N/ND v12

2019-08-05T08:54:11Z

This router has the same hardware as TP-LINK TL-WR841N/ND v11 (same FCC ID, same TFTP image name...). Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to wr841nv11_tp_recovery.bin (it's really v11, not v12) 3. Start a tftp server with the image file in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Adrian Schmutzler

ath79: add support for TP-Link TL-WR841N/ND v10

2019-08-05T08:54:11Z

The TL-WR841N/ND v10 is mostly identical to the v9. Apart from some minor changes, it contains a newer revision of the QCA9533 SoC and the CPU clock is significantly higher. Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to wr841nv10_tp_recovery.bin 3. Start a tftp server with the image file in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Adrian Schmutzler

ipset: update to 7.3

2019-08-05T07:42:09Z

Signed-off-by: DENG Qingfang

ar71xx: wpj531: fix SIG1/RSS1 LED GPIO

2019-08-04T20:37:15Z

In commit 6c937df749c7 ("ar71xx: wpj531: fix GPIOs for LED") wrong GPIO 13 for SIG1/RSS1 LED was commited, the correct GPIO number for this LED is 12. It's listed in "Hardware Guide - wpj531 7A06 (02/07/2019)" as GPIO12/RSS1 on the LED header and same GPIO 12 is used in the vendor's SDK as well. Fixes: 6c937df749c7 ("ar71xx: wpj531: fix GPIOs for LED") Signed-off-by: Leon M. George [commit subject/message facelift] Signed-off-by: Petr Štetiar