From: Pannirselvam Kanagaratnam <pannir@xsmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Enabling 4.9 GHz
Date: Sun, 03 Aug 2014 07:05:50 +0800 [thread overview]
Message-ID: <53DD6ECE.5030108@xsmail.com> (raw)
In-Reply-To: <CAJ-Vmok1Lpgxj-Nyrc8Gc=KCAXVHvM-4+Mr8Use8=prU-vniFA@mail.gmail.com>
Thanks Adrian. 2 & 3 are done. Will look into regdb.
Regards,
Pannir
On 03/08/2014 6:18 AM, Adrian Chadd wrote:
> hi!
>
> I think you'll have to hack up a custom regulatory domain database
> that includes the frequencies your device is licenced to work on.
>
> The things that need to happen:
>
> * regdb support, or the driver/802.11 layer won't let you do anything;
> * make sure your AR9590 has the "I'm allowed to do 4.9GHz!" bit in the
> OTP EEPROM set, or the NIC may not let you;
> * then make sure the AR9590 has calibration data for the 4.9GHz
> channel(s), or things won't work very well.
>
>
> -a
>
>
> On 1 August 2014 01:57, Pannirselvam Kanagaratnam <pannir@xsmail.com> wrote:
>> Hello,
>>
>> I would like to know how to enable 4.9 GHz on ath9k. The module I am
>> using is based on AR9590.
>>
>> Regards,
>>
>> Pannir
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next prev parent reply other threads:[~2014-08-02 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 8:57 [ath9k-devel] Enabling 4.9 GHz Pannirselvam Kanagaratnam
2014-08-02 15:15 ` abhinav narain
2014-08-02 15:18 ` Pannirselvam Kanagaratnam
2014-08-02 15:37 ` abhinav narain
2014-08-02 22:45 ` Pannirselvam Kanagaratnam
2014-08-02 22:18 ` Adrian Chadd
2014-08-02 23:05 ` Pannirselvam Kanagaratnam [this message]
2014-08-03 16:31 ` abhinav narain
2014-08-06 10:13 ` Pannirselvam Kanagaratnam
2014-08-06 16:14 ` abhinav narain
2014-08-06 9:54 ` Pannirselvam Kanagaratnam
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=53DD6ECE.5030108@xsmail.com \
--to=pannir@xsmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox