aboutsummaryrefslogtreecommitdiff
path: root/target
Commit message (Collapse)AuthorAge
* mediatek: add Airoha EN8801SC PHY driverRobert Marko2024-04-11
| | | | | | | | | | | Airoha EN8801SC PHY is a gigabit PHY used on Edgecore EAP111 so, include the MTK driver with some cleanups. Unfortunatelly, there is no specification sheet nor datasheet available in order to demistify the magic PBUS writes and work on upstreaming this driver. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* generic: 6.1, 6.6: import two pending patches for mt7530 DSA driverDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | First patch allows to inquire and modify Energy-Efficient-Ethernet (EEE) settings via ethtool and thereby override the default setting of a board done via bootstrap pins. The second patch fixes a long-standing issue with STP (and similar protocols) when using boards (or SoCs) governed by the mt7530 DSA driver. Both patches could also be (dirty-)applied to Linux 5.15, but I'd rather just wait for that to happen via linux-stable to avoid the mess. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: 6.6: sync mt7530 DSA driver with upstreamDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | | Backport lots upstream changes, many of them fixes, for the mt7530 DSA driver, similar to how it was done for Linux 6.1 in the previous commit. The remaining differences compared to the upstream driver are only the 'slave' -> 'user', 'master' -> 'conduit' language change in DSA and the rename of 'struct ethtool_eee' to 'struct ethtool_keee' as well as tree-wide replacement of ethtool_sprintf with ethtool_puts, all of them do not have any functional impact. Apart from some minor bug fixes and style improvements the switch should now behave more conformant when it comes to link-local frames, and we will again be able to cleanly pick patches from upstream. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: 6.1: sync mt7530 DSA driver with upstreamDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport lots upstream changes, many of them fixes, for the mt7530 DSA driver. Some of them may or may not find they way into Linux 6.1 stable, some certainly won't because they are fixes for backported commits which aren't even present in Linux 6.1 upstream. Apart from adding new patches, also remove mutated patch 723-net-mt7531-ensure-all-MACs-are-powered-down-before-r.patch which should never have been added for Linux 6.1 -- it was applied already upstream but coincidentally would fuzzy-apply in the wrong place as well (for MT7530 instead of MT7531). While that didn't really hurt anyone it is just unneeded. The other deleted patch 795-mt7530-register-OF-node-for-internal-MDIO-bus.patch has been replaced by an equivalent commit with a more complete patch description by upstream maintainer Arınç Ünal. The remaining differences compared to the upstream driver are: * C22/C45 MDIO ops aren't split Upstream did that, backporting it would require making changes to *all* DSA drivers * 'slave' -> 'user', 'master' -> 'conduit' language change in DSA * support for selecting preferred CPU port on MT7531 Also this would require too many DSA framework changes potentially affecting other devices. If we ever really use Linux 6.1 in a release (I hope not) we can still reconsider to make the effort to backport that. In addition to some minor bug fixes and style improvements the switch should now behave more conformant when it comes to link-local frames, and we will again be able to cleanly pick patches from upstream. MAINTAIERS NOTE: Three patches are already part of Linux stable and should be removed with the next minor kernel version bump: 789-STABLE-01-net-dsa-mt7530-prevent-possible-incorrect-XTAL-frequ.patch 789-STABLE-02-net-dsa-mt7530-fix-link-local-frames-that-ingress-vl.patch 789-STABLE-03-net-dsa-mt7530-fix-handling-of-all-link-local-frames.patch Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: add missing patch headersDaniel Golle2024-04-09
| | | | | | | Make sure all patches can be applied to a git tree using 'git am' by adding missing patch headers where needed. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: filogic: switch TP-LINK XDR series to fitblkDaniel Golle2024-04-09
| | | | | | | Instead of using the deprecated FIT partition parser, use the new fitblk driver instead. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: puzzle-m90x: wipe rootfs_data on sysupgradeDaniel Golle2024-04-09
| | | | | | | | | | | | | | | | | | | The sysupgrade formware of the Puzzle series is a slightly strange dual-boot approach while remaining compatible with Marvell's SDK firmware upgrade binary format -- which happens to be a full-disk image with GPT partition table. Hence that /lib/upgrade/emmc-puzzle.sh script is like an exotic disease which results from those decisions, and as we also want to somehow stay compatible with the IEI-World stock firmware we got to use it in that same way (we are not compatible with the QNAP-branded identical hardware device anyway). Currently, on sysupgrade the result is that one ends up with the old content of rootfs_data (a GPT partition on those devices) as nothing ever wipes or in any way re-creates the filesystem there. As a simple work-around, let's kill the filesystem on rootfs_data so fstools re-formats it on the next boot. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* sdk: include lib/crtsavres.o for powerpcRobert Marko2024-04-09
| | | | | | | | | | | | | | | | | | | | Trying to link certain kernel modules like dahdi-linux when building with the OpenWrt SDK will fail with: openwrt-sdk-apm821xx-sata_gcc-13.2.0_musl.Linux-x86_64/staging_dir/toolchain-powerpc_464fp_gcc-13.2.0_musl/bin/powerpc-openwrt-linux-musl-ld: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory Previously this worked with the PowerPC SDK since we carried a hack that was passing --save-restore-funcs to module LDFLAGS so the linker provided the required functions automatically as without --save-restore-funcs it doesnt do so automatically on relocatable links and as a sideffect did not require the kernel provided crtsaves.o to link against. Now that hack has been removed as upstream kernel now compiles crtsaves.o by default so it can be linked against but its not included in the SDK. So, lets include lib/crtsavres.o when SDK is generated for PowerPC. Fixes: 99c9d8abd677 ("kernel: bump 5.15 to 5.15.148") Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: Skip compiling unnecessary dtbsSean Khan2024-04-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the compile phase of the kernel builds `Image dtbs modules`. However, none of the dtbs that get built are used for the final image. This ends up unnecessarily taking CPU cycles and produces a lot of `WARNINGS` that can lead users to believe there's cause for concern. I believe the same principle can be applied to other targets. ``` DTC arch/arm64/boot/dts/qcom/msm8996-mtp.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-dora.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-kagura.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-keyaki.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-gemini.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-natrium.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-scorpio.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) ``` Signed-off-by: Sean Khan <datapronix@protonmail.com>
* treewide: remove implicit SUBTARGETPaul Spooren2024-04-08
| | | | | | | | | | | | | | | | | | Historically it's possible to leave the `SUBTARGETS` undefined and automatically fallback to a "generic" subtarget. This however breaks various downstream scripts which may have expectations around filenames: While some targets with an explicit generic subtarget contain `generic` in the filenames of artifacts, implicit "subtargets" don't. Right now this breaks the CI[1], possibly also scripts using the ImageBuilders. This commit removes all code that support implicit handling of subtargets and instead requires every target to define "SUBTARGETS". [1]: https://github.com/openwrt/openwrt/actions/runs/8592821105/job/23548273630 Signed-off-by: Paul Spooren <mail@aparcar.org>
* d1: define subtarget specificallyPaul Spooren2024-04-08
| | | | | | | | | | | | | | | | | | Historically it's possible to leave the `SUBTARGETS` undefined and automatically fallback to a "generic" subtarget. This however breaks various downstream scripts which may have expectations around filenames: While some targets with an explicit generic subtarget contain `generic` in the filenames of artifacts, implicit "subtargets" don't. Right now this breaks the CI[1], possibly also scripts using the ImageBuilders. Do to the D1 target what's done to other target, explicitly define the "generic" subtarget. [1]: https://github.com/openwrt/openwrt/actions/runs/8592821105/job/23548273630 Signed-off-by: Paul Spooren <mail@aparcar.org>
* realtek: add support for switch Zyxel GS1900-24EPMirko Vogt2024-04-08
| | | | | | | | | | | This device is very similar to the GS1900-24E switch (added in b515ad1), except that the first 12 of 24 ethernet ports are capable of PoE and the physical jacks are in the right order - unlike for the GS1900-24E, where even and uneven ports are flipped (up <-> down on panel). Zyxel version code for this device (-24EP) is: ABTO Signed-off-by: Mirko Vogt <mirko-openwrt@nanl.de>
* bcm27xx: bcm2712: backport RP1 interrupt affinityÁlvaro Fernández Rojas2024-04-07
| | | | | | Support for setting the CPU affinity on RP1 has been added to RPi linux v6.6 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update 6.1 patches from RPi foundationÁlvaro Fernández Rojas2024-04-07
| | | | | | | | Sync 6.1 patches with the RPi foundation. Since rpi-6.6.y is now the main branch of the RPi foundation, there won't be any new patches for linux 6.1. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* generic: backport at803x kernel panic fixChristian Marangi2024-04-07
| | | | | | Backport at803x kernel panic fix merged upstream for kernel 6.1 and 6.6. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* generic: 6.6: backport arm64 swiotlb default size reductionRobert Marko2024-04-07
| | | | | | | | | | | | | | Kernel 6.6 added dynamic SWIOTLB allocation, but with it also started allocating 64MB of the SWIOTLB bounce buffer by default which is quite a lot of memory on most OpenWrt devices. Luckily in kernel 6.7 arm64 received an optimization that reduces that default size to 1MB per 1GB of RAM if certain criteria was met. So in order to reclaim back 63MB of RAM which brought some ipq807x devices close to OOM under load lets backport the upstream commit. Signed-off-by: Robert Marko <robimarko@gmail.com>
* x86: geode: 6.6: add missing kernel optionsMieczyslaw Nalewaj2024-04-07
| | | | | | | Add options removed by `make kernel_oldconfig CONFIG_TARGET=subtarget', missing which causes compilation to stop and cause an error. Fixes: 2a86425de107 ("x86: 6.6: refresh kernel config") Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel: bump 6.6 to 6.6.24John Audia2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.24 Removed upstreamed: generic/backport-6.6/838-v6.9-leds-trigger-netdev-Fix-kernel-panic-on-interface-re.patch[1] generic/backport-6.6/981-mtd-spinand-Add-support-for-5-byte-IDs.patch[2] mediatek/patches-6.6/831-thermal-drivers-mediatek-Fix-control-buffer-enablement-on-MT7896.patch[3] Removed: ipq40xx/patches-6.6/110-mtd-limit-OTP-nvmem-to-non-nand-devices.patch[4] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.24&id=10f2af1af8ab8a7064f193446abd5579d3def7e3 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.24&id=9c74507e6c4382d12a5e418742b81fd441f03313 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.24&id=fe750e2744428be6aec7395b13df3b34381ce6b6 4. Acknowledgment to @DragonBlurp for pointing out the redundancy of this patch. https://github.com/openwrt/openwrt/commit/dd78a59cd7b029560b33cb3ac0e1aa8b747bd807 Build system: x86/64 Build-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3 Run-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me>
* ipq806x: 6.6: refresh patchesMieczyslaw Nalewaj2024-04-05
| | | | | Refresh patches for kernel 6.6.23 with make target/linux/refresh. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* pistachio: add 6.1 testing kernelZoltan HERPAI2024-04-05
| | | | | | Configure 6.1 as testing kernel. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* pistachio: refresh 6.1 configZoltan HERPAI2024-04-05
| | | | | | Kernel config needs to be refreshed after copy from 5.15. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* pistachio: update and extend 6.1 patchesZoltan HERPAI2024-04-05
| | | | | | | | | | | Add: 110-pwm-img-fix-clock-lookup.patch - patch to fix a clock lookup issue from upstream Update: 401-mtd-nor-support-mtd-name-from-device-tree.patch - mtd-name lookup hack to reflect the updated spi_nor_scan function Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* pistachio: copy config and patches of 5.15 to 6.1Zoltan HERPAI2024-04-05
| | | | | | Simple copy of config and patches. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ipq40xx: 6.6: remove redundant patchMieczyslaw Nalewaj2024-04-05
| | | | | | Remove file 110-mtd-limit-OTP-nvmem-to-non-nand-devices.patch redundand after adding 440-mtd-don-t-look-for-OTP-legacy-NVMEM-cells-if-proper-.patch in dd78a59 Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kirkwood: 6.6: refresh patchesMieczyslaw Nalewaj2024-04-05
| | | | | | Refresh patches for kernel 6.6.23 with make target/linux/refresh. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* apm821xx: restore 6.1 config+patchesChristian Lamparter2024-04-05
| | | | | | | simply attached previous versions of the config-6.1 and patches-6.1 directory. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add 6.6 testing kernelChristian Lamparter2024-04-05
| | | | | | | | | refreshed kernel config + patches otherwise same as 6.1/5.15. Tested on: WNDAP620, WNDAP660, MyBook Live Single, MR24, MX60, WNDR4700 Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: prepare WNDR4700 for 6.6 - add preliminary u-boot-env accessChristian Lamparter2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the default BUILD_BOT configuration on a linux 6.6 kernel, the WNDR4700's kernel no longer fits into the alloted ~3.5MiB, even with LZMA compression. Bigger kernels are possible, but there's a problem with Netgear's "bootcmd": > if loadn_dniimg 0 0x180000 0x4e0000 && chk_dniimg 0x4e0000; then nand read 0x800000 0x180000 0x20000;bootm 0x500000 - 0x800040;else fw_recovery; fi" This loads the dni-image starting offset 0x180000 from the NAND flash (which is the DTB partition) to 0x4e0000 in the RAM. It then checks whenever the provided image is "valid". If it is then it reads the DTB again to 0x800000 in the RAM and starts the extraction and boot process. (If the image wasn't valid then it starts the automated firmware recovery). The issues here are that first: the kernel image gets "squeezed" between 0x500040 and 0x7fffff... And second, the decompressor only has area 0x0 - 0x500000 for decompression. Hence the image now requires to update the bootcmd by providing new values (which have been successfully tested with the original Netgear WNDR4700 v1.0.0.56 firmware) for the RAM locations and make full use of the fact that loadn_dniimg loads the DTB as well. This needs to be done only once. Just connect a serial adapter to interface with uboot and overwrite (and save) the new bootcmd. WARNING: The serial port needs a TTL/RS-232 3.3v level converter! Steps: 0. Power-off the WNDR4700 1. Connect the serial interface (you need to open the WNDR4700) 2. Power-up the WNDR4700 3. Monitor the boot-sequence and hit "Enter"-key when it says: "Hit any key to stop autoboot" (Be quick, you have a ~2 second window) 4. in the Prompt enter the following commands (copy & paste) setenv bootcmd "if loadn_dniimg 0 0x180000 0xce0000 && chk_dniimg 0xce0000; then bootm 0xd00000 - 0xce0040;else fw_recovery; fi" saveenv run bootcmd Note: This new bootcmd will also unbrick devices that were bricked by the bigger 4.19-6.1 kernels. Note2: This method was tested with a WNDR4700. A big kernel with most debug features enabled on v6.6.22 measured 4.30 MiB when compressed with lzma. The uncompressed kernel is 12.34 MiB. This is over the 3 MiB, the device reserves for the kernel... But it booted! For bigger kernels, the device needs repartitioning of the the ubi partition due to the kernel+dtb not fitting into the partition. Note3: For initramfs development. I would advice to load the initramfs images to 0x800000 (or higher). i.e.: tftp 800000 wndr4700.bin Note4: the fw_recovery uboot command to transfer the factory image to the flash still works. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ramips: 6.6: set testing kernelMieczyslaw Nalewaj2024-04-05
| | | | | | Allow selecting 6.6 as testing kernel on ramips. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: 6.6: refresh kernel configMieczyslaw Nalewaj2024-04-05
| | | | | | Refresh kernel config. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: adjusted pinctrl-aw9523 for kernel 6.6Mieczyslaw Nalewaj2024-04-05
| | | | | | | | Compatiblity with kernel 6.6 for Awinic AW9523B i2c pin controller driver. It follows the kernel patch: i2c: Drop legacy callback .probe_new() (https://github.com/torvalds/linux/commit/5eb1e6e459cfa025f79c43014f66ff62a55542f1) and kernel patch: gpiolib: Get rid of not used of_node member (https://github.com/torvalds/linux/commit/70d0fc4288dabd65025fde7774b4f9262afa9034) Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620: alignment with updated snd_soc_dai_driver structureMieczyslaw Nalewaj2024-04-05
| | | | | | | Fix error: 'struct snd_soc_dai_driver' has no member named 'remove' It follows the kernel patch: ASoC: soc-dai.h: remove unused call back functions (https://github.com/torvalds/linux/commit/446b31e894935ebbcf84302061a4e0e2efb2368f) Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* generic: fix detect_memory_region() functionShiji Yang2024-04-05
| | | | | | | This patch fixes the broken detect_memory_region() function on 6.6 kernel. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: 6.6: fix net drivers compatibilityMieczyslaw Nalewaj2024-04-05
| | | | | | | Fix compatibility of ralink net drivers with kernel 6.6. It follows the kernel patch: u64_stats: Streamline the implementation (https://github.com/torvalds/linux/commit/44b0c2957adc62b86fcd51adeaf8e993171b) Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: 6.6: refresh patchesMieczyslaw Nalewaj2024-04-05
| | | | | | Refresh kernel patches. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: 6.6: remove old patchesMieczyslaw Nalewaj2024-04-05
| | | | | | Remove patches for old kernel. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel/ramips: Restore kernel files for v6.1Mieczyslaw Nalewaj2024-04-05
| | | | | | | | | | This is an automatically generated commit which aids following Kernel patch history, as git will see the move and copy as a rename thus defeating the purpose. See: https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html for the original discussion. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel/ramips: Create kernel files for v6.6 (from v6.1)Mieczyslaw Nalewaj2024-04-05
| | | | | | | | This is an automatically generated commit. During a `git bisect` session, `git bisect --skip` is recommended. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel/ramips: Restore kernel patches for v6.1Mieczyslaw Nalewaj2024-04-05
| | | | | | | | | | This is an automatically generated commit which aids following Kernel patch history, as git will see the move and copy as a rename thus defeating the purpose. See: https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html for the original discussion. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel/ramips: Create kernel patches for v6.6 (from v6.1)Mieczyslaw Nalewaj2024-04-05
| | | | | | | | This is an automatically generated commit. During a `git bisect` session, `git bisect --skip` is recommended. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kirkwood: add 6.6 kernel as testing versionPawel Dembicki2024-04-04
| | | | | | This patch introduce kernel 6.6 for kirkwood target as testing version. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: split files into 6.1 and 6.6 versionPawel Dembicki2024-04-04
| | | | | | | Upstream change location of kirkwood dts files. Split downstream files location for better upstream follow. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: kernel: refresh 6.6 configPawel Dembicki2024-04-04
| | | | | | Done by 'make kernel_oldconfig'. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: refresh 6.6 patchesPawel Dembicki2024-04-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removed upstream merged: 002-6.2-ARM-dts-kirkwood-Add-Zyxel-NSA310S-board.patch 003-6.5-ARM-dts-kirkwood-Add-Endian-4i-Edge-200-board.patch 004-6.4-ARM-dts-kirkwood-Add-missing-phy-mode-and-fixed-link.patch 005-6.7-net-dsa-mv88e6xxx-fix-marvell-6350-switch-probing.patch Manually refreshed: 100-ib62x0.patch 101-iconnect.patch 102-dockstar.patch 103-iomega-ix2-200.patch 105-linksys-viper-dts.patch 106-goflexnet.patch 107-01-zyxel-nsa3x0-common-nand-partitions.patch 107-03-nsa325.patch 109-pogoplug_v4.patch 110-pogo_e02.patch 111-l-50.patch 112-sheevaplug.patch 113-readynas_duo_v2.patch 114-ctera-c-200-v1.patch 115-nsa310s.patch 116-4i-edge-200.patch 117-netgear_stora.patch 203-blackarmor-nas220.patch Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kernel/kirkwood: Restore kernel files for v6.1Pawel Dembicki2024-04-04
| | | | | | | | | | This is an automatically generated commit which aids following Kernel patch history, as git will see the move and copy as a rename thus defeating the purpose. See: https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html for the original discussion. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kernel/kirkwood: Create kernel files for v6.6 (from v6.1)Pawel Dembicki2024-04-04
| | | | | | | | This is an automatically generated commit. During a `git bisect` session, `git bisect --skip` is recommended. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* qualcommax: ipq60xx: add yuncore fap650 supportIsaev Ruslan2024-04-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Yuncore FAP650 device. Specifications: - Qualcomm IPQ6018+QCA8075+QCN5022+QCN5052 - 512 MB of RAM (DDR3) - 8 MB of serial flash (SPI NOR) - 128 MB of parallel flash (NAND) - 2x2 2.4 GHz WiFi (IPQ6010) - 2x2 5 GHz WiFi (IPQ6010) - 2x 2dBi 2.4G MIMO antenna - 2x 3dBi 5.8G MIMO antenna - 5x 1 Gbps Ethernet (QCA8075) - POE: 48V (IEEE 802.3af) - power: 12V (~1.5A) - 1x passthru port (rj45 - rj45) - 1x cisco rj45 console port - size: 160mm*86mm*29mm BACKUP YOUR STOCK FIRMWARE: ``` export device=fap650 mkdir -p /tmp/fw_dump_$device cd /tmp/fw_dump_$device dmesg > dmesg_$device.log dtc -I fs /sys/firmware/devicetree/base > $device.dts cat /proc/device-tree/model > model cat /proc/mtd > proc_mtd while read p; do mtd_dev=$(echo $p | cut -d: -f1) echo $mtd_dev dd if=/dev/$mtd_dev of=$mtd_dev done < proc_mtd md5sum * > md5sum.log tar -cvzf ../$device.tar.gz . export sum=$(md5sum /tmp/$device.tar.gz | cut -d' ' -f1) mv ../$device.tar.gz /tmp/${device}_${sum}.tar.gz echo fw backup saved to: /tmp/${device}_${sum}.tar.gz ``` Upload your backup via tftp to the safe place. INSTALLATION: 1. stock firmware web ui Rename factory.bin fw image file to factory.ubin. Flash this image like ordinary stock fw upgrade. 2. stock firmware telnet method Enter telnet cli (login: root, password: 476t*_f0%g09y) and upload factory.bin fw image and rename it to factory.ubin `cd /tmp && wget <your_web_server_ip>/factory.ubin` `sysupgrade factory.ubin 3. initramfs method Put imitramfs image to your TFTP server and rename it for example to fap650.initram Enable serial console and enter to the u-boot cli. Exec these commands: `tftpboot <your_tftp_server_ip>:fap650.initram` `dhcp` When downloading is finished: `bootm` After booting the device, you need to upload to the device factory.ubi fw image. ``` cd /tmp && wget <your_web_server_ip>/factory.ubi` export rootfs=$(cat /proc/mtd | grep rootfs | cut -d: -f1) export rootfs_1=$(cat /proc/mtd | grep rootfs_1 | cut -d: -f1) ubiformat /dev/${rootfs} -y -f factory.ubi ubiformat /dev/${rootfs_1} -y -f factory.ubi reboot ``` 4. u-boot factory.ubi image method Put factory.ubi to your TFTP server Enter u-boot cli and exec these commands: `tftpboot <your_tftp_server_ip>:factory.ubi` `dhcp` After downloading is finished: `flash rootfs` `flash rootfs_1` `reset` STOCK FIRMWARE RECOVERY: Boot initramfs image. Upload your rootfs mtd partition to the device using scp or download it from the device using wget. Enter device ssh cli and exec: ``` cd /tmp && wget <your_web_server_ip>/rootfs_mtd` export rootfs=$(cat /proc/mtd | grep rootfs | cut -d: -f1) export rootfs_1=$(cat /proc/mtd | grep rootfs_1 | cut -d: -f1) ubiformat /dev/${rootfs} -y -f /tmp/rootfs_mtd ubiformat /dev/${rootfs_1} -y -f /tmp/rootfs_mtd reboot ``` Signed-off-by: Isaev Ruslan <legale.legale@gmail.com>
* x86: 6.6: set testing kernelMieczyslaw Nalewaj2024-04-04
| | | | | | Allow selecting 6.6 as testing kernel on x86. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* x86: 6.6: refresh kernel configMieczyslaw Nalewaj2024-04-04
| | | | | | Refresh kernel config. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* generic: 6.6: Removal of tools_portability.patch already included in kernel 6.6Mieczyslaw Nalewaj2024-04-04
| | | | | | Removal of tools_portability.patch already included in kernel 6.6 Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Powered by cgit, Themed by Ted Yin.