Re: [PATCH] ath9k: make driver usable standalone

From: Gábor Stefanik
Date: Wed Aug 17 2011 - 12:26:17 EST


2011/8/17 Pavel Ivanov <paivanof@xxxxxxxxx>:
>> WIRELESS_EXT is not required for configuring wireless on recent
>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
>
> Since what version it's deprecated? Do user-space tools know about this new API?
>
> Neither iwconfig nor iwlist worked for me without WIRELESS_EXT.
>
>
> Pavel
>

Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
configuration tool.

>
> 2011/8/17 Gábor Stefanik <netrolller.3d@xxxxxxxxx>:
>> On Wed, Aug 17, 2011 at 5:28 AM, Pavel Ivanov <paivanof@xxxxxxxxx> wrote:
>>> When ath9k is the only wireless driver included in the build
>>> WIRELESS_EXT configuration option becomes undefined. Because of that
>>> driver becomes essentially unusable as you can't actually connect to
>>> any WiFi network. By including WIRELESS_EXT into Kconfig we ensure
>>> that build with ath9k and without other drivers (having WIRELESS_EXT
>>> selected in their Kconfig) is actually usable.
>>
>> WIRELESS_EXT is not required for configuring wireless on recent
>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
>>
>>>
>>> Signed-off-by: Pavel Ivanov <paivanof@xxxxxxxxx>
>>> ---
>>>
>>> diff --git a/drivers/net/wireless/ath/ath9k/Kconfig
>>> b/drivers/net/wireless/ath/ath9k/Kconfig
>>> index d9c08c6..2573f77 100644
>>> --- a/drivers/net/wireless/ath/ath9k/Kconfig
>>> +++ b/drivers/net/wireless/ath/ath9k/Kconfig
>>> @@ -11,6 +11,7 @@ config ATH9K
>>>        select LEDS_CLASS
>>>        select NEW_LEDS
>>>        select ATH9K_COMMON
>>> +       select WIRELESS_EXT
>>>        ---help---
>>>          This module adds support for wireless adapters based on
>>>          Atheros IEEE 802.11n AR5008, AR9001 and AR9002 family
>



--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/