From: Valentin Manea <linux-wireless@mrs.ro>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Intel 4965 HT rates
Date: Mon, 21 Dec 2009 00:36:21 +0200 [thread overview]
Message-ID: <200912210036.21895.linux-wireless@mrs.ro> (raw)
In-Reply-To: <43e72e890912201342w2f5916d0p2b30683ccbb5dbfe@mail.gmail.com>
Hmmm,
Sorry, you are right, Intel describes this as a feature for the 4965. I was
probably running a very old driver(it was before they added support for the
5000 series), because I remember specifically the router reporting a 117Mbs
bitrate.
I'm still trying to track down that driver as it seems quite silly to have
this artificial limitation.
Thanks,
Valentin
On Sunday 20 December 2009 11:42:58 pm Luis R. Rodriguez wrote:
> On Sun, Dec 20, 2009 at 5:10 AM, Valentin Manea <linux-wireless@mrs.ro>
wrote:
> > Hi,
> >
> > I'm running compat-wireless-2.6.33-rc1 and iw list shows some confusing
> > HT capabilities:
> > Band 1:
> > HT capabilities: 0x082c
> > * 20 MHz operation
> > * SM PS disabled
> > * 20 MHz short GI
> > * max A-MSDU len 7935
> >
> > but for 802.11a channels:
> > Band 2:
> > HT capabilities: 0x086e
> > * 20/40 MHz operation
> > * SM PS disabled
> > * 20 MHz short GI
> > * 40 MHz short GI
> > * max A-MSDU len 7935
> >
> > While I can't tell when this happened, I remember older 2.6.29 releases
> > supported HT40 for both bands.
>
> How do you know? What makes you believe that was the case?
>
> > The wireless card is an Intel 4965 on a Thinkpad T61.
>
> The ht_cap that gets parsed and sent back through nl80211 is
> initialized in iwl-agn on iwl-core.c on iwlcore_init_ht_hw_capab() as
> follows
>
> static void iwlcore_init_ht_hw_capab(const struct iwl_priv *priv,
> struct ieee80211_sta_ht_cap *ht_info,
> enum ieee80211_band band)
> {
> ....
> if (priv->hw_params.ht40_channel & BIT(band)) {
> ht_info->cap |= IEEE80211_HT_CAP_SUP_WIDTH_20_40;
> ht_info->cap |= IEEE80211_HT_CAP_SGI_40;
> ht_info->mcs.rx_mask[4] = 0x01;
> max_bit_rate = MAX_BIT_RATE_40_MHZ;
> }
> ....
> }
>
> And the priv->hw_params.ht40_channel gets initialized for 4965
> hardware on iwl4965_hw_set_hw_params():
>
> static int iwl4965_hw_set_hw_params(struct iwl_priv *priv)
> {
> ...
> priv->hw_params.ht40_channel = BIT(IEEE80211_BAND_5GHZ);
> ....
> }
>
> iwl-5000 and iwl-6000 sets this to both bands:
>
> int iwl5000_hw_set_hw_params(struct iwl_priv *priv)
> {
> ....
> priv->hw_params.ht40_channel = BIT(IEEE80211_BAND_2GHZ) |
> BIT(IEEE80211_BAND_5GHZ);
> ....
> }
>
> static int iwl6000_hw_set_hw_params(struct iwl_priv *priv)
> {
> ....
> priv->hw_params.ht40_channel = BIT(IEEE80211_BAND_2GHZ) |
> BIT(IEEE80211_BAND_5GHZ);
> ....
> }
>
> So it appears to be done explicitly in software, not sure if hardware
> does support HT40 on 2.4 GHz band on the 4965, Intel folks would
> though.
>
> Luis
>
next prev parent reply other threads:[~2009-12-20 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 13:10 Intel 4965 HT rates Valentin Manea
2009-12-20 21:42 ` Luis R. Rodriguez
2009-12-20 21:48 ` Luis R. Rodriguez
2009-12-20 21:51 ` Luis R. Rodriguez
2009-12-20 21:52 ` Gábor Stefanik
2009-12-20 22:36 ` Valentin Manea [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-21 2:33 Guy, Wey-Yi W
2009-12-21 2:44 ` Zhu Yi
2009-12-21 13:52 ` Gábor Stefanik
2009-12-28 3:45 ` Zhu Yi
2009-12-28 20:33 ` Gábor Stefanik
2009-12-29 0:46 ` Zhu Yi
2010-01-21 7:18 ` Zhu Yi
2010-01-21 21:09 ` Gábor Stefanik
2010-01-22 1:37 ` Zhu Yi
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=200912210036.21895.linux-wireless@mrs.ro \
--to=linux-wireless@mrs.ro \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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).