From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Richard Farina <sidhayn@gmail.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-regdb: flaw in general functionality
Date: Tue, 25 Nov 2008 16:19:42 -0800 [thread overview]
Message-ID: <20081126001942.GN5950@tesla> (raw)
In-Reply-To: <1227580299.32415.2.camel@dv>
On Mon, Nov 24, 2008 at 06:31:39PM -0800, Pavel Roskin wrote:
> On Mon, 2008-11-24 at 21:26 -0500, Richard Farina wrote:
>
> > I'm all for adding it to crda as no-transmit but, is that a valid flag?
> > Also, how well does it work? From a monitor mode interface you can
> > inject raw packets out of the interface. Would just adding
> > "no-transmit" into the crda line work? I certainly don't see this in
> > the crda code anywhere, nor in the definition of regdb file. I presume
> > this has to be added?
>
> I don't know anything about the process for introducing new CRDA flags.
This is documented here:
http://wireless.kernel.org/en/developers/Regulatory#Changingthedatabasefileformat
Luis
next prev parent reply other threads:[~2008-11-26 0:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 22:32 wireless-regdb: flaw in general functionality Richard Farina
2008-11-24 23:12 ` Luis R. Rodriguez
2008-11-24 23:21 ` Pavel Roskin
2008-11-24 23:26 ` Luis R. Rodriguez
2008-11-25 2:26 ` Richard Farina
2008-11-25 2:31 ` Pavel Roskin
2008-11-26 0:19 ` Luis R. Rodriguez [this message]
2008-11-26 0:35 ` Pavel Roskin
2008-11-26 1:02 ` Luis R. Rodriguez
2008-11-26 3:10 ` Richard Farina
2008-11-26 17:05 ` Luis R. Rodriguez
2008-11-26 5:53 ` Michael Renzmann
2008-11-26 17:17 ` Luis R. Rodriguez
2008-11-26 19:55 ` Michael Renzmann
2008-11-26 20:04 ` Johannes Berg
2008-11-27 5:26 ` Michael Renzmann
2008-11-26 17:19 ` Johannes Berg
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=20081126001942.GN5950@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
--cc=sidhayn@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).