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] 802.11n PCI-E 300Mbps with AP mode?
Date: Thu, 14 Jul 2011 22:27:28 +0200	[thread overview]
Message-ID: <4E1F5130.7070803@ionic.de> (raw)
In-Reply-To: <CAN0CFw0tUNFRGr2XnGg5ap1rnX2vXP9mtu48n+p+t4ZtqUiGiw@mail.gmail.com>

* On 14.07.2011 08:56 PM, Grant wrote:
> Will I need to hack the kernel source in order to use an 802.11n card
> in AP mode?

In general, no. But depending on your setup and the card's EEPROM
(hardcoded world regulatory domain for instance), you may run into some
regulatory issues* and are required to patch the module, yeah.

However, if you live in the US and get a card with an US regdomain set
in its EEPROM, everything is fine. Unfortunately there is no way to
determine which regdomain is being used prior mounting it, so no
definite answer here.

Best regards,


Mihai

*) if I remember correctly, there are HT40 channels available on 2GHz in
(world_reg & us_reg), although not all US legitimate channels will work
with an unpatched version of ath9k if the card uses some world
regdomain, as regulatory restrictions are stacking. Ask Google for more,
I've had a thread on this mailing list regarding this as well.

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

  reply	other threads:[~2011-07-14 20:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 22:10 [ath9k-devel] 802.11n PCI-E 300Mbps with AP mode? Grant
2011-07-12 23:23 ` Adrian Chadd
2011-07-13  0:26 ` Galen
2011-07-13  1:20   ` Grant
2011-07-13  1:55     ` Adrian Chadd
2011-07-13 23:42       ` Grant
2011-07-13 23:58         ` Mihai Moldovan
2011-07-14  4:39           ` Adrian Chadd
2011-07-14  0:00         ` Adrian Chadd
2011-07-14  4:18           ` Alex Hacker
2011-07-14 13:23         ` Galen
2011-07-14 18:56           ` Grant
2011-07-14 20:27             ` Mihai Moldovan [this message]
2011-07-15  2:35               ` Grant
2011-07-16  0:04                 ` Mihai Moldovan
2011-07-16 18:47                   ` Grant
2011-07-16 20:14                     ` Mihai Moldovan
2011-07-13 15:22     ` Galen
2011-07-13 17:46       ` Grant
2011-07-13 19:55         ` Grant
2011-07-13 20:29           ` Daniel Smith
2011-07-14 18:54   ` Grant
2011-07-14 20:44     ` Mihai Moldovan
2011-07-15  2:54       ` Grant
2011-07-16  0:28         ` Mihai Moldovan
2011-07-16 19:54           ` Grant
2011-07-16 20:16             ` Mihai Moldovan
2011-07-17  1:58               ` Adrian Chadd
2011-07-17  2:10                 ` Mihai Moldovan
2011-07-17  3:01                   ` Adrian Chadd
2011-07-17 16:34                 ` Grant

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=4E1F5130.7070803@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.