From: "John W. Linville" <linville@tuxdriver.com>
To: Ronald Wahl <ronald.wahl@raritan.com>
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] differing world regulary domain (linux kernel builtin vs. crda)
Date: Fri, 28 Feb 2014 09:13:56 -0500 [thread overview]
Message-ID: <20140228141355.GA30876@tuxdriver.com> (raw)
In-Reply-To: <530F6027.9010608@raritan.com>
On Thu, Feb 27, 2014 at 04:56:23PM +0100, Ronald Wahl wrote:
> Hi,
>
> on "Thu May 16 17:06:52 EDT 2013" Johannes Berg posted a message on
> that list with the subject "[PATCH] regulatory: enable channels
> 52-64 and 100-144 for world roaming" which has been later applied to
> the kernel but not in the official regdb. Now the sitiuation is this
> that the built-in world regulatory domain has a greater frequency
> range than the world regulatory domain installed by crda (albeit for
> passive scanning only). Unfortunately the built-in is not used when
> crda is installed. I'm very much interested in getting this change
> into the official regdb as it allows finding and accessing wireless
> networks with unprovisioned wireless devices that are otherwise not
> detected. Is there any reason why the additional channels cannot be
> added for regdomain 00 in the official regdb?
>
> thx,
> ron
>
> PS: Please keep me in Cc:!
Someone needs to post a patch...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
prev parent reply other threads:[~2014-02-28 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 15:56 [wireless-regdb] differing world regulary domain (linux kernel builtin vs. crda) Ronald Wahl
2014-02-28 14:13 ` John W. Linville [this message]
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=20140228141355.GA30876@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ronald.wahl@raritan.com \
--cc=wireless-regdb@lists.infradead.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.