Hi,
I would lik to know if the ath9k drivers come with inbuilt nl80211 and cfg80211
Or is do i have to separaely download and use nl80211 and cfg80211?
Pl advise
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/l
On Wed, Nov 3, 2010 at 11:00 AM, Queenie de Melo wrote:
> Hi,
>
> I would lik to know if the ath9k drivers come with inbuilt nl80211 and
> cfg80211
>
> Or is do i have to separaely download and use nl80211 and cfg80211?
No you don't have to when you do
sudo modprobe ath9k it will take care of it
Thanks Shafi for your reply.
So nl80211 n cfg80211 is built in the kernel? or is it in the ath9k driver.
iam using kernel 2.6.32 Do i need to apply wireless extension patch? or
will it already have nl80211/cf802.11?
Pl help!
On Wed, Nov 3, 2010 at 12:26 PM, Mohammed Shafi wrote:
> On Wed,
Thanks Shafi for your reply.
So nl80211 n cfg80211 is built in the kernel? or is it in the ath9k driver.
iam using kernel 2.6.32 Do i need to apply wireless extension
patch? or will it already have nl80211/cf802.11?
Pl help!
On Wed, Nov 3, 2010 at 12:26 PM, Mohammed Shafi
wrote:
>
> On Wed
Thanks Shafi for your reply.
So nl80211 n cfg80211 is built in the kernel? or is it in the ath9k driver.
iam using kernel 2.6.32 Do i need to apply wireless extension
patch? or will it already have nl80211/cf802.11?
Pl help!
> On Wed, Nov 3, 2010 at 12:26 PM, Mohammed Shafi
> wrote:
>>
On Wed, Nov 3, 2010 at 7:33 PM, Queenie de Melo wrote:
> Thanks Shafi for your reply.
> So nl80211 n cfg80211 is built in the kernel? or is it in the ath9k driver.
> iam using kernel 2.6.32 Do i need to apply wireless extension patch? or
> will it already have nl80211/cf802.11?
> Pl help!
> On
On Wed, Nov 3, 2010 at 3:12 PM, Queenie de Melo wrote:
> Thanks Shafi for your reply.
>
> So nl80211 n cfg80211 is built in the kernel? or is it in the ath9k driver.
>
> iam using kernel 2.6.32 Do i need to apply wireless extension
> patch? or will it already have nl80211/cf802.11?
>
Please
many thanks Jonathan and Shafi for your valuable inputs...
I have gone through the docs.
We are using an SDK that has kernel 2.6.32.13 used for a mips64 target
board. hence the reason for not moving to the lastest kernel.
in my kernel(2.6.32.13) , i do not see CONFIG_WEXT_* in my .config.
Any cl
