aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* imx6: image: increase max ubifs file-system sizeTim Harvey2020-06-031-1/+1
| | | | | | The latest 2GiB NAND flash parts used by Gateworks ventana are 2K page-size. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* imx6: backport v5.8 imx6qdl-gw dt patchesTim Harvey2020-06-037-0/+455
| | | | | | | | | | | | - add fxos8700 support to GW52xx/GW53xx/GW54xx - add USB_OTG support to GW552x - add LSM9DS1 IMU support to GW560x - add LSM9DS1 IMU support to GW5904 - add CC1352 UART to GW5910 - add BCM4330 support to GW5910 - fix wlan regulator for GW5910 Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* kernel: add gpio-it87Florian Eckert2020-06-032-2/+2
| | | | | | | | | | | | | | | Since commit 910df3f06cc902ca2cb0ca8e963e9354c930df1a we have build in on all X86/64 platforms the gpio-it87 driver. Since this change I am getting the following error message on boot. > kern.err kernel: [ 1.009416] gpio_it87: no device I do not have this device on my system. To prevent the nonsensical message and the loading of the module I have added this as a package, so that it can be installed later or during image building. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Reviewed-by: Philip Prindeville <philipp@redfish-solutions.com>
* ath79: phy-ar7200-usb: do not print error on defered initJohann Neuhauser2020-06-032-4/+6
| | | | | | | | | | | This is only a cosmetic correction, as the driver works as expected. However, the error message confuses users about a missing reset definition. On a defered init we don't see the following error message now: [ 0.078292] ar7200-usb-phy usb-phy: phy reset is missing Tested-by: Lech Perczak <lech.perczak@gmail.com> Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de>
* mvebu: espressobin: fix SATA and USB 3.0 ports detectionTomasz Maciej Nowak2020-06-031-0/+53
| | | | | | | | | | | | | | | | | This commit removes changes from upstream commits: 8e18c8e58da6 arm64: dts: marvell: armada-3720-espressobin: declare SATA PHY property bd3d25b07342 arm64: dts: marvell: armada-37xx: link USB hosts with their PHYs For most boards which have factory bootloader this caused that devices connected to USB 3.0 and SATA port were not detected. For them to function users would need to upgrade the bootloader to version with ARM Trusted Firmware 2.1 or later. Unfortunately there is no official bootloader image with updated ATF component, therefore drop these properties from nodes. This change was also tested briefly with bootloader with updated ATF and the ports functioned properly. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* ipq806x: enable disk-activity LED triggerThomas Albers2020-06-032-0/+2
| | | | | | | | | Enable the disk-activity LED trigger for ipq806x, since this SoC has an onboard SATA controller. Signed-off-by: Thomas Albers <thomas.gameiro@googlemail.com> [split into separate commit] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* linux/generic: remove obsolete config option LEDS_TRIGGER_IDE_DISKThomas Albers2020-06-033-3/+0
| | | | | | | | | | | | | Kernel config option LEDS_TRIGGER_IDE_DISK was renamed in kernel 4.8 to CONFIG_LEDS_TRIGGER_DISK in upstream commit eb25cb9956cc ("leds: convert IDE trigger to common disk trigger"). Removing it as it should be added only on targets which has usage for this trigger. Signed-off-by: Thomas Albers <thomas.gameiro@googlemail.com> [commit description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add kmod-usb-dwc2 to ZyXEL Keenetic imageAlexey Dobrovolsky2020-06-031-1/+2
| | | | | | | | | | ZyXEL Keenetic has a USB port. Thus, DWC2 USB controller driver should be in the default image for this device. Fixes: a7cbf59e0e04 ("ramips: add new device ZyXEL Keenetic as kn") Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: remove patches for USB-dwc2Alexey Dobrovolsky2020-06-032-58/+0
| | | | | | | | | | | | | | In FS#2738 we can see that patch first introduced in e8ebcff ("ramips: add a explicit reset to dwc2") breaks USB functionality since 18.06. Thus, this patch should be removed. Removed: - 0032-USB-dwc2-add-device_reset.patch Fixes: FS#2738 Fixes: FS#2964 Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com>
* apm821xx: set DEVICE_TYPE to "nas" for sata subtargetAdrian Schmutzler2020-06-031-0/+1
| | | | | | | | | | | | | | | | Since DEVICE_TYPE cannot be set per device, just set DEVICE_TYPE to "nas" for the entire subtarget, which only contains this single device. Note that while this looks like a cosmetic change in combination with the previous patches, this particular patch actually changes the packages for the device. Suggested-by: Christian Lamparter <chunkeey@gmail.com> Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: provide consistent basic DEVICE_TYPEAdrian Schmutzler2020-06-032-2/+2
| | | | | | | | | | | | | | | | | | | | | While the effective "default" based on frequent use is "router", the DEVICE_TYPE variable actually provides a "basic" configuration without selecting any additional packages. This is currently set up with the identifier "bootloader", which seems to be not used at all. However, the only targets not using "router" or "nas" are actually archs38 and arc770, which use their own value "developerboard" for DEVICE_TYPE which seems to have been invented when these targets where added. The latter is not implemented in target.mk, though, and will fall back to the "basic" set of packages then. So, to clean this up and make it more readable, let's just define a DEVICE_TYPE "basic" and use it for the aforementioned cases. Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: drop DEVICE_TYPE when used as device variableAdrian Schmutzler2020-06-033-4/+0
| | | | | | | | | | | | | | | | | | | | | | | DEVICE_TYPE is a target/subtarget variable, and it does not have any effect when set in a device definition. It can only be set in a target's or subtarget's Makefile. Consequently, having it set anyway is misleading, so this drops all cases. This effectively reverts the following commits: 7a1497fd601d ("apm821xx: MBL: set DEVICE_TYPE to NAS") 5b4765c93a1b ("gemini: Classify Raidsonic NAS IB-4220-B as a NAS") cdc6de460bb4 ("gemini: D-Link DNS-313 is a NAS") For the following commit, the variable was set when adding device support: 27b2f0fc0fc5 ("kirkwood: add support for Iomega Storcenter ix2-200") Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: lzma-loader: allow bigger ramdisksÁlvaro Fernández Rojas2020-06-032-4/+6
| | | | | | | | | | | | | | | | Some (older) CFEs are loaded at 0x80401000 and ramdisks are loaded at 0x80010000, which means that ramdisk size limit is 0x3F1000 (almost 4M). Therefore, current ramdisks (~4MB) are overwritting CFE in these devices, which results in a crash. This commit changes the address where ramdisks are loaded to 0x80a00000, which is the same address where kernel is loaded when booting from the flash. Therefore, lzma-loader will now be loaded at 0x80a00000, but it will still decompress the kernel at 0x80010000. Tested with huawei,hg556a-b, which has its CFE loaded at 0x80401000. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* malta: add missing symbols for kernel 5.4Daniel Golle2020-06-031-0/+2
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* bcm63xx: ad1018: remove cfe.bin image supportÁlvaro Fernández Rojas2020-06-032-27/+1
| | | | | | | | | | | | Apparently, Sercomm allows loading a BCM WFI image via CFE, but this image destroys "serial" and "protect" nand partitions, which is wrong. It will also set both bootflags to the same value, which causes booting issues with cferam (cferom will alternatively boot from cferam1 or cferam2 each time the device is rebooted). Now that OEM Sercomm images are supported it's time to remove this hacky cfe.bin image support. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: add missing partitionsÁlvaro Fernández Rojas2020-06-031-0/+12
| | | | | | This partitions were missing when support for this device was added. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: stop using legacy lzma for all devicesÁlvaro Fernández Rojas2020-06-031-54/+59
| | | | | | | | | BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vg-8050: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-022-6/+6
| | | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Also fix hsspi address warning. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vr-3032u: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-022-3/+3
| | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: order devices alphabeticallyÁlvaro Fernández Rojas2020-06-021-10/+10
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: add CFE_WFI_VERSION values for each deviceÁlvaro Fernández Rojas2020-06-021-1/+5
| | | | | | CFE_WFI_VERSION should be defined per device instead of using a generic value. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: support Broadcom WFI bootflagsÁlvaro Fernández Rojas2020-06-021-0/+110
| | | | | | | | When firmware is flashed, cferam.000 extension is renamed to the next number. When booting, CFE scans the NAND and picks the partition with the highest cferam extension and ignores the other one. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 22:30:24 +0000