summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bcm53xx: refresh kernel configopenwrt-21.02Rafał Miłecki2023-11-061-68/+3
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: backport 1 more late DT patch accepted for v6.7Rafał Miłecki2023-10-262-44/+63
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 732ae343ffb3ad19978b75a8105d55f5e6d1d435)
* bcm53xx: disable unused switch ports in downstream patchRafał Miłecki2023-10-261-16/+144
| | | | | | | | | This makes Linux use correct switch ports again. Fixes: fff279f4a712 ("bcm53xx: backport DT changes from v6.5") Fixes: https://github.com/openwrt/openwrt/issues/13548 Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a912ee74d6ca08020933dcdb9ce791e74244c25b)
* bcm53xx: backport DT changes queued for v6.7Rafał Miłecki2023-10-267-1/+686
| | | | | | | | | Among other changes this commit makes Linux use correct switch ports again. Fixes: fff279f4a712 ("bcm53xx: backport DT changes from v6.5") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a67af19bc84e98588c307af9b08686bde9dd38d5)
* bcm53xx: simplify patch adding switch portsRafał Miłecki2023-10-261-136/+16
| | | | | | | | We now have all raw ports defined in bcm-ns.dtsi. Leave only lables in custom device files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 08ce0c76d7d7daad5e9382d51960d69f4b8b8f3a)
* bcm53xx: build a single device per profileRani Hod2023-10-261-0/+1
| | | | | | | | | | | | | | | So far every build of a single bcm53xx Target Profile (it means: when NOT using CONFIG_TARGET_MULTI_PROFILE) resulted in all target devices images being built. Now it only builds the one matching selected profile. Fixes: #13572 Suggested-by: Jonas Gorski <jonas.gorski@gmail.com> Signed-off-by: Rani Hod <rani.hod@gmail.com> [rmilecki: update commit subject + body & move PROFILES line] Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 802a5f5cb4a7b42d25e82b787d7ab1323a20183f)
* bcm53xx: add support for ASUS RT-AC3100Arınç ÜNAL2023-10-261-0/+9
| | | | | | | | | | | | | | ASUS RT-AC3100 is ASUS RT-AC88U without the external switch. OpenWrt forum users effortless and ktmakwana have confirmed that there are revisions with either 4366b1 or 4366c0 wireless chips. Therefore, include firmware for 4366b1 along with 4366c0. This way, all hardware revisions of the router will be supported by having brcmfmac use the firmware file for the wireless chip it detects. Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com> (cherry picked from commit 2214bab3503981fe6168746acd13044a9d5e89e7)
* bcm53xx: backport DT changes for ASUS RT-AC3100 queued for v6.6Arınç ÜNAL2023-10-262-1/+432
| | | | | | | Backport the patch that adds the DT for ASUS RT-AC3100. Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com> (cherry picked from commit b7ee8c9f83ea0e3b861e6b71b08ed7a62066d149)
* ipq40xx: switch to performance governor by defaultKoen Vandeputte2023-10-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Doing a simple ping to my device shows this: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=2.00 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=2.02 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=1.68 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=1.91 ms 64 bytes from 10.0.253.101: icmp_seq=5 ttl=64 time=1.92 ms 64 bytes from 10.0.253.101: icmp_seq=6 ttl=64 time=2.04 ms Some users even report higher values on older kernels: 64 bytes from 192.168.1.10: seq=0 ttl=64 time=0.612 ms 64 bytes from 192.168.1.10: seq=1 ttl=64 time=2.852 ms 64 bytes from 192.168.1.10: seq=2 ttl=64 time=2.719 ms 64 bytes from 192.168.1.10: seq=3 ttl=64 time=2.741 ms 64 bytes from 192.168.1.10: seq=4 ttl=64 time=2.808 ms The problem is that the governor is set to Ondemand, which causes the CPU to clock all the way down to 48MHz in some cases. Switching to performance governor: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=0.528 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=0.561 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=0.633 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=0.526 ms In theory, using the Performance governor should increase power draw, but it looks like it really does not matter for this soc. Using a calibrated precision DC power supply (cpu idle): Ondemand 24.00V * 0.134A = 3.216 Watts 48.00V * 0.096A = 4.608 Watts Performance 24.00V * 0.135A = 3.240 Watts 48.00V * 0.096A = 4.608 Watts Let's simply switch to the Performance governor by default to fix the general jittery behaviour on devices using this soc. Tested on: MikroTik wAP ac Fixes: #13649 Reviewed-by: Robert Marko <robimarko@gmail.com> Reviewed-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: Koen Vandeputte <koen.vandeputte@citymesh.com> (cherry picked from commit b8e52852bd62236a2a84663b4592d221ebc64cb4)
* ath79: wpj563: enable 2nd USB controllerKoen Vandeputte2023-10-131-0/+8
| | | | | | | | | | | | | The compex WPJ563 actually has both usb controllers wired: usb0 --> pci-e slot usb1 --> pin header As the board exposes it for generic use, enable this controller too. fixes: #13650 Signed-off-by: Koen Vandeputte <koen.vandeputte@citymesh.com> (cherry picked from commit 9188c77cbee55a933d0fa75c74e175fbc52c556d)
* openssl: bump to 1.1.1vHauke Mehrtens2023-09-291-2/+2
| | | | | | | | | | Major changes between OpenSSL 1.1.1u and OpenSSL 1.1.1v [1 Aug 2023] o Fix excessive time spent checking DH q parameter value (CVE-2023-3817) o Fix DH_check() excessive time with over sized modulus (CVE-2023-3446) Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit de29f15af173e9434d11a00ffcf437bd6bc97727)
* openssl: bump to 1.1.1uHauke Mehrtens2023-09-293-265/+3
| | | | | | | | | | | | | | Major changes between OpenSSL 1.1.1t and OpenSSL 1.1.1u [30 May 2023] o Mitigate for very slow `OBJ_obj2txt()` performance with gigantic OBJECT IDENTIFIER sub-identities. (CVE-2023-2650) o Fixed documentation of X509_VERIFY_PARAM_add0_policy() (CVE-2023-0466) o Fixed handling of invalid certificate policies in leaf certificates (CVE-2023-0465) o Limited the number of nodes created in a policy tree ([CVE-2023-0464]) Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit afb442270211c00282cecf323d568aa88391a32c)
* treewide: Add extra CPE identifierHauke Mehrtens2023-09-274-0/+4
| | | | | | | This adds some Common Platform Enumerations (CPE) identifiers which I found. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* toolchain: musl: add PKG_CPE_IDArne Zachlod2023-09-271-0/+1
| | | | | | | Vulnerabilities of musl libc are tracked as cpe:/a:musl-libc:musl Signed-off-by: Arne Zachlod <arne@nerdkeller.org>
* toolchain: assign PKG_CPE_IDAlexander Couzens2023-09-276-0/+6
| | | | | | | | | The PKG_CPE_ID links to NIST CPE version 2.2. Assign PKG_CPE_ID to all remaining package which have a CPE ID. Not every package has a CPE id. Related: https://github.com/openwrt/packages/issues/8534 Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* tools: assign PKG_CPE_IDAlexander Couzens2023-09-275-0/+5
| | | | | | | | | The PKG_CPE_ID links to NIST CPE version 2.2. Assign PKG_CPE_ID to all remaining tools which have a CPE ID. Not every tool has CPE id. Related: https://github.com/openwrt/packages/issues/8534 Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* packages: assign PKG_CPE_ID for all missing packagesAlexander Couzens2023-09-2713-0/+14
| | | | | | | | | The PKG_CPE_ID links to NIST CPE version 2.2. Assign PKG_CPE_ID to all remaining package which have a CPE ID. Not every package has CPE id. Related: https://github.com/openwrt/packages/issues/8534 Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* x86: geode: fix hwrng register accessesJonas Gorski2023-09-141-0/+47
| | | | | | | | | | | | | | | | | | | | When the membase and pci_dev pointer were moved to a new struct in priv, the actual membase users were left untouched, and they started reading out arbitrary memory behind the struct instead of registers. This unfortunately turned the RNG into a constant number generator, depending on the content of what was at that offset. To fix this, update geode_rng_data_{read,present}() to also get the membase via amd_geode_priv, and properly read from the right addresses again. Closes #13417. Reported-by: Timur I. Davletshin <timur.davletshin@gmail.com> Tested-by: Timur I. Davletshin <timur.davletshin@gmail.com> Suggested-by: Jo-Philipp Wich <jo@mein.io> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> (cherry picked from commit 09d13cd8d87cc50fde67bbe81c6cca4b799b2724)
* urngd: update to the latest masterRafał Miłecki2023-09-011-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | 7aefb47 jitterentropy-rngd: update to the v1.2.0 What's interesting about jitterentropy-rngd v1.2.0 release is that it bumps its copy of jitterentropy-library from v2.2.0 to the v3.0.0. That bump includes a relevant commit 3130cd9 ("replace LSFR with SHA-3 256"). When initializing entropy jent calculates time delta. Time values are obtained using clock_gettime() + CLOCK_REALTIME. There is no guarantee from CLOCK_REALTIME of unique values and slow devices often return duplicated ones. A switch from jent_lfsr_time() to jent_hash_time() resulted in many less cases of zero delta and avoids ECOARSETIME. Long story short: on some system this fixes: [ 6.722725] urngd: jent-rng init failed, err: 2 This is important change for BCM53573 which doesn't include hwrng and seems to have arch_timer running at 36,8 Hz. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit c74b5e09e692839b39c8325b5f8dc5f2a3b3896c)
* bcm53xx: backport more DT changes queued for v6.6Rafał Miłecki2023-07-298-28/+290
| | | | | | | Those sort out BCM53573 Ethernet info finally. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ca8868a51127f6081a524d47eab937b90af0bf05)
* bcm53xx: add BCM53573 Ethernet fix sent upstream for v6.6Rafał Miłecki2023-07-291-0/+28
| | | | | | | | | | | | | | It seems that DSA-based b53 driver never worked with BCM53573 SoCs and BCM53125. In case of swconfig-based b53 this fixes a regression. Switching bgmac from using mdiobus_register() to of_mdiobus_register() resulted in MDIO device (BCM53125) having of_node set (see of_mdiobus_register_phy()). That made downstream b53 driver read invalid data from DT and broke Ethernet support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 79fd3e62b4910731c13692b2daa2083e0f95c023)
* sdk: rename README + update MakefileTomasz Maciej Nowak2023-07-202-1/+1
| | | | | | | | | | | | | 'help' target fails not finding a file, so follow up on a change[2] made as a fix for main README[1]. 1. d0113711a31f ("README: port to 21st century") 2. 751486b31fd9 ("build: fix README.md reference after rename") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (cherry picked from commit 2d5f7035cf45801158bed6f5d0ac0de0002c1810) (cherry picked from commit e9911f10e482f3174f745a36c0c9fd7964758caf) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ib: split out processing user provided packagesTomasz Maciej Nowak2023-07-201-1/+3
| | | | | | | | | | Some device recipes remove default target packages. If user tries to add them back they will be ignored, since packages list is processed in one go. Process the device recipe packages first and do user ones later, so additions won't get filtered out. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (cherry picked from commit e40b9a7fa002154e85459791101a0444d99dfb86)
* bcm53xx: backport DT changes queued for v6.6Rafał Miłecki2023-07-1410-1/+474
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 37ff916af789911fdefb802ce9903e866eb82435)
* bcm53xx: backport DT changes from v6.5Rafał Miłecki2023-07-1128-11/+4883
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 8674b41c0d84f09e14bf8ebe08e1d6dc6ac5fa64)
* kernel: bgmac: fix regressed support for BCM53573 SoCsRafał Miłecki2023-07-101-0/+45
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit d54f3b2cfdbd34aa61ca67fd590eebfdf3db51cf)
* kernel: fix bgmac support for BCM5358Rafał Miłecki2023-07-102-6/+82
| | | | | | | | Fix two long-standing regressions. Fixes: https://github.com/openwrt/openwrt/issues/8278 Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 5e48c534f7c6b3a861f4a2dbb81d7bfcd9606f61)
* bcm47xx: fix bgmac regression present in 5.4 kernelRafał Miłecki2023-07-101-0/+42
| | | | | | | | | | This fixes: [ 2.548098] bgmac_bcma bcma0:1: Failed to register fixed PHY device [ 2.554584] bgmac_bcma bcma0:1: Cannot connect to phy and downstream (swconfig-based) b53 driver failing to load. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 6cdac994012003065a7040ceba3186f80db3cdbe)
* kernel: backport bgmac upstream commits from 5.15 / for 5.16Rafał Miłecki2023-07-102-0/+138
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit fd71ef34b75c81646d17d21d80dc3a5b5e2e6bb8)
* bcm63xx: fix NETGEAR DGND3700v2 boot loopÁlvaro Fernández Rojas2023-06-151-0/+1
| | | | | | | | | | | | | The DGND3700v2 renames the cferam bootloader from cferam to cfeXXX, where XXX is the number of firmware upgrades performed by the bootloader. Other bcm63xx devices rename cferam.000 to cferam.XXX, but this device is special because the cferam name isn't changed on the first firmware flashing but it's changed on the subsequent ones. Therefore, we need to look for "cfe" instead of "cferam" to properly detect the cferam partition and fix the bootlop. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit cdfcac6e246de9f237d1425e498db3f34ddebbaf)
* kernel: mtd: bcm-wfi: add cferam name supportÁlvaro Fernández Rojas2023-06-151-2/+14
| | | | | | | | | Some devices rename cferam bootloader using specific patterns and don't follow broadcom standards for renaming cferam files. This requires supporting different cferam file names. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit 8813edd8d9695d4e3939fdaa3c530c682f91de11)
* build: generate index.jsonPaul Spooren2023-05-111-0/+4
| | | | | | | | | | | | The index.json file lies next to Packages index files and contains a json dict with the package architecture and a dict of package names and versions. This can be used for downstream project to know what packages in which versions are available. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 218ce40cd738f3373438aab82467807a8707fb9c)
* OpenWrt v21.02.7: revert to branch defaultsHauke Mehrtens2023-04-275-11/+10
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* OpenWrt v21.02.7: adjust config defaultsv21.02.7Hauke Mehrtens2023-04-275-10/+11
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* openssl: fix CVE-2023-464 and CVE-2023-465Eneas U de Queiroz2023-04-173-1/+263
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apply two patches fixing low-severity vulnerabilities related to certificate policies validation: - Excessive Resource Usage Verifying X.509 Policy Constraints (CVE-2023-0464) Severity: Low A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. - Invalid certificate policies in leaf certificates are silently ignored (CVE-2023-0465) Severity: Low Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. Note: OpenSSL also released a fix for low-severity security advisory CVE-2023-466. It is not included here because the fix only changes the documentation, which is not built nor included in any OpenWrt package. Due to the low-severity of these issues, there will be not be an immediate new release of OpenSSL. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* kernel: backport fix for recently introduced UBI bugDaniel Golle2023-04-152-2/+71
| | | | | | | | | | Import commit "ubi: Fix failure attaching when vid_hdr offset equals to (sub)page size" which did not yet make it to stable upstream Linux trees. Fixes: #12232 Fixes: #12339 Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit aad34818b50029e07ed9221ae46f9770d6e29785)
* uclient: update to Git version 2023-04-13Matthias Schiffer2023-04-131-3/+3
| | | | | | | | | 007d94546749 uclient: cancel state change timeout in uclient_disconnect() 644d3c7e13c6 ci: improve wolfSSL test coverage dc54d2b544a1 tests: add certificate check against letsencrypt.org Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> (cherry picked from commit 4f1c2e8deef10e9ca34ceff5a096e62aaa668e90)
* OpenWrt v21.02.6: revert to branch defaultsDaniel Golle2023-04-095-11/+10
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* OpenWrt v21.02.6: adjust config defaultsv21.02.6Daniel Golle2023-04-095-10/+11
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* imagebuilder: allow to specific ROOTFS_PARTSIZEPaul Spooren2023-04-091-1/+3
| | | | | | | | | | | | Setting this options modifies the rootfs size of created images. When installing a large number of packages it may become necessary to increase the size to have enough storage. This option is only useful for supported devices, i.e. with an attached SD Card or installed on a hard drive. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 7b7edd25a571568438c886529d3443054e02f55f)
* kernel: remove obsolete netfilter tcp window size check bypass patchFelix Fietkau2023-03-301-73/+0
| | | | | | | | On any currently supported hardware, the performance impact should not matter anymore. Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit 75e78bcaab847557ce1782eb2dea9dff9a029171)
* mac80211, mt76: add fixes for recently discovered security issuesFelix Fietkau2023-03-309-9/+676
| | | | | | | Fixes CVE-2022-47522 Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit d54c91bd9ab3c54ee06923eafbd67047816a37e4)
* ipq40xx: Linksys MR8300: fix the USB port powerDaniel González Cabanelas2023-03-291-1/+11
| | | | | | | | | | | | | | | The USB port on the MR8300 randomly fails to feed bus-powered devices. This is caused by a misconfigured pinmux. The GPIO68 should be used to enable the USB power (active low), but it's inside the NAND pinmux. This GPIO pin was found in the original firmware at a startup script in both MR8300 and EA8300. Therefore apply the fix for both boards. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> Reviewed-by: Robert Marko <robimarko@gmail.com> (cherry picked from commit ed64c3323590e3c9fa8b423bf37689023a7a101f) Signed-off-by: Steffen Scheib <steffen@scheib.me>
* kernel: bump 5.4 to 5.4.238Hauke Mehrtens2023-03-2988-318/+300
| | | | | | | Compile-tested: armvirt/64, lantiq/xrx200 Run-tested: armvirt/64, lantiq/xrx200 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: ltq-tapi: add kernel 5.10 compatiblityMathias Kresin2023-03-291-0/+51
| | | | | | | | | | | | | | Due to SCHED_FIFO being a broken scheduler model, all users of sched_setscheduler() are converted to sched_set_fifo_low() upstream and sched_setscheduler() is no longer exported. The callback handling of the tasklet API was redesigned and the macros using the old syntax renamed to _OLD. Signed-off-by: Mathias Kresin <dev@kresin.me> (cherry picked from commit 31f3f797004ad318a1de88ec9cfdece523ee46d9) [Add DECLARE_TASKLET handling for kernel 5.4.235 too] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ltq-atm/ltq-ptm: add kernel 5.10 compatiblityMathias Kresin2023-03-273-0/+27
| | | | | | | | | | | | | The callback handling of the tasklet API was redesigned and the macros using the old syntax renamed to _OLD. The stuck queue is now passed to ndo_tx_timeout callback but not used so far. Signed-off-by: Mathias Kresin <dev@kresin.me> (cherry picked from commit 804c541446ab8e3fab11dba5d8fe07807af7fac5) [Add DECLARE_TASKLET handling for kernel 5.4.235 too] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: tcindex classifier has been retiredJohn Audia2023-03-272-3/+1
| | | | | | | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/sched?h=v5.4.235&id=7a6fb69bbcb21e9ce13bdf18c008c268874f0480 Signed-off-by: John Audia <therealgraysky@proton.me> (cherry picked from commit fbfec3286e8bfce3a78749b7bcb67e658665f197)
* kernel: bump 5.4 to 5.4.234Hauke Mehrtens2023-03-275-6/+6
| | | | | | | Compile-tested: armvirt/64, lantiq/xrx200 Run-tested: armvirt/64 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm4908: include usbport triggerRafał Miłecki2023-03-271-1/+2
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit cb2661844a5d54d44230ee564d4f17605a794a49)
* bcm4908: backport v6.4 pending DTS changesRafał Miłecki2023-03-279-1/+791
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ffaabee9b8d9da7c15a50f52897ae5f70b40b4e7)
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-02 14:12:10 +0000