aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq
Commit message (Collapse)AuthorAgeFilesLines
* kernel: update kernel 4.4 to version 4.4.9Álvaro Fernández Rojas2016-05-101-2/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* lantiq: VGV7510KW22BRN - set the phy clock sourceblogic2016-05-101-0/+6
| | | | | | | | | | | | | VGV7510KW2 with VRX288 v1.2 has brnboot 1.8 installed. Starting with this brnboot version, the "GPHY Clock Source" isn't set anymore by brnboot, with the result that xrx200-net fails to probe/initialize the phys. Use the phy clock source device tree binding to specify the clock source. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49284
* lantiq: add device tree binding for the phy clock sourceblogic2016-05-101-0/+30
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49283
* lantiq: VGV7510KW22BRN - support dual-imageblogic2016-05-101-1/+4
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49282
* lantiq: handle the dual-firmware layout of brnbootblogic2016-05-101-0/+93
| | | | | | | | | | | | | | | | | brnboot based devices can have two Image partitions. When flashing images via the brnboot recovery web interface, the Image partitions are written alternating. The current active Image partition is stored in the first byte of the Primary_Setting partition by using 0x00 for Code_Image_0 and 0x01 for Code_Image_1. By using the information about the active "Code Image", it is possible to ensure that the rootfs belongs to the current booted Image/Kernel. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49281
* lantiq: move partitions into partion table nodeblogic2016-05-1042-1006/+1253
| | | | | | | | | | Starting with kernel 4.4, the use of partitions as direct subnodes of the mtd device is discouraged and only supported for backward compatiblity reasons. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49280
* lantiq: use sysupgrade.bin postfix for tplink imagesblogic2016-05-101-3/+4
| | | | | | | | | | | | Use the same name for TP-Link images as it was with the old image build code. Move the BOARD_ID export to the TP-Link image build recipe, to indicate that the variable is only related in this context. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49279
* lantiq: VG3503J - use the same PHY led functionality as the OEM firmwareblogic2016-05-101-8/+8
| | | | | | | | | | | | | Based on the vg3503j_gphy_led.sh script published in the VG3503J wiki article, the OEM Firmware uses the following PHY led functionality: gphy led 0: LINK/ACTIVITY gphy led 1: LINK gphy led 2: ACTIVITY Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49278
* lantiq: use the same functionality for all ethernet phys ledblogic2016-05-102-6/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys and the led for LAN4 connect to pin0 of the phy. This results with the current configuration in a fast flashing LAN4 led as soon as a network cable is connected. Something similar was reported on the forum[1] for the VGV7519 as well. Since it isn't predicable to which pin a (single) phy led is connected, use the (default) pin1 functionality Constant On: 10/100/1000MBit Blink Fast: None Blink Slow: None Pulse: TX/RX for all ethernet phy leds. After checking pictures of all vr9 boards, it looks like only the VG3503J has more than one led connected per phy. Using the phy led device tree bindings to assign the functionality to the "additional" leds, the VG3503J phy leds should behave as before. Signed-off-by: Mathias Kresin <openwrt@kresin.me> [1] https://forum.openwrt.org/viewtopic.php?pid=321523 SVN-Revision: 49270
* lantiq: fix minor typos in 11G/22F phy driverblogic2016-05-101-2/+2
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49269
* lantiq: fix xway image buildingJo-Philipp Wich2016-04-271-3/+3
| | | | | | | | | | | | | | | | | | | Commit 8c130dd (lantiq: use new image build process for some images) broke image generation for the xway target since the generated macros reference not existing WBMRA.dts and WBMRB.dts files leading to the following build error: mips-openwrt-linux-musl-cpp: error: ../dts/WBMRA.dts: No such file or directory mips-openwrt-linux-musl-cpp: warning: '-x assembler-with-cpp' after last input file has no effect mips-openwrt-linux-musl-cpp: fatal error: no input files Previously both the WBMRA and WBMRB profiles shared a common WBMR DT since the only difference is the embedded firmware kmod package. Extend the lantiqImage macro to optionally support specifying a different DTS file and use this facility to let the both WBMR profiles reference the correct device tree file. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: update kernel 4.4 to version 4.4.8Álvaro Fernández Rojas2016-04-241-1/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* image / basefiles: make console password configurableJohn Crispin2016-04-181-1/+1
| | | | | Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com> Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: use dwc2 by default on all ar9 boardsJohn Crispin2016-04-267-9/+9
| | | | | | | | | | | | The dwc2 USB driver now works on Lantiq ar9, but the default is still ltq-hcd-ar9. This patch switches to dwc2 by default. v2: all ar9 boards (v1 was just for BTHOMEHUBV3A and WBMR) Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 49254
* lantiq: install uboot-envtools by default on BTHOMEHUBV3AJohn Crispin2016-04-261-1/+1
| | | | | | | | | | | | | The only way to access the u-boot console on the BTHOMEHUBV3A is by soldering a serial console onto some really tiny pads. To enable installation without soldering it would be helpful to be able to modify the uboot environment from within the ramdisk image used as part of the installation process. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 49253
* lantiq: remove read-only flag on two partitions on BTHOMEHUBV3AJohn Crispin2016-04-261-2/+0
| | | | | | | | | | | Remove read-only flag on two partitions on BTHOMEHUBV3A: uboot-config - otherwise fw_setenv command cannot be used. ath9k-cal - so that ath9k calibration data can be copied to the partition on a newly installed board. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 49250
* lantiq: Fix typo in LED diag script.John Crispin2016-04-261-1/+1
| | | | | | | Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> Acked-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49242
* lantiq: use new image build process for brnImagesJohn Crispin2016-04-261-14/+28
| | | | | | | | | | | | | | LZMA compress the kernel without dictionary, otherwise brnboot fails to uncompress the kernel. The filesystem parameter of mkbrncmdline was dropped since the used filesystem isn't exported in the kernel build step and at least in my tests everything works without the parameter. If the parameter is required for some reason, the static keyword "squashfs" can be used. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49241
* lantiq: remove orphaned tp-link image build stepsJohn Crispin2016-04-261-22/+0
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49239
* lantiq: build sysupgrade images for lantiqImageJohn Crispin2016-04-261-0/+2
| | | | | | | | Tested with VGV7510KW22NOR. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49238
* lantiq: new image build process - fix kernel entry addressJohn Crispin2016-04-261-1/+1
| | | | | | | | | | | Set the kernel entry address to the same value as it is used for the old image build build process. Fixes boot of uImages on VGV7510KW22NOR and others. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49237
* lantiq: use new image build process for some imagesJohn Crispin2016-04-211-90/+95
| | | | | | | | | | This adds for some easy images the new build process. This was only tested on some TP-Link devices, please test. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 49210
* kernel: update kernel 4.4 to version 4.4.7Hauke Mehrtens2016-04-161-1/+1
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 49176
* lantiq-dsl: add missing blank in dsl outputJohn Crispin2016-04-091-1/+1
| | | | | | | | blank inserted before ACTATP Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com> SVN-Revision: 49137
* lantiq-dsl: bugfix latency values swapped for lucistatJohn Crispin2016-04-091-2/+2
| | | | | | | | swapped wrong latency output Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com> SVN-Revision: 49136
* lantiq-dsl: bugfix db negative sign after commaJohn Crispin2016-04-091-1/+1
| | | | | | | | If db is negative minus sign was shown after comma Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com> SVN-Revision: 49135
* lantiq: lzma-loader: fix O32 ABI conformanceGabor Juhos2016-03-211-0/+3
| | | | | | | | | | | | | | | | | | | According to the calling convention of the o32 ABI the caller function must reserve stack space for $a0-$a3 registers in case the callee needs to save its arguments. The assembly startup code does not reserve stack space for these registers thus when the main C function needs to save its arguments, that will cause a stack overflow. Fix the assembly code to reserve stack space for the registers to avoid that. Compile tested only. Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 49061
* lantiq: use upstream mechanism to append device tree fileJohn Crispin2016-03-206-69/+91
| | | | | | | | | | | Instead of using our patch-dtb program just place the device tree behind the kernel binary and then let the in kernel mechanism fetch it. This also adds support for having the device tree file in the boot loader. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 49050
* lantiq: print profile name in dsl lucistatFelix Fietkau2016-03-071-0/+1
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48949
* lantiq: add dsl firmware to default packagesFelix Fietkau2016-03-072-5/+5
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48942
* lantiq: do not set default firmware fileFelix Fietkau2016-03-071-1/+1
| | | | | | | | | We are now shipping a DSL firmware, do not set it by default to some file name. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48941
* kernel: update kernel 4.4 to version 4.4.3Hauke Mehrtens2016-02-253-6/+6
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48783
* use "-gt" instead of ">" with [ in /lib/functions/lantiq_dsl.shJohn Crispin2016-02-121-2/+2
| | | | | | | | | Avoids inadvertent file creation when executing `/etc/init.d/dsl_control status`. Signed-off-by: Jonathan A. Kollasch <jakllsch@kollasch.net> SVN-Revision: 48700
* lantiq: VGV7510KW22/VGV7519 update spi pinmux groupJohn Crispin2016-02-082-2/+2
| | | | | | | | | | | | | With the backport of the kernel 4.5 pinctrl-xway patches (3551609d & 826bca29) the pinmux group "spi" was splitted into "spi_di", "spi_do" & "spi_clk". But the no longer existing group "spi" is still used by some device tree source files. This fixes the detection of the wireless chipset of the VGV7510KW22. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48658
* lantiq: BTHOMEHUBV5A - explicit select the flash deviceJohn Crispin2016-02-081-1/+1
| | | | | | | | | | | | | The stock u-boot doesn't disable unused flash banks. Therefore, the nand driver tries to initialize a not connected NOR flash and the device hangs on boot. Workaround the issue by selecting the second flash bank (NAND). Signed-off-by: Mathias Kresin <openwrt@kresin.me> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48657
* lantiq: fix wrong parameter order in xway_nand driverJohn Crispin2016-02-081-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48656
* lantiq: Make the ar9.dtsi sram node match "simple-bus"Felix Fietkau2016-01-291-1/+1
| | | | | | | | | | | All other SoC types are using "lantiq,sram" and "simple-bus" to ensure that all child nodes are set up correctly during linux kernel initialization (plat_of_setup(void) in arch/mips/lantiq/prom.c). Without this some of sram child nodes might not be parsed. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48548
* lantiq: Move the definition of the xrx200-net node to vr9.dtsiFelix Fietkau2016-01-2911-764/+669
| | | | | | | | | | This removes a lot of duplicate register and interrupt definitions by moving the xrx200-net definition to vr9.dtsi and making all devices re- use it. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48547
* lantiq: fix PHY state handling issueFelix Fietkau2016-01-291-0/+38
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48546
* base-files: remove default /etc/config/network, generate it via board.d insteadFelix Fietkau2016-01-251-5/+0
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48493
* lantiq: Fix enabling CONFIG_MTD_UIMAGE_SPLITFelix Fietkau2016-01-201-1/+1
| | | | | | | | | | | | r48381 added CONFIG_MTD_SPLIT_UIMAGE_FW=Y to the lantiq kernel configuration. That unfortunately contains a typo since the "y" has to be lower-case. This leads to the kernel asking whether the config symbol should be enabled and thus breaking the build. FIXES: r48381/feab990887b4: lantiq: Enable the uImage mtd splitter Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48389
* lantiq: Enable the uImage mtd splitterFelix Fietkau2016-01-191-0/+1
| | | | | | | | | | | Until linux 4.1 the lantiq target used CONFIG_MTD_UIMAGE_SPLIT=y. That option however is only available until linux 4.3 - thus it was not added to lantiq's 4.4 kernel config (in r48307). This results in broken images for devices which are using uImages. This fixes #21652 Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48381
* lantiq: add support for TP-Link VR200vHauke Mehrtens2016-01-184-0/+297
| | | | | | | | | This adds basic support for TP-Link VR200v. Currently the following parts are not working: FXO, Voice, DECT, WIFI (both) Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48328
* lantiq: drop linux 4.1 supportFelix Fietkau2016-01-1839-21352/+0
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48323
* lantiq: switch to linux 4.4Felix Fietkau2016-01-181-1/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48322
* lantiq: fix VDSL device detection with Linux 4.4Felix Fietkau2016-01-181-1/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48319
* lantiq: Add support for linux 4.4Felix Fietkau2016-01-1835-0/+18096
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following patches were dropped because they are already applied upstream: - 0038-MIPS-lantiq-fpi-on-ar9.patch - 0039-MIPS-lantiq-initialize-usb-on-boot.patch - 0042-USB-DWC2-big-endian-support.patch - 0043-gpio-stp-xway-fix-phy-mask.patch All other patches were simply refreshed, except the following: - 0001-MIPS-lantiq-add-pcie-driver.patch Changes to arch/mips/lantiq/xway/sysctrl.c (these changes disabled some PMU gates for the vrx200 / VR9 SoCs) were removed since the upstream kernel disables unused PMU gates automatically (since 95135bfa7ead1becc2879230f72583dde2b71a0c "MIPS: Lantiq: Deactivate most of the devices by default"). - 0025-NET-MIPS-lantiq-adds-xrx200-net.patch Since OpenWrt commit 55ba20afcc2fe785146316e5be2c2473cb329885 drivers should use of_get_mac_address(). of_get_mac_address_mtd is not available for drivers anymore since it's called automatically within of_get_mac_address(). - 0028-NET-lantiq-various-etop-fixes.patch Same changes as in 0025-NET-MIPS-lantiq-adds-xrx200-net.patch While refreshing the kernel configuration SPI support had to be moved to config-4.4 because otherwise M25P80 was disabled. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48307
* lantiq: Remove incorrect PCIe compatible stringsFelix Fietkau2016-01-172-5/+0
| | | | | | | | | Re-defining the compatible property is not required since the correct value is inherited from vr9.dtsi. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48295
* lantiq: Remove the old SPI driver patchFelix Fietkau2016-01-171-1048/+0
| | | | | | Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48294
* lantiq: Switch to the new SPI driverFelix Fietkau2016-01-1710-35/+94
| | | | | | | | | | | | | | | | Compared to the "old" driver: - Each device must assign a pinctrl setting to the SPI node to allow the new SPI driver to configure the SPI pins. While here we are also using separate input and output settings so we are independent of whether the bootloader configures the pins correctly. - We use the new "compatible" strings to make the driver choose the correct number of chip-selects for each SoC. - The new driver starts counting the chip-selects at 1 (instead of 0, like the old one did). Thus we have to adjust the devices accordingly. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48293
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 03:57:32 +0000