All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Hardware or software limitation?
Date: Fri, 03 Aug 2012 03:19:59 +0200	[thread overview]
Message-ID: <501B273F.5020406@ionic.de> (raw)
In-Reply-To: <1343846868.18731.YahooMailClassic@web120706.mail.ne1.yahoo.com>

Hi Seth,

it is both, really.

Both cards likely have a world roaming regulatory roaming set in their EEPROM
(check dmesg...). On top of that information, restrictions for your current
country are added.

You cannot bypass the card's EEPROM value without hacking the kernel source
(well... with hacking, yes, you could, there is a patch, and I do that as well,
but always within country law.)

Note that "no IBSS" in the iw list output also means "no beaconing" and hence
"no AP mode".


* On 01.08.2012 08:47 PM, Seth Baker wrote:
> I can use 5Ghz AP mode on one, but not the other.
> [...]
>             * 5745 MHz [149] (30.0 dBm)
>             * 5765 MHz [153] (30.0 dBm)
>             * 5785 MHz [157] (30.0 dBm)
>             * 5805 MHz [161] (30.0 dBm)
>             * 5825 MHz [165] (30.0 dBm)

AP mode possible on those 5 channels with the second card, but the first one has
"no IBSS" set on all non-disabled channels (probably due to a preconfigured
world regdom in the EEPROM chip.)

Best regards,


Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4506 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120803/9f609596/attachment.bin 

  reply	other threads:[~2012-08-03  1:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 18:47 [ath9k-devel] Hardware or software limitation? Seth Baker
2012-08-03  1:19 ` Mihai Moldovan [this message]
     [not found] <1343964291.53026.YahooMailClassic@web120701.mail.ne1.yahoo.com>
2012-08-03  8:04 ` Mihai Moldovan

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=501B273F.5020406@ionic.de \
    --to=ionic@ionic.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.