From: "Luis R. Rodriguez" <mcgrof@frijolero.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: Vadim <Vadims.Kurmis@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Adding custom channels to ath5k for researching purposes
Date: Tue, 8 May 2012 09:49:22 -0700 [thread overview]
Message-ID: <CAB=NE6Xx_KKjk5s_CMRopwBuHDxajgn=Jdc_Nbb1DN2s=2QL0A@mail.gmail.com> (raw)
In-Reply-To: <20120508163018.GE25400@localhost>
On Tue, May 8, 2012 at 9:30 AM, Bob Copeland <me@bobcopeland.com> wrote:
> On Tue, May 08, 2012 at 07:50:06AM -0700, Luis R. Rodriguez wrote:
>> I'm thinking it may make sense to add CONFIG_WIRELESS_EXPERT where we
>> can stuff some of this stuff under. It may be useful for other
>> regulatory testing / certification stuff.
>
> No objection here, so long as this kind of config opt wouldn't become
> a dumping ground (cf. CONFIG_EMBEDDED). "EXPERT" could mean different
> things to different people.
Well it should depend on CONFIG_EXPERT but yeah -- I was surprised to
learn recently even Ubuntu is shipping with CONFIG_EXPERT, so WTF.
Localizing the expert config to wireless might make more sense.
> I still like the idea of exporting more stuff to userspace and letting
> CRDA handle the card-based restrictions, but ISTR you had reasons that
> didn't work for everything.
What do you mean?
Luis
next prev parent reply other threads:[~2012-05-08 16:49 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
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 [this message]
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='CAB=NE6Xx_KKjk5s_CMRopwBuHDxajgn=Jdc_Nbb1DN2s=2QL0A@mail.gmail.com' \
--to=mcgrof@frijolero.org \
--cc=Vadims.Kurmis@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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 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.