aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/patches-4.4
Commit message (Collapse)AuthorAgeFilesLines
* kernel: update kernel 4.4 to version 4.4.9Álvaro Fernández Rojas2016-06-201-2/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: update kernel 4.4 to version 4.4.8Álvaro Fernández Rojas2016-06-201-1/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* lantiq: add device tree binding for the phy clock sourceJohn Crispin2016-06-191-0/+30
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49283 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: handle the dual-firmware layout of brnbootJohn Crispin2016-06-191-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> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49281 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: use the same functionality for all ethernet phys ledJohn Crispin2016-06-191-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49270 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: fix minor typos in 11G/22F phy driverJohn Crispin2016-06-191-2/+2
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49269 3c298f89-4303-0410-b956-a3cf2f4a3e73
* kernel: update kernel 4.4 to version 4.4.7Hauke Mehrtens2016-04-161-1/+1
| | | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49176 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: use upstream mechanism to append device tree fileJohn Crispin2016-03-204-63/+85
| | | | | | | | | | | 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> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49050 3c298f89-4303-0410-b956-a3cf2f4a3e73
* kernel: update kernel 4.4 to version 4.4.3Hauke Mehrtens2016-02-253-6/+6
| | | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48783 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: fix wrong parameter order in xway_nand driverJohn Crispin2016-02-081-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48656 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: fix PHY state handling issueFelix Fietkau2016-01-291-0/+38
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48546 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add support for linux 4.4Felix Fietkau2016-01-1834-0/+17892
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> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48307 3c298f89-4303-0410-b956-a3cf2f4a3e73