aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ath79: fix dts of Teltonika RUT9xx devicesDaniel Golle2020-04-292-2/+2
| | | | | | The previous commits were missing a semicolon. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: add support for Teltonika RUT955 H7V3C0Daniel Golle2020-04-295-1/+219
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This board was previously supported in ar71xx as 'RUT9XX'. The difference between that and the other RUT955 board already supported in ath79 is that instead of the SPI shift registers driving the LEDs and digital outputs that model got an I2C GPIO expander instead. To support LEDs during early boot and interrupt-driven digital inputs, I2C support as well as support for PCA953x has to be built-in and cannot be kernel modules, hence select those symbols for ath79/generic. Specification: - 550/400/200 MHz (CPU/DDR/AHB) - 128 MB of RAM (DDR2) - 16 MB of FLASH (SPI NOR) - 4x 10/100 Mbps Ethernet, with passive PoE support on LAN1 - 2T2R 2,4 GHz (AR9344) - built-in 4G/3G module (example: Quectel EC-25EU) - internal microSD slot (spi-mmc, buggy and disabled for now) - RS232 on D-Sub9 port (Cypress ACM via USB, /dev/ttyACM0) - RS422/RS485 (AR934x high speed UART, /dev/ttyATH1) - analog 0-24V input (MCP3221) - various digital inputs and outputs incl. a relay - 11x LED (4 are driven by AR9344, 7 by PCA9539) - 2x miniSIM slot (can be swapped via GPIO) - 2x RP-SMA/F (Wi-Fi), 3x SMA/F (2x WWAN, GPS) - 1x button (reset) - DC jack for main power input (9-30 V) - debugging UART available on PCB edge connector Serial console (/dev/ttyS0) pinout: - RX: pin1 (square) on top side of the main PCB (AR9344 is on top) - TX: pin1 (square) on bottom side Flash instruction: Vendor firmware is based on OpenWrt CC release. Use the "factory" image directly in GUI (make sure to uncheck "keep settings") or in U-Boot web based recovery. To avoid any problems, make sure to first update vendor firmware to latest version - "factory" image was successfully tested on device running "RUT9XX_R_00.06.051" firmware and U-Boot "3.0.1". Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: split Teltonika RUT955 to support other RUT9xx modelsDaniel Golle2020-04-292-171/+198
| | | | | | | | | Split device-tree of Teltonika RUT955 into a generic RUT9xx part and a part specific to that version of RUT955 already supported. Also harmonize GPIO and LED names with what is used by the vendor firmware and assign RS485 DTR signal. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kirkwood: disable image for Linksys EA3500 (Audi)Adrian Schmutzler2020-04-291-0/+1
| | | | | | | | | | | Due to the switch to DSA, the kernel image has become too big (2641k) for the kernel partition (2624k) on this device: WARNING: Image file [...]/linux-kirkwood/linksys_audi-uImage is too big Disable the device until this is fixed, so buildbots can continue their work. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add SUPPORTED_DEVICES based on ar71xx for some devicesAdrian Schmutzler2020-04-282-0/+13
| | | | | | | | | This adds some still-missing board names for old TP-Link devices to ath79 SUPPORTED_DEVICES. Fixes: FS#3017 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* Revert "ramips: explicitly disable built-in switch for lan-only devices"Adrian Schmutzler2020-04-282-4/+0
| | | | | | | | | This reverts commit a1693bf626f8cd00363b0b98642b682522dfcf75. The rt288x and rt3883 devices in question don't have switches. Only keep the merged case for rt305x. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: remove support for kernel 4.19Adrian Schmutzler2020-04-2817-1759/+0
| | | | | | | | | | kirkwood has moved to DSA on 5.4, which will make kernel 4.14 and 4.19 support broken on the affected devices. Support on kernel 5.4 seems to have been running fine for almost 2 months on multiple devices, while support for 4.19 has never left testing state. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: remove support for kernel 4.14Adrian Schmutzler2020-04-2818-1818/+0
| | | | | | | | | | kirkwood has moved to DSA on 5.4, which will make kernel 4.14 and 4.19 support broken on the affected devices. Support on kernel 5.4 seems to have been running fine for almost 2 months on multiple devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: switch from swconfig to dsaPawel Dembicki2020-04-286-69/+68
| | | | | | | | | | | | | | | | | | | | | | This patch removes support for swconfig and switches to dsa driver. swconfig and switch drivers are removed. DSA driver is enabled and configuration is adjusted. In kirkwood only two devices have switches: Linksys EA3500 and EA4500. WAN MAC configuration in 02_network is required because otherwise WAN would have the same MAC address as lan interfaces. In swconfig solution the WAN address was assigned in u-Boot to eth1. Now, as eth1 is disabled and wan is part of the switch, we have to set it manually. Compile tested: EA3500, EA4500 Run tested: EA4500 Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [minor commit title/message adjustments, remove swconfig package for devices] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix MikroTik 750Gr3 ports MAC addressesDENG Qingfang2020-04-282-4/+9
| | | | | | | | | | | | | | | According to a user in OpenWrt forum, on RouterOS the MAC addresses are ether1(WAN) = MAC ether2(LAN2) = MAC+1 ether3(LAN3) = MAC+2 etc. Fix the MAC addresses in OpenWrt. Ref: https://forum.openwrt.org/t/few-dumb-question-about-mt7530-rb750gr3-dsa/61608 Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [remove label_mac in 02_network] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath10k-ct-firmware: rename ct-htt packagesÁlvaro Fernández Rojas2020-04-281-1/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* omap: remove support for kernel 4.14Andre Heider2020-04-281-740/+0
| | | | | | There's support for 5.4 and 4.19 now, remove the 3rd option. Signed-off-by: Andre Heider <a.heider@gmail.com>
* omap: switch to kernel 5.4Andre Heider2020-04-281-1/+1
| | | | | | | | Runtime tested on beagleblack. Signed-off-by: Andre Heider <a.heider@gmail.com> [added test comment] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* omap: make kernel_oldconfigAndre Heider2020-04-281-56/+52
| | | | | | Attempt to keep the same nand/sound/panel functionality using new knobs. Signed-off-by: Andre Heider <a.heider@gmail.com>
* omap: copy kernel 4.19 config for 5.4Andre Heider2020-04-281-0/+763
| | | | Signed-off-by: Andre Heider <a.heider@gmail.com>
* ath79: indicate boot/failsafe/upgrade for NanoBeam/Nanostation ACAdrian Schmutzler2020-04-272-2/+14
| | | | | | | | Like for Ubiquiti PowerBeam 5AC Gen2, the highest RSSI LED can be exploited to indicate boot/failsafe/upgrade for the NanoBeam AC and Nanostation AC as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Ubiquiti PowerBeam 5AC Gen2Roger Pueyo Centelles2020-04-275-2/+80
| | | | | | | | | | | | | | | | | | | | | | | | The Ubiquiti PowerBeam 5AC Gen 2 (PBE-5AC-Gen2) is an outdoor 802.11ac 5 GHz bridge with a radio feed and a dish antenna. The device is hardware-compatible with the LiteBeam AC Gen2, plus the 4 extra LEDs. Specifications: - SoC: Qualcomm Atheros AR9342 rev 2 - RAM: 64 MB DDR2 - Flash: 16 MB SPI NOR (mx25l12805d) - Ethernet: 1x 10/100/1000 Mbps Atheros 8035, 24 Vdc PoE-in - WiFi 5 GHz: QCA988x HW2.0 Ubiquiti target 0x4100016c chip_id 0x043222ff - WiFi 2.4 GHz: Atheros AR9340 (SoC-based) - Buttons: 1x (reset) - LEDs: 1x power, 1x Ethernet, 4x RSSI via GPIO. All blue. - UART: not tested Installation from stock airOS firmware: - Follow instructions for WA-type Ubiquiti devices on OpenWrt wiki Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [changed device name in commit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: rt3883: remove swconfig from individual DEVICE_PACKAGESAdrian Schmutzler2020-04-272-9/+6
| | | | | | | | | In rt3883 subtarget, several devices add swconfig to their DEVICE_PACKAGES. This is redundant as the package is already provided via DEFAULT_PACKAGES. Remove the redundant inclusions. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove (kmod-)swconfig DEVICE_PACKAGES for Sitecom WL-351Adrian Schmutzler2020-04-271-1/+1
| | | | | | | | These definitions are not required since swconfig is selected for the target anyway and kmod-swconfig is pulled as dependency by kmod-switch-rtl8366rb. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: explicitly disable built-in switch for lan-only devicesSungbo Eo2020-04-273-5/+5
| | | | | | | | | Commit 8f6334eb947a ("ramips: explicitly disable built-in switch when needed") did not fix rt288x and rt3883 devices. This patch deals with them. While at it, consolidate duplicate cases in interface setup. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: create common definition for I-O DATA NAND devicesAdrian Schmutzler2020-04-271-23/+11
| | | | | | | | Three of the I-O DATA devices with NAND flash share a lot of variables. Create a common definition for them to reduce duplicate code. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mediatek: fix compile error caused by upstreamed mtk_m32 functionYong-hyu, Ban2020-04-271-23/+17
| | | | | | | | | | | | | | | | | | | | This fixes following compile error: ``` CC drivers/net/ethernet/mediatek/mtk_eth_soc.o drivers/net/ethernet/mediatek/mtk_eth_soc.c:70:5: error: conflicting types for 'mtk_m32' u32 mtk_m32(struct mtk_eth *eth, u32 mask, u32 set, unsigned reg) ^~~~~~~ In file included from drivers/net/ethernet/mediatek/mtk_eth_soc.c:25: drivers/net/ethernet/mediatek/mtk_eth_soc.h:964:6: note: previous declaration of 'mtk_m32' was here void mtk_m32(struct mtk_eth *eth, u32 clear, u32 set, unsigned reg); ^~~~~~~ ``` which caused by 5.4.34 mainlining of mtk_m32 function. Fixes: faf668be354a ("kernel: bump 5.4 to 5.4.34") Signed-off-by: Yong-hyu, Ban <perillamint@quendi.moe>
* ramips: use lzma-loader for I-O DATA mt7621 devicesINAGAKI Hiroshi2020-04-271-0/+6
| | | | | | | | | | | | | | | | | | The official sysupgrade images for I-O DATA devices manufactured by MSTC (MitraStar Technology Corp.) cannot be booted normally and the kernel panics after switching to kernel 5.4. This commit fixes the issue by using lzma-loader. Note: These devices use Z-LOADER to read the kernel from NAND flash and boot it. Z-LOADER cannot load and start plain lzma-loader, so additional lzma-compression is needed. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> Co-developed-by: Yanase Yuki <dev@zpc.sakura.ne.jp> Signed-off-by: Yanase Yuki <dev@zpc.sakura.ne.jp> Tested-by: Yanase Yuki <dev@zpc.sakura.ne.jp> [wn-ax2033gr]
* ramips: use lzma-loader for Japanese mt7621 devicesINAGAKI Hiroshi2020-04-271-0/+8
| | | | | | | | | In several Japanese routers with MT7621 SoC, the official sysupgrade image cannot be booted properly after switching to kernel 5.4. This commit fixes the issue by using lzma-loader. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: mt7621: use lzma-loader for D-Link DIR-860L B1Szabolcs Hubai2020-04-271-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This device has trouble extracting big kernel from flash, and supports LZMA compressed kernels only. Using OpenWrt kernel loader saves us 64 KB compared to the dictionary size limiting workaround. Factory image sizes (commit: 5f126c541a74) with "CONFIG_ALL_KMODS=y": - original ("-d23", default): 4784188 bytes, LZMA ERROR 1 - with "-d19": 4915260, LZMA ERROR 1 - with "-d18": 4915260, diff to original: +128 KB - with "-d17": 4980796, diff to original: +192 KB - with this patch: 4849724, diff to original: +64 KB To save some CPU cycle, use minimal compression ("-a0") for the LZMA compressed uImage. The most robust solution would use a different loader, which reads the compressed kernel directly from the flash. See the thread at [0] for more details! [0] http://lists.infradead.org/pipermail/openwrt-devel/2020-April/022926.html Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com> Tested-by: Stijn Segers <foss@volatilesystems.org> [fixed identation] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: enable SGMII workaround for affected boardsDavid Bauer2020-04-273-0/+8
| | | | | | | These boards suffer from a sudden inability to establish a link on the SGMII. Enable the workaround to fix the link when it dies. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: ag71xx: unify version dependent codeDavid Bauer2020-04-271-5/+1
| | | | | | | Use IS_ERR_OR_NULL macro to use the same code on kernel 4.19 as well as 5.4. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: ag71xx: remove code for legacy kernelsDavid Bauer2020-04-271-32/+0
| | | | | | | ath79 does not support kernels prior to 4.19 anymore. Remove legacy code for those kernels from the ag71xx driver. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: remove unused TP-Link partition parserDavid Bauer2020-04-274-496/+0
| | | | | | | This parser was added with the target, but no device seems to use it currently, as all partitions are specified in the device-tree. Signed-off-by: David Bauer <mail@david-bauer.net>
* mvebu: tidy up support for GL.iNet GL-MV1000Adrian Schmutzler2020-04-274-19/+12
| | | | | | | | | | | | | | | | | This fixes a bunch of cosmetic issues with GL.iNet GL-MV1000: - apply alphabetic sorting in multiple files - use armada-3720 prefix for DTS like for other devices - fix vendor capitalization for model in DTSes - remove trivial comment in DTS files - use DEVICE_VENDOR/DEVICE_MODEL - remove redundant SUPPORTED_DEVICES - use SOC instead of DEVICE_DTS - remove empty line at EOF Fixes: 050c24f05c85 ("mvebu: add support for GL.iNet GL-MV1000") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: 5.4: enable NANDDENG Qingfang2020-04-261-1/+4
| | | | | | | NAND driver was dropped in the 5.4 bump, so enable it back Fixes: 50c6938b95a0 ("bcm53xx: add v5.4 support") Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: add support for GL.iNet GL-MV1000Li Zhang2020-04-264-1/+341
| | | | | | | | | | | | | | | | | | | | | | | | This patch adds supports for GL-MV1000. Specification: - SOC: Marvell Armada 88F3720 (1GHz) - Flash: 16MB (W25Q128FWSIG) - RAM: 1GB DDR4 - Ethernet: 3x GE (1 WAN + 2 LAN) - EMMC: 8GB EMMC (KLM8G1GETF-B041) - MicroSD: 1x microSD slot - USB: 1x USB 2.0 port(TypeA),1x USB 3.0 port(TypeC) - Button: 1x reset button,1x slide switch - LED: 3x greed LED - UART: 1x UART on PCB (JP1: 3.3V, RX, TX, GND) Update firmware instructions ============================ In the compiled,please gzip -d xxx.img.gz,then update firmware on uboot web. Signed-off-by: Li Zhang <li.zhang@gl-inet.com> [Copied dts file to files-5.4] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: backport fix for non-regular inodes on f2fsMatt Merhar2020-04-261-0/+69
| | | | | | | | | | | | | | | Upstream commit dda9f4b9ca ("f2fs: fix to skip verifying block address for non-regular inode"). On 4.14, attempting to perform operations on a non-regular inode residing on an f2fs filesystem, such rm-ing a device node, would fail and lead to a warning / call trace in dmesg. This fix was already applied to other kernels upstream - including 4.19, from which the patch was taken. More info at https://bugzilla.kernel.org/show_bug.cgi?id=202495. Signed-off-by: Matt Merhar <mattmerhar@protonmail.com>
* ramips: remove unnecessary DEVICE_PACKAGES for Belkin F7C027Sungbo Eo2020-04-261-1/+0
| | | | | | | kmod-usb-dwc2 and kmod-usb-ledtrig-usbport are not target default packages, and Belkin F7C027 does not have a USB port anyway. Just drop it. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: fix SUPPORTED_DEVICES for Mercury MAC1200R v2Sungbo Eo2020-04-261-1/+0
| | | | | | | | Currently SUPPORTED_DEVICES only contains the old device string. Fix it by removing the first assignment. Fixes: c2334ad60dc8 ("ramips/mt76x8: Synchronize Makefiles with DTS compatible") Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* oxnas: move service file to correct placeSungbo Eo2020-04-261-0/+0
| | | | | | | This service file has been misplaced from the very beginning. Fixes: dcc34574efba ("oxnas: bring in new oxnas target") Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* x86: fix unusable squashfs images by adding missing paddingPetr Štetiar2020-04-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was reported, that after image generation rework x86-64-generic-squashfs-rootfs.img image won't boot on XenServer x86_64 anymore: F2FS-fs (xvda): Magic Mismatch, valid(0xf2f52010) - read(0x84289960) F2FS-fs (xvda): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (xvda): Magic Mismatch, valid(0xf2f52010) - read(0x4e8ee223) F2FS-fs (xvda): Can't find valid F2FS filesystem in 2th superblock List of all partitions: ca00 4207 xvda driver: vbd No filesystem could mount root, tried: ext3 ext2 ext4 squashfs iso9660 f2fs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,0) So lets fix this by adding back padding which was introduced in commit a17d9482f5e2 ("x86: image: fix small disk space in squashfs overlay"). Ref: FS#3036 Fixes: 258f070d1a4f ("x86: fix missing squashfs and ext4 rootfs images") Fixes: cb007a7bf619 ("x86: switch image generation to new code") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: enable SFP port for Ubiquiti ER-X-SFPRené van Dorst2020-04-253-3/+64
| | | | | | | | | | | | | | | SFP cage of this device is connected via a AT8031 phy to port 5 of the switch. This phy act as a RGMII-to-SerDes converter. Also a I2C clock gate needs to be enabled in order to access the SFP module via I2C bus. SFP cage also has module detect pin which is connected to I2C gpio expander. With this patch the kernel/PHYLINK now can detect, readout and use the SFP module/port. NOTE: SFP cage / AT8033 PHY only support 1000base-X encoding! This means that some SGMII modules can work and only at forced 1GBit/full-duplex! Signed-off-by: René van Dorst <opensource@vdorst.com>
* kernel: add module to support SFP cagesRené van Dorst2020-04-251-1/+1
| | | | | | Enables kernel SFP case support. Signed-off-by: René van Dorst <opensource@vdorst.com>
* ramips: phy: at803x: support RGMII-to-SerDes and SFP supportDENG Qingfang2020-04-251-0/+141
| | | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> Signed-off-by: René van Dorst <opensource@vdorst.com>
* kernel: backport support for clause 37 1000Base-X auto-negotiationDENG Qingfang2020-04-251-0/+199
| | | | | | | This patch is needed for clause 37 1000Base-X encoding used in many SFP modules. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> Signed-off-by: René van Dorst <opensource@vdorst.com>
* kernel: bump 5.4 to 5.4.35Petr Štetiar2020-04-251-1/+1
| | | | | | | | | Refreshed one patch. Run tested: qemu-x86-64 Build tested: x86/64, imx6, sunxi/a53, rockchip/armv8 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: add back perf monitor related config symbolPetr Štetiar2020-04-251-0/+1
| | | | | | | | | Commit 0543eb111081 ("imx6: 5.4: add missing kernel perf monitor symbol") has added missing kernel config symbol FSL_IMX8_DDR_PMU which is exposed only when building perf, so add it back. Fixes: 8d9b36270b1f ("imx6: refresh kernel config") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq40xx: fix alphabetical order in 02_networkDavid Bauer2020-04-241-11/+11
| | | | Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix QCA953x DDR and GPIO compatible bindingsDavid Bauer2020-04-241-2/+2
| | | | | | | The memory as well as GPIO controller had the wrong SoC name used for their compatible binding. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: correct QCA9550 machine compatible bindingDavid Bauer2020-04-2414-14/+14
| | | | | | | Some boards using a QCA9556 or QCA9558 had their machine compatible binding incorrectly set to qca,qca9557. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: rename qca9557.dtsi to qca955x.dtsiDavid Bauer2020-04-2426-29/+29
| | | | | | | | | | | There are at least 3 different chips in the Scorpion series of SoCs. Rename the common DTSI to better reflect it's purpose for the whole series. Also rename the compatible bindings from qca,ar9557 and qca,qca9557 to qca,qca9550. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: move tplinkpart.c parser to patchesAdrian Schmutzler2020-04-243-253/+462
| | | | | | | | | | | | | Between 4.19 and 5.4, mtd parsers have been moved to "parsers" subdirectory. Like for myloader.c in the previous patch, this patch moves tplinkpart.c to the kernel patches, so the code and the kernel includes are at the same location and the path can be adjusted per kernel. While at it, remove some outdated kernel version switches from the C code. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix include of myloader.o since kernel 5.4Adrian Schmutzler2020-04-246-208/+569
| | | | | | | | | | | | | | | | | | | | | | Between 4.19 and 5.4, mtd parsers have been moved to "parsers" subdirectory. Based on this, the selection of myloader.o in OpenWrt was also moved to that subdirectory, while the Kconfig and our local myloader.c file remained in /drivers/mtd. This resulted in linking errors like the following (on ath25@5.4): make[8]: *** No rule to make target 'drivers/mtd/parsers/myloader.o', ... needed by 'drivers/mtd/parsers/built-in.a'. Stop. make[7]: *** [scripts/Makefile.build:500: drivers/mtd/parsers] Error 2 make[6]: *** [scripts/Makefile.build:500: drivers/mtd] Error 2 Since myloader.c is not too big, this patch moves it to the kernel patches, allowing to adjust the path for kernel 5.4 and keeping Makefiles and file paths better in sync. Other patches have been refreshed accordingly. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove config-4.14 for mt7621/mt76x8Adrian Schmutzler2020-04-232-547/+0
| | | | | | | | | | | mt7621 and mt76x8 subtargets have been moved to kernel 5.4 and their DTS(I) files are incompatible to kernel 4.14. Remove the corresponding kernel config files to signal that more boldly and to prevent accidentally patching the wrong kernel when pulling in older config patches. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-27 05:13:07 +0000