aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* mac80211: merge the virtual time based airtime schedulerFelix Fietkau2021-11-234-3/+1430
| | | | | | | Improves airtime fairness, especially for devices with larger firmware buffers Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit a5888ad6b33840d913438ce664c0e7da7e7f53e6)
* mac80211: set beamformer/beamformee number of antennas in VHT capsFelix Fietkau2021-11-231-0/+16
| | | | | | | Without this, beamforming is probably not working Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit e2c4998f6dca7d9b74a8b01762040ff2c5e38fd7)
* mac80211: fix IBSS/adhoc mode for brcmfmacBastian Bittorf2021-11-231-0/+1
| | | | | | | | | | | | | | | | | | | | | On systems using brmcfmac (e.g. Raspberry Pi Zero W) without this fix, the final setup-call: iw dev wlan0 ibss join ... fails with returncode 161 and message: "command failed: Not supported (-95)" So this patch calls an explicit: iw dev wlan0 set type ibss just prior to the 'ibss join' command. I have tested several ath9k and mt76xx devices with different revisions: this patch does not harm. please also apply to stable branch. Signed-off-by: Bastian Bittorf <bb@npl.de> (cherry-picked from commit ea5fce3f4616df3e4331e6b4e8e79767bded442c)
* mac80211: allow retry of wifi setup if an iw interface add command failsFelix Fietkau2021-11-231-1/+1
| | | | | | | In some cases, spurious failures might be cleared by teardown and retry Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 42dda0ed3e941bc36661e29b990e2ee2adf7f508)
* mac80211: fix HT40 mode for 6G bandFelix Fietkau2021-11-231-3/+4
| | | | | | | The channel offset used for VHT segment calculation was missing for HT Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit a0d81ba0d5e9d055c55b5e478cb913c217122317)
* mac80211: fix processing HE capabilities (FS#3871)Felix Fietkau2021-11-231-1/+1
| | | | | | | Use the right argument to fix setting unsupported capabilities to 0 Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 49ef4dbee519e006bb998de11e3bdf1c10c43e6a)
* mac80211: fix typoFelix Fietkau2021-11-231-1/+1
| | | | | | | Remove stray parenthesis Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 2cd1a108290f48fd35373f91056c05277c289687)
* mac80211: do not enable VHT in the default config on 2.4 GHzFelix Fietkau2021-11-231-1/+1
| | | | | | | | Some drivers advertise it, but it's not supported at the moment Reported-by: John Thomson <git@johnthomson.fastmail.com.au> Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 42a99b18ff23fa768a6ae5f1076f15cbfa494f24)
* mac80211: fix detecting VHT capabilities when generating the default configFelix Fietkau2021-11-231-1/+1
| | | | | | | | The colon does not directly follow the "VHT Capabilities" string Reported-by: John Thomson <git@johnthomson.fastmail.com.au> Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 3518b793a2f2293e7e9124b5beae7b09887c5e32)
* mac80211: add more HE capabilitiesFelix Fietkau2021-11-231-5/+81
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit fbd6f099f50e77d2bb95708c62e86a358779251a)
* mac80211: fix center freq selection for 6 GHzFelix Fietkau2021-11-231-6/+20
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 8d79915327b7b9ed221f513589281328e4fdc6ef)
* mac80211: set hostapd op_class for 6 GHzFelix Fietkau2021-11-231-0/+8
| | | | | | | This is needed to disambiguate it from 5 GHz channels Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit c8bcdd561909034a14cbfd785e13848cbd5f5e50)
* mac80211: rework default config scriptFelix Fietkau2021-11-231-20/+85
| | | | | | | | Emit the new band option instead of hwmode Support 6 GHz band and HE options Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 8504212f65865449dd6b9ed9daa0ba9781f8f287)
* mac80211: make use of the new 'band' optionFelix Fietkau2021-11-231-14/+31
| | | | | | | | Use it to look up frequencies only in the configured band to better deal with channel number overlap Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 8b8c1cb09bf2259e647a15d0c881b5dea15330da)
* netifd: update to the master branchFelix Fietkau2021-11-231-3/+3
| | | | | | Sync with commit 4eba313065f372ef0edf4abdbe00538fdbe7538f Signed-off-by: Felix Fietkau <nbd@nbd.name>
* iw: enable print wpa ie for scanJianhui Zhao2021-11-231-19/+25
| | | | | | | | This increases the size of the iw_5.9-8fab0c9e-3_mips_24kc.ipk from 41166 to 41942 bytes by 776 bytes. Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com> (cherry-picked from commit 9df7eadcfd3129cecfb30ec78a43ae9b3175869e)
* netifd: fix deletion of ip tunnels (FS#4058)Hans Dedecker2021-11-171-3/+3
| | | | | | a68e805 system-linux: fix deletion of ip tunnels (FS#4058) Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* uboot-lantiq: danube: fix hanging lzma kernel uncompressionMathias Kresin2021-11-141-0/+48
| | | | | | | | | | | | | | | | | | | | | | | At least since gcc 7.3.0 (OpenWrt 18.06) lwr/lwl are used in the assembly of LzmaProps_Decode. While the decission made by the compiler looks perfect fine, it triggers some obscure hang on lantiq danube-s v1.5 with MX29LV640EB NOR flash chips. Only if the offset 1 is used, the hang can be observed. Using any other offset works fine: lwl s0,0(a1) - s0 == 0x6d000080 lwl s0,1(a1) - hangs lwl s0,2(a1) - s0 == 0x0080xxxx lwl s0,3(a1) - s0 == 0x80xxxxxx It isn't clear whether it is a limitation of the flash chip, the EBU or something else. Force 8bit reads to prevent gcc optimizing the read with lwr/lwl instructions. Signed-off-by: Mathias Kresin <dev@kresin.me>
* wireless-regdb: update to version 2021.08.28Christian Lamparter2021-11-071-2/+2
| | | | | | | | | | | | | e983a25 Update regulatory rules for Ecuador (EC) a0bcb88 wireless-regdb: Update regulatory rules for Norway (NO) on 6 and 60 GHz cdf854d wireless-regdb: Update regulatory rules for Germany (DE) on 6GHz 86cba52 wireless-regdb: reduce bandwidth for 5730-5850 and 5850-5895 MHz in US 6fa2384 wireless-regdb: remove PTMP-ONLY from 5850-5895 MHz for US 9839e1e wireless-regdb: recent FCC report and order allows 5850-5895 immediately 42dfaf4 wireless-regdb: update 5725-5850 MHz rule for GB Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit dbb4c47798b17112cb1eed2a309cdefd33b5f193)
* kernel: bump 5.4 to 5.4.158Hauke Mehrtens2021-11-0733-133/+73
| | | | | | | | | | | | Removed upstreamed: generic/backport-5.4/790-v5.7-net-switchdev-do-not-propagate-bridge-updates-across.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>
* base-files: chmod 1777 /var/lockDeomid Ryabkov2021-11-051-2/+3
| | | | | | | | | | | | | | Per FHS 3.0, /var/lock is the location for lock files [1]. However its current permissions (755) are too restrictive for use by unprivileged processes. Debian and Ubuntu set them to 1777, and now so do we. [1] <https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#varlockLockFiles> Signed-off-by: Deomid Ryabkov <rojer@rojer.me> [fixed typo in commit message, had to remove "rojer" due to git hooks] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 430f69194388ad6a7826a51e0e2b2dd478e27f0f)
* libpcap: add rpcapd as packageStephan Schmidtmer2021-11-051-1/+20
| | | | | | | | | | | | | | This enables building of rpcapd and adds it as a package. It is a daemon that allows remote packet capturing from another machine. E.g. Wireshark can talk to it using the Remote Capture Protocol (RPCAP). https://www.tcpdump.org/manpages/rpcapd.8.html Compile and run tested: OpenWrt 21.02.0-rc4 r16256-2d5ee43dc6 on x86/64 and mvebu/cortexa9 Signed-off-by: Stephan Schmidtmer <hurz@gmx.org> (cherry picked from commit 891c8676a1602d31adf3ab9f913664ae0d3b4029)
* gpio-button-hotplug: convert to gpio descriptor (gpiod_) APIChristian Lamparter2021-11-051-79/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OpenWrt's special gpio-button-hotplug driver is still using exclusively the legacy GPIO Subsystem gpio_ API. While it still does work fine for most devices, upstream linux is starting to convert platform support like that of the APU2/3/4 to the new GPIOD LOOKUP tables that are not supported by it. Hence, this patch replaces the gpio_ calls present in gpio-button-hotplug with gpiod_ equivalent wherever it's possible. This allows the driver to use the gpiod lookup tables and still have a fallback for legacy platform data code that just sets button->gpio set to the real button/switch GPIO. As a bonus: the active_low logic is now being handled by the linux's gpio subsystem too. Another issue that was address is the of_handle leak in the dt parser error path. Tested with legacy platform data: x86_64: APU2, MX-100 Tested on OF: ATH79; MR18, APM821xx: Netgear WNDR4700, RAMIPS: WL-330N3G LANTIQ: AVM FritzBox 7360v1 Reported-by: Chris Blake <chrisrblake93@gmail.com> Tested-by: Chris Blake <chrisrblake93@gmail.com> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 2b0378cf9f3163bac29fa9946b3aa1607fc03802)
* bcm4908: fix calculation of new cferam indexSungbo Eo2021-11-051-2/+2
| | | | | | | | | | | | | | The arithmetic expansion fails when idx becomes a two digit number. Fix this by relying on expr command. root@OpenWrt:/# echo $(((028 + 0) % 1000)) /bin/ash: arithmetic syntax error root@OpenWrt:/# echo $(($(expr 028 + 0) % 1000)) 28 Fixes: a6a0b252baa6 ("bcm4908: add sysupgrade support") Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit f4323538501d58298f4df73a034a51375a477cfc)
* ramips: minew g1-c: Allow dynamic RAM sizesBruno Randolf2021-11-011-5/+0
| | | | | | | | Allow RAM size to be passed thru U-Boot. There are 128MB and 64MB versions of Minew G1-C. This is also in line with the behaviour of most other RAMIPS boards. Signed-off-by: Bruno Randolf <br1@einfach.org>
* iproute2: m_xt.so depends on dynsyms.listRoman Yeryomin2021-10-271-1/+2
| | | | | | | | | | | | | | | | | | | When doing parallel build on a fast machine with bottleneck in i/o, m_xt.so may start linking faster than dynsyms.list gets populated, resulting in error: ld:dynsyms.list:0: syntax error in dynamic list Fix this by adding dynsyms.list as make dependency to m_xt.so Described also here: https://bugs.openwrt.org/index.php?do=details&task_id=3353 Change from v1: - add dynsysms.list dependancy only when shared libs are enabled Signed-off-by: Roman Yeryomin <roman@advem.lv> Fixes: FS#3353 (cherry-picked from commit edd53df16843a0a6380920ed17b88bfe7d26d71b)
* OpenWrt v21.02.1: revert to branch defaultsHauke Mehrtens2021-10-255-11/+10
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* OpenWrt v21.02.1: adjust config defaultsv21.02.1Hauke Mehrtens2021-10-255-10/+11
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ipq40xx: ar40xx: reset port status registerDavid Bauer2021-10-241-2/+1
| | | | | | | | This resolves incosnsitencies of the configured RX / TX flow control modes between different boards or bootloaders. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 4d81f087715524994448ecaefd3ca87c8ba7e0a3)
* wolfssl: fix compile when enable-devcrypto is setIvan Pavlov2021-10-231-0/+22
| | | | | | | | fixing linking error when --enable-devcrypto=yes fixes: 7d92bb050961 wolfssl: update to 4.8.1-stable Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com> (cherry picked from commit be3e260f92643a841f4f83b03cbb07b9a26cff66)
* wolfssl: remove --enable-sha512 configure switchAndre Heider2021-10-231-2/+2
| | | | | | | | | | | It's the default anyway and this just looks confusing, as if it wasn't. Switch to AUTORELEASE while at it. The binary size is unchanged. Signed-off-by: Andre Heider <a.heider@gmail.com> (cherry picked from commit 7cb5af30f48d6788cd471138820a772610a7f8e0)
* wolfssl: always build with --enable-reproducible-buildAndre Heider2021-10-231-0/+1
| | | | | | | | | | | | This gates out anything that might introduce semantically frivolous jitter, maximizing chance of identical object files. The binary size shrinks by 8kb: 1244352 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f 1236160 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f Signed-off-by: Andre Heider <a.heider@gmail.com> (cherry picked from commit c76300707e8d705d9efc7ed4bb1b7449d0a5fe00)
* ath79: mikrotik: use 64 KiB SPI NOR erase sectorsRoger Pueyo Centelles2021-10-221-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch removes CONFIG_MTD_SPI_NOR_USE_4K_SECTORS from the default symbols for the ath79/mikrotik target. MikroTik devices hold some of their user-configurable settings in the soft_config partition, which is typically sized 4 KiB, of the SPI NOR flash memory. Previously, in the ar71xx target, it was possible to use 64 KiB erase sectors but also smaller 4 KiB ones when needed. This is no longer the case in ath79 with newer kernels so, to be able to write to these 4 KiB small partitions without erasing 60 KiB around, the CONFIG_MTD_SPI_NOR_USE_4K_SECTORS symbol was added to the defaults. However, this ended up making sysupgrade images which were built with 64 KiB size blocks not to keep settings (e.g., the files under /etc/config/) over the flashing process. Using 4 KiB erase sector size on the sysupgrade images (by setting BLOCKSIZE = 4k) allows keeping settings over a flashing process, but renders the process terribly slow, possibly causing a user to mistakenly force a manual device reboot while the process is still on- going. Instead, ditching the 4 KiB erase sectors for the default 64 KiB erase size provides normal SPI write speed and sysupgrade times, at the expense of not being able to modify the soft_config partition (which is rarely a required thing). An OpenWrt patch for MTD_SPI_NOR_USE_4K_SECTORS_LIMIT may once have allowed to use different per-partition erase sector sizes. Due to changes on recent kernels it now only works on a per-device basis. Also, partial eraseblock write can be performed in ath79 with kernels 5.4 and lower, by copying the blocks from the 64 KiB, erasing the whole sector and restoring those blocks not meant to be modified. A kernel bump had that patch broken for a long time, but got fixed in bf2870c. Note: the settings in the soft_config partition can be reset to their defaults by holding the reset button for 5 seconds (and less than 10 seconds) at device boot. Fixes: FS#3492 (sysupgrade […] loses settings...) Fixes: a66eee63368e (ath79: add mikrotik subtarget) Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> (cherry picked from commit 68d91f08edd0efd47841a2e53d3437d570a61612)
* wolfssl: update to 4.8.1-stableIvan Pavlov2021-10-225-18/+24
| | | | | | | | | | | | | | Changes from 4.7.0: Fix one high (OCSP verification issue) and two low vulnerabilities Improve compatibility layer Other improvements and fixes For detailed changes refer to https://github.com/wolfSSL/wolfssl/releases Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com> (cherry picked from commit 7d92bb0509615550b98e2dc71091073c8258d564) [Added patch to allow compilation with libtool 2.4] Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* wolfssl: fix build with GCC 10 on 32 x86 targetsStijn Tintel2021-10-221-0/+123
| | | | | | | Backport upstream patch to fix build with GCC 10 on 32 x86 targets. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> (cherry picked from commit 718a4f47806da8f68cb8f1fe2ebecf403e14ae96)
* layerscape: Add missing config optionHauke Mehrtens2021-10-221-0/+1
| | | | | | | This option is not set when building the target. In master this is also unset. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* 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: b4ed8a92751f ("kernel: bump 5.4 to 5.4.154") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 9501ce909f54b87dab95f17c0408a4962365e130)
* ncurses: add tmux terminfoJitao Lu2021-10-211-1/+3
| | | | | | | | | | | They're preferred terminal descriptions for tmux, with additional support to some special characters and italic fonts. More info can be found at: https://github.com/tmux/tmux/wiki/FAQ Fixes: FS#3404 Signed-off-by: Jitao Lu <dianlujitao@gmail.com> (cherry picked from commit 917126ff4cfb1ea4795cfc93820ed5d304b084c3)
* ncurses: add screen-256color terminfoPaul Spooren2021-10-211-1/+2
| | | | | | | | The terminfo is required by the popular terminal multiplexer screen and tmux, offer it by default as the size impact is minimal with 885 Bytes. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 6a6b5a677e8c245f6c82ad40cc718e614aa9f7a1)
* ncurses: split long line of supported terminfoPaul Spooren2021-10-211-1/+12
| | | | | | | | The terminfo files were all in one row which is terrible to read. Split them over multiple lines to improve readability. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 75ea474b9002c758e9a23023f7636258a467704c)
* glibc: update to latest 2.33 HEAD (bug 28213)Hans Dedecker2021-10-211-2/+2
| | | | | | | | | | | 9b01145592 MIPS: Setup errno for {f,l,}xstat 9c676ef514 RISC-V: Update rv64 ULPs c6cadbf83a linux: Remove shmmax check from tst-sysvshm-linux 22d37364ae librt: add test (bug 28213) 27a78fd712 librt: fix NULL pointer dereference (bug 28213) Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> (cherry picked from commit c6a2ffd505cf7b8ce7ea0424a7709bb8f73e6999)
* tools/isl: update the download URLRui Salvaterra2021-10-211-1/+1
| | | | | | | | | | isl.gforge.inria.fr has been dead since early this month [1]. Switch to libisl.sourceforge.io for the time being. [1] https://groups.google.com/g/isl-development/c/JGaMo2VUu_8 Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> (cherry picked from commit dd0ad9b661b604163d1736fcfe18714ff47c3728)
* ath10k-ct: update to version from 2021-09-22Andrew Robbins2021-10-212-4/+4
| | | | | | | | | Add in a fix for 160Mhz dfs on 5.10 and higher. Add support for 5.13 and 5.15 kernels. Add of_get_mac_address support for 5.15 driver. Signed-off-by: Andrew Robbins <andrew@robbinsa.me> (cherry picked from commit 1d2bc94f786434e89bc87003b2a2202e92ad84e7)
* tools/m4: update to 1.4.19Rosen Penev2021-10-203-145/+2
| | | | | | | Remove upstreamed patches. Signed-off-by: Rosen Penev <rosenp@gmail.com> (cherry picked from commit fc9682ed3961e098ace708ca1ca41c2239a4e2ee)
* kernel: bump 5.4 to 5.4.154Hauke Mehrtens2021-10-2032-1720/+70
| | | | | | | | | | | | Removed upstreamed: generic/backport-5.4/070-v5.5-MIPS-BPF-Restore-MIPS32-cBPF-JIT.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>
* wolfssl: bump PKG_RELEASEDavid Bauer2021-10-191-1/+1
| | | | | | Fixes commit 4b212b1306a9 ("wolfssl: build with WOLFSSL_ALT_CERT_CHAINS") Signed-off-by: David Bauer <mail@david-bauer.net>
* wolfssl: build with WOLFSSL_ALT_CERT_CHAINSAndre Heider2021-10-171-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | "Alternate certification chains, as oppossed to requiring full chain validataion. Certificate validation behavior is relaxed, similar to openssl and browsers. Only the peer certificate must validate to a trusted certificate. Without this, all certificates sent by a peer must be used in the trust chain or the connection will be rejected." This fixes e.g. uclient-fetch and curl connecting to servers using a Let's Encrypt certificate which are cross-signed by the now expired DST Root CA X3, see [0]. This is the recommended solution from upstream [1]. The binary size increases by ~12.3kb: 1236160 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f 1248704 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f [0] https://github.com/openwrt/packages/issues/16674 [1] https://github.com/wolfSSL/wolfssl/issues/4443#issuecomment-934926793 Signed-off-by: Andre Heider <a.heider@gmail.com> [bump PKG_RELEASE] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 28d8e6a8711ba78f1684a205e11b0dbd4ff2b2f3)
* mvebu: add support for iEi Puzzle-M901/Puzzle-M902Ian Chang2021-10-146-0/+868
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware specification ---------------------- * CN9130 SoC, Quad-core ARMv8 Cortex-72 @ 2200 MHz * 4 GB DDR * 4 GB eMMC * mmcblk0 - mmcblk0p1 64M kernel_1 - mmcblk0p2 64M kernel_2 - mmcblk0p3 512M rootfs_1 - mmcblk0p4 512M rootfs_2 - mmcblk0p5 512M Reserved - mmcblk0p6 64M Reserved - mmcblk0p7 1.8G rootfs_data * 4 MB (SPI Flash) * 6 x 2.5 Gigabit ports (Puzzle-M901) - External PHY with 6 ports (AQR112R) * 6 x 2.5 Gigabit ports (Puzzle-M902) - External PHY with 6 ports (AQR112R) 3 x 10 Gigabit ports (Puzzle-M902) - External PHY with 3 ports (AQR113R) * 4 x Front panel LED * 1 x USB 3.0 * Reset button on Rear panel * UART (115200 8N1,header on PCB) Flash instructions: The original firmware is based on OpenWrt. Flash firmware using LuCI and CLI Signed-off-by: Ian Chang <ianchang@ieiworld.com> (cherry picked from commit 70c75965a97799b44871249c205bad48fea9a4ae) Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: backport CN9130 dts necessary files changes to 5.4Ian Chang2021-10-1410-0/+2883
| | | | | | | | | | | 1. Add support for Marvell CN9130 SoC 2. Add support for CP115,and create an armada-cp11x.dtsi file which will be used to instantiate both CP110 and CP115 3. Add support for AP807/AP807-quad,AP807 is a major component of CN9130 SoC series 4. Drop PCIe I/O ranges from CP11x file and externalize PCIe macros from CP11x file Signed-off-by: Ian Chang <ianchang@ieiworld.com> (cherry picked from commit c98ddf0f019986bbb4c868bfcaf97e0d1f4ee2dc) Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* build: prereq detect Python 3.10 for `python3` binaryPaul Spooren2021-10-121-2/+2
| | | | | | | | | | | While the binary `python3.10` is correctly detected by the build system the default `python3` binary is currently not detected if pointing to a Python 3.10 installation. Fix this by extending the grep regex. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 56ea2bf2eec431ccd3c566190a444ad63db39b65)