aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib/dev
Commit message (Collapse)AuthorAgeFilesLines
* ath: return error code of HAL_STATUS typeGleb Smirnoff5 days1-1/+1
| | | | Found with: clang -Werror=assign-enum
* mt76: update script to to deal with 7921 and 7925 flavorsJim Chen2026-07-271-8/+17
| | | | | | | | | Update the mt76/zzz_fw_ports_fwget.sh script to set fwget to download mt7921 and mt7925 rather than the these days non-existent mt792x flavor. Sponsored by: The FreeBSD Foundation MFC after: 30 days Differential Revision: https://reviews.freebsd.org/D57242
* qat: driver updates to enhance qat infrastructureHareshx Sankar Raj2026-06-241-7/+4
| | | | | | | | | | | | | | | - Updated QAT infrastructure FW version/AE mask/num_banks fields to facilitate integration of future QAT products. - Exposed service as sym;asym instead of cy for gen4 - Enhanced cpaGetInstances() for accurate instance retrieval - Added 57-bit virtual address support to lac_lock_free_stack - Minor bug fixes and improvements Signed-off-by: Hareshx Sankar Raj <hareshx.sankar.raj@intel.com> Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D57746
* mt76: mt7925: prevent PM from scheduling another delayed work on detachBjoern A. Zeeb2026-06-221-0/+5
| | | | | | | This duplicates 009d92b25f7c from mt7921 which has the full description. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* rtw88: Fix typo in portability glueLambert Lim2026-06-201-1/+1
| | | | | | | | Fix typo in if statement for compiling rtw88 against a Linux target. Signed-off-by: Lambert Lim <lambert@sanesecurityguy.com> Reviewed by: imp,ziaee Pull Request: https://github.com/freebsd/freebsd-src/pull/2262
* mt76: mt7921: depend on lindebugfs and turn debugfs support onBjoern A. Zeeb2026-06-143-0/+9
| | | | | | | | | | | | | Add the missing MODULE_DEPEND() calls for lindebugfs. It is unfortunate that they are shared code between various bus implementations. Ideally we would leave the MODULE_DEPEND() calls in the debugfs.c file instead of adding extra #ifdef guards to the bus attachment files. Turn debugfs support on for mt76(core) and the mt7921 module for now. Sponsonred by: The FreeBSD Foundation MFC after: 3 days
* mt76: mt7921: terminate fw log messages with \nBjoern A. Zeeb2026-06-141-0/+4
| | | | | | | | In order to make the firmware messages spewed on the console readable write one message per line and not one very long line. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* mt76: ensure net80211 com instance before returning from driver loadBjoern A. Zeeb2026-06-146-0/+33
| | | | | | | | | | | | | | | | | | Do as we have done for iwlwifi (f808c43ad923, bee60c989745) add a completion event for device registration which calls into 802.11 and creates the wifi "device" (net80211 com instance). This is needed as otherwise the deferred work in the mt76 drivers (mt7915, mt7921, mt7925, mt7996; but not the 7615 [*]) would make driver loading return before the wifi device is there. We would then continue, e.g., during rc startup and race possibly trying to create a vap (wlan interface) with the underlying device not being registered yet and fail. [*] the 7615 does not seem to do this asynchronously so is fine. Sponsored by: The FreeBSD Foundation Tested on: 7921, others to be tested at time MFC after: 3 days
* mt76: mt7921: prevent PM from scheduling another delayed work on detachBjoern A. Zeeb2026-06-141-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Amongst others mt76_connac_pm_unref() is calling mt76_connac_power_save_sched() which will (normaly) re-schedule the pm_work. In various parts we also cancel that work, also during PCI detach ("shutdown", "remove" in LinuxKPI terms). However we also keep calling mt76_connac_pm_unref() in the detach path and thus we get to a point where we re-scheduled the work but then the device goes away. At that point LinuxKPI delayed work has a callput pending which is embedded in the work structure (pm_work). The moment we free the device that structure and callout is gone but the callout is still on the list and once that list is walked we panic. Simply prevent mt76_connac_power_save_sched() from getting to the point of possibly re-scheduling the pm_work by setting pm->enable to false in the beginning of the detach path. The are likely more paths which will need the same treatment as the code is by far anything from "symmetric" (that is the attach path is highly bus independent while the detach path is implemented per-bus). Also other chipsets share the same "logical paths" with their own names, so they will need this too once we get to them. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* LinuxKPI: 802.11: add support for suspend/resumeBjoern A. Zeeb2026-05-243-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for automatic suspend/resume as we know it for wireless. The problem is that the PCI driver which would normally gets the code is the LinuxKPI PCI framework/Linux wireless driver, which we cannot ammend or generally add extra suspend/resume code to. A further problem is that with growing support, the LinuxKPI 802.11 (mac80211) layer also is involved in suspend/resume for WoWLAN (not yet supported) meaning that we need to hook the suspend/resume framework into that as well. Unlike Linux we do not have a general suspend/resume "hook" we can hang into and we need to tie this one to the hardware so cannot indepedently (after the driver one) run it. The solution for FreeBSD, in order to not mangle the Linux native drivers and get extra maintanace overhead, is to add a bus child which inherits the general framework and thus is 2 lines + #includes for each driver extra to add to. The general suspend/resume framework lives in LinuxKPI (linuxkpi_80211_pm) and imitates the normal suspend/resume path overloading it (there is a slight code/logic duplication from the PCI code). Given we are passed the LinuxKPI p(ci)dev, we can go and peel out the net80211 ic from the native bsddev and that way get access to the wireless stack. We then call into LinuxKPI 802.11 in order to do the suspend/resume dance there, and, if needed also call the official suspend/resume routine from the device driver after (reverse for resume). If any in this fails, suspend will be blocked as we will return the error (no different to any native driver could do). The LinuxKPI 802.11 suspend/resume code has the initial code for doing a WoWLAN suspend (one could change the sysctl) but other bits like access to ifnet flags etc. has to be sorted out before we can go and support that. The default code path calles into net80211 to clear everything like native wireless drivers do. The one thing we need to do in addition is to remove the vif devices from the firmware and restore them prior to net80211 resume. We also check for a possible HW SCAN to still be runinng on resume and warn as that may cause problems though the scan should be stopped before suspend (we may still get a callback). You can easily see these problems if you suspend/resume without stopping the wlan. Enable the PM framework for iwlwifi in the module Makefile to be able to use all this; others can follow as tested. In case anyone has problems with this, they can change the sysctl back to 0 until we can figure out any further problems. The linuxkpi_wlan.4 man page got adjusted to document this. Sponsored by: The FreeBSD Foundation Tested on: Dell XPS 13 (AX200), Lenovo TP X270 (AX210) MFC after: 3 days PR: 263632
* iwlwifi: firmware: reduce script to extract fwget informationBjoern A. Zeeb2026-05-171-345/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | Due to driver changes it is no longer feasible to extract the full PCI ID / firmware / card type information in one go as we used to be able to. We have already changed the way we extract firmware information for ports and marked the iwlwififw.4 man page as obsolete. Reduce the script to simply extarct the fwget(8) information and, compared to the old times, sort each section so diffs will be easier to see in the future. This was particular helpful this time to make sure we do not lose entries with the change of technique. We also keep the script in the best perl spirit to do the job but not to win a price, especially given it seems we have to change matters every (other) year. Given we can no longer extract firmware information for the PCI IDs, we need to "manually" check against the ports that names match. Ideally we will simplify things for everything "mld-only" one day to only have a single firmware package for these (even if size increases slightly). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* rtw89: firmware: extend script to extract fwget entriesBjoern A. Zeeb2026-05-171-2/+2
| | | | | | | | The so far so consistent (file)names got an outlier so add the one character longer pattern as well to catch that. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* acpica: Merge ACPICA 20260408Jung-uk Kim2026-05-11359-412/+1611
|\ | | | | | | Merge commit '69ae37302ee98839857791a261546e19d078cdb8'
* | rtw89: fix mismergeBjoern A. Zeeb2026-04-211-0/+2
| | | | | | | | | | | | | | | | | | | | Due to FreeBSD-specific code it seems a code update was not applied to the FreeBSD part during the v6.17 driver update. Add the missing lines. Sponsored by: The FreeBSD Foundation MFC after: 3 days Fixes: b35044b38f74c
* | ath12k: update Atheros/QCA's ath12k driverBjoern A. Zeeb2026-04-1986-17537/+21943
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath11k: update Atheros/QCA's ath11k driverBjoern A. Zeeb2026-04-1927-110/+1999
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | brcm80211: update Broadcom wireless brcmsmac and brcmfmac driversBjoern A. Zeeb2026-04-1933-112/+106
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath10k: update Atheros/QCA's ath10k driverBjoern A. Zeeb2026-04-1912-51/+100
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath-common: update common Atheros/QCA codeBjoern A. Zeeb2026-04-192-5/+5
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | mt76: update Mediatek's mt76 driverBjoern A. Zeeb2026-04-189-7/+9
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw89: update Realtek's rtw89 driverBjoern A. Zeeb2026-04-1844-535/+5675
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | iwlwifi: update Intel's mvm/mld driversBjoern A. Zeeb2026-04-1880-1099/+1827
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw88: update Realtek's rtw88 driverBjoern A. Zeeb2026-04-1816-34/+78
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 028ef9c96e96197026887c0f092424679298aae8 ( tag: v7.0 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw89: add a warn about beacon_int or dtim_period being 0Bjoern A. Zeeb2026-04-181-0/+4
| | | | | | | | | | | | | | | | | | While after the changes to LinuxKPI 802.11 we should never be assoc and not have dtim_period set, we have seen before that this could happen. Add a WARN as that will help debugging the following DIV 0. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath11k: reduce diff to upstream Atheros/QCA's ath11k driverBjoern A. Zeeb2026-03-197-194/+415
| | | | | | | | | | | | | | | | | | | | It seems that over the time of merging and only partly working on making it compile again a few mis-merges happened. Reduce diff to the v6.19 upstream version so that we only have additions to the driver (usually guarded by #ifdef __FreeBSD__). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath12k: update Atheros/QCA's ath12k driverBjoern A. Zeeb2026-03-1970-5481/+42693
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b ( tag: v6.19 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | ath11k: update Atheros/QCA's ath11k driverBjoern A. Zeeb2026-03-197-191/+380
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | iwlwifi: update Intel's mvm/mld driversBjoern A. Zeeb2026-03-06109-4413/+3108
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b ( tag: v6.19 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | iwlwifi: mld: add LINUXKPI_PARAM_PREFIXBjoern A. Zeeb2026-03-061-0/+4
| | | | | | | | | | | | | | | | | | Add a LINUXKPI_PARAM_PREFIX to mld to properly export the power_scheme module_param (sysctl). This is especially needed given mvm has the same parameter and we need to avoid a clash. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | iwlwifi: adjust driver descriptionBjoern A. Zeeb2026-03-062-2/+7
| | | | | | | | | | | | | | | | | | Adjust the module driver descriptions for mvm and mld to make it clear that this is not a driver for Linux but a Linux-based driver for FreeBSD. Cleanup surroundings. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | iwlwifi: mld: move module_init() to SI_ORDER_SECONDBjoern A. Zeeb2026-03-061-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In FreeBSD the iwlwifi driver is a single kernel module. As for iwlwifi/mvm we need to make sure the common "iwlwifi drv" code is initialized before trying to register the mld sub-driver in order for lists, etc. in the registration code to be initialized. We do this by using an extended (FreeBSD specific) version of module_init which overrides the order parameter of the SYSINIT. Otherwise we can randomly (depending on SYSINIT run order) run into a NULL pointer deref panic. Sponsored by: The FreeBSD Foundation PR: 291120 MFC after: 3 days
* | iwlwifi: fixup link_id for certain casesBjoern A. Zeeb2026-03-051-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In iwl_mvm_mld_vif_cfg_changed_station() if we do not do MLO (which we do not do yet at all), dtim_period is not yet set but asssoc is (our common case) the link_id can become -1 as active_links is always 0 for the non-MLO case. This leads to logging of a WARN; Invalid link ID for session protection: 4294967295 Fixup the link_id if it is -1 to be 0. This is the deflink link_id so that should always be fine in this case. For Linux 7.0-rc2 that code is already gone so this is a local temporary stopgap measure for the mvm-mld devices (e.g., some AX210). Sponosred by: The FreeBSD Foundation MFC after: 3 days
* | brcm80211: update Broadcom wireless brcmsmac and brcmfmac driversBjoern A. Zeeb2026-02-119-35/+65
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | brcmfmac: make USB parts compile (and not panic right away)Bjoern A. Zeeb2026-02-102-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix casts and consts and add one extra error check for a NULL pointer. This will require [a future] linuxkpi_usb. There are very few dongles I know off: - the original Raspberry PI USB dongle [1] - Cisco Linksys AE1200 The reason for making USB compile despite the limited 11n 150/300 Mbit/s adapters is that it is the simplest way to work on cfg80211 while on the road, not requiring a full PCIe slot or another SoC for SDIO. Sponsored by: The FreeBSD Foundation Hardware donated by: Martin Husemann (martin NetBSD.org) [1] MFC after: 3 days
* | brcm80211: add LinuxKPI files and module MakefilesBjoern A. Zeeb2026-02-1020-0/+609
| | | | | | | | | | | | | | | | | | | | | | | | | | | | sys/compat/linuxkpi/common/include/linux/platform_data/brcmfmac.h is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ). Currently only PCIe is made to compile. It does load firmware (if needed, e.g., on arm64 with an alignment issue fixed), and starts to come up. To make it work there is a cfg80211 layer and netdevice integration to do, so do not hold your breath just yet.
* | brcm80211: import Broadcom wireless brcmsmac and brcmfmac driversBjoern A. Zeeb2026-02-10133-0/+116023
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ). We are likely only going to use the brcmfmac driver but given they come nicely packaged in a directory structure and bwn(9) still uses GPL-only phy files we could use some of the information from brcmsmac and fix that (should it ever still be relevant). git-subtree-dir: sys/contrib/dev/broadcom/brcm80211 git-subtree-mainline: 69c64e3fb575e0db0e2f0c1fc56f466624940ded git-subtree-split: 1eabd3ed89eb4bb5c69e90eeaeda1a6dd31e8bab
* | ath10k: update Atheros/QCA's ath10k driverBjoern A. Zeeb2026-02-101-8/+8
| | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b ( tag: v6.19 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw89: harmonize all MODULE_DEPEND to rtw89Bjoern A. Zeeb2026-02-104-8/+13
| | | | | | | | | | | | | | | | rtw89 came like rtw88 was done. Given rtw88 once was split up rtw89 got modelled the same way. Clean this up too. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw89: cleanup static_assert() callsBjoern A. Zeeb2026-02-109-58/+0
| | | | | | | | | | | | | | | | | | These days we can use static_assert() without trouble so remove the FreeBSD-specific rtw89_static_assert implementation. This reduces the diff to upstream and will ease future driver updates. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | rtw88: harmonize all MODULE_DEPEND to rtw88Bjoern A. Zeeb2026-02-104-12/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the time I used to split up the driver into a core part and bus attachment sub-drivers the various bus attachments had their own module name but all is "rtw88" now. Core functionality depends on linuxkpi, linuxkpi_wlan, and for debug.c lindebugfs. Each bus attachment then depends on its own parent layer if needed: PCI gets pull in through linuxkpi, USB: depends on [the future] linuxkpi_usb, and SDIO: depends on [the future] linuxkpi_sdio. Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D55021
* | rtw89: update Realtek's rtw89 driverBjoern A. Zeeb2026-02-1057-1093/+4642
| | | | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days PR: 285228
* | ath10k: usb: make compile using [a future] linuxkpi_usbBjoern A. Zeeb2026-02-091-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make ath10k usb code compile just to gather more USB bits. Currently (and likely forever) it is useless as the ath10k USB implementation never got finished. At the moment it lacks an entry for the USB bus attachment in core.c ath10k_hw_params_list[]. ath10k_usb0 on uhub1 ath10k_usb0: <Qualcomm Atheros USBWLAN, rev 2.01/92.10, addr 6> on usbus0 ath10k_usb0: Warning: ath10k USB support is incomplete, don't expect anything to work! ath10k_usb0: Unsupported hardware version: 0x5020001 ath10k_usb0: could not get hw params (-22) ath10k_usb0: could not probe fw (-22) There is another possible hardware [1] which was also never merged upstream. [1] https://lists.infradead.org/pipermail/ath10k/2024-August/016037.html "[PATCH] wifi: ath10k: add USB device ID for Atheros QCA9377-7" MFC after: 3 days
* | ath10k: harmonize all MODULE_DEPEND to ath10kBjoern A. Zeeb2026-02-094-9/+15
| | | | | | | | | | | | | | | | | | With theoretically multiple bus attachements (unclear if we will ever support anything but PCI) rename the module name to "ath10k" and use it consistently. Move the common depends to core.c and lindebugfs and usb to their respective files. MFC after: 3 days
* | ath10k: cleanup some bits no longer FreeBSD-specificBjoern A. Zeeb2026-02-093-41/+4
| | | | | | | | | | | | | | | | We have since I did this port in 2023 added ACPI support to LinuxKPI, so we can use it. Also there is a linux/of.h header so we no longer need to guard the #include. MFC after: 3 days
* | ath10k: add sysctl to turn on/off fwlogBjoern A. Zeeb2026-02-091-0/+17
| | | | | | | | | | | | | | | | FWLOG, if compiled in, was on by default without a way to stop it from printing everything to the console. Add a modparam to enable it with it being disabled by default if available. MFC after: 3 days
* | ath10k: fix a schedule() callBjoern A. Zeeb2026-02-092-2/+10
| | | | | | | | | | | | | | | | | | | | | | Using kern_yield does not seem ideal either for polling here; use a schedule_timeout() call from LinuxKPI instead and use about 100 iterations per second. Improve an error message to include the error code so we have a better idea of what happens. MFC after: 3 days
* | rtw88: set .bsddriver.name for USB chipsetsBjoern A. Zeeb2026-02-097-4/+13
| | | | | | | | | | | | | | | | | | We use the FreeBSD-specifc bsddriver.name to get the device name; set it everywere consistently. Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D55020
* | mt76: fix a check wrongly giving us random ether addresses all the timeBjoern A. Zeeb2026-02-071-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not cover the is_valid_ether_addr() check under CONFIG_OF. Unclear if this is an initial porting or a merging error before the driver hit the FreeBSD src tree. The end result was that we always got a random link-layer address, while the individual drivers may have setup phy->macaddr and this function would only overwride if given in device tree. Only if both, driver and and the OF backup, fail then go and use the random link-layer address. While here adjust printing the random link-layer address using a FreeBSD format specifier and not the unsupported Linux one. Fixes: 6c92544d7c97 Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | mt76: mt7925: add missing LINUXKPI_PARAM_PREFIXBjoern A. Zeeb2026-02-071-0/+4
| | | | | | | | | | | | | | | | | | | | | | There is a module_param_named() in the file so we need to set LINUXKPI_PARAM_PREFIX to get it a uniq sysctl name. mt7921 has the exact same option. Without their individual prefixes the names would clash on systems with both chipsets and not work for both. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | mt76: make USB compileBjoern A. Zeeb2026-02-072-0/+13
| | | | | | | | | | | | | | | | This is the mt76-specific changes to make the USB driver targets for 7921 and 7925 compile. Sponsored by: The FreeBSD Foundation MFC after: 3 days
generated by cgit v1.3 (git 2.53.0) at 2026-08-12 21:41:12 +0000