[pull] master from coolsnowwolf:master #1129
Open
+591,171
−428,818
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
coolsnowwolf
force-pushed
the
master
branch
from
7b04035 to
037eb44
Compare
coolsnowwolf
force-pushed
the
master
branch
from
02561ed to
6da4057
Compare
aiamadeus
force-pushed
the
master
branch
2 times, most recently
from
ad43ee0 to
fac34a2
Compare
coolsnowwolf
force-pushed
the
master
branch
3 times, most recently
from
66e03f1 to
2d1c8ab
Compare
aiamadeus
force-pushed
the
master
branch
3 times, most recently
from
6269d0f to
9f65b6f
Compare
Use pending patchset for 2.5GE PHY driver, unifying LED handling accross all MediaTek Ethernet PHYs. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Add additionals possible pinctrl group for pwm2~7 on pins pin 4 (GPIO_A) pwm7 pin 58 (JTAG_JTDI) pwm2 pin 59 (JTAG_JTDO) pwm3 pin 60 (JTAG_JTMS) pwm4 pin 61 (JTAG_JTCLK) pwm5 pin 62 (JTAG_JTRST_N) pwm6 They can be useful e.g. on the BPi-R4 as in that way pwm2~6 can be exposed on the 26-pin header (pwm6 always, pwm2~5 instead of the full UART). Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Assign pwm function of PWM0 pin to the pwm-fan. This is mostly just cosmetics as it basically reflects the default setting of that pin. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
The clocks for SPI busses were named wrongly which resulted in the spi-mt65xx driver not requesting them. This has apparently been worked around by marking the clocks required for SPI0 which is used for SPI-NOR and SPI-NAND flash chips as critical. Fix the device tree for all 3 generic SPI host controllers and no longer mark clocks as critical. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
leigod-acc: fixed bind issues & use fail issues
Changelog: openwrt/rtl8168@8.053.00...8.054.00 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Changelog: openwrt/rtl8125@9.013.02...9.014.01 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Uses upstream DSA switch modules (rtl8365mb, rtl8366), similar to RTL8367C and rtl8366rb swconfig drivers. The package dependencies exclude targets built without kernel CONFIG_OF. It also fixes the rtl8366rb LED support. Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com> Signed-off-by: Robert Marko <robimarko@gmail.com>
Detect the RTL8367D chip family and set the appropriate extif Co-authored-by: Serge Vasilugin <vasilugin@yandex.ru> Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
The FDB roaming issues were observed on ipq807x and ipq60xx boards. The fix depends on API exposed only when NSS_DP_PPE_SUPPORT is enabled. However, this flag applies to above mentioned platforms only and is causing the logs to be flooded on other QCA platforms, including ipq50xx, with: [ 34.893418] nss-dp 39c00000.dp1 lan: cannot get VSI ID for port 1 [ 34.898370] nss-dp 39c00000.dp1 lan: cannot get VSI ID for port 1 [ 34.904598] nss-dp 39c00000.dp1 lan: cannot get VSI ID for port 1 [ 34.910661] nss-dp 39c00000.dp1 lan: cannot get VSI ID for port 1 So let's apply a dependency on the NSS_DP_PPE_SUPPORT flag and contain the patch code for ipq807x and ipq60xx within conditional directives. Tested on: Linksys SPNMX56 Signed-off-by: George Moussalem <george.moussalem@outlook.com> Link: openwrt/openwrt#17966 Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Felix Fietkau <nbd@nbd.name>
The calculation in some cases does not finish for non-prime p. This fixes CVE-2022-0778. Based on patch by David Benjamin <davidben@google.com>. Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Co-authored-by: Su Yindu <yindusu@smu.edu.sg>
Refreshed patches for qualcommb/ipq95xx by running make target/linux/refresh after creating a .config containing: CONFIG_TARGET_qualcommbe=y CONFIG_TARGET_qualcommbe_ipq95xx=y CONFIG_TARGET_qualcommbe_ipq95xx_DEVICE_qcom_rdp433=y Signed-off-by: John Audia <therealgraysky@proton.me> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Introduce EN7581 SoC support with currently rfb board supported. This is a new 64bit SoC from Airoha that is currently almost fully supported upstream with only the DTS missing. Setting source-only waiting for the full upstream support to be completed. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Setting up usb gadgets using g_* kernel modules are considered a legacy approach, but the usb_gadget configfs is a bit annoying to use directly. The usb_gadget configfs works by creating magic directories and writing to magic files under /sys/kernel/config/usbgadget. This new package is an init script to setup usb_gadget configfs using uci. In the config file, gadget/configuration/function sections create corresponding directories. UCI options are magic files available in the configfs and strings/0x409 directories, grabbed with a 'find' command. UDC option in gadget writes the UDC file under the 'gadget' directory to attach the generated gadget config. It's also possible to apply pre-made config templates under /usr/share/usbgadget. The templates use the same UCI config format, with the 'gadget' entry named 'g1'. Currently, there are templates for CDC-ACM and CDC-NCM gadgets written based on existing g_*.ko module code. Certain SBCs come with only a USB device port (e.g. Raspberry Pi Zero). With this script, it's now possible to perform initial setup on them by adding a default NCM gadget. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
rockchop:fine3399 wifi support
The calculation in some cases does not finish for non-prime p. This fixes CVE-2022-0778. Based on patch by David Benjamin <davidben@google.com>. Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )