aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.19 to 4.19.105Koen Vandeputte2020-02-2419-47/+47
| | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2013-1798 - CVE-2019-3016 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.171Koen Vandeputte2020-02-2426-50/+50
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2013-1798 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kirkwood: tidy up hwmon_fancontrolSungbo Eo2020-02-241-17/+16
| | | | | | | | Add indent and sort board_name alphabetically. Sourcing /lib/functions.sh is already handled by /etc/rc.common. Drop the line. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* kirkwood: add kmod-hwmon-core to DEVICE_PACKAGESSungbo Eo2020-02-231-2/+4
| | | | | | | | | kmod-hwmon-lm* will not get into images unless kmod-hwmon-core is added to DEVICE_PACKAGES as well. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [only address kmod-hwmon-core in this commit] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: tidy up image MakefileSungbo Eo2020-02-231-4/+5
| | | | | | | - use k in SIZE variables - break long lines Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* kirkwood: fix device node name of Iomega ix2-200Sungbo Eo2020-02-231-2/+2
| | | | | | | | | | | | | | | The current device node name of ix2-200 is "iom_ix2_200", which results in a SUPPORTED_DEVICES string "iom,ix2,200" that does not match the compatible in DTS and the board name used in board.d. Fix this by replacing the second underscore with a dash, following vendor_model scheme. Fixes: 27b2f0fc0fc5 ("kirkwood: add support for Iomega Storcenter ix2-200") Signed-off-by: Sungbo Eo <mans0n@gorani.run> [commit title/message rephrase] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix TP-Link TL-WA901ND v2 PHY stuck in resetDavid Bauer2020-02-231-0/+6
| | | | | | | | | | Some newer bootloaders for the TP-Link TL-WA901ND put the ethernet PHY in reset before loading the kernel, thus the LAN interface is not working in OpenWrt. Clear the reset to restore ethernet functionality. Signed-off-by: David Bauer <mail@david-bauer.net>
* x86: avoid underscore in package nameSungbo Eo2020-02-231-3/+3
| | | | | | | As 07e1d88d7beb ("kernel: avoid underscore in *6lowpan package names") shows, underscores might cause build failures. Replace underscore with dash. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: move includes to DTSI for mt7628an_tplink_8m*Adrian Schmutzler2020-02-2213-33/+6
| | | | | | | | | | All devices inherited from mt7628an_tplink_8m.dtsi and mt7628an_tplink_8m-split-uboot.dtsi contain the same additional includes in the DTS files. Move them to the DTSI files instead. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: move compatible for Ubiquiti Edgerouter X to DTS fileAdrian Schmutzler2020-02-222-2/+1
| | | | | | | | | | | | So far, the compatible for the Ubiquiti Edgerouter X has been defined in the DTSI file and inherited for the edgerouterx.dts, but overwritten for the edgerouterx-sfp.dts. In contrast, the model was stored in the DTS file in both cases. To resolve this somewhat confusing situation, move the compatible with the device name for edgerouterx to the DTS file as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove redundant includes in DTS filesAdrian Schmutzler2020-02-227-15/+2
| | | | | | | | | | Many DTS files contain the same includes again that are already present in the DTSI files they are derived from. Remove those redundant includes in the DTS files. For vocore, the include is moved to the parent DTSI file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: remove redundant includes in DTS filesAdrian Schmutzler2020-02-2217-50/+0
| | | | | | | | | Many DTS files contain the same includes again that are already present in the DTSI files they are derived from. Remove those redundant includes in the DTS files. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix xt_connmark.hMartin Schiller2020-02-221-2/+2
| | | | | | | | | Commit a1cfe0dcbb24 (kernel: connmark set-dscpmark follow upstreamimg attempt") broke the usage of xt_connmark.h in user-space (e.g. strongswan), because the BIT() macro is unknown there. Fixes: a1cfe0dcbb24 (kernel: connmark set-dscpmark follow upstreamimg attempt") Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* generic: refresh patchesAleksander Jan Bajkowski2020-02-223-47/+8
| | | | | | | | just run: make target/linux/refresh V=s Fixes: 6e315de0f422acf66c3505a4ed8c095a0f5d3424 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: remove non-existant symbols from 4.19 configAleksander Jan Bajkowski2020-02-226-17/+0
| | | | | | These symbols only exist in kernel version <= 4.15 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* build: Add additional kernel debug optionsHauke Mehrtens2020-02-222-0/+10
| | | | | | | | Make it possible to activate some additional kernel debug options. This can be used to debug some problems in kernel drivers. Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* build: Add option KERNEL_KASANHauke Mehrtens2020-02-222-0/+2
| | | | | | | | The kernel kernel address sanitizer is able to detect some memory bugs in the kernel like out of range array accesses. Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* build: Add option KERNEL_UBSANHauke Mehrtens2020-02-222-0/+7
| | | | | | | | The kernel Undefined Behavior Sanitizer is able to detect some memory bugs in the kernel like out of range array accesses. Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* x86: Add missing kernel option CONFIG_X86_DECODER_SELFTESTHauke Mehrtens2020-02-222-0/+2
| | | | | | | | | This option has now a different dependency and can be activated, set a default value. Fixes: 20b5a4ca01ca ("kernel: bump 4.19 to 4.19.101") Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com> Tested-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* kirkwood: do not expose status LED to user config by defaultAdrian Schmutzler2020-02-221-23/+0
| | | | | | | | | | | | So far, the state of status LEDs is set up in 01_leds for many devices in kirkwood target. As those LEDs are also controlled by diag.sh, exposing them to the user via uci config by default seems not helpful and might even have confusing results for the user. Thus, remove the ucidef_set_led_default setup for power/status LED, but do not touch the rest where user control is actually a feature. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: set default state for status LEDs in device treeAdrian Schmutzler2020-02-2226-50/+78
| | | | | | | | | | This adds the default-state = "on"; statement for the power or primary status LED in DTS on kirkwood. This will ensure that this LED will be lit up very early in the boot process (i.e. before diag.sh is executed) and thus will provide an additional hint to the user when problems arise during early boot process. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: add diag LEDs for ZyXEL NSA325Adrian Schmutzler2020-02-222-0/+60
| | | | | | | This device has had no diag LEDs set up so far, so let's just add them. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: use generic diag.shPawel Dembicki2020-02-2225-113/+542
| | | | | | | | | | | | | | | | | | This commit removes the target-specific diag.sh script. This way, the generic one is used for the target, which uses DT-aliases to specify the LEDs used. Generic diag.sh allow to use different LEDs to indicate different states. Non-red status LEDs for indicating boot and a running system. Where possible, the red or orange LEDs are used to indicate failsafe mode and a running upgrade. Compile-tested: all target devices. Run-tested: CheckPoint L-50 Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [remove unrelated cosmetic changes, rename some labels, add pogo_e02] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Teltonika RUT955Daniel Golle2020-02-214-0/+397
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - 550/400/200 MHz (CPU/DDR/AHB) - 128 MB of RAM (DDR2) - 16 MB of FLASH (SPI NOR) - 4x 10/100 Mbps Ethernet, with passive PoE support on LAN1 - 2T2R 2,4 GHz (AR9344) - built-in 4G/3G module (example: Quectel EC-25EU) - internal microSD slot (spi-mmc, buggy and disabled for now) - RS232 on D-Sub9 port (Cypress ACM via USB, /dev/ttyACM0) - RS422/RS485 (AR934x high speed UART, /dev/ttyATH1) - analog 0-24V input (MCP3221) - various digital inputs and outputs incl. a relay - 11x LED (4 are driven by AR9344, 7 by 74HC595) - 2x miniSIM slot (can be swapped via GPIO) - 2x RP-SMA/F (Wi-Fi), 3x SMA/F (2x WWAN, GPS) - 1x button (reset) - DC jack for main power input (9-30 V) - debugging UART available on PCB edge connector Serial console (/dev/ttyS0) pinout: - RX: pin1 (square) on top side of the main PCB (AR9344 is on top) - TX: pin1 (square) on bottom side Flash instruction: Vendor firmware is based on OpenWrt CC release. Use the "factory" image directly in GUI (make sure to uncheck "keep settings") or in U-Boot web based recovery. To avoid any problems, make sure to first update vendor firmware to latest version - "factory" image was successfully tested on device running "RUT9XX_R_00.06.051" firmware and U-Boot "3.0.2". Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* serial: ar933x_uart: add rs485 supportDaniel Golle2020-02-211-0/+271
| | | | | | | | | Add support for RS485 tranceiver with transmit/receive switch hooked to a RTS GPIO pin. Use the 'rts-gpios' and 'rs485-rts-active-low' properties as described in devicetree/bindings/serial/rs485.yaml. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: add support for TP-Link TL-WA701ND/730RE/801ND/901ND v1Adrian Schmutzler2020-02-218-1/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the various clones of the TL-WA830RE recently supported in fb99ac6807f2 ("ath79: add support for TP-Link TL-WA830RE v1"): - tplink,tl-wa701nd-v1 - tplink,tl-wa730re-v1 - tplink,tl-wa801nd-v1 - tplink,tl-wa830re-v1 (already supported) - tplink,tl-wa901nd-v1 Since these devices are 100%-clones in ar71xx, this patch adds all of them without run-testing (as this has been done for TL-WA830RE v1). Specifications: - SOC: Atheros AR7240 - CPU: 400MHz - Flash: 4 MiB (Spansion S25FL032P) - RAM: 32 MiB (Zentel A3S56D40FTP-G5) - WLAN: Atheros AR9280 bgn 2x2 - Ethernet: 1 port (100M) Flash instructions: - install from u-boot with tftp (requires serial access) > setenv ipaddr a.b.c.d > setenv serverip e.f.g.h > tftpboot 0x80000000 \ openwrt-ath79-tiny-tplink_tl-waxxxxx-v1-squashfs-factory.bin > erase 0x9f020000 +0x3c0000 > cp.b 0x80000000 0x9f020000 0x3c0000 > bootm 0x9f020000 - flash factory image from OEM WebUI - sysupgrade from ar71xx image Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix HiWiFi HC5761A USB portDENG Qingfang2020-02-211-1/+12
| | | | | | Export GPIO 41 to power USB port Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: gsw_mt7621: disable PORT 5 MAC RX/TX flow control by defaultPetr Štetiar2020-02-201-9/+3
| | | | | | | | | | | | | | | | | | | | | | | | Looking at the current upstream driver implementation, it seems like the TX/RX flow control is enabled only if the flow control pause option is resolved from the device/link partner advertisements (or otherwise set). On the other hand, our current in-tree driver force enables TX/RX flow control by default, thus possibly leading to TX timeouts if the other end sends pause frames (which are not properly handled?): WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x1ac/0x324 NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out Disabling the flow control on PORT 5 MAC seems to fix this issues as the pause frames are then filtered out. While at it, I'm removing the if condition completely as suggested, since this code is run only on mt7621 SoC, so there is no need to check for the silicon revisions. Ref: https://lists.openwrt.org/pipermail/openwrt-devel/2017-November/009882.html Ref: https://forum.openwrt.org/t/mtk-soc-eth-watchdog-timeout-after-r11573/50000/12 Suggested-by: Felix Fietkau <nbd@nbd.name> Reported-by: Rosen Penev <rosenp@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: correct Siemens WS-AP3610 blocksizeDavid Bauer2020-02-201-0/+1
| | | | | | | With the wrong blocksize, the rootfs was not positioned on the boundary of a block, thus breaking the mtdsplit driver. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add label MAC address for Ubiquiti Picostation M (XM)Adrian Schmutzler2020-02-191-0/+1
| | | | | | | This adds the label MAC address for the Ubiquiti Picostation M (XM). This was overlooked when adding support in the previous patch. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Ubiquiti Picostation M (XM)Adrian Schmutzler2020-02-195-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti Picostation M (XM), which has the same board/LEDs as the Bullet M XM, but different case and antennas. Specifications: - AR7241 SoC @ 400 MHz - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - External antenna: 5 dBi (USA), 2 dBi (EU) - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Attention: airOS firmware versions >= 5.6 have a new bootloader with an incompatible partition table! Please downgrade to <= 5.5 _before_ flashing OpenWrt! Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other NanoStation M boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_picostation-m-squashfs-factory.bin Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Ubiquiti Nanostation Loco M (XM)Sven Roederer2020-02-195-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti Nanostation Loco M (XM), which has the same board/LEDs as the Bullet M XM, but different case and antennas. Specifications: - AR7241 SoC @ 400 MHz - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - NS Loco M2: built-in antenna: 8 dBi; AR9287 - NS Loco M5: built-in antenna: 13 dBi; 2T2R 5 GHz radio - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Note that only certain firmware versions accept unsigned images. Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other NanoStation M boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_nanostation-loco-m-squashfs-factory.bin Tested on NanoStation Loco M2. Signed-off-by: Sven Roederer <freifunk@it-solutions.geroedel.de> Co-developed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: move TPLINK_HWID/_HWREV to parent for tplink-safeloaderAdrian Schmutzler2020-02-193-10/+4
| | | | | | | | | | | Several devices with tplink-safeloader contain default values (0x0) for TPLINK_HWID and TPLINK_HWREV in their device definitions. Move those to common tplink-safeloader definition so they do not have to be repeated each time. While at it, set default value for tplink-v1 and tplink-v2 as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add gpio4 pinmux on TL-WR841N/ND v8, WR842N v2, MR3420 v2Adrian Schmutzler2020-02-181-4/+8
| | | | | | | | | | | | | | | | | | | | | This adds a pinmux to the shared DTSI for TP-Link TL-WR841N/ND v8, TL-WR842N v2 and TL-MR3420 v2. It is supposed to be the equivalent of: /* config gpio4 as normal gpio function */ ath79_gpio_output_select(TL_MR3420V2_GPIO_USB_POWER,AR934X_GPIO_OUT_GPIO); This allows to enable USB power on these devices. While at it, move the jtag_disable_pins to &gpio node and remove the redundant status=okay there. Tested on TP-Link TL-WR842N v2. Fixes: FS#2753 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Armin Fuerst <armin@fuerst.priv.at>
* ath79: move mikrotik-caldata.sh to target base-filesAdrian Schmutzler2020-02-171-0/+0
| | | | | | | | | | | | | | Mikrotik devices will be found in both generic and nand subtargets. The file mikrotik-caldata.sh, currently used in generic, contains a few lines of code that would need to be duplicated for nand support. Instead of duplicating it, move it to target base-files, as size impact is small and the maintenance gain should outweigh it. This is changed separately to make life easier for the people currently working on Mikrotik NAND support. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Siemens WS-AP3610David Bauer2020-02-166-0/+218
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: Atheros AR7161 RAM: Samsung K4H511638D-UCCC 2x 64M DDR1 SPI: Micron M25P128 (16M) WiFi: Atheros AR9160 bgn Atheros AR9160 an ETH: Broadcom BCM5481 LED: Power (Green/Red) ETH (Green / Blue / Yellow) (PHY-controlled) WiFi 5 (Green / Blue) WiFi 2 (Green / Blue) BTN: Reset Serial: Cisco-Style RJ45 - 115200 8N1 Installation ------------ 1. Download the OpenWrt initramfs-image. Place it into a TFTP server root directory and rename it to 1401A8C0.img. Configure the TFTP server to listen at 192.168.1.66/24. 2. Connect the TFTP server to the access point. 3. Connect to the serial console of the access point. Attach power and interrupt the boot procedure when prompted (bootdelay is 1 second). 4. Configure the U-Boot environment for booting OpenWrt from Ram and flash: $ setenv boot_openwrt 'setenv bootargs; bootm 0xbf080000' $ setenv ramboot_openwrt 'setenv serverip 192.168.1.66; tftpboot; bootm' $ saveenv 5. Load OpenWrt into memory: $ run ramboot_openwrt Wait for the image to boot. 6. Transfer the OpenWrt sysupgrade image to the device. Write the image to flash using sysupgrade: $ sysupgrade -n /path/to/openwrt-sysuograde.bin Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: backport phy reset-controller patchesDavid Bauer2020-02-162-0/+151
| | | | | | | | | | The Siemens WS-AP3610 asserts reset to the ethernet PHY with the reset-register. Backport the necessary patches to de-assert reset when probing the PHY. These patches can be dropped when using kernel 5.4. Signed-off-by: David Bauer <mail@david-bauer.net>
* brcm2708: rename target to bcm27xxAdrian Schmutzler2020-02-14845-18/+18
| | | | | | | | | | | | | | | | | This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Despite, since subtargets range from bcm2708 to bcm2711, it seems appropriate to use bcm27xx instead of bcm2708 (again, as already done for BOARDNAME). This also renames the packages brcm2708-userland and brcm2708-gpu-fw. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: rename target to bcm63xxAdrian Schmutzler2020-02-14501-7/+7
| | | | | | | | | | This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* brcm47xx: rename target to bcm47xxAdrian Schmutzler2020-02-1492-9/+9
| | | | | | | | | | This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix HiWiFi HC5761A switch settingsDENG Qingfang2020-02-141-1/+4
| | | | | | HC5761A has only 2 LAN ports Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* sunxi: backport increased SATA/AHCI DMA TX/RX FIFOsAleksander Jan Bajkowski2020-02-131-0/+94
| | | | | | | | | | | | | | | | | | | | | This backports SATA performance boost from 5.3 kernel: Increasing the SATA/AHCI DMA TX/RX FIFOs (P0DMACR.TXTS and .RXTS, ie. TX_TRANSACTION_SIZE and RX_TRANSACTION_SIZE) from default 0x0 each to 0x3 each, gives a write performance boost of 120 MiB/s to 132 MiB/s from lame 36 MiB/s to 45 MiB/s previously. Read performance is above 200 MiB/s. [tested on SSD using dd bs=4K/8K/12K/16K/20K/24K/32K: peak-perf at 12K] dd bs Before MB/s After MB/s Increase 4k 14.4 16.5 15% 64k 34.5 74.4 116% 1M 40.5 93.2 130% Ref: https://forum.openwrt.org/t/sunxi-sata-write-speed-patch/54555/5 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> [commit subject & description tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for TP-Link TL-WR940N v6Adrian Schmutzler2020-02-134-0/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The TL-WR940N v6 is similar to v3/v4, it just has different LEDs and MAC address assignment. Specification: - 750 MHz CPU - 32 MB of RAM - 4 MB of FLASH - 2.4 GHz WiFi - 4x 10/100 Mbps Ethernet The use of LEDs is based on ar71xx, so blue LED is used for WAN and orange LED for diag (boot/failsafe/etc.). 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 wr940nv6_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. Thanks to Manuel Kock for reviewing and testing this patch. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Manuel Kock <github.web@manu.li>
* ath79: enable forceless sysupgrade from ar71xx on fritz300eAdrian Schmutzler2020-02-131-0/+1
| | | | | | | This adds the ar71xx board name to the SUPPORTED_DEVICES on ath79, so forceless sysupgrade on this device becomes possible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: swconfig: make compatible with kernel 5.2Mathias Kresin2020-02-121-6/+41
| | | | | | | | | | | | | | | | | | | | | Since kernel 5.2 within netlink messages the NLA_F_NESTED nested flag is validated. But swconfig/swlib doesn't set the flag for SWITCH_ATTR_OP_VALUE_PORTS related netlink messages and assigning ports to vlans via swconfig dev switch0 vlan 1 set ports '0 1 2 3 4 6t' Errors put with "Failed to set attribute: Invalid input data or parameter". Relax the validation rules and use the deprecated functions, to use the same level of validation as it was till kernel 5.1. Depending on who has swconfig related netlink messages implemented, there might be more broken tools out there and we should keep backward compatibility if possible. Signed-off-by: Mathias Kresin <dev@kresin.me> Tested-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: rewrite run_parsers_by_type() to use add_mtd_partitions()Rafał Miłecki2020-02-113-24/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make run_parsers_by_type() more similar to the parse_mtd_partitions(): 1. Use struct mtd_partitions 2. Use add_mtd_partitions() This change simplifies run_parsers_by_type() by: 1. Dropping loop 2. Dropping code getting partition properties (name, offset, size) Moreover this change allows passing more partitions details (e.g. mask_flags). One noticeable change introduced by this patch is adding parsed partitions as children. This results in printing their *relative* offsets which unifies this code with parse_mtd_partitions() behaviour. Before: [ 1.785448] 0x00000018f800-0x000000fb0000 : "rootfs" [ 1.791642] mtd: device 4 (rootfs) set to be root filesystem [ 1.797537] 1 squashfs-split partitions found on MTD device rootfs [ 1.804009] 0x0000004e0000-0x000000fb0000 : "rootfs_data" After: [ 1.785376] 0x00000018f800-0x000000fb0000 : "rootfs" [ 1.791601] mtd: device 4 (rootfs) set to be root filesystem [ 1.797491] 1 squashfs-split partitions found on MTD device rootfs [ 1.803936] Creating 1 MTD partitions on "rootfs": [ 1.808910] 0x000000350800-0x000000e20800 : "rootfs_data" Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: append tail to WF2881 initramfs imageSungbo Eo2020-02-111-0/+8
| | | | | | | | | | | | Stock firmware has a vendor-defined tail at the end of uImage for image validation. This patch enables OpenWrt installation from stock firmware without having to access the UART console. Installation via web interface: 1. Flash **initramfs** image through the stock web interface. 2. Boot into OpenWrt and perform sysupgrade with sysupgrade image. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ath79: add support for TP-Link TL-WA830RE v1Christian Buschau2020-02-116-1/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ports support for the TL-WA830RE v1 range extender from ar71xx to ath79. Specifications: - SOC: Atheros AR7240 - CPU: 400MHz - Flash: 4 MiB (Spansion S25FL032P) - RAM: 32 MiB (Zentel A3S56D40FTP-G5) - WLAN: Atheros AR9280 bgn 2x2 - Ethernet: 1 port (100M) Flash instructions: - install from u-boot with tftp (requires serial access) > setenv ipaddr a.b.c.d > setenv serverip e.f.g.h > tftpboot 0x80000000 \ openwrt-ath79-tiny-tplink_tl-wa830re-v1-squashfs-factory.bin > erase 0x9f020000 +0x3c0000 > cp.b 0x80000000 0x9f020000 0x3c0000 > bootm 0x9f020000 - flash factory image from OEM WebUI - sysupgrade from ar71xx image The device seems to be a clone of the following devices not yet added to ath79: - tl-wa701nd-v1 - tl-wa730re-v1 - tl-wa801nd-v1 - tl-wa901nd-v1 Signed-off-by: Christian Buschau <christian.buschau@mailbox.org> [make use of ar7240_tplink.dtsi, add note about clones] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: reorganize DTSI for ar7240 TP-Link devicesAdrian Schmutzler2020-02-118-46/+57
| | | | | | | | | | | | | | | | The current set of TP-Link devices with ar7240 SoC all share the same DTSI file. As the latter is very similar to the definition required for the to-be-supported TP-Link TL-WA devices with ar7240, this patch splits the definitions into a shared part for all TP-Link devices (ar7240_tplink.dtsi) and a file containing the specific setup for the present TL-WR devices (ar7240_tplink_tl-wr.dtsi), equivalent to the former ar7240_tplink_tl-wr74xn-v1.dtsi. While at it, remove unused firmware partition label and rename pinmux_switch_led_pins. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: restore pin state on probe for ar934x-spiChuanhong Guo2020-02-101-5/+11
| | | | | | | | | | | | If bootloader doesn't terminate its last spi operation properly before starting kernel, our first transfer in kernel becomes a continuous transfer to that request instead of a new one. Fix this flaw by restoring IOC register, which restored all pin state to default. Fixes: ebf0d8dade ("ath79: add new ar934x spi driver") Reported-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 04:28:41 +0000