linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Test for N-mode from userspace?
@ 2009-10-20 15:42 Kunal Gangakhedkar
  2009-10-20 17:28 ` [ath9k-devel] " xxiao
  0 siblings, 1 reply; 7+ messages in thread
From: Kunal Gangakhedkar @ 2009-10-20 15:42 UTC (permalink / raw)
  To: ath9k-devel; +Cc: linux-wireless

Hi,

Is it possible to check for whether the N-mode is alive on the laptop and not 
blocked by the OEM (HP)?

I don't have access to an N-mode AP to try to associate and check; but I'm 
planning to buy a new AP/router - so, might as well go for one having N-mode 
now that it's standardised.

The device I have is AR9285 - which does have N mode support as per the 
following iwconfig output:

kunal@plutonium:~$ iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:"Kunal-home"
          Mode:Managed  Frequency:2.432 GHz  Access Point: 00:1A:70:EE:8D:62
          Bit Rate=5.5 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=70/70  Signal level=-35 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


lspci -v output:
08:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless 
Network Adapter (PCI-Express) (rev 01)                                                  
        Subsystem: Hewlett-Packard Company Device 3040
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at d1200000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- 
Queue=0/0Enable-
        Capabilities: [60] Express Legacy Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [160] Device Serial Number 12-14-24-ff-ff-17-15-00
        Capabilities: [170] Power Budgeting <?>
        Kernel driver in use: ath9k
        Kernel modules: ath9k


iw list output:
Wiphy phy0                                               
        Band 1:                                          
                HT capabilities: 0x104e                  
                        * 20/40 MHz operation            
                        * SM PS disabled                 
                        * 40 MHz short GI                
                        * max A-MSDU len 3839            
                        * DSSS/CCK 40 MHz                
                HT A-MPDU factor: 0x0003 (65535 bytes)   
                HT A-MPDU density: 0x0006 (8 usec)       
                HT MCS set: ff 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
                HT TX/RX MCS rate indexes supported:                       
                        MCS index 0                                        
                        MCS index 1                                        
                        MCS index 2                                        
                        MCS index 3                                        
                        MCS index 4                                        
                        MCS index 5                                        
                        MCS index 6                                        
                        MCS index 7                                        
                Frequencies:                                               
                        * 2412 MHz [1] (20.0 dBm)                          
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (passive scanning)
                        * 2472 MHz [13] (20.0 dBm) (passive scanning)
                        * 2484 MHz [14] (disabled)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point

Thanks,
Kunal

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-20 15:42 Test for N-mode from userspace? Kunal Gangakhedkar
@ 2009-10-20 17:28 ` xxiao
  2009-10-20 18:26   ` Kunal Gangakhedkar
  2009-10-20 23:20   ` Luis R. Rodriguez
  0 siblings, 2 replies; 7+ messages in thread
From: xxiao @ 2009-10-20 17:28 UTC (permalink / raw)
  To: ath9k-devel, Kunal Gangakhedkar; +Cc: linux-wireless

interesting, why is MCS range just 0-7, which means no HT?

xxiao

--- On Tue, 10/20/09, Kunal Gangakhedkar <kunal.gangakhedkar@gmail.com> wrote:

