aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: Fix typo in wan LED color of gl-mifiReto Schneider2018-04-041-1/+1
| | | | | | | | | It was wrong from the beginning and the trigger for the wan led was never set due to the typo. Signed-off-by: Reto Schneider <code@reto-schneider.ch> [add commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: fix vr9 reboot maskMathias Kresin2018-04-041-1/+1
| | | | | | | We need to reset the GPHYs on reboot as well. Otherwise the bootloader might have issues to reset/find the GPHYs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for DLINK DWR-921-C3Pawel Dembicki2018-04-041-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The DWR-921-C3 Wireless Routers with LTE embedded modem is based on the MT7620N SoC. Specification: * MediaTek MT7620N (580 Mhz) * 64 MB of RAM * 16 MB of FLASH * 802.11bgn radio * 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN) * 2x external, detachable (LTE) antennas * UART header on PCB (57600 8n1) * 6x LED (GPIO-controlled) * 1x bi-color Signal Strength LED (GPIO-controlled) * 2x button * JBOOT bootloader Installation: Apply factory image via d-link http web-gui. How to revert to OEM firmware: 1.) Push the reset button and turn on the power. Wait until LED start blinking (~10sec.) 2.) Upload original factory image via JBOOT http (IP: 192.168.123.254) 3.) If http doesn't work, it can be done with curl command: curl -F FN=@XXXXX.bin http://192.168.123.254/upg where XXXXX.bin is name of firmware file. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: add support for DLINK DWR-921-C1Giuseppe Lippolis2018-04-047-3/+175
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The DWR-921-C1 Wireless Routers with LTE embedded modem is based on the MT7620N SoC. Specification: * MediaTek MT7620N (580 Mhz) * 64 MB of RAM * 16 MB of FLASH * 802.11bgn radio * 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN) * 2x external, detachable (LTE) antennas * UART header on PCB (57600 8n1) * 6x LED (GPIO-controlled) * 1x bi-color Signal Strength LED (GPIO-controlled) * 2x button * JBOOT bootloader The status led has been assigned to the dwr-921-c1:green:sigstrength (lte signal strength) led. At the end of the boot it is switched off and is available for lte operation. Work correctly also during sysupgrade operation. Installation: Apply factory image via d-link http web-gui. How to revert to OEM firmware: 1.) Push the reset button and turn on the power. Wait until LED start blinking (~10sec.) 2.) Upload original factory image via JBOOT http (IP: 192.168.123.254) 3.) If http doesn't work, it can be done with curl command: curl -F FN=@XXXXX.bin http://192.168.123.254/upg where XXXXX.bin is name of firmware file. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: add BroadMobi BM806U lte-modem supportPawel Dembicki2018-04-042-0/+56
| | | | | | | Backport patch which adds suport for the BroadMobi BM806U 3G/4G modem, which is used in D-Link DWR-921 C3. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: add wistron neweb d18q1 lte-modem supportGiuseppe Lippolis2018-04-042-0/+122
| | | | | | | Backport patch which adds suport for the Wistron NeWeb d18q1 LTE modem which is used in D-Link DWR-921 C1. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: mt7620: eMMC: fix compiler warnings in non-debug modeAndré Draszik2018-04-042-40/+26
| | | | | | | | | | | drivers/mmc/host/mtk-mmc/dbg.c:51:13: warning: 'cmd_buf' defined but not used [-Wunused-variable] static char cmd_buf[256]; ^~~~~~~ In addition, msdc_reg[] is completely unused, even in debug mode. Signed-off-by: André Draszik <git@andred.net>
* ramips: mt7620: eMMC: remove unused variableAndré Draszik2018-04-042-8/+2
| | | | | | | | msdc_6575_host[] is unused, just remove it. Also, it was the source of memory corruption up until the previous fix to this driver. Signed-off-by: André Draszik <git@andred.net>
* ramips: mt7620: eMMC: stop invalid memory access if only one device is definedAndré Draszik2018-04-042-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | pdev->id is -1 when only one device exists, and is used: * as an index into drv_mode[] to determine whether to use PIO or DMA mode (via host->id) * as an index into msdc_6575_host[], to store the mmc_priv() data. Obviously, -1 is not a valid index in either case, causing us to read invalid memory, and memory corruption, respectively. The invalid memory read is causing non-deterministic behaviour, in particular in the v4.4 kernel it still picked DMA mode, but in the v4.9 it now always picks PIO mode. Also, PIO mode doesn't work, causing the following: / # echo 3 > /proc/sys/vm/drop_caches [ 3845.249237] sh (128): drop_caches: 3 / # /root/usr/lib/libc.so [ 3846.096070] do_page_fault(): sending SIGSEGV to libc.so for invalid read access from 7f9cb5a0 [ 3846.104758] epc = 779b0ea4 in libc.so[7792f000+c3000] [ 3846.109907] ra = 779a8004 in libc.so[7792f000+c3000] Segmentation fault / # /root/usr/lib/libc.so musl libc (mipsel-sf) Version 1.1.16-git-40-g54807d47 Dynamic Program Loader Usage: /root/usr/lib/libc.so [options] [--] pathname [args] (i.e. initial page-in of any binary causes a segfault, subsequent access works.) While this change doesn't fix PIO mode, it at least makes us deterministically use DMA (which works), and it also stops us from corrupting memory. Signed-off-by: André Draszik <git@andred.net>
* ramips: mt7620: eMMC: fix MODULE_DEVICE_TABLEAndré Draszik2018-04-042-2/+2
| | | | | | | This was referencing an undefined symbol, probably due to copy/paste error. Signed-off-by: André Draszik <git@andred.net>
* ramips: mt7620: eMMC: fix compiler warning (misleading indentation)André Draszik2018-04-042-8/+8
| | | | | | | | | | | drivers/mmc/host/mtk-mmc/sd.c:2782:5: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if ((hw->flags & MSDC_SDIO_IRQ) || (hw->flags & MSDC_EXT_SDIO_IRQ)) ^~ drivers/mmc/host/mtk-mmc/sd.c:2785:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if' cd_active_low = !of_property_read_bool(pdev->dev.of_node, "mediatek,cd-high"); ^~~~~~~~~~~~~ Signed-off-by: André Draszik <git@andred.net>
* ramips: mt7620: eMMC: clear owner fieldAndré Draszik2018-04-042-4/+2
| | | | | | | a) This is not needed in recent kernels anymore (> 3.x ??) b) this allows driver unloading now Signed-off-by: André Draszik <git@andred.net>
* kernel: update kernel 4.14 to 4.14.32Hauke Mehrtens2018-04-0316-121/+31
| | | | | | | | | | | | | The following patches are now included upstream: * 0052-MIPS-lantiq-fix-usb-clocks.patch * 0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch * 0060-lantiq-ase-enable-MFD-SYSCON.patch Closes: FS#1466 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: Add support for XM25QH64A and XM25QH128A SPI NOR flashHauke Mehrtens2018-04-032-0/+60
| | | | | | | | | | | | These devices are produced by Wuhan Xinxin Semiconductor Manufacturing Corp. (XMC) and found on some routers from Chinese manufactures. The data sheets can be found here: http://www.xmcwh.com/Uploads/2018-03-01/5a9799e4cb355.pdf http://www.xmcwh.com/Uploads/2018-02-05/5a77e6dbe968b.pdf Closes: FS#1460 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm47xx: add kernel 4.14 supportPaul Wassi2018-04-0323-1/+2686
| | | | | | | | | | | | | | Add patches for 4.14, drop patch 030 since it's already included upstream. Tested on: 1) WRT54GL (with RAM upgraded to 32 MiB) 2) WL500gPv2 (with RAM upgraded to 64 MiB) 3) BCM47186B0 SoC board 4) BCM4706 SoC board Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm47xx: add Luxul XAP-1500 and XWR-1750 WiFi LEDsRafał Miłecki2018-04-034-4/+176
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: update kernel 4.9 to version 4.9.91Hauke Mehrtens2018-03-3140-252/+142
| | | | | | | | | | * Refreshed patches. * Deleted 210-Revert-led-core-Fix-brightness-setting-when-setting-.patch (was accepted upstream) * Deleted 812-pci-dwc-fix-enumeration.patch (was accepted upstream) Compile and run tested on lantiq Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* pistachio: remove kernel 4.9 supportMatti Laakso2018-03-3121-3690/+0
| | | | Signed-off-by: Matti Laakso <matti.laakso@outlook.com>
* pistachio: Switch to kernel 4.14Matti Laakso2018-03-311-1/+1
| | | | Signed-off-by: Matti Laakso <matti.laakso@outlook.com>
* pistachio: add kernel 4.14 supportMatti Laakso2018-03-3117-0/+2442
| | | | | | Add patches and config for 4.14, refreshed from 4.9. Signed-off-by: Matti Laakso <matti.laakso@outlook.com>
* mvebu: add support for MACCHIATObin (cortex-a72)Damir Samardzic2018-03-319-3/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for Marvell MACCHIATObin, cortex-a72 based Marvell ARMADA 8040 Community board. Comes in two forms: Single Shot and Double Shot. Specifications: - Quad core Cortex-A72 (up to 2GHz) - DDR4 DIMM slot with optional ECC and single/dual chip select support - Dual 10GbE (1/2.5/10GbE) via copper or SFP 2.5GbE (1/2.5GbE) via SFP 1GbE via copper - SPI Flash - 3 X SATA 3.0 connectors - MicroSD connector - eMMC - PCI x4 3.0 slot - USB 2.0 Headers (Internal) - USB 3.0 connector - Console port (UART) over microUSB connector - 20-pin Connector for CPU JTAG debugger - 2 X UART Headers - 12V input via DC Jack - ATX type power connector - Form Factor: Mini-ITX (170 mm x 170 mm) More details at http://macchiatobin.net Booting from micro SD card: 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot with boot script: setenv bootcmd "load mmc 1:1 0x4d00000 boot.scr; source 0x4d00000" saveenv or manually: setenv fdt_name armada-8040-mcbin.dtb setenv image_name Image setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr $image_name;ext4load mmc 1:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr - $fdt_addr' saveenv Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* mvebu: clearfog-pro: set new DTB name in boot-scriptJosua Mayer2018-03-311-0/+4
| | | | | | | The DTB for Clearfog Pro has been renamed in mainline. However U-Boot hasn't picked up that change yet :(, so we need to hardcode it for now. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: Add support for WRT3200ACM with new NAND flashImre Kaloz2018-03-315-2/+23
| | | | | | | | Newer Linksys boards might come with a Winbond W29N02GV which can be configured in different ways. Make sure we configure it the same way as the older chips so everything keeps working. Signed-off-by: Imre Kaloz <kaloz@openwrt.org>
* mvebu: Get rid of RTC hack for Turris Omnia.Rosen Penev2018-03-311-1/+1
| | | | | | As Solidrun's RTC patch got merged, this hack is no longer needed. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* kernel: add missing config optionHauke Mehrtens2018-03-301-0/+1
| | | | | | | | | CONFIG_NVMEM_BCM_OCOTP was added in kernel 4.10 and it is possible to activate it on the bcm53xx target. Deactivate it by default to fix the build of the bcm53xx target. This was found by build bot. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* apm821xx: increase WNDR4700's dtb+kernel partition to 3.5 MiBChristian Lamparter2018-03-302-23/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch cleans and reworks the WNDR4700 dts to increase the now combined dtb+kernel partition to 3.5 MiB. This has become necessary due to the switch to GCC 7.3 and the ever increasing kernel binary size. The dtb+kernel partition was combined in order to finally fix the problem with out-of-sync device-trees. From now on, the kernel and device-tree will always be updated together. Upgrade Note: Existing installations will have to use the TFTP firmware recovery option in order to install the update. Affected users are advised to make a backup of their existing configuration prior to running sysupgrade: <https://openwrt.org/docs/guide-user/installation/generic.backup#backup_openwrt_configuration> Due to the repartitioning of the NAND, the generated backup should be placed on either the internal HDD, an attached USB-Stick or on another PC (externally). To manually trigger the firmware recovery, the reset button has to be pressed (and hold) during boot. U-boot will enter the "Upgrade Mode" and starts a tftpserver listening on 192.168.1.1 for a tftp client from one of the four LAN/Ethernet ports to connect and upload the new system: (enable tftp binary mode!). openwrt-apm821xx-nand-netgear_wndr4700-squashfs-factory.img Cc: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: switch MR24's initramfs to multi-image methodChristian Lamparter2018-03-301-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The recent change to switch to gcc 7.3 broke the image generation code, as the kernel would no longer fit into KERNEL_SIZE. This patch fixes the issue by reworking the initramfs creation and packaging, which will get rid of the KERNEL_SIZE check in the process. This new initramfs can be loaded through the MR24 U-boot in the following way: => setenv ipaddr 192.168.1.1 => setenv bootargs console=ttyS0,$baudrate => tftpboot c00000 192.168.1.2:meraki_mr24-initramfs-kernel.bin [...] Load address: 0xc00000 Loading: ################################################ [...] done Bytes transferred = 5952544 (5ad420 hex) => bootm $fileaddr \## Booting kernel from Legacy Image at 00c00000 ... ... For more information and the latest flashing guide: please visit the OpenWrt Wiki Page for the MR24: <https://openwrt.org/toh/meraki/mr24#flashing> Cc: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* bcm53xx: switch to kernel 4.14Rafał Miłecki2018-03-291-1/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: update kernel 4.14 configRafał Miłecki2018-03-291-7/+34
| | | | | | | | | | | There are few symbol changes but only 3 symbols were possible to set: THERMAL_EMERGENCY_POWEROFF_DELAY_MS CLK_BCM_SR PHY_NS2_USB_DRD Both new drivers don't seem to apply to Northstar so they are disabled. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: fix earlycon regression in kernel 4.14Rafał Miłecki2018-03-291-0/+33
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: fix ar934x usb controller resource conflictFelix Fietkau2018-03-281-1/+1
| | | | | | Use the right size for the EHCI block Signed-off-by: Felix Fietkau <nbd@nbd.name>
* sunxi: add build for sopineFan Fan2018-03-231-0/+10
| | | | | | This will generate image for Pine64 Sopine board. Signed-off-by: Fan Fan <fkpwolf@gmail.com>
* Kernel: bump 4.14 to 4.14.29Stijn Segers2018-03-2319-80/+80
| | | | | | | | | | | | Right patch version this time, sorry! * Patch 180-usb-xhci-add-support-for-performing-fake-doorbell.patch had to be adjusted slightly because of upstream adapted code. * Refreshed patches. Compile-tested: ramips/mt7621, x86/64 Run-tested: ramips/mt7621, x86/64 Signed-off-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Rosen Penev <rosenp@gmail.com>
* ramips: remove dead (and potentially crashy) code in mt7621 gsw initFelix Fietkau2018-03-231-11/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: rename ethernet priv->device field to dev to match upstreamFelix Fietkau2018-03-237-26/+26
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: netfilter: fix dst entries in flowtable offloadFelix Fietkau2018-03-232-11/+111
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix crash in flow offload when removing net devicesFelix Fietkau2018-03-231-3/+5
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: flow-offload: only offload connections that have been fully establishedFelix Fietkau2018-03-231-1/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: intel-xway: add vr9 v1.1 phy supportMathias Kresin2018-03-234-0/+264
| | | | | | | | | | | | During upstreaming the intel phy driver, support for the vr9 v1.1 embedded phys got lost. Backport the upstream send patch adding support for the vr9 v1.1 embbeded phys to the driver. Signed-off-by: Mathias Kresin <dev@kresin.me> cosmetic fixes Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix switch and MAC address for WHR-G300NINAGAKI Hiroshi2018-03-232-1/+7
| | | | | | | | | | | | WHR-G300N has 5 ethernet ports (lan: 4, wan: 1), but there was no correct configuration in 02_network script and 6 ports was configured on the switch. Also, since the MAC address was not acquired from factory partition, incorrect values was set to LAN and WAN interfaces. This commit fixes these issues. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ipq40xx: Add reserved memory for WPJ428Sven Eckelmann2018-03-231-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The APPSBL and anything after that it not allowed to touch some of the memory regions which are used by other components. Still trying to write to the memory can lead to sudden device restarts (IPQ40xx) # mw 87e80000 0 data abort pc : [<873149f8>] lr : [<87308578>] sp : 86edfc28 ip : 86ef4412 fp : 00000000 r10: 00000000 r9 : 00000000 r8 : 86edff68 r7 : 00000003 r6 : 8737e624 r5 : 86ef4420 r4 : 8736c154 r3 : 00000000 r2 : 00000010 r1 : 00000000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... The device manufacturer only provided a very rough list of regions: * rsvd1: 0x87000000 0x500000 * wifi_dump: 0x87500000 0x600000 * rsvd2: 0x87b00000 0x500000 A more detailed list for devices using the AP.DK reference design memory maps was provided by Roman Yeryomin <roman@advem.lv> in commit 56f2df879fd ("ipq806x: ipq4019: add ap-dk01.1-c1 board support"): * apps_bl: 0x87000000 0x400000 * sbl: 0x87400000 0x100000 * cnss_debug: 0x87500000 0x600000 * cpu_context_dump: 0x87b00000 0x080000 * tz_apps: 0x87b80000 0x280000 * smem: 0x87e00000 0x080000 * tz: 0x87e80000 0x180000 The u-boot function ipq_fdt_mem_rsvd_fixup seems to suggest that only the rsvd2 (tz_apps, smem, tz) should be protected. All other regions would have been removed by it when CONFIG_QCA_APPSBL_DLOAD is not enabled. This allows to reduce the 16MB reserved memory region to only 4.5MB. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Use detailed reserved memory for A42Sven Eckelmann2018-03-231-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The APPSBL and anything after that it not allowed to touch some of the memory regions which are used by other components. Still trying to write to the memory can lead to sudden device restarts (IPQ40xx) # mw 87e80000 0 data abort pc : [<873149f8>] lr : [<87308578>] sp : 86edfc28 ip : 86ef4412 fp : 00000000 r10: 00000000 r9 : 00000000 r8 : 86edff68 r7 : 00000003 r6 : 8737e624 r5 : 86ef4420 r4 : 8736c154 r3 : 00000000 r2 : 00000010 r1 : 00000000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... The device manufacturer only provided a very rough list of regions: * rsvd1: 0x87000000 0x500000 * wifi_dump: 0x87500000 0x600000 * rsvd2: 0x87b00000 0x500000 A more detailed list for devices using the AP.DK reference design memory maps was provided by Roman Yeryomin <roman@advem.lv> in commit 56f2df879fd ("ipq806x: ipq4019: add ap-dk01.1-c1 board support"): * apps_bl: 0x87000000 0x400000 * sbl: 0x87400000 0x100000 * cnss_debug: 0x87500000 0x600000 * cpu_context_dump: 0x87b00000 0x080000 * tz_apps: 0x87b80000 0x280000 * smem: 0x87e00000 0x080000 * tz: 0x87e80000 0x180000 The u-boot function ipq_fdt_mem_rsvd_fixup seems to suggest that only the rsvd2 (tz_apps, smem, tz) should be protected. All other regions would have been removed by it when CONFIG_QCA_APPSBL_DLOAD is not enabled. This allows to reduce the 16MB reserved memory region to only 4.5MB. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Remove phy reset gpio from Cisco Meraki MR33Sven Eckelmann2018-03-231-1/+0
| | | | | | | | There is currently no code to read the phy reset gpios for the ethernet PHY. It would also have been better to use the more common name "phy-reset-gpios" for this property. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ipq40xx: Adjust SoC name of AVM Fritz!Box 4040Sven Eckelmann2018-03-233-2/+2
| | | | | | | The AVM Fritz!Box 4040 uses an IPQ4018 as SoC and not an IPQ4019. The DTS must be adjusted to reflect this. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ipq40xx: Use constant to set gpio active low/highSven Eckelmann2018-03-237-8/+9
| | | | | | | | | The GPIO configuration in the DTS have as third parameter the active low/high configuration. This parameter is not easy to parse by humans when it is only set to 0/1. It is better to use the predefined constants GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Fix DTS status parameter valuesSven Eckelmann2018-03-234-47/+47
| | | | | | | | The "Devicetree Specification, Release v0.2 - 2.3.4 status" [1] only allows the "okay" value for an operational device. The "ok" value will be accepted by the kernel but should be avoided. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Provide prefered DTS config name for A42Sven Eckelmann2018-03-231-0/+1
| | | | | | | | The OpenMesh A42 will use the default config entry in the FIT when no other on is found but prefers the config@om.a42. This only becomes relevant when a Multi-FIT image is prepared for this device. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Remove SUPPORTED_DEVICES for A42Sven Eckelmann2018-03-231-1/+0
| | | | | | | The SUPPORTED_DEVICES will be defined automatically via Device/Default in ipq40xx. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* kernel: fix offloading connections with SNAT + DNATFelix Fietkau2018-03-231-0/+23
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix flow offload UDP handling issueFelix Fietkau2018-03-231-0/+48
| | | | | | Only run the TCP state check for TCP connections Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 03:04:06 +0000