From: Bob Copeland <me@bobcopeland.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
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 13:55:36 -0400 [thread overview]
Message-ID: <20120508175536.GF25400@localhost> (raw)
In-Reply-To: <CAB=NE6Xx_KKjk5s_CMRopwBuHDxajgn=Jdc_Nbb1DN2s=2QL0A@mail.gmail.com>
On Tue, May 08, 2012 at 09:49:22AM -0700, Luis R. Rodriguez wrote:
> > 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?
/me digs in the archives...
http://marc.info/?l=linux-wireless&m=125752855010045&w=2
I guess I "still" liked it back then :)
So with that setup people who want to fiddle with the card in 'expert'
mode could override the card's eeprom reg domain stuff by suitably
changing crda db instead of recompiling the kernel.
But if I read your follow-ups correctly, going that way wasn't actually
a big win. I didn't then (much less now) have the time to explore it
in actual code.
That doesn't cover the person who wanted to use all_channels, but at
least that is exported by a modparam today. There are probably other
things that an 'expert' would want to do beyond these two, though.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2012-05-08 17:55 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
2012-05-08 17:55 ` Bob Copeland [this message]
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=20120508175536.GF25400@localhost \
--to=me@bobcopeland.com \
--cc=Vadims.Kurmis@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.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.