From: Daniel Drake <dsd@gentoo.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Ulrich Kunitz <kune@deine-taler.de>,
Joerg Mayer <jmayer@loplof.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] zd1211rw-mac80211: basic regulatory domain support
Date: Sun, 01 Jul 2007 22:09:56 -0400 [thread overview]
Message-ID: <46885E74.8000501@gentoo.org> (raw)
In-Reply-To: <200707020015.32480.mb@bu3sch.de>
Michael Buesch wrote:
> Which registers do control power and where are they written?
We don't know - we program the vendor driver with the default map that
the vendor driver supplies, based on RF type. e.g. see zd_rf_al2230.c
zd1211_al2230_init_hw()
The vendor driver does do some kind of TX power calibration, but it is
not in absolute terms. Instead it is done in increments based on the
current level. So, if we studied the vendor driver enough we might be
able to figure out how to make the TX frames be transmitted with
slightly higher or lower power, but there's no way we'd be able to TX at
a specific strength measured in dBm. (the long term plan is to port
such functionality over from the vendor driver, but there are also many
other items on the list)
I do not recall the vendor driver imposing any TX power restrictions
based on regulatory domain, which is the discussion at hand. So, I don't
think we'll be implementing regdomain-based TX power restrictions in
zd1211rw. That said, patches considered, if someone does manage to
figure it out :)
Daniel
prev parent reply other threads:[~2007-07-02 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 16:39 [PATCH] zd1211rw-mac80211: basic regulatory domain support Daniel Drake
2007-07-01 20:32 ` Joerg Mayer
2007-07-01 21:35 ` Ulrich Kunitz
2007-07-01 22:15 ` Michael Buesch
2007-07-02 2:09 ` Daniel Drake [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=46885E74.8000501@gentoo.org \
--to=dsd@gentoo.org \
--cc=jmayer@loplof.de \
--cc=kune@deine-taler.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).