aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/layerscape
Commit message (Collapse)AuthorAgeFilesLines
* layerscape: image: drop redundant parameter from kernel build recipePiotr Dymacz2022-04-011-2/+2
| | | | | | | Neither 'fit', nor target-specific 'traverse-fit' build recipes accept FDT load address in 3rd parameter. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* layerscape: make boot filesystem reproducibleDaniel Golle2022-03-281-1/+3
| | | | | | | Set timestamp option for make_ext4fs to make boot filesystem reproducible. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: delete Linux 5.4 config and patchesDaniel Golle2022-03-21892-311507/+0
| | | | | | | | As the upcoming release will be based on Linux 5.10 only, remove all kernel configuration as well as patches for Linux 5.4. There were no targets still actively using Linux 5.4. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: 5.10: remove CONFIG_DEVTMPFS{,_MOUNT} from kconfigsRui Salvaterra2022-03-012-4/+0
| | | | | | They are required for container support, but are handled in Config-kernel.in. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.4 to 5.4.174John Audia2022-01-287-48/+6
| | | | | | | | | | | | | | Removed upstreamed patches: layerscape/patches-5.4/302-dts-0083-arm64-ls1028a-qds-correct-bus-of-rtc.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.174&id=65816c1034769e714edb70f59a33bc5472d9e55f Build system: x86_64 Build-tested: ramips/mt7621 Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: switch to 5.10 KernelPaul Spooren2022-01-191-1/+1
| | | | | | | Tested by multiple users and since all targets need to be on Kernel 5.10 to be part of the next release, add changes. Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 5.4 to 5.4.172John Audia2022-01-161-1/+1
| | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.169John Audia2022-01-032-3/+3
| | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *Had to revert 7f1edbd in order to build due to FS#4149 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-172-4/+0
| | | | | | | | | | | | | | | | | | | | | | Each of - CRYPTO_AEAD2 - CRYPTO_AEAD - CRYPTO_GF128MUL - CRYPTO_GHASH - CRYPTO_HASH2 - CRYPTO_HASH - CRYPTO_MANAGER2 - CRYPTO_MANAGER - CRYPTO_NULL2 either directly required for mac80211 crypto support, or directly selected by such options. Support for the mac80211 crypto was enabled in the generic config since c7182123b9 ("kernel: make cryptoapi support needed by mac80211 built-in"). So move the above options from the target configs to the generic config to make it clear why do we need them. CC: Felix Fietkau <nbd@nbd.name> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: filter out both Clang and LLD versionsSergey Ryazanov2021-12-172-2/+0
| | | | | | | | Both CLANG_VERSION and LLD_VERISON are autogenerated runtime configuration options, so add them to the kernel configuration filter and remove from generic and per-target configs to keep configs clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: bump 5.4 to 5.4.167John Audia2021-12-171-1/+1
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *FS#4149 affects me so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.165John Audia2021-12-1727-88/+88
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *FS#4149 affects me so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: armv7: refresh config-5.10Martin Schiller2021-12-131-24/+30
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv7: copy config-5.4 to config-5.10Martin Schiller2021-12-131-0/+673
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: refresh config-5.10Martin Schiller2021-12-131-99/+71
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: copy config-5.4 to config-5.10Martin Schiller2021-12-131-0/+881
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: use non-SDK dts files for linux-5.10 or newerMartin Schiller2021-12-131-0/+24
| | | | | | | Since we decided to drop the LSDK patches with linux-5.10, we now have to switch to the corresponding upstream dts files as well. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: armv8_64b: fix KERNEL_LOADADDR for linux >= 5.8Martin Schiller2021-12-131-0/+4
| | | | | | | | | | In kernel versions newer than 5.8 the arm64 TEXT_OFFSET (0x80000) has been set to 0x0 (and later removed). This will break Uimages with kernel load addresses that aren't 2MiB aligned any longer. Resulting in the kernel silently fail to boot. For layerscape armv8_64b targets this needs to be changed to 0x80000000 (start of RAM). Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: add patches for kernel 5.10Martin Schiller2021-12-135-0/+12680
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: add kernel 5.10 as testing versionMartin Schiller2021-12-131-0/+1
| | | | | | | This patch adds "KERNEL_TESTING_PATCHVER:=5.10" to the Makefile in layerscape target to allow using Kernel 5.10 for testing. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: remove unneeded KERNEL_ENTRY_POINT definitionMartin Schiller2021-12-132-2/+0
| | | | | | As KERNEL_ENTRY_POINT is identical to KERNEL_LOADADDR, drop it. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* kernel: bump 5.4 to 5.4.162John Audia2021-11-285-14/+15
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *I am hit with the binutils 2.37 bug so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.161John Audia2021-11-2812-24/+24
| | | | | | | | | | | | | | | Removed upstreamed: ath79/patches-5.4/921-serial-core-add-support-for-boot-console-with-arbitr.patch[1] Manually rebased: layerscape/patches-5.4/804-crypto-0016-MLKU-114-1-crypto-caam-reduce-page-0-regs-access-to-.patch octeontx/patches-5.4/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch All other patches automatically rebased. 1. Private email exchange with patch author, Hauke Mehrtens Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.159John Audia2021-11-201-1/+1
| | | | | | | | | Manually rebased: generic-backport/850-v5.13-usb-ehci-add-spurious-flag-to-disable-overcurrent-ch.patch All other patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: mkits-multiple-config: fail on invalid argumentsRafał Miłecki2021-11-081-0/+5
| | | | | | | | Fail if arguments couldn't be parsed and print unrecognized part. It's important when running it from script with dynamic values. Missing value could result in skipping argument and silent failures (unexpected its). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 5.4 to 5.4.158John Audia2021-11-074-5/+5
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: Fix build in dtbHauke Mehrtens2021-10-2223-64/+37
| | | | | | | | This fixes a kernel build problem. The removed parts of the patch are already applied upstream. Fixes: 9ad3ef27b9ce ("kernel: bump 5.4 to 5.4.153") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.4 to 5.4.155John Audia2021-10-214-5/+5
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.154John Audia2021-10-2112-12/+12
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.153John Audia2021-10-2124-49/+49
| | | | | | | | | Removed upstreamed: backport-5.4/070-v5.5-MIPS-BPF-Restore-MIPS32-cBPF-JIT.patch All other patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: Deactivate some ARM64 errata workaroundsHauke Mehrtens2021-10-031-2/+0
| | | | | | | | | | | This deactivates the following workarounds for erratas in ARM64 CPUS: CONFIG_ARM64_ERRATUM_1165522: Cortex-A76 cores (r0p0, r1p0, r2p0) CONFIG_ARM64_ERRATUM_1286807: Cortex-A76 cores (r0p0 to r3p0) CONFIG_ARM64_ERRATUM_1418040: Cortex-A76/Neoverse-N1 cores (r0p0 to r3p1) CONFIG_CAVIUM_TX2_ERRATUM_219: Cavium ThunderX2 CONFIG_FUJITSU_ERRATUM_010001: Fujitsu-A64FX Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.4 to 5.4.150Hauke Mehrtens2021-10-0215-47/+19
| | | | | | | | | | | | | | | | Manually rebased: generic/pending-5.4/800-bcma-get-SoC-device-struct-copy-its-DMA-params-to-th.patch mvebu/patches-5.4/021-arm64-dts-marvell-armada-37xx-Move-PCIe-comphy-handl.patch Removed upstreamed: layerscape/patches-5.4/819-uart-0004-MLK-18137-fsl_lpuart-Fix-loopback-mode.patch All others updated automatically. Compile-tested on: lantiq/xrx200, armvirt/64 Runtime-tested on: lantiq/xrx200, armvirt/64 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.4 to 5.4.145John Audia2021-09-133-3/+3
| | | | | | | | | | | | Removed upstreamed: generic-backport/040-ARM-8918-2-only-build-return_address-if-needed.patch All other patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.144John Audia2021-09-131-1/+1
| | | | | | | | | | | | | Manually rebased: backport-5.4/370-netfilter-nf_flow_table-fix-offloaded-connection-tim.patch All other patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: Add missing kernel config optionsHauke Mehrtens2021-09-132-4/+0
| | | | | | | These options are selectable when some of the kernel debug options like KERNEL_SOFTLOCKUP_DETECTOR are selected. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Set CONFIG_RCU_CPU_STALL_TIMEOUT=21Hauke Mehrtens2021-09-092-2/+0
| | | | | | | | | | | | The default value for CONFIG_RCU_CPU_STALL_TIMEOUT was changed from 60 seconds to 21 seconds in 2012 in the upstream kernel. Some targets already use 21 seconds. This patch changes the default value in the generic configuration to 21 seconds and removes the target specific configuration options. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: move two symbols to the generic kconfigsRui Salvaterra2021-08-292-4/+0
| | | | | | | CONFIG_RCU_{NEED_SEGCBLIST,STALL_COMMON} are set basically everywhere. Move them to the generic kconfigs. And resort the generic kconfigs while at it. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: disable CONFIG_RCU_EXPERT and friendsRui Salvaterra2021-08-292-2/+0
| | | | | | | | | | | | | | Based on the existing documentation [1][2], I dare anyone to demonstrate that we need to fine-tune these RCU parameters. The (performance) breakage potential for doing so is immense, so let's just please put down this loaded footgun. Disable CONFIG_RCU_EXPERT and its dependent symbols. Additionally, remove the CONFIG_RCU_EXPERT symbol from the target kconfigs which contain it. [1] https://www.kernel.org/doc/Documentation/RCU/Design/Data-Structures/Data-Structures.html [2] https://lwn.net/Articles/777214/ Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.4 to 5.4.143John Audia2021-08-292-2/+2
| | | | | | | | | | | | | | | | | | Manually rebased: bcm27xx/patches-5.4/950-1031-net-lan78xx-Ack-pending-PHY-ints-when-resetting.patch Removed upstreamed: mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch All other patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.141John Audia2021-08-211-1/+1
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: Do not activate ext2 and ext3 driver optionsHauke Mehrtens2021-08-211-6/+0
| | | | | | | | The ext3 driver was already removed, the kernel config options are only there for backwards compatibility. The eth4 driver takes care of ext3 file systems. The ext4 driver also handled ext2 file systems. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* treewide: add various missing config symbolsDavid Bauer2021-08-101-0/+1
| | | | | | Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: David Bauer <mail@david-bauer.net>
* layerscape: Fix multiple bugs in of_get_mac_address() changesHauke Mehrtens2021-08-0910-30/+24
| | | | | | | | | | | The change which backported the of_get_mac_address() change broke some patches in the layerscape target so the patches did not apply any more. This commit makes them apply again and also fixes some other problems related to this change. Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* layerscape: armv8_64b: do not disable CONFIG_IP_ADVANCED_ROUTERMartin Schiller2021-08-081-1/+0
| | | | | | | | This option is needed e.g. to use strongswan for IPSec. BTW: This was the only target where this option was disabled. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* treewide: backport support for nvmem on non platform devicesAnsuel Smith2021-08-054-27/+7
| | | | | | | | | | | | In the current state, nvmem cells are only detected on platform device. To quickly fix the problem, we register the affected problematic driver with the of_platform but that is more an hack than a real solution. Backport from net-next the required patch so that nvmem can work also with non-platform devices and rework our current patch. Drop the mediatek and dsa workaround and rework the ath10k patches. Rework every driver that use the of_get_mac_address api. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* kernel: bump 5.4 to 5.4.136John Audia2021-07-316-7/+7
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.135John Audia2021-07-3113-39/+39
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* layerscape: armv8_64b: enable Microsemi phy driver for FRWY-LS1046AMartin Schiller2021-07-251-0/+1
| | | | | | | | | Enable the Microsemi phy driver to support the VSC8514 QSGMII phy on the FRWY-LS1046A board. Otherwise, the "Generic PHY" driver is used. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: fix config restore for FRWY-LS1046AMartin Schiller2021-07-251-0/+1
| | | | | | | | | commit 2c2d77bd3bd4 ("layerscape: add FRWY-LS1046A board support") missed to add an entry to the 79_move_config preinit script. Therefore, the config transfer on sysupgrade wass broken for this device. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* kernel: bump 5.4 to 5.4.134John Audia2021-07-257-17/+17
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 04:17:50 +0000