aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ramips: add support for Netgear EX6120Adrian Schmutzler2020-06-116-2/+72
| | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: * SoC: MT7620A * CPU: 580 MHz * RAM: 64 MB DDR * Flash: 8MB NOR SPI flash * WiFi: MT7612E (5GHz) and builtin MT7620A (2.4GHz) * LAN: 1x100M The device is identical to the EX6130 except for the mains socket and the hardware ID. Installation: The -factory images can be flashed from the device's web interface or via nmrpflash. Notes: MAC addresses were set up based on the EX6130 setup. This is based on prior work of Adam Serbinski and Mathias Buchwald. Tested by Mathias Buchwald. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add mt7621 ethernet driver improvementsFelix Fietkau2020-06-102-0/+98
| | | | | | | - Speed up MDIO bus access - Improve performance on tx completion Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: backport upstream DSA GRO supportFelix Fietkau2020-06-101-0/+143
| | | | | | Should improve performance Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: enable packet steering by default on mt7621Felix Fietkau2020-06-101-0/+4
| | | | | | | It provides a significant performance boost, especially with flow offloading enabled Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ath79: wndr3700 series: fix wifi range & throughputChristian Lamparter2020-06-092-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds ar71xx's GPIO setup for the 2.4GHz and 5GHz antennae demultiplexer: | 158 /* 2.4 GHz uses the first fixed antenna group (1, 0, 1, 0) */ | 159 ap9x_pci_setup_wmac_gpio(0, (0xf << 6), (0xa << 6)); | 160 | 161 /* 5 GHz uses the second fixed antenna group (0, 1, 1, 0) */ | 162 ap9x_pci_setup_wmac_gpio(1, (0xf << 6), (0x6 << 6)); This should restore the range and throughput of the 2.4GHz radio on all the derived wndr3700 variants and versions with the AR7161 SoC. A special case is the 5GHz radio. The original wndr3700(v1) will benefit from this change. However the wndr3700v2 and later revisions were unaffected by the missing bits, as there is no demultiplexer present in the later designs. This patch uses gpio-hogs within the device-tree for all wndr3700/wndr3800/wndrmac variants. Notes: Based on the PCB pictures, the WNDR3700(v1) really had eight independent antennae. Four antennae for each radio and all of those were printed on the circut board. The WNDR3700v2 and later have just six antennae. Four of those are printed on the circuit board and serve the 2.4GHz radio. Whereas the remaining two are special 5GHz Rayspan Patch Antennae which are directly connected to the 5GHz radio. Hannu Nyman dug pretty deep and unearthed a treasure of information regarding the history of how these values came to be in the OpenWrt archives: <https://dev.archive.openwrt.org/ticket/6533.html>. Mark Mentovai came across the fixed antenna group when he was looking into the driver: fixed_antenna_group 1, (0, 1, 0, 1) fixed_antenna_group 2, (0, 1, 1, 0) fixed_antenna_group 3, (1, 0, 0, 1) fixed_antenna_group 4, (1, 0, 1, 0) Fixes: FS#3088 Reported-by: Luca Bensi Reported-by: Maciej Mazur Reported-by: Hannu Nyman <hannu.nyman@iki.fi> Debugged-by: Hannu Nyman <hannu.nyman@iki.fi> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* oxnas: build with 8021Q VLAN supportDaniel Golle2020-06-091-1/+0
| | | | | | | | CONFIG_VLAN_8021Q was explicitely disabled in oxnas kernel config. Don't do that, so VLANs can be used on the target. Fixes: dcc34574ef ("oxnas: bring in new oxnas target") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 5.4 to 5.4.45Petr Štetiar2020-06-0929-594/+350
| | | | | | | | | | | | | | | | | | | Fixes CVE-2020-10757 via upstream commit df4988aa1c96 ("mm: Fix mremap not considering huge pmd devmap"). Resolved merge conflict in the following patches: bcm27xx: 950-0128-gpiolib-Don-t-prevent-IRQ-usage-of-output-GPIOs.patch Refreshed patches, removed upstreamed patch: generic: 751-v5.8-net-dsa-mt7530-set-CPU-port-to-fallback-mode.patch generic: 754-v5.7-net-dsa-mt7530-fix-roaming-from-DSA-user-ports.patch Run tested: qemu-x86-64 Build tested: x86/64, imx6, sunxi/a53 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: erx and erx-sfp: fix missing WAN interfacePerry Melange2020-06-091-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This partially reverts commit 5acd1ed0be0d ("ramips: mt7621: fix Ubiquiti ER-X ports names and MAC addresses"), this change was discussed in https://github.com/openwrt/openwrt/pull/2901#discussion_r407238452 With commit 5acd1ed0be0d ("ramips: mt7621: fix Ubiquiti ER-X ports names and MAC addresses"), all the ports were put into the LAN bridge, with the argument that the OEM firmware does not have a WAN port enabled. In the default OEM setup, all of the ports except eth0 are dead and eth0 is set to a static IP address without providing DHCP services when connected. It is only after the wizard has been run that eth0 becomes the WAN port and all the rest of the ports belong to LAN with DHCP enabled. Having all of the ports set to the LAN bridge does not mirror the default OEM setup. To accomplish that, then only eth0 would be in the LAN bridge. But this is not the expected behaviour of OpenWrt. Therefore this proposal to set eth0 to WAN and eth1-N to LAN provides the expected behaviour expected from OpenWrt, maintains the current documentation as up-to-date, and does not require the user to manually detach eth0 from the LAN bridge, create the WAN(6) interface(s), and set eth0 to the WAN(6) interface(s). Fixes: 5acd1ed0be0d ("ramips: mt7621: fix Ubiquiti ER-X ports names and MAC addresses") Signed-off-by: Perry Melange <isprotejesvalkata@gmail.com> [commit subject and description tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mediatek: fix image/mt7622.mkJohn Crispin2020-06-071-1/+1
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* bcm63xx: bcm6328: switch to upstream boot sel patchÁlvaro Fernández Rojas2020-06-072-13/+30
| | | | | | BCM6328 boot selection fix has been upstreamed. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add support for the Sercomm H500-sDaniel González Cabanelas2020-06-078-3/+350
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sercomm H500-s is an xDSL dual band wireless router based on Broadcom BCM63167 SoC. Hardware: SoC: Broadcom BCM63167 CPU: BMIPS4350 V8.0, 400 MHz, 2 cores Flash: NAND 128 MiB RAM: DDR3 128 MiB Ethernet: 4x 10/100/1000 Mbps Switch: BCM53134S Wireless: 802.11b/g/n: BCM435f (integrated) 802.11ac: Quantenna QT3740BC (onboard SoC) USB: 1x 2.0 LEDs/Buttons: 11x / 2x Flash instruction, web UI: 1. Reset to defaults using the reset button if the admin password is unknown 2. Login into the web UI as admin. Address: http://192.168.0.1 User: admin Password: VF-ESVodafone-H-500-s or l033i-h500s 3. Go to Settings -> Firmware Update, and select the Openwrt factory firmware 4. Update the firmware. 5. Wait until it finish, the device will reboot with Openwrt installed on the alternative image partitions keeping the stock firmware in the former. Notes: - The patch also adds support for the lowi version. Only the factory firmware is different. - The integrated Wifi in the Broadcom Soc isn't still supported. - The Quantenna 802.11ac wifi works ok, but needs to be configured with the Quantenna client application. It can't be configured with Luci nor any iw command since it's a separated subsystem linked via ethernet. - The BCM53134S external switch is managed via MDIO which isn't supported in this target. Therefore it will behave as a dumb switch. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: image: support device-specific load addressÁlvaro Fernández Rojas2020-06-071-12/+10
| | | | | | | Some CFEs are located at the address currently used for relocation and lzma loader load address, so we need to provide a way to override it. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: don't add the CFE to the sercomm factoryDaniel González Cabanelas2020-06-071-12/+0
| | | | | | | | | | | | | | | There is no need to include the CFE bootloader in the Sercomm factory images. There might be a case when this could be useful: - We are running the stock firmware on the first Sercomm image - The second partition storing the botloader was erased (unlikely) Even in this case flashing an image without a bootlader is harmless. Don't include the bootloader in the factory image creation and rid of the risk of flashing factory images with an untested bootloader partition. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: kernel: add BCM63167 cpuid variantDaniel González Cabanelas2020-06-073-24/+28
| | | | | | | | | The BCM63167 is a BCM63268 SoC with a different physical packaging. Add the CPU ID to allow supporting routers with this SoC (i.e Sercomm H500-s) Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: vr-3032u: add missing compatible propertyÁlvaro Fernández Rojas2020-06-071-1/+1
| | | | | | SoC is a BCM63168. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vg-8050: add missing compatible propertyÁlvaro Fernández Rojas2020-06-071-1/+1
| | | | | | SoC is a BCM63169. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mediatek: add mt7531 DSA supportJohn Crispin2020-06-078-38/+2028
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: add bpi-r64 emmc supportJohn Crispin2020-06-075-8/+638
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: make emmc image generation work on mt7622John Crispin2020-06-072-1/+20
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: switch over to extended upstream eip97 driverJohn Crispin2020-06-073-0/+5514
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: tidy up image subtarget MakefilesSungbo Eo2020-06-072-24/+23
| | | | | | | | | | - sort device recipes alphabetically - adjust board name of ELECOM WRC-2533GENT - harmonize line wrapping Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rebased] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm27xx: fix unmounting /boot after sysupgradeStijn Tintel2020-06-071-1/+1
| | | | | | | | Due to a typo, /boot is not properly unmounted after copying the backup file to it. Fix the typo to solve this. Fixes: 246916ddf4a1 ("brcm2708: use x86's upgrade scripts for all rpi targets") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: sch_cake: use skb hash improve wireguard compatibilityKevin Darbyshire-Bryant2020-06-051-0/+170
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While the other fq-based qdiscs take advantage of skb->hash and doesn't recompute it if it is already set, sch_cake does not. This was a deliberate choice because sch_cake hashes various parts of the packet header to support its advanced flow isolation modes. However, foregoing the use of skb->hash entirely loses a few important benefits: - When skb->hash is set by hardware, a few CPU cycles can be saved by not hashing again in software. - Tunnel encapsulations will generally preserve the value of skb->hash from before the encapsulation, which allows flow-based qdiscs to distinguish between flows even though the outer packet header no longer has flow information. It turns out that we can preserve these desirable properties in many cases, while still supporting the advanced flow isolation properties of sch_cake. This patch does so by reusing the skb->hash value as the flow_hash part of the hashing procedure in cake_hash() only in the following conditions: - If the skb->hash is marked as covering the flow headers (skb->l4_hash is set) AND - NAT header rewriting is either disabled, or did not change any values used for hashing. The latter is important to match local-origin packets such as those of a tunnel endpoint. The immediate motivation for fixing this was the recent patch to WireGuard to preserve the skb->hash on encapsulation. As such, this is also what I tested against; with this patch, added latency under load for competing flows drops from ~8 ms to sub-1ms on an RRUL test over a WireGuard tunnel going through a virtual link shaped to 1Gbps using sch_cake. This matches the results we saw with a similar setup using sch_fq_codel when testing the WireGuard patch. Fixes: 046f6fd5daef ("sched: Add Common Applications Kept Enhanced (cake) qdisc") Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* mvebu: remove ClearFog Pro SUPPORTED_DEVICESDENG Qingfang2020-06-051-1/+0
| | | | | | | | | | A direct upgrade from previous swconfig version with incompatible settings to DSA will break the internet. Remove SUPPORTED_DEVICES so users cannot upgrade directly. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [rebase after Linksys rename, adjust title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: rename Linksys devices based on their common namesPaul Spooren2020-06-0521-77/+223
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Linksys devices in mvebu target feature a mixed naming, where parts are based on the official product name (device node, image; e.g. WRT3200ACM) and parts are based on the internal code name (DTS file name, compatible, LED labels; e.g. rango). This inconsistent naming has been perceived as quite confusing. A recent attempt by Paul Spooren to harmonize this naming in kernel has been declined there. However, for us it still makes sense to apply at least a part of these changes locally. Primarily, this patch changes the compatible in DTS and thus the board name used in various scripts to have them in line with the device, model and image names. Due to the recent switch from swconfig to DSA, this allows us to drop SUPPORTED_DEVICES and thus prevent seamless upgrade between these incompatible setups. However, this does not include the LED label rename from Paul's initial patch: I don't think it's worth keeping the enormous diff locally for this case, as we can implement this much easier in 01_leds if we have to live with the inconsistency anyway. Signed-off-by: Paul Spooren <mail@aparcar.org> [rebase, extend to all devices, drop DT LED changes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: b53: fix compilation with kernels 5.5+Rafał Miłecki2020-06-051-0/+8
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* generic: mt7530: support adjusting EEEDENG Qingfang2020-06-041-0/+121
| | | | | | Add support for adjusting EEE with ethtool Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* generic: mt7530: fix roaming from DSA user portsDENG Qingfang2020-06-041-0/+116
| | | | | | | | | | | | | | | | | | | When a client moves from a DSA user port to a software port in a bridge, it cannot reach any other clients that connected to the DSA user ports. That is because SA learning on the CPU port is disabled, so the switch ignores the client's frames from the CPU port and still thinks it is at the user port. Fix it by enabling SA learning on the CPU port. To prevent the switch from learning from flooding frames from the CPU port, set skb->offload_fwd_mark to 1 for unicast and broadcast frames, and let the switch flood them instead of trapping to the CPU port. Multicast frames still need to be trapped to the CPU port for snooping, so set the SA_DIS bit of the MTK tag to 1 when transmitting those frames to disable SA learning. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* generic: fix DSA VLAN filteringDENG Qingfang2020-06-043-0/+199
| | | | | | | | | | | Currently enabling VLAN filtering blocks all traffic in the bridge immediately. That is because DSA ignores all VLAN setup when VLAN filtering is disabled, and when it is enabled, there is no VLAN entry in the VLAN table, causing all traffic to be blocked. Add patches to allow VLAN setup even if VLAN filtering is disabled. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* generic: mt7530: set CPU port to fallback modeDENG Qingfang2020-06-041-0/+65
| | | | | | | | | | | | | | | | | | | Currently, setting a bridge's self PVID to other value and deleting the default VID 1 renders untagged ports of that VLAN unable to talk to the CPU port: bridge vlan add dev br0 vid 2 pvid untagged self bridge vlan del dev br0 vid 1 self bridge vlan add dev sw0p0 vid 2 pvid untagged bridge vlan del dev sw0p0 vid 1 # br0 cannot send untagged frames out of sw0p0 anymore That is because the CPU port is set to security mode and its PVID is still 1, and untagged frames are dropped due to VLAN member violation. Set the CPU port to fallback mode so untagged frames can pass through. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips/mediatek: select kmod-mt7615-firmware where kmod-mt7615e is selectedFelix Fietkau2020-06-043-28/+29
| | | | | | | The new mt76 version splits out the firmware, because the driver can also be used for MT7663/MT7613 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix portability issue with perf on linux 5.4Felix Fietkau2020-06-041-3/+48
| | | | | | | Remove dependencies on core kernel headers in host tools used to build perf, which break on any non-linux system Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: rename Linksys Mamba WAN portDENG Qingfang2020-06-032-0/+26
| | | | | | Rename it to wan to match Linksys Armada 385 series Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: remove swconfig packageDENG Qingfang2020-06-031-2/+2
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* generic: backport mv88e6xxx port mirroring supportDENG Qingfang2020-06-034-0/+479
| | | | | | Backport port mirroring support for mv88e6xxx Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: drop 06_set_iface_mac preinit scriptDENG Qingfang2020-06-031-50/+0
| | | | | | | | MAC address is set in board.d script Interface swapping is not needed anymore as switching to DSA breaks previous configuration anyway Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: use ucidef to set up MAC addressDENG Qingfang2020-06-031-38/+75
| | | | | | Use ucidef to set up MAC address instead of preinit script Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: use eth0 as DSA CPU port for Linksys WRTDENG Qingfang2020-06-032-0/+54
| | | | | | | | eth0 has HW MAC address while eth2 does not. Use eth0 instead so we don't have to set LAN MAC manually. Disable unused eth2, until multi CPU port is supported. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: update default config for DSADENG Qingfang2020-06-032-11/+5
| | | | | | | | Update network/LED configuration for DSA driver. sysupgrade from images prior to this commit with config preserved will break the ethernet. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: remove swconfig symbols from kernel configDENG Qingfang2020-06-032-4/+0
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: drop swconfig patchesDENG Qingfang2020-06-036-182/+0
| | | | | | Drop swconfig patches for Clearfog and Linksys WRT Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: switch to kernel 5.4Adrian Schmutzler2020-06-031-1/+1
| | | | | | | | | Last reports with kernel 5.4 have all been positive [1], so let's open this to a wider range of testers. [1] https://github.com/openwrt/openwrt/pull/2804 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: vg-8050: fix WFI partition sizeÁlvaro Fernández Rojas2020-06-031-1/+1
| | | | | | Each image can take up to 0x3d60000, which means 128k more per image. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vr-3032u: fix WFI partition sizeÁlvaro Fernández Rojas2020-06-031-1/+1
| | | | | | Each image can take up to 0x3d60000, which means 128k more per image. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: bcm_wfi: always add img partitionsÁlvaro Fernández Rojas2020-06-031-9/+44
| | | | | | | | | This is useful when booting OpenWrt from ramdisks in order to have both images partitions defined. Furthermore, instead of always using img2 for the inactive image, let's use img1 or img2 accordingly. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ramips: mt7621: use higher SPI clock speed on Mikrotik rbm11g and rbm33gTobias Schramm2020-06-032-5/+3
| | | | | | | | | Previously the dts were using a value determined by empirical testing, because of a spi driver/clock bug. The bug was fixed quite some time ago. 33 MHz is the default clock frequency used by RouterBOOT and thus safe. Signed-off-by: Tobias Schramm <t.schramm@manjaro.org>
* bcm47xx: fix brcm-wl module loadingSungbo Eo2020-06-031-1/+2
| | | | | | | | | | | _dma_cache_wback_inv needs to be exported to load wl module successfully. root@OpenWrt:/# insmod wl [ 363.867779] wl: Unknown symbol _dma_cache_wback_inv (err -2) failed to insert /lib/modules/5.4.40/wl.ko Signed-off-by: Sungbo Eo <mans0n@gorani.run> Cc: Rafał Miłecki <rafal@milecki.pl>
* octeontx: fix mcp251x can controllerTim Harvey2020-06-031-7/+24
| | | | | | | | | | | | | | | Update the can-mcp251x-convert-to-half-duplex-SPI patch to fix reception Some SPI host controllers such as the Cavium Thunder TX do not support full-duplex SPI. Using half-duplex transfers allows the driver to work with those host controllers. This patch fixes the fact that mcp251x_hw_rx_frame was still relying on a full-duplex transfer where bits were being shifted on MOSI at the same time as MISO. After splitting the transaction into a spi_write_then_read() care must be taken to ignore the first byte. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* octeontx: fix gpio irq requestTim Harvey2020-06-031-0/+46
| | | | | | | This fixes a regression in 5.4 that causes a crash when a driver requests an ARM GPIO for an IRQ. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* octeontx: refresh kernel 5.4 configTim Harvey2020-06-031-27/+2
| | | | | | refresh kernel config by running make kernel_menuconfig and saving changes Signed-off-by: Tim Harvey <tharvey@gateworks.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 07:41:02 +0000