From: Michael Buesch <mb@bu3sch.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] d80211: Split antenna selection into TX and RX antenna
Date: Wed, 21 Feb 2007 17:12:53 +0100 [thread overview]
Message-ID: <200702211712.54089.mb@bu3sch.de> (raw)
In-Reply-To: <200702211702.46661.IvDoorn@gmail.com>
On Wednesday 21 February 2007 17:02, Ivo van Doorn wrote:
> Currently d80211 only uses a single variable for antenna selection,
> some devices (rt2x00) can configure the TX and RX antenna
> seperately from eachother.
> Assuming that antenna_sel is only for tx, and rx is "the other antenna"
> is flawed and does hinder possible switching of RX antenna based
> on RSSI results. And configuring the wrong antenna also impacts
> transfer rates and link quality.
>
> This patch will remove the usage of the IOCTL call:
> PRISM2_PARAM_ANTENNA_SEL but will restore the usage of
> (the already excisting) IOCTL calls PRISM2_PARAM_ANTSEL_TX and
> PRISM2_PARAM_ANTSEL_RX.
>
> Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
>
> ---
>
> diff --git a/include/net/d80211.h b/include/net/d80211.h
> index 551fe46..68c8c8a 100644
> --- a/include/net/d80211.h
> +++ b/include/net/d80211.h
> @@ -196,7 +196,8 @@ struct ieee80211_tx_control {
> * above */
> u8 retry_limit; /* 1 = only first attempt, 2 = one retry, .. */
> u8 power_level; /* per-packet transmit power level, in dBm */
> - u8 antenna_sel; /* 0 = default/diversity, 1 = Ant0, 2 = Ant1 */
> + u8 antenna_sel_tx; /* 0 = default/diversity, 1 = Ant0, 2 = Ant1 */
> + u8 antenna_sel_rx; /* 0 = default/diversity, 1 = Ant0, 2 = Ant1 */
This doesn't make sense to me.
Why should we want to set the RX antenna on TXing a packet?
> s8 key_idx; /* -1 = do not encrypt, >= 0 keyidx from
> * hw->set_key() */
> u8 icv_len; /* length of the ICV/MIC field in octets */
> @@ -285,10 +286,9 @@ struct ieee80211_conf {
> u8 antenna_max; /* maximum antenna gain */
> short tx_power_reduction; /* in 0.1 dBm */
>
> - int antenna_sel; /* default antenna conf:
> - * 0 = default/diversity,
> - * 1 = Ant0,
> - * 2 = Ant1 */
> + /* 0 = default/diversity, 1 = Ant0, 2 = Ant1 */
> + u8 antenna_sel_tx;
> + u8 antenna_sel_rx;
This makes sense, yes. I ack this.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-21 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:02 [PATCH 1/3] d80211: Split antenna selection into TX and RX antenna Ivo van Doorn
2007-02-21 16:12 ` Michael Buesch [this message]
2007-02-21 16:27 ` Ivo van Doorn
2007-02-21 16:36 ` Michael Buesch
2007-02-21 17:06 ` Ivo van Doorn
2007-02-23 16:53 ` Jiri Benc
2007-02-22 18:46 ` Dan Williams
2007-02-22 18:45 ` 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=200702211712.54089.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--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).