aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.4 to 5.4.48Petr Štetiar2020-06-221-1/+1
| | | | | | | | | | | | | | | | Resolved merge conflict in the following patches: layerscape: 701-net-0213-dpaa2-eth-Add-CEETM-qdisc-support.patch ramips: 0013-owrt-hack-fix-mt7688-cache-issue.patch Refreshed patches, removed upstreamed patch: bcm63xx: 020-v5.8-mtd-rawnand-brcmnand-fix-hamming-oob-layout.patch Run tested: qemu-x86-64 Build tested: x86/64 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: fritz7312: set maximum speed to 100 mbit on 5.4Adrian Schmutzler2020-06-211-0/+1
| | | | | | | | | | | | The fritz 7312 does not support 1000 gbit. Advertising it makes it worse. Some NIC will change to 1000 gibt and turn off and on again for ever. The previous patch in 36f628910b8b was only applied to the 4.19 file, so let's just make it consistent with this patch. Cc: Alexander Couzens <lynxis@fe80.eu> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: drop "CONFIG_HZ_100 is not set"Adrian Schmutzler2020-06-172-2/+0
| | | | | | | | | | CONFIG_HZ_100 is not set to "y" in generic config anymore since 3a761c90afc0 ("treewide: Don't diverge from upstream default HZ settings on 4.19"), so we don't need to disable it anymore either. This was the only remaining case in the entire tree. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: switch to 5.4Aleksander Jan Bajkowski2020-06-171-2/+1
| | | | | | Runtime tested on BT Home Hub 5A and D-Link DWR-966. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* treewide: drop shebang from non-executable target filesAdrian Schmutzler2020-06-162-3/+0
| | | | | | | | | | | | | | This drops the shebang from all target files for /lib and /etc/uci-defaults folders, as these are sourced and the shebang is useless. While at it, fix the executable flag on a few of these files. This does not touch ar71xx, as this target is just used for backporting now and applying cosmetic changes would just complicate things. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fritz 7360 v2: remove additional supported devicesAlexander Couzens2020-05-181-1/+0
| | | | | | | | | | | | The additional supported device isn't required since this is a new device. Some board contains an addtional device, those device were supported in earlier versions which used the "old" image builder code. To support an sysupgrade from such old version, there is the all caps additional device. Signed-off-by: Alexander Couzens <lynxis@fe80.eu> Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fritz 7360 v2: rename device before it will be usedAlexander Couzens2020-05-185-18/+18
| | | | | | | | | | | Use similiar naming scheme as ath79. Since the fritz 7360 v2 was only in the tree for 2 days, there is no compatibility for the old image. Users which has installed the fritz 7360 v2 before this change, must use sysupgrade --force to skip checks on the board. Signed-off-by: Alexander Couzens <lynxis@fe80.eu> Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: drop outdated kernel version switches from patches-5.4Adrian Schmutzler2020-05-171-15/+3
| | | | | | | | | This drops some ancient kernel version switches from patches on lantiq target. The patch only adjusts the latest kernel 5.4, as doing it a second time for an older kernel seems a waste of time for a cosmetic change. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq/xrx200: add support for the Fritzbox 7360v2Yushi Nishida2020-05-165-1/+175
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Fritzbox 7360v2 CPU: VR9 500MHz Cores: 2 RAM: 128 MB NOR-Flash: 32 MB WLAN: AR9287-BL1A DECT is not working. Thanks Sebastian Ortwein for adding 7360SL. The dts file is derived from avm_fritz7360sl.dts. Firmware can be flashed with this method: 1.) Set your client IP to 192.168.178.2 2.) Power on your your Fritzbox and connect to 192.168.178.1 via ftp in the first 5 seconds. 3.) login with adam2/adam2 4.) type into the ftp prompt: passive binary debug 1 quote MEDIA FLSH // (not FLASH) put openwrt-lantiq-xrx200-avm_fritz7360v2-squashfs-sysupgrade.bin mtd1 // using the correct location for the squashfs-sysupgrade-firmware.bin 5.) wait till red light flashing turns off. 6.) type: exit Run tested with kernel 4.19 and 5.4 on Fritzbox 7360 V2. Issue: Ethernet speed is slow, (iperf between a Xiaomi mir3g and this router results in <80Mbits throughput with a wired cable when using the gbit ports.) Signed-off-by: Yushi Nishida <kyro2man@gmx.net>
* lantiq/fritz 7312: set maximum speed to 100 mbitAlexander Couzens2020-04-211-0/+1
| | | | | | | | The fritz 7312 does not support 1000 gbit. Advertising it makes it worse. Some NIC will change to 1000 gibt and turn off and on again for ever. Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* kernel: bump 5.4 to 5.4.28Petr Štetiar2020-03-281-25/+0
| | | | | | | | | | | | | | | | | | | | Changelog since 5.4.24 mentions CVE-2019-19769, CVE-2020-8648, CVE-2020-8649 and CVE-2020-8647. Removed upstreamed: generic: 507-v5.6-iio-chemical-sps30-fix-missing-triggered-buffer-depe.patch generic: 600-ipv6-addrconf-call-ipv6_mc_up-for-non-Ethernet-inter.patch bcm27xx: 950-0435-ASoC-pcm512x-Fix-unbalanced-regulator-enable-call-in.patch ipq806x: 701-stmmac-fix-notifier-registration.patch lantiq: 002-pinctrl-falcon-fix-syntax-error.patch octeontx: 0002-net-thunderx-workaround-BGX-TX-Underflow-issue.patch Run tested: apu2, qemu-x86-64, apalis, a64-olinuxino, nbg6617 Build tested: sunxi/a53, imx6, x86/64, ipq40xx Tested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [apu2] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* treewide: omit IMAGE_SIZE argument from check-sizeSungbo Eo2020-03-214-9/+9
| | | | | | | | | Now that check-size uses IMAGE_SIZE by default, we can skip the argument from image recipes to reduce redundancy. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: gather DEVICE_VARS into one placeSungbo Eo2020-03-212-2/+3
| | | | | | | | | | | Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: kernel 5.4: enable JFFS2Mathias Kresin2020-03-171-1/+0
| | | | | | | | We do not build images with a jffs2 rootfs, but jffs2 is still used as filesystem for the rootfs_data. Fixes: e3eaf578082e ("lantiq: kernel 5.4: debloat kernel config") Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 5.4: debloat kernel configMathias Kresin2020-03-165-11/+8
| | | | | | | | | | | | | | | The etop driver is used by all targets except xrx200. Remove the UBIFS compression support for zlib and zstd from the xway subtarget. The hardware is EOL for a long time and it's unlikely to ever see a board shipped with an UBIFS using these compression methods. Remove the JFFS2 support. Support for jjfs2 images was dropped years ago. It shrinks the compressed kernel up to 130 KByte. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Linux 5.4 support as testing kernel versionMathias Kresin2020-03-1639-366/+883
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Switch to the mainline Lantiq PCIe PHY driver and update the vr9.dtsi accordingly. The Lantiq IRQ SMP support added upstream required changes to the SoC dtsi as well. Following changes are made to the Lantiq kernel patches: 0005-lantiq_etop-pass-struct-device-to-DMA-API-functions.patch 0006-MIPS-lantiq-pass-struct-device-to-DMA-API-functions.patch applied upstream 0008-MIPS-lantiq-backport-old-timer-code.patch access_ok API update because it lost it's type (which was the first) parameter in upstream commit 96d4f267e40f95 ("Remove 'type' argument from access_ok() function") 0024-MIPS-lantiq-autoselect-soc-rev-matching-fw.patch merged into 0026-MIPS-lantiq-Add-GPHY-Firmware-loader.patch 0024-MIPS-lantiq-revert-DSA-switch-driver-PMU-clock-chang.patch revert upstream changes required for upstream xrx200 ethernet and xrx200 (DSA) switch driver but breaking our driver 0026-MIPS-lantiq-Add-GPHY-Firmware-loader.patch required for our driver but dropped upstream, add former upstream version 0028-NET-lantiq-various-etop-fixes.patch now has to use the phy_set_max_speed API instead of modifying phydev->supported. Also call ltq_dma_enable_irq() in ltq_etop_open() based on upstream commit cc973aecf0b054 ("MIPS: lantiq: Do not enable IRQs in dma open") Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: linux 5.4: remove support for the linux,mtd-name OF propertyMartin Blumenstingl2020-03-163-46/+0
| | | | | | | | This is referenced in two .dts but never actually used from userspace. Drop support for this property because it's not used and because it makes updating to Linux 5.4 harder (as the patch doesn't apply anymore). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: copy target to kernel 5.4Mathias Kresin2020-03-16195-0/+27082
| | | | | | | | | Duplicate kernel 4.19 config and patches for kernel 5.4. Duplicate the devicetree source files as well, they need kernel 5.4 specific adjustments. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: vgv7510kw22: fix missing wirelessMathias Kresin2020-03-161-2/+2
| | | | | | | | | | | | | | | | | | | | For some reason pin 7 (gphy0_led1_pins) need to be set to output prior to loading the PCI driver. Otherwise the wireless doesn't appear on the PCI bus. Of course, it doesn't make much sense, since pin 7 is used to drive the LAN1 led. It can either be done by setting the pins function to GPHY or GPIO + direction output. However, the pinctrl driver doesn't provide a way to switch a pin to GPIO. It is done indirectly by the pinctrl driver at the time a GPIO is requested (requesting a GPIO always resets the function to GPIO). Do it via pinmux driver, as it is always loaded first. Use the GPHY function as it's the pins intended purpose for this board. Fixes: FS#2895 Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: remove maintainer variable from targetsPetr Štetiar2020-03-161-1/+0
| | | | | | | | | | | | | There is no such role as target maintainer anymore, one should always send corresponding changes for the review and anyone from the commiters is allowed to merge them or eventually use the hand break and NACK them. Lets make it clear, that it is solely a community doing the maintenance tasks. Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Piotr Dymacz <pepe2k@gmail.com>
* lantiq: move mux for pins into subnodesMathias Kresin2020-03-153-115/+161
| | | | | | | | | | | The mux need to be defined in a subnode to be considered by the pinctrl framework. These muxes aren't set as expected and might cause not working subsystems. Fixes: 8e7b573b7aa4 ("lantiq: dts: assign the PCI pins to the PCI controller node") Fixes: dcb5e52209e5 ("lantiq: dts: assign the STP pins to the STP GPIO controller node") Fixes: 660200e53d62 ("lantiq: dts: assign the GPHY LED pins to the Ethernet controller node") Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: make kmod-i2c-core selected by dependent modulesSungbo Eo2020-03-131-1/+1
| | | | | | | | | | | | | | | | | | Currently kmod-i2c-* will not get into images unless kmod-i2c-core is added to DEVICE_PACKAGES as well. By changing the dependencies from "depends on" to "select", we do not have the issue anymore. Furthermore, we can remove most occurrences of the package from DEVICE_PACKAGES and similar variables, as it is now pulled by dependent modules such as: - kmod-hwmon-lm75 - kmod-i2c-gpio - kmod-i2c-gpio-custom - kmod-i2c-mux - kmod-i2c-ralink Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* build: image: move IMAGE_SIZE to image.mkSungbo Eo2020-03-111-2/+0
| | | | | | | | | | IMAGE_SIZE is widely used in many targets. Declare it in the default template to clean up redundant code. This also prevents deriving IMAGE_SIZE unintentionally from the previously defined device. While at it, remove duplicate KERNEL_SIZE declaration. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* kernel: remove non-existant symbols from 4.19 configAleksander Jan Bajkowski2020-02-223-9/+0
| | | | | | These symbols only exist in kernel version <= 4.15 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* lantiq: tidy up image/MakefileAdrian Schmutzler2020-01-241-7/+5
| | | | | | | This harmonizes indent for Build blocks and removes multiple empty lines. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fix setting SOC to DEFAULT_SOCAdrian Schmutzler2020-01-241-0/+1
| | | | | | | | | This adds the missing assignment of DEFAULT_SOC to the SOC variable by default. Fixes: 09ee51c614d9 ("lantiq: define SOC only once for uniform targets") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: define SOC only once for uniform targetsAdrian Schmutzler2020-01-246-38/+4
| | | | | | | | | | | | | | In lantiq there are several subtarget where all devices have the same value set to the SOC variable for each device individually. This patch introduces a non-device-dependent variable DEFAULT_SOC, which is used if no specific SOC is set for a device, and thus reduces the number of redundant definitions drastically. This is applied to all subtargets except xway, as only the latter has two different SOCs. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: move DTS_DIR variable out of Device definitionAdrian Schmutzler2020-01-241-1/+2
| | | | | | | | | The DTS_DIR variable is not a device variable, thus it should not be set inside Device/Default but globally. Fixes: c640370939d7 ("lantiq: use soc_vendor_device scheme on DTS file") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fix model name for BT Home Hub 3 Type AAdrian Schmutzler2020-01-241-1/+1
| | | | | | | | | The number 3 was accidentally removed from the name during split of DEVICE_TITLE. Fixes: fd666870582f ("lantiq: split up DEVICE_TITLE") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: reorganize 02_network board.d filesAdrian Schmutzler2020-01-145-276/+378
| | | | | | | | | | This reorganizes 02_network board.d files based on what's done for ath79 and ramips: Instead of putting all settings into a single big case, the interface/dsl/MAC address setup is put into separate functions with a specific switch case for each of them. This makes grouping of devices much easier and should be easier to read, too. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: move common DSL setup into lantiq.shAdrian Schmutzler2020-01-146-52/+20
| | | | | | | | | DSL setup consists of the same commands for all subtargets, so move it into a helper function. While at it, remove shebang from library file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: split base-files into subtargetsAdrian Schmutzler2020-01-1417-214/+523
| | | | | | | | | | | | | | | | | | This splits the device-dependent base-files into subtarget directories, like done recently for ath79 and ramips. While this increases the overall lines of codes, it will make the code per subtarget smaller and easier to keep track of features and devices. While at it, several variables at the top of 02_network are removed, as they were never changed. The values are put directly into the function calls where they are used. Remove unneeded LED setup from 01_leds, and remove 01_leds entirely for falcon subtarget (as it is not used there). Applies alphabetic reordering to device cases in base-files. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: use shared code for LED migrationAdrian Schmutzler2020-01-031-45/+6
| | | | | | | | | | Shared base-files package contains functions for LED migration that are already used by several targets. Apply those also to lantiq and drop the (redundant) local code. While at it, reorder board names in file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove includes of non-existent /lib/functions/lantiq.shAdrian Schmutzler2020-01-032-3/+0
| | | | | | | lantiq.sh is still included in files which do not use it anymore. Remove the includes. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.19 to 4.19.90Koen Vandeputte2019-12-241-1/+1
| | | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 010-dmaengine-dw-dmac-implement-dma-prot.patch - 950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch - 950-0206-Mailbox-firmware-calls-now-use-kmalloc-2749.patch - 402-leds-trigger-netdev-fix-handling-on-interface-rename.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [Add 010-dt-bindings-dmaengine-dw-dmac-add-protection-control.patch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: enable 5ghz wifi on VR200/VR200vKevin Schmidt2019-12-232-3/+22
| | | | | | Enable mt76 driver on VR200/VR200v. Signed-off-by: Kevin Schmidt <kevin.patrick.schmidt@googlemail.com>
* lantiq: fix phys ledAleksander Jan Bajkowski2019-12-231-2/+2
| | | | | | | | led2l and led2h value is incorrectly set by led3l and led3h. Bug was introduced in commit: 863e79f8d5544a8a884375d7e867f350fddca9b9 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Fixes: 863e79f8d554 ("lantiq: add support for kernel 4.9")
* lantiq: move include to parent falcon_lantiq_easy98000.dtsiAdrian Schmutzler2019-12-224-6/+2
| | | | | | | This moves the include of lantiq.dtsi from the DTS files to the parent falcon_lantiq_easy98000.dtsi. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove ar9_lantiq_easy50810.dtsAdrian Schmutzler2019-12-221-73/+0
| | | | | | This file seems to be orphaned, no device setup existing for it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: use soc_vendor_device scheme on DTS fileAdrian Schmutzler2019-12-2290-99/+98
| | | | | | | | | | | | This renames lantiq DTS(I) files to follow soc_vendor_device scheme. This will make DTS files easier to maintain. As a side effect, DTS file name can be derived from device node names now, only having to specify a SOC variable in Makefiles. While at it, move files to arch/mips/boot/dts/lantiq subfolder. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: split device definitions into filesAdrian Schmutzler2019-12-227-851/+838
| | | | | | | This splits device definitions into several *.mk files to increase overview. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: dts: assign the ASC pins to the serial controller nodeMartin Blumenstingl2019-12-223-8/+9
| | | | | | | | Assign the ASC pins to the serial controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the PCI pins to the PCI controller nodeMartin Blumenstingl2019-12-2227-260/+213
| | | | | | | | Assign the PCI pins to the PCI controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the STP pins to the STP GPIO controller nodeMartin Blumenstingl2019-12-2211-68/+36
| | | | | | | | Assign the STP pins to the STP GPIO controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the GPHY LED pins to the Ethernet controller nodeMartin Blumenstingl2019-12-227-54/+71
| | | | | | | | Assign the GPHY LED pins to the Ethernet controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the NAND pins to the nand-controller nodeMartin Blumenstingl2019-12-2216-85/+112
| | | | | | | | | | | | Assign the NAND pins to the NAND controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. While here, define all NAND pins (CLE, ALE, read/RD, ready busy/RDY and CE/CS1). This means that the pinctrl subsystem knows that these pins are in use and cannot be re-assigned as GPIOs for example. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: define the SPI pins in {amazonse,ar9,vr9}.dtsiMartin Blumenstingl2019-12-2212-141/+66
| | | | | | | | | Define the SPI pins in the corresponding SoCs.dtsi and assign them to the SPI controller node. All known boards use CS4 and it's likely that this is hardcoded in bootrom so this doesn't bother with having per-board SPI pinmux settings. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the MDIO pins to the gsw nodeMartin Blumenstingl2019-12-2219-80/+27
| | | | | | | | | | | | Assign the MDIO pins to the switch node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. This converts amazonse, ar9 and vr9. danube is skipped because the pin controller doesn't define a pinmux for the MDIO pins (some of the SoC pads may be hardwired to the MDIO pins instead of being configurable). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* kernel: bump 4.19 to 4.19.88Koen Vandeputte2019-12-101-29/+0
| | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 0004-boot-sq201-from-sda1.patch - 500-v4.20-ubifs-Fix-default-compression-selection-in-ubifs.patch - 0003-usb-dwc2-use-a-longer-core-rest-timeout-in-dwc2_core.patch Altered patches: - 0011-ARM-dts-Fix-up-SQ201-flash-access.patch - 400-mtd-add-rootfs-split-support.patch - 0101-pci-mediatek-backport-fix-pcie.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: remove dts-v1 identifier from DTSI filesAdrian Schmutzler2019-12-081-1/+0
| | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be put once at the beginning of a device tree file. Thus, it makes no sense to provide it a second time in to-be-included DTSI files. This removes the identifier from all DTSI files in /target/linux. Most of the DTS files in OpenWrt do contain the "/dts-v1/;". It is missing for most of the following targets, though: mvebu, ipq806x, mpc85xx, ipq40xx This does not touch ipq806x for now, as the bump to 4.19 is close. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 11:58:14 +0000