aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.14 to 4.14.49 for 18.06Koen Vandeputte2018-06-183-9/+9
| | | | | | | | | Refreshed all patches Compile-tested on: cns3xxx, imx6, x86-64 Runtime-tested on: cns3xxx, imx6, x86-64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.108 for 18.06Koen Vandeputte2018-06-188-171/+193
| | | | | | | | | Refreshed all patches Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: add support for TP-Link TL-WR842N v5Maxim Anisimov2018-06-166-1/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link TL-WR842N v5 are simple N300 router with 5-port FE switch and non-detachable antennas. Its very similar to TP-Link TL-MR3420 V5. Specification: - MT7628N/N (580 MHz) - 64 MB of RAM (DDR2) - 8 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - USB 2.0 Port - UART (J1) header on PCB (115200 8n1) - 7x LED, 2x button, power input switch Flash instruction: The only way to flash OpenWrt image in wr842nv5 is to use tftp recovery mode in U-Boot: 1. Configure PC with static IP 192.168.0.225/24 and tftp server. 2. Rename "lede-ramips-mt7628-tplink_tl-wr842n-v5-squashfs-tftp-recovery.bin" to "tp_recovery.bin" and place it in tftp server directory. 3. Connect PC with one of LAN ports, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. 4. Router will download file from server, write it to flash and reboot. Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
* ramips: use phytpt trigger for mt76 wirelessDavid Bauer2018-06-161-4/+4
| | | | | | | | | | | | | With this change, the LED trigger is independent from the (wireless) netdev name. The (wireless) netdev name can be easiliy changed in OpenWrt and would require an update of the netdev trigger settings each time it is done. This change is (for now) applied only to MT7628 devices from TP-Link, as we only had the possibility to test this change against two of those devices, namely a TL-WR841 v13 and a Archer C50 v3. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: fix mt7688 watchdog register base addrlbzhung2018-06-161-2/+2
| | | | | | | | | | | | | I found mt7688 watchdog not working. The watchdog registers are identical for mt7621 and mt7628/mt7688. The first watchdog related register is at 0x10000100, the last one - a 16bit sized - at 0x10000128. Set the correct register address and size in the dtsi file to get the watchdog working. Signed-off-by: lbzhung <gewalalb@gmail.com> [add commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: fix conntrack fixup of offloaded flows on timeoutFelix Fietkau2018-06-143-9/+33
| | | | | | Fixes excessively long conntrack timeout of short lived connections Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix conntrack leak for flow_offload connectionsFelix Fietkau2018-06-143-28/+123
| | | | | | | This was caused by a race condition between offload teardown and conntrack gc bumping the timeout of offloaded connections Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: allow hardware NAT offload drivers to keep a priv pointerFelix Fietkau2018-06-141-0/+25
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: fix network config for ravpower wd03Matthias Badaire2018-06-091-1/+1
| | | | | | | | This device has only one ethernet port. Signed-off-by: Matthias Badaire <mbadaire@gmail.com> [add the existing eth0 as lan block, shorten commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: use Power-LED as Diag-LED on FRITZBox 4020David Bauer2018-06-092-1/+1
| | | | | | | This commit makes use of the Power-LED as Diag-LED, allowing the LED to work as a status indicator. Signed-off-by: David Bauer <mail@david-bauer.net>
* ar71xx: fix AVM package selectionDavid Bauer2018-06-091-2/+2
| | | | | | | The AVM package selection partially broke with the addition of the FRITZ!Box 4020. This commit restores the intended behavior. Signed-off-by: David Bauer <mail@david-bauer.net>
* ar71xx: fix USB switch to mPCIE for Mikrotik rb91x boardsKoen Vandeputte2018-06-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some devices like the Mikrotik RB912 only have 1 USB port which is shared between an USB A type port, and the mini PCIe socket. Toggling a gpio selects the output to which USB is connected. Since kernel 4.9, gpio base is rounded up to a value of 32. Commit 65da6f9ca164 ("ar71xx: fix secondary gpio controller base values") accounts correctly for that. In this commit, rb912 sees it's value changed from AR934X_GPIO_COUNT (23) to 32 This means that the USB toggle gpio number actually also changes from 52 to 61. But .. Some of these GPIO numbers are also used in other locations, like the boardfile. The author forgot to also change them over there. Switching the USB port to mPCIe now shows my modem is correctly discovered again: [ 2863.864471] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 2864.055303] usb 1-1: config 1 has an invalid interface number: 8 but max is 3 [ 2864.062728] usb 1-1: config 1 has no interface number 1 [ 2864.074567] qcserial 1-1:1.0: Qualcomm USB modem converter detected [ 2864.081474] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0 [ 2864.111960] qcserial 1-1:1.2: Qualcomm USB modem converter detected [ 2864.118976] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB1 [ 2864.139808] qcserial 1-1:1.3: Qualcomm USB modem converter detected [ 2864.146777] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB2 [ 2864.165276] qmi_wwan 1-1:1.8: cdc-wdm0: USB WDM device [ 2864.171879] qmi_wwan 1-1:1.8 wwan0: register 'qmi_wwan' at usb-ehci-platform-1, WWAN/QMI device, 02:00:44:ed:3b:11 Fixes: 65da6f9ca164 ("ar71xx: fix secondary gpio controller base values") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Cc: Robin Leblon <robin.leblon@ncentric.com> Cc: Felix Fietkau <nbd@nbd.name> (cherry picked from commit 55b4b1eba0af6d2240f48eb93d68fb2e9ff41b08)
* kernel: fix 811-pci_disable_usb_common_quirks.patchStijn Tintel2018-06-071-11/+12
| | | | | | | | | | The kernel bump wrongly modified the patch generic/pending-4.14/811-pci_disable_usb_common_quirks.patch. Sync it from master. Fixes: 1199a9109526 ("kernel: bump 4.14 to 4.14.48 for 18.06") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.14 to 4.14.48 for 18.06Stijn Segers2018-06-0786-1241/+956
| | | | | | | | | | | | | | Refreshed patches. The following patches were upstreamed and have been deleted: * target/linux/lantiq/patches-4.14/0025-MIPS-lantiq-gphy-Remove-reboot-remove-reset-asserts.patch * target/linux/generic/pending-4.14/101-clocksource-mips-gic-timer-fix-clocksource-counter-w.patch * target/linux/generic/pending-4.14/103-MIPS-c-r4k-fix-data-corruption-related-to-cache-coherence.patch * target/linux/generic/pending-4.14/181-net-usb-add-lte-modem-wistron-neweb-d18q1.patch Compile-tested: ramips/mt7621, x86/64 Run-tested: ramips/mt7621 Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* kernel: bump 4.9 to 4.9.106 for 18.06Stijn Segers2018-06-0734-604/+398
| | | | | | | | | | | Refreshed patches. The following patches were upstreamed and have been deleted: * target/linux/ar71xx/patches-4.9/106-01-MIPS-ath79-fix-AR724X_PLL_REG_PCIE_CONFIG-offset.patch * target/linux/generic/pending-4.9/180-net-phy-at803x-add-support-for-AT8032.patch * target/linux/generic/pending-4.9/181-net-usb-add-lte-modem-wistron-neweb-d18q1.patch * target/linux/generic/pending-4.9/182-net-qmi_wwan-add-BroadMobi-BM806U-2020-2033.patch Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* ar71xx: switch CPE/WBS 210/510 to okli-loaderMatthias Schiffer2018-06-061-1/+4
| | | | | | | | | | | | | | | | | | | | | We recently increased the kernel partition size of the CPE/WBS 210/510. This works fine for new installations of the factory image, but on sysupgrades, the partition table read by the bootloader is not adjusted. This limits the maximum size of the kernel loaded by the bootloader to the old partition size. While adjusting the partition table would be a cleanest solution, such a migration would have to happen before an upgrade to a new version with a newer kernel. This is error-prone and would require a two-step upgrade, as we mark the partition table partition read-only. Instead, switch from the lzma-loader with embedded kernel to the okli-loader, so only the tiny lzma-loader is loaded by the bootloader as "kernel", and the lzma-loader will then load the rest of the kernel by itself. Fixes: e39847ea2f70 ("ar71xx: increase kernel partition size for CPE/WBS 210/510") Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: make loader-okli build step more genericMatthias Schiffer2018-06-061-2/+3
| | | | | | Add support for different loader types. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: constify kernel argv arrayMatthias Schiffer2018-06-061-1/+1
| | | | | | | By making the kernel argv array const, the .data section can always be omitted from the laoder binary. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: set page size to 4KBMatthias Schiffer2018-06-061-1/+1
| | | | | | | | The text section in the ELF loader is aligned to the maximum page size, which defaults to 64KB. Reduce it to the actual page size to avoid wasting flash space for this alignment. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: move padding workaround to gzip stepMatthias Schiffer2018-06-062-2/+5
| | | | | | | | | | | | | | | | | | | | | | | Some devices (TP-Link TL-WR1043ND v1) don't boot reliably when the uncompressed loader is too small. This was workarounded in the loader by adding 512KB of padding to the .data section of the loader binary. This approach had two issues: - The padding was only working when .data was non-empty (otherwise the section would become NOBITS, omitting it in the binary). .data was only empty when no CMDLINE was set, leading to further workarounds like fe594bf90d09 ("ath79: fix loader-okli, lzma-loader"), and this workaround was only effective because a missing "const" led to the kernel argv being stored in .data instead of .rodata - The padding was not only added to the compressed .gz loader, but also uncompressed .bin and .elf loaders. The prevented embedding the kernel cmdline in the loader for non-gz loader types. To fix both issues, move the creation of the padding from the linker script to the gzip step. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* kernel: backport patch to fix dst handling for offloaded connectionsFelix Fietkau2018-06-051-0/+49
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* Revert "ramips: Move PCI driver to files directory"John Crispin2018-06-012-837/+842
| | | | | | This reverts commit a098a78a33a6b096d15c9982b5d6457988e09f03. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: Remove redundant owner assignment"John Crispin2018-06-011-0/+1
| | | | | | This reverts commit 2ad4daf5794b08878467c1dac5bef7487109e4da. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: improve interrupt mapping"John Crispin2018-06-012-14/+69
| | | | | | This reverts commit 5f7396ebef09b224edf08b0bda113613a42f0928. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: remove conditional compilation."John Crispin2018-06-011-8/+58
| | | | | | This reverts commit 1f786257147f978ce4c5750fdc404851453fafcb. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: remove unnecessary resource details."John Crispin2018-06-011-2/+15
| | | | | | This reverts commit edea934799911c54ffa7024ef9a650f9dfc8c695. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: pci: sync with staging driver"John Crispin2018-06-011-150/+168
| | | | | | This reverts commit e07baec9faf487fd143976636025b5da55e13c20. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928"John Crispin2018-06-0121-0/+82
| | | | | | This reverts commit 8ccdf809c0de567cfb781f38ce1c897b04cbeb78. Signed-off-by: John Crispin <john@phrozen.org>
* mvebu: fix broken console on WRT32X (venom)Michael Gray2018-06-013-0/+208
| | | | | | | | | | | | | | | | The console bootarg is being corrupted on boot, causing various issues including broken sysupgrade. Utilising the bootargs mangle patch from other targets, hardcode the console arguments and fetch the rootfs from the bootloader. Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8 Bootloader command line (ignored): console= root=/dev/mtdblock8 Please cherry pick to 18.06 too Signed-off-by: Michael Gray <michael.gray@lantisproject.com> (cherry picked from commit 4fdc6ca31bda4aad2a65b8460b0caa5c60f87f41)
* ramips: Use generic board detect for GnuBee devicesRosen Penev2018-05-306-9/+6
| | | | | | | | | | | | This is a port of an old commit from mkresin's tree: 09260cdf3e9332978c2a474a58e93a6f2b55f4a8 This has the potential to break sysupgrade but it should be fine as there is no stable release of LEDE or OpenWrt that support these devices. Signed-off-by: Rosen Penev <rosenp@gmail.com> (cherry picked from commit 9685f3978795727ac99d5d20a4af16c808b1e24b)
* ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928Rosen Penev2018-05-3021-82/+0
| | | | | | | | | | | | | | That commit exposed a bug in the DTS files used by mt7621 where the wrong reg value for pcie1 (and potentially pcie2) was being used. This was causing WiFi failures for interfaces in pcie1. eg. 2.4GHz working but not 5GHz. As all of these dts entries are already specified in mt7621.dtsi, remove them. Signed-off-by: Rosen Penev <rosenp@gmail.com> (cherry picked from commit 02f815d1907cdd7e042415a2b4a749c819087168)
* target/linux: drop anything not on v4.9 or v4.14John Crispin2018-05-24342-33516/+0
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ath79: drop, its not ready for a release yetJohn Crispin2018-05-24119-21040/+0
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ramips: Fix up GnuBee PC1 DTS file a littleRosen Penev2018-05-241-7/+1
| | | | | | | | | There's nothing connected to i2c on this board, so remove it. Also edited the gpio group to match the PC2 as they're the same. Signed-off-by: Rosen Penev <rosenp@gmail.com> (cherry picked from commit 8c818fa1f0507b0e17aa3ebf051439c9c65f78f3)
* brcm47xx: add switch port mapping to Asus WL-500WMirko Parthey2018-05-241-1/+1
| | | | | | | | | | | | Switch ports 0..3 are connected to external ports LAN{1..4} in sequence, switch port 4 is not used, and switch port 5 is connected to the CPU. The WAN port is attached to the CPU's second network interface; it has no connection to the internal switch. Reuse the "Dell TrueMobile 2300" entry, which describes the same mapping. Signed-off-by: Mirko Parthey <mirko.parthey@web.de> (cherry picked from commit 7ac238fc9855d20f0cfbc5754a1f9591438abfe3)
* ipq806x: drop "mtd: nand: add Winbond manufacturer and chip"Stefan Lippers-Hollmann2018-05-241-38/+0
| | | | | | | The W25N01GV NAND is currently not used in any ipq806x device. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit a436ef992d26768652e5a76d9e0983377adfc89b)
* ipq806x: drop linux 4.9 supportStefan Lippers-Hollmann2018-05-2487-29438/+0
| | | | | Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 2819732219904a81205abe0fa3fbe9c06884f119)
* ipq806x: switch to linux 4.14Stefan Lippers-Hollmann2018-05-241-1/+1
| | | | | Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 18e9ed2482d6988b5962e856ec0792d5794ad93f)
* ipq806x: remove spi-nor from r7800 dtsPavel Kubelun2018-05-242-90/+0
| | | | | | | | | | There's no spi-nor in R7800, so disable unequipped interfaces. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 8c1c1c4874c3bcaa16a21257a8fe15c2f6ec4012)
* ipq806x: remove rpm pinctrl from board dtsPavel Kubelun2018-05-2416-80/+0
| | | | | | | | | | | These pins seem to be used by hw exclusively, so claiming it in kernel causes an error in syslog in k4.14+. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 96cd31655d3de9078036ff74562ee50ef8724318)
* ipq806x: fix EA8500 switch controlPavel Kubelun2018-05-242-8/+36
| | | | | | | | | | | | | | | | | | | EA8500 has pcie2 slot unequipped. By EA8500 hw design default pcie2 reset gpio (gpio63) is used to reset the switch. That's why enabling pcie2 brings the switch into a working state. So let's just control the gpio63 without enabling the pcie2 slot. We have to remove the pcie2_pins node so the gpio63 is not defined twice. Because pcie2 node has a reference to pcie2_pins we have to remove it as well. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 7f694ef3d9f1121c03935c330093c594b8437098)
* ipq806x: move mmc specific nodes into v1.0 dtsiPavel Kubelun2018-05-244-150/+150
| | | | | | | | | | | These nodes are common for all revisions so put it into SoC v1.0 dtsi file. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 7a4f9c5993a726a3009a93dcd6aacb93d2aea6e1)
* ipq806x: fix pcie tx termination offsetPavel Kubelun2018-05-242-0/+24
| | | | | | | | | | | | | | | | According to GPL tarballs and QSDK related branch tx termination offset for ipq8064 SoC version >= 2.0 should be equal to 0 and not 7. https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L1682-L1685 Fix this. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit fbedc2213c19023bb4ec4ed7bd71908501aaf6d1)
* ipq806x: apply updated USB PHY settings to v2.0 SoCPavel Kubelun2018-05-244-22/+34
| | | | | | | | | | | | | | | | | | | | | USB PHY power settings introduced for ipq8065 SoC with commit 644a0d5 "ipq8065: adjust SS USB PHY power settings" According to that commit msg and in correspondence to GPL tarballs and related QSDK branch those settings are applied to ipq8064 SoCs of version >= 2.0. https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L2507-L2514 Now as we have clarified that mass market boards are of SoC v2.0 move those USB PHY settings from ipq8065 (v3.0 SoC) dtsi to ipq8064 v2.0 dtsi. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit d4b98c38c6acdabf37c9d099be5e2c3cf06a05fb)
* ipq806x: reference ipq8065 as ipq8064 v3.0Pavel Kubelun2018-05-248-8/+6
| | | | | | | | | | | | | ipq8065 is ipq8064 v3.0 > socinfo_init: v6, id=280, ver=3.0, raw_id=17, raw_ver=17, hw_plat=0, hw_plat_ver=65536 Include dtsi accordingly and remove the unneeded qcom-ipq8065-v1.0.dtsi Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit e16f9abf6b5b5d56d83892d7d86d89023f1e5d42)
* ipq806x: move mass market ipq8064 to v2 dtsiPavel Kubelun2018-05-2410-10/+10
| | | | | | | | | | | | | | | | | | | According to OEM bootlog entry mass market devices are ipq8064 SoC v2.0: > socinfo_init: v6, id=202, ver=2.0, raw_id=2064, raw_ver=2064, hw_plat=0, hw_plat_ver=65536 I've checked C2600, EA8500 and VR2600v but couldn't find other boards bootlog. I think it's safe to assume that other boards are also v2.0. R7500 may be an exception because it was the first device to hit the market. So switch to v2.0 dtsi. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 067036e8750a61a700718bf874e52b18a11cb277)
* ipq806x: introduce ipq8064 SoC v2 dtsiPavel Kubelun2018-05-242-0/+2
| | | | | | | | | | | | | | | | | According to QCA internal numbering there are 3 versions of ipq8064/5 SoC: ipq8064 v1.0 - probably ipq8064 evaluation boards only ipq8064 v2.0 - probably ipq8064 mass market boards only ipq8064 v3.0 - aka ipq8065, boards based on ipq8065. Each next revision includes configuration differences from previous revision and adds something new. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit adbdf780492c0b877057ffb6765d0329adcbd2be)
* kernel: iqp806x low latency kernel does not bootMarc Benoit2018-05-242-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It keeps failing (R7800) with the stack trace below BUG: scheduling while atomic: kworker/0:1/26/0x00000002 (unwind_backtrace) from [<c02121d0>] (show_stack+0x10/0x14) (show_stack) from [<c03932e4>] (dump_stack+0x7c/0x9c) (dump_stack) from [<c0239b90>] (__schedule_bug+0x5c/0x80) (__schedule_bug) from [<c05b7260>] (__schedule+0x50/0x3f4) (__schedule) from [<c05b76a8>] (schedule+0xa4/0xd4) (schedule) from [<c05ba430>] (schedule_hrtimeout_range_clock+0xc8/0x100) (schedule_hrtimeout_range_clock) from [<c05ba480>] (schedule_hrtimeout_range+0x18/0x20) (schedule_hrtimeout_range) from [<c05b9f78>] (usleep_range+0x48/0x50) (usleep_range) from [<c03f333c>] (__clk_hfpll_enable+0x44/0xd0) (__clk_hfpll_enable) from [<c03f3474>] (clk_hfpll_set_rate+0xac/0xc4) (clk_hfpll_set_rate) from [<c03ec390>] (clk_change_rate+0xf4/0x1fc) (clk_change_rate) from [<c03ec510>] (clk_core_set_rate_nolock+0x78/0x94) (clk_core_set_rate_nolock) from [<c03ec54c>] (clk_set_rate+0x20/0x30) (clk_set_rate) from [<c0424168>] (dev_pm_opp_set_rate+0x190/0x26c) (dev_pm_opp_set_rate) from [<c04a8548>] (set_target+0x40/0x108) (set_target) from [<c04a4.140>] (__cpufreq_driver_target+0x3f4/0x488) (__cpufreq_driver_target) from [<c04a7494>] (od_dbs_timer+0xcc/0x154) (od_dbs_timer) from [<c04a7998>] (dbs_work_handler+0x2c/0x54) (dbs_work_handler) from [<c02309e8>] (process_one_work+0x1c0/0x2f0) (process_one_work) from [<c02319a8>] (worker_thread+0x2a4/0x404) (worker_thread) from [<c0235944>] (kthread+0xd8/0xe8) (kthread) from [<c020eef0>] (ret_from_fork+0x14/0x24) Signed-off-by: Marc Benoit <marcb62185@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit e40db2907e2a7d4837b25be3bedb1f25fc248bbf)
* ipq806x: define KERNEL_SIZE in KB instead of byte for the image generationStefan Lippers-Hollmann2018-05-241-5/+5
| | | | | Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 05f53eecca5e1b28706ef074477a55917ed6deb1)
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 R7500v2Stefan Lippers-Hollmann2018-05-243-7/+7
| | | | | | | | | | | | | | | | | | | Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the 2 MB reserved for the kernel partition by the OEM firmware anymore. This patch increases the kernel partition from 2 MB to 4 MB, at the expense of the rootfs, for all supported kernels. WARNING: This breaks sysupgrade! Flashing a firmware containing this changed partitioning from an older image with 2 MB reserved for the kernel partion requires the tftp recovery procedure, thereby losing all settings. This change follows the functional example of the Netgear r7800, but has not been runtime tested on a Netgear Nighthawk X4 R7500v2. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit c3af761e4740820a29e993414d3d2f49c7eff6e7)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 21:12:04 +0000