View | Details | Raw Unified | Return to bug 733148
Collapse All | Expand All

(-)file_not_specified_in_diff (-2 / +5 lines)
Line  Link Here
The brcmsmac driver requests firmware but doesn't document the
The brcmsmac driver requests firmware but doesn't document the
1
dependency. This means that software that analyzes the modules to
1
dependency. This means that software that analyzes the modules to
2
determine if firmware is needed won't detect it.
2
determine if firmware is needed won't detect it.
3
Specifically, (at least) openSUSE won't install the kernel-firmware
3
Specifically, (at least) openSUSE won't install the kernel-firmware
4
package if no hardware requires it.
4
package if no hardware requires it.
5
This patch adds the MODULE_FIRMWARE directives.
5
This patch adds the MODULE_FIRMWARE directives.
6
--
7
drivers/staging/brcm80211/brcmsmac/mac80211_if.c |    4 ++++
6
drivers/staging/brcm80211/brcmsmac/mac80211_if.c |    4 ++++
8
1 file changed, 4 insertions(+)
7
1 file changed, 4 insertions(+)
9
-- a/drivers/staging/brcm80211/brcmsmac/mac80211_if.c
8
++ b/drivers/staging/brcm80211/brcmsmac/mac80211_if.c
Lines 1737-1742 char *brcms_firmwares[MAX_FW_IMAGES] = { Link Here
1737
	NULL
1737
	NULL
1738
};
1738
};
1739
1739
1740
/* This needs to be adjusted when brcms_firmware changes */
1741
MODULE_FIRMWARE("brcm/bcm43xx-0.fw");
1742
MODULE_FIRMWARE("brcm/bcm43xx_hdr-0.fw");
1743
1740
/*
1744
/*
1741
 * precondition: perimeter lock has been acquired
1745
 * precondition: perimeter lock has been acquired
1742
 */
1746
 */

Return to bug 733148