> From: Kunal Gangakhedkar <kunal.gangakhedkar@gmail.com>
> Subject: [ath9k-devel] Test for N-mode from userspace?
> To: ath9k-devel@lists.ath9k.org
> Cc: "linux-wireless" <linux-wireless@vger.kernel.org>
> Date: Tuesday, October 20, 2009, 10:42 AM
> Hi,
> 
> Is it possible to check for whether the N-mode is alive on
> the laptop and not 
> blocked by the OEM (HP)?
> 
> I don't have access to an N-mode AP to try to associate and
> check; but I'm 
> planning to buy a new AP/router - so, might as well go for
> one having N-mode 
> now that it's standardised.
> 
> The device I have is AR9285 - which does have N mode
> support as per the 
> following iwconfig output:
> 
> kunal@plutonium:~$ iwconfig wlan0
> wlan0     IEEE 802.11bgn 
> ESSID:"Kunal-home"
>           Mode:Managed 
> Frequency:2.432 GHz  Access Point: 00:1A:70:EE:8D:62
>           Bit Rate=5.5
> Mb/s   Tx-Power=20 dBm
>           Retry  long
> limit:7   RTS
> thr:off   Fragment thr:off
>           Power Management:on
>           Link Quality=70/70 
> Signal level=-35 dBm
>           Rx invalid nwid:0 
> Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive
> retries:0  Invalid misc:0   Missed
> beacon:0
> 
> 
> lspci -v output:
> 08:00.0 Network controller: Atheros Communications Inc.
> AR9285 Wireless 
> Network Adapter (PCI-Express) (rev 01)     
>                
>                
>             
>         Subsystem: Hewlett-Packard
> Company Device 3040
>         Flags: bus master, fast devsel,
> latency 0, IRQ 17
>         Memory at d1200000 (64-bit,
> non-prefetchable) [size=64K]
>         Capabilities: [40] Power
> Management version 3
>         Capabilities: [50] Message
> Signalled Interrupts: Mask- 64bit- 
> Queue=0/0Enable-
>         Capabilities: [60] Express
> Legacy Endpoint, MSI 00
>         Capabilities: [100] Advanced
> Error Reporting <?>
>         Capabilities: [140] Virtual
> Channel <?>
>         Capabilities: [160] Device
> Serial Number 12-14-24-ff-ff-17-15-00
>         Capabilities: [170] Power
> Budgeting <?>
>         Kernel driver in use: ath9k
>         Kernel modules: ath9k
> 
> 
> iw list output:
> Wiphy phy0             
>                
>              
>    
>         Band 1:     
>                
>                
>     
>                 HT
> capabilities: 0x104e         
>         
>                
>         * 20/40 MHz operation 
>           
>                
>         * SM PS disabled   
>              
>                
>         * 40 MHz short GI   
>             
>                
>         * max A-MSDU len 3839 
>           
>                
>         * DSSS/CCK 40 MHz   
>             
>                 HT
> A-MPDU factor: 0x0003 (65535 bytes)   
>                 HT
> A-MPDU density: 0x0006 (8 usec)   
>    
>                 HT
> MCS set: ff 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
>                 HT
> TX/RX MCS rate indexes supported:       
>            
>    
>                
>         MCS index 0     
>                
>                
>   
>                
>         MCS index 1     
>                
>                
>   
>                
>         MCS index 2     
>                
>                
>   
>                
>         MCS index 3     
>                
>                
>   
>                
>         MCS index 4     
>                
>                
>   
>                
>         MCS index 5     
>                
>                
>   
>                
>         MCS index 6     
>                
>                
>   
>                
>         MCS index 7     
>                
>                
>   
>                
> Frequencies:             
>                
>              
>    
>                
>         * 2412 MHz [1] (20.0 dBm) 
>                
>         
>                
>         * 2417 MHz [2] (20.0 dBm)
>                
>         * 2422 MHz [3] (20.0 dBm)
>                
>         * 2427 MHz [4] (20.0 dBm)
>                
>         * 2432 MHz [5] (20.0 dBm)
>                
>         * 2437 MHz [6] (20.0 dBm)
>                
>         * 2442 MHz [7] (20.0 dBm)
>                
>         * 2447 MHz [8] (20.0 dBm)
>                
>         * 2452 MHz [9] (20.0 dBm)
>                
>         * 2457 MHz [10] (20.0 dBm)
>                
>         * 2462 MHz [11] (20.0 dBm)
>                
>         * 2467 MHz [12] (20.0 dBm)
> (passive scanning)
>                
>         * 2472 MHz [13] (20.0 dBm)
> (passive scanning)
>                
>         * 2484 MHz [14] (disabled)
>                
> Bitrates (non-HT):
>                
>         * 1.0 Mbps
>                
>         * 2.0 Mbps (short preamble
> supported)
>                
>         * 5.5 Mbps (short preamble
> supported)
>                
>         * 11.0 Mbps (short preamble
> supported)
>                
>         * 6.0 Mbps
>                
>         * 9.0 Mbps
>                
>         * 12.0 Mbps
>                
>         * 18.0 Mbps
>                
>         * 24.0 Mbps
>                
>         * 36.0 Mbps
>                
>         * 48.0 Mbps
>                
>         * 54.0 Mbps
>         max # scan SSIDs: 4
>         Supported interface modes:
>              
>    * IBSS
>              
>    * managed
>              
>    * AP
>              
>    * AP/VLAN
>              
>    * monitor
>              
>    * mesh point
> 
> Thanks,
> Kunal
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-20 17:28 ` [ath9k-devel] " xxiao
@ 2009-10-20 18:26   ` Kunal Gangakhedkar
  2009-10-20 23:20   ` Luis R. Rodriguez
  1 sibling, 0 replies; 7+ messages in thread
From: Kunal Gangakhedkar @ 2009-10-20 18:26 UTC (permalink / raw)
  To: austinxxh-ath9k; +Cc: ath9k-devel, linux-wireless

On Tuesday 20 Oct 2009 10:58:31 pm xxiao wrote:
> interesting, why is MCS range just 0-7, which means no HT?
>
> xxiao
>

I have no clue why it's that way - I don't even know what HT means in wireless 
context :)

Sorry, I'm just an end-user in this respect ..

Kunal

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-20 17:28 ` [ath9k-devel] " xxiao
  2009-10-20 18:26   ` Kunal Gangakhedkar
@ 2009-10-20 23:20   ` Luis R. Rodriguez
  2009-10-21  5:37     ` Kunal Gangakhedkar
  1 sibling, 1 reply; 7+ messages in thread
From: Luis R. Rodriguez @ 2009-10-20 23:20 UTC (permalink / raw)
  To: austinxxh-ath9k; +Cc: ath9k-devel, Kunal Gangakhedkar, linux-wireless

On Wed, Oct 21, 2009 at 2:28 AM, xxiao <austinxxh-ath9k@yahoo.com> wrote:
> interesting, why is MCS range just 0-7, which means no HT?

MCS 1-7 is for single stream devices.

http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n

  Luis

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-20 23:20   ` Luis R. Rodriguez
@ 2009-10-21  5:37     ` Kunal Gangakhedkar
  2009-10-21  6:49       ` Luis R. Rodriguez
  0 siblings, 1 reply; 7+ messages in thread
