Re: git: 558d63889623 - main - iwlwififw: remove Intel iwlwifi firmware from src.git
Date: Thu, 10 Apr 2025 14:42:54 UTC
On Thu, 10 Apr 2025, Cy Schubert wrote: > In message <202504101335.53ADZR4T007246@gitrepo.freebsd.org>, "Bjoern A. > Zeeb" > writes: >> The branch main has been updated by bz: >> >> URL: https://cgit.FreeBSD.org/src/commit/?id=558d638896239f9cd25b9d825ecfce62 >> ec54681e >> >> commit 558d638896239f9cd25b9d825ecfce62ec54681e >> Author: Bjoern A. Zeeb <bz@FreeBSD.org> >> AuthorDate: 2025-04-08 16:57:14 +0000 >> Commit: Bjoern A. Zeeb <bz@FreeBSD.org> >> CommitDate: 2025-04-10 13:32:49 +0000 >> >> iwlwififw: remove Intel iwlwifi firmware from src.git >> >> Following the example of rtw88 and rtw89 only ship iwlwifi firmware >> from ports/packages. Users are asked to run fwget(8) to install the >> firmware needed for their system or build it from ports >> (see also UPDATING). >> >> This is the end of a long story adding wireless support to fwget(8), >> migrating the firmware for multiple branches into ports, splitting them >> up into flavors, and updating some install media and the installer to >> provide firmware. >> >> The overall amount for new firmware amongst all drivers would have >> added more than 100M of binary blobs to src.git for the first import, >> ignoring future updates which (along with some duplication between >> multiple drivers) was considered too much. >> >> While maintenance within the src tree certainly would have been >> easier in the longer term this seems to be the better solution and >> I would like to thank everyone who helped along the path to get there. >> >> The iwlwififw.4 man page is to stay (for now) and will likely point >> at the appropriate firmware package flavor in the future as well >> so people may find it easier to transition. In the long term this >> information is likely not needed anymore. > > Maybe have the man page mention the port. Yes, that's the plan for iwlwififw.4 (plust flavour depending on chipset/PCI IDs where possible given we do have the information and create it for fwget(8)). The longer term it is a lot easier to tell the user who wants to build themselves to run fwget -n to get the name of the package/flavour automatically and not maintain the information twice or thrice anymore. > It's not like we don't use ports for other firmware either, i.e. CPU > firmware. Ports maintaining firmware are an important part of our ecosystem. iwlwifi(8) just should mention fwget(8) and it does have the reference in SEE ALSO but unlike rtw88.4 and rtw89.4 it misses the sentence in the description. And I didn't want to mangle the fix, and the re-generation of the lists for the iwlwififw.4 man pages into this commit. The changes are queued here too but need to push some other fixes first. /bz -- Bjoern A. Zeeb r15:7