From: Marcel Holtmann <marcel@holtmann.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wireless: support internal statically compiled regulatory database
Date: Mon, 14 Dec 2009 08:55:12 +0100 [thread overview]
Message-ID: <1260777312.4041.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20091214032920.GB4743@tuxdriver.com>
Hi John,
> > > +config CFG80211_INTERNAL_REGDB
> > > + bool "use statically compiled regulatory rules database"
> > > + default n
> > > + depends on CFG80211
> > > + ---help---
> > > + This option generates an internal data structure representing
> > > + the wireless regulatory rules described in net/wireless/db.txt
> > > + and includes code to query that database. This is an alternative
> > > + to using CRDA for defining regulatory rules for the kernel.
> > > +
> > > + For details see:
> > > +
> > > + http://wireless.kernel.org/en/developers/Regulatory
> > > +
> > > + Most distributions have a CRDA package. So if unsure, say N.
> >
> > since it is pretty clear that people should be defaulting to CRDA, why
> > not make it depend on CONFIG_EMBEDDED.
>
> Other than expanding the amount of config options available, what are
> the ramifications of selecting CONFIG_EMBEDDED? Is it just a way of
> hiding options that "normal" people don't need to see? Or does it
> have some significant change on the built kernel by itself?
from my understand it is just hiding options, that most people don't
need to see. While you might have the Debian not shipping crda case
here, but mostly this option should only selected by people building
their own special kernel. And lets face it, these are mostly embedded
distros that are building special kernels. Every desktop distro should
be just packaging and installing crda. Just from a pure database update
perspective it makes more sense.
So my personal view on this is that it is an embedded feature and not
something for the general wireless people. My 2 cents.
Regards
Marcel
next prev parent reply other threads:[~2009-12-14 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 1:45 [PATCH 1/2] wireless: support internal statically compiled regulatory database John W. Linville
2009-12-14 1:45 ` [PATCH 2/2] wireless: remove CONFIG_WIRELESS_OLD_REGULATORY John W. Linville
2009-12-14 1:55 ` [PATCH 1/2] wireless: support internal statically compiled regulatory database Marcel Holtmann
2009-12-14 3:29 ` John W. Linville
2009-12-14 7:55 ` Marcel Holtmann [this message]
2009-12-14 13:54 ` John W. Linville
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=1260777312.4041.13.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).