aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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)
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 R7500Stefan 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 R7500 Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Jonas Gorski <jonas.gorski@gmail.com> (cherry picked from commit c228bbe616a52921a9d8fc961b3efcbdd3880c25)
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 D7800Stefan 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 D7800. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Tathagata Das <tathagata@alumnux.com> (cherry picked from commit 45b8a7c1a6415125f4fe872ec83b3d31a2fa799b)
* ipq806x: increase kernel partition size for the TP-Link Archer VR2600vStefan Lippers-Hollmann2018-05-243-7/+7
| | | | | | | | | | | | | | | | | | | The default image does not fit 2 MB anymore, expand kernel partition to 3 MB. Upgrading should work transparently via sysupgrade in both directions. Another option would be to merge "kernel" and "rootfs" into a single "firmware" partition using MTD_SPLIT_TPLINK_FW, but just changing the sizes of the existing partitioning has been deemed safer in the absence of an actual runtime test on an affected device; the maximum for rootfs changes from 10.4 MB to 9.4 MB. This change follows the example for the TP-Link Archer C2600, but has not been runtime tested on a TP-Link Archer VR2600v. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Sebastian Quilitz <zeraphim@x-pantion.de> (cherry picked from commit 0c967d92b3d9ca34f01f194ad0353f131b42e986)
* ipq806x: increase kernel partition size for the TP-Link Archer C2600Stefan Lippers-Hollmann2018-05-242-5/+10
| | | | | | | | | | | | | | | | | | | | The default image does not fit 2 MB anymore, expand os-image partition to 4 MB. Upgrading works transparently via sysupgrade in both directions. Another option would have been to merge "os-image" and "rootfs" into a single "firmware" partition using MTD_SPLIT_TPLINK_FW, but just changing the sizes of the existing partitioning has been deemed safer and actually tested on an affected device; the maximum for rootfs changes from 27 MB to 25 MB. Run-tested on TP-Link Archer C2600. Signed-off-by: Joris de Vries <joris@apptrician.nl> [slh: extend comments and commit message, rename rootfs] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit b72b36653a3fc8347456ab9c45d26a3144688a4c)
* ipq806x: increase kernel partition size for the Netgear r7800Stefan 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 patch is based on a corresponding change by Pavel Kubelun <be.dissent@gmail.com> and has been tested by Michael Yartys <michael.yartys@protonmail.com> Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit dc50694bd1a8f81b40c185bc8cacbdc8e821a3c6)
* ipq806x: cleanup kernel configRam Chandra Jangir2018-05-241-14/+8
| | | | | | | | | | | Disable MSM8960, MSM8974 and APQ8084 - since these are different SoC's than IPQ806x Removed unrequired serial configs - since ipq806x uses SERIAL_MSM only Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 7ac6697fe269e7915e2dd55ba872cffcc102338b)
* ipq806x: add kernel 4.14 supportRam Chandra Jangir2018-05-2468-0/+25602
| | | | | | | | | | | | | | | | | | | - Rebased the patches for 4.14 - Dropped spi-qup and 0027, 0028, 0029 clk patches since it's already included in upstream. Tested on IPQ AP148 Board: 1) NOR boot and NAND boot 2) Tested USB and PCIe interfaces 3) WDOG test 4) cpu frequency scaling 5) ethernet, 2G and 5G WiFi 6) ubi sysupgrade Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> (cherry picked from commit 93dd2f7211db6607184adadb488582e01fd5c29b)
* ipq40xx: add eva-image for FRITZ!Box 4040David Bauer2018-05-241-1/+4
| | | | | | | | | | This commit adds an EVA flashable image for the FRITZ!Box 4040. The image contains the U-Boot with OpenWRT appended to it. This way we remove the need to use UART for initial flashing. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 70e6ea319d3bfdfdb34be540dc7d89aa175b5587)
* build: add apend-uboot commandDavid Bauer2018-05-241-0/+4
| | | | | | | | This commit adds an append-uboot command to append U-Boot from the bin-directory. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 399495a952bf687d9c59226bddf4e73d3b42b30c)
* ramips: change wifi led trigger for Archer C50v3David Bauer2018-05-241-2/+2
| | | | | | | | | This commit alters the TP-Link Archer C50v3 LED settings to use the phy trigger instead of the netdev one. This way the WiFi status is displayed even if the wifi interface name is altered. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit ce91c85e01050cb19c89c9a19369a56a94619e7f)
* ramips: fix Archer C50v3 LED mappingDavid Bauer2018-05-241-4/+4
| | | | | | | | This commit fixes the wrong LED mapping of the Archer C50 v3. Commit was tested with an EU device. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 35d00d9a41ac369fd4be4e37998043f11ce80906)
* ar71xx: Add support for PISEN TS-D084Chuanhong Guo2018-05-2411-0/+117
| | | | | | | | | | | | | | | | | | | PISEN TS-D084 is an wireless router with a battery and integrated power supply based on Atheros AR9331. Specification: - 400/400/200 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 1x 10/100 Mbps Ethernet - 1T1R 2.4 GHz (AR9331) - 1x USB 2.0 Flash instruction: The manufacturer are using exactly the same firmware header as TP-LINK TL-WR703N (including device ID!). Simply upload the factory firmware into WebUI and flashing is done. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> (cherry picked from commit a789c0f49159c618d990541c23e00630f7296ebc)
* kernel: enable THIN_ARCHIVES by defaultSergey Ryazanov2018-05-2425-24/+1
| | | | | | | | | THIN_ARCHIVES option is enabled by default in the kernel configuration and no one target config disables it. So enable it by default and remove this symbol from target specific configs to keep them light. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 67a3cdcbb05559549985a189eabaf2df92559ed7)
* kernel: enable FUTEX_PI by defaultSergey Ryazanov2018-05-2425-24/+1
| | | | | | | | | | New FUTEX_PI configuration symbol enabled if FUTEX and RT_MUTEX symbols are enabled. Both of these symbols are enabled by default in the generic config, so enable FUTEX_PI by default too to keep platform specific configs minimal. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit bdc2b58c4bccb50242af853dc80b50f9324b841c)
* kernel: enable EXPORTFS by defaultSergey Ryazanov2018-05-2425-25/+1
| | | | | | | | | OVERLAY_FS config symbol selects EXPORTFS since 4.12 kernel, we have OVERLAY_FS enabled by default, so enable EXPORTFS in the generic config of 4.14 and remove this option from platform specific configs. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit a08b0d0c3149060f1585ad3ea2ea3edfde71bce4)
* kernel: disable DRM_LIB_RANDOM by defaultSergey Ryazanov2018-05-2425-24/+1
| | | | | | | | DRM_LIB_RANDOM config symbol selected only by DRM_DEBUG_MM_SELFTEST which is disable by default, so disable DRM_LIB_RANDOM by default too. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 978543a246c6badb5e5e1c2430211e01f005af27)
* kernel: disable DMA_{NOOP|VIRT}_OPS by defaultSergey Ryazanov2018-05-2425-48/+2
| | | | | | | | These options do not used by any supported arch, so disable them by default to make arch configs a bit more clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit ead26e9db649a508ba93e7e8193ada70322620b1)
* kernel: disable ARCH_WANTS_THP_SWAP by defaultSergey Ryazanov2018-05-2425-24/+1
| | | | | | | | | Only one arch (x86_64) enables this option. So disable ARCH_WANTS_THP_SWAP by default and remove referencies to it from all configs (except x86_64) to make them clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit f928c338ad6c8215a5fe280473e37786157a2d05)
* arc770: remove source-onlyEvgeniy Didin2018-05-241-1/+1
| | | | | | | | | | | | | | | In commit 8b9cdebc9c53 ("arc770: mark as source-only") arc770 was marked as source-only because of iproute2 compile issues. With uClibc-ng version 1.0.30 issues with iproute2 were fixed. Lets remove "source-only" for arc770 as soon as uClibc-ng version will be updated to 1.0.30. Patch for uClibc-ng is here: https://patchwork.ozlabs.org/patch/917547/ Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org> (cherry picked from commit a2418dba0214318f4ef22c5bd3f9204d0f092253)
* uClibc-ng: update to 1.0.30Evgeniy Didin2018-05-241-2/+2
| | | | | | | | | | | | | | | uClibc-ng 1.0.28 does not provide PF_VSOCK/AF_VSOCK definitions, which causes iproute2 v4.16.0 compile errors. In commit 57f2f80383b5 ("bits/socket.h: add missing defines") necessary defines were included and iproute2 builds fine. This commit now is part of uClibc-ng 1.0.30. Lets update uClibc-ng to latest 1.0.30 version. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org> (cherry picked from commit 83e926270361ca2cc7c773282bb1b57a5e67588f)
* ar71xx: Fix build for dap-1330-a1 boardHauke Mehrtens2018-05-241-1/+1
| | | | | | | | | | | | | | | | | Using a version number of 16 character causes a buffer overflow in the version number overwriting the first bit of the signature in the mkdapimg2 tool. I am not sure if the version number should be null terminated or not. This patch reduces the size of the version number by removing the number of private commits from it. This was the original version number which caused problems: OpenWrt-r6727+10 Now it uses this version number: OpenWrt-r6727 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit ae8ff1c65c4ea4e0b2e1e8ef94fad87587d979bc)
* ath25: drop 4.9 kernel supportSergey Ryazanov2018-05-2412-3850/+0
| | | | | Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 06116473cca4ee765978aa3035eab321cd57bd71)
* ath25: switch to 4.14 kernelSergey Ryazanov2018-05-241-1/+1
| | | | | Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 5191ea56218b5c7f17dbe5cdb6fb6895ee386156)
* ath25: add kernel 4.14 supportSergey Ryazanov2018-05-2412-0/+3865
| | | | | | | Copy and refresh patches and config from 4.9, no more work is need. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 3d69857ac1647e5bc924a9af1e8d00182316cb0d)
* kernel: whitespace fixesJohn Crispin2018-05-241-2/+0
| | | | | Signed-off-by: John Crispin <john@phrozen.org> (cherry picked from commit 22c16c5d823fa8de1c05837faf7b404405b8c74f)
* x86: disable CONFIG_EFI_VARSAlif M. Ahmad2018-05-241-1/+1
| | | | | | | | | | | Disable CONFIG_EFI_VARS, since it suffers from sysfs limitation (no support for variable longer than 1024 bytes). kmod-fs-efivarfs is the replacement of this, which enables mounting efivarfs file system and doesn't suffer from 1024 bytes limitation. Signed-off-by: Alif M. Ahmad <alive4ever@live.com> (cherry picked from commit b0a51dab8c5b8d40828a00b0c6d66450bf90f217)
* hostapd: fix IEEE 802.11r (fast roaming) defaultsGospod Nassa2018-05-241-21/+27
| | | | | | | | | | | | | | | | | | | | | | | | | Use ft_psk_generate_local=1 by default, as it makes everything else fairly trivial. All of the r0kh/r1kh and key management stuff goes away and hostapd fairly much does it all for us. We do need to provide nas_identifier, which can be derived from the BSSID, and we need to generate a mobility_domain, for which we default to the first four chars of the md5sum of the SSID. The complex manual setup should also still work, but the defaults also now work easily out of the box. Verified by manually running hostapd (with the autogenerated config) and watching the debug output: wlan2: STA ac:37:43:a0:a6:ae WPA: FT authentication already completed - do not start 4-way handshake This was previous submitted to LEDE in https://github.com/lede-project/source/pull/1382 [dwmw2: Rewrote commit message] Signed-off-by: Gospod Nassa <devianca@gmail.com> Signed-off-by: David Woodhouse <dwmw2@infradead.org> (cherry picked from commit 3cc56a5534b8b49a7e9ba57edf9878ec32bdd27a)
* wireguard: no longer need portability patchKevin Darbyshire-Bryant2018-05-242-19/+1
| | | | | | | | | | Drop package/network/services/wireguard/patches/100-portability.patch Instead pass 'PLATFORM=linux' to make since we are always building FOR linux. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> (cherry picked from commit f06def4221c25f4ee43d31c2b90a1371ba4d6d33)
* ramips: add support for YUKAI Engineering Inc. BOCCOYuheiOKAWA2018-05-245-0/+174
| | | | | | | | | | | | | | BOCCO is a communication robot provided by YUKAI Engineering Inc. SoC: MT7620A MEM: 256MB Flash: 8MB NAND: 512MB (non support) Include Sound DAC and AMP. No Wired Ethernet. Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com> (cherry picked from commit d91953cb5351f1ab3e75ae9e2d9622f754d518ed)
* ar71xx: WNDR3700: enable RFKILL function for Wifi buttonMichal Cieslakiewicz2018-05-241-4/+4
| | | | | | | | | | | | | | | | | | Wifi button for WNDR3700 dual band routers has been renamed to "rfkill" and its emitted keycode changed to KEY_RFKILL. This allows OpenWrt/LEDE to support it 'out of the box' without additional tweaking. Until this patch, button had been sending BTN_2 keycode which was ignored by default (no action script present). To get expected behaviour of switching radios on and off, user had to manually rename/link 'rfkill' script to name 'BTN_2' in /etc/rc.button directory. This patch follows similar changes for other Netgear ar71xx routers, for example WNR2000v3. It applies cleanly to both latest trunk and 17.01 branch. Tested on WNDR3700v1. Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> (cherry picked from commit 45dc530334d8694a962d0833432effd14fa5cc4a)
* brcm2708: add squashfs rootfs imageChristian Lamparter2018-05-246-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds a image with squashfs as the root filesystem. A rootfs_data partition will be generated on the first boot and placed inside the rootfs partition (just after the squashfs image). advantages: - it is possible to migrate from an existing -ext4 installation and back via sysupgrade. - existing partition layout will not be lost. - slightly smaller image size. - support for attendedsysupgrade disadvantages: - needs f2fs + tools as well. This is because fs-tools decides on the blocksize of the sdcard. So either f2fs or ext4 can get choosen as the rootfs_data filesystem (depends on the size of the root partition). - rootfs_data is placed into the rootfs partition. This makes it difficult for tools that expect a /dev/mmc0pX device. It also makes it difficult for data recovery tools since they might not expect to find a embedded partition or will be confused. For people with existing build configurations: make sure to include mkf2fs and f2fsck package into the image... Otherwise the new -squashfs image will boot of a ram-overlay and won't keep the configurations after a reboot. Cc: Álvaro Fernández Rojas <noltari@gmail.com> Cc: Paul Spooren <spooren@informatik.uni-leipzig.de> Cc: Daniel Golle <daniel@makrotopia.org> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Acked-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 707b6c815bba34e9783d2695020bb17385fdcf1d)
* x86: Add APU3 reference to x86 board.dKristian Evensen2018-05-242-2/+2
| | | | | | | | | | | | There is a new APU-model available, APU3. The device is configured in the same way as the APU1 and APU2, so the same LED/network setup can be used. I considered changing the case to pc-engines-apu*, but I chose to follow the existing pattern and add the full board name. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com> (cherry picked from commit 8f9baf5e1a9300fe66ff90486182a1fd2e645d9e)
* apm821xx: backport and reassign crypto4xx patchesChristian Lamparter2018-05-2413-12/+1268
| | | | | | | | | | | | | | | | | | | | | This patch backports several patches that went upstream into Herbert Xu's cryptodev-2.6 tree: crypto: Use zeroing memory allocator instead of allocator/memset crypto: crypto4xx - performance optimizations crypto: crypto4xx - convert to skcipher crypto: crypto4xx - avoid VLA use crypto: crypto4xx - add aes-ctr support crypto: crypto4xx - properly set IV after de- and encrypt crypto: crypto4xx - extend aead fallback checks crypto: crypto4xx - put temporary dst sg into request ctx The older, outstanding patches from 120-wxyz series have been upstreamed as well and therefore they have been reassigned to fit into the series. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 16e39624b728264bd4759580f6292bffefcae466)
* apm821xx: don't select swconfig for the MR24Christian Lamparter2018-05-241-1/+1
| | | | | | | | | | | The swconfig package is part of the DEFAULT_PACKAGES list in the apm821xx's nand subtarget. It's enabled by default because the MX60(W) and WNDR4700 need it for their initramfs. However the package is not necessary for the MR24's sysupgrade image, as the MR24 does not have a switch. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit e6e51ce87fac2d6b9d082336f8d767f12154d79b)
* ipq40xx: fix ethernet on ap-dk01.1Roman Yeryomin2018-05-241-0/+25
| | | | | | | | Not sure how it worked before but ethernet is disabled by default in ipq4019 dtsi. Signed-off-by: Roman Yeryomin <roman@advem.lv> (cherry picked from commit 1f42deec8edac3e99f83f7343cbd4fec29333345)
* brcm63xx: Tune the network configuration for several routersDaniel Gonzalez Cabanelas2018-05-241-3/+7
| | | | | | | | | - DGND3700v1: fix port numbers, they're in reverse order - FaST2704n: there is no WAN port identified as such, only 4 LAN - AD1018: configure the "FIBRE" port as WAN Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> (cherry picked from commit fbbb97777297bf8a168b840c88d18d6e2079ce8f)
* ltq-xdsl-app: start after led scriptMathias Kresin2018-05-242-3/+2
| | | | | | | | | | | | | During handshake we are highjack and reset a LED to the configured trigger afterwards. ltq-xdsl-app need to start after the LED init script, to ensure that the LED init script doesn't re-highjack the LED we are currently using for handshake indication. Drop the comment about the atm dependency. The dependency was fixed quite some time ago by using hotplug scripts for br2684ctl. Signed-off-by: Mathias Kresin <dev@kresin.me> (cherry picked from commit 0678cc850ccc068ba33eb87f5f1bf8294a87e611)
* tools: zlib: do not hardcode the install prefix in zlib.pcJo-Philipp Wich2018-05-241-0/+14
| | | | | | | | | | | | | | | | | | Our pkg-config wrapper relies on the ability to redefine the $prefix and $exec_prefix variables in order to construct proper search paths relative to the build environment. Patch the .pc file template to construct libdir, sharedlibdir and includedir relative to the ${prefix} variable so that it can be overridden as needed. This also fixes the libxml2/host build issue raised at https://github.com/openwrt/packages/issues/6073 - it was caused by libxml2's configure picking up a wrong host search path through zlib.pc, letting it include the wrong endian.h, causing spurious member redeclaration errors in system headers. Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 4da832e201da2493b66024f234a78a2249af4aff)
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-30 23:03:00 +0000