From: Bob Copeland <me@bobcopeland.com>
To: Vadim <Vadims.Kurmis@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Adding custom channels to ath5k for researching purposes
Date: Thu, 4 Nov 2010 10:47:52 -0400 [thread overview]
Message-ID: <AANLkTinMSH2Vr=iUTD0Pc_OdaM_LFETDEjsOJn+2ZzVD@mail.gmail.com> (raw)
In-Reply-To: <loom.20101104T140201-178@post.gmane.org>
On Thu, Nov 4, 2010 at 9:03 AM, Vadim <Vadims.Kurmis@gmail.com> wrote:
> I need to enable 802.11p standard frequencies. How can I accomplish this? I
> found that CRDA is responsible for allowed channels.
Partially -- the channel list is exported by the driver but CRDA
adds additional regulatory restrictions. The driver also imposes
certain regulatory restrictions based on the EEPROM data.
> So, where can I get binary
> frequency/channel database to use my hardware for researching purposes ?
You can create your own database, but you may need to modify the driver to
disregard the EEPROM settings, with the usual disclaimers: we won't support
it and if it breaks you get to keep both pieces.
Also note that ath5k only advertises a partial channel list; you can
get more via all_channels=1 modparam. We don't do this by default
because they make scanning take forever and exceed channel list limits
in netlink.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2010-11-04 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 13:03 Adding custom channels to ath5k for researching purposes Vadim
2010-11-04 14:47 ` Bob Copeland [this message]
2012-05-08 14:50 ` Luis R. Rodriguez
2012-05-08 15:01 ` Richard Farina
2012-05-08 16:30 ` Bob Copeland
2012-05-08 16:49 ` Luis R. Rodriguez
2012-05-08 17:55 ` Bob Copeland
2012-05-08 18:24 ` Luis R. Rodriguez
2012-05-08 9:04 ` wangqinlong
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='AANLkTinMSH2Vr=iUTD0Pc_OdaM_LFETDEjsOJn+2ZzVD@mail.gmail.com' \
--to=me@bobcopeland.com \
--cc=Vadims.Kurmis@gmail.com \
--cc=linux-wireless@vger.kernel.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.