Updating the entire patchset from Raspberry Pi upstream would also add
the Raspberry Pi Zero 2 patch, but as that is a cumbersome process, just
import the required patch. Prefix it with 950 so it is clear that this
patch comes from the same source, but use a high number for the 2nd part
of the
This series adds support for the new Raspberry Pi Zero 2. I've been
running it on mine for 10 days.
Stijn Tintel (5):
cypress-firmware: update URL
mac80211: add patch for BCM43436 firmware
bcm43436-firmware: new package
bcm27xx-gpu-fw: bump to git HEAD
bcm27xx: add support for Raspberry
Signed-off-by: Stijn Tintel
---
package/kernel/bcm27xx-gpu-fw/Makefile | 30 +-
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/package/kernel/bcm27xx-gpu-fw/Makefile
b/package/kernel/bcm27xx-gpu-fw/Makefile
index b99912542b..faca1777fa 100644
---
This package contains the firmware for the Wi-Fi chip used in the
Raspberry Pi Zero 2. This firmware is not available in
linux-firmware.git, nor in the latest Cypress Linux Wi-Fi archive.
Signed-off-by: Stijn Tintel
---
package/firmware/bcm43436-firmware/Makefile | 36 +
1
Cypress was acquired by Infineon and the URL is no longer valid.
Signed-off-by: Stijn Tintel
---
package/firmware/cypress-firmware/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/firmware/cypress-firmware/Makefile
This chip is used in the Raspberry Pi Zero 2.
Signed-off-by: Stijn Tintel
---
...ac-BCM43436-needs-dedicated-firmware.patch | 29 +++
1 file changed, 29 insertions(+)
create mode 100644
package/kernel/mac80211/patches/brcm/865-brcmfmac-BCM43436-needs-dedicated-firmware.patch
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Ansuel,
below are a few
There's no such thing as ucidef_set_interfaces_lan. It's
ucidef_set_interface_lan.
Cc: David Bauer
Signed-off-by: Mark Mentovai
---
target/linux/mediatek/mt7622/base-files/etc/board.d/02_network | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Nov 19, 2021 at 12:47:41PM +0100, Janusz Dziedzic wrote:
> Hello,
>
> I see that my board negotiate only 100mbps on wan iface.
> First think cable or switch issue - but using same cable and
> same ext switch port I get 1000 when using lanX iface.
>
> Do you see the same - or my board
Hello,
I see that my board negotiate only 100mbps on wan iface.
First think cable or switch issue - but using same cable and
same ext switch port I get 1000 when using lanX iface.
Do you see the same - or my board have some issue with WAN?
Fresh master used.
root@OpenWrt:~# ethtool wan
Settings
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 19/11/2021 06:06, Felix
On 2021-11-18 12:58, Jo-Philipp Wich wrote:
Since OpenWrt's main libc library, musl, does not provide separate shared
object files for libpthread and librt, the existing binary packages for
them are empty placeholders which provide no runtime functionality and
frequently cause confusion among
By calling the command 'fw3 reload' several times at the same time, I
noticed that the locking was not working properly. It happened from time
to time that some firewall rules were present twice in the system!
By removing the 'unlink' systemcall, this error no longer occurred on my
systems.
13 matches
Mail list logo
