Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rpi-firmware: add firmware for zero 2w
Date: Tue, 06 Sep 2022 01:42:03 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39123@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

There is a new pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages rpi-firmware-02w
https://github.com/void-linux/void-packages/pull/39123

rpi-firmware: add firmware for zero 2w
<!-- Uncomment relevant sections and delete options which are not applicable -->

This took some figuring out, there's no documentation anywhere except a couple commit messages and blog posts.

- https://picockpit.com/raspberry-pi/raspberry-pi-zero-2-w-wifi-chipset-speeds-monitor-mode/
- https://github.com/RPi-Distro/firmware-nonfree/issues/24
- https://github.com/RPi-Distro/firmware-nonfree/commit/bda9207acee945633464e89614f3717b856579b5

#### Testing the changes
- I tested the changes in this PR: **YES**

```
```



A patch file from https://github.com/void-linux/void-packages/pull/39123.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rpi-firmware-02w-39123.patch --]
[-- Type: text/x-diff, Size: 1589 bytes --]

From 5560a366a8dbacd739cdfb7717d906cefb645710 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 5 Sep 2022 19:39:01 -0400
Subject: [PATCH] rpi-firmware: add firmware for zero 2w

---
 srcpkgs/rpi-firmware/template | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/rpi-firmware/template b/srcpkgs/rpi-firmware/template
index ed8529716065..62d809b840ce 100644
--- a/srcpkgs/rpi-firmware/template
+++ b/srcpkgs/rpi-firmware/template
@@ -4,7 +4,7 @@ _gitshort="${_githash:0:7}"
 
 pkgname=rpi-firmware
 version=20220823
-revision=1
+revision=2
 archs="armv6l* armv7l* aarch64*"
 wrksrc="firmware-${_githash}"
 provides="linux-firmware-broadcom-${version}_${revision}"
@@ -58,6 +58,16 @@ do_install() {
 	$XBPS_FETCH_CMD https://raw.githubusercontent.com/RPi-Distro/bluez-firmware/master/broadcom/BCM4345C0.hcd
 	vinstall BCM4345C0.hcd 0644 usr/lib/firmware/brcm
 
+	# Firmware for rpi zero 2w wifi chip
+	for f in bin txt clm_blob; do
+		$XBPS_FETCH_CMD https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/buster/brcm/brcmfmac43436-sdio.${f}
+		vinstall brcmfmac43436-sdio.${f} 0644 usr/lib/firmware/brcm
+	done
+	for f in bin txt; do
+		$XBPS_FETCH_CMD https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/buster/brcm/brcmfmac43436s-sdio.${f}
+		vinstall brcmfmac43436s-sdio.${f} 0644 usr/lib/firmware/brcm
+	done
+
 	# Firmware for rpi4/rpi400 wifi chip
 	for f in bin txt clm_blob; do
 		$XBPS_FETCH_CMD https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/buster/brcm/brcmfmac43456-sdio.${f}

             reply	other threads:[~2022-09-05 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 23:42 classabbyamp [this message]
2022-09-07 23:27 ` [PR PATCH] [Merged]: " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39123@inbox.vuxu.org \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).