[ath9k-devel] Ath9k: changing regulatory domain

2011-04-11 Thread Adrien Decostre
Hello all,

 I am quite new to the ath9k driver and I am currently trying to use this
driver for an access point on the 5GHz band.

The problem is that my card has a regulation domain set to WORA_WORLD 0x6A
which prevents the card to do active probing on any 5GHz channel. I tried
setting different country codes but this does not improve the situation, so
I suspect that the limitation comes from the regulatory domain.

So I am now looking to a way to adapt the reg_domain on the EEPROM of the
Wifi card. On some posts, I found references to the ath_info tool to modify
the reg_domain on the EEPROM but I did not even manage to install this tool
yet.

So, would someone know any other method to adapt the reg_domain?

 Thanks in advance for any answers or advices.

Best regards
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Mohammed Shafi
2011/4/11 Hasan Rashid hras...@avionica.com:
 That's exactly what I did, also, I had to add the vendor ID in the hw_init
 function for the driver to fully load. I got it to work after making these
 changes in the ath9k driver.

yes i missed it, you could got in debug messages.

 Now I have a different problem. In AP mode using hostapd, the driver doesn't
 transmit at a higher rate than 54Mbit. The iw tool reports only non-HT data
 rates. Does the vendor id need to be added somewhere else as well for the
 rate control algorithm to load 802.11n HT rates? Using iperf I can only
 get a transmit rate up to 29Mbps. However, when I transmit from an 802.11n
 station, it works like you would expect, a throughput of 70-80 Mbps.

you need enable  in .config
IEEE 802.11n (High Throughput) support
CONFIG_IEEE80211N=y
and also in hostapd.conf

 Note: You will also need to enable WMM for full HT functionality.