From: Kunal Gangakhedkar @ 2009-10-21  5:37 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: austinxxh-ath9k, ath9k-devel, linux-wireless

On Wednesday 21 Oct 2009 4:50:18 am Luis R. Rodriguez wrote:
> On Wed, Oct 21, 2009 at 2:28 AM, xxiao <austinxxh-ath9k@yahoo.com> wrote:
> > interesting, why is MCS range just 0-7, which means no HT?
>
> MCS 1-7 is for single stream devices.
>
> http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n

So, does this mean that I can use N-mode on this device?
That would be really great, if possible :)

Thanks,
Kunal

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-21  5:37     ` Kunal Gangakhedkar
@ 2009-10-21  6:49       ` Luis R. Rodriguez
  2009-10-21 14:17         ` Kunal Gangakhedkar
  0 siblings, 1 reply; 7+ messages in thread
From: Luis R. Rodriguez @ 2009-10-21  6:49 UTC (permalink / raw)
  To: Kunal Gangakhedkar; +Cc: austinxxh-ath9k, ath9k-devel, linux-wireless

On Wed, Oct 21, 2009 at 2:37 PM, Kunal Gangakhedkar
<kunal.gangakhedkar@gmail.com> wrote:
> On Wednesday 21 Oct 2009 4:50:18 am Luis R. Rodriguez wrote:
>> On Wed, Oct 21, 2009 at 2:28 AM, xxiao <austinxxh-ath9k@yahoo.com> wrote:
>> > interesting, why is MCS range just 0-7, which means no HT?
>>
>> MCS 1-7 is for single stream devices.
>>
>> http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n
>
> So, does this mean that I can use N-mode on this device?

Yes, MCS 7 is your highest rate on your card.

  Luis

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ath9k-devel] Test for N-mode from userspace?
  2009-10-21  6:49       ` Luis R. Rodriguez
@ 2009-10-21 14:17         ` Kunal Gangakhedkar
  0 siblings, 0 replies; 7+ messages in thread
From: Kunal Gangakhedkar @ 2009-10-21 14:17 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: austinxxh-ath9k, ath9k-devel, linux-wireless

On Wednesday 21 Oct 2009 12:19:44 pm Luis R. Rodriguez wrote:
> On Wed, Oct 21, 2009 at 2:37 PM, Kunal Gangakhedkar
>
> <kunal.gangakhedkar@gmail.com> wrote:
> > On Wednesday 21 Oct 2009 4:50:18 am Luis R. Rodriguez wrote:
> >> On Wed, Oct 21, 2009 at 2:28 AM, xxiao <austinxxh-ath9k@yahoo.com> wrote:
> >> > interesting, why is MCS range just 0-7, which means no HT?
> >>
> >> MCS 1-7 is for single stream devices.
> >>
> >> http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n
> >
> > So, does this mean that I can use N-mode on this device?
>
> Yes, MCS 7 is your highest rate on your card.
>

Great.. that is really sweet :)

Thanks,
Kunal

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2009-10-21 14:17 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-20 15:42 Test for N-mode from userspace? Kunal Gangakhedkar
2009-10-20 17:28 ` [ath9k-devel] " xxiao
2009-10-20 18:26   ` Kunal Gangakhedkar
2009-10-20 23:20   ` Luis R. Rodriguez
2009-10-21  5:37     ` Kunal Gangakhedkar
2009-10-21  6:49       ` Luis R. Rodriguez
2009-10-21 14:17         ` Kunal Gangakhedkar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).