aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/qoriq
Commit message (Collapse)AuthorAgeFilesLines
* treewide: remove label = "cpu" from DSA dt-bindingArınç ÜNAL2023-02-261-2/+0
| | | | | | | This is not used by the DSA dt-binding, so remove it from all devicetrees. Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9cc115d8d6f73dd260de1609182f3645844d6907 Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
* qoriq: drop unused kernel configStijn Tintel2023-01-091-384/+0
| | | | | | | | While switching qoriq to kernel 5.15, the config for kernel 5.10 was left behind. Drop it. Fixes: 230f2fccd14e ("qoriq: switch to kernel 5.15") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: switch to kernel 5.15Stijn Tintel2022-12-141-2/+1
| | | | | | | | | The testing kernel has been running fine for months on a rather complex network setup, with one exception being a crash in __xfrm_state_delete(). This crash has been fixed in kernel 5.15.82, so let's switch the qoriq target to kernel 5.15 by default. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: add missing symbol in generic configPawel Dembicki2022-11-162-2/+0
| | | | | | | | Found during work on qoriq target. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [improve commit message, remove from target configs] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: fix typo in FEATURESStijn Tintel2022-10-051-1/+1
| | | | | | | There is no root-part FEATURE. Reported-by: Karl Palsson <karlp@etactica.com> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: Move some IOMMU options to genericHauke Mehrtens2022-09-242-3/+0
| | | | | | | | | | | | This adds some missing IOMMU related options for x86/64 and moves some of them to generic for all targets. On x86 IOMMU_DEFAULT_DMA_LAZY is used by default, on all other platforms IOMMU_DEFAULT_DMA_STRICT is the default. we just follow the default kernel configuration here. Fixes: 8fea4a102ccd ("x86/64: enable IOMMU support") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Activate CONFIG_GPIOLIB in generic configurationHauke Mehrtens2022-08-102-2/+0
| | | | | | | | All targets expect the malta target already activate the CONFIG_GPIOLIB option. Move it to generic kernel configuration and also activate it for malta. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* qoriq: enable Book-E Watchdog TimerStijn Tintel2022-07-012-0/+4
| | | | | | | | | | | | | | | Enable PowerPC Book-E Watchdog Timer support. Having this enabled in-kernel will result in procd starting it during boot. This effectively solves the problem of the WDT in the Winbond W83793 chip potentially resetting the system during sysupgrade, which could result in an unbootable device. While the driver is modular, resulting in procd not starting the WDT during boot (because that happens before kmod load), the WDT handover during sysupgrade results in the WDT being started. This normally shouldn't be a problem, but the W83793 WDT does not like procd's defaults, nor the handover happening during sysupgrade. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: add kernel 5.15 supportStijn Tintel2022-06-292-0/+403
| | | | | | Add support for kernel 5.15 as testing kernel for qoriq. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: enable HARDENED_USERCOPYStijn Tintel2022-06-291-1/+0
| | | | | | | The random crashes observed with HARDENED_USERCOPY enabled no longer seem to occur. Enable HARDENED_USERCOPY to improve security. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: disable CONFIG_COMPATStijn Tintel2022-06-291-8/+0
| | | | | | | We do not need support for 32 bit applications, as we're building everything for 64 bit. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: 02_network fix sweth globbing logicThibaut VARÈNE2022-06-291-1/+1
| | | | | | This prevents invalid configuration of non-existent sweth devices. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* qoriq: define reset button for Firebox M300Thibaut VARÈNE2022-06-292-1/+13
| | | | | | This patch provides support for the Firebox M300 reset button. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* qoriq: define leds for Firebox M300Thibaut VARÈNE2022-06-292-1/+22
| | | | | | | | This patch provides support for the Firebox M300 only user-controllable bi-color LED, and makes the green "shield" LED act as the typical OpenWrt status led. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]Tomasz Maciej Nowak2022-06-241-0/+2
| | | | | | | | | | | | This is now built-in, enable so it won't propagate on target configs. Link: https://lkml.org/lkml/2022/1/3/168 Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44") Fixes: 0ca93670693b ("kernel: bump 5.10 to 5.10.119") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (Link to Kernel's commit taht made it built-in, CRYPTO_LIB_BLAKE2S[_ARM|_X86] as it's selectable, 5.10 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* qoriq: use FIT uImage for Firebox M300 kernelStijn Tintel2022-06-141-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This requires U-Boot environment changes: setenv OpenWrt_kernel watchguard_firebox-m300-fit-uImage.itb setenv loadaddr 0x20000000 setenv wgBootSysA 'setenv bootargs root=/dev/mmcblk0p2 rw rootdelay=2 console=$consoledev,$baudrate fsl_dpaa_fman.fsl_fm_max_frm=1530; mmc dev 0; ext2load mmc 0:1 $loadaddr $OpenWrt_kernel; bootm $loadaddr' Trying to sysupgrade an image containing this change on an M300 already running OpenWrt will fail with the following error: Tue Jun 14 12:06:21 EEST 2022 upgrade: The device is supported, but the config is incompatible to the new image (1.0->1.1). Please upgrade without keeping config (sysupgrade -n). Tue Jun 14 12:06:21 EEST 2022 upgrade: Kernel switched to FIT uImage. Update U-Boot environment. Tue Jun 14 12:06:21 EEST 2022 upgrade: Reading partition table from bootdisk... Tue Jun 14 12:06:21 EEST 2022 upgrade: Extract boot sector from the image Tue Jun 14 12:06:21 EEST 2022 upgrade: Reading partition table from image... Image check failed. This is to prevent rendering your device unbootable. Make the U-Boot environment changes as instruced above, and then flash the image using sysupgrade -F. The config can be kept, there is no need to use -n. After the new image booted successfully, you can increase the compat_version: uci set system.@system[0].compat_version='1.1' uci commit Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: use KERNEL_SUFFIX in Build/sdcard-imgStijn Tintel2022-06-141-1/+1
| | | | | | | | | Use the KERNEL_SUFFIX variable in Build/sdcard-img, rather than using hardcoded "-kernel.bin", to allow overriding KERNEL_SUFFIX for a device. Fixes: 080a769b4da8 ("qoriq: new target") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* config: limit CONFIG_DEBUG_INFO to top-level generic configsTony Ambardar2022-05-181-2/+0
| | | | | | | | | | Remove redundant target-level entries, noting that these settings will be configured from "Kernel build options" of Kconfig. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove from new configs introduced after patch submission] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: enable support for Marvell Alaska PHYsStijn Tintel2022-04-031-0/+1
| | | | | | | | The WatchGuard Firebox M200 and M300 use a Marvell 88e1543 PHY for the first 3 ethernet ports. This PHY is supported by the Marvell Alaska PHY driver, so enable it. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: remove CONFIG_GDB_SCRIPTS from kernel configStijn Tintel2022-03-251-1/+0
| | | | | | | | It is disabled in the generic kernel config and not used in any of the other targets. There was no specific reason for enabling it, so let's be consistent and remove it from the qoriq kernel config. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: enable I2C in target kernel configStijn Tintel2022-03-161-0/+3
| | | | | | | | | | | The I2C controller used in QorIQ PPC devices requires the mpc-i2c driver, which is enabled by the I2C_MPC kernel config symbol. Enable this and its dependencies in the target kernel config, as is done for the mpc85xx target. This fixes missing hwmon, rtc and tpm devices on the M300. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: Expand generic subtarget descriptionMatt Fawcett2022-01-051-1/+3
| | | | | | Signed-off-by: Matt Fawcett <mattytap@icloud.com> [remove trailing whitespace] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: add support for WatchGuard Firebox M300Stijn Tintel2021-12-215-0/+431
| | | | | | | | | | | | | | | | | | | | | | | This device is based on NXP's QorIQ T2081QDS board, with a quad-core dual-threaded 1.5 GHz ppc64 CPU and 4GB ECC RAM. The board has 5 ethernet interfaces, of which 3 are connected to the ethernet ports on the front panel. The other 2 are internally connected to a Marvell 88E6171 switch; the other 5 ports of this switch are also connected to the ethernet ports on the front panel. Installation: write the sdcard image to an SD card. Stock U-Boot will not boot, wait for it to fail then run these commands: setenv OpenWrt_fdt image-watchguard-firebox-m300.dtb setenv OpenWrt_kernel watchguard_firebox-m300-kernel.bin setenv wgBootSysA 'setenv bootargs root=/dev/mmcblk0p2 rw rootdelay=2 console=$consoledev,$baudrate fsl_dpaa_fman.fsl_fm_max_frm=1530; ext2load mmc 0:1 $fdtaddr $OpenWrt_fdt; ext2load mmc 0:1 $loadaddr $OpenWrt_kernel; bootm $loadaddr - $fdtaddr' saveenv reset The default U-Boot boot entry will now boot OpenWrt from the SD card. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Acked-by: Rui Salvaterra <rsalvaterra@gmail.com>
* qoriq: new targetStijn Tintel2021-12-215-0/+452
Add a new target named "qoriq", that will support boards using PowerPC processors from NXP's QorIQ brand. This doesn't actually add support for any board yet, so that installation instructions can go in the commit message of the commit that adds actual support for a board. Using CONFIG_E6500_CPU here due to the kernel using -mcpu=powerpc64 rather than -mcpu=e5500 when selecting CONFIG_E5500_CPU. The only difference between e5500 and e6500 is AltiVec support, and the kernel checks for it at runtime. Musl will only check at runtime if AltiVec support is disabled at compile-time, so we need to use e5500 in CPU_TYPE to avoid SIGILL. Math emulation (CONFIG_MATH_EMULATION_HW_UNIMPLEMENTED) is required, as neither e5500 nor e6500 implement fsqrt nor fsqrts, and musl hardcodes sqrt and sqrtf to use these ASM instructions on PowerPC64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Reviewed-by: Rui Salvaterra <rsalvaterra@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 03:37:36 +0000