search

raspberrypi / linux

Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/
Other
10.96k stars 4.93k forks source link

Please submit brcmfmac43436-sdio and brcmfmac43436s-sdio to linux-firmware.git #4723

Open stintel opened 2 years ago

stintel commented 2 years ago

Describe the bug The firmware required for the Raspberry Pi Zero 2 wireless chip should be published in linux-firmware.git so that distros can ship it without having to worry about being sued by whoever owns the IP.

odhiambo commented 1 year ago

Licensing of the Wi-Fi firmware is the contention. You get it, no?

On Sun, Mar 12, 2023, 23:37 deftdawg @.***> wrote:

@stintel https://github.com/stintel no worries enjoy the show (T2 is epic)! I was more hoping @ossguy https://github.com/ossguy would chime-in so the Pi Zero 2w image could join those officially supported by OpenWRT and the firmware could be distribute through OpenWRT channels.

I know you've done the work to support the arch in the OpenWRT snapshots https://downloads.openwrt.org/snapshots/targets/bcm27xx/bcm2710/ and I'm grateful for it, however the hidden away / temporal nature of snapshots (cannot add new kmods next day when snapshot refreshes) and lack of support in firmware-selector https://firmware-selector.openwrt.org/ make it a bit of a slog to use as a project base.

For those with an established project if you want to use the Pi Zero 2 W's wifi w/ a snapshot build you'll need to do this on your running router hardware:

mkdir -p /lib/firmware/brcm cd /lib/firmware/brcm mount -o rw,remount / wget https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436-sdio.bin wget https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436-sdio.txt wget https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436s-sdio.bin wget https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436s-sdio.txt reboot

wlan0 should now be available

— Reply to this email directly, view it on GitHub https://github.com/raspberrypi/linux/issues/4723#issuecomment-1465294007, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGK4XUAAN5PRGV7XVH2UW3W3Y63JANCNFSM5IOJGFGQ . You are receiving this because you commented.Message ID: @.***>

pawelchcki commented 4 months ago

Hey all. I noticed that since the discussion started the Synaptic licence was added to the rpi fw repo.

I've decided to make a MR upstream: https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/185

But we'll probably need some one from the RPi foundation/company to weigh in. To me the new licence looks good but I'm not a lawyer nor a relevant party here :)

/cc @pelwell

Thanks in advance for looking into it :bow:

pelwell commented 4 months ago

You should at least give the licence file the correct company name - they are Synaptics, not Synaptic.

qrp73 commented 4 days ago

No - both 43436(P) and 43436S are from Synaptics. 43436 appears as 43430B0, and 43436S is 43430A1. The PR above is about the 43438/43436S distinction, where both appear as 43430A1.

If I understand correctly, 43436 has the same hardware and the same ID as 43430B0. And 43436s has the same hardware and ID as 43430A1. Is that correct?

And if I understand correctly there are two firmware Synaptics and Infineon for the same hardware 43436/43430B0 and two firmware for the same hardware 43436s/43430A1. Is that correct?

I'm not sure what is the reason to keep 4 firmware for 2 pairs of hardware identical chips? And how it selects which firmware needs to use if it has the same ID? Does it depends on raspi model id?