aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ramips: support IMAGE_SIZE in kiB for Build/trxAdrian Schmutzler2019-07-251-1/+1
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix ralink_default_fw_size_16MAdrian Schmutzler2019-07-255-6/+6
| | | | | | | | | | | | | | | | | | | | | | In ramips, there are the following predefined values for IMAGE_SIZE ralink_default_fw_size_4M 3866624 3776k 0x3B0000 ralink_default_fw_size_8M 8060928 7872k 0x7B0000 ralink_default_fw_size_16M 16121856 15744k 0xF60000 ralink_default_fw_size_32M 33226752 32448k 0x1FB0000 Out of those, the "16M" value is obviously odd, as it provides more room for the remaining partitions than the tree others. Of the devices in all subtargets, there are actually > 50 that have a firmware partition with 0xFB0000 size, while only 5 (!) have 0xF60000. From the former, many are set to ralink_default_fw_size_16M anyway, although it is wrong at the present point. Consequently, it makes sense to change ralink_default_fw_size_16M to 0xFB0000, and to update IMAGE_SIZE for the 5 devices with 0xF60000. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/rt305x: fix firmware partition size for some 4MB devicesAdrian Schmutzler2019-07-253-3/+3
| | | | | | | | | | | | | | | allnet_all0256n-4m, tenda_w150m and unbranded_wr512-3gn-4m have their firmware partition set to reg = <0x50000 0x3c8000>. However, based on the 4MB flash, the size should be 0x3b0000. After some research in the target's history, it looks like the changed size has been a mistake when transferring device partitions from Makefile to DTS in 770b28f146f. This patch changes the named three devices back to 0x3b0000. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix mac addresses used by Phicomm K2PChuanhong Guo2019-07-251-0/+4
| | | | | | | | | | | Like most mt7621 boards, Phicomm K2P stores LAN/WAN mac addresses at 0xe000/0xe006 of factory partition. Phicomm uses lan_mac-1 as wan_mac, while our default case in 02_network uses lan_mac+1. Add a special case reading lan/wan mac address for Phicomm K2P. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: add kmod-mt7615e to Phicomm K2P imagesRoger Pueyo Centelles2019-07-251-0/+1
| | | | | | | | | | | | Now that the mt76 driver supports the MT7615D chip found on these devices, use it. Also add the wpad-basic package. Note: the driver supports operation on both the 2.4 GHz and the 5 GHz bands, but not yet concurrently. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* kernel: netfilter add connmark savedscp supportKevin Darbyshire-Bryant2019-07-252-0/+242
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | savedscp is a method of storing the DSCP of an ip packet into conntrack mark. In combination with a suitable tc filter action (conndscp but may end up being integrated into connmark) DSCP values are able to be stored on egress and restored on ingress across links that otherwise alter or bleach DSCP. This is useful for qdiscs such as CAKE which are able to shape according to policies based on DSCP. Ingress classification is traditionally a challenging task since iptables rules haven't yet run and tc filter/eBPF programs are pre-NAT lookups, hence are unable to see internal IPv4 addresses as used on the typical home masquerading gateway. The ingress problem is solved by the tc filter, but the tc people didn't like the idea of tc setting conntrack mark values, though they are ok with reading conntrack values and hence restoring DSCP from conntrack marks. x_tables CONNMARK with the new savedscp action solves the problem of storing the DSCP to the conntrack mark. It accepts 2 parameters. The mark is a 32bit value with usually one 1 bit set. This bit is set when savedscp saves the DSCP to the mark. This is useful to implement a 'one shot' iptables based classification where the 'complicated' iptables rules are only run once to classify the connection on initial (egress) packet and subsequent packets are all marked/restored with the same DSCP. A mark of zero disables the setting of a status bit/s. The mask is a 32bit value of at least 6 contiguous bits and represents the area where the DSCP will be stored. e.g. iptables -A QOS_MARK_eth0 -t mangle -j CONNMARK --savedscp-mark 0xfc000000/0x01000000 Would store the DSCP in the top 6 bits of the 32bit mark field, and use the LSB of the top byte as the 'DSCP has been stored' marker. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ar71xx: fix WLAN LED names for Archer C7Tomislav Požega2019-07-251-2/+2
| | | | | | Update WLAN LED colour identifier for both interfaces on Archer C7 Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: fix system LED names on Archer C5/C7Tomislav Požega2019-07-251-2/+2
| | | | | | | Move system LED board definitions of Archer C5/C7 to reflect actual system LED colour used Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: Archer C7 v1 LED names and RFKILL fixesTomislav Požega2019-07-251-10/+10
| | | | | | | | | | All leds on these boards are green. v1 has RFKILL GPIO 23 for production units (it had GPIO 13 only for test phase units, and these are rather very rare to find). As for the previous attempt to fix this and revert due to WDR boards have blue leds, it was wrong: WDR board does not use common setup (false). Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: update qca-usb-quirks patchTomislav Požega2019-07-251-1/+1
| | | | | | | Base address for USB0 has changed from 0x18116c94 on AR934X to 0x18116d94 on QCA9558. CP Typo remained for years here... Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ath79: fix indent in 01_ledsAdrian Schmutzler2019-07-241-2/+2
| | | | | | | | | Change capitalization from spaces to tabs in order to match the style of the file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [fix capitalization in commit title, add short description] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for D-Link DIR-842 C2Jackson Lim2019-07-246-0/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware spec of DIR-842 C2: SoC: QCA9563 DRAM: 128MB DDR2 Flash: 16MB SPI-NOR Switch: QCA8337N WiFi 5.8GHz: QCA9888 WiFi 2.4Ghz: QCA9563 USB: 2.0 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 <jackcolentern@gmail.com> [Reword reset-hog comment, fix formatting] Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: enable Newifi D1 SD slotDENG Qingfang2019-07-231-1/+1
| | | | | | | Newifi D1 is shipped with an 8GB microSD card in its SD slot Without SD driver users would not be able to use it unless manually installed Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* treewide: sysupgrade: get rid of platform_nand_pre_upgrade()Rafał Miłecki2019-07-228-88/+64
| | | | | | | | | | | 1) nand_do_upgrade() is always called by a target code 2) nand_do_upgrade() starts with calling platform_nand_pre_upgrade() It means there is no need for the platform_nand_pre_upgrade() callback at all. All code that was present there could bo moved & simplly called by a target right before the nand_do_upgrade(). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* layerscape: sysupgrade: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-221-9/+8
| | | | | | | | | | 1) RAMFS_COPY_BIN and RAMFS_COPY_DATA can be defined at top of the file like it's done for all other targets. 2) fw_printenv.lock can be created one step later in the platform_do_upgrade(). It seems to be working well on many other targets. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mac80211: Update to version 5.2-rc7Hauke Mehrtens2019-07-183-217/+1
| | | | | | | | | | | | | | This updates mac80211 to version 5.2-rc7, this contains all the changes to the wireless subsystem up to Linux 5.2-rc7. * The removed patches are applied upstream * b43 now uses kmod-lib-cordic * Update the nl80211.h file in iw to match backports version. * Remove the two backports from kernel 4.9, they were needed for mt76, but that can use the version from backports now, otherwise they collide and cause compile errors. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: modify device name of I-O DATA WN-AC1600DGR2INAGAKI Hiroshi2019-07-182-5/+6
| | | | | | | | | | | | | | | | | | | | | | | The hardware of I-O DATA WN-AC1600DGR3 has completely compatibility with WN-AC1600DGR2, so modify the device name of WN-AC1600DGR2 to show the images for DGR2 also support DGR3. Specification of WN-AC1600DGR3: - SoC : Qualcomm Atheros QCA9557 - RAM : DDR2 128 MiB - Flash : SPI-NOR 16 MiB - WLAN : 2.4/5 GHz - 2.4 GHz : QCA9557 (SoC), 2T2R - 5 Ghz : QCA9880, 3T3R - Ethernet : 5x 10/100/1000 Mbps - Switch : QCA8337N - LEDs/Input : 6x/6x (4x buttons, 1x slide-switch) - UART : through-hole on PCB - J1: Vcc, GND, TX, RX from ethernet port side - 115200n8 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: Add support for TP-Link Archer C60 v2Adrian Schmutzler2019-07-185-2/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60 v2 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561 + QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB 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 tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin 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 Flash instruction (under U-Boot, using UART): tftp 0x81000000 ...-sysupgrade.bin erase 0x9f030000 +$filesize cp.b $fileaddr 0x9f030000 $filesize reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: Add support for TP-Link Archer C60 v1Adrian Schmutzler2019-07-186-1/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60v1 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561+QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB 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 tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin 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. Flash instruction under U-Boot, using UART: 1. tftp 0x81000000 ...-sysupgrade.bin 2. erase 0x9f020000 +$filesize 3. cp.b $fileaddr 0x9f020000 $filesize 4. reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link CPE510-v2/v3Andrew Cameron2019-07-186-0/+215
| | | | | | | | | | | | | | | | | | | | | | | | | TP-Link CPE510-v2/v3 is an outdoor wireless CPE for 5 GHz with one Ethernet port based on Atheros AR9344 Specifications: - Based on the same underlying hardware as the TP-Link CPE510 - Power, LAN, and 4 green LEDs - 1 10/100Mbps Shielded Ethernet Port (Passive PoE in) - Built-in 13dBi 2x2 dual-polarized directional MIMO antenna - Adjustable transmission power from 0 to 23dBm/200mw Flashing instructions: Flash factory image through stock firmware WEB UI or through TFTP To get to TFTP recovery just hold reset button while powering on for around 4-5 seconds and release. Rename factory image to recovery.bin Stock TFTP server IP:192.168.0.100 Stock device TFTP adress:192.168.0.254 Signed-off-by: Andrew Cameron <apcameron@softhome.net> [whitespace fixes] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for Trendnet TEW-823DRUPramod Pancha2019-07-185-1/+249
| | | | | | | | | | | | | | | | | | | | | Trendnet TEW-823DRU is a dual-band AC1750 router. The router is based on Qualcomm/Atheros QCA9558 + QCA9880. Specification: 720 MHz CPU 256 MB of RAM 16 MB of FLASH 3T3R 2.4 GHz 3T3R 5 GHz 5x 10/100/1000 Mbps Ethernet Firmware can be flashed from the web interface. Tested on 3 routers with no issues. Signed-off-by: Pramod Pancha <pancha@vill.com> [whitespace fixes] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for TP-Link RE355 v1 and RE450 v1Christoph Krapp2019-07-178-0/+240
| | | | | | | | | | | | | | | | | | | | | | Specification: SoC: Qualcomm Atheros QCA9558 RAM: 64/128MiB Flash: 8MiB SPI-NOR Wifi: - 2.4GHz: 3T3R (QCA9558) - 5GHz: 3T3R (QCA9880) LAN: 1x 10/100/1000 Mbps UART: - TP1: Tx - TP2: Rx - TP3: Gnd - TP4: 3v3 Flash instructions: Flash factory image through stock firmware WEB UI. Signed-off-by: Christoph Krapp <achterin@googlemail.com>
* ramips: add support for TP-Link RE650 v1Georgi Vlaev2019-07-174-9/+204
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link RE650 v1 is a dual-band AC2600 range extender, based on MediaTek MT7621A and MT7615E. According to the wikidevi entry for RE650 this device is identical with TP-Link RE500 as hardware. This patch supports only RE650. Hardware specification: - SoC 880 MHz - MediaTek MT7621AT - 128 MB of DDR3 RAM - 16 MB - Winbond 25Q128FVSG - 4T4R 2.4 GHz - MediaTek MT7615E - 4T4R 5 GHz - MediaTek MT7615E - 1x 1 Gbps Ethernet - MT7621AT integrated - 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2)) - 4x buttons (Reset, Power, WPS, LED) - UART header (J1) - 2:GND, 3:RX, 4:TX Serial console @ 57600,8n1 Flash instructions: Upload openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin from the RE650 web interface. TFTP recovery to stock firmware: Unfortunately, I can't find an easy way to recover the RE without opening the device and using modified binaries. The TFTP upload will only work if selected from u-boot, which means you have to open the device and attach to the serial console. The TFTP update procedure does *not* accept the published vendor firmware binaries. However, it allows to flash kernel + rootfs binaries, and this works if you have a backup of the original contents of the flash. It's probably possible to create special image out of the vendor binaries and use that as recovery image. Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com> [re-added variables for kernel header] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for Bluesocket BSAP1880 boardDaniel Gimpelevich2019-07-178-0/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This board was used in dual-band 802.11n enterprise access points, models BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was acquired by Adtran in 2011, who has now EOL'ed them. They differed only in that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were inside the case. They have an external RJ-45 console port, which works with standard Cisco 72-3383-01 console cables. Specification: - System-On-Chip: AR7161 - CPU/Speed: 600 MHz - Flash-Chip: Macronix MX25L12845E - Flash size: 16 MiB - RAM: 64 MiB - Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn - Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an - PHY: Vitesse VSC8601, Rev. B Installation: 1. Connect to the serial console using a terminal that supports YMODEM at 115200 bps, 8 data bits, no parity, 1 stop bit 2. Interrupt the bootloader using its password, which is: r00t 3. Issue the "fis init" command, confirming if prompted 4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin file, and substitute it below, instead of where I have "LeNgTh" 5. Issue the following command, and upload this file using YMODEM protocol load -r -v -b 0x80060000 -m ymodem 6. Issue the following commands, substituting as mentioned above: fis create -b 0x80060000 -l LeNgTh vmlinux_2 load -r -v -b 0x80100000 -m ymodem 7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin 8. Issue the "fis free" command, and for the first range in its response, use a hexadecimal calculator to subtract the start from the end in order to substitute it below, with the leading "0x" to specify it in hexadecimal, instead of where I have "LeNgTh" 9. Issue the following commands, substituting as mentioned above: fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs reset 10.Wait for the status LED to go solid green Tested-by: Brian Gonyer <bgonyer@gmail.com> Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> [fixed obsolete $ARGV in platform_do_upgrade] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: widen RedBoot directory search and add PHYDaniel Gimpelevich2019-07-171-1/+2
| | | | | | | | The Bluesocket BSAP1880 board has a Vitesse PHY, for which the driver was not being included, and its RedBoot directory block is earlier in the flash than the search was allowing. This commit prepares for supporting it. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ath79: support "rgmii-id" PHY mode in ag71xxDaniel Gimpelevich2019-07-171-0/+2
| | | | | | | The ag71xx code did not include a case for the "rgmii-id" PHY mode in the code. There are devices that need this mode, so I'm adding it. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* brcm47xx: fix 831-old_gpio_wdt.patch for linux 4.19Zachary Cook2019-07-171-2/+2
| | | | | | | | | | | | Fix the following compilation error when using linux 4.19 on brcm47xx: drivers/watchdog/old_gpio_wdt.c:236:2: error: implicit declaration of function 'setup_timer' setup_timer was removed and replaced by timer_setup in linux >=4.15: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=513ae785 Update the patch to use the timer_setup interface Signed-off-by: Zachary Cook <zachcook1991@gmail.com>
* ath79: ar9330: add missing watchdog nodePetr Štetiar2019-07-171-0/+10
| | | | | | | | It was reported in FS#2385, that Carambola2 doesn't currently have working watchdog so fix it by adding watchdog node. Ref: FS#2385 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add MT7615 wireless support for ELECOM WRC-1167GHBK2-SINAGAKI Hiroshi2019-07-172-4/+12
| | | | | | | | | | | | | ELECOM WRC-1167GHBK2-S has a MediaTek MT7615D chip for 2.4/5 GHz wireless. A driver package for MT7615 chip is added to OpenWrt in a0e5ca4f3523b9eef96bff32e45f6fa8275b982f, so add preliminary MT7615 chip support for WRC-1167GHBK2-S. Note: Currently, DBDC mode for MT7615 is not supported in mt76 driver. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* kernel: generic: fix perf build breakage on 4.19Petr Štetiar2019-07-171-40/+0
| | | | | | | | | | | | Drop 211-host_tools_portability.patch which is breaking perf build on 4.19 kernels by removing the include directory from the host's CFLAGS leading to the following build breakage: pmu-events/jevents.c:48:10: fatal error: linux/list.h: No such file or directory #include <linux/list.h> ^~~~~~~~~~~~~~ Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: apalis: add missing jffs2reset to ramfs during sysupgradePetr Štetiar2019-07-171-1/+1
| | | | | | | | | | | | | jffs2reset is used to cleanup the rootfs_data overlay, but it's currently missing in the ramfs during sysupgrade leading to the following error: Switching to ramdisk... Performing system upgrade... /lib/upgrade/do_stage2: line 27: jffs2reset: not found Fixes: 2f1a11d0089c ("imx6: apalis: fix config survival after sysupgrade -n") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: apalis: fix sysupgrade pathsPetr Štetiar2019-07-171-5/+2
| | | | | | | | We can't use $board_name in sysupgrade paths for kernel and rootfs as we currently generate one image which could be used on two different base boards. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: add modern network modules to Generic targetAlberto Bursi2019-07-171-1/+2
| | | | | | | | | | | | | | | Many Atom-based embedded/industrial x86 boards can't run 64bit operating systems due to either processor or board firmware limitations, but they have modern interfaces (PCIe) or have modern Intel gigabit controllers onboard. With the current default package selection for x86 Generic target their network won't work. Add the modern gigabit network modules needed or most likely going to be used as add-in cards, similar to what is the list on x86_64 target. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mvebu: sysupgrade: don't use $ARGV in platform_check_image()Rafał Miłecki2019-07-171-1/+1
| | | | | | | sysupgrade passes image path to platform_check_image() as an argument so it can be simply accessed using $1 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: sysupgrade: don't use $ARGV in platform_do_upgrade()Rafał Miłecki2019-07-1716-45/+45
| | | | | | | stage2 passes image path to platform_do_upgrade() as an argument so it can be simply accessed using $1 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-161-12/+8
| | | | | | | | | | | The only step between platform_pre_upgrade() and platform_do_upgrade() is switching to ramdisk. It should be fine to "mtd erase firmware" from the later callback and get rid of the first one. This change wasn't tested on affected target but identical code logic was verified to work as expected on brcm47xx with initramfs firmware. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-161-27/+23
| | | | | | | | | | | The only step between platform_pre_upgrade() and platform_do_upgrade() is switching to ramdisk. It should be fine to "mtd erase firmware" from the later callback and get rid of the first one. This change wasn't tested on affected target but identical code logic was verified to work as expected on brcm47xx with initramfs firmware. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: enable SGMII fixup on Mikrotik wAP ACEtienne Champetier2019-07-161-0/+16
| | | | | | | | | | | | | | | | fixes intermittent loss of connectivity on 1Gbit port, with log message: > 803x_aneg_done: SGMII link is not ok Thanks to David Bauer for pointing me in the right direction. I just had to figure out the right bus_id, which you find in this log: > ag71xx ag71xx.1: connected to PHY at gpio-1:00 [uid=004dd074, driver=Atheros 8031 ethernet] Fixes FS#2236 Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> [Wrapped commit message - Fixed whitespace erors] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add seama header fixup for Qihoo C301Chuanhong Guo2019-07-161-0/+15
| | | | | | | | | This script is copied from ar71xx. Without a header fixup, u-boot checksum for kernel will fail after the first boot. Fixes: a9360452f0 ("ath79: add support for Qihoo C301") Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* orion: sysupgrade: change platform_check_image() args validationRafał Miłecki2019-07-161-1/+1
| | | | | | | sysupgrade passes image to check as argument so use $# instead of $ARGC. It also fits this function better as it checks $1 and not $ARGV. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mvebu: sysupgrade: drop platform_copy_config_sdcard() argumentRafał Miłecki2019-07-161-1/+1
| | | | | | | That function doesn't take any arguments so don't pass anything when calling it. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: Remove left-over mistyped device string from 02_networkAdrian Schmutzler2019-07-161-1/+0
| | | | | | | | | | | In 2011 (!), network setup for nexaira,bc2 was moved to network defaults script with a typo so it became b2c: 295e04084c ("ramips: setup bc2 mac addresses from the generic network script") This patch just removes the useless entry without replacement, since it seems to have worked for 8 years anyway. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add wmac migration for all ar93xx/qca95xx SoCsChuanhong Guo2019-07-161-5/+6
| | | | | | | Add migration for all ar71xx device path as well as previously incorrect ath79 path. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ath79: ar93xx/qca95xx: move gmac/wmac/pcie node out of apb busChuanhong Guo2019-07-165-123/+123
| | | | | | | | according to functional block diagram in datasheet, these devices don't belong to apb bus. Move these nodes out to match datasheet description. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ath79: add support for Qihoo C301Chuanhong Guo2019-07-168-0/+280
| | | | | | | | | | | | | | | | Specifications: - SoC: AR9344 - RAM: 128MB - Flash: 2 * 16MB (MX25L12845) - Ethernet: 2 * FE LAN & 1 * FE WAN - WiFi: 2.4G: AR9344 5G: QCA9882 Flash instruction: 1. Hold reset and power up the router 2. Set your IP to 192.168.1.x 3. Open 192.168.1.1 and upload the generated *factory* firmware Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: mtk-mmc: mt76x8: check ESD_MODE before applying AGPIO_CFGChuanhong Guo2019-07-161-8/+4
| | | | | | | | | | | | | | | | | | | | | | | Since mt76x8an ver1 eco2, SDXC pins can be switched to the following pinmap: sd_d1 -> PAD_I2S_SDI sd_d0 -> PAD_I2S_WS sd_cmd -> PAD_I2S_CLK sd_d3 -> PAD_I2C_SCLK sd_d2 -> PAD_I2C_SD sd_clk -> PAD_GPIO0 sd_wp -> PAD_TXD1 sd_cd -> PAD_RXD1 To use this pinmap, one would need to set ESD_MODE bit (bit 15) to 1 in GPIO1_MODE and switch other used pads into GPIO mode. In this mode, we don't need to switch ethernet pins to digital pad. Check ESD_MODE bit before applying AGPIO_CFG and use rt_sysc_m32 to set it. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* mpc85xx: split up DEVICE_TITLEMoritz Warning2019-07-161-5/+12
| | | | | | Splits up DEVICE_TITLE into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* tegra: split up DEVICE_TITLEMoritz Warning2019-07-151-1/+2
| | | | | | Splits up DEVICE_TITLE into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* ath79: add support for devolo WiFi pro 1750xDavid Bauer2019-07-144-1/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- CPU: Qualcomm Atheros QCA9558 RAM: 128M DDR2 FLASH: 16MiB ETH: 1x Atheros AR8035 (PoE in) WiFi2: QCA9558 3T3R WiFi5: QCA9880 3T3R BTN: 1x Reset LED: 1x LED Power (non-controllable) 1x LED Status (internal) 1x LED LAN (controlled by PHY) 1x LED WLAN BEEP: 1x GPIO attached piezo beeper UART: 3.3V GND TX RX (115200-N-8) (3.3V is square pad) Header is located next to external-LED header. Installation ------------ Make sure you set a password for the root user as prompted on first setup! 1. Upload OpenWRT sysupgrade image via SSH to the device. Use /tmp as the destination folder on the device. User is root, password the one set in the web interface. 2. Install OpenWRT with > sysupgrade -n -F /tmp/<openwrt-image-name> Signed-off-by: David Bauer <mail@david-bauer.net>
* gemini: Stop enforcing command lineLinus Walleij2019-07-142-4/+0
| | | | | | | | | | | | The command line enforced by the kernel is harmful, we want to use the command line passed from the device tree. This is especially important for the SQ201, Teltonika RUT and WBD111 which has a console set to 115200n8 and not 19200n8 like all the others, so their consoles will be confusingly changing baudrate between boot loader and kernel. The setting in the device tree corresponds to what the boot loader is using. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 04:58:19 +0000