From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
proski@gnu.org, ath5k-devel@lists.ath5k.org,
linux-wireless@vger.kernel.org, ic.felix@gmail.com,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: Ath5k and proprietary extensions
Date: Mon, 31 Aug 2009 08:53:12 -0400 [thread overview]
Message-ID: <20090831125312.GB11006@hash.localnet> (raw)
In-Reply-To: <40f31dec0908282151t245912f0ye79684d4a519f3c9@mail.gmail.com>
On Sat, Aug 29, 2009 at 07:51:29AM +0300, Nick Kossifidis wrote:
> Most code is there for half/quarter and (static) turbo operation, we
> just have to deal with pll programming, clock settings etc. Question
> is how do we use it, NL80211_CMD_TESTMODE is an option i guess and in
> case no one else thinks that we could use a channel width API (or
> extend what we have) for setting 5/10/40MHz width through cfg80211, we
> can just stick to NL80211_CMD_TESTMODE.
Well, we will have a channel width API, I think; several people
have expresed an interest in doing so.
Your summary is useful, and I really don't have any qualms about
keeping the non-standard stuff as long as someone has plans to
write the code to support it. I personally have no interest
in using those features, but of course I only speak for me.
If we do remove turbo code for now, we can leave the initvals, as
they are such a pain to verify. But I'm not sure half a page of
text is worth the churn.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-08-31 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 4:51 Ath5k and proprietary extensions Nick Kossifidis
2009-08-29 7:18 ` [ath5k-devel] " Benoit PAPILLAULT
2009-08-29 9:56 ` RHS Linux User
2009-08-29 15:47 ` Nick Kossifidis
2009-08-29 19:15 ` Luis R. Rodriguez
2009-08-31 12:53 ` Bob Copeland [this message]
2009-09-01 14:37 ` Jouni Malinen
2009-09-01 20:31 ` Pavel Roskin
2009-09-30 3:11 ` [ath5k-devel] " Aditya
2009-09-01 21:39 ` Luis R. Rodriguez
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=20090831125312.GB11006@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=ic.felix@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=nbd@openwrt.org \
--cc=proski@gnu.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 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).