aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ramips: mt7621: fix 5GHz WiFi LED on ZBT WG3526Andreas Ziegler2019-01-211-0/+4
| | | | | | | This fixes the 5GHz WiFi LED which was previously not working. Signed-off-by: Andreas Ziegler <dev@andreas-ziegler.de> (cherry picked from commit d492da702a2118b34ced9772586c5a6de68e70fd)
* kernel: bump 4.14 to 4.14.93Koen Vandeputte2019-01-1517-110/+55
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 510-f2fs-fix-sanity_check_raw_super-on-big-endian-machines.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.150Koen Vandeputte2019-01-1517-99/+44
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 510-f2fs-fix-sanity_check_raw_super-on-big-endian-machines.patch Altered patches: - 024-7-net-reorganize-struct-sock-for-better-data-locality.patch Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* octeon: fix typo in platform.shHans Dedecker2019-01-131-1/+1
| | | | | | Fix upgrade typo Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* cns3xxx: use actual size reads for PCIeKoen Vandeputte2019-01-082-0/+102
| | | | | | | | | | | | | | | | | | | upstream commit 802b7c06adc7 ("ARM: cns3xxx: Convert PCI to use generic config accessors") reimplemented cns3xxx_pci_read_config() using pci_generic_config_read32(), which preserved the property of only doing 32-bit reads. It also replaced cns3xxx_pci_write_config() with pci_generic_config_write(), so it changed writes from always being 32 bits to being the actual size, which works just fine. Due to: - The documentation does not mention that only 32 bit access is allowed. - Writes are already executed using the actual size - Extensive testing shows that 8b, 16b and 32b reads work as intended It makes perfectly sense to also swap 32 bit reading in favor of actual size. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.91Koen Vandeputte2019-01-088-107/+14
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 902-debloat_proc.patch Removed upstreamed: - 500-ubifs-Handle-re-linking-of-inodes-correctly-while-re.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.148Koen Vandeputte2019-01-083-12/+8
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 902-debloat_proc.patch Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* apm821xx: switch MX60(W)'s recovery images to multi-image methodChristian Lamparter2019-01-011-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past, the MX60(W)'s recovery images always had problems with the size restriction and never really worked without manual intervention. This patch reworks the initramfs, which allows the device to ease up on the impossible tight kernel size requirements for the initramfs image. This new initramfs can be loaded through the MX60(W) U-boot in the following way: => setenv bootargs console=ttyS0,$baudrate => tftpboot $meraki_loadaddr meraki_mx60-initramfs-kernel.bin [...] Load address: 0x800000 Loading: ################################################ [...] done [...] => bootm $fileaddr \## Booting kernel from Legacy Image at 00800000 ... ... For more information and the latest flashing guide: please visit the OpenWrt Wiki Page for the MX60(W): <https://openwrt.org/toh/meraki/mx60#flashing> Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 36c19c9f0be23ad327085aa762e95de638e19b4a)
* kernel: fix f2fs on big endian machinesChristian Lamparter2019-01-012-0/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The WD MyBook Live SquashFS images didn't work anymore due to a upstream regression in f2fs commit: 0cfe75c5b01199 ("f2fs: enhance sanity_check_raw_super() to avoid potential overflows") that got backported to 4.14.86 and 4.9.144. by Martin Blumenstingl: |Treat "block_count" from struct f2fs_super_block as 64-bit little endian |value in sanity_check_raw_super() because struct f2fs_super_block |declares "block_count" as "__le64". | |This fixes a bug where the superblock validation fails on big endian |devices with the following error: | F2FS-fs (sda1): Wrong segment_count / block_count (61439 > 0) | F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock | F2FS-fs (sda1): Wrong segment_count / block_count (61439 > 0) | F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock |As result of this the partition cannot be mounted. | |With this patch applied the superblock validation works fine and the |partition can be mounted again: | F2FS-fs (sda1): Mounted with checkpoint version = 7c84 | |My little endian x86-64 hardware was able to mount the partition without |this fix. |To confirm that mounting f2fs filesystems works on big endian machines |again I tested this on a 32-bit MIPS big endian (lantiq) device. Hopefully, this will do until Martin's patch moved through upstream to -stable. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: backport DTS changes queued for the 4.21Rafał Miłecki2018-12-279-5/+241
| | | | | | | It just replaces some downstream patches & adds relicensing work. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 7a7d19abcfc56c5073931e81f481e2e1fdf774c2)
* bcm53xx: rename dts backport patches changing their prefixesRafał Miłecki2018-12-2716-0/+0
| | | | | | | | Start 03x with 030 instead of 035. It's a trivial change that adds more place for further backports in the 03x space. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a5d6f2eb76a549af9e5e186042ab6bf2371be725)
* bcm53xx: update pinctrl driver & use its new DT bindingRafał Miłecki2018-12-252-0/+130
| | | | | | | | Driver has been updated upstream to support more precise DT binding and avoid mapping conflicts between pinctrl and USB 2.0 PHY. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a28f6ab27f9ae1a08c6945013cdb796b12ce150d)
* x86: make sysupgrade.tgz reachable againTomasz Maciej Nowak2018-12-181-1/+1
| | | | | | | | | | Moving binding mount before check for saved sysupgrade configuration made it unreachable. Fix it by moving binding mount after the check. Fixes: f78b2616 (x86: mount writable bootfs) Reported-by: Lucian Cristian <luci@powerneth.ro> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (backported from c288ad9c2b2a4ab62e4c887f13f220870911cc28)
* x86: add packages files to image bootfsTomasz Maciej Nowak2018-12-181-0/+2
| | | | | | | | Add files to bootfs image from selected as built-in packages, which want to install files to targets boot file system. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (backported from 51e199fbe80acb6e95dff942280b0396e094032b)
* x86: mount writable bootfsTomasz Maciej Nowak2018-12-181-8/+4
| | | | | | | | Mount boot file system with rw option to allow installation of packages which install files to /boot directory. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (backported from f78b26163790fdf2b53464ab808af10f72e31c3e)
* lantiq/basefiles: use shutdown instead of stop when the system goes downMartin Schiller2018-12-181-1/+1
| | | | | | | I can't see any reason why we shouldn't use shutdown for lantiq as well. Signed-off-by: Martin Schiller <ms@dev.tdt.de> (backported from 18398abe1eb5de50b3d8affd51e003bf7555d91a)
* kernel: support gcc-optimized inlining on all architecturesFelix Fietkau2018-12-186-2/+143
| | | | | | | | | | | Optimized inlining was disabled by default when gcc 4 was still relatively new. By now, all gcc versions handle this well and there seems to be no real reason to keep it x86-only. Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from 1e8882585c6f4a5e7f5e2b4f18cd550aafa6f81d) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* cns3xxx: fix writing to wrong PCI registersKoen Vandeputte2018-12-182-0/+158
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally, cns3xxx used it's own functions for mapping, reading and writing registers. Upstream commit 802b7c06adc7 ("ARM: cns3xxx: Convert PCI to use generic config accessors") removed the internal PCI config write function in favor of the generic one: cns3xxx_pci_write_config() --> pci_generic_config_write() cns3xxx_pci_write_config() expected aligned addresses, being produced by cns3xxx_pci_map_bus() while the generic one pci_generic_config_write() actually expects the real address as both the function and hardware are capable of byte-aligned writes. This currently leads to pci_generic_config_write() writing to the wrong registers on some ocasions. First issue seen due to this: - driver ath9k gets loaded - The driver wants to write value 0xA8 to register PCI_LATENCY_TIMER, located at 0x0D - cns3xxx_pci_map_bus() aligns the address to 0x0C - pci_generic_config_write() effectively writes 0xA8 into register 0x0C (CACHE_LINE_SIZE) This seems to cause some slight instability when certain PCI devices are used. Another issue example caused by this this is the PCI bus numbering, where the primary bus is higher than the secondary, which is impossible. Before: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=02, secondary=01, subordinate=ff, sec-latency=0 After fix: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 And very likely some more .. Fix all by omitting the alignment being done in the mapping function. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.89Koen Vandeputte2018-12-1831-149/+149
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.146Koen Vandeputte2018-12-182-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: Activate VDSO on MIPS againHauke Mehrtens2018-12-181-23/+0
| | | | | | | | The cache coloring problem on MIPS CPUs was fixed with kernel 4.9.129 of the kernel 4.9 branch. Activate VDSO support for MIPS again. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (backported from 91a71804f89a238082904ae027fffb52114e3499)
* kernel: re-enable MIPS VDSOKevin Darbyshire-Bryant2018-12-181-23/+0
| | | | | | | | | | | | | | | kernel upstream commit 9efcaa7c4afba5628f2650a76f69c798f47eeb18 to 4.14 itself a backport of 0f02cfbc3d9e413d450d8d0fd660077c23f67eff has resolved the cache line issues that led to us disabling VDSO by default on MIPS. Remove our force disable patch: pending-4.14/206-mips-disable-vdso.patch Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Acked-by: Hauke Mehrtens <hauke@hauke-m.de> (backported from 8ee7a80d190b291e828cace3cac8c485f3b8667d)
* kernel: fix build of nftablesHauke Mehrtens2018-12-181-0/+67
| | | | | | | | | Backport an additional patch from 4.16 for nftables. This fixes a build problem recently introduced. Fixes: f57806b56e5 ("kernel: generic: Fix nftables inet table breakage") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (backported from efffba34097ff75d12365fb863621d893f974623)
* kernel: generic: Fix nftables inet table breakageBrett Mastbergen2018-12-1831-42/+1230
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit b7265c59ab7d ("kernel: backport a series of netfilter cleanup patches to 4.14") added patch 302-netfilter-nf_tables_inet-don-t-use- multihook-infrast.patch. That patch switches the netfilter core in the kernel to use the new native NFPROTO_INET support. Unfortunately, the new native NFPROTO_INET support does not exist in 4.14 and was not backported along with this patchset. As such, nftables inet tables never see any traffic. As an example the following nft counter rule should increment for every packet coming into the box, but never will: nft add table inet foo nft add chain inet foo bar { type filter hook input priority 0\; } nft add rule inet foo bar counter This commit pulls in the required backport patches to add the new native NFPROTO_INET support, and thus restore nftables inet table functionality. Tested on Turris Omnia (mvebu) Fixes: b7265c59ab7d ("kernel: backport a series of netfilter cleanup ...") Signed-off-by: Brett Mastbergen <bmastbergen@untangle.com> (backported from f57806b56e5f6ca7bb9fb66d5b175b5f98ece93c) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* brcm47xx: Enable USB power on WNDR3400v3Tuomas Tynkkynen2018-12-181-0/+39
| | | | | | | | WNDR3400v3 needs GPIO 21 pulled high to enable power to USB ports. Add a kernel patch to do that. Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi> (backported from 5dd745588edea19846b2bc3a2e6938f139374ea9)
* x86/64: enable X86_INTEL_LPSS to select PINCTRLMartin Schiller2018-12-181-1/+10
| | | | | | | | This makes it possible to use the MCP23S08 i/o expander on x86_64 platforms with linux 4.14. Signed-off-by: Martin Schiller <ms@dev.tdt.de> (backported from 17f30bfcf7329c1770dc996b0d29934942bb2899)
* x86: geode: Add missing config optionsHauke Mehrtens2018-12-181-2/+2
| | | | | | | | | This adds a configuration options which is needed now. Without this patch the geode build will fail. Fixes: 4eda2fddf2 ("x86/geode: enable X86_INTEL_LPSS to select PINCTRL") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (backported from 0f2787b9ff6976cf4999ed2dbb7debdb53bac2e3)
* x86/geode: enable X86_INTEL_LPSS to select PINCTRLMartin Schiller2018-12-181-1/+10
| | | | | | | | This makes it possible to use the MCP23S08 i/o expander on geode platforms with linux 4.14. Signed-off-by: Martin Schiller <ms@dev.tdt.de> (backported from 4eda2fddf2995c8ade2b1e0faddc8ce1f1e0ec5f)
* x86: add UHCI and XHCI USB host drivers to 4.14Alex Maclean2018-12-181-1/+5
| | | | | | | | | | | Without UHCI a non-trivial number of machines will have no keyboard without BIOS assistance. Add XHCI as well in case there are chipsets which don't support legacy interfaces, and support PCI OHCI controllers also. Signed-off-by: Alex Maclean <monkeh@monkeh.net> (backported from 894a95fa2df9467afe559c899af741a0c9040953)
* bcm53xx: exit if writing kernel during sysupgrade failsRafał Miłecki2018-12-181-2/+2
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (backported from 93cc44c433fed754bd76f8016a1660a6b932361e)
* kernel: don't auto attach ubi on read errorMathias Kresin2018-12-182-10/+20
| | | | | | | | | | | | | | | With a10a204aab26cc ("kernel: make ubi auto-attach check for a tar file magic") the check for the magic was added without considering a failing mtd_read(). If the read fails, no check is done and the mount code is called straight away. Failing with an error message for such cases seems to me the cleaner way, as it would allow to spot hidden/workaround issues. Signed-off-by: Mathias Kresin <dev@kresin.me> (backported from 3716b5e4e6374883c80e61021923733b14cdb011) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: handle bad blocks in ubi auto attach codeMathias Kresin2018-12-182-8/+36
| | | | | | | | | | | | | The first block(s) of the ubi mtd device might be bad. We need to take care on our own to skip the bad block(s) and read the next one(s). Don't treat recoverable read errors as fatal and check for the UBI magic if the data of a block could be recovered using ECC or similar. Signed-off-by: Mathias Kresin <dev@kresin.me> (backported from 0ac91d82ed4d077150db902eb12d383c2be44fb2) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: improve ubi auto attach code readabilityMathias Kresin2018-12-182-52/+62
| | | | | | | | | | | | | | | | | Move the put_mtd_device() called on multiple error conditions to a goto label to use it later for more error conditions. The early return on failed open of the mtd device and mismatching mtd type allows to get rid of one level of indentation. By jumping to the cleanup code, a refcount bug is fixed for the wrong flash type condition. While at it, make clear that we only check for the UBI magic if the read from flash was successful. Signed-off-by: Mathias Kresin <dev@kresin.me> (backported from fdf6760cda15b2710287c66c9969a3ed527793d8) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: replace bridge port isolate hack with upstream patch backport on 4.14Felix Fietkau2018-12-184-82/+150
| | | | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from 21ee8ce9b52f8ae4a6babf4032f71e2d4d56392b) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: adjust bridge port isolate patch to match upstream attribute namingFelix Fietkau2018-12-182-4/+4
| | | | | | | | | Newer kernels have a patch that implements compatible functionality directly. Adjust the attribute of our own patch in preparation for dropping it later Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from 41a1c1af4bbf18cb5f3a4dfd1fb988317da9aa2d)
* ramips: fix wizfi630a swapped lan/wan portLev2018-12-181-1/+1
| | | | | | | | The order of the Ethernet ports were mixed up. This commit fixes the order to be aligned with the physical layout. Signed-off-by: Lev <leventelist@gmail.com> (backported from 3d6f57f3c6dabfe3911ffb1f1a2afbe3ff41c3fd)
* ramips: mt7621: fix mtu setting with kernel 4.14Mathias Kresin2018-12-181-11/+7
| | | | | | | | | | | Since kernel 4.10 commit 61e84623ace3 ("net: centralize net_device min/max MTU checking"), the range of mtu is [min_mtu, max_mtu], which is [68, 1500] by default. It's necessary to set a max_mtu if a mtu > 1500 is supported. Signed-off-by: Mathias Kresin <dev@kresin.me> (backported from 5da2c68d001ee44b15a58639ed03a0ebb6f68020)
* kernel: avoid flow offload for connections with xfrm on the dst entry ↵Felix Fietkau2018-12-182-3/+6
| | | | | | | | | (should fix IPSec) Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from b560c1748a4edf0d02046e5a988cc0caf1f4f987) (rebased patches) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: fix reboot with W25Q256 with 4-address-mode enabledDaniel Golle2018-12-181-0/+73
| | | | | | | | | | | | | | | | Some board vendors actually changed the loader to expect the chip to come up in 4-address-mode and flipped the ADP bit in the flash chip's configuration register which makes it come up in 4-address-mode. Hence it doesn't make sense to avoid switching to 4-address-mode on those boards but the opposite as otherwise reboot hangs eg. on the WrtNode2 boards. Fix this by checking the ADP register and only using SPI_NOR_4B_READ_OP on chips which have ADP==0 (come up in 3-byte mode). See also datasheet section 7.1.11 Power Up Address Mode (ADP) Fixes: 22d982ea0 ("ramips: add support for switching between 3-byte and 4-byte addressing on w25q256 flash") Signed-off-by: Daniel Golle <daniel@makrotopia.org> (backported from 8796680277f4b231386fbc6e8a1ccae91d9fcbe8)
* ar71xx: add support for UniFi-AC-Mesh-ProChristoph Krapp2018-12-155-8/+21
| | | | | | | | | | | | | | | | | This adds the build option for UniFi AC Mesh Pro as well as model detection for it. The device is a hardware clone of the AC Pro. - SoC: QCA9563-AL3A (775Mhz) - RAM: 128MiB - Flash: 16MiB - dual firmware partitions! - LAN: 2x 1000M - POE+ - Wireless: 2.4G: QCA9563 5G: UniFi Chip, QCA988X compatible Signed-off-by: Christoph Krapp <achterin@googlemail.com> (cherry picked from commit 987b961537b7002eda21df97dd8bfebe8882bc6d)
* kernel: bump 4.14 to 4.14.88Koen Vandeputte2018-12-145-10/+10
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 180-usb-xhci-add-support-for-performing-fake-doorbell.patch Fixes CVE: - CVE-2018-14625 Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.145Koen Vandeputte2018-12-149-13/+13
| | | | | | | | | | | | Refreshed all patches. Fixes CVE: - CVE-2018-14625 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.87Koen Vandeputte2018-12-132-3/+3
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.144Koen Vandeputte2018-12-131-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested: ar71xx Runtime-tested: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.86Koen Vandeputte2018-12-1319-41/+41
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 180-usb-xhci-add-support-for-performing-fake-doorbell.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.143Koen Vandeputte2018-12-1318-38/+46
| | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 950-0063-Improve-__copy_to_user-and-__copy_from_user-performa.patch - 950-0149-Update-vfpmodule.c.patch - 201-extra_optimization.patch New symbol: - CONFIG_HARDEN_BRANCH_PREDICTOR Compile-tested on: ar71xx, ar7, arc770, at91, brcm2708, brcm63xx, ixp4xx, lantiq, layerscape, mpc85xx, orion, rb532, uml Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: fix leds on GL.iNet GL-MT300N-V2Martin Weinelt2018-12-072-1/+2
| | | | | | | | The WAN LED now shows the link state. It's color is green, not blue. Signed-off-by: Martin Weinelt <hexa@darmstadt.ccc.de> (cherry picked from commit 0411813c6f0520dea23a1c4f58f5956c504bf129)
* ipq40xx: fix openmesh sysupgrade with tar content out of orderMarek Lindner2018-12-051-3/+3
| | | | | | | | | | | | The tar extraction depends on the order in which the files are added to the tar file. Since the order is not guaranteed and depends on the host system, the combined mtd write fails with sysupgrade images built on some systems. Fix by changing to tar file order independent mtd write. Fixes: 86e18f6706e1 ("ipq806x: add support for OpenMesh A42") Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch> Signed-off-by: Sven Eckelmann <sven@narfation.org>
* apm821xx: MBL: load kernel/dtb from SATA 0:1 firstFreddy Leitner2018-11-261-3/+3
| | | | | | | | | | | | | | | | | | | | | | This remedies an issue with the MBL Duo if both disks are inserted and contain OpenWrt. kernel and dtb would be loaded from SATA 1:1 while rootfs (/dev/sda2) would be mounted on SATA 0:1. Such a mix&match would obviously only work if both OpenWrt versions/ builds are identical, and especially fail after sysupgrade upgraded the system disk on SATA 0:1. The fallback to SATA 1:1 needs to be kept for MBL Single (only has SATA 1:1) and MBL Duo with one disk inserted on SATA 1:1. To speed up booting in those cases, the unneccesarily doubled "sata init" will only be called once. (In theory it could be omitted completely since the on-flash boot script already initializes SATA to load the on-disk boot script.) Tested on MBL Duo (all possible combination of disks) and MBL Single Signed-off-by: Freddy Leitner <hello@square.wf> Acked-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: wndr4700: restore sd-card media detectionChristian Lamparter2018-11-261-1/+1
| | | | | | | This was not converted to the new, dt-based board name. Fixes: e90dc8d2722 ("apm821xx: convert to device-tree board detection") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-04 08:15:15 +0000