#ieee80211n=1



 Thank you!

 Regards, Hasan R.
 
 From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
 Sent: اتوار 10/04/2011 8:14 AM
 To: Hasan Rashid
 Cc: ath9k-devel@lists.ath9k.org
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 5:39 PM, Mohammed Shafi shafi.at...@gmail.com
 wrote:
 On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com wrote:
 Hello All,

 I recently purchased a Sparklan WPEA-121N, it uses the AR9382 chipset. It
 is
 mentioned as supported on the device list, however, when I load that
 ath9k
 modules nothing comes up.

 Does ath9k support this chipset? I compiled compat-wirless on Ubuntu
 10.10
 on an x86 Core2Duo machine.

 lspci -vvvnn returns the following:

 02:00.0 Ethernet controller [0200]: Atheros Communications Inc. Device
 [168c:abcd] (rev 01)

 Yes AR9382 is supported in ath9k, your device id 'abcd' ?
 Did you check with the latest compat wireless?

 I doubt the vendor id, if you get you vendor id some thing like this might
 help
 diff --git a/drivers/net/wireless/ath/ath9k/pci.c
 b/drivers/net/wireless/ath/ath9k/pci.c
 index e83128c..594336a 100644
 --- a/drivers/net/wireless/ath/ath9k/pci.c
 +++ b/drivers/net/wireless/ath/ath9k/pci.c
 @@ -30,6 +30,7 @@ static DEFINE_PCI_DEVICE_TABLE(ath_pci_id_table) = {
     { PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI   */
     { PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
     { PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E  AR9300 */
 +   { PCI_VDEVICE(ATHEROS, 0xabcd) }, /* PCI-E  AR9300 */
     { PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E  AR9485 */
     { 0 }
  };




     Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr-
 Stepping- SERR- FastB2B- DisINTx-
     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort-
 TAbort- MAbort- SERR- PERR- INTx-
     Latency: 0, Cache Line Size: 32 bytes
     Interrupt: pin A routed to IRQ 15
     Region 0: Memory at fc8e (64-bit, non-prefetchable)
 [size=128K]
     Expansion ROM at fc8d [disabled] [size=64K]
     Capabilities: [40] Power Management version 3
     Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
 PME(D0+,D1+,D2-,D3hot+,D3cold-)
     Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
     Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
     Address:   Data: 
     Masking:   Pending: 
     Capabilities: [70] Express (v2) Endpoint, MSI 00
     DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
 1us,
 L1 8us
     ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
     DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
 Unsupported-
     RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
     DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
 TransPend-
     LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
 Latency L0 2us, L1 64us
     ClockPM- Surprise- LLActRep- BwNot-
     LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
 CommClk+
     ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
     LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
 DLActive- BWMgmt- ABWMgmt-
     DevCap2: Completion Timeout: Not Supported, TimeoutDis+
     DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
     LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
 SpeedDis-, Selectable De-emphasis: -6dB
  Transmit Margin: Normal Operating Range,
 EnterModifiedCompliance- ComplianceSOS-
  Compliance De-emphasis: -6dB
     LnkSta2: Current De-emphasis Level: -6dB
     Capabilities: [100 v1] Advanced Error Reporting
     UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
 UnxCmplt-
 RxOF- MalfTLP- ECRC- 

Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Hasan Rashid
 
Which .config? Are you speaking of buildin hostapd with 802.11n support?

I do have ieee80211n set to 1 in hostapd.conf. I have used the same 
hostapd.conf with other 802.11n cards and it worked just fine, I will attach it 
nonetheless.

Hasan R.

-Original Message-
From: ath9k-devel-boun...@lists.ath9k.org 
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
Sent: Monday, April 11, 2011 10:13 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011/4/11 Hasan Rashid hras...@avionica.com:
 That's exactly what I did, also, I had to add the vendor ID in the 
 hw_init function for the driver to fully load. I got it to work after 
 making these changes in the ath9k driver.

yes i missed it, you could got in debug messages.

 Now I have a different problem. In AP mode using hostapd, the driver 
 doesn't transmit at a higher rate than 54Mbit. The iw tool reports 
 only non-HT data rates. Does the vendor id need to be added somewhere 
 else as well for the rate control algorithm to load 802.11n HT rates? 
 Using iperf I can only get a transmit rate up to 29Mbps. However, when 
 I transmit from an 802.11n station, it works like you would expect, a 
 throughput of 70-80 Mbps.

you need enable  in .config
IEEE 802.11n (High Throughput) support
CONFIG_IEEE80211N=y
and also in hostapd.conf

 Note: You will also need to enable WMM for full HT functionality.
#ieee80211n=1



 Thank you!

 Regards, Hasan R.
 
 From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
 Sent: اتوار 10/04/2011 8:14 AM
 To: Hasan Rashid
 Cc: ath9k-devel@lists.ath9k.org
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 5:39 PM, Mohammed Shafi 
 shafi.at...@gmail.com
 wrote:
 On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com wrote:
 Hello All,

 I recently purchased a Sparklan WPEA-121N, it uses the AR9382 
 chipset. It is mentioned as supported on the device list, however, 
 when I load that ath9k modules nothing comes up.

 Does ath9k support this chipset? I compiled compat-wirless on Ubuntu 
 10.10 on an x86 Core2Duo machine.

 lspci -vvvnn returns the following:

 02:00.0 Ethernet controller [0200]: Atheros Communications Inc. 
 Device [168c:abcd] (rev 01)

 Yes AR9382 is supported in ath9k, your device id 'abcd' ?
 Did you check with the latest compat wireless?

 I doubt the vendor id, if you get you vendor id some thing like this 
 might help diff --git a/drivers/net/wireless/ath/ath9k/pci.c
 b/drivers/net/wireless/ath/ath9k/pci.c
 index e83128c..594336a 100644
 --- a/drivers/net/wireless/ath/ath9k/pci.c
 +++ b/drivers/net/wireless/ath/ath9k/pci.c
 @@ -30,6 +30,7 @@ static DEFINE_PCI_DEVICE_TABLE(ath_pci_id_table) = {
     { PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI   */
     { PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
     { PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E  AR9300 */
 +   { PCI_VDEVICE(ATHEROS, 0xabcd) }, /* PCI-E  AR9300 */
     { PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E  AR9485 */
     { 0 }
  };




     Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr-
 Stepping- SERR- FastB2B- DisINTx-
     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast 
 TAbort-
 TAbort- MAbort- SERR- PERR- INTx-
     Latency: 0, Cache Line Size: 32 bytes
     Interrupt: pin A routed to IRQ 15
     Region 0: Memory at fc8e (64-bit, non-prefetchable) 
 [size=128K]
     Expansion ROM at fc8d [disabled] [size=64K]
     Capabilities: [40] Power Management version 3
     Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
 PME(D0+,D1+,D2-,D3hot+,D3cold-)
     Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 
 PME-
     Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
     Address:   Data: 
     Masking:   Pending: 
     Capabilities: [70] Express (v2) Endpoint, MSI 00
     DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency 
 L0s 1us,
 L1 8us
     ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ 
 FLReset-
     DevCtl: Report errors: Correctable- Non-Fatal- 
 Fatal-
 Unsupported-
     RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
     DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ 
 AuxPwr-
 TransPend-
     LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s 
 L1, Latency L0 2us, L1 64us
     ClockPM- Surprise- LLActRep- BwNot-
     LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- 
 Retrain-
 CommClk+
     ExtSynch- ClockPM- AutWidDis- BWInt- 
 AutBWInt-
     LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- 
 SlotClk+
 DLActive- BWMgmt- ABWMgmt-
     DevCap2: Completion Timeout: Not Supported, 
 

Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Mohammed Shafi
On Mon, Apr 11, 2011 at 3:16 AM, Serene Gud serene_...@yahoo.co.in wrote:

 Hi all,


 I am able to print out the present operating frequency from the
 ath9k/main.c file in dmesg and if I change the frequency using iwconfig, the
 output of of dmesg shows that the frequency has been changed. As far as I
 could figure out struct ieee80211_channel is defined in
 ./include/net/cfg80211.h which defines one element as center_freq. But what
 I do not know is that which file has the code that is affected by the
 iwconfig wlan0 channel # command because struct ieee80211_channel is used
 in may files in ./net/mac80211 ./net/wireless and
 ./drivers/net/wireless/ath/ath9k folders mainly.

 *driver in main.c see ath_set_channel which is called by ath9k_config (this
is called by mac80211 callback .config)
*then look at ieee80211_set_channel in mac80211
* look at wext-* files (complex)

 If anybody knows, kindly share...
 Thanks!

 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel


___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Hasan Rashid
 
Do I absolutely need Kernel 2.6.36 for AR9382? I am running 2.6.35 at the 
moment. 

One of the AR9382 based radio's vendors got back to me and mentioned that I 
need that for the driver work right.

I did compile 
http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2011-03-31.tar.bz2
 on Ubuntu Natty 2.6.38 and it had the same issue.

Hasan R.

-Original Message-
From: ath9k-devel-boun...@lists.ath9k.org 
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
Sent: Monday, April 11, 2011 10:13 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011/4/11 Hasan Rashid hras...@avionica.com:
 That's exactly what I did, also, I had to add the vendor ID in the 
 hw_init function for the driver to fully load. I got it to work after 
 making these changes in the ath9k driver.

yes i missed it, you could got in debug messages.

 Now I have a different problem. In AP mode using hostapd, the driver 
 doesn't transmit at a higher rate than 54Mbit. The iw tool reports 
 only non-HT data rates. Does the vendor id need to be added somewhere 
 else as well for the rate control algorithm to load 802.11n HT rates? 
 Using iperf I can only get a transmit rate up to 29Mbps. However, when 
 I transmit from an 802.11n station, it works like you would expect, a 
 throughput of 70-80 Mbps.

you need enable  in .config
IEEE 802.11n (High Throughput) support
CONFIG_IEEE80211N=y
and also in hostapd.conf

 Note: You will also need to enable WMM for full HT functionality.
#ieee80211n=1



 Thank you!

 Regards, Hasan R.
 
 From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
 Sent: اتوار 10/04/2011 8:14 AM
 To: Hasan Rashid
 Cc: ath9k-devel@lists.ath9k.org
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 5:39 PM, Mohammed Shafi 
 shafi.at...@gmail.com
 wrote:
 On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com wrote:
 Hello All,

 I recently purchased a Sparklan WPEA-121N, it uses the AR9382 
 chipset. It is mentioned as supported on the device list, however, 
 when I load that ath9k modules nothing comes up.

 Does ath9k support this chipset? I compiled compat-wirless on Ubuntu 
 10.10 on an x86 Core2Duo machine.

 lspci -vvvnn returns the following:

 02:00.0 Ethernet controller [0200]: Atheros Communications Inc. 
 Device [168c:abcd] (rev 01)

 Yes AR9382 is supported in ath9k, your device id 'abcd' ?
 Did you check with the latest compat wireless?

 I doubt the vendor id, if you get you vendor id some thing like this 
 might help diff --git a/drivers/net/wireless/ath/ath9k/pci.c
 b/drivers/net/wireless/ath/ath9k/pci.c
 index e83128c..594336a 100644
 --- a/drivers/net/wireless/ath/ath9k/pci.c
 +++ b/drivers/net/wireless/ath/ath9k/pci.c
 @@ -30,6 +30,7 @@ static DEFINE_PCI_DEVICE_TABLE(ath_pci_id_table) = {
     { PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI   */
     { PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
     { PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E  AR9300 */
 +   { PCI_VDEVICE(ATHEROS, 0xabcd) }, /* PCI-E  AR9300 */
     { PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E  AR9485 */
     { 0 }
  };




     Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr-
 Stepping- SERR- FastB2B- DisINTx-
     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast 
 TAbort-
 TAbort- MAbort- SERR- PERR- INTx-
     Latency: 0, Cache Line Size: 32 bytes
     Interrupt: pin A routed to IRQ 15
     Region 0: Memory at fc8e (64-bit, non-prefetchable) 
 [size=128K]
     Expansion ROM at fc8d [disabled] [size=64K]
     Capabilities: [40] Power Management version 3
     Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
 PME(D0+,D1+,D2-,D3hot+,D3cold-)
     Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 
 PME-
     Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
     Address:   Data: 
     Masking:   Pending: 
     Capabilities: [70] Express (v2) Endpoint, MSI 00
     DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency 
 L0s 1us,
 L1 8us
     ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ 
 FLReset-
     DevCtl: Report errors: Correctable- Non-Fatal- 
 Fatal-
 Unsupported-
     RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
     DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ 
 AuxPwr-
 TransPend-
     LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s 
 L1, Latency L0 2us, L1 64us
     ClockPM- Surprise- LLActRep- BwNot-
     LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- 
 Retrain-
 CommClk+
     ExtSynch- ClockPM- AutWidDis- BWInt- 
 AutBWInt-
     LnkSta: Speed 2.5GT/s, Width 

Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Serene Gud


--- On Mon, 4/11/11, Mohammed Shafi shafi.at...@gmail.com wrote:

From: Mohammed Shafi shafi.at...@gmail.com
Subject: Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k
To: Serene Gud serene_...@yahoo.co.in
Cc: ath9k ath9k-devel@lists.ath9k.org
Date: Monday, April 11, 2011, 9:49 AM



On Mon, Apr 11, 2011 at 3:16 AM, Serene Gud serene_...@yahoo.co.in wrote:

Hi all,


I am able to print out the present operating frequency from the ath9k/main.c 
file in dmesg and if I change the frequency using iwconfig, the output of of 
dmesg shows that the frequency has been changed. As far as I could figure out 
struct ieee80211_channel is defined in ./include/net/cfg80211.h which defines 
one element as center_freq. But what I do not know is that which file has the 
code that is affected by the iwconfig wlan0 channel # command because struct 
ieee80211_channel is used in may files in ./net/mac80211 ./net/wireless and 
./drivers/net/wireless/ath/ath9k folders mainly.


*driver in main.c see ath_set_channel which is called by ath9k_config (this is 
called by mac80211 callback .config) 
*then look at ieee80211_set_channel in mac80211
* look at wext-* files (complex)


If anybody knows, kindly share...
Thanks!

___

ath9k-devel mailing list

ath9k-devel@lists.ath9k.org

https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Yes, I am printing the value of operating frequency from ath_set_channel in 
ath9k/main.c and it comes up in the dmesg every time I change the value with 
iwconfig. 

Thanks a lot for the telling me about ieee80211_set_channel in mac80211 !


___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Serene Gud
I M using linux kernel downloaded from kernel.org instead of compat-wireless.

But I was able to find tthe following:

./include/net/cfg80211.h:int cfg80211_wext_giwname
./include/net/cfg80211.h:int cfg80211_wext_siwmode
./include/net/cfg80211.h:int cfg80211_wext_giwmode
./include/net/cfg80211.h:int cfg80211_wext_siwscan
./include/net/cfg80211.h:int cfg80211_wext_giwscan
./include/net/cfg80211.h:int cfg80211_wext_siwmlme
./include/net/cfg80211.h:int cfg80211_wext_giwrange
./include/net/cfg80211.h:int cfg80211_wext_siwgenie

Not sure of how to use them 8-|



--- On Mon, 4/11/11, Mohammed Shafi shafi.at...@gmail.com wrote:

From: Mohammed Shafi
 shafi.at...@gmail.com
Subject: Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k
To: Serene Gud serene_...@yahoo.co.in
Date: Monday, April 11, 2011, 9:53 AM

also wext-core.c
static const struct iw_ioctl_description standard_ioctl[] = {
    [IW_IOCTL_IDX(SIOCSIWCOMMIT)] = {


On Mon, Apr 11, 2011 at 8:21 PM, Mohammed Shafi shafi.at...@gmail.com wrote:

in wext-compat.c 
static const iw_handler cfg80211_handlers[] = {
    [IW_IOCTL_IDX(SIOCGIWNAME)] = (iw_handler) cfg80211_wext_giwname,

    [IW_IOCTL_IDX(SIOCSIWFREQ)] = (iw_handler) cfg80211_wext_siwfreq,

    [IW_IOCTL_IDX(SIOCGIWFREQ)] = (iw_handler) cfg80211_wext_giwfreq,
    [IW_IOCTL_IDX(SIOCSIWMODE)] = (iw_handler) cfg80211_wext_siwmode,
    [IW_IOCTL_IDX(SIOCGIWMODE)] = (iw_handler) cfg80211_wext_giwmode,


    [IW_IOCTL_IDX(SIOCGIWRANGE)]    = (iw_handler) cfg80211_wext_giw

On Mon, Apr 11, 2011 at 8:19 PM, Mohammed Shafi shafi.at...@gmail.com wrote:




On Mon, Apr 11, 2011 at 3:16 AM, Serene Gud serene_...@yahoo.co.in wrote:



Hi all,


I am able to print out the present operating frequency from the ath9k/main.c 
file in dmesg and if I change the frequency using iwconfig, the output of of 
dmesg shows that the frequency has been changed. As far as I could figure out 
struct ieee80211_channel is defined in ./include/net/cfg80211.h which defines 
one element as center_freq. But what I do not know is that which file has the 
code that is affected by the iwconfig wlan0 channel # command because struct 
ieee80211_channel is used in may files in ./net/mac80211 ./net/wireless and 
./drivers/net/wireless/ath/ath9k folders mainly.




*driver in main.c see ath_set_channel which is called by ath9k_config (this is 
called by mac80211 callback .config) 
*then look at ieee80211_set_channel in mac80211


* look at wext-* files (complex)




If anybody knows, kindly share...
Thanks!

___

ath9k-devel mailing list

ath9k-devel@lists.ath9k.org

https://lists.ath9k.org/mailman/listinfo/ath9k-devel








___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Mohammed Shafi
On Mon, Apr 11, 2011 at 6:58 AM, Hasan Rashid hras...@avionica.com wrote:

 I have contacted the manufacturer of the card as well. The correspondent 
 claimed to have used ath9k without any issues. When I first rant lspci the 
 output looked suspiciously bogus to me as well for this card.

 I am using a Ubuntu 10.10 x86 distro and I have little reason to believe 
 lspci has a bug in it. It's most likely that card's eeprom has a bogus vendor 
 id in it. Any how, I was able to modify the code to load the driver for this 
 vendor id. The only problem now is that the driver transmit at non-HT rates 
 only.

 The iw phy info output is attached. I have about 29 clients associated with 
 this AP.

if you have 29 clients and incase you run the traffic surely the rate
will be low and what about the legacy stations.


 Hasan R.


 -Original Message-
 From: ath9k-devel-boun...@lists.ath9k.org 
 [mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
 Sent: Sunday, April 10, 2011 11:41 AM
 To: Adrian Chadd
 Cc: ath9k-devel@lists.ath9k.org; Peter Stuge
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 9:04 PM, Adrian Chadd adr...@freebsd.org wrote:
 Incorrect or misplaced EEPROM/OTP data, perhaps?
 From what I gather, the PCI ID on earlier devices is loaded out of
 EEPROM by the silicon itself at power-on. 'abcd' sounds a bit too
 convenient to be what's in EEPROM/OTP; so maybe it's a default value in the 
 silicon?
 (All just conjecture here at this point.)

 Yes, 'abcd' surely looks like a default value stored.


 Adrian
 On 10 April 2011 23:17, Mohammed Shafi shafi.at...@gmail.com wrote:

 On Sun, Apr 10, 2011 at 8:41 PM, Peter Stuge pe...@stuge.se wrote:
  Mohammed Shafi wrote:
   Is this a serious proposal from Atheros, or just your attempt at
   a quick fix?
 
  No! its purely a personal idea (am completely responsible for the
  mistake),and I will take a look at it carefully to fix this.
 
  Sorry, I didn't mean that you made a mistake, just that the
  suggestion probably would not get us closer to the actual issue.
 
  Bus level issues are indeed difficult. :\

 thanks, i did not know that. thought simple as adding another device id.
 
 
   A device having an unexpected PCI id means that something is
   really wrong in the device or on the bus, and the solution is
   rarely to pretend that it didn't happen.]
 
  Yeah I can see that, hoping that I may get a correct Device ID
  from the reporter. I dont think 'abcd' is a proper vendor id.
 
  Yes, it's easy to spot. The question is how we can find out *why*
  this happened, so that this error case can be prevented.

 Yes sure.
 
 
   Since this card should work fine in principle, maybe it's some
   issue with missing, or wrong, firmware stored on the Linux system.
 
  AR9382 does not seems to have firmware
 
  Aha! That's only for the USB devices maybe. I don't know much
  detail for these latest devices.
 
 currently only  ath9k_htc needs firmware.

 
  and you have any idea what might went wrong.
 
  Sorry, I don't understand what you mean here.

 Your suggestions about what might have went wrong, as you had already
 told it might be a bus level issue.

 
 
  Also why its detected as Ethernet Controller rather than Network
  controller.
 
  This string comes from the pciutils package and could easily have
  changed. Better look at the numerical device class code, which is
  what is read from hardware.

 thanks, I will look into that.

 
  But I expect that when one thing in config space (device id) is
  bogus then the rest of config space is also quite possibly bogus,
  for the same reason, whatever it is.
 
 
  //Peter
  ___
  ath9k-devel mailing list
  ath9k-devel@lists.ath9k.org
  https://lists.ath9k.org/mailman/listinfo/ath9k-devel
 
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel


 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel

 This communication contains information that may be confidential or 
 privileged. The information is solely intended for the use of the addressee. 
 If you are not the intended recipient, be advised that any disclosure, copy, 
 distribution, or use of the contents of this communication is prohibited. If 
 you have received this communication in
 error, please immediately notify the sender by telephone or by electronic 
 mail.
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Hasan Rashid
 
The throughput results are consistent regardless of mixed or purely 802.11n 
clients. If you notice the iw phy info shows only non-HT data rates. This 
wasn't the case when I used a Ralink 2860 chipset based card.

Hasan R. 

-Original Message-
From: Mohammed Shafi [mailto:shafi.at...@gmail.com] 
Sent: Monday, April 11, 2011 12:05 PM
To: Hasan Rashid
Cc: Adrian Chadd; ath9k-devel@lists.ath9k.org; Peter Stuge
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

On Mon, Apr 11, 2011 at 6:58 AM, Hasan Rashid hras...@avionica.com wrote:

 I have contacted the manufacturer of the card as well. The correspondent 
 claimed to have used ath9k without any issues. When I first rant lspci the 
 output looked suspiciously bogus to me as well for this card.

 I am using a Ubuntu 10.10 x86 distro and I have little reason to believe 
 lspci has a bug in it. It's most likely that card's eeprom has a bogus vendor 
 id in it. Any how, I was able to modify the code to load the driver for this 
 vendor id. The only problem now is that the driver transmit at non-HT rates 
 only.

 The iw phy info output is attached. I have about 29 clients associated with 
 this AP.

if you have 29 clients and incase you run the traffic surely the rate will be 
low and what about the legacy stations.


 Hasan R.


 -Original Message-
 From: ath9k-devel-boun...@lists.ath9k.org 
 [mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed 
 Shafi
 Sent: Sunday, April 10, 2011 11:41 AM
 To: Adrian Chadd
 Cc: ath9k-devel@lists.ath9k.org; Peter Stuge
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 9:04 PM, Adrian Chadd adr...@freebsd.org wrote:
 Incorrect or misplaced EEPROM/OTP data, perhaps?
 From what I gather, the PCI ID on earlier devices is loaded out of 
 EEPROM by the silicon itself at power-on. 'abcd' sounds a bit too 
 convenient to be what's in EEPROM/OTP; so maybe it's a default value in the 
 silicon?
 (All just conjecture here at this point.)

 Yes, 'abcd' surely looks like a default value stored.


 Adrian
 On 10 April 2011 23:17, Mohammed Shafi shafi.at...@gmail.com wrote:

 On Sun, Apr 10, 2011 at 8:41 PM, Peter Stuge pe...@stuge.se wrote:
  Mohammed Shafi wrote:
   Is this a serious proposal from Atheros, or just your attempt 
   at a quick fix?
 
  No! its purely a personal idea (am completely responsible for the 
  mistake),and I will take a look at it carefully to fix this.
 
  Sorry, I didn't mean that you made a mistake, just that the 
  suggestion probably would not get us closer to the actual issue.
 
  Bus level issues are indeed difficult. :\

 thanks, i did not know that. thought simple as adding another device id.
 
 
   A device having an unexpected PCI id means that something is 
   really wrong in the device or on the bus, and the solution is 
   rarely to pretend that it didn't happen.]
 
  Yeah I can see that, hoping that I may get a correct Device ID 
  from the reporter. I dont think 'abcd' is a proper vendor id.
 
  Yes, it's easy to spot. The question is how we can find out *why* 
  this happened, so that this error case can be prevented.

 Yes sure.
 
 
   Since this card should work fine in principle, maybe it's some 
   issue with missing, or wrong, firmware stored on the Linux system.
 
  AR9382 does not seems to have firmware
 
  Aha! That's only for the USB devices maybe. I don't know much 
  detail for these latest devices.
 
 currently only  ath9k_htc needs firmware.

 
  and you have any idea what might went wrong.
 
  Sorry, I don't understand what you mean here.

 Your suggestions about what might have went wrong, as you had 
 already told it might be a bus level issue.

 
 
  Also why its detected as Ethernet Controller rather than Network 
  controller.
 
  This string comes from the pciutils package and could easily have 
  changed. Better look at the numerical device class code, which is 
  what is read from hardware.

 thanks, I will look into that.

 
  But I expect that when one thing in config space (device id) is 
  bogus then the rest of config space is also quite possibly bogus, 
  for the same reason, whatever it is.
 
 
  //Peter
  ___
  ath9k-devel mailing list
  ath9k-devel@lists.ath9k.org
  https://lists.ath9k.org/mailman/listinfo/ath9k-devel
 
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel


 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel

 This communication contains information that may be confidential or 
 privileged. The information is solely intended for the use of the addressee. 
 If you are not the intended recipient, be advised that any disclosure, copy, 
 distribution, or use of the contents of this communication is prohibited. If 
 you 

Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Mohammed Shafi
2011/4/11 Hasan Rashid hras...@avionica.com:

 Do I absolutely need Kernel 2.6.36 for AR9382? I am running 2.6.35 at the 
 moment.

you need =2.6.36 as mentioned in
http://linuxwireless.org/en/users/Drivers/ath9k


 One of the AR9382 based radio's vendors got back to me and mentioned that I 
 need that for the driver work right.

he should have meant that =2.6.36


 I did compile 
 http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2011-03-31.tar.bz2
  on Ubuntu Natty 2.6.38 and it had the same issue.

but i have 2.6.32-25-generic ubuntu and used the same compat-wireless.
so for compat wireless, 2.6.36 is not a constraint.


 Hasan R.

 -Original Message-
 From: ath9k-devel-boun...@lists.ath9k.org 
 [mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Mohammed Shafi
 Sent: Monday, April 11, 2011 10:13 AM
 To: Hasan Rashid
 Cc: ath9k-devel@lists.ath9k.org
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 2011/4/11 Hasan Rashid hras...@avionica.com:
 That's exactly what I did, also, I had to add the vendor ID in the
 hw_init function for the driver to fully load. I got it to work after
 making these changes in the ath9k driver.

 yes i missed it, you could got in debug messages.

 Now I have a different problem. In AP mode using hostapd, the driver
 doesn't transmit at a higher rate than 54Mbit. The iw tool reports
 only non-HT data rates. Does the vendor id need to be added somewhere
 else as well for the rate control algorithm to load 802.11n HT rates?
 Using iperf I can only get a transmit rate up to 29Mbps. However, when
 I transmit from an 802.11n station, it works like you would expect, a 
 throughput of 70-80 Mbps.

 you need enable  in .config
 IEEE 802.11n (High Throughput) support
 CONFIG_IEEE80211N=y
 and also in hostapd.conf

  Note: You will also need to enable WMM for full HT functionality.
 #ieee80211n=1



 Thank you!

 Regards, Hasan R.
 
 From: Mohammed Shafi [mailto:shafi.at...@gmail.com]
 Sent: اتوار 10/04/2011 8:14 AM
 To: Hasan Rashid
 Cc: ath9k-devel@lists.ath9k.org
 Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

 On Sun, Apr 10, 2011 at 5:39 PM, Mohammed Shafi
 shafi.at...@gmail.com
 wrote:
 On Sat, Apr 9, 2011 at 2:00 AM, Hasan Rashid hras...@avionica.com wrote:
 Hello All,

 I recently purchased a Sparklan WPEA-121N, it uses the AR9382
 chipset. It is mentioned as supported on the device list, however,
 when I load that ath9k modules nothing comes up.

 Does ath9k support this chipset? I compiled compat-wirless on Ubuntu
 10.10 on an x86 Core2Duo machine.

 lspci -vvvnn returns the following:

 02:00.0 Ethernet controller [0200]: Atheros Communications Inc.
 Device [168c:abcd] (rev 01)

 Yes AR9382 is supported in ath9k, your device id 'abcd' ?
 Did you check with the latest compat wireless?

 I doubt the vendor id, if you get you vendor id some thing like this
 might help diff --git a/drivers/net/wireless/ath/ath9k/pci.c
 b/drivers/net/wireless/ath/ath9k/pci.c
 index e83128c..594336a 100644
 --- a/drivers/net/wireless/ath/ath9k/pci.c
 +++ b/drivers/net/wireless/ath/ath9k/pci.c
 @@ -30,6 +30,7 @@ static DEFINE_PCI_DEVICE_TABLE(ath_pci_id_table) = {
     { PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI   */
     { PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
     { PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E  AR9300 */
 +   { PCI_VDEVICE(ATHEROS, 0xabcd) }, /* PCI-E  AR9300 */
     { PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E  AR9485 */
     { 0 }
  };




     Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr-
 Stepping- SERR- FastB2B- DisINTx-
     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
 TAbort-
 TAbort- MAbort- SERR- PERR- INTx-
     Latency: 0, Cache Line Size: 32 bytes
     Interrupt: pin A routed to IRQ 15
     Region 0: Memory at fc8e (64-bit, non-prefetchable)
 [size=128K]
     Expansion ROM at fc8d [disabled] [size=64K]
     Capabilities: [40] Power Management version 3
     Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
 PME(D0+,D1+,D2-,D3hot+,D3cold-)
     Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0
 PME-
     Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
     Address:   Data: 
     Masking:   Pending: 
     Capabilities: [70] Express (v2) Endpoint, MSI 00
     DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency
 L0s 1us,
 L1 8us
     ExtTag- AttnBtn- AttnInd- PwrInd- RBE+
 FLReset-
     DevCtl: Report errors: Correctable- Non-Fatal-
 Fatal-
 Unsupported-
     RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
     DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+
 AuxPwr-
 TransPend-
     LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s
 L1, 

Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Mohammed Shafi
may i ask what is the problem

On Mon, Apr 11, 2011 at 9:34 PM, Serene Gud serene_...@yahoo.co.in wrote:

 I M using linux kernel downloaded from kernel.org instead of
 compat-wireless.

 But I was able to find tthe following:

 ./include/net/cfg80211.h:int cfg80211_wext_giwname
 ./include/net/cfg80211.h:int cfg80211_wext_siwmode
 ./include/net/cfg80211.h:int cfg80211_wext_giwmode
 ./include/net/cfg80211.h:int cfg80211_wext_siwscan
 ./include/net/cfg80211.h:int cfg80211_wext_giwscan
 ./include/net/cfg80211.h:int cfg80211_wext_siwmlme
 ./include/net/cfg80211.h:int cfg80211_wext_giwrange
 ./include/net/cfg80211.h:int cfg80211_wext_siwgenie

 Not sure of how to use them 8-|




 --- On *Mon, 4/11/11, Mohammed Shafi shafi.at...@gmail.com* wrote:


 From: Mohammed Shafi shafi.at...@gmail.com
 Subject: Re: [ath9k-devel] iwconfig drives which modules in the
 kernel/ath9k
 To: Serene Gud serene_...@yahoo.co.in
 Date: Monday, April 11, 2011, 9:53 AM

 also wext-core.c
 static const struct iw_ioctl_description standard_ioctl[] = {
 [IW_IOCTL_IDX(SIOCSIWCOMMIT)] = {


 On Mon, Apr 11, 2011 at 8:21 PM, Mohammed Shafi shafi.at...@gmail.comwrote:

 in wext-compat.c
 static const iw_handler cfg80211_handlers[] = {
 [IW_IOCTL_IDX(SIOCGIWNAME)] = (iw_handler)
 cfg80211_wext_giwname,
 [IW_IOCTL_IDX(SIOCSIWFREQ)] = (iw_handler)
 cfg80211_wext_siwfreq,
 [IW_IOCTL_IDX(SIOCGIWFREQ)] = (iw_handler)
 cfg80211_wext_giwfreq,
 [IW_IOCTL_IDX(SIOCSIWMODE)] = (iw_handler)
 cfg80211_wext_siwmode,
 [IW_IOCTL_IDX(SIOCGIWMODE)] = (iw_handler)
 cfg80211_wext_giwmode,
 [IW_IOCTL_IDX(SIOCGIWRANGE)]= (iw_handler) cfg80211_wext_giw


 On Mon, Apr 11, 2011 at 8:19 PM, Mohammed Shafi shafi.at...@gmail.comwrote:



 On Mon, Apr 11, 2011 at 3:16 AM, Serene Gud serene_...@yahoo.co.inwrote:

 Hi all,


 I am able to print out the present operating frequency from the
 ath9k/main.c file in dmesg and if I change the frequency using iwconfig, the
 output of of dmesg shows that the frequency has been changed. As far as I
 could figure out struct ieee80211_channel is defined in
 ./include/net/cfg80211.h which defines one element as center_freq. But what
 I do not know is that which file has the code that is affected by the
 iwconfig wlan0 channel # command because struct ieee80211_channel is used
 in may files in ./net/mac80211 ./net/wireless and
 ./drivers/net/wireless/ath/ath9k folders mainly.

 *driver in main.c see ath_set_channel which is called by ath9k_config (this
 is called by mac80211 callback .config)
 *then look at ieee80211_set_channel in mac80211
 * look at wext-* files (complex)

 If anybody knows, kindly share...
 Thanks!

 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel





___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Peter Stuge
Adrian Chadd wrote:
 Is there an easy way to get an EEPROM/OTP contents dump in ath9k?

No. I have some PCI problem, so no progress in the EEPROM direction
from me.


//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Peter Stuge
Mohammed Shafi wrote:
 to make sure that HT is configured in driver please do this
 
 diff --git a/drivers/net/wireless/ath/ath9k/hw.c
 b/drivers/net/wireless/ath/ath9k/hw.c
 index 1b5bd13..720a866 100644
 --- a/drivers/net/wireless/ath/ath9k/hw.c
 +++ b/drivers/net/wireless/ath/ath9k/hw.c
 @@ -1855,6 +1855,8 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
 else
 pCap-hw_caps = ~ATH9K_HW_CAP_HT;
 
 +   pCap-hw_caps |= ATH9K_HW_CAP_HT;
 +

The indentation is off, or do you mean to include the added line only
within the else block? If so, remember to add braces.


//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Serene Gud


--- On Mon, 4/11/11, Serene Gud serene_...@yahoo.co.in wrote:

From: Serene Gud serene_...@yahoo.co.in
Subject: Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k
To: Mohammed Shafi shafi.at...@gmail.com
Cc: ath9k ath9k-devel@lists.ath9k.org
Date: Monday, April 11, 2011, 11:03 AM



--- On Mon, 4/11/11, Mohammed Shafi shafi.at...@gmail.com wrote:

From: Mohammed Shafi shafi.at...@gmail.com
Subject: Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k
To: Serene Gud serene_...@yahoo.co.in
Cc: ath9k ath9k-devel@lists.ath9k.org
Date: Monday, April 11, 2011, 9:49 AM



On Mon, Apr 11, 2011 at 3:16 AM, Serene Gud serene_...@yahoo.co.in wrote:

Hi all,


I am able to print out the present operating frequency from the ath9k/main.c 
file in dmesg and if I change the frequency using iwconfig, the output of of 
dmesg shows that the frequency has been changed. As far as I could figure out 
struct ieee80211_channel is defined in ./include/net/cfg80211.h which defines 
one element as center_freq. But what I do not know is that which file has the 
code that is affected by the iwconfig wlan0 channel # command because struct 
ieee80211_channel is used in may files in ./net/mac80211 ./net/wireless and 
./drivers/net/wireless/ath/ath9k folders mainly.


*driver in main.c see ath_set_channel which is called by ath9k_config (this is 
called by mac80211 callback .config) 
*then look at ieee80211_set_channel in mac80211
* look at wext-* files (complex)


If anybody knows, kindly share...
Thanks!

___

ath9k-devel mailing list

ath9k-devel@lists.ath9k.org

https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Yes, I am printing the value of operating frequency from ath_set_channel in 
ath9k/main.c and it comes up in the dmesg every time I change the value with 
iwconfig. 

Thanks a lot for the telling me about ieee80211_set_channel in mac80211 !




In case I need to test and see if I can manually insert a channel value in 
ieee80211_set_channel, what is the best way of doing it? 

My purpose is to know which is the function/struct that I exactly need to 
address when I need to put my function that will make the channel change 
without the use of iwconfig command but on the basis of the data values 
provided in the function; dynamically without intervention. 
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2011-04-11 Thread Hasan Rashid
 
I have attached the driver load output in dmesg.

By the way why does AR9382 require Kernel 2.6.36 or higher? Can you list
the major requirements?

Hasan R.

-Original Message-
From: ath9k-devel-boun...@lists.ath9k.org
[mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Peter Stuge
Sent: Monday, April 11, 2011 12:20 PM
To: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

Mohammed Shafi wrote:
 to make sure that HT is configured in driver please do this
 
 diff --git a/drivers/net/wireless/ath/ath9k/hw.c
 b/drivers/net/wireless/ath/ath9k/hw.c
 index 1b5bd13..720a866 100644
 --- a/drivers/net/wireless/ath/ath9k/hw.c
 +++ b/drivers/net/wireless/ath/ath9k/hw.c
 @@ -1855,6 +1855,8 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
 else
 pCap-hw_caps = ~ATH9K_HW_CAP_HT;
 
 +   pCap-hw_caps |= ATH9K_HW_CAP_HT;
 +

The indentation is off, or do you mean to include the added line only
within the else block? If so, remember to add braces.


//Peter
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

This communication contains information that may be confidential or privileged. 
The information is solely intended for the use of the addressee. If you are not 
the intended recipient, be advised that any disclosure, copy, distribution, or 
use of the contents of this communication is prohibited. If you have received 
this communication in
error, please immediately notify the sender by telephone or by electronic mail.[239836.321983] ath9k: Driver unloaded
[239866.470591] Compat-wireless backport release: 
compat-wireless-2011-03-30-1-g7b4debf
[239866.470597] Backport based on linux-next.git next-20110331
[239866.504285] cfg80211: Calling CRDA to update world regulatory domain
[239866.615488] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[239866.615508] ath9k :02:00.0: setting latency timer to 64
[239866.615655] ath9k_hw_init: ah-hw_version.devid 43981
[239866.618241] cfg80211: World regulatory domain updated:
[239866.618247] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[239866.618254] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 
mBi, 2000 mBm)
[239866.618260] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 
mBi, 2000 mBm)
[239866.618265] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 
mBi, 2000 mBm)
[239866.618271] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 
mBi, 2000 mBm)
[239866.618276] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 
mBi, 2000 mBm)
[239866.624382] ath: EEPROM regdomain: 0x6a
[239866.624385] ath: EEPROM indicates we should expect a direct regpair map
[239866.624392] ath: Country alpha2 being used: 00
[239866.624395] ath: Regpair used: 0x6a
[239866.624401] cfg80211: Updating information on frequency 2412 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624407] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624412] cfg80211: Updating information on frequency 2417 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624418] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624423] cfg80211: Updating information on frequency 2422 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624428] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624433] cfg80211: Updating information on frequency 2427 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624439] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.62] cfg80211: Updating information on frequency 2432 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624449] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624454] cfg80211: Updating information on frequency 2437 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624460] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624465] cfg80211: Updating information on frequency 2442 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624471] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624475] cfg80211: Updating information on frequency 2447 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624481] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624486] cfg80211: Updating information on frequency 2452 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624492] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624496] cfg80211: Updating information on frequency 2457 MHz for a 20 
MHz width channel with regulatory rule:
[239866.624502] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
[239866.624507] cfg80211: Updating information on frequency 2462 MHz for a 20 
MHz 

Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Adrian Chadd
On 12 April 2011 11:09, Sujith m.suj...@gmail.com wrote:

 Adrian Chadd wrote:
  There's actually something in 802.11h that handles switching channels.
 
  Does mac80211 handle sending/receiving CSA?

 Yep.


Cool.

Serene, see if you can find the code that handles CSA. This is where the AP
makes the decision to change channel and informs all associated stations
about the new details. The stations then try re-associating to the new
channel.

That may do exactly what you're after!


Adrian
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] iwconfig drives which modules in the kernel/ath9k

2011-04-11 Thread Larry Vaden
On Mon, Apr 11, 2011 at 10:26 PM, Adrian Chadd adr...@freebsd.org wrote:
 On 12 April 2011 11:09, Sujith m.suj...@gmail.com wrote:

 Adrian Chadd wrote:
  There's actually something in 802.11h that handles switching channels.
 
  Does mac80211 handle sending/receiving CSA?

 Yep.

 Cool.

 Serene, see if you can find the code that handles CSA. This is where the AP
 makes the decision to change channel and informs all associated stations
 about the new details. The stations then try re-associating to the new
 channel.

 That may do exactly what you're after!


 Adrian

This sounds exactly like what Ubiquiti calls AirSelect, with the
following parms:

Enable AirSelect:   
Frequency List: 
Hop Interval:miliseconds
Announce Count:
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel