aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/xrx200
Commit message (Collapse)AuthorAgeFilesLines
* ltq-deu: Mark lantiq DEU brokenHauke Mehrtens2021-06-301-1/+0
| | | | | | | | | | | | | | | | | | | | When the ltq_deu_vr9 kernel module is loaded, hostapd does not start any more. It fails with this error message: daemon.err hostapd: nl80211: kernel reports: key addition failed daemon.err hostapd: Interface initialization failed OpenWrt uses the standard Linux crypto API in the wifi drivers now and this probably makes the system offload more crypto operations to special hardware like the Lantiq DEU. There is probably a bug in the DEU and these operations fail and then hostapd does not start the interface. Do not include the Lantiq DEU by default any more. Fixes: FS#3901 Fixes: 53b6783907f3 ("mac80211: remove patches stripping down crypto support") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Tested-by: Notupus <notpp46@gmail.com>
* lantiq: xrx200: switch the subtarget to the mainline DSA driverMartin Blumenstingl2021-06-265-50/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable the XRX200 PMAC, GSWIP DSA tag and GSIP DSA drivers in the 5.4 kernel config. Update the existing vr9_*.dts{,i} to use the new Ethernet and switch drivers. Drop the swconfig package from the xrx200 target because swconfig doesn't manage DSA based switches. The new /etc/config/network format for the DSA driver is not compatible with the old (swconfig) based one. Show a message during sysupgrade notifying users about this change and asking them to start with a fresh config (or forcefully update and then migrate the config manually). Failsafe mode can now automatically bring up the first lan interface based on board.json including DSA based setups. Drop 05_set_preinit_iface_lantiq from the xRX200 sub-target as this is not needed anymore. For now we are keeping it for the ase, xway and xway_legacy until there's some confirmation that it can be dropped from there as well. While here, some boards also receive minor fixups: - Use LAN1 as LAN1 (according to a photo this port can also be configured as WAN) on the Buffalo WBMR-300HPD. This makes it easier to read the port mapping because otherwise we would have LAN{2,3,4} and WAN (which was the case for the non-DSA version previously). - vr9_avm_fritz3390.dts: move the "gpio" comment from port 0 and 1 to their corresponding PHYs - vr9_tplink_vr200.dtsi: move the "gpio" comment from port 0 to PHY 0 - vr9_tplink_tdw89x0.dtsi: move the "gpio" comment from port 0 to PHY 0 Acked-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Tested-by: Notupus <notpp46@googlemail.com> # TD-W9980/DM200/FRITZ 7430 Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on TDT VR2020 Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on TP-Link TD-W8980B Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on ZyXEL P-2812HNU-F1 Tested-by: Daniel Kestrel <kestrel1974@t-online.de> # tested on Fritzbox 7490 Tested-by: Daniel Kestrel <kestrel1974@t-online.de> # tested on Fritzbox 3490 Tested-by: @jospezial <jospezial@gmx.de> # tested on VGV7510KW22 (o2 Box 6431) Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* treewide: remove "+" sign for increment with macaddr_addAdrian Schmutzler2021-06-052-2/+2
| | | | | | | | | | | | Many people appear to use an unneeded "+" prefix for the increment when calculating a MAC address with macaddr_add. Since this is not required and used inconsistently [*], just remove it. [*] As a funny side-fact, copy-pasting has led to almost all hotplug.d files using the "+", while nearly all of the 02_network files are not using it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: remove redundant ubifs kconfig symbolsRui Salvaterra2021-04-212-8/+0
| | | | | | | For the targets which enable ubifs, these symbols are already part of the generic kconfigs. Drop them from the target kconfigs. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* lantiq: add Linux 5.10 support as testing kernelMathias Kresin2021-04-121-0/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Following changes are made to the Lantiq kernel patches: 0001-MIPS-lantiq-add-pcie-driver.patch The pci header isn't included by the of_pci header any longer 0024-MIPS-lantiq-revert-DSA-switch-driver-PMU-clock-chang.patch Due to the merge of grx390 and ar10 clocks, extend support to grx390 0025-NET-MIPS-lantiq-adds-xrx200-legacy.patch The do_carrier arguments was dropped from phy_link_change. The phylib has always sets the third parameter to true so the flag is always changed anyway. of_get_phy_mode() returns an error, or 0 on success, and pass a pointer, of type phy_interface_t, where the phy mode should be stored now. So far an error wasn't considered. Print at least an error message if something unexpected happens. The stuck queue is now passed to xrx200_tx_timeout (the timeout handler) but not used so far. 0028-NET-lantiq-various-etop-fixes.patch ioremap has provided non-cached semantics by default since the Linux 2.6 days and was removed with kernel version 5.6. of_get_phy_mode() returns an error, or 0 on success, and pass a pointer, of type phy_interface_t, where the phy mode should be stored now. So far an error wasn't considered. Print at least an error message if something unexpected happens. 0042-arch-mips-increase-io_space_limit.patch Move IO space extension to laniq specific file Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add basic support for AVM FRITZ!Box 3390Andreas Böhler2021-04-034-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FRITZ!Box 3390 actually contains two SoCs, one Lantiq with a 5GHz WiFi and one AR9342 with a 2.4GHz WiFi. Only the Lantiq has access to the flash memory, the Atheros runs fully from RAM. Specifications -------------- - Lantiq 500 MHz - 128MiB RAM - 128MiB NAND - 256k Flash - AR9580 5GHz WiFi - AR9342 560 MHz - 64MiB RAM - AR9328 2.4GHz WiFi Remarks ------- This commit only adds support for the Lantiq side of things and prepares the drivers for communication with the Atheros SoC. Thus, only 5GHz WiFi works by default, the 2.4GHz WiFi will be added via another target. Some kernel patches will be required to add support for the Atheros SoC. Installation ------------ Use the eva_ramboot.py script to boot the initramfs image. Then, transfer the sysupgrade image to the device and run sysupgrade to flash it to the NAND. Signed-off-by: Andreas Böhler <dev@aboehler.at> Acked-by: Aleksander Jan Bajkowski A.Bajkowski@stud.elka.pw.edu.pl Signed-off-by: Joachim Cerny <cocktail_yogi@web.de>
* treewide: remove execute bit and shebang from board.d filesAdrian Schmutzler2021-03-062-2/+0
| | | | | | | | | | | | | | | | So far, board.d files were having execute bit set and contained a shebang. However, they are just sourced in board_detect, with an apparantly unnecessary check for execute permission beforehand. Replace this check by one for existance and make the board.d files "normal" files, as would be expected in /etc anyway. Note: This removes an apparantly unused '#!/bin/sh /etc/rc.common' in target/linux/bcm47xx/base-files/etc/board.d/01_network Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: vr9: set the usb led trigger via devicetreeMathias Kresin2021-03-011-6/+0
| | | | | | | | | | Assign the usbdev trigger via devicetree and drop the userspace handling of the usb leds. Drop the now unused userspace helper code as well. Signed-off-by: Mathias Kresin <dev@kresin.me> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: enable CONFIG_LEDS_TRIGGER_HEARTBEATSungbo Eo2021-01-151-1/+0
| | | | | | | | | | The heartbeat trigger is used by luci-mod-system, which is installed as a part of the standard luci package set. It seems the LED trigger will be required quite often, so let's enable it by default. This increases uncompressed kernel size by about 100 bytes on ath79/generic. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* kernel: move some disabled symbols to genericAleksander Jan Bajkowski2020-12-221-3/+0
| | | | | | Move some disabled config options found in lantiq target to generic. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* lantiq: fix build of squashfs imagesAleksander Jan Bajkowski2020-11-291-1/+1
| | | | | | | | | | | | This patch fixes build of squashfs image on lantiq. Currently the FEATURE variable is overwritten by the subtarget. Fixes: FS#3480 Fixes: f1c652337628 ("lantiq: clean up target/subtarget features") Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> [reformat Fixes:] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: clean up target/subtarget featuresRui Salvaterra2020-11-251-1/+1
| | | | | | | | | The feature "squashfs" is defined for target and all subtargets individually. Remove the redundant entries in the subtargets. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> [split patch, adjust commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: add support for AVM FRITZ!Box 7430Leon Maurice Adam2020-10-273-3/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: - SoC: Lantiq VRX 220 - CPU: 2x MIPS 34Kc 500 MHz - RAM: 128 MiB 250 MHz - Flash: 128 MiB NAND - Ethernet: Built-in Fast Ethernet switch, 4 ports used - Wifi: Atheros AR9381-AL1A b/g/n with 2 pcb/internal and 1 external antennas - USB: 1x USB 2.0 - DSL: Built-in A/VDSL2 modem - DECT: Dialog SC14441 - LEDs: 1 two-color, 4 one-color - Buttons: 1x DECT, 1x WIFI - Telephone connectors: 1 FXS port via TAE or RJ11 connector With the exception of FXS/DECT everything works (there are no drivers for AVM's FXS or DECT implementation), DSL is yet untested. Installation: Boot up the device and wait a few seconds. Run the eva_ramboot.py script in scripts/flashing/ to load the initramfs image on the device: $ ./scripts/flashing/eva_ramboot.py 192.168.178.1 <path to your initramfs image> If the script fails to reach the device, maybe try 169.254.120.1. Wait until booting is complete. You should now be able to reach your device under the default ip address 192.168.1.1. Before flashing, check if linux_fs_start is not set to 1 in the tffs partition: $ fritz_tffs_nand -d /dev/mtd1 -n linux_fs_start If linux_fs_start is 1, you will need to reset it to 0, either by FTP, upgrading FritzOS or doing a recovery. Now you should be able to flash the device using sysupgrade. Signed-off-by: Leon Maurice Adam <leon.adam@aol.de> Acked-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> [drop BOARD_NAME, use wpad-basic-wolfssl, drop 4.19, drop dts-v1, remove model prefix from LED names] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove support for kernel 4.19Adrian Schmutzler2020-10-191-90/+0
| | | | | | | | | | | | | The target uses 5.4 as default kernel since 06/2020. Kernel 4.19 support is not really maintained anymore, it does not seem to be needed and upcoming changes (mainly DSA) will break backward-compatibility anyway. Thus, make maintaining of old stuff and reviewing of new stuff easier by removing support for kernel 4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove model name from LED labelsAdrian Schmutzler2020-10-082-15/+15
| | | | | | | | | | | | | | | | Like in the previous patches for other targets, this will remove the "devicename" from LED labels in lantiq. The devicename is removed in DTS files and 01_leds, consolidation of definitions into DTSI files is done where (easily) possible, and migration scripts are updated. The DTS/DTSI consolidation is only performed for files-5.4. For lantiq,easy98020 some LED definitions have the form "devicename:function" without the color, so we need to implement explicit migration for that one. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: use uniform "u-boot-env" mtd labelMartin Schiller2020-09-171-4/+4
| | | | | | | | | | | This is the most popular choice in the linux kernel tree. Within OpenWrt, this change will establish consistency with ath79 and ramips targets. Signed-off-by: Martin Schiller <ms@dev.tdt.de> [extend commit message, include netgear_dm200, update base-files] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: move 01_led_migration script to subtargetsAdrian Schmutzler2020-07-171-0/+32
| | | | | | | | | | | | Split the /etc/uci-defaults/01_led_migration scripts into subtargets as already done for most of the other base-files. While this introduces a minor amount of code duplication, it still is considered an improvement, as device-specific settings are kept together in the subtargets' base-files and the script at hand can be removed entirely for two of the subtargets not needing it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: kernel: drop redundant USB_EHCI_HCD=n config symbolPetr Štetiar2020-07-092-2/+0
| | | | | | | | | Commit e53ec043bae1 ("kirkwood: move usb support to modules") has moved this config symbol into generic configs, so it could be removed from other configs. Suggested-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: remove unused PHY drivers on xrx200Aleksander Jan Bajkowski2020-06-272-12/+0
| | | | | | | | | | All boards on xrx200 use builtin switch and there is no supported device with external switch. It was copy paste from xway subtarget and was added in commit 18b76c66fbfea0e21ff66c6df432fa109c5bbb43. Save 20.3 kB flash memory. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* lantiq: fritz 7360 v2: rename device before it will be usedAlexander Couzens2020-05-182-2/+2
| | | | | | | | | | | 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/xrx200: add support for the Fritzbox 7360v2Yushi Nishida2020-05-162-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: add Linux 5.4 support as testing kernel versionMathias Kresin2020-03-161-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: copy target to kernel 5.4Mathias Kresin2020-03-161-0/+97
| | | | | | | | | 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: reorganize 02_network board.d filesAdrian Schmutzler2020-01-141-115/+156
| | | | | | | | | | 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-141-10/+1
| | | | | | | | | 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-145-0/+296
| | | | | | | | | | | | | | | | | | 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: drop kernel 4.14 supportMathias Kresin2019-07-041-97/+0
| | | | | | | The current state of the kernel 4.14 support is in the openwrt-19.07 branch. No need to keep a not default used kernel in this branch. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: make patches applyHauke Mehrtens2019-07-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | The following patches are dropped because they are now upstreamed: - 0002-gpio-stp-xway-Implement-get-callback.patch upstreamed with commit 5b9b2b5284f819 ("gpio: stp-xway: Implement get callback") - 0027-01-net-phy-intel-xway-add-VR9-version-number.patch upstreamed with commit 5b73d9955fb4b0 ("net: phy: intel-xway: add VR9 version number") - 0027-02-net-phy-intel-xway-add-VR9-v1.1-phy-ids.patch upstreamed with commit f452518c982e57 ("net: phy: intel-xway: add VR9 v1.1 phy ids") The following patches were updated: - 0018-MTD-nand-lots-of-xrx200-fixes.patch the mainline driver now resides in drivers/mtd/nand/raw/xway_nand.c (instead of drivers/mtd/nand/xway_nand.c) - 0025-NET-MIPS-lantiq-adds-xrx200-net.patch the DMA API now requires a valid device to be passed to all operations - 0028-NET-lantiq-various-etop-fixes.patch the DMA API now requires a valid device to be passed to all operations Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: copy target to kernel 4.19Hauke Mehrtens2019-07-041-0/+97
| | | | | | | | This just copies the files from the kernel 4.14 specific folders into the kernel 4.19 specific folder, no changes are done to the files in this commit. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq/xrx200: enable initramfs imagesStijn Segers2019-05-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Commit eae6cac6a3 ("lantiq: add support for AVM FRITZ!Box 7362 SL"), but one needs an initramfs image to flash OpenWrt from stock firmware (as described in the commit log). This patch has the initramfs image built by default. Thanks to blogic (for pointing to the FEATURES declaration in the target Makefiles) and Musashino on the forum for suggesting config/Config-images.in needed editing too. While at it, reorder the TARGET_INITRAMFS_COMPRESSION_LZMA declarations alphabetically. This patch will result in initramfs images for all lantiq subtargets that have the ramdisk flag set. I tested on the falcon and ase subtargets, which lack that flag, to confirm they don't produce any initramfs images with this patch - which they do not. Given the limited scope of the lantiq (sub)target(s), blogic indicated this should be OK. Signed-off-by: Stijn Segers <foss@volatilesystems.org> Signed-off-by: Petr Štetiar <ynezz@true.cz> [fixed the wrong reference to eae6cac6a3 commit]
* lantiq-vdsl-fw: update to provide recent vectoring firmwareDaniel Golle2018-06-151-1/+1
| | | | | | | | | | | | | | Recent Speedport firmware downloads only work over HTTPS, so the user either needs to provide the already downloaded file or install ustream-ssl-* as well as ca-certificates or ca-bundle. So to get VDSL2 with vectoring on xRX200, simply run vdsl_fw_install.sh on the target and either provide the downloaded file as instructed or make sure the device is connected to the Internet and can download that HTTPS url itself. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* Revert "lantiq: get rid of ltq-vdsl-fw"Daniel Golle2018-06-151-0/+1
| | | | | | This reverts commit 0938233fcdef67d969f9429a10761cc640c6d56d. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* lantiq: switch to kernel 4.14Mathias Kresin2018-05-171-90/+0
| | | | | | Use kernel 4.14 by default. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: update patches and configHauke Mehrtens2018-02-201-2/+9
| | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: copy patches, config and dts filesHauke Mehrtens2018-02-201-0/+90
| | | | | | | This just copies the patches, configuration and dts files into the directories hich are used for kernel 4.14. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: make dts files and kernel config kernel version specificMathias Kresin2018-02-201-0/+0
| | | | | | | | | | Move the devicetree source files to a kernel specific directory in preparation of adding kernel 4.14 support. Rename the subtarget kernel config files to match a specific kernel version. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: nand: drop ubifs imagesMathias Kresin2017-12-111-1/+1
| | | | | | | | | | | | | | | Users are confused which image type they should use and there are more drawbacks than adavantages in using a r/w ubifs rootfs in constrast to a read-only squashfs rootfs like: - less available free flash space due to better compression of squashfs images - no support for factory reset due to r/w filesystem - possibility to break failsafe due to r/w filesystem Therefore, drop support for r/w ubifs rootfs images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: select PCI support in subtargetsMathias Kresin2017-10-041-0/+7
| | | | | | | | | | | | | | | | AmazonSE and Falcon do not have support for PCI and it can't be unselected in the subtarget kernel config. This way the enabled PCI support is inherit from the higher level config to the subtarget. If CONFIG_PCI is selected, PCI_SUPPORT will be autoselected as well and all packages depending on this config symbol will be build and at least some of them fail due to missing pci functions. The issue can be observed if all kmods and all non-shared packages are build. Fix the issue by enabling PCI support only in subtargets with PCI support. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: xrx200: cleanup kernel configMathias Kresin2017-10-041-3/+8
| | | | | | | | | | | CONFIG_MTSCHED & CONFIG_PERFCTRS were never defined in the kernel. CONFIG_LANTIQ_PHY was replaced by CONFIG_INTEL_XWAY_PHY with the switch to the upstreamed driver. Add autoselected dependecies to the kernel config. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: xrx200: fix sorting of kernel configMathias Kresin2017-10-041-6/+6
| | | | | | | Use the kconfig script to sort the kernel config. It makes further changes more obvious. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add support for kernel 4.9Hauke Mehrtens2017-02-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following patches were dropped because they are already applied upstream: 0012-pinctrl-lantiq-fix-up-pinmux.patch 0013-MTD-lantiq-xway-fix-invalid-operator.patch 0014-MTD-lantiq-xway-the-latched-command-should-be-persis.patch 0015-MTD-lantiq-xway-remove-endless-loop.patch 0016-MTD-lantiq-xway-add-missing-write_buf-and-read_buf-t.patch 0017-MTD-xway-fix-nand-locking.patch 0044-pinctrl-lantiq-introduce-new-dedicated-devicetree-bi.patch 0045-pinctrl-lantiq-Fix-GPIO-Setup-of-GPIO-Port3.patch 0046-pinctrl-lantiq-2-pins-have-the-wrong-mux-list.patch 0047-irq-fixes.patch 0047-mtd-plat-nand-pass-of-node.patch 0060-usb-dwc2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch 0120-MIPS-lantiq-add-support-for-device-tree-file-from-bo.patch 0121-MIPS-lantiq-make-it-possible-to-build-in-no-device-t.patch 122-MIPS-store-the-appended-dtb-address-in-a-variable.patch The PHY driver was reduced to the code adding the LED configuration, the rest is already upstream: 0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch The SPI driver was replaced with the version pending for upstream inclusion: New driver: 0090-spi-add-transfer_status-callback.patch 0091-spi-lantiq-ssc-add-support-for-Lantiq-SSC-SPI-controller.patch Old driver: 0100-spi-add-support-for-Lantiq-SPI-controller.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: enable SMP for XRX200Felix Fietkau2017-02-011-0/+19
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: remove mips16 feature flag from target makefilesFelix Fietkau2017-01-241-1/+1
| | | | | | | It can be implicitly derived from the MIPS32 revision support in the kernel configuration Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: remove ubifs xz decompression supportFelix Fietkau2017-01-091-1/+0
| | | | | | | It has been unused, and less useful than squashfs for cases where flash space usage matters. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: add vpe/watchdog modules to kernelStefan Koch2016-10-311-0/+6
| | | | | | | | | (required not-distributable firmware blob - dump it by yourself from original firmware) Signed-off-by: Eddi De Pieri <eddi@depieri.net> (cherry picked from commit 064f467264c5c9b6eca0bb96b587f9412b770cc5) Signed-off-by: Stefan Koch <stefan.koch10@gmail.com>
* lantiq: switch from 34k to 24kJonas Gorski2016-08-231-1/+1
| | | | | | | GCC treats 24kc and 34kc exactly the same and will generate identical code, so there is no need to tune to 34kc instead of 24kc. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* lantiq: add cpu temperatur sensor driver for xrx200Florian Eckert2016-08-031-0/+2
| | | | Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com>
* build: remove MIPS dsp/dsp2 CPU_SUBTYPEFelix Fietkau2016-08-031-1/+0
| | | | | | | There does not seem to be any meaningful difference in generated code. This will save some time and space on snapshot builds Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: disable jffs2 support on xrx200Felix Fietkau2016-07-201-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* Revert "lantiq: enable SMP for XRX200"Felix Fietkau2016-06-271-19/+0
| | | | | | | | | This reverts commit cc3bfdb62f941dff3e2983591c78b6d39ca8d88a. Apparently the ethernet driver is not SMP safe, as reported in https://bugs.lede-project.org/index.php?do=details&task_id=27 Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 17:10:52 +0000