All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: set 5/10 MHz supported channels
Date: Fri, 22 Nov 2013 11:30:47 +0100	[thread overview]
Message-ID: <201311221130.47941.sw@simonwunderlich.de> (raw)
In-Reply-To: <CADxDmp6BCFPzoC3njSAvp6sjtaY+W2ToEefDPmLrcWXwXEbQBA@mail.gmail.com>

Kamran,

> I have an AP with  AR9160 tunning openWRT. When I set chennel to 10MHz from
> debugfs entry. I can still connect it with other boards running OpenWrt.
> But from computers running latest linux kernel it was visible in scan when
> I was using AR5416 but I was not able to connect to my AP.
> Then I changed NIC to Atheros AR9227 based card not I can even see openwrt
> AP with 10MHz channel.

Please note that the OpenWRT and the mainline Linux implementation of 5/10 MHz 
are different. In Linux we have a limited but (hopefully) standard-conforming 
implementation, that means that also bitrates are interpreted for their 
respective frequencies. For example on mainline LInux in 5 MHz mode you have 
OFDM bitrates of 1.5, 2.25, 3, 4.5 Mbit/s etc what would be 6, 9, 12, 18 
Mbit/s on 20 MHz. OpenWRT will just announce the 20 MHz bitrates even on 5 MHz 
(it's more of a hack). This will likely confuse the Linux clients. There might 
also be other knobs not complete, as I said I've only tested the IBSS mode.

For the record I tested AR9220 and AR5213 in 5 and 10 MHz mode and after some 
timing corrections (patches have been merged upstream) this worked quite well.

I'd recommend to use only the same implementation together.

Cheers,
    Simon

  parent reply	other threads:[~2013-11-22 10:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  7:02 [ath9k-devel] ath9k: set 5/10 MHz supported channels Kamran Nishat
2013-11-08 10:05 ` Simon Wunderlich
2013-11-08 10:46 ` Sergey Ryazanov
2013-11-12 11:58   ` Kamran Nishat
2013-11-12 13:02     ` Sergey Ryazanov
2013-11-08 15:07 ` Adrian Chadd
2013-11-11  8:11   ` Alex Hacker
2013-11-11  8:57     ` Adrian Chadd
2013-11-11  9:16       ` Alex Hacker
2013-11-11 13:15         ` Kamran Nishat
2013-11-11 14:47           ` sotouki
2013-11-12  6:49             ` Alex Hacker
2013-11-12 16:34             ` Simon Wunderlich
2013-11-18 10:42               ` sotouki
2013-11-18 11:07                 ` Simon Wunderlich
2013-11-18 19:39                   ` Kamran Nishat
2013-11-19 15:16                     ` Simon Wunderlich
2013-11-19 20:07                       ` Adrian Chadd
2013-11-20 14:50                         ` Holger Schurig
2013-11-19 20:12                       ` Johannes Berg
2013-11-21 22:44                       ` Kamran Nishat
2013-11-21 23:27                         ` Adrian Chadd
2013-11-21 23:29                           ` Adrian Chadd
2013-11-22  3:29                             ` Kamran Nishat
2013-11-22  3:33                               ` Adrian Chadd
2013-11-22 10:30                         ` Simon Wunderlich [this message]
     [not found]                           ` <CADxDmp4UnGdSpPXt5B6_GAfkmOcFAx7+36Bv2ymgpWzZHvnRZA@mail.gmail.com>
2013-11-23 14:18                             ` [ath9k-devel] Fwd: " Kamran Nishat
2013-12-13 11:24                               ` sotouki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201311221130.47941.sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.