aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ramips: improve support for HiWiFi HC5661A and HC5861BDENG Qingfang2019-08-083-8/+25
| | | | | | | | | | | | | HC5661A: - Fix pinctrl - Fix image size (15808k) - Use switch trigger for WAN LED Both: - Use tpt LED trigger for wireless - Explicitly disable USB nodes Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: add HC5X61A.dtsi for HiWiFi MT7628AN boardsDENG Qingfang2019-08-083-186/+104
| | | | | | | HiWiFi has several MT7628AN routers which have similar specs Add HC5X61A.dtsi to include them, like HC5X61.dtsi (for MT7620A) Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ath79: add support for PISEN WMB001NChuanhong Guo2019-08-085-0/+259
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: - SoC: AR9341 - RAM: 64M - Flash: 16M - Ethernet: 1 * FE port - WiFi: ar934x-wmac - Sound: WM8918 DAC 1 * 3.5mm headphone jack 2 * RCA connectors for speakers 1 * SPDIF out - USB: 1 * USB2.0 port Flash instruction: Upload generated factory image via vendor's web interface. Notes: A. Audio stuff: 1. Since AR934x, all pins for peripheral blocks can be mapped to any available GPIOs. We currently don't have a PCM/I2S driver for AR934x so pinmux for i2s and SPDIF are bound to i2c gpio node. This should be moved into I2S node when a PCM/I2S driver is available. 2. The i2c-gpio node is for WM8918. DT binding for it can't be added currently due to a missing clock from I2S PLL. B. Factory image: Image contains a image header and a tar.gz archive. 1. Header: A 288 byte header that has nothing to do with appended tarball. Format: 0x0-0x7 and 0x18-0x1F: magic values 0x20: Model number string 0xFC: Action string. It's either "update" or "backup" 0x11C: A 1 byte checksum. It's XOR result of 0x8-0x11B Firmware doesn't care about the rest of the header as long as checksum result is correct. The same header is used for backup and update routines so the magic values and model number can be obtained by generating a backup bin and grab values from it. 2. Tarball: It contains two files named uImage and rootfs, which will be flashed into corresponding mtd partition. Writing a special utility that can only output a fixed binary blob is overkill so factory image header is placed under image/bin instead. C. LED The wifi led has "Wi-Fi" marked on the case but vendor's firmware used it as system status indicator. I did the same in this device support patch. D. Firmware Factory u-boot is built without 'savenv' support so it's impossible to change kernel offset. A 2MB kernel partition won't be enough in the future. OKLI loader is used here to migrate this problem: 1. add OKLI image magic support into uImage parser. 2. build an OKLI loader, compress it with lzma and add a normal uImage header. 3. flash the loader to where the original kernel supposed to be. 4. create a uImage firmware using OKLI loader. 5. flash the created firmware to where rootfs supposed to be. By doing so, u-boot will start OKLI loader, which will then load the actual kernel at 0x20000. The kernel partition is 2MB, which is too much for our loader. To save this space, "mtd-concat" is used here: 1. create a 64K (1 erase block) partition for OKLI loader and create another partition with the left space. 2. concatenate rootfs and this partition into a virtual flash. 3. use the virtual flash for firmware partition. Currently OKLI loader is flashed with factory image only. sysupgrade won't replace it. Since it only has one function and it works for several years, its unlikely to have some bugs that requires a replacement. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* kernel: mtdsplit_uimage: add support for okli imageChuanhong Guo2019-08-081-0/+58
| | | | | | | | | | This adds support for uImage used by OpenWrt kernel loader. The parser searches for uImage header at flash eraseblock boundary and it might attempt to split any firmware with loader, therefore this entry doesn't have MTD_PARSER_TYPE_FIRMWARE so that this parser is only used when explicitly defined in dts. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ath79: add support for D-Link DIR-842 C3Perry Melange2019-08-076-0/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware spec of DIR-842 C3: 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: Perry Melange <isprotejesvalkata@gmail.com>
* ath79: fix vendor capitalization of TP-LinkAdrian Schmutzler2019-08-072-2/+2
| | | | | | | According to detective grep, with this patch all devices should be labelled "TP-Link" consistently. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link CPE220 v2Adrian Schmutzler2019-08-075-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | This seems to be identical to CPE210 v1 despite having removable antennas. Specifications: * SoC: Qualcomm Atheros AR9344 (560 MHz) * RAM: 64MB * Storage: 8 MB * Wireless: 2.4GHz N based built into SoC 2x2 * Ethernet: 2x 100/10 Mbps, integrated into SoC, 24V POE IN Installation: 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 address:192.168.0.254 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link CPE510 v1Adrian Schmutzler2019-08-075-2/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link CPE510-v1 is an outdoor wireless CPE for 5 GHz with two Ethernet ports based on Atheros AR9334 Specifications: - 560/450/225 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, 1x PoE-in, 1x PoE-out - 64 MB of DDR2 RAM - 8 MB of SPI-NOR Flash - 2T2R 5 GHz - 13 dBi built-in antenna - Power, LAN0, LAN1 green LEDs - 4x green RSSI LEDs 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 address:192.168.0.254 Based on the work of Paul Wassi <p.wassi@gmx.at> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link CPE210 v1Adrian Schmutzler2019-08-076-0/+117
| | | | | | | | | | | | | | | | | | | | | | Specifications: * SoC: Qualcomm Atheros AR9344 (560 MHz) * RAM: 64MB * Storage: 8 MB * Wireless: 2.4GHz N based built into SoC 2x2 * Ethernet: 2x 100/10 Mbps, integrated into SoC, 24V POE IN Installation: 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 address:192.168.0.254 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: create common definition tplink-loader-okliAdrian Schmutzler2019-08-072-18/+12
| | | | | | | The loader-okli is shared by several TP-Link CPExxx devices, so give it its own definition to prevent too much code duplication. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: provide common DTSI for CPE510 v2/v3 and CPE610Adrian Schmutzler2019-08-073-194/+103
| | | | | | | This puts some common code into a new shared DTSI. Common nodes are chosen so that the new DTSI can be used for CPE210 v1, too. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* tplink-safeloader: increase kernel partition for CPE/WBSx10v1Adrian Schmutzler2019-08-071-1/+1
| | | | | | | | | | | | | This is a preparation for ath79 support of the CPE210/CPE510 v1. Kernel size is chosen equal to the latest update for CPE610 v1. This also updates the partition size in ar71xx target, so code remains consistent if someone looks up the device. Since CPE210, CPE510, WBS210 and WBS510 (all v1) share the same partition layout definition, and are on deprecated target anyway, this changes them all at once. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: drop Fon(Foxconn) parser matching for the "firmware" partitionRafał Miłecki2019-08-061-1/+0
| | | | | | | | | | | | | | | | This parser's matching function appears to be too generic as it matches e.g. Buffalo WZR-HP-G300NH. That results in incorrect parts parsing. Luckily this parser is needed by Fon FON2601 only which uses DT-based ramips target. It means we can depend on mtd subsystem matching of "fonfxc,uimage" string. That said triggering this parser based on the "firmware" (or whatever MTD_SPLIT_FIRMWARE_NAME is) partiiton name is not needed. It can be dropped which will automatically fix the Buffalo WZR-HP-G300NH case. Fixes: a1c6a316d299 ("ramips: add support for Fon FON2601") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 4.19 to 4.19.64Koen Vandeputte2019-08-0619-396/+148
| | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 100-powerpc-4xx-uic-clear-pending-interrupt-after-irq-ty.patch - 950-0309-usb-dwc2-Disable-all-EP-s-on-disconnect.patch - 950-0310-usb-dwc2-Fix-disable-all-EP-s-on-disconnect.patch Fixes: - CVE-2019-13648 - CVE-2019-3900 - CVE-2019-10207 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.136Koen Vandeputte2019-08-0626-171/+58
| | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 306-v4.16-netfilter-remove-saveroute-indirection-in-struct-nf_.patch Remove upstreamed: - 100-powerpc-4xx-uic-clear-pending-interrupt-after-irq-ty.patch - 088-0002-i2c-qup-fixed-releasing-dma-without-flush-operation.patch - 500-arm64-dts-marvell-Fix-A37xx-UART0-register-size.patch Fixes: - CVE-2019-13648 - CVE-2019-10207 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.187Koen Vandeputte2019-08-0614-40/+40
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 021-bridge-multicast-to-unicast.patch Compile-tested on: none Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mediatek: add new dts files for mt7622 to v4.14John Crispin2019-08-062-0/+1123
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* Revert "kernel: generic: fix fonfxc uimage parser"Rafał Miłecki2019-08-061-14/+7
| | | | | | | | | | | | | | | | | This reverts commit e92a14709d37f64dcba8c81fa51e61e5f10f439a. mtdsplit_uimage_parse_fonfxc() gets called in two situations: 1) It was /requested/ from DT using "fonfxc,uimage" compatible string 2) It was called by parsing code after finding "firmware" (MTD_SPLIT_FIRMWARE_NAME) due to the parser's type Code added in the /fix/ commit basically just disabled the second case. If that's the real goal it could be achieved by simply dropping type MTD_PARSER_TYPE_FIRMWARE. It may however require another solution as it's possible that some non-DT target actually needs fonfxc uImage parsing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mediatek: update the mt7531 switch driverJohn Crispin2019-08-061-211/+94
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mvebu: remove support for deprecated DSA bindingsTomasz Maciej Nowak2019-08-051-1/+0
| | | | | | | | These legacy bindings were removed long time ago from dts, so there's no need to keep support for them. Spotted-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: enable xHCI USB controller connected to PCIeTomasz Maciej Nowak2019-08-052-0/+2
| | | | | | | | | | This commit fixes regression on Linksys WRT1900 (Mamba) where this device doesn't have USB 3.0 controller integrated in SoC, instead it has Etron EJ168 connected to PCIe lane. Previously enabled in kernel 4.4 and 4.9, was lost in transition to 4.14. Fixes: 4ccad92 ("mvebu: Add support for kernel 4.14") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: drop mvebu support in kmod-usb3Tomasz Maciej Nowak2019-08-053-0/+3
| | | | | | | This is already enabled as kernel built-in feature in mvebu target and none other target will use it. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mpc85xx: correct OCEDO Panda LED definitionDavid Bauer2019-08-051-2/+2
| | | | | | | WLAN0 and the unused LED are currently swapped. Fix this, so the LED behavior matches the other OCEDo devices. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for TP9343-based TP-Link TL-WR94x devicesAdrian Schmutzler2019-08-058-0/+297
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for several TP-Link devices based on TP9343 ("a QCA9561 without PCIe and USB"): - TL-WR940N v3 - TL-WR940N v4 - TL-WR941ND v6 The devices are only different concerning LEDs and MAC address assignment. All TL-WR940 are with non-detachable antennas (N), all TL-WR941 devices are with detachable antennas (ND). Specification: - 750 MHz CPU - 32 MB of RAM - 4 MB of FLASH - 2.4 GHz WiFi - 4x 10/100 Mbps Ethernet 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 * (see below) 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. * TFTP image names: 940 v3: wr941ndv6_tp_recovery.bin 940 v4: wr940nv4_tp_recovery.bin 941 v6: wr941ndv6_tp_recovery.bin Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for D-Link DIR-842 C1Jackson Lim2019-08-058-144/+207
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <jackcolentern@gmail.com> [fix whitespace issues] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add SUPPORTED_DEVICES for TP-Link TL-WR841N/ND v9 to v12Adrian Schmutzler2019-08-051-0/+4
| | | | | | In ar71xx, v10 and v12 did not have separate board_name. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WR841N/ND v12Adrian Schmutzler2019-08-056-23/+49
| | | | | | | | | | | | | | | | | | | | | | | 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 <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WR841N/ND v10Adrian Schmutzler2019-08-055-3/+27
| | | | | | | | | | | | | | | | | | | | | | | 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 <freifunk@adrianschmutzler.de>
* ar71xx: wpj531: fix SIG1/RSS1 LED GPIOLeon M. George2019-08-041-1/+1
| | | | | | | | | | | | | | 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 <leon@georgemail.eu> [commit subject/message facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: fix fonfxc uimage parserNOGUCHI Hiroshi2019-08-041-7/+14
| | | | | | | | | | | | | | | | We cannot distinguish between fonfxc uImage and generic uImage because fonfxc uImage header is almost same as generic uImage, except padding length after image name. The fonfxc uImage parser is available when specifying directly with DT compatible property. So this patch adds check if the partition DT node is compatible with the parser. Ref: https://bugs.openwrt.org/index.php?do=details&task_id=2413 Fixes: a1c6a316d299 ("ramips: add support for Fon FON2601") Signed-off-by: NOGUCHI Hiroshi <drvlabo@gmail.com> [commit light touches and removed C code comment] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* brcm2708: split up DEVICE_TITLEMoritz Warning2019-08-041-3/+5
| | | | | | | | | Splits up DEVICE_TITLE into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. Fixes https://github.com/openwrt/openwrt/pull/2245 Signed-off-by: Moritz Warning <moritzwarning@web.de> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: fix warnings due to non-breaking spaceÁlvaro Fernández Rojas2019-08-041-1/+1
| | | | | | | Reported by ZWx4 on Github: https://github.com/openwrt/openwrt/commit/19226502bf6393706defe7f049c587b32c9b4f33#r34555799 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mediatek: fix typo in Banana Pi R64 device titleAdrian Schmutzler2019-08-042-20/+1
| | | | | | | The DEVICE_TITLE introduced in 66458c49aa14 ("mediatek: add v4.19 support") is mistyped. Fix it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* brcm2708: arm8stub is no longer neededÁlvaro Fernández Rojas2019-08-031-8/+3
| | | | | | It's already embedded on latest RPi firmware. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: clean up target configsÁlvaro Fernández Rojas2019-08-034-13/+3
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ipq40xx: remove redundant PHY_POLL set codeChristian Lamparter2019-08-022-12/+2
| | | | | | | | The [devm_]mdiobus_alloc[_size()] functions are creating the array of interrupt numbers as well as initializing them to POLLING. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: decouple mdio-ipq40xx and ar40xxChristian Lamparter2019-08-022-235/+234
| | | | | | | This makes it possible to delete the ar40xx driver in the future by just removing the file. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: extend DT mdio node to be more accessibleChristian Lamparter2019-08-021-6/+6
| | | | | | | | The MDIO node will become more important in the future. Hence, this patch adds DT labels to make the properties inside the various subnodes more accessible. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* at91: split up DEVICE_TITLEMoritz Warning2019-08-021-19/+39
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* apm821xx: split up DEVICE_TITLEMoritz Warning2019-08-021-6/+11
| | | | | | Splits up DEVICE_TITLE into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* ipq806x: split up DEVICE_TITLEMoritz Warning2019-08-021-15/+36
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* bcm53xx: split up DEVICE_TITLEMoritz Warning2019-08-021-24/+46
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* gemini: split up DEVICE_TITLEMoritz Warning2019-08-021-7/+14
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* octeon: split up DEVICE_TITLEMoritz Warning2019-08-021-2/+4
| | | | | | Splits up DEVICE_TITLE into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* brcm2708: add bcm2711 subtarget (RPi 4B aarch64)Álvaro Fernández Rojas2019-08-025-4/+623
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: remove linux 4.14 supportÁlvaro Fernández Rojas2019-08-02455-153801/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: update to latest patches from the RPi foundationÁlvaro Fernández Rojas2019-08-021181-71541/+76419
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mediatek: add v4.19 supportJohn Crispin2019-08-0235-3/+13220
| | | | | | | | Bump the target to v4.19. Add a patch with additional eth driver fixes/features that MTK provided aswell as the driver for the new mt7530 switch. Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: fix HiveAP 121 PLL for 1000MDavid Bauer2019-08-011-1/+1
| | | | | | | | | | | | The Aerohive HiveAP 121 has the wrong PLL value set for Gigabit speeds, leading to packet-loss. 10M and 100M work fine. This commit sets the Gigabit Ethernet PLL value to the correct value, fixing packet loss. Confirmed with iperf and floodping. Signed-off-by: David Bauer <mail@david-bauer.net>
* ar71xx: really fix Mikrotik board detectionKoen Vandeputte2019-08-011-0/+1
| | | | | | | | | | | | | | | | | commit e09da0169a08 ("ar71xx: fix Mikrotik board detection") was generated based on testing a rb-912 board, on which detection failed. Testing on more hardware shows something fun: machine : MikroTik RouterBOARD 922UAGS-5HPacD machine : Mikrotik RouterBOARD 912UAG-5HPnD Both lowercase and uppercase are used. So ensure we support both now .. Fixes: e09da0169a08 ("ar71xx: fix Mikrotik board detection") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 07:52:21 +0000