CONFIG_WLAN getting disabled - copy-list usage
FYI, if anyone's using backports with a copy-list file that restricts the wifi drivers to their own, and is working against a recent tree that includes the drivers/net/wireless/realtek/ move, then CONFIG_WLAN will end up getting disabled.
To fix that for now modify your copy-list to include drivers/net/wireless/realtek/Makefile (and that file only).
Once Kconfig changes go in and the Makefile statement
obj-$(CONFIG_WLAN) += realtek/
changes to
obj-$(CONFIG_WLAN_REALTEK) += realtek/
(or similar) this issue will go away.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 10 lines · Johannes Berg
FYI, if anyone's using backports with a copy-list file that restricts the wifi drivers to their own, and is working against a recent tree that includes the
drivers/net/wireless/realtek/move, thenCONFIG_WLANwill end up getting disabled.To fix that for now modify your copy-list to include
drivers/net/wireless/realtek/Makefile(and that file only).Once
Kconfigchanges go in and theMakefilestatement
Quoted 7 lines
obj-$(CONFIG_WLAN) += realtek/
changes to
obj-$(CONFIG_WLAN_REALTEK) += realtek/
(or similar) this issue will go away.
Thanks. It worked for me. As Kalle intends to move more drivers into vendor subfolder, can we expect this will happen again. Can we fix up kconfig handling for this?
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 17 lines · Arend van Spriel
Quoted 16 lines · Johannes Berg
FYI, if anyone's using backports with a copy-list file that restricts
the wifi drivers to their own, and is working against a recent tree that includes thedrivers/net/wireless/realtek/move, thenCONFIG_WLAN
will end up getting disabled.To fix that for now modify your copy-list to include
drivers/net/wireless/realtek/Makefile(and that file only).Once
Kconfigchanges go in and theMakefilestatementobj-$(CONFIG_WLAN) += realtek/
changes to
Quoted 8 lines
Quoted 3 lines
obj-$(CONFIG_WLAN_REALTEK) += realtek/
(or similar) this issue will go away.
Thanks. It worked for me. As Kalle intends to move more drivers into vendor subfolder, can we expect this will happen again. Can we fix up kconfig handling for this?
I asked Kalle and he's planning to also add per-vendor Kconfig, at which point this will not be needed any more. Like ethernet has, really.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in