summaryrefslogtreecommitdiff
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* 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)
* 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-241-3/+3
| | | | | | | | | | | | | | | | | | | | 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)
* 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)
generated by cgit v1.1 at 2024-07-10 21:50:40 +